public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/44586] gcc does not warn about casting non-variadic types to variadic types
Date: Sun, 20 Jun 2010 22:17:00 -0000	[thread overview]
Message-ID: <20100620221735.24401.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44586-10179@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from joseph at codesourcery dot com  2010-06-20 22:17 -------
Subject: Re:  gcc does not warn about casting non-variadic types
 to variadic types

It's not the conversion that's undefined, but the call.  You could have an 
option to warn for all function pointer conversions to incompatible 
function pointer types (but they have reasonable uses as there isn't a 
generic function pointer type like void *) - or you could have the 
optimizers detect calls to incompatibly cast types and warn then like the 
front ends does when the cast appears directly in the call.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44586


  parent reply	other threads:[~2010-06-20 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 19:48 [Bug c/44586] New: " raj dot khem at gmail dot com
2010-06-20 21:41 ` [Bug c/44586] " manu at gcc dot gnu dot org
2010-06-20 22:17 ` joseph at codesourcery dot com [this message]
2010-06-20 22:25 ` manu 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=20100620221735.24401.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).