public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19108] [4.0 regression] ICE initializing arrays
Date: Sat, 01 Jan 2005 16:28:00 -0000	[thread overview]
Message-ID: <20050101162822.27272.qmail@sourceware.org> (raw)
In-Reply-To: <20041221143657.19108.reichelt@gcc.gnu.org>


------- Additional Comments From steven at gcc dot gnu dot org  2005-01-01 16:28 -------
Yup, -march=i686 does the trick for me: 
 
$ ./cc1plus t.C -O -m32 -march=i686 
 A::A() 
 A::A() 
 A::A() 
 B::B(const A&) 
 B::B(const A&) 
 B::B(const A&) 
 void __static_initialization_and_destruction_0(int, int) 
 void _GLOBAL__I_b() 
 
Analyzing compilation unit 
Performing intraprocedural optimizations 
Assembling functions: 
 void __static_initialization_and_destruction_0(int, int) 
 
t.C: In function 'void __static_initialization_and_destruction_0(int, int)': 
t.C:13: internal compiler error: in sra_hash_tree, at tree-sra.c:384 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://gcc.gnu.org/bugs.html> for instructions. 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19108


  parent reply	other threads:[~2005-01-01 16:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 14:37 [Bug c++/19108] New: " reichelt at gcc dot gnu dot org
2004-12-21 15:30 ` [Bug tree-optimization/19108] " pinskia at gcc dot gnu dot org
2004-12-21 16:10 ` pinskia at gcc dot gnu dot org
2004-12-22 12:44 ` steven at gcc dot gnu dot org
2004-12-31 12:13 ` steven at gcc dot gnu dot org
2004-12-31 16:08 ` reichelt at gcc dot gnu dot org
2004-12-31 16:10 ` pinskia at gcc dot gnu dot org
2005-01-01 16:28 ` steven at gcc dot gnu dot org [this message]
2005-03-16 20:52 ` [Bug tree-optimization/19108] [4.0/4.1 " reichelt at gcc dot gnu dot org
2005-03-18 15:49 ` sayler at thewalrus dot org
2005-03-18 23:00 ` sayler at thewalrus dot org
2005-03-24 17:58 ` mmitchel at gcc dot gnu dot org
2005-03-28 19:13 ` rth at gcc dot gnu dot org
2005-03-28 21:05 ` steven at gcc dot gnu dot org
2005-03-29 22:44 ` cvs-commit at gcc dot gnu dot org
2005-03-29 22:56 ` cvs-commit at gcc dot gnu dot org
2005-03-29 22:58 ` rth 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=20050101162822.27272.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).