public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/43629] [4.3/4.4/4.5 Regression] Struct to register optimization fails
Date: Fri, 02 Apr 2010 15:05:00 -0000 [thread overview]
Message-ID: <20100402150454.14561.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43629-18994@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rguenther at suse dot de 2010-04-02 15:04 -------
Subject: Re: [4.3/4.4/4.5 Regression] Struct
to register optimization fails
On Fri, 2 Apr 2010, julien dot etienne at gmail dot com wrote:
> ------- Comment #4 from julien dot etienne at gmail dot com 2010-04-02 15:03 -------
> What about using -O1 -fno-tree-ccp as a workaround rather than -O1
> -fno-tree-rsa ?
> Isn't it more efficient and more related to the root cause ?
>
> Thanks for your help.
>
> FYI: I was unable to check out the trunk due to firewall restriction (even on
> http). I will try it from another connection.
Disabling constant propagation is going to affect code quality a lot
more (and might uncover latent bugs). Anyway, I have a patch for
trunk already.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43629
next prev parent reply other threads:[~2010-04-02 15:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 9:46 [Bug c/43629] New: " julien dot etienne at gmail dot com
2010-04-02 11:32 ` [Bug tree-optimization/43629] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2010-04-02 11:47 ` rguenth at gcc dot gnu dot org
2010-04-02 12:51 ` [Bug tree-optimization/43629] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org
2010-04-02 15:03 ` julien dot etienne at gmail dot com
2010-04-02 15:05 ` rguenther at suse dot de [this message]
2010-04-02 16:50 ` rguenth at gcc dot gnu dot org
2010-04-02 16:51 ` [Bug tree-optimization/43629] [4.3/4.4 " rguenth at gcc dot gnu dot org
2010-04-02 20:12 ` julien dot etienne at gmail dot com
2010-04-03 19:38 ` mikpe at it dot uu dot se
2010-04-03 19:53 ` rguenth at gcc dot gnu dot org
2010-04-07 15:41 ` rguenth at gcc dot gnu dot org
2010-04-07 15:44 ` [Bug tree-optimization/43629] [4.3 " rguenth at gcc dot gnu dot org
2010-04-12 8:51 ` julien dot etienne at gmail dot com
2010-04-12 9:01 ` rguenther at suse dot de
2010-04-20 13:08 ` rguenth at gcc dot gnu dot org
2010-04-20 13:09 ` rguenth at gcc dot gnu dot org
2010-04-23 21:12 ` julien dot etienne at gmail dot com
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=20100402150454.14561.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).