mkuper created this revision.
mkuper added a reviewer: rengolin.
mkuper added a subscriber: cfe-commits.
This partially reverts r260506 which removed this note.
Renato, the part about "not being implemented soon because it requires backend
support" was taken verbatim from the original text, pre-r260506, I only added
the fact non-allocatable registers are now supported.
If you prefer to have strong wording, feel free to make suggestions.
https://reviews.llvm.org/D27473
Files:
docs/UsersManual.rst
Index: docs/UsersManual.rst
===================================================================
--- docs/UsersManual.rst
+++ docs/UsersManual.rst
@@ -1830,6 +1830,10 @@
...
local_function(1);
+- clang only supports global register variables when the register specified
+ is non-allocatable (e.g. the stack pointer). Support for general global
+ register variables is unlikely to be implemented soon because it requires
+ additional LLVM backend support.
- clang does not support static initialization of flexible array
members. This appears to be a rarely used extension, but could be
implemented pending user demand.
Index: docs/UsersManual.rst
===================================================================
--- docs/UsersManual.rst
+++ docs/UsersManual.rst
@@ -1830,6 +1830,10 @@
...
local_function(1);
+- clang only supports global register variables when the register specified
+ is non-allocatable (e.g. the stack pointer). Support for general global
+ register variables is unlikely to be implemented soon because it requires
+ additional LLVM backend support.
- clang does not support static initialization of flexible array
members. This appears to be a rarely used extension, but could be
implemented pending user demand.
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
