From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-198628-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 75676 invoked by alias); 28 Mar 2019 06:07:59 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 75660 invoked by uid 89); 28 Mar 2019 06:07:58 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:648, H*r:a17, HTo:U*joel
X-HELO: mail-ed1-f43.google.com
Received: from mail-ed1-f43.google.com (HELO mail-ed1-f43.google.com) (209.85.208.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Mar 2019 06:07:57 +0000
Received: by mail-ed1-f43.google.com with SMTP id x10so16072630edh.11        for <gcc@gcc.gnu.org>; Wed, 27 Mar 2019 23:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gwmail-gwu-edu.20150623.gappssmtp.com; s=20150623;        h=mime-version:in-reply-to:references:from:date:message-id:subject:to         :cc;        bh=LwDSKa9+RNfQCWN6piDQhuFfi6LR1N0nwsV9CvS0oVI=;        b=MUyx+oONE5Ss6usc/Au0lBrfVRwasJuiFObHCY2bPb6O+enobqEzQsLxC423rYQp53         f8Sak2Mm3qjektLyDpqPGPU0KVuRWZZ7SU2OOK4CUToX9GVbk8RvUf3YaNEFd9sOEXvX         wc9sxga7VBQ5aTp9DCReHhNBljGNW97IeFrQBSktOdxjf4GRY5iuLlaAFQHfF3oW9BFM         746Ax51YLhNcWO6zOSaEx93ruvPpKZe1tXky8CwBSuYoZM0DHhFDd3d91MDR2vDruQZ3         WeWLhQ37AF5NGD7PxuKiPQaXJVLGpT3o51DgmDXASqX6v3lr0V+efX9IBAqH/Jey37Me         udEg==
MIME-Version: 1.0
Received: by 2002:a17:906:3602:0:0:0:0 with HTTP; Wed, 27 Mar 2019 23:07:53 -0700 (PDT)
In-Reply-To: <CAF9ehCXPqqt8Qw0BWEufivHyoX61SwZKNhC-UqpnXEgGGvUJYw@mail.gmail.com>
References: <CAF9ehCXPqqt8Qw0BWEufivHyoX61SwZKNhC-UqpnXEgGGvUJYw@mail.gmail.com>
From: Eric Gallager <egall@gwmail.gwu.edu>
Date: Thu, 28 Mar 2019 06:07:00 -0000
Message-ID: <CAMfHzOuRX1-e=rA=-staDf=-0BThJ+6-YKgQWb1m2N9o0AnkZA@mail.gmail.com>
Subject: Re: Warning for C Parameter Name Mismatch
To: joel@rtems.org
Cc: GCC <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-03/txt/msg00242.txt.bz2

On 3/8/19, Joel Sherrill <joel@rtems.org> wrote:
> Hi
>
> This may be just an ignorant user question on my part.
>
> Can gcc report when the parameter name in a C prototype
> does not match that used in the implementation?
>
> int f(int x);
>
> int f(int y) {...}
>
> We try to fix every warning gcc reports but this is one that gcc
> doesn't report for us. It could be we need an extra -Wxxx but
> we end up spotting these with Doxygen.
>
> Anything we are missing?
>
> Thanks.
>
> --joel
>

I found bug 79022 which seems relevant to this conversation:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79022