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: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Sep 2005 19:54:23 -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 dann at godzilla dot ics dot uci dot edu 2005-09-26 19:54 -------
(In reply to comment #4)
> Because one file uses K&R style function defintions and the other uses a
prototype which is ANSI/ISO
> style.
> Simple example:
[snip]
> So I don't think this is not an inappropriate warning.
The question is: can this EVER result in incorrect behavior?
Is it incorrect from the standard point of view?
If the answer to the above is no, then there no reason to warn.
> --------------------------------------------
> As an aside, I wish people would stop using K&R style C already.
Aggreed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24068