public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matt at use dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/48600] New: [4.6 regression] ICE when using cold attribute
Date: Thu, 14 Apr 2011 02:36:00 -0000 [thread overview]
Message-ID: <bug-48600-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48600
Summary: [4.6 regression] ICE when using cold attribute
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: matt@use.net
Compiling the attached file at -O1 or above yields a stack overflow:
g++ -O1 ci.cpp
g++: internal compiler error: Segmentation fault (program cc1plus)
valgrind says:
==7379== Stack overflow in thread 1: can't grow stack to 0x7fe801ff8
==7379== Can't extend stack to 0x7fe801410 during signal delivery for thread 1:
==7379== no stack segment
==7379==
==7379== Process terminating with default action of signal 11 (SIGSEGV)
==7379== Access not within mapped region at address 0x7FE801410
==7379== at 0x89E8D5: ??? (in
/usr/lib/gcc-snapshot/libexec/gcc/x86_64-linux-gnu/4.6.0/cc1plus)
==7379== If you believe this happened as a result of a stack
==7379== overflow in your program's main thread (unlikely but
==7379== possible), you can try to increase the size of the
==7379== main thread stack using the --main-stacksize= flag.
==7379== The main thread stack size used in this run was 8388608.
==7379== Stack overflow in thread 1: can't grow stack to 0x7fe801f70
If you remove the cold attribute from Arch::Debugger_entry(), the ICE (and
explosive memory consumption) goes away.
Tested with 4.6.0 RC, final, and another 4.6 variant. They all have the same
problem. Testing with 4.5.2 and 4.4.4 shows no such problem.
next reply other threads:[~2011-04-14 2:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 2:36 matt at use dot net [this message]
2011-04-14 9:23 ` [Bug middle-end/48600] " rguenth at gcc dot gnu.org
2011-04-14 17:00 ` matt at use dot net
2011-04-15 18:30 ` matt at use dot net
2011-04-18 11:23 ` jakub at gcc dot gnu.org
2011-04-26 21:10 ` [Bug middle-end/48600] [4.6/4.7 Regression] " jsm28 at gcc dot gnu.org
2011-06-01 14:36 ` matt at use dot net
2011-06-27 16:19 ` jakub at gcc dot gnu.org
2011-08-18 6:08 ` jakub at gcc dot gnu.org
2011-08-18 9:12 ` rguenth at gcc dot gnu.org
2011-08-19 22:18 ` hubicka at gcc dot gnu.org
2011-10-26 17:25 ` jakub at gcc dot gnu.org
2011-12-09 9:14 ` rguenth at gcc dot gnu.org
2011-12-09 9:18 ` rguenth at gcc dot gnu.org
2012-01-24 10:20 ` jakub at gcc dot gnu.org
2012-01-31 14:55 ` hubicka at gcc dot gnu.org
2012-01-31 15:07 ` hubicka at gcc dot gnu.org
2012-02-10 12:22 ` hubicka at gcc dot gnu.org
2012-02-10 12:23 ` [Bug middle-end/48600] [4.7 " hubicka at gcc dot gnu.org
2012-03-01 14:55 ` [Bug middle-end/48600] [4.6 " jakub at gcc dot gnu.org
2012-03-23 10:52 ` hubicka at gcc dot gnu.org
2012-03-23 14:36 ` hubicka at gcc dot gnu.org
2012-03-23 14:53 ` hubicka at gcc dot gnu.org
2012-06-11 9:11 ` jye2 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-48600-4@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: 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).