public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103989] [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og since r12-1992-g6feb628a706e86eb
Date: Wed, 12 Jan 2022 12:54:37 +0000	[thread overview]
Message-ID: <bug-103989-4-i98rUHoKB3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103989-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |12.0

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
The IL has

  <bb 2> [local count: 1073741824]:
  D.35417 = D.35181;
  [/home/rguenther/install/gcc-12/usr/local/include/c++/12.0.0/optional:737:17]
D.34833 ={v} {CLOBBER};
  [/home/rguenther/install/gcc-12/usr/local/include/c++/12.0.0/optional:237:14]
MEM[(union _Storage *)[t.C:26:20] &D.34833] ={v} {CLOBBER};
  [/home/rguenther/install/gcc-12/usr/local/include/c++/12.0.0/optional:118:7]
[/home/rguenther/install/gcc-12/usr/local/include/c++/12.0.0/optional:118:7]
MEM[(struct _Optional_payload_base *)[t.C:26:20] &D.34833]._M_engaged = 0;
  [t.C:26:20] D.35417 ={v} {CLOBBER};

I suspect we warn on the use of D.35181 which is indeed not initialized
(of std::nullopt_t type).  The copied to D.35417 is dead but at -Og we
fail to elide the store.  I see there's no DSE performed for -Og
possibly on purpose to not degrade debug info more.  But that makes
-Wuninitialized susceptible for these kind of issues.

Note at -O1 the same IL is in the program, it's just elided before we get
the chance to warn on it.  The uninit use there is even visible before
inlining but we don't seem to diagnose by value passing of uninitialized
aggregates:

int main ()
{
  struct B b;
  struct nullopt_t D.35181;
  const struct optional D.34833;
  int _8;

  <bb 2> :
  [t.C:26:20] std::optional<A>::optional ([t.C:26:20] &D.34833, D.35181);

here D.35181 is passed to the CTOR (where it might be eventually not
used so not warning at the call is eventually OK).  The copy itself
is emitted by the inliner, so it's spurious to warn there and the
inliner could either try harder to not emit it or alternatively
mark the copy as to be not warned about.

  parent reply	other threads:[~2022-01-12 12:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 12:10 [Bug tree-optimization/103989] New: [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og marc@nieper-wisskirchen.de
2022-01-12 12:16 ` [Bug tree-optimization/103989] [12 regression] std::optional and bogus -Wmaybe-unitialized at -Og since r12-1992-g6feb628a706e86eb marxin at gcc dot gnu.org
2022-01-12 12:54 ` rguenth at gcc dot gnu.org [this message]
2022-01-12 17:44 ` jakub at gcc dot gnu.org
2022-01-12 19:11 ` pinskia at gcc dot gnu.org
2022-01-13 11:10 ` jakub at gcc dot gnu.org
2022-01-13 11:39 ` rguenth at gcc dot gnu.org
2022-01-13 11:56   ` Jan Hubicka
2022-01-13 11:56 ` hubicka at kam dot mff.cuni.cz
2022-01-13 12:03   ` Jan Hubicka
2022-01-13 12:03 ` hubicka at kam dot mff.cuni.cz
2022-01-13 12:25 ` rguenth at gcc dot gnu.org
2022-01-13 13:39 ` hubicka at kam dot mff.cuni.cz
2022-01-13 13:44 ` rguenther at suse dot de
2022-01-13 13:55 ` hubicka at kam dot mff.cuni.cz
2022-01-13 13:58 ` rguenth at gcc dot gnu.org
2022-01-13 14:11   ` Jan Hubicka
2022-01-13 14:11 ` hubicka at kam dot mff.cuni.cz
2022-01-13 15:01 ` cvs-commit at gcc dot gnu.org
2022-01-13 15:05 ` jakub at gcc dot gnu.org
2022-01-13 15:10 ` rguenther at suse dot de
2022-01-18 12:35 ` rguenth at gcc dot gnu.org
2022-01-18 14:43 ` cvs-commit at gcc dot gnu.org
2022-01-18 14:43 ` cvs-commit at gcc dot gnu.org
2022-01-18 14:43 ` 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-103989-4-i98rUHoKB3@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).