Indeed. The invalid optimization clang is making is assuming malloc doesn't fail. Unless GCC also does that, GCC is ok.
SO is undefined, by contradiction if nothing else. C doesn't preclude unlim rec, but imposes finite # objs
-
-
There is an obvious limit on the # of objects if you take their addresses. Otherwise it's more tricky.
-
Allowing pgm w/ >2**CHAR_BIT*sizeof(void*) objs violates req that objs have addr even w/out &, by cnt arg.
-
Objects are not required to have an address, they could be located in registers.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.