4 Commits

Author	SHA1	Message	Date
Akira Hatanaka	f5c136186f	[Sema] Issue a warning for integer overflow in struct initializer ... Clang wasn't issuing a warning when compiling the following code: struct s { unsigned x; } s = { .x = 4 * 1024 * 1024 * 1024 }; rdar://problem/23399683 Differential Revision: http://reviews.llvm.org/D15097 llvm-svn: 257357	2016-01-11 17:22:01 +00:00
Richard Smith	ce8eca578d	Explicitly permit undefined behavior in constant initializers for global ... variables in C, in the cases where we can constant-fold it to a value regardless (such as floating-point division by zero and signed integer overflow). Strictly enforcing this rule breaks too much code. llvm-svn: 254992	2015-12-08 03:21:47 +00:00
Richard Smith	0c6124ba82	PR17381: Treat undefined behavior during expression evaluation as an unmodeled ... side-effect, so that we don't allow speculative evaluation of such expressions during code generation. This caused a diagnostic quality regression, so fix constant expression diagnostics to prefer either the first "can't be constant folded" diagnostic or the first "not a constant expression" diagnostic depending on the kind of evaluation we're doing. This was always the intent, but didn't quite work correctly before. This results in certain initializers that used to be constant initializers to no longer be; in particular, things like: float f = 1e100; are no longer accepted in C. This seems appropriate, as such constructs would lead to code being executed if sanitizers are enabled. llvm-svn: 254574	2015-12-03 01:36:22 +00:00
Josh Magee	4d1a79b8c0	Catch more cases when diagnosing integer-constant-expression overflows. ... When visiting AssignmentOps, keep evaluating after a failure (when possible) in order to identify overflow in subexpressions. Differential Revision: http://reviews.llvm.org/D1238 llvm-svn: 228202	2015-02-04 21:50:20 +00:00