On Fri, 9 Oct 2015, Daniel Lezcano wrote: > On 10/09/2015 03:46 PM, Marc Gonzalez wrote: > > On 09/10/2015 15:24, Daniel Lezcano wrote: > > [ ... ] > > > On a tangential subject, it would seem that platforms with verbose logs > > at init might benefit from marking as __initconst strings used in __init > > functions. > > > > I discussed this some time ago: > > https://lkml.org/lkml/2015/3/25/688 > > > > which pointed to an earlier discussion: > > https://lkml.org/lkml/2014/8/21/255 > > https://lkml.org/lkml/2014/6/22/149 > > Thanks for the pointer. > > Nicolas Pitre (Cc'ed) is working on optimizing the memory consumption by > stripping unreferenced code at compile time. Perhaps he thought a solution for > this particular use case.
This is different. Here those strings are actually referenced and can't be discarded. The solution is to mark them so they go in the appropriate section as suggested. It might be worth investigating the addition of a new gcc function attribute that provides a replacement section for .data, .rodata, etc. in addition to .text, that would apply to data objects created within that function. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
