Go to file
Chandler Carruth b009b14971 There were some frustrating problems with the implementation of
-Wwrite-strings. First and foremost, once the positive form of the flag
was passed, it could never be disabled by passing -Wno-write-strings.
Also, the diagnostic engine couldn't in turn use -Wwrite-strings to
control diagnostics (as GCC does) because it was essentially hijacked to
drive the language semantics.

Fix this by giving CC1 a clean '-fconst-strings' flag to enable
const-qualified strings in C and ObjC compilations. Corresponding
'-fno-const-strings' is also added. Then the driver is taught to
introduce '-fconst-strings' in the CC1 command when '-Wwrite-strings'
dominates.

This entire flag is basically GCC-bug-compatibility driven, so we also
match GCC's bug where '-w' doesn't actually disable -Wwrite-strings. I'm
open to changing this though as it seems insane.

llvm-svn: 130051
2011-04-23 06:30:43 +00:00
clang There were some frustrating problems with the implementation of 2011-04-23 06:30:43 +00:00
compiler-rt Make sure we include __sync_synchronize on arm platforms if we need it. 2011-04-21 22:05:05 +00:00
debuginfo-tests These tests are x86_64 specific. 2011-03-28 20:00:34 +00:00
libcxx http://llvm.org/bugs/show_bug.cgi?id=9765 2011-04-21 14:29:59 +00:00
lldb Fixed the SymbolContext::DumpStopContext() to correctly indent and dump 2011-04-23 02:04:55 +00:00
llvm Accidental function name mangling. 2011-04-23 04:08:15 +00:00