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
rth@gcc.gnu.org
rth@gcc.gnu.org
Sat Mar 30 16:01:00 GMT 2002
- Previous message (by thread): 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
- Next message (by thread): java/5986: SIGSEGV in __gcj_personality_v0
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
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
State-Changed-From-To: open->feedback
State-Changed-By: rth
State-Changed-When: Sat Mar 30 16:01:26 2002
State-Changed-Why:
I don't think this is really true. The documentation for
these rtx codes only mentions FIX and UNSIGNED_FIX as being
defined for fixed point modes.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5985
- Previous message (by thread): 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
- Next message (by thread): java/5986: SIGSEGV in __gcj_personality_v0
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Gcc-prs
mailing list