public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: gcc-bugs@gcc.gnu.org
Cc: Zack Weinberg <zack@codesourcery.com>
Subject: Re: [Bug c++/13717] New: duplicated parameter name not caught ?
Date: Sat, 17 Jan 2004 12:17:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0401171213130.9475@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20040117112758.13717.d.binderman@virgin.net>

On Sat, 17 Jan 2004, d dot binderman at virgin dot net wrote:

> The one liner
> 
> void f( int fred, char * fred);
> 
> is IMHO illegal code because fred is the name of two parameters.
> 
> I couldn't get gcc332 to find the bug in this code.
> This is salted down from real code in Fedora Core 1.

If you give the parameters the same type, then the C front end has
acquired such a bug as well in 3.4/3.5.  Neither

void f (int fred, int fred);

nor

void f (int fred, int fred) {}

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.

(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?)

-- 
Joseph S. Myers
jsm@polyomino.org.uk


  reply	other threads:[~2004-01-17 12:17 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 [this message]
2004-01-17 21:20   ` Andrew Pinski
2004-01-18  2:12     ` Zack Weinberg
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=Pine.LNX.4.58.0401171213130.9475@digraph.polyomino.org.uk \
    --to=jsm@polyomino.org.uk \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=zack@codesourcery.com \
    /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).