https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63707
Eyal Rozenberg changed:
What|Removed |Added
CC||eyalroz at technion dot ac.il
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97553
--- Comment #5 from Eyal Rozenberg ---
(In reply to Jakub Jelinek from comment #4)
> Depends on what you mean by properly. -O3 can be used with sanitization,
> but expecting the code to be optimized the same way as without sanitization
> is wron
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97553
--- Comment #3 from Eyal Rozenberg ---
> And, the runtime sanitization intentionally isn't heavily optimized away,
> because the intent is to detect when the code is invalid, so it can't e.g.
> optimize away those checks based on assumption tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97553
Bug ID: 97553
Summary: [missed optimization] constexprness not noticed when
UBsan enabled
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97274
--- Comment #2 from Eyal Rozenberg ---
(In reply to Jonathan Wakely from comment #1)
> The linker issues the warning, because the symbol in glibc is annotated to
> cause a warning. It has nothing to do with GCC.
Hmm. There's still a question of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97274
Bug ID: 97274
Summary: Need ability to ensure no warning about tmpnam
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
