|
From: | Fabrice Popineau |
Subject: | Re: Windows 64 port |
Date: | Sat, 24 Mar 2012 10:27:12 +0100 |
The situation with the INT_RANGE_OVERFLOW check is similar, except
there the macro is more like this:
#define a 2147483647
#define b 1
#define FOO (INT_ADD_OVERFLOW (a,b) ? INT_MAX : (a)+(b))
int i = FOO;
Again, any compiler that warns about potential overflow of
2147483647+1 should be ignored, because the _expression_
2147483647+1 cannot possibly be evaluated.
[Prev in Thread] | Current Thread | [Next in Thread] |