"multiple compilers for a single language is bad because they aren't fully compatible" yea and making the code works on multiple of them, the ones that might be used, is your job as a developer
anyone scream at web devs if they go "sorry we don't care about firefox, only chromium, they don't have perfect compatibility" but when it comes to literally any other codebase suddenly it's not expected anymore
like, webdevs write some utterly fucked up architecture, sure, and i'm not defending them for everything, but double standard much ?
@SRAZKVT people only care about portability when it affects their own usage, more at 11
it's not like it's not exactly like this with *anything*
@q66 yea but idk i was kinda hoping people were better, maybe that's hoping for too much though
@SRAZKVT
the number of times i've seen cases like someone whining that someone support their thing only to immediately deride someone else's case with "who cares noone even uses your shit"
@kirtai @SRAZKVT @hypha uh, no it won't? -ffast-math is never enabled unless explicitly, since it's not ieee754 compliant
under clang -O3 is identical to -O2 plus some optimizations with high compile time costs and low runtime benefits, under gcc -O3 is closer to clang -O2 but definitely no ffast-math either