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 middle-end/44790] [4.6 Regression] Bootstrap fails after MEM-REF merge
Date: Wed, 07 Jul 2010 08:35:00 -0000	[thread overview]
Message-ID: <20100707083543.25550.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44790-3107@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from rguenther at suse dot de  2010-07-07 08:35 -------
Subject: Re:  [4.6 Regression] Bootstrap fails after
 MEM-REF merge

On Tue, 6 Jul 2010, sje at cup dot hp dot com wrote:

> ------- Comment #4 from sje at cup dot hp dot com  2010-07-06 22:56 -------
> I successfully bootstrapped ToT (after setting flag_partial_inlining to 0 to
> work around pr44716) using the patch.  Testing also looked good, there are some
> new failures but they are all either new tests that may have never worked on
> this platform or tests that are also failing on other platforms.

Ok.  I'll bootstrap & test the patch on x86_64-linux and apply it.

Thanks,
Richard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44790


  parent reply	other threads:[~2010-07-07  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 18:53 [Bug middle-end/44790] New: " sje at cup dot hp dot com
2010-07-02 19:49 ` [Bug middle-end/44790] " sje at cup dot hp dot com
2010-07-03 11:17 ` rguenth at gcc dot gnu dot org
2010-07-06 14:26 ` [Bug middle-end/44790] [4.6 Regression] " rguenth at gcc dot gnu dot org
2010-07-06 16:44 ` sje at cup dot hp dot com
2010-07-06 22:56 ` sje at cup dot hp dot com
2010-07-07  8:35 ` rguenther at suse dot de [this message]
2010-07-07 12:44 ` rguenth at gcc dot gnu dot org
2010-07-07 13:04 ` rguenth at gcc dot gnu dot org
2010-07-28  7:45 ` ebotcazou 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=20100707083543.25550.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).