public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stephen Biggs <xyzzy@hotpop.com>
To: GCC list <gcc@gcc.gnu.org>
Subject: Re: General search for symbols...
Date: Wed, 09 Apr 2003 08:43:00 -0000	[thread overview]
Message-ID: <1049890222.25387.24.camel@steve> (raw)
In-Reply-To: <Pine.BSF.4.44.0304031906420.54128-100000@dair.pair.com>

On Thu, 2003-04-03 at 22:11, Hans-Peter Nilsson wrote:
> 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.

Ok... I'll check, thanks for the reply.

> 
> > I
> > thought to check to see if either "_VARARGS_H" or "_STDARG_H" was
> > defined.  I am also going to need this for other things.
> 
> I can't guess what you mean by "other things" so I can't help
> you there.

I wish I could tell you, but I am not at liberty, at this time... Thanks
for the advice.

I believe that if I check to see if the function decl for "va_end"
exists, then this tells me whether I am running stdarg or varargs...

> 
> brgds, H-P
> 
> 



  parent reply	other threads:[~2003-04-09  7:06 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
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 [this message]
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=1049890222.25387.24.camel@steve \
    --to=xyzzy@hotpop.com \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).