public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/7315: [3.2] DEC floating point support in real.c is broken
Date: Sat, 15 Mar 2003 04:06:00 -0000 [thread overview]
Message-ID: <20030315040600.13207.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/7315; it has been noted by GNATS.
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: bangerth@dealii.org, dave@hiauly1.hia.nrc.ca, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, mark@codesourcery.com, nobody@gcc.gnu.org,
gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mark@codesourcery.com,
nobody@gcc.gnu.org
Subject: Re: target/7315: [3.2] DEC floating point support in real.c is broken
Date: Fri, 14 Mar 2003 23:02:20 -0500 (EST)
> Old Synopsis: DEC floating point support in real.c is broken
> New Synopsis: [3.2] DEC floating point support in real.c is broken
>
> State-Changed-From-To: open->analyzed
> State-Changed-By: bangerth
> State-Changed-When: Sat Mar 15 03:29:08 2003
> State-Changed-Why:
> Apparently fixed on 3.3 and mainline, from the audit trail.
> Only 3.2 branch affected.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7315
Well, actually real.c was broken in previous releases but it wasn't used
for native builds. This was changed by ~ for 3.2. Unfortunately, the vax
port in 3.3 and later is broken for several other reasons which I haven't
found time to diagnose.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next reply other threads:[~2003-03-15 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 4:06 John David Anglin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-28 22:14 bangerth
2003-03-15 3:29 bangerth
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=20030315040600.13207.qmail@sources.redhat.com \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).