public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36849] IMA rejects to merge (function)decls with va_args
Date: Mon, 11 Aug 2008 00:51:00 -0000 [thread overview]
Message-ID: <20080811005004.24161.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36849-11811@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from pinskia at gcc dot gnu dot org 2008-08-11 00:50 -------
The error message is correct as the function types are not compatible. If in
fact this is invalid C even though we don't currently diagnostic it without
-combine.
Closing as invalid as -combine is doing the correct job of rejecting this.
> Ideally the __VA_ARGS__ would be dealt with as "any or none" param decl, so the
> function(s) above would be considered equal.
No, that is not what the C/C++ standard says about compatible function types.
Yes we could enable this and have -pedantic-error reject it but I don't see why
we should allow this as it is obvious invalid C code.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Component|middle-end |c
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36849
next prev parent reply other threads:[~2008-08-11 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 13:05 [Bug middle-end/36849] New: " aldot at gcc dot gnu dot org
2008-08-11 0:51 ` pinskia at gcc dot gnu dot org [this message]
2008-08-12 9:55 ` [Bug c/36849] " aldot at gcc dot gnu dot org
2008-08-12 15:06 ` pinskia at gcc dot gnu dot org
2008-08-12 15:50 ` aldot 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=20080811005004.24161.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).