public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: neil@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/7143: real.c: In function `make_nan': `TFbignan' undeclared Date: Fri, 28 Jun 2002 08:40:00 -0000 [thread overview] Message-ID: <20020628153601.8199.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/7143; it has been noted by GNATS. From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: neil@daikokuya.co.uk (Neil Booth) Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: bootstrap/7143: real.c: In function `make_nan': `TFbignan' undeclared Date: Fri, 28 Jun 2002 11:30:36 -0400 (EDT) > I've got a clue. You mentioned you were compiling with -pedantic. The only new clue that I have is tradcpp0 correctly processed the test file. I can't duplicate the problem with a cross compiler. > Is DEC a built-in? If so, -pedantic won't define it because it's in > the user's namespace. If DEC is defined in a file, then it doesn't > matter of course. No, it isn't. I changed DEC to DECXXX and it didn't affect the problem. -pedantic also didn't affect the situation. I'm going to retry the bootstrap using the native compiler. If that fails, I'll try to debug the problem. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2002-06-28 15:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-28 8:40 John David Anglin [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-09 8:16 John David Anglin 2002-11-09 8:08 neil 2002-11-09 4:18 neil 2002-07-01 12:46 John David Anglin 2002-07-01 9:06 Neil Booth 2002-06-27 23:31 Neil Booth 2002-06-27 23:26 neil 2002-06-27 23:20 Neil Booth 2002-06-27 11:56 dave
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=20020628153601.8199.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --cc=gcc-prs@gcc.gnu.org \ --cc=neil@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: linkBe 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).