public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: ecohen@angeles.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/3864: #line directive/template interaction produces wrong file name on errors
Date: Thu, 21 Nov 2002 18:17:00 -0000	[thread overview]
Message-ID: <20021116005717.5393.qmail@sources.redhat.com> (raw)

Synopsis: #line directive/template interaction produces wrong file name on errors

State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Fri Nov 15 16:57:17 2002
State-Changed-Why:
    This has been fixed in the meantime:
    tmp/g> /home/bangerth/bin/gcc-3.0.4/bin/c++ -c x.cc
    x.cc: In function `void doit(T) [with T = double]':
    somefile.x:25:   instantiated from here
    x.cc:20: `args' undeclared (first use this function)
    x.cc:20: (Each undeclared identifier is reported only once for each function it
       appears in.)
    tmp/g>
    tmp/g>
    tmp/g> /home/bangerth/bin/gcc-3.2.1-pre/bin/c++ -c x.cc
    somefile.x: In function `void doit(T) [with T = double]':
    somefile.x:25:   instantiated from here
    somefile.x:20: `args' undeclared (first use this function)
    somefile.x:20: (Each undeclared identifier is reported only once for each
       function it appears in.)
    tmp/g>
    tmp/g>
    tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/c++ -c x.cc
    somefile.x: In function `void doit(T) [with T = double]':
    somefile.x:25:   instantiated from here
    somefile.x:20: error: `args' undeclared (first use this function)
    somefile.x:20: error: (Each undeclared identifier is reported only once for
       each function it appears in.)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3864


             reply	other threads:[~2002-11-16  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 18:17 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-29  3:53 neil

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=20021116005717.5393.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=ecohen@angeles.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).