public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102953] Improvements to CET-IBT and ENDBR generation
Date: Thu, 28 Oct 2021 01:53:27 +0000 [thread overview]
Message-ID: <bug-102953-4-0MWWY8A5Fz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102953-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102953
--- Comment #10 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andrew Cooper from comment #8)
> Actually, there is a (possibly pre-existing) diagnostics issue:
>
> $ cat proto.c
> static void __attribute__((cf_check)) foo(void);
> static void __attribute__((unused)) foo(void)
> {
> }
> void (*ptr)(void) = foo;
>
> $ gcc -Wall -Os -fcf-protection=branch -mmanual-endbr
> -fcf-check-attribute=no -c proto.c -o proto.o
> proto.c:2:37: error: conflicting types for 'foo'; have 'void(void)'
> 2 | static void __attribute__((unused)) foo(void)
> | ^~~
> proto.c:1:39: note: previous declaration of 'foo' with type 'void(void)'
> 1 | static void __attribute__((cf_check)) foo(void);
> | ^~~
>
>
> The diagnostic complaining that the forward declaration doesn't match the
> definition gives 'void(void)' as the type in both cases, leaving out the
> fact that they differ by cf_check-ness.
Please try the v2 patch.
next prev parent reply other threads:[~2021-10-28 1:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 17:01 [Bug c/102953] New: " andrew.cooper3 at citrix dot com
2021-10-26 20:45 ` [Bug target/102953] " hjl.tools at gmail dot com
2021-10-26 21:31 ` hjl.tools at gmail dot com
2021-10-26 22:48 ` hjl.tools at gmail dot com
2021-10-26 22:49 ` hjl.tools at gmail dot com
2021-10-27 8:38 ` peterz at infradead dot org
2021-10-27 13:40 ` hjl.tools at gmail dot com
2021-10-27 18:50 ` andrew.cooper3 at citrix dot com
2021-10-27 23:48 ` andrew.cooper3 at citrix dot com
2021-10-28 1:53 ` hjl.tools at gmail dot com
2021-10-28 1:53 ` hjl.tools at gmail dot com [this message]
2021-10-28 10:40 ` andrew.cooper3 at citrix dot com
2021-10-28 13:17 ` hjl.tools at gmail dot com
2021-10-28 13:17 ` hjl.tools at gmail dot com
2021-10-28 17:36 ` andrew.cooper3 at citrix dot com
2021-10-28 19:11 ` hjl.tools at gmail dot com
2021-10-28 19:12 ` hjl.tools at gmail dot com
2021-10-29 22:57 ` andrew.cooper3 at citrix dot com
2021-10-30 0:03 ` hjl.tools at gmail dot com
2021-10-30 0:04 ` hjl.tools at gmail dot com
2021-10-30 0:51 ` andrew.cooper3 at citrix dot com
2021-10-30 4:03 ` andrew.cooper3 at citrix dot com
2021-10-30 12:22 ` hjl.tools at gmail dot com
2021-11-05 11:11 ` andrew.cooper3 at citrix dot com
2021-11-05 14:29 ` hjl.tools at gmail dot com
2022-02-23 20:34 ` andrew.cooper3 at citrix 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-102953-4-0MWWY8A5Fz@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).