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: Sat, 09 Nov 2002 08:16:00 -0000	[thread overview]
Message-ID: <20021109161604.8795.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@gcc.gnu.org, dave@hiauly1.hia.nrc.ca, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, neil@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, neil@gcc.gnu.org
Subject: Re: bootstrap/7143: real.c: In function `make_nan': `TFbignan' undeclared
Date: Sat, 9 Nov 2002 11:06:31 -0500 (EST)

 > Synopsis: real.c: In function `make_nan': `TFbignan' undeclared
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: neil
 > State-Changed-When: Sat Nov  9 04:17:59 2002
 > State-Changed-Why:
 >     Can I close this?  I find it really hard to believe a CPP bug is biting in this case.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7143
 
 Go ahead.
 
 Dave
 -- 
 J. David Anglin                                  dave.anglin@nrc.ca
 National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


             reply	other threads:[~2002-11-09 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09  8:16 John David Anglin [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-28  8:40 John David Anglin
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=20021109161604.8795.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: 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).