public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mmitchel@gcc.gnu.org,
	nobody@gcc.gnu.org, wlandry@ucsd.edu
Subject: Re: c++/9285: [3.4 regression] False shadowing of parameters in templates
Date: Mon, 13 Jan 2003 00:09:00 -0000	[thread overview]
Message-ID: <20030113000904.26191.qmail@sources.redhat.com> (raw)

Old Synopsis: REGRESSION: False shadowing of parameters in templates
New Synopsis: [3.4 regression] False shadowing of parameters in templates

Responsible-Changed-From-To: unassigned->mmitchel
Responsible-Changed-By: bangerth
Responsible-Changed-When: Sun Jan 12 16:09:04 2003
Responsible-Changed-Why:
    Author of the new parser.
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Sun Jan 12 16:09:04 2003
State-Changed-Why:
    This is a reduced testcase:
    ------------------------
    struct X{
        X(double *data, double d0, double d1);
    };
    
    int foo(double d0) {
      double * data;
      X(data,d0,d0);
    }
    ----------------------------
    It compiled with a snapshot from 2002-12-25, but fails now.
    Probably due to the new parser.
    
    Present compilers say
    regression/test> ../bin/gcc-2003-01-05/bin/c++ -c PR9285.cc
    PR9285.cc: In function `int foo(double)':
    PR9285.cc:7: error: declaration of `d0' shadows a parameter
    PR9285.cc:7: error: no matching function for call to `X::X()'
    PR9285.cc:1: error: candidates are: X::X(const X&)
    PR9285.cc:2: error:                 X::X(double*, double, double)
    PR9285.cc:7: error: expected init-declarator
    PR9285.cc:7: error: expected `,' or `;'
    
    W.

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


             reply	other threads:[~2003-01-13  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13  0:09 bangerth [this message]
2003-01-15 20:46 Andrew Pollard
2003-01-22 17:52 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=20030113000904.26191.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mmitchel@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=wlandry@ucsd.edu \
    /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).