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

Fix numerous typos in documentation (goodness)

Browse Source
This commit is contained in:
Matt Pharr
2011-12-14 10:26:35 -08:00
parent 533b539780
commit 4adf527a4d
3 changed files with 48 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/faq.txt
View File

@@ -273,10 +273,10 @@ Then four object files will be generated: ``foo_sse2.o``, ``foo_sse4.o``,
``foo_avx.o``, and ``foo.o``.[#]_ Link all of these into your executable, and
when you call a function in ``foo.ispc`` from your application code,
``ispc`` will determine which instruction sets are supported by the CPU the
code is running on and will call the most appropraite version of the
code is running on and will call the most appropriate version of the
function available.
.. [#] Similarly, if you choose to generate assembly langauage output or
.. [#] Similarly, if you choose to generate assembly language output or
LLVM bitcode output, multiple versions of those files will be created.
In general, the version of the function that runs will be the one in the