public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/35509] [4.3/4.4 Regression] builtin isinf() mismatch to compile-time substitution Date: Mon, 14 Apr 2008 11:07:00 -0000 [thread overview] Message-ID: <20080414110630.20625.qmail@sourceware.org> (raw) In-Reply-To: <bug-35509-6291@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from rguenth at gcc dot gnu dot org 2008-04-14 11:06 ------- I propose that we do the following: - add a warning to the C/C++ frontends that isinf (x) CMP isinf (y) is only well-defined for !isinf (x) && !isinf (y). this doesn't result in a runtime penalty and informs people about the possible problem in their code (it is non-portable). A different workaround would be to canonicalize the return value of isinf to bool. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35509
next prev parent reply other threads:[~2008-04-14 11:07 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-08 10:03 [Bug target/35509] New: [avr] 4.3.0: " dmixm at marine dot febras dot ru 2008-03-08 10:41 ` [Bug middle-end/35509] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org 2008-03-08 10:53 ` rguenth at gcc dot gnu dot org 2008-03-08 15:45 ` ghazi at gcc dot gnu dot org 2008-03-08 15:51 ` ubizjak at gmail dot com 2008-03-08 15:56 ` pinskia at gcc dot gnu dot org 2008-04-13 16:28 ` ghazi at gcc dot gnu dot org 2008-04-14 10:56 ` dmixm at marine dot febras dot ru 2008-04-14 11:07 ` rguenth at gcc dot gnu dot org [this message] 2008-04-15 0:38 ` ghazi at gcc dot gnu dot org 2008-04-15 1:37 ` ghazi at gcc dot gnu dot org 2008-04-15 8:59 ` rguenther at suse dot de 2008-04-28 4:38 ` mmitchel at gcc dot gnu dot org 2008-05-18 15:51 ` ghazi at gcc dot gnu dot org 2008-05-18 23:21 ` ghazi at gcc dot gnu dot org 2008-05-19 6:17 ` ghazi at gcc dot gnu dot org 2008-05-19 6:17 ` ghazi at gcc dot gnu dot org 2008-05-19 6:20 ` ghazi at gcc dot gnu dot org
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=20080414110630.20625.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).