Release notes for 1.1.2 and doxygen version number bump
This commit is contained in:
@@ -1,3 +1,24 @@
|
|||||||
|
=== v1.1.2 === (9 January 2012)
|
||||||
|
|
||||||
|
The major new feature in this release is support for "generic" C++
|
||||||
|
vectorized output; in other words, ispc can emit C++ code that corresponds
|
||||||
|
to the vectorized computation that the ispc program represents. See the
|
||||||
|
examples/intrinsics directory in the ispc distribution for two example
|
||||||
|
implementations of the set of functions that must be provided map the
|
||||||
|
vector calls generated by ispc to target specific functions.
|
||||||
|
|
||||||
|
ispc now has partial support for 'goto' statements; specifically, goto is
|
||||||
|
allowed if any enclosing control flow statements (if/for/while/do) have
|
||||||
|
'uniform' test expressions, but not if they have 'varying' tests.
|
||||||
|
|
||||||
|
A number of improvements have been made to the code generated for gathers
|
||||||
|
and scatters--one of them (better matching x86's "free" scale by 2/4/8 for
|
||||||
|
addressing calculations) improved the performance of the noise example by
|
||||||
|
14%.
|
||||||
|
|
||||||
|
Many small bugs have been fixed in this release as well, including issue
|
||||||
|
numbers 138, 129, 135, 127, 149, and 142.
|
||||||
|
|
||||||
=== v1.1.1 === (15 December 2011)
|
=== v1.1.1 === (15 December 2011)
|
||||||
|
|
||||||
This release doesn't include any significant new functionality, but does
|
This release doesn't include any significant new functionality, but does
|
||||||
|
|||||||
@@ -31,7 +31,7 @@ PROJECT_NAME = "Intel SPMD Program Compiler"
|
|||||||
# This could be handy for archiving the generated documentation or
|
# This could be handy for archiving the generated documentation or
|
||||||
# if some version control system is used.
|
# if some version control system is used.
|
||||||
|
|
||||||
PROJECT_NUMBER = 1.1.1
|
PROJECT_NUMBER = 1.1.2
|
||||||
|
|
||||||
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
||||||
# base path where the generated documentation will be put.
|
# base path where the generated documentation will be put.
|
||||||
|
|||||||
Reference in New Issue
Block a user