public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/47620] [4.6 Regression] Profiledbootstrap failure on powerpc-linux
Date: Sun, 13 Feb 2011 16:32:00 -0000 [thread overview]
Message-ID: <bug-47620-4-jpFy6fSyMV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47620-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47620
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-02-13 15:57:05 UTC ---
(In reply to comment #6)
> Here's a patch that fixes the problem. Jakub, is it easy for you to test it on
> the affected platforms? Please? :-) TIA,
Profiledootstrapped/regtested on x86_64-linux, i686-linux and powerpc64-linux
(64-bit), profiledbootstrapped so far on powerpc-linux (regtest still pending).
next prev parent reply other threads:[~2011-02-13 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 13:03 [Bug rtl-optimization/47620] New: " jakub at gcc dot gnu.org
2011-02-06 13:06 ` [Bug rtl-optimization/47620] " jakub at gcc dot gnu.org
2011-02-06 14:23 ` jakub at gcc dot gnu.org
2011-02-07 9:17 ` jakub at gcc dot gnu.org
2011-02-07 13:47 ` jakub at gcc dot gnu.org
2011-02-08 15:04 ` rguenth at gcc dot gnu.org
2011-02-12 12:59 ` [Bug debug/47620] " aoliva at gcc dot gnu.org
2011-02-12 13:09 ` aoliva at gcc dot gnu.org
2011-02-12 13:50 ` aoliva at gcc dot gnu.org
2011-02-13 16:32 ` jakub at gcc dot gnu.org [this message]
2011-02-14 13:08 ` dan at danny dot cz
2011-02-16 23:51 ` jakub at gcc dot gnu.org
2011-02-16 23:54 ` jakub at gcc dot gnu.org
2011-02-17 0:36 ` jakub at gcc dot gnu.org
2011-02-17 8:29 ` jakub at gcc dot gnu.org
2011-02-17 22:31 ` aoliva at gcc dot gnu.org
2011-02-18 11:01 ` jakub at gcc dot gnu.org
2011-02-19 8:57 ` jakub at gcc dot gnu.org
2011-02-19 21:00 ` aoliva at gcc dot gnu.org
2011-02-19 21:37 ` aoliva at gcc dot gnu.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=bug-47620-4-jpFy6fSyMV@http.gcc.gnu.org/bugzilla/ \
--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).