aaron/ispc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fixed typos.

Browse Source
This commit is contained in:
Daniel Schubert
2011-06-28 10:14:24 +02:00
committed by Matt Pharr
parent cb74346d36
commit b6d6ee6fc2
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ispc.txt
View File

@@ -341,7 +341,7 @@ before it's compiled. On Windows®, pre-processor definitions should be
provided to the ``cl`` call. provided to the ``cl`` call.
By default, the compiler generates x86-64 Intel® SSE4 code. To generate By default, the compiler generates x86-64 Intel® SSE4 code. To generate
32-bit code, you can use the the ``--arch=x86`` command-line flag. To 32-bit code, you can use the ``--arch=x86`` command-line flag. To
select Intel® SSE2, use ``--target=sse2``. select Intel® SSE2, use ``--target=sse2``.
``ispc`` supports an alternative method for generating Intel® SSE4 code, ``ispc`` supports an alternative method for generating Intel® SSE4 code,
@@ -1247,7 +1247,7 @@ section.)
For ``if`` statements where the different running SPMD program instances For ``if`` statements where the different running SPMD program instances
don't have coherent values for the boolean ``if`` test, using ``cif`` don't have coherent values for the boolean ``if`` test, using ``cif``
introduces some additional overhead from the ``all`` and ``any`` tests as introduces some additional overhead from the ``all`` and ``any`` tests as
well as the corresponding branches. For cases where the the program well as the corresponding branches. For cases where the program
instances often do compute the same boolean value, this overhead is instances often do compute the same boolean value, this overhead is
worthwhile. If the control flow is in fact usually incoherent, this worthwhile. If the control flow is in fact usually incoherent, this
overhead only costs performance. overhead only costs performance.