public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zlynx at acm dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/22071] New: 4.1 regression: ICE in first_vi_for_offset, at tree-ssa-structalias.c:2506
Date: Wed, 15 Jun 2005 02:03:00 -0000 [thread overview]
Message-ID: <20050615020311.22071.zlynx@acm.org> (raw)
# g++ -O /tmp/j1.cc
adaptors/lambda/lambda.cc: In function 'void
__static_initialization_and_destruction_0(int, int)':
adaptors/lambda/lambda.cc:15: internal compiler error: in first_vi_for_offset,
at tree-ssa-structalias.c:2506
j1.cc will be attached.
-O is what triggers the ICE. Compiling without optimization works.
# g++ -v
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/portage/gcc-4.1.0_beta20050611/work/gcc-4.1-20050611/configure
--enable-version-specific-runtime-libs --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.0-beta20050611
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.0-beta20050611/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.0-beta20050611
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.0-beta20050611/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.0-beta20050611/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.0-beta20050611/include/g++-v4
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec
--enable-nls --without-included-gettext --with-system-zlib --disable-checking
--disable-werror --disable-libunwind-exceptions --enable-multilib
--disable-libgcj --enable-languages=c,c++,f95 --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.1.0 20050611 (experimental)
--
Summary: 4.1 regression: ICE in first_vi_for_offset, at tree-ssa-
structalias.c:2506
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: zlynx at acm dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22071
next reply other threads:[~2005-06-15 2:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 2:03 zlynx at acm dot org [this message]
2005-06-15 2:03 ` [Bug c++/22071] " zlynx at acm dot org
2005-06-15 2:05 ` zlynx at acm dot org
2005-06-15 2:29 ` [Bug tree-optimization/22071] [4.1 regression] " pinskia at gcc dot gnu dot org
2005-06-22 17:59 ` bkoz at gcc dot gnu dot org
2005-06-22 18:54 ` dberlin at dberlin dot org
2005-06-22 18:59 ` bkoz at gcc dot gnu dot org
2005-06-22 19:01 ` Andrew Pinski
2005-06-22 19:02 ` pinskia at physics dot uc dot edu
2005-06-22 19:23 ` dberlin at dberlin dot org
2005-06-22 20:14 ` bkoz at gcc dot gnu dot org
2005-06-22 20:33 ` pinskia at gcc dot gnu dot org
2005-06-22 20:52 ` dberlin at dberlin dot org
2005-06-27 16:25 ` dberlin at gcc dot gnu dot org
2005-07-01 3:37 ` dberlin at gcc dot gnu dot org
2005-07-01 19:16 ` pinskia at gcc dot gnu dot org
2005-07-01 19:45 ` cvs-commit at gcc dot gnu dot org
2005-07-01 20:15 ` pinskia 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=20050615020311.22071.zlynx@acm.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).