public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103036] New: incorrect #pragma GCC diagnostic suppression for macro expansion and -Wuninitialized
Date: Mon, 01 Nov 2021 23:50:13 +0000	[thread overview]
Message-ID: <bug-103036-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103036
           Summary: incorrect #pragma GCC diagnostic suppression for macro
                    expansion and -Wuninitialized
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

The test case below shows that suppressing -Wuninitialized by #pragma GCC
diagnostic doesn't work the same as it does for other warnings (-Wrray-bounds
in this instance, but most other warnings behave like it).  This makes it
difficult for users to control -Wuninitialized (and -Wmaybe-uninitialized),
compounding their frustration when they run into one of its false positives.

The reason for the difference is that tree-ssa-uninit.c calls
linemap_resolve_location (line_table, location, LRK_SPELLING_LOCATION, NULL)
before using location, which other warnings don't do.  The call was introduced
in r186971 along with a test for its effect, gcc.dg/cpp/pragma-diagnostic-2.c,
with the goal to improve the macro expansion output printed by GCC with
-ftrack-macro-expansion as well as its interaction with on #pragma GCC
diagnostic.  It seems to me that the change was ill thought out: I can think of
no reason why -Wunitialized should be treated differently from all other
warnings.

$ cat a.c && gcc -O2 -S -Wall -Werror a.c
#define X(i) f (a[i]);

int f (int);

int g (void)
{
  int a[3];
#pragma GCC diagnostic push
#pragma GCC diagnostic warning "-Wuninitialized"
  return X (1);
#pragma GCC diagnostic pop
}

int h (void)
{
  int a[] = { 1, 2, 3 };
#pragma GCC diagnostic push
#pragma GCC diagnostic warning "-Warray-bounds"
  return X (3);
#pragma GCC diagnostic pop
}
a.c: In function ‘g’:
a.c:1:14: error: ‘a’ is used uninitialized [-Werror=uninitialized]
    1 | #define X(i) f (a[i]);
      |              ^~~~~~~~
a.c:10:10: note: in expansion of macro ‘X’
   10 |   return X (1);
      |          ^
a.c:7:7: note: ‘a’ declared here
    7 |   int a[3];
      |       ^
a.c: In function ‘h’:
a.c:1:14: warning: array subscript 3 is above array bounds of ‘int[3]’
[-Warray-bounds]
    1 | #define X(i) f (a[i]);
      |              ^~~~~~~~
a.c:19:10: note: in expansion of macro ‘X’
   19 |   return X (3);
      |          ^
a.c:16:7: note: while referencing ‘a’
   16 |   int a[] = { 1, 2, 3 };
      |       ^
cc1: all warnings being treated as errors

             reply	other threads:[~2021-11-01 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 23:50 msebor at gcc dot gnu.org [this message]
2021-11-01 23:53 ` [Bug middle-end/103036] " msebor at gcc dot gnu.org
2022-10-04  1:58 ` lhyatt 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-103036-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).