helixhorned 4b44063853 Fix taking address out of bounds of stack'd array, introduced in r3983. ... Clang's UBSan reports this as undefined behavior. I think that the reason is as follows: C99 6.5.3.2#1 (Constraints) says: The operand of the unary & operator shall be either a function designator, the result of a [] or unary * operator, or an lvalue that designates an object that is not a bit-field and is not declared with the register storage-class specifier. But in case of an expression like "&array[-1]", the operand ("array[-1]") does not designate a valid object. Moral: check first -- assure that an expression is valid for a particular operation before carrying it out. Keep in mind that otherwise, the compiler is absolutely free to optimize out the *check*. git-svn-id: https://svn.eduke32.com/eduke32@4014 1a8010ca-5511-0410-912e-c29ae57300e0		2013-08-12 15:18:18 +00:00
..
eduke32	Fix taking address out of bounds of stack'd array, introduced in r3983.	2013-08-12 15:18:18 +00:00
synthesis.sh	synthesis.sh: keep executable extension in a variable.	2013-08-11 15:28:47 +00:00