https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88935
Andrea Griffini changed:
What|Removed |Added
CC||agriff at tin dot it
--- Comment #12 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23
--- Comment #1 from Andrea Griffini ---
Forgot to say that -O3 is needed to see the warning (this is however expected)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23
Bug ID: 23
Summary: Warning about "used uninitialized" member shown or
hidden randomly
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108299
--- Comment #9 from Andrea Griffini ---
I agree that comment 0 is wrong and was based on a text that I thought was
taken from the standard but apparently was not (cppreference.com). Sorry for
the noise.
I think that if the dynamic initializatio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108299
--- Comment #5 from Andrea Griffini ---
So you are saying that the standard forgot to add "that requires dynamic
initialization" and that this is the intention?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108299
--- Comment #3 from Andrea Griffini ---
Thread storage duration is different from static storage duration.
The text I found on the topic is different from the one you are linking,
but even in this version (that is indeed more permissive) it's e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108299
Bug ID: 108299
Summary: toplevel thread_local variables are not initialized if
not referenced and initialized at wrong moment when
referenced
Product: gcc
Versio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105867
Andrea Griffini changed:
What|Removed |Added
CC||agriff at tin dot it
--- Comment #4 f
