diff options
| author | Howard Hinnant <hhinnant@apple.com> | 2013-02-15 15:37:50 +0000 |
|---|---|---|
| committer | Howard Hinnant <hhinnant@apple.com> | 2013-02-15 15:37:50 +0000 |
| commit | 65af0388b98a052725e62332adaa2485ad191f75 (patch) | |
| tree | 7845909e4ca6c5af52dcccf308a9fa2eb0da4140 /libcxx/www | |
| parent | 1fd843eee7b6a35297b2f1c3cb6017ef341a2413 (diff) | |
| download | bcm5719-llvm-65af0388b98a052725e62332adaa2485ad191f75.tar.gz bcm5719-llvm-65af0388b98a052725e62332adaa2485ad191f75.zip | |
Bruce Mitchener: Minor typo fixes.
llvm-svn: 175274
Diffstat (limited to 'libcxx/www')
| -rw-r--r-- | libcxx/www/atomic_design.html | 2 | ||||
| -rw-r--r-- | libcxx/www/atomic_design_a.html | 4 | ||||
| -rw-r--r-- | libcxx/www/atomic_design_c.html | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/libcxx/www/atomic_design.html b/libcxx/www/atomic_design.html index 87a2f624914..231484166a7 100644 --- a/libcxx/www/atomic_design.html +++ b/libcxx/www/atomic_design.html @@ -37,7 +37,7 @@ <p> There are currently 3 designs under consideration. They differ in where most -of the implmentation work is done. The functionality exposed to the customer +of the implementation work is done. The functionality exposed to the customer should be identical (and conforming) for all three designs. </p> diff --git a/libcxx/www/atomic_design_a.html b/libcxx/www/atomic_design_a.html index 0fc00436fb7..b329fd1ee9c 100644 --- a/libcxx/www/atomic_design_a.html +++ b/libcxx/www/atomic_design_a.html @@ -38,7 +38,7 @@ <p> The compiler supplies all of the intrinsics as described below. This list of intrinsics roughly parallels the requirements of the C and C++ atomics -proposals. The C and C++ library imlpementations simply drop through to these +proposals. The C and C++ library implementations simply drop through to these intrinsics. Anything the platform does not support in hardware, the compiler arranges for a (compiler-rt) library call to be made which will do the job with a mutex, and in this case ignoring the memory ordering parameter (effectively @@ -52,7 +52,7 @@ behavior is acceptable when the inputs do not conform as defined below. <blockquote><pre> <font color="#C80000">// In every intrinsic signature below, type* atomic_obj may be a pointer to a</font> -<font color="#C80000">// volatile-qualifed type.</font> +<font color="#C80000">// volatile-qualified type.</font> <font color="#C80000">// Memory ordering values map to the following meanings:</font> <font color="#C80000">// memory_order_relaxed == 0</font> <font color="#C80000">// memory_order_consume == 1</font> diff --git a/libcxx/www/atomic_design_c.html b/libcxx/www/atomic_design_c.html index ae2f5ffbc64..f574d4d7e2e 100644 --- a/libcxx/www/atomic_design_c.html +++ b/libcxx/www/atomic_design_c.html @@ -43,7 +43,7 @@ inserted directly into your application ... assembly that is not otherwise representable by higher level C or C++ expressions. The design of the libc++ <tt><atomic></tt> header started with this goal in mind. A secondary, but still very important goal is that the compiler should have to do minimal work to -faciliate the implementaiton of <tt><atomic></tt>. Without this second +facilitate the implementation of <tt><atomic></tt>. Without this second goal, then practically speaking, the libc++ <tt><atomic></tt> header would be doomed to be a barely supported, second class citizen on almost every platform. |
