From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7706 invoked by alias); 17 Mar 2002 13:46:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 7662 invoked by uid 71); 17 Mar 2002 13:46:02 -0000 Resent-Date: 17 Mar 2002 13:46:02 -0000 Resent-Message-ID: <20020317134602.7661.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-To: nobody@gcc.gnu.org Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, hp@bitrange.com Received:(qmail 4225 invoked by uid 61); 17 Mar 2002 13:42:15 -0000 Message-Id:<20020317134214.4223.qmail@sources.redhat.com> Date: Sun, 17 Mar 2002 05:46:00 -0000 From: hp@bitrange.com Reply-To: hp@bitrange.com To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version:gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: 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 X-SW-Source: 2002-03/txt/msg00595.txt.bz2 List-Id: >Number: 5985 >Category: target >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 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Mar 17 05:46:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Hans-Peter Nilsson >Release: trunk and 3.1 branch and everywhere else >Organization: >Environment: >Description: >>From , edited: While checking on the floating point operations and comparing with the manual and other targets, it seems several targets (briefly: a29k, alpha, arm, c4x, dsp16xx, i370, i386, ia64, m88k, mips, ns32k, pj, romp, rs6000, s390, sh, xtensa) have fix_truncMN2 patterns that are incorrectly expressed. For example for M=df N=di, the input operand should be (fix:DI (fix:DF (DF-operand)) not just (fix:DI (DF-operand)), since the latter expression requires/promises that the operand is already truncated to an integer in a float-mode, which is the input operand for the fixdfdi2 pattern. Similarly for fixuns_truncMN2. >How-To-Repeat: Read .md for target, specifically fix_truncMN2 and fixuns_truncMN2 patterns. Compare with docs and other targets, like sparc.md, m68k.md. Marvel at how it doesn't seem to affect anything. >Fix: See sparc.md, m68k.md, mmix.md. >Release-Note: >Audit-Trail: >Unformatted: