public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Zack Weinberg" <zack@codesourcery.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: "Joseph S. Myers" <jsm@polyomino.org.uk>,  gcc-bugs@gcc.gnu.org
Subject: Re: [Bug c++/13717] New: duplicated parameter name not caught ?
Date: Sun, 18 Jan 2004 02:12:00 -0000	[thread overview]
Message-ID: <87brp2uhrm.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <E9D776A7-4932-11D8-833F-000393A6D2F2@physics.uc.edu> (Andrew Pinski's message of "Sat, 17 Jan 2004 13:20:02 -0800")

Andrew Pinski <pinskia@physics.uc.edu> writes:

> On Jan 17, 2004, at 04:17, Joseph S. Myers wrote:
>> now give a diagnostic for C.  I guess Zack's patches are the most
>> likely
>> cause, or at least the subsequent ones the most likely fix.
>
> It was the most recent patch which broke this as it failed still on
> 2004-01-01.
>
>
>> (Sent to gcc-bugs rather than gcc-bugzilla because this is a
>> separate bug.
>> Shall I open a new PR for this regression or will this be fixed shortly
>> (with the above testcases included) in a subsequent stage of the
>> c-decl.c
>> cleanup patches?)
>
> I would open just to make sure that it gets fixed.

Please do.

zw


  reply	other threads:[~2004-01-18  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 11:28 d dot binderman at virgin dot net
2004-01-17 12:17 ` Joseph S. Myers
2004-01-17 21:20   ` Andrew Pinski
2004-01-18  2:12     ` Zack Weinberg [this message]
2004-01-17 23:35 ` Gabriel Dos Reis
2004-01-18  9:20 ` [Bug c++/13717] " dhazeghi at yahoo dot com
2004-10-03 19:52 ` pinskia at gcc dot gnu dot org
2004-10-04 12:45 ` bangerth at dealii dot org

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=87brp2uhrm.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=jsm@polyomino.org.uk \
    --cc=pinskia@physics.uc.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).