public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bug-apl at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94905] Bogus warning -Werror=maybe-uninitialized
Date: Sun, 03 May 2020 13:28:48 +0000	[thread overview]
Message-ID: <bug-94905-4-AR2Id3YDXr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94905-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Dr. Jürgen Sauermann <bug-apl at gnu dot org> ---
I checked different g++ versions; the problem occurs in versions 9, 10, and 11
of g++ but not in version 8.

I tried to shrink the code to the bare minimum but if I do so then the warning
is no longer emitted.

I noticed that the warning has become more verbose in g++ version 11.
Before version 11 the warning said (one example of many):


Shape.hh:133:18: error: ‘shape_Z.Shape::rho[axis]’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
         if (rho[r])   { volume /= rho[r];  rho[r] = sh;  volume
*= rho[r]; }
                  ~~~~~^

In version g++ 11 it now says:


Shape.hh: In member function ‘virtual Token Bif_F12_FORMAT::eval_B(Value_P)’:
Shape.hh:133:18: error: ‘shape_Z.Shape::rho[<unknown>]’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
  133 |         if (rho[r])   { volume /= rho[r];  rho[r] = sh;  volume *=
rho[r]; }
      |             ~~~~~^


The <unknown> in shape_Z.Shape::rho[<unknown>] above is the function argument
'axis' of the function set_shape_item(axis, length) inside which the warning is
being issued.

This suggests that the warning is issued whenever the compiler is unable to
statically determine if some function argument (the vector index 'axiss' in
this case) is inside or outside the initialized region of a vector.

This seems to be overly picky; I would normally assume that the data members of
a class are always initialized. If not then the constructor and not any member
function should emit a warning.

Thanks for your attention and for gcc/g++
Jürgen Sauermann

  parent reply	other threads:[~2020-05-03 13:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 16:25 [Bug c++/94905] New: " bug-apl at gnu dot org
2020-05-01 22:41 ` [Bug c++/94905] " glisse at gcc dot gnu.org
2020-05-03 13:28 ` bug-apl at gnu dot org [this message]
2020-05-03 15:02 ` asolokha at gmx dot com
2020-05-03 16:10 ` bug-apl at gnu dot org
2020-05-03 16:16 ` bug-apl at gnu dot org
2020-05-03 16:26 ` asolokha at gmx dot com
2020-07-02 15:47 ` moller at mollerware dot com
2020-07-02 15:51 ` moller at mollerware dot com
2020-09-03 18:34 ` manu at gcc dot gnu.org
2020-09-03 18:46 ` [Bug c++/94905] [10 Regression] " manu at gcc dot gnu.org
2021-04-08 16:34 ` [Bug tree-optimization/94905] [10/11 " jason at gcc dot gnu.org
2022-01-21 13:41 ` rguenth at gcc dot gnu.org
2022-01-21 13:41 ` rguenth at gcc dot gnu.org
2022-01-21 13:43 ` rguenth at gcc dot gnu.org
2022-01-31 14:50 ` marxin at gcc dot gnu.org
2022-04-07  9:39 ` rguenth at gcc dot gnu.org
2022-04-07 10:01 ` jakub at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug tree-optimization/94905] [11 " rguenth 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-94905-4-AR2Id3YDXr@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).