From: Zack Weinberg <zack@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Stephen Biggs <xyzzy@hotpop.com>, GCC list <gcc@gcc.gnu.org>
Subject: Re: General search for symbols...
Date: Fri, 04 Apr 2003 09:35:00 -0000 [thread overview]
Message-ID: <87of3m9b6l.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0304031906420.54128-100000@dair.pair.com> (Hans-Peter Nilsson's message of "Thu, 3 Apr 2003 19:11:57 -0500 (EST)")
Hans-Peter Nilsson <hp@bitrange.com> writes:
> On 3 Apr 2003, Stephen Biggs wrote:
>
>> On Wed, 2003-04-02 at 13:34, Hans-Peter Nilsson wrote:
>> > On 2 Apr 2003, Stephen Biggs wrote:
>> > > I am trying to port GCC to another machine.
>> > >
>> > > Given that I have a file <new gcc
>> > > path>/gcc/config/<machine>/<machine>.c, how would I, within any of the
>> > > functions in that file find out if a certain symbol has been defined by
>> > > a "#define" statement in the C source that is being compiled?
>> >
>> > That's an odd need for a new port. Care to elaborate; example?
>> > (It might turn out to be a misunderstanding or a need covered
>> > by an existing mechanism, that's mainly why I ask.)
>>
>> Thanks for the reply.
>>
>> E.g., I need to do something different in the assembly output based on
>> whether varargs.h or stdarg.h was included in the C source file.
>
> Maybe that need is covered by the macro current_function_stdarg.
> See function.h. That particular macro unfortunately seems not
> documented. See also other ports. One or another has probably
> solved the same problem your port has.
Note that as of 3.3 GCC no longer supports <varargs.h>, although there
are still vestiges of the old code for it.
zw
next prev parent reply other threads:[~2003-04-04 3:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 14:10 Stephen Biggs
2003-04-02 16:22 ` Hans-Peter Nilsson
2003-04-03 7:18 ` Stephen Biggs
2003-04-04 2:13 ` Hans-Peter Nilsson
2003-04-04 9:35 ` Zack Weinberg [this message]
2003-04-04 18:51 ` Joe Buck
2003-04-10 9:37 ` Zack Weinberg
2003-04-10 19:36 ` Mike Stump
2003-04-10 20:03 ` Zack Weinberg
2003-04-10 20:12 ` Mike Stump
2003-04-09 8:43 ` Stephen Biggs
2003-04-02 15:07 Ilia Dyatchkov
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=87of3m9b6l.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=xyzzy@hotpop.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).