public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/46034] [4.6 regression] internal compiler error: Segmentation fault
Date: Wed, 27 Oct 2010 23:00:00 -0000 [thread overview]
Message-ID: <20101027230000.NpJPlhXoDUg38Cmq_aLk_WYHCG2Nk0y70dMa0caEws0@z> (raw)
In-Reply-To: <bug-46034-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46034
--- Comment #8 from Zdenek Sojka <zsojka at seznam dot cz> 2010-10-27 22:59:53 UTC ---
Created attachment 22186
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22186
reduced testcase
Needs only "-O -fexpensive-optimizations" to reproduce
Relevant valgrind output:
$ gcc -O -fexpensive-optimizations testcase2.c
==10818==
==10818== Stack overflow in thread 1: can't grow stack to 0x7fe801fd8
==10818== Can't extend stack to 0x7fe801450 during signal delivery for thread
1:
==10818== no stack segment
==10818==
==10818== Process terminating with default action of signal 11 (SIGSEGV)
==10818== Access not within mapped region at address 0x7FE801450
==10818== at 0xF1C9BB: if_then_else_cond (combine.c:8504)
==10818== If you believe this happened as a result of a stack
==10818== overflow in your program's main thread (unlikely but
==10818== possible), you can try to increase the size of the
==10818== main thread stack using the --main-stacksize= flag.
==10818== The main thread stack size used in this run was 8388608.
==10818== Stack overflow in thread 1: can't grow stack to 0x7fe801f50
gcc: internal compiler error: Segmentation fault (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Tested revisions:
r165985 - crash
r163636 - crash
r161659 - OK
next prev parent reply other threads:[~2010-10-27 23:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 11:49 [Bug middle-end/46034] New: " moonshine at kapsi dot fi
2010-10-15 12:10 ` [Bug middle-end/46034] " moonshine at kapsi dot fi
2010-10-15 15:27 ` [Bug middle-end/46034] [4.6 regression] " moonshine at kapsi dot fi
2010-10-27 22:14 ` [Bug rtl-optimization/46034] " pinskia at gcc dot gnu.org
2010-10-27 22:14 ` pinskia at gcc dot gnu.org
2010-10-27 22:17 ` pinskia at gcc dot gnu.org
2010-10-27 22:19 ` pinskia at gcc dot gnu.org
2010-10-27 22:34 ` pinskia at gcc dot gnu.org
2010-10-27 22:38 ` pinskia at gcc dot gnu.org
2010-10-27 23:00 ` zsojka at seznam dot cz [this message]
2010-10-28 10:34 ` ebotcazou at gcc dot gnu.org
2010-10-28 16:05 ` hjl.tools at gmail dot com
2010-11-01 11:25 ` [Bug rtl-optimization/46034] [4.6 regression] internal compiler error: segmentation fault jakub at gcc dot gnu.org
2010-11-01 21:22 ` ebotcazou at gcc dot gnu.org
2010-11-03 0:28 ` moonshine at kapsi dot fi
2010-11-03 8:31 ` 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=20101027230000.NpJPlhXoDUg38Cmq_aLk_WYHCG2Nk0y70dMa0caEws0@z \
--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).