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 middle-end/61949] [4.10 regression] SEGV compiling gcc.dg/pch/import-[12].c Date: Wed, 30 Jul 2014 12:14:00 -0000 [thread overview] Message-ID: <bug-61949-4-MzvVGCzr8s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61949-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61949 --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- > it's odd that stage2 is not affected... can you provide preprocessed source I lied: if you generate the .gch file with the stage2 cc1, both stage2 and 3 cc1 SEGV the same way. > of libiberty/md5.c as compiled for the host? Attached. Rainer
next prev parent reply other threads:[~2014-07-30 12:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-29 15:10 [Bug middle-end/61949] New: " ro at gcc dot gnu.org 2014-07-29 15:10 ` [Bug middle-end/61949] " ro at gcc dot gnu.org 2014-07-30 10:01 ` rguenth at gcc dot gnu.org 2014-07-30 12:14 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2014-07-30 12:14 ` ro at gcc dot gnu.org 2014-07-30 14:07 ` [Bug target/61949] " rguenth at gcc dot gnu.org 2014-07-30 14:54 ` hjl.tools at gmail dot com 2015-02-17 18:58 ` [Bug target/61949] [5 " jakub at gcc dot gnu.org 2015-02-19 14:33 ` 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-61949-4-MzvVGCzr8s@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).