3 ms·
I also wouldn't expect "undefined" to be consistent within a single compiler implementation. The optimizer is free to make different instances behave differentl
by dunham 3y ago
I also wouldn't expect "undefined" to be consistent within a single compiler implementation. The optimizer is free to make different instances behave differently.
- Someone 3y agoA single compiler can even seem inconsistent. A conforming compiler is allowed to completely remove undefined behavior like this: if((n << 64) == 0) { println("Hi!\n"); } if((n << 64) != 0) { println("Hi!\n"); } If it were implementation-defined, it would have to compile it to the equivalent of println("Hi!\n");
- deleted 3y ago[deleted]