public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50686] [4.7 regression] IRIX 6.5 bootstrap failure: ICE in in lookup_cfa_1, at dwarf2cfi.c:595 Date: Thu, 11 Apr 2013 14:30:00 -0000 [thread overview] Message-ID: <bug-50686-4-dnbZBkWI20@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50686-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50686 --- Comment #40 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2013-04-11 14:30:49 UTC --- > --- Comment #39 from Bernd Schmidt <bernds at gcc dot gnu.org> 2013-04-11 > 11:35:33 UTC --- [...] > Ok, the --enable-checking made it reproducible. The lesson here is that a good > bug report includes information on how the build was configured. Couldn't agree more, given how long it took me to reproduce the issue myself :-) > Try this patch. I'm currently running a bootstrap of gcc 4.7.3 with this patch applied and without any special --enable-checking=release. It just entered stage2, so seems to be fine. I'll report once the bootstrap completed successfully. Thanks. Rainer
next prev parent reply other threads:[~2013-04-11 14:30 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-10 15:05 [Bug bootstrap/50686] New: " ro at gcc dot gnu.org 2011-10-10 15:15 ` [Bug bootstrap/50686] " rguenth at gcc dot gnu.org 2011-10-12 13:09 ` ro at gcc dot gnu.org 2011-10-12 13:10 ` ro at gcc dot gnu.org 2011-10-12 15:38 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-12 16:46 ` bernds at gcc dot gnu.org 2011-10-12 16:54 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-17 11:31 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-17 11:40 ` bernds at gcc dot gnu.org 2011-10-17 14:54 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-17 15:05 ` bernds at gcc dot gnu.org 2011-10-17 15:50 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-17 15:53 ` ro at gcc dot gnu.org 2011-10-17 15:54 ` ro at gcc dot gnu.org 2011-10-17 15:55 ` ro at gcc dot gnu.org 2011-10-17 16:35 ` bernds at gcc dot gnu.org 2011-10-17 17:13 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-17 17:38 ` bernds at gcc dot gnu.org 2011-10-18 15:39 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-24 11:43 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-24 12:11 ` bernds at gcc dot gnu.org 2011-11-21 13:30 ` ro at gcc dot gnu.org 2011-12-07 9:01 ` jakub at gcc dot gnu.org 2011-12-07 9:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-12-07 9:22 ` jakub at gcc dot gnu.org 2011-12-16 17:06 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-12-16 20:06 ` pinskia at gcc dot gnu.org 2011-12-19 16:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-12-21 16:29 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-04 13:30 ` rguenth at gcc dot gnu.org 2012-01-04 13:37 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-13 20:50 ` jakub at gcc dot gnu.org 2012-01-17 16:57 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-19 12:53 ` rguenth at gcc dot gnu.org 2012-01-19 13:01 ` ro at gcc dot gnu.org 2013-03-25 14:18 ` ro at gcc dot gnu.org 2013-03-26 10:18 ` ro at CeBiTec dot Uni-Bielefeld.DE 2013-04-03 12:19 ` ro at gcc dot gnu.org 2013-04-05 10:41 ` ro at CeBiTec dot Uni-Bielefeld.DE 2013-04-05 14:16 ` ro at CeBiTec dot Uni-Bielefeld.DE 2013-04-11 8:00 ` rguenth at gcc dot gnu.org 2013-04-11 11:35 ` bernds at gcc dot gnu.org 2013-04-11 14:30 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2014-06-12 13:03 ` rguenth 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-50686-4-dnbZBkWI20@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).