Not much point in pedantic coding if you don't know what the compiler is doing
there is a development phase called "trust"
practically speaking you have to verify what the compiler does, forcing the compiler to the assembly
(e.g. gcc $flags -S source.c -o source.asm, flags=optimization level? -O0? -O1? -O2? -O3? -OS? )
and then analyzing it, code-statement per code-statement
(if you are the "trust-verifier dude" you also have a lot of documentation to write)
it's boring, but it's required by the "life cycle process in Avionics" (explained this way, by my Boss)
so It smells that someone has deliberately disabled the "short-circuits" feature in SierraC
if this is true (I have to find and check its documentation), I'd like to know WHY?