public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pavel.morozkin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/83584] "ISO C forbids conversion of object pointer to function pointer type" -- no, not really
Date: Wed, 12 Jan 2022 19:22:10 +0000 [thread overview]
Message-ID: <bug-83584-4-in18h2yeLf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83584-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83584
Pavel M <pavel.morozkin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pavel.morozkin at gmail dot com
--- Comment #21 from Pavel M <pavel.morozkin at gmail dot com> ---
FYI: Rationale for C, Revision 5.10, April-2003:
> Even with an explicit cast, it is invalid to convert a function pointer to an object pointer or a pointer to void, or vice versa.
next prev parent reply other threads:[~2022-01-12 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-83584-4@http.gcc.gnu.org/bugzilla/>
2018-01-01 0:15 ` joseph at codesourcery dot com
2022-01-12 19:22 ` pavel.morozkin at gmail dot com [this message]
2024-03-28 22:51 ` kkylheku 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=bug-83584-4-in18h2yeLf@http.gcc.gnu.org/bugzilla/ \
--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).