News for hackers. Stuff that matters.
Re:Clang vs. Clang by exe34 on Saturday August 03, 2024 @12:25PM (#41147525)
clang::optnone
Re:Clang vs. Clang by nabla9 on Saturday August 03, 2024 @12:34PM (#41147588)
"Optimizing compilers that don't allow disabling __all__ optimizations"
Re:Clang vs. Clang by layer8 on Saturday August 03, 2024 @02:21PM (#41148250)
It’s not well-defined what counts as an optimization. For example, should every single source-level read access of a memory location go through all cache levels down to main memory, instead of, for example, caching values in registers? That would be awfully slow. But that question is one reason for UB.
Re:Clang vs. Clang by kevingadd on Saturday August 03, 2024 @04:34PM (#41149054)
Or writing code that relies on inlining and/or tail call optimization to successfully run at all without running out of stack... We've got some code that doesn't run if compiled O0 due to that.
Re:Clang vs. Clang by exe34 on Saturday August 03, 2024 @01:05PM (#41147775)
do these exist? who's using them?