HELP with linker script!!!
Andreas Schwab
schwab@suse.de
Fri Apr 1 14:34:00 GMT 2005
More information about the Binutils mailing list
Fri Apr 1 14:34:00 GMT 2005
- Previous message (by thread): HELP with linker script!!!
- Next message (by thread): HELP with linker script!!!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Dave Korn" <dave.korn@artimi.com> writes: > ----Original Message---- >>From: Nick Clifton >>Sent: 01 April 2005 15:02 > > >> The other way is hackier, but it avoids the warnings: >> >> int foo __attribute__((section (".cached_bss,\"w\",@nobits#"))); >> >> This assumes that the hash character (#) is the start-of-line-comment >> character for the particular instruction set you are using. If you have >> a look at the assembler emitted by GCC you can see why: >> >> .section .cached_bss,"w",@nobits#,"aw",@progbits >> >> The hash stops GAS from interpreting the >> >> ,"aw",@probits >> >> which gcc has appended to the name of the section... > > <koff> *start*-of-line comment character ......... <g> > > You could either add a \n before the # or use a ';' or whatever the port > uses for the mid-line comment character....... > > And boy, is that _ever_ a gross hack! (I quite like it!) This will fail within #NO_APP. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
- Previous message (by thread): HELP with linker script!!!
- Next message (by thread): HELP with linker script!!!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list