public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5985: fix_truncMN2 (e.g. fix_truncdfdi) and fixuns_truncMN2 incorrect on a29k, alpha, arm, c4x, dsp16xx, i370, i386, ia64, m88k, mips, ns32k, pj, romp, rs6000, s390, sh, xtensa
Date: Thu, 02 Jan 2003 20:26:00 -0000 [thread overview]
Message-ID: <20030102202601.1811.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/5985; it has been noted by GNATS.
From: Hans-Peter Nilsson <hp@bitrange.com>
To: neroden@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<hp@bitrange.com>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: target/5985: fix_truncMN2 (e.g. fix_truncdfdi) and fixuns_truncMN2
incorrect on a29k, alpha, arm, c4x, dsp16xx, i370, i386, ia64, m88k, mips,
ns32k, pj, romp, rs6000, s390, sh, xtensa
Date: Thu, 2 Jan 2003 15:18:02 -0500 (EST)
On 2 Jan 2003 neroden@gcc.gnu.org wrote:
> Synopsis: fix_truncMN2 (e.g. fix_truncdfdi) and fixuns_truncMN2 incorrect on a29k, alpha, arm, c4x, dsp16xx, i370, i386, ia64, m88k, mips, ns32k, pj, romp, rs6000, s390, sh, xtensa
> Theoretically annoyance which appears to not be real; in feedback 9 months.
The FP bits have changed, IIRC by RTH himself making changes in
a direction against his earlier comment. I'll revisit some day.
The issue is real enough for people writing new ports. Sorry I
haven't persisted and still don't.
brgds, H-P
next reply other threads:[~2003-01-02 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 20:26 Hans-Peter Nilsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 18:33 neroden
2002-03-30 16:01 rth
2002-03-17 5:46 hp
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=20030102202601.1811.qmail@sources.redhat.com \
--to=hp@bitrange.com \
--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).