https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96269
--- Comment #6 from sshannin at gmail dot com ---
Thanks to you both for your analysis. As I said, I wasn't sure if it was an
issue, so I'm certainly willing to accept that it's not.
The one point I wanted to emphasize though just to make sure we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98980
Bug ID: 98980
Summary: Very slow compilation with -Wduplicated-branches and
ubsan
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69600
--- Comment #7 from sshannin at gmail dot com ---
Comment on attachment 37541
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37541
preprocessed source
> #include
> #include
> #include
>typedef std::unique_ptr inner_value_t;
>typedef std
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118194
Bug ID: 118194
Summary: spurious warning with -Wmaybe-uninitialized
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118194
--- Comment #3 from sshannin at gmail dot com ---
> The wording is also quite confusing - it should probably say
'dereferencing 'p' would access uninitialized memory'.
Oh, indeed. I can certainly confirm that's how I interpreted it when filing
t
