diff options
| author | Eric Fiselier <eric@efcs.ca> | 2017-02-17 07:31:38 +0000 |
|---|---|---|
| committer | Eric Fiselier <eric@efcs.ca> | 2017-02-17 07:31:38 +0000 |
| commit | 7f1604aae62800e111f008717523498630473422 (patch) | |
| tree | 7d1e84d30655d35452ed351d47b2ca23adbde87c /lldb/packages/Python/lldbsuite/test/python_api/symbol-context/main.c | |
| parent | dc4cb02470d9046d9f11129c0e09fbf18a8b34ad (diff) | |
| download | bcm5719-llvm-7f1604aae62800e111f008717523498630473422.tar.gz bcm5719-llvm-7f1604aae62800e111f008717523498630473422.zip | |
Use inline namespaces with GCC instead of __attribute__((__strong__)).
GCC 7.0.1 started warning that __attribute__((__strong__)) is depricated.
This patch switches to using inline namespace with GCC instead. I believe
this wasn't done originally in order to support older GCC versions w/o
support for inline namespaces, or because earlier versions of GCC warned
users that the STL was using an inline namespace (even though it shouldn't affect users).
However I believe all of the above problems are gone for GCC 4.9 and greater.
Therefore switching to using inline namespaces instead of using __strong__
is the most correct behavior.
llvm-svn: 295428
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/symbol-context/main.c')
0 files changed, 0 insertions, 0 deletions
