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 tree-optimization/34099] [4.3 Regression] optimizer problem Date: Thu, 15 Nov 2007 15:40:00 -0000 [thread overview] Message-ID: <20071115154014.10455.qmail@sourceware.org> (raw) In-Reply-To: <bug-34099-3137@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2007-11-15 15:40 ------- That is, a certain class of operations (like COMPLEX_EXPR) do not fulfil the constraint that if one operand is UNDEFINED the result is UNDEFINED as well. For example MIN_EXPR <INT_MIN, UNDEFINED>, or MAX_EXPR <INT_MAX, UNDEFINED> are of such kind as well. No idea if we want a white-list here instead. BIT_AND_EXPR <UNDEFINED, 0> is also not UNDEFINED. (all of the above not with actual constants as defined arg, but VARYING ones) I have a patch. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |rguenth at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2007-11-15 10:21:31 |2007-11-15 15:40:13 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34099
next prev parent reply other threads:[~2007-11-15 15:40 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-15 6:56 [Bug c++/34099] New: " rwgk at yahoo dot com 2007-11-15 6:57 ` [Bug c++/34099] " rwgk at yahoo dot com 2007-11-15 10:21 ` [Bug tree-optimization/34099] [4.3 Regression] " rguenth at gcc dot gnu dot org 2007-11-15 14:56 ` rguenth at gcc dot gnu dot org 2007-11-15 15:08 ` rguenth at gcc dot gnu dot org 2007-11-15 15:40 ` rguenth at gcc dot gnu dot org [this message] 2007-11-15 15:44 ` ebotcazou at gcc dot gnu dot org 2007-11-15 15:51 ` rguenther at suse dot de 2007-11-15 16:04 ` rguenth at gcc dot gnu dot org 2007-11-15 16:06 ` rguenth at gcc dot gnu dot org 2007-11-15 16:08 ` rguenth at gcc dot gnu dot org 2007-11-15 16:38 ` rguenth at gcc dot gnu dot org 2007-11-15 17:10 ` rguenth at gcc dot gnu dot org 2007-11-15 17:17 ` rguenth at gcc dot gnu dot org 2007-11-16 10:10 ` rguenth at gcc dot gnu dot org 2007-11-16 10:36 ` rguenth at gcc dot gnu dot org 2007-11-19 12:52 ` rguenth at gcc dot gnu dot org 2007-11-19 12:53 ` rguenth 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=20071115154014.10455.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).