summaryrefslogtreecommitdiffstats
path: root/clang/test/SemaCXX/writable-strings-deprecated.cpp
Commit message (Collapse)AuthorAgeFilesLines
* [Lit Test] Updated 20 Lit tests to be C++11 compatible.Charles Li2015-12-101-12/+18
| | | | | | | | This is the 5th Lit test patch. Expanded expected diagnostics to vary by C++ dialect. Expanded RUN line to: default, C++98/03 and C++11. llvm-svn: 255196
* Move the C++11 ExtWarn for converting a string literal to 'char*' out ofRichard Smith2014-04-221-1/+12
| | | | | | | | | -Wc++11-compat-deprecated-writable-strings. It's neither a C++11 compatibility warning nor a deprecated feature, it's just ill-formed. In passing, add that warning to -Wdeprecated, where it belongs. llvm-svn: 206833
* Add -Wdeprecated-writable-string in C++ to -Wc++11-compat, since it's ↵Richard Smith2013-11-141-0/+4
| | | | | | ill-formed in C++11. llvm-svn: 194736
* GCC overloads -Wwrite-strings just to make it extra confusing. While itChandler Carruth2011-04-231-0/+1
| | | | | | | | | | | | | | | | changes language semantics in C and ObjC (which Clang has supported for a while), in C++ it's the name used for Clang's -Wdeprecated-writable-strings. Clang's name is at least less overloaded if still confusing (the string isn't writable, we just allow converting to a non-const pointer without warning), so I've left it in place and made the GCC name an alias for compatibility. With this I've implemented all the aspects of GCC's -Wwrite-strings I've encountered which didn't work with Clang. llvm-svn: 130052
* -fwritable-strings should silence warnings about the deprecated stringDouglas Gregor2011-03-141-0/+1
| | | | | | -literal to char* conversion. Make it so. llvm-svn: 127586
* Put warning about makeing a string writable intoFariborz Jahanian2011-01-061-0/+12
its own deprecated diagnostics group so it can be turned off selectively. // rdar://8827606 llvm-svn: 122967
OpenPOWER on IntegriCloud