public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tg at mirbsd dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/40506] ICE with -fwhole-program --combine (verify_stmts failed) Date: Tue, 30 Jun 2009 08:44:00 -0000 [thread overview] Message-ID: <20090630084432.28718.qmail@sourceware.org> (raw) In-Reply-To: <bug-40506-5724@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from tg at mirbsd dot org 2009-06-30 08:44 ------- @Richard Guenther: the problem is that "-fwhole-program --combine" works most of the time, but if it fails, there is no simple way to detect it from a build script (by compiling a small test programme with these options I can only detect if they are recognised at all or (e.g. gcc3) not, but a hello-world style will always succeed). So I suggest that, if it is known to the gcc maintainers that the- se options are broken in a specific gcc version, it be deactivated so that compiling the test programme will fail due to an "unrecog- nised" command line option. On the other hand, in later gcc4.1 versions as well as some gcc4.4 versions (eg. that on sid), gcc-snapshot on karmic, gcc4.2, gcc4.3 and llvm-gcc4.2 it works very well, so I'd like to use this featu- re if I can. -- tg at mirbsd dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tg at mirbsd dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40506
next prev parent reply other threads:[~2009-06-30 8:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-20 18:20 [Bug middle-end/40506] New: " debian-gcc at lists dot debian dot org 2009-06-20 18:22 ` [Bug middle-end/40506] " debian-gcc at lists dot debian dot org 2009-06-20 19:13 ` rguenth at gcc dot gnu dot org 2009-06-21 23:51 ` pinskia at gcc dot gnu dot org 2009-06-30 8:44 ` tg at mirbsd dot org [this message] 2009-10-14 21:30 ` rguenth at gcc dot gnu dot org 2010-09-17 9:09 ` rguenth at gcc dot gnu dot 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=20090630084432.28718.qmail@sourceware.org \ --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).