public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9651: [Alpha] FPE with NAN in spite of isnan protection Date: Tue, 11 Feb 2003 02:56:00 -0000 [thread overview] Message-ID: <20030211025600.17435.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9651; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: gcc-gnats@gcc.gnu.org,gcc-patches@gcc.gnu.org Cc: Will Woods <will.woods@hp.com> Subject: Re: optimization/9651: [Alpha] FPE with NAN in spite of isnan protection Date: 11 Feb 2003 03:53:46 +0100 --=-=-= Hi, This patch marks fix expressions as trappable, preventing them from being scheduled out of their block. 2003-02-11 Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> PR optimization/9651 * rtlanal.c (may_trap_p): Handle FIX. -- Falk --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=fix-trap.patch Index: gcc/rtlanal.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/rtlanal.c,v retrieving revision 1.145 diff -u -r1.145 rtlanal.c --- gcc/rtlanal.c 17 Jan 2003 03:28:09 -0000 1.145 +++ gcc/rtlanal.c 11 Feb 2003 02:50:01 -0000 @@ -2517,6 +2517,12 @@ return 1; break; + case FIX: + /* Conversion of floating point might trap. */ + if (flag_trapping_math && HONOR_NANS (GET_MODE (XEXP (x, 0)))) + return 1; + break; + case NEG: case ABS: /* These operations don't trap even with floating point. */ --=-=-=--
next reply other threads:[~2003-02-11 2:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-11 2:56 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-11 20:59 rth 2003-02-11 20:56 Richard Henderson 2003-02-11 0:36 Falk Hueffner
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=20030211025600.17435.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --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: linkBe 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).