public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jochen447 at concept dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105628] New: False positive with -Waddress
Date: Tue, 17 May 2022 12:32:59 +0000	[thread overview]
Message-ID: <bug-105628-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105628
           Summary: False positive with -Waddress
           Product: gcc
           Version: 12.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jochen447 at concept dot de
  Target Milestone: ---

Created attachment 52986
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52986&action=edit
minified example program to show the false positive

Option -Wall also enables -Waddress, which causes a lot of false positives like
shown in my attached example problem (minimized and anonymized real world
example):

waddress.c: In function ‘comp_has_ExtraPtr’:
waddress.c:44:29: warning: the comparison will always evaluate as ‘true’ for
the pointer operand in ‘(struct Extra **)&comp->pin + 4’ must not be NULL
[-Waddress]
   44 |     return ExtraPtrOf(comp) ? 1 : 0;
      |                             ^

It only seems to be emitted when using the ?-operator.


# gcc -v
...
gcc version 12.1.1 20220507 (Red Hat 12.1.1-1) (GCC)


# uname -a
Linux fedora 5.17.6-300.fc36.x86_64 #1 SMP PREEMPT Mon May 9 15:47:11 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux

             reply	other threads:[~2022-05-17 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 12:32 jochen447 at concept dot de [this message]
2022-05-17 12:44 ` [Bug c/105628] " pinskia at gcc dot gnu.org
2022-10-25  7:11 ` [Bug c/105628] [12/13 Regression] " pinskia at gcc dot gnu.org
2023-04-08 14:45 ` law at gcc dot gnu.org
2023-05-08 12:24 ` [Bug c/105628] [12/13/14 " rguenth at gcc dot gnu.org
2024-03-11 12:32 ` pinskia at gcc dot gnu.org
2024-03-11 12:34 ` 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-105628-4@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).