public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9524
Date: Fri, 21 Feb 2003 20:26:00 -0000	[thread overview]
Message-ID: <20030221202600.12808.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9524; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/9524
Date: Fri, 21 Feb 2003 14:18:09 -0600 (CST)

 ---------- Forwarded message ----------
 Date: Fri, 21 Feb 2003 20:57:46 +0100 (CET)
 From: Michael Matz <matz@suse.de>
 To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
 Cc: gcc-gnats@gcc.gnu.org
 Subject: Re: c++/9524
 
 Hi,
 
 On Fri, 21 Feb 2003, Wolfgang Bangerth wrote:
 
 > It seems as if this has been fixed on mainline,
 
 No:
 
 % cvs -z2 up -A
 [omitted]
 % cd ../devel; make -j 8
 [omitted]
 
 % cd ../ ; ./devel/gcc/cc1plus -version
 GNU C++ version 3.4 20030221 (experimental) (i686-pc-linux-gnu)
         compiled by GNU C version 2.95.3 20010315 (SuSE).
 options passed:
 options enabled:  -fpeephole -ffunction-cse -fkeep-static-consts
  -fpcc-struct-return -fgcse-lm -fgcse-sm -fsched-interblock -fsched-spec
  -fbranch-count-reg -fexceptions -fcommon -fgnu-linker -fargument-alias
  -fzero-initialized-in-bss -fident -fmath-errno -ftrapping-math -m80387
  -mhard-float -mno-soft-float -mieee-fp -mfp-ret-in-387
  -maccumulate-outgoing-args -mcpu=pentiumpro -march=i386
 
 % cat boost.ii
 struct A {
   void (*f)(void);
 };
 
 template< typename R >
 struct B : public A {
   void g()
   {
     A::f();
   }
 };
 template class B<bool>;
 
 % ./devel/gcc/cc1plus boost.ii
  void B<R>::g() void B<R>::g() [with R = bool] void B<R>::g() [with R = bool]
 boost.ii:12:   instantiated from here
 boost.ii:9: internal compiler error: in c_expand_expr, at c-common.c:4339
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 Regarding 3.3 branch:
 
 % cd ../3.3-clean/gcc; cvs -z2 up ; cd ../devel; make -j 8; cd ..
 
 % ./devel/gcc/cc1plus -version
 GNU C++ version 3.3 20030221 (prerelease) (i686-pc-linux-gnu)
         compiled by GNU C version 2.95.3 20010315 (SuSE).
 
 % ./devel/gcc/cc1plus boost.ii
  void B<R>::g() void B<R>::g() [with R = bool] void B<R>::g() [with R = bool]
 boost.ii:12:   instantiated from here
 boost.ii:9: internal compiler error: in c_expand_expr, at c-common.c:4319
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 > on a 3.3 snapshot of 2003-02-14. Can you double check whether it may
 > already have been fixed on 3.3 as well and if not possibly identify the
 > patch that fixed it on mainline, for backporting?
 
 There is no patch fixing it.
 
 
 Ciao,
 Michael.
 


             reply	other threads:[~2003-02-21 20:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21 20:26 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-08  9:16 c++/9524 mmitchel
2003-02-27 16:16 c++/9524 Wolfgang Bangerth
2003-02-21 20:06 c++/9524 Wolfgang Bangerth
2003-02-21 19:26 c++/9524 Wolfgang Bangerth

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=20030221202600.12808.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).