This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/5985: fix_truncMN2 (e.g. fix_truncdfdi) and fixuns_truncMN2incorrect on a29k, alpha, arm, c4x, dsp16xx, i370, i386, ia64, m88k, mips,ns32k, pj, romp, rs6000, s390, sh, xtensa
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: neroden at gcc dot gnu dot org, <gcc-bugs at gcc dot gnu dot org>, <gcc-prs at gcc dot gnu dot org>, <hp at bitrange dot com>, <nobody at gcc dot gnu dot org>, <gcc-gnats at gcc dot gnu dot org>
- Date: Thu, 2 Jan 2003 15:18:02 -0500 (EST)
- Subject: Re: target/5985: fix_truncMN2 (e.g. fix_truncdfdi) and fixuns_truncMN2incorrect on a29k, alpha, arm, c4x, dsp16xx, i370, i386, ia64, m88k, mips,ns32k, pj, romp, rs6000, s390, sh, xtensa
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
- References:
- 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