public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/55660] [4.7 Regression] ICE instead of some warning during lto build with supplied different options (-funsigned-char vs none) Date: Thu, 13 Dec 2012 11:14:00 -0000 [thread overview] Message-ID: <bug-55660-4-rocdJBfFEf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55660-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55660 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.8.0 Summary|[4.7/4.8 Regression] ICE |[4.7 Regression] ICE |instead of some warning |instead of some warning |during lto build with |during lto build with |supplied different options |supplied different options |(-funsigned-char vs none) |(-funsigned-char vs none) Known to fail|4.8.0 | --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-13 11:13:53 UTC --- Fixed on trunk sofar.
next prev parent reply other threads:[~2012-12-13 11:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-12 6:40 [Bug lto/55660] New: ICE instead of some warning during lto build vbyakovl23 at gmail dot com 2012-12-12 9:55 ` [Bug lto/55660] [4.7/4.8 Regression] ICE instead of some warning during lto build with supplied different options (-funsigned-char vs none) rguenth at gcc dot gnu.org 2012-12-12 14:19 ` rguenth at gcc dot gnu.org 2012-12-13 11:13 ` rguenth at gcc dot gnu.org 2012-12-13 11:14 ` rguenth at gcc dot gnu.org [this message] 2013-02-04 12:05 ` [Bug lto/55660] [4.7 " rguenth at gcc dot gnu.org 2013-02-04 12:07 ` 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-55660-4-rocdJBfFEf@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).