diff --git a/docs/ReleaseNotes.txt b/docs/ReleaseNotes.txt index 492d7428..e7e26213 100644 --- a/docs/ReleaseNotes.txt +++ b/docs/ReleaseNotes.txt @@ -1,3 +1,29 @@ +=== v1.0.12 === (20 October 2011) + +This release includes a new "double-pumped" 8-wide target for SSE2, +"sse2-x2". Like the sse4-x2 and avx-x2 targets, this target may deliver +higher performance for some workloads than the regular sse2 target. (For +other workloads, it may be slower.) + +The ispc language now includes an "assert()" statement. See +http://ispc.github.com/ispc.html#assertions for more information. + +The compiler now sets a preprocessor #define based on the target ISA; for +example, ISPC_TARGET_SSE4 is defined for the sse4 targets, and so forth. + +The standard library now provides high-performance routines for converting +between some "array of structures" and "structure of arrays" formats. +See +http://ispc.github.com/ispc.html#converting-between-array-of-structures-and-structure-of-arrays-layout +for more information. + +Inline functions now have static linkage. + +A number of improvements have been made to the optimization passes that +detect when gathers and scatters can be transformed into vector stores and +loads, respectively. In particular, these passes now handle variables that +are used as loop induction variables much better. + === v1.0.11 === (6 October 2011) The main new feature in this release is support for generating code for diff --git a/docs/ispc.txt b/docs/ispc.txt index 654601de..af34cbe2 100644 --- a/docs/ispc.txt +++ b/docs/ispc.txt @@ -123,7 +123,7 @@ Contents: + `Explicit Vector Programming With Uniform Short Vector Types`_ + `Choosing A Target Vector Width`_ + `Compiling With Support For Multiple Instruction Sets`_ - + `Implementing Reductions Efficiently `+ + + `Implementing Reductions Efficiently`_ * `Disclaimer and Legal Information`_ diff --git a/doxygen.cfg b/doxygen.cfg index 3f88bc50..a84560fa 100644 --- a/doxygen.cfg +++ b/doxygen.cfg @@ -31,7 +31,7 @@ PROJECT_NAME = "Intel SPMD Program Compiler" # This could be handy for archiving the generated documentation or # if some version control system is used. -PROJECT_NUMBER = 1.0.11 +PROJECT_NUMBER = 1.0.12 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) # base path where the generated documentation will be put.