From: Richard Smith
Date: Fri, 14 Mar 2014 20:26:09 +0000 (+0000)
Subject: Try to remove confusion about C++11 feature support:
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ccccaddb184c6ef5460106b25c50473d653a1a24;p=clang
Try to remove confusion about C++11 feature support:
* Explicitly say that we conform to the two N/A bullets that required no
compiler changes.
* Remove a library feature from our features list.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@203964 91177308-0d34-0410-b5e6-96231b3b80d8
---
diff --git a/www/cxx_status.html b/www/cxx_status.html
index 316f6b0590..b29d587a94 100644
--- a/www/cxx_status.html
+++ b/www/cxx_status.html
@@ -303,7 +303,7 @@ currently requires the C++ runtime library from g++-4.8 or later.
Minimal support for garbage collection and reachability-based leak detection |
N2670 |
- N/A |
+ N/A (2) |
Allowing move constructors to throw [noexcept] |
@@ -332,7 +332,7 @@ currently requires the C++ runtime library from g++-4.8 or later.
Strong Compare and Exchange |
N2748 |
- Clang 3.1 (2) |
+ Clang 3.1 (3) |
Bidirectional Fences |
@@ -348,18 +348,13 @@ currently requires the C++ runtime library from g++-4.8 or later.
Data-dependency ordering: atomics and memory model |
N2664 |
- Clang 3.2 (3) |
+ Clang 3.2 (4) |
Propagating exceptions |
N2179 |
Clang 2.9 |
-
- Abandoning a process and at_quick_exit |
- N2440 |
- N/A |
-
Allow atomics use in signal handlers |
N2547 |
@@ -397,20 +392,24 @@ currently requires the C++ runtime library from g++-4.8 or later.
Extended integral types |
N1988 |
- N/A (4) |
+ N/A (5) |
(1): The [[carries_dependency]]
attribute
has no effect.
-(2): All compare-exchange operations are emitted as
+(2): No compiler changes are required for an implementation
+such as Clang that does not provide garbage collection.
+(3): All compare-exchange operations are emitted as
strong compare-exchanges.
-(3): memory_order_consume
is lowered to
+(4): memory_order_consume
is lowered to
memory_order_acquire
.
-(4): __int128
is not treated as an extended
-integer type, because changing intmax_t
would be an
-ABI-incompatible change.
+(5): No compiler changes are required for an implementation
+such as Clang that does not provide any extended integer types.
+__int128
is not treated as an extended integer type,
+because changing intmax_t
would be an ABI-incompatible
+change.
C++1y implementation status