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: target/10084: [3.2/3.3 regression] alpha: ICE while building kseg/ddd
Date: Sun, 23 Mar 2003 21:06:00 -0000	[thread overview]
Message-ID: <20030323203600.25703.qmail@sources.redhat.com> (raw)

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

From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, rmurray@debian.org,
   184753@bugs.debian.org
Cc:  
Subject: Re: target/10084: [3.2/3.3 regression] alpha: ICE while building kseg/ddd
Date: 23 Mar 2003 21:29:34 +0100

 Hi,
 
 here's a smaller test case:
 
 struct Foo {
     Foo();
     Foo(const Foo &);
 };
 
 inline Foo foo(Foo s1) {
     Foo tmp(s1);
     return tmp;
 }
 
 const Foo bar = foo(Foo());
 
 % g++ -v
 Reading specs from /usr/local/stow/gcc-2003.03.11/bin/../lib/gcc-lib/alphaev68-unknown-linux-gnu/3.4/specs
 Configured with: ../configure --enable-languages=c++
 Thread model: posix
 gcc version 3.4 20030310 (experimental)
 % g++ -c -g -O bug.cc
 bug.cc: In function `void __static_initialization_and_destruction_0(int, int)':
 bug.cc:11: internal compiler error: in mem_loc_descriptor, at dwarf2out.c:8508
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 g++ 2.95 has no problems. Removing -g or -O also fixes the problem.
 
 -- 
 	Falk


             reply	other threads:[~2003-03-23 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-23 21:06 Falk Hueffner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-28  8:16 target/10084: [3.2/3.3 regression][alpha] " ebotcazou
2003-03-14 15:26 target/10084: [3.2/3.3 regression] alpha: " 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=20030323203600.25703.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).