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/41783] r151561 (PRE fix) regresses zeusmp Date: Wed, 21 Oct 2009 20:14:00 -0000 [thread overview] Message-ID: <20091021201426.12428.qmail@sourceware.org> (raw) In-Reply-To: <bug-41783-12182@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from rguenth at gcc dot gnu dot org 2009-10-21 20:14 ------- Created an attachment (id=18861) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18861&action=view) 1st part of a patch Like this. We should never produce new non-constant value-numbers during phi-translation as that may spuriously increase the maximal set and thus cause insertion of non-redundant values. We do so for NARYs anyway - I'm not sure if that is good though. Maybe the idea is that repeated translation can eventually lead to a known value. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41783
next prev parent reply other threads:[~2009-10-21 20:14 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-21 14:34 [Bug tree-optimization/41783] New: " matz at gcc dot gnu dot org 2009-10-21 14:53 ` [Bug tree-optimization/41783] " rguenth at gcc dot gnu dot org 2009-10-21 15:07 ` rguenth at gcc dot gnu dot org 2009-10-21 15:14 ` rguenth at gcc dot gnu dot org 2009-10-21 15:16 ` rguenth at gcc dot gnu dot org 2009-10-21 15:20 ` matz at gcc dot gnu dot org 2009-10-21 15:22 ` matz at gcc dot gnu dot org 2009-10-21 15:26 ` rguenth at gcc dot gnu dot org 2009-10-21 15:35 ` matz at gcc dot gnu dot org 2009-10-21 18:09 ` rguenth at gcc dot gnu dot org 2009-10-21 20:14 ` rguenth at gcc dot gnu dot org [this message] 2009-10-22 15:13 ` matz at gcc dot gnu dot org 2009-10-26 13:01 ` matz at gcc dot gnu dot org 2009-10-26 13:04 ` matz at gcc dot gnu dot org 2009-10-30 16:14 ` rguenth at gcc dot gnu dot org 2009-10-30 16:40 ` rguenth at gcc dot gnu dot org 2010-01-19 16:06 ` matz 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=20091021201426.12428.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).