summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorEric Christopher <echristo@gmail.com>2015-12-10 21:38:56 +0000
committerEric Christopher <echristo@gmail.com>2015-12-10 21:38:56 +0000
commitb5c2b8dc92b09bddcbf63d75cba5cbc0bb9f43cd (patch)
tree9946c41779197e699b5bdd148df481cc8beb8dde /llvm/docs
parentd9f8ce997773e18315e04ab17d052f1db926d77b (diff)
downloadbcm5719-llvm-b5c2b8dc92b09bddcbf63d75cba5cbc0bb9f43cd.tar.gz
bcm5719-llvm-b5c2b8dc92b09bddcbf63d75cba5cbc0bb9f43cd.zip
Fix non-ascii quotes.
llvm-svn: 255301
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/DeveloperPolicy.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst
index 5eac458b8e7..5a83f5e43a8 100644
--- a/llvm/docs/DeveloperPolicy.rst
+++ b/llvm/docs/DeveloperPolicy.rst
@@ -528,12 +528,12 @@ for llvm users and not imposing a big burden on llvm developers:
C API Changes
----------------
-* Stability Guarantees: The C API is, in general, a “best effort” for stability.
+* Stability Guarantees: The C API is, in general, a "best effort" for stability.
This means that we make every attempt to keep the C API stable, but that
stability will be limited by the abstractness of the interface and the stability
-of the C++ API that it wraps. In practice, this means that things like “create
-debug info” or “create this type of instruction” are likely to be less stable
-than “take this IR file and JIT it for my current machine”.
+of the C++ API that it wraps. In practice, this means that things like "create
+debug info" or "create this type of instruction" are likely to be less stable
+than "take this IR file and JIT it for my current machine".
* Release stability: We won’t break the C API on the release branch with patches
that go on that branch, with the exception that if we will fix an unintentional
OpenPOWER on IntegriCloud