public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobias at strongswan dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/105654] transparent_union, function pointer and different types arguments causes null pointer to be passed Date: Fri, 20 May 2022 12:59:33 +0000 [thread overview] Message-ID: <bug-105654-4-a2P8GcTYZc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105654-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105654 Tobias Brunner <tobias at strongswan dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tobias at strongswan dot org --- Comment #4 from Tobias Brunner <tobias at strongswan dot org> --- Note that changing the macro so that instead of static typeof(_cb_parse)* parse = _cb_parse; it declares the function like this static _Bool (*parse)(void*, char* in) = _cb_parse; seems to fix the issue (see my update here: https://github.com/strongswan/strongswan/issues/1053#issuecomment-1131356912).
prev parent reply other threads:[~2022-05-20 12:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 6:41 [Bug c/105654] New: Address of local variable as function call argument is NULL?! gnu.org at quisquis dot de 2022-05-19 11:13 ` [Bug middle-end/105654] transparent_union, function pointer and different types arguments causes null pointer to be passed rguenth at gcc dot gnu.org 2022-05-19 11:34 ` schwab@linux-m68k.org 2022-05-19 12:25 ` schwab@linux-m68k.org 2022-05-20 12:59 ` tobias at strongswan dot org [this message]
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-105654-4-a2P8GcTYZc@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: linkBe 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).