https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18635
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|accepts-invalid |diagnostic
Blocks| |24639
Summary|[DR 504] use of |[DR 504] use of
|uninitialised reference |uninitialised reference
|accepted in C++ front end |accepted (without
| |-Wuninitialized) in C++
| |front end
Severity|normal |enhancement
--- Comment #17 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #16)
> This is
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3293.html#504 which
> is Open, so I'm suspending this. If/when that gets resolved we can revisit
> this PR.
>
> I think SUSPENDED rather than INVALID is being generous, as G++ is
> completely correct to accept the code, and follows the committee's
> intentions:
> "Implementations can warn about such constructs, and the resolution for
> issue 453 makes executing such code undefined behavior; that seemed to
> address the situation adequately."
Changing from an accepts-invalid to an enhancement request for an optional
-Wuninitialized diagnostic then
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
[Bug 24639] [meta-bug] bug to track all Wuninitialized issues
