3 Commits

Author	SHA1	Message	Date
Richard Smith	eb3cad53e7	Add a warning for when an array-to-pointer decay is performed on an array ... temporary or an array subobject of a class temporary, and the resulting value is used to initialize a pointer which outlives the temporary. Such a pointer is always left dangling after the initialization completes and the array's lifetime ends. In order to detect this situation, this change also adds an LValueClassification of LV_ArrayTemporary for temporaries of array type which aren't subobjects of class temporaries. These occur in C++11 T{...} and GNU C++ (T){...} expressions, when T is an array type. Previously we treated the former as a generic prvalue and the latter as a class temporary. llvm-svn: 157955	2012-06-04 22:27:30 +00:00
Argyrios Kyrtzidis	e72f7154f1	Follow through references to catch returned stack addresses, local blocks, label addresses or references to temporaries, e.g: ... const int& g2() { int s1; int &s2 = s1; // expected-note {{binding reference variable 's2' here}} return s2; // expected-warning {{reference to stack memory associated with local variable 's1' returned}} } llvm-svn: 120483	2010-11-30 22:57:32 +00:00
Douglas Gregor	b154fdc974	Introduce a new kind of failed result for isLvalue/isModifiableLvalue ... which describes temporary objects of class type in C++. Use this to provide a more-specific, remappable diagnostic when takin the address of such a temporary. llvm-svn: 96396	2010-02-16 21:39:57 +00:00