public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kumba at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38052] [4.4 Regression] genautomata segfaults when -O2 is enabled
Date: Wed, 12 Nov 2008 01:02:00 -0000 [thread overview]
Message-ID: <20081112010136.8141.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38052-16496@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from kumba at gentoo dot org 2008-11-12 01:01 -------
I ran into this too. The problem flag is -foptimize-sibling-calls. You can
pass that with -O1 to trigger the bug, but not with -O0. Some other
optimization in -O1 seems to be mixing with this one and causing the flaw.
Ran into this on mips-unknown-linux-gnu, btw. Mips-specific maybe?
--
kumba at gentoo dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kumba at gentoo dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38052
next prev parent reply other threads:[~2008-11-12 1:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 15:33 [Bug c/38052] New: " r0bertz at gentoo dot org
2008-11-07 15:42 ` [Bug c/38052] " r0bertz at gentoo dot org
2008-11-10 22:46 ` [Bug target/38052] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-11-12 1:02 ` kumba at gentoo dot org [this message]
2008-11-13 9:54 ` r0bertz at gentoo dot org
2008-11-13 11:38 ` r0bertz at gentoo dot org
2008-11-13 17:28 ` r0bertz at gentoo dot org
2008-11-13 17:35 ` ebotcazou at gcc dot gnu dot org
2008-11-15 20:43 ` rsandifo at gcc dot gnu dot org
2008-11-16 20:28 ` rsandifo at gcc dot gnu dot org
2008-11-16 20:34 ` rsandifo at gcc dot gnu dot org
2008-11-16 21:10 ` rsandifo 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=20081112010136.8141.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: link
Be 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).