Strict aliasing is the most retarded thing I have ever heard of in my entire life. The class of optimizations it allows for aren't even that good or common.
You sound like you're 20 minutes into learning what compiler optimizations are.
>>106486563Strict aliasing is probably the greatest disaster in computing history. It utterly wrecked C/C++ and as such undermined the stability and reliability of basically all software.
>>106486912It's genuinely incredible that nobody ever even says this. Nobody criticizes the fact that it's in the standard and it's the default behavior, despite clearly being fucking insane. It's just "Oh yeah haha, that's undefined behavior, the compiler will break your code" and act like it's fine.
>>106486563TinyC dont have the problem
>>106486563That is such a cool duck!
>>106487860Crypto futures are now live in the USUS clients can start trading crypto futures todaythrough Kraken Derivatives USSign upExplore Pro
>>106486563caching variables in registers and not having to reload them is both good and common
>>106486563>Strict aliasingmust be one of the biggest nothingburgers in cs
>>106486953>>106486912Whats "fucking insane" is morons like you and every other midwitted "ahhh source" poster on stackoverflow who are dumb enough to think, "hmm, some global homo organization with zero R&D budget, zero development experience, zero experience beyond paper-pushing for that matter, these are the ones dictating what is 'the default behavior'". I don't know whats more pathetic: the fact that these aforementioned paper pushers exist, people like you who respect their word, or the midwits who will unironically argue to hell and back that "trust me bro, you need to use <current spec, current year -1>" in a heavily amended answer accounting for every god damn biannual rephrasing and reproposed wording of these totally legitimate specifications. Reality check, there were only ever 3 main compilers - GCC, EDG, and MSVC; and none of them force retarded behavior on you. Next time you could just say "im a retard nigger who got filtered by a compiler flag" and be done with it.
>>106488775 ****4* LLVM (except its GCC like), maybe 5* if you wanna include RADAlso worthy of note, most of the compilers boomers will cream themselves over were glorified EDG packages with a naive backend glued on, so they werent really a consideration.
>>106488586wtf are you talking about? is this about beancounting again?>captcha: 8krah
>>106488775Who the fuck is edg
>>106486563If you're aliasing incompatible pointers whatever it is you're doing is hardware specific enough you should be writing it in assembly.
