public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107618] Incorrect diagnostics when using -Og, builtin_expect(), and function attribute "warning" or "error"
Date: Thu, 10 Nov 2022 17:21:09 +0000	[thread overview]
Message-ID: <bug-107618-4-FlkZFct3vD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107618-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107618

Yann Droneaud <yann at droneaud dot fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann at droneaud dot fr

--- Comment #1 from Yann Droneaud <yann at droneaud dot fr> ---
A smallest reproducer (generated with some help from C-reduce):

    void a(void) __attribute__((__warning__("")));
    int main(void) {
      unsigned long b = __builtin_object_size(0, 0);
      if (__builtin_expect(b < 1, 0))
        a();
    }

Works at all level above -00, except -Og:

    $ gcc -Og warning.c
    warning.c: In function ‘main’:
    warning.c:5:5: warning: call to ‘a’ declared with attribute warning: 
[-Wattribute-warning]
        5 |     a();
          |     ^~~

  reply	other threads:[~2022-11-10 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 15:42 [Bug other/107618] New: " yann at droneaud dot fr
2022-11-10 17:21 ` yann at droneaud dot fr [this message]
2022-11-10 17:45 ` [Bug middle-end/107618] " yann at droneaud dot fr
2022-11-11  7:47 ` [Bug tree-optimization/107618] " rguenth at gcc dot gnu.org
2022-11-11 13:32 ` cvs-commit at gcc dot gnu.org
2022-11-11 13:33 ` rguenth at gcc dot gnu.org
2022-11-11 14:37 ` yann at droneaud dot fr
2022-11-28 22:19 ` pinskia at gcc dot gnu.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=bug-107618-4-FlkZFct3vD@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).