From: "Dave Korn" <dave.korn@artimi.com>
To: "'Nick Clifton'" <nickc@redhat.com>,
"'Vincent Rubiolo'" <vincent.rubiolo@windriver.com>
Cc: "'Pieter Arnout'" <pieter@powerescape.com>,
<grigory.zagorodnev@intel.com>, <binutils@sources.redhat.com>
Subject: RE: HELP with linker script!!!
Date: Fri, 01 Apr 2005 14:13:00 -0000 [thread overview]
Message-ID: <SERRANOp9O2zVzcQnmA00000016@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <424D545F.70203@redhat.com>
----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!)
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-04-01 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 14:42 Pieter Arnout
2005-03-31 15:50 ` Nick Clifton
[not found] ` <29c1ff0410ff9cc2b88a3ad82d1938aa@powerescape.com>
2005-04-01 11:27 ` Nick Clifton
2005-04-01 12:53 ` Vincent Rubiolo
2005-04-01 14:05 ` Nick Clifton
2005-04-01 14:13 ` Dave Korn [this message]
2005-04-01 14:34 ` Andreas Schwab
2005-04-01 16:53 ` Pieter Arnout
2005-04-04 9:39 ` Vincent Rubiolo
2005-04-04 11:06 ` Nick Clifton
2005-04-04 11:11 ` Dave Korn
2005-04-04 11:59 ` Sergei Organov
2005-04-04 13:39 ` Nick Clifton
2005-03-31 15:08 Zagorodnev, Grigory
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SERRANOp9O2zVzcQnmA00000016@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=binutils@sources.redhat.com \
--cc=grigory.zagorodnev@intel.com \
--cc=nickc@redhat.com \
--cc=pieter@powerescape.com \
--cc=vincent.rubiolo@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).