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/26542] bogus diagnostic with -pedantic?: format '%p'; expects type 'void*', but argument 2 has type 'A*'
Date: Fri, 08 Dec 2006 04:37:00 -0000 [thread overview]
Message-ID: <20061208043744.11046.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26542-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-08 04:37 -------
> I'd like to (probably uselessly but still) argue for reopening this bug and
> removing this warning. The interpretation of the standard text is open to
> questions: IMHO an "A *" pointer is a pointer to void, too, as any pointer in C
> is, implicitely, pointer to void. But most importantly I think this warning is
> absolutely useless and the only way to get rid of it is ugly (you need an
> explicit cast to "void *").
Except IIRC a target could have void* pass different from a char* when it comes
to var-args so really the warning is still correct.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26542
next prev parent reply other threads:[~2006-12-08 4:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 9:50 [Bug c/26542] New: bogus diagnostic with -pedantic?: format ‘%p’ expects type ‘void*’, but argument 2 has type ‘A*’ pluto at agmk dot net
2006-03-03 11:50 ` [Bug c/26542] bogus diagnostic with -pedantic?: format '%p'; expects type 'void*', but argument 2 has type 'A*' rguenth at gcc dot gnu dot org
2006-03-03 12:45 ` pinskia at gcc dot gnu dot org
2006-03-03 14:07 ` pinskia at gcc dot gnu dot org
2006-07-24 17:03 ` vz-gcc at zeitlins dot org
2006-07-24 17:16 ` pluto at agmk dot net
2006-12-08 4:37 ` pinskia at gcc dot gnu dot org [this message]
2006-12-08 11:08 ` vz-gcc at zeitlins dot org
2006-12-08 18:17 ` Andrew Pinski
2006-12-08 18:18 ` pinskia at gmail dot com
2009-02-10 22:23 ` jason dot orendorff at gmail dot com
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=20061208043744.11046.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).