On Sat, May 09, 2009 at 04:27:20PM -0700, H. Peter Anvin wrote:
> Sam Ravnborg wrote:
> > * . = START;
> > * __init_begin = .;
> > * HEAD_SECTION
> > * INIT_TEXT_SECTION(PAGE_SIZE)
> > * INIT_DATA_SECTION(...)
> > * PERCPU(PAGE_SIZE)
> > * __init_end = .;
> > *
> > * __text_begin = .;
> > * TEXT_SECTION = 0
> > * __text_end = .;
> > *
> > * __data_begin = .;
> > * RO_DATA_SECTION(PAGE_SIZE)
> > * RW_DATA_SECTION(...)
> > * __data_end = .;
> > *
> > * EXCEPTION_TABLE(...)
> > * NOTES
> > *
> > * __bss_start = .;
> > * BSS_SECTION(0, 0)
> > * __bss_end = .;
> > * _end = .;
> > *
> > *
> > * [__init_begin, __init_end] is the init section that may be freed after init
> > * [_stext, _etext] is the text section
> > * [_sdata, _edata] is the data section
> > *
> > * Some of the included output section include their own set of constants.
> > * Examples are: [__initramfs_start, __initramfs_end] for initramfs and
> > * [__nosave_begin, __nosave_end] for the nosave data
> > */
> >
>
> It seems rather disturbing to me that different sections have different
> start and end symbols. I realize this is largely for historical
> reasons, but if we used a single pattern (e.g. something like
> __text_start, __text_end for the .text section)
The 'oldish' names were kept only because they are widely used.
I agree to be consistent is better so will change it to be so.
I edited the sample above to consistently use __<section>_{begin,end}.
For now I kept '_end' as I had no better name for it.
> then at least in the
> i386 case we could easily recognize those as relocatable symbols even if
> they show up as absolute.
Do you then say that i386 could allow us to use absolute symbols,
and we could adjust in the code instead?
That would make the linker script nicer but with added
complexity in the code..
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
