From: Neil Booth <neil@daikokuya.co.uk>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrapping hppa64? CPP problem
Date: Thu, 11 Jul 2002 07:42:00 -0000 [thread overview]
Message-ID: <20020711060708.GB30428@daikokuya.co.uk> (raw)
In-Reply-To: <200207102254.PAA18705@hpsje.cup.hp.com>
Steve Ellcey wrote:-
> I am curious if anyone is currently bootstrapping the hppa64 GCC
> compiler from the latest sources? I am running into a very curious cpp
> problem. With the attached example, using the cc1 that I just built I
> get two definitions of sigpause showing up because _SVID2 seems to be
> considered defined and undefined at the same time. It doesn't happen on
> the other platforms I have tried but it happens consistenly for me on
> PA64.
>
> Steve Ellcey
> sje@cup.hp.com
>
> [hpsje - sje_pa64] $ cat x.c
> #define _SVID2
>
> #if !defined(_SVID2)
> extern long sigpause(long);
> #endif
>
> #if defined(_SVID2)
> extern int sigpause(int);
> #endif
Steve,
Could you step into the code (should be not too hard to grok
for such a simple case) starting with the #define and see
what hash entry pointer is given for _SVID2? Then figure
out why you're not getting it for the !defined line?
A breakpoint on do_define() might be useful; be sure to
step into lex_macro_node () which lexes and creates a hash
entry for _SVID2. If this is a CPP bug I would really like
to catch it.
Neil.
next prev parent reply other threads:[~2002-07-11 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 23:15 Steve Ellcey
2002-07-11 5:32 ` Zack Weinberg
2002-07-11 7:42 ` Neil Booth [this message]
2002-07-11 8:33 ` Neil Booth
2002-07-10 23:56 John David Anglin
2002-07-11 3:22 Steve Ellcey
2002-07-11 3:51 ` Jeff Law
2002-07-11 6:44 ` Neil Booth
2002-07-11 13:16 ` John David Anglin
[not found] <no.id>
2002-07-11 6:34 ` John David Anglin
2002-07-11 13:25 Steve Ellcey
2002-07-11 13:31 ` John David Anglin
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=20020711060708.GB30428@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=sje@cup.hp.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).