public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10695: 2.95/3.2/3.3: ICE on alpha while building agistudio
Date: Fri, 09 May 2003 15:56:00 -0000	[thread overview]
Message-ID: <20030509155600.15050.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/10695; it has been noted by GNATS.

From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: rmurray@debian.org
Cc: gcc-gnats@gcc.gnu.org, 192568@bugs.debian.org
Subject: Re: c++/10695: 2.95/3.2/3.3: ICE on alpha while building agistudio
Date: 09 May 2003 17:54:03 +0200

 rmurray@debian.org writes:
 
 > g++ -c -pipe -Wall -W -g -D_REENTRANT -DQT_THREAD_SUPPORT -I/usr/include/qt3 -I/usr/include/qt -o wordsedit.o wordsedit.cpp
 > wordsedit.cpp: In member function `void WordsEdit::merge_file()':
 > wordsedit.cpp:620: Internal compiler error in dwarf2out_frame_debug_expr, at dwarf2out.c:1328
 > Please submit a full bug report,
 
 This is acually a bug in the Debian package, because the file isn't
 compiled with -O2 as policy mandates, and the error only occurs at -O0
 ;)
 
 Here's a test case:
 
 struct WordList {
     char c[320000];
 };
 
 void merge(struct WordList);
 
 void merge_file()
 {
     struct WordList w;
     merge(w);
 }
 
 The problem is still there in g++ 3.4 20030423. It also occurs with
 gcc -g.
 
 The author should probably also consider not passing 320k large
 structures by value...
 
 -- 
 	Falk


             reply	other threads:[~2003-05-09 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 15:56 Falk Hueffner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09  6:06 rmurray

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=20030509155600.15050.qmail@sources.redhat.com \
    --to=falk.hueffner@student.uni-tuebingen.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).