Bug 1507358 - spurious -Wmaybe-uninitialized warning for default initialised member
Summary: spurious -Wmaybe-uninitialized warning for default initialised member
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 26
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1507359
TreeView+ depends on / blocked
 
Reported: 2017-10-30 02:31 UTC by Brad Hubbard
Modified: 2018-05-29 12:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1507359 (view as bug list)
Environment:
Last Closed: 2018-05-29 12:42:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Preprocessed multidelta output (42.25 KB, application/x-gzip)
2017-10-30 02:31 UTC, Brad Hubbard
no flags Details

Description Brad Hubbard 2017-10-30 02:31:42 UTC
Created attachment 1345261 [details]
Preprocessed multidelta output

Description of problem:
Unexpected -Wmaybe-uninitialized warning with gcc7 that doesn't appear to me to match any upstream bug.

Version-Release number of selected component (if applicable):
gcc-7.2.1-2.fc26.x86_64

How reproducible:
100%

Steps to Reproduce:
$ cat<<EOF>minimal.cpp
#include <boost/variant.hpp>
#include <string>

struct A {
  A() {}
  A(int64_t _x, std::string _y) : x(_x), y(_y) {}
  int64_t x = 0;
  std::string y;
};

struct B {
  B() {}
};

typedef boost::variant<A, B> BV;

struct D {
  D() {}
  BV bv;
  void f();
};

void D::f() { bv = B(); }
EOF

$ g++ -Wuninitialized -O1 -c minimal.cpp

Actual results:
minimal.cpp: In member function ‘void D::f()’:
minimal.cpp:4:8: warning: ‘*((void*)(& temp)+8).A::x’ may be used uninitialized in this function [-Wmaybe-uninitialized]
 struct A {

Expected results:
No warnings generated.

Additional info:
Moving the definition of 'f' inside the declaration of 'D' resolves the warning as does swapping the order of 'x' and 'y'. Attaching group_pool.ii which is preprocessed source which has been run through multidelta to try and reduce the size with limited success.

Comment 1 Brad Hubbard 2017-10-30 04:39:18 UTC
Changing 'typedef boost::variant<A, B> BV;' to 'typedef boost::variant<B, A> BV;' also eliminates the warning.

Comment 2 Fedora End Of Life 2018-05-03 08:26:06 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 12:42:34 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.