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/45232] [4.6 regression] tree reassociation introduces undefined overflow
Date: Tue, 10 Aug 2010 09:24:00 -0000 [thread overview]
Message-ID: <20100810092409.27639.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45232-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from rguenth at gcc dot gnu dot org 2010-08-10 09:24 -------
The patch doens't work - we have to disable a lot more reassociation which
isn't really allowed for types with undefined overflow. There are a bunch
of invalid testcases in the testsuite as well.
We might be able to recover some of the regressions by teaching our tree
combiner of some tricks. It looks like that will delay a fix for this
PR somewhat, but I'm working on it ...
--
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|2010-08-08 22:42:06 |2010-08-10 09:24:08
date| |
Target Milestone|--- |4.6.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45232
next prev parent reply other threads:[~2010-08-10 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 12:31 [Bug tree-optimization/45232] New: Several passes introduce " rguenth at gcc dot gnu dot org
2010-08-08 12:35 ` [Bug tree-optimization/45232] " rguenth at gcc dot gnu dot org
2010-08-08 12:55 ` [Bug tree-optimization/45232] Tree reassociation introduces " rguenth at gcc dot gnu dot org
2010-08-08 22:42 ` ebotcazou at gcc dot gnu dot org
2010-08-10 9:24 ` rguenth at gcc dot gnu dot org [this message]
2010-08-12 10:38 ` [Bug tree-optimization/45232] [4.6 regression] tree " rguenth at gcc dot gnu dot org
2010-08-12 10:38 ` 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=20100810092409.27639.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: link
Be 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).