This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/24068] Unconditional warning when using -combine
- From: "drow at false dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Sep 2005 18:58:35 -0000
- Subject: [Bug c/24068] Unconditional warning when using -combine
- References: <20050926192427.24068.dann@godzilla.ics.uci.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From drow at false dot org 2005-09-29 18:58 -------
Subject: Re: Unconditional warning when using -combine
On Mon, Sep 26, 2005 at 08:46:20PM -0000, dann at godzilla dot ics dot uci dot edu wrote:
> > So this about the following:
> > int f(a)
> > int a;
> > {
> > return a;
> > }
> > int f(int);
> >
> > Which is questionable.
> >
> > So I don't think this is not an inappropriate warning.
>
> It seems that the warning was designed for code like your example above.
> But if you have 1 K&R file and one C90 file, then there should be no warning...
> Another bad thing is that if you swap the files on the command line then you get
> no warning.
There certainly should be a warning. It's not obvious on most targets
with int, but what you're doing here won't work with float arguments;
if the prototype includes an argument list, the definition should also.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24068