https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95349
--- Comment #49 from Christopher Nerz ---
Ah, misunderstood and therefore forgot optimization to a constant.
In the current code example, we have the problem that the (second)
initialization does not initialize with a value (ergo undefined behav
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95349
--- Comment #47 from Christopher Nerz ---
But shouldn't both give the same value?
The return of the new and the std::launder(...) point to the same object and
are both equal read-operations! It is imho not predictable that they behave
differently
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95349
Christopher Nerz changed:
What|Removed |Added
CC||Christopher.Nerz at de dot
bosch.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92687
Christopher Nerz changed:
What|Removed |Added
CC||Christopher.Nerz at de dot
bosch.c
