public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/23461] New: ICE in tree_low_cst, allocating oversized array from stack
@ 2005-08-18 15:42 pete at void dot printf dot net
2005-08-18 15:59 ` [Bug c++/23461] " pete at void dot printf dot net
2005-08-18 16:03 ` pinskia at gcc dot gnu dot org
0 siblings, 2 replies; 3+ messages in thread
From: pete at void dot printf dot net @ 2005-08-18 15:42 UTC (permalink / raw)
To: gcc-bugs
The following is a minimal test case. Obviously, this is trying to do a dumb
thing, but it shouldn't give ICE, and g++ asked me to report it. The error is
"internal compiler error: in tree_low_cst, at tree.c:3843".
int main()
{
int ptr[1000000000];
return 0;
};
The output of g++ -v follows.
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib --enable-nls
--without-included-gettext --enable-threads=posix --program-suffix=-4.0
--enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu
--enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre --enable-mpfr
--disable-werror --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.0.1 (Debian 4.0.1-2)
Just in case it's relevant, the output of uname -a is "Linux [hostname] 2.4.18
#3 SMP Wed Oct 15 17:04:52 BST 2003 i686 GNU/Linux".
--
Summary: ICE in tree_low_cst, allocating oversized array from
stack
Product: gcc
Version: 4.0.1
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pete at void dot printf dot net
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23461
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/23461] ICE in tree_low_cst, allocating oversized array from stack
2005-08-18 15:42 [Bug c++/23461] New: ICE in tree_low_cst, allocating oversized array from stack pete at void dot printf dot net
@ 2005-08-18 15:59 ` pete at void dot printf dot net
2005-08-18 16:03 ` pinskia at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: pete at void dot printf dot net @ 2005-08-18 15:59 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pete at void dot printf dot net 2005-08-18 15:42 -------
It's possible that this might be related to bug 22551, but I'm not sure.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23461
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/23461] ICE in tree_low_cst, allocating oversized array from stack
2005-08-18 15:42 [Bug c++/23461] New: ICE in tree_low_cst, allocating oversized array from stack pete at void dot printf dot net
2005-08-18 15:59 ` [Bug c++/23461] " pete at void dot printf dot net
@ 2005-08-18 16:03 ` pinskia at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-08-18 16:03 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-18 15:59 -------
This is a dup of bug 23426. The C example of this was fixed already. See PR 23426 for the current
status of this bug.
*** This bug has been marked as a duplicate of 23426 ***
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23461
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-08-18 15:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-08-18 15:42 [Bug c++/23461] New: ICE in tree_low_cst, allocating oversized array from stack pete at void dot printf dot net
2005-08-18 15:59 ` [Bug c++/23461] " pete at void dot printf dot net
2005-08-18 16:03 ` pinskia at gcc dot gnu dot org
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).