summaryrefslogtreecommitdiffstats
path: root/lldb/unittests/Process/gdb-remote/GDBRemoteClientBaseTest.cpp
diff options
context:
space:
mode:
authorAndrey Bokhanko <andreybokhanko@gmail.com>2016-07-29 10:42:48 +0000
committerAndrey Bokhanko <andreybokhanko@gmail.com>2016-07-29 10:42:48 +0000
commit276055bb2f4a4297405fdcdfdb1940dc41bc7459 (patch)
tree35076a6c3bf02be6cfe286d1d4a3d3c7f4626454 /lldb/unittests/Process/gdb-remote/GDBRemoteClientBaseTest.cpp
parent12fc6752122d24c2585696b7ea20b6e93fa498be (diff)
downloadbcm5719-llvm-276055bb2f4a4297405fdcdfdb1940dc41bc7459.tar.gz
bcm5719-llvm-276055bb2f4a4297405fdcdfdb1940dc41bc7459.zip
[GCC] Support for __final specifier
As reported in bug 28473, GCC supports "final" functionality in pre-C++11 code using the __final keyword. Clang currently supports the "final" keyword in accordance with the C++11 specification, however it ALSO supports it in pre-C++11 mode, with a warning. This patch adds the "__final" keyword for compatibility with GCC in GCC Keywords mode (so it is enabled with existing flags), and issues a warning on its usage (suggesting switching to the C++11 keyword). This patch also adds a regression test for the functionality described. I believe this patch has minimal impact, as it simply adds a new keyword for existing behavior. This has been validated with check-clang to avoid regressions. Patch is created in reference to revisions 276665. Patch by Erich Keane. Differential Revision: https://reviews.llvm.org/D22919 llvm-svn: 277134
Diffstat (limited to 'lldb/unittests/Process/gdb-remote/GDBRemoteClientBaseTest.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud