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

[Hans-Peter Nilsson]

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