public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/24068] Unconditional warning when using -combine
Date: Mon, 26 Sep 2005 20:46:00 -0000 [thread overview]
Message-ID: <20050926204620.27438.qmail@sourceware.org> (raw)
In-Reply-To: <20050926192427.24068.dann@godzilla.ics.uci.edu>
------- Additional Comments From dann at godzilla dot ics dot uci dot edu 2005-09-26 20:46 -------
(In reply to comment #4)
> 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.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24068
next prev parent reply other threads:[~2005-09-26 20:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 19:24 [Bug c/24068] New: Unconditional warning when using -fwhole-program dann at godzilla dot ics dot uci dot edu
2005-09-26 19:25 ` [Bug c/24068] " dann at godzilla dot ics dot uci dot edu
2005-09-26 19:25 ` dann at godzilla dot ics dot uci dot edu
2005-09-26 19:29 ` [Bug c/24068] Unconditional warning when using -combine pinskia at gcc dot gnu dot org
2005-09-26 19:31 ` pinskia at gcc dot gnu dot org
2005-09-26 19:41 ` pinskia at gcc dot gnu dot org
2005-09-26 19:47 ` pinskia at gcc dot gnu dot org
2005-09-26 19:54 ` dann at godzilla dot ics dot uci dot edu
2005-09-26 19:59 ` pinskia at gcc dot gnu dot org
2005-09-26 20:46 ` dann at godzilla dot ics dot uci dot edu [this message]
2005-09-29 18:58 ` drow at false dot org
2005-09-29 20:10 ` dann at godzilla dot ics dot uci dot edu
[not found] <bug-24068-1008@http.gcc.gnu.org/bugzilla/>
2007-11-12 20:43 ` tromey at gcc dot gnu dot org
2010-09-17 9:08 ` rguenth at gcc dot gnu 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=20050926204620.27438.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).