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 bootstrap/48158] New: [4.7 Regression] profiledbootstrap failure on x86_64-linux Date: Wed, 16 Mar 2011 20:54:00 -0000 [thread overview] Message-ID: <bug-48158-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48158 Summary: [4.7 Regression] profiledbootstrap failure on x86_64-linux Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: jakub@gcc.gnu.org CC: davidxl@gcc.gnu.org Created attachment 23686 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23686 go.ii profiledbootstrap on x86_64-linux fails while building go. Attached is a distilled testcase: ./cc1plus -quiet -O2 -Wall -fprofile-use go.ii -w go.ii: In function ‘std::basic_string<_CharT, <template-parameter-1-2>, <template-parameter-1-3> >::~basic_string() [with _CharT = std::allocator<char>, <template-parameter-1-2> = std::char_traits<std::allocator<char> >, _Alloc = std::allocator<std::allocator<char> >]’: go.ii:116:1: note: file /usr/src/gcc/obj534a/gcc/go.gcda not found, execution counts estimated go.ii: In member function ‘Type* Parse::type()’: go.ii:107:8: internal compiler error: vector VEC(use_pred_info_t,base) index domain error, in pred_chain_length_cmp at tree-ssa-uninit.c:1626 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. go.gcda isn't needed...
next reply other threads:[~2011-03-16 20:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-16 20:54 jakub at gcc dot gnu.org [this message] 2011-03-16 21:01 ` [Bug bootstrap/48158] " jakub at gcc dot gnu.org 2011-03-17 14:18 ` jakub at gcc dot gnu.org 2011-04-06 17:22 ` jakub at gcc dot gnu.org 2011-04-13 7:22 ` jakub 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-48158-4@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: 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).