public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: jason@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9965
Date: Thu, 06 Mar 2003 19:36:00 -0000	[thread overview]
Message-ID: <20030306193601.29422.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: jason@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, <bero@arklinux.org>
Subject: Re: c++/9965
Date: Thu, 6 Mar 2003 13:31:04 -0600 (CST)

 Jason,
 take the reduced testcase. The reason why you can't compile the 
 preprocessed sources is that they were generated with 3.3's libstdc++, 
 which is missing all those this-> qualifications that 3.4 now wants to 
 see. I reduced the testcase with 3.3, and checked with the reduced one 
 that it fails on both 3.3 and 3.4.
 
 This is going to happen with a lot of preprocessed sources in the future, 
 if they were created with an older libstdc++...
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-03-06 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 19:36 Wolfgang Bangerth [this message]
2003-03-06 22:56 c++/9965 mmitchel
2003-03-06 22:56 c++/9965 mmitchel
2003-03-06 22:56 c++/9965 mmitchel
2003-03-06 22:56 c++/9965 mmitchel
2003-03-06 22:56 c++/9965 mmitchel
2003-03-06 22:56 c++/9965 mmitchel

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=20030306193601.29422.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jason@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).