From: Uwe Reimann <linux-kernel@pulsar.homelinux.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ENTRY-macro in linkage.h
Date: Sun, 09 Feb 2003 13:35:32 +0100 [thread overview]
Message-ID: <3E464B14.5040004@pulsar.homelinux.net> (raw)
In-Reply-To: <1044752435.18908.23.camel@irongate.swansea.linux.org.uk>
My problem is how to add the whitespace. The preprocessor seems to strip
it. Consider this (test.S):
#define ENTRY(X) \
.global X##; \
X##:
ENTRY(foo)
ENTRY(bar)
gcc -S test.S:
.global foo; foo:
.global bar; bar:
For c4x-gcc, this has to be like this:
.global foo
foo:
.global bar
bar:
Without the leading whitespace, .global is taken as a name of a label.
Without the newline before the labels, they are not recognized (taken as
comments).
How can I tell the preprocessor to emit spaces and newlines?
Alan Cox wrote:
>On Sat, 2003-02-08 at 16:51, Uwe Reimann wrote:
>
>
>>Hi,
>>
>>I'm currently porting linux to TI's TMS320C31. I'm using c4x-gcc, which
>>has a problem with the ENTRY-macro from linkage.h. c4x-gcc will accept
>>the generated .globl-directive only if it is preceded by whitescape.
>>Right know, gcc thinks I want to create a label called .globl. Any ideas
>>how to fix this without fixing gcc?
>>
>>
>
>I think every other port will probably be fine with the whitespace present
>so I guess add a space 8)
>
>
>
>
>
next prev parent reply other threads:[~2003-02-09 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 16:51 Uwe Reimann
[not found] ` <1044752435.18908.23.camel@irongate.swansea.linux.org.uk>
2003-02-09 12:35 ` Uwe Reimann [this message]
2003-02-09 16:11 ` Roman Zippel
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=3E464B14.5040004@pulsar.homelinux.net \
--to=linux-kernel@pulsar.homelinux.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®