diff --git a/documentation/BuildingNBody.html b/documentation/BuildingNBody.html
index 81fc0f06017e502e433b7e6561c05727b02fbc51..a6b1d70c939fb9bc62e1aa349abb932dbba8e7dc 100644
--- a/documentation/BuildingNBody.html
+++ b/documentation/BuildingNBody.html
@@ -66,7 +66,7 @@
examples/
...
nbody/
- src/java/com.syncleus.aparapi.nbody/
+ src/java/com.aparapi.nbody/
build.xml
nbody.sh
nbody.bat
diff --git a/documentation/ConvertingBytecodeToOpenCL.html b/documentation/ConvertingBytecodeToOpenCL.html
index 3d0c14073d887cfe5152ace09539b0715b633794..e0bd58bc84fda9a4133f47eecda072bf42262f5d 100644
--- a/documentation/ConvertingBytecodeToOpenCL.html
+++ b/documentation/ConvertingBytecodeToOpenCL.html
@@ -74,7 +74,7 @@
<p>The classfile format is well documented here and we will not go into too much detail here, however it should be known that Aparapi must parse the classfile of each Kernel to extract the bytecode for the Kernel.run() and any method reachable from Kernel.run().</p>
<p>Lets start with a simple Kernel.</p>
- <pre class="highlight plaintext"><code>import com.syncleus.aparapi.Kernel;
+ <pre class="highlight plaintext"><code>import com.aparapi.Kernel;
public class Squarer extends Kernel{
int[] in;
@@ -92,7 +92,7 @@
<pre class="highlight plaintext"><code>javap -c -classpath path/to/aparapi/aparapi.jar;. Squarer
</code></pre>
<p>Compiled from “Squarer.java”</p>
- <pre class="highlight plaintext"><code>public class Squarer extends com.syncleus.aparapi.Kernel
+ <pre class="highlight plaintext"><code>public class Squarer extends com.aparapi.Kernel
SourceFile: "Squarer.java"
minor version: 0
major version: 50
diff --git a/documentation/DevelopersGuideLinux.html b/documentation/DevelopersGuideLinux.html
index ada1072dda038da6603a4556b5470ff126671477..72735559601167f651aac7008427539d36f941da 100644
--- a/documentation/DevelopersGuideLinux.html
+++ b/documentation/DevelopersGuideLinux.html
@@ -134,7 +134,7 @@
<h2>Eclipse</h2>
- <p>Eclipse is not required to build Aparapi; however, the developers of Aparapi do use Eclipse and have made the Eclipse artifacts (.classpath and .project files) available so that projects can be imported into Eclipse. The com.syncleus.aparapi.jni subproject (containing C++ JNI source) should be imported as a resource project. We do not recommend importing com.syncleus.aparapi.jni as a CDT project, and we do not recommend trying to configure a CDT build, the existing build.xml files has been customized for multiplatform C++ compilations.</p>
+ <p>Eclipse is not required to build Aparapi; however, the developers of Aparapi do use Eclipse and have made the Eclipse artifacts (.classpath and .project files) available so that projects can be imported into Eclipse. The com.aparapi.jni subproject (containing C++ JNI source) should be imported as a resource project. We do not recommend importing com.aparapi.jni as a CDT project, and we do not recommend trying to configure a CDT build, the existing build.xml files has been customized for multiplatform C++ compilations.</p>
<h2>Building</h2>
@@ -143,43 +143,43 @@
</code></pre>
<p>Checkout provides the following:</p>
<pre class="highlight plaintext"><code>aparapi/
- com.syncleus.aparapi/
- src/java/com.syncleus.aparapi/*.java
+ com.aparapi/
+ src/java/com.aparapi/*.java
build.xml
- com.syncleus.aparapi.jni/
+ com.aparapi.jni/
src/cpp/*.cpp
src/cpp/*.h
build.xml
test/
codegen/
src/java/
- com.syncleus.aparapi/
- com.syncleus.aparapi.test/
+ com.aparapi/
+ com.aparapi.test/
build.xml
runtime/
src/java/
- com.syncleus.aparapi/
- com.syncleus.aparapi.test/
+ com.aparapi/
+ com.aparapi.test/
build.xml
samples/
mandel
- src/java/com.syncleus.aparapi.samples.mandel/*.java
+ src/java/com.aparapi.samples.mandel/*.java
build.xml
mandel.sh
mandel.bat
squares/
- src/java/com.syncleus.aparapi.samples.squares/*.java
+ src/java/com.aparapi.samples.squares/*.java
build.xml
squares.sh
squares.bat
convolution/
- src/java/com.syncleus.aparapi.samples.convolution/*.java
+ src/java/com.aparapi.samples.convolution/*.java
build.xml
conv.sh
conv.bat
examples/
nbody/
- src/java/com.syncleus.aparapi.nbody/
+ src/java/com.aparapi.nbody/
build.xml
nbody.sh
nbody.bat
@@ -190,15 +190,15 @@
</code></pre>
<h2>Sub Directories</h2>
- <p>The com.syncleus.aparapi and com.syncleus.aparapi.jni subdirectories contain the source for building and using Aparapi.</p>
+ <p>The com.aparapi and com.aparapi.jni subdirectories contain the source for building and using Aparapi.</p>
<p>The ant build.xml file, in each folder accept common ‘clean’ and 'build’ targets. You can use the build.xml file at the root of the tree for two purposes:</p>
- <pre class="highlight plaintext"><code>To initiate a build com.syncleus.aparapi of com.syncleus.aparapi.jni.
+ <pre class="highlight plaintext"><code>To initiate a build com.aparapi of com.aparapi.jni.
To create a binary ‘distribution’ directory and zip file. This zip file is same as those available from the download section of the code.google.com/p/aparapi site.
</code></pre>
<h2>Preparing for your first build</h2>
- <p>Edit com.syncleus.aparapi.jni\build.properties and ensure that the properties are valid for your platform.</p>
+ <p>Edit com.aparapi.jni\build.properties and ensure that the properties are valid for your platform.</p>
<p>View the comments in the properties file for assistance. The build.xml ant file contains some simple checks to help diagnose simple configuration errors in case something gets messed up.</p>
diff --git a/documentation/DevelopersGuideWindows.html b/documentation/DevelopersGuideWindows.html
index cc8180892795ad9374df1fb5b72a1c0dd76f43f8..1eecf6c4a2370ad0cc52105b362a82a4bdd1912e 100644
--- a/documentation/DevelopersGuideWindows.html
+++ b/documentation/DevelopersGuideWindows.html
@@ -113,7 +113,7 @@
<h2>A C++ compiler</h2>
- <p>For Microsoft® Windows® platforms the JNI build can support either Microsoft® Visual Studio® 2008, 2009 or 2010 compiler or MinGW (Minimal GNU for Windows) from GNU. Now that Visual Studio express is available for free, we would recommend using Visual studio. If you wish to use another compiler then you will have to tweak the com.syncleus.aparapi.jni/build.xml file to get your compiler to work.
+ <p>For Microsoft® Windows® platforms the JNI build can support either Microsoft® Visual Studio® 2008, 2009 or 2010 compiler or MinGW (Minimal GNU for Windows) from GNU. Now that Visual Studio express is available for free, we would recommend using Visual studio. If you wish to use another compiler then you will have to tweak the com.aparapi.jni/build.xml file to get your compiler to work.
Microsoft® Visual Studio® 2008/2010 for 32-bit or 64-bit platforms</p>
<p>Aparapi has been tested with various versions of Microsoft® Visual Studio® 2008, 2009 and 2010 including Enterprise, Professional and Express editions, if you encounter any version specific issues please let us know so we can address it and/or update this documentation.</p>
@@ -122,7 +122,7 @@
<p>And an SDK, such as. c:\Program Files\Microsoft SDKs\Windows\v6.0A</p>
- <p>Note the location of both of these as this information will be needed to configure the com.syncleus.aparapi.jni\build.property file (later).
+ <p>Note the location of both of these as this information will be needed to configure the com.aparapi.jni\build.property file (later).
For Visual Studio Express 64 bit users</p>
<p>Visual studio express does not include the 64 bit compiler or libraries. You will need to also install the SDK from Microsoft. this link should help</p>
@@ -153,7 +153,7 @@
<p>Eclipse is not required to build Aparapi, however the developers of Aparapi do use Eclipse and have made the Eclipse artifacts (.classpath and .project files) available so that projects can be imported into Eclipse.</p>
- <p>The com.syncleus.aparapi.jni subproject (containing C++ JNI source) should be imported as a resource project, we do not recommend importing com.syncleus.aparapi.jni as a CDT project, and we do not recommend trying to configure a CDT build, the existing build.xml files has been customized for multiplatform C++ compilations.</p>
+ <p>The com.aparapi.jni subproject (containing C++ JNI source) should be imported as a resource project, we do not recommend importing com.aparapi.jni as a CDT project, and we do not recommend trying to configure a CDT build, the existing build.xml files has been customized for multiplatform C++ compilations.</p>
<h2>Building</h2>
@@ -163,43 +163,43 @@
<p>You will end up with the following files/directories</p>
<pre class="highlight plaintext"><code>aparapi/
- com.syncleus.aparapi/
- src/java/com.syncleus.aparapi/*.java
+ com.aparapi/
+ src/java/com.aparapi/*.java
build.xml
- com.syncleus.aparapi.jni/
+ com.aparapi.jni/
src/cpp/*.cpp
src/cpp/*.h
build.xml
test/
codegen/
src/java/
- com.syncleus.aparapi/
- com.syncleus.aparapi.test/
+ com.aparapi/
+ com.aparapi.test/
build.xml
runtime/
src/java/
- com.syncleus.aparapi/
- com.syncleus.aparapi.test/
+ com.aparapi/
+ com.aparapi.test/
build.xml
samples/
mandel
- src/java/com.syncleus.aparapi.samples.mandel/*.java
+ src/java/com.aparapi.samples.mandel/*.java
build.xml
mandel.sh
mandel.bat
squares/
- src/java/com.syncleus.aparapi.samples.squares/*.java
+ src/java/com.aparapi.samples.squares/*.java
build.xml
squares.sh
squares.bat
convolution/
- src/java/com.syncleus.aparapi.samples.convolution/*.java
+ src/java/com.aparapi.samples.convolution/*.java
build.xml
conv.sh
conv.bat
examples/
nbody/
- src/java/com.syncleus.aparapi.nbody/
+ src/java/com.aparapi.nbody/
build.xml
nbody.sh
nbody.bat
@@ -210,17 +210,17 @@
</code></pre>
<h2>Sub Directories</h2>
- <p>The com.syncleus.aparapi and com.syncleus.aparapi.jni subdirectories contain the source for building and using Aparapi.</p>
+ <p>The com.aparapi and com.aparapi.jni subdirectories contain the source for building and using Aparapi.</p>
<p>The ant build.xml file, in each folder accept ‘clean’ and 'build’ targets.</p>
<p>Use the build.xml file at the root of the tree for two purposes:</p>
- <pre class="highlight plaintext"><code>To initiate a build of com.syncleus.aparapi and com.syncleus.aparapi.jni.
+ <pre class="highlight plaintext"><code>To initiate a build of com.aparapi and com.aparapi.jni.
To create a binary distribution directory and zip file. This zip file is same as those available from the download section of the code.google.com/p/aparapi site.
</code></pre>
<h2>Preparing for your first build</h2>
- <p>You should only need to edit com.syncleus.aparapi.jni\build.xml file if you wish to use mingw or if you Visual Studio or gcc compiler is in an unusual place.</p>
+ <p>You should only need to edit com.aparapi.jni\build.xml file if you wish to use mingw or if you Visual Studio or gcc compiler is in an unusual place.</p>
<p>Perform a build from the root directory using the following command:</p>
<pre class="highlight plaintext"><code>$ ant clean dist
diff --git a/documentation/FrequentlyAskedQuestions.html b/documentation/FrequentlyAskedQuestions.html
index 7c774d2028c7af2d599a81cf7fd8f14e0bb1f48c..fa5fc4f7211d0bbe0edfbd9bb8fe3cafbc10a40c 100644
--- a/documentation/FrequentlyAskedQuestions.html
+++ b/documentation/FrequentlyAskedQuestions.html
@@ -105,7 +105,7 @@
<h2>Is there a way I can see the generated OpenCL?</h2>
- <p>Yes, by using adding -Dcom.syncleus.aparapi.enableShowGeneratedOpenCL=true to your command line when you start your JVM.</p>
+ <p>Yes, by using adding -Dcom.aparapi.enableShowGeneratedOpenCL=true to your command line when you start your JVM.</p>
<h2>Does Aparapi support sharing buffers with JOGL? Can I exploit the features of JOGAMP/glugen?</h2>
@@ -149,7 +149,7 @@
</code></pre>
<p>The above code fragment will print either ‘GPU’ if the kernel executed on the GPU or JTP if Aparapi executed the Kernel in a Java Thread Pool.</p>
- <p>Alternatively, setting the property –Dcom.syncleus.aparapi.enableShowExecutionModes=true when you start your JVM will cause Aparapi to automatically report the execution mode of all kernels to stdout.</p>
+ <p>Alternatively, setting the property –Dcom.aparapi.enableShowExecutionModes=true when you start your JVM will cause Aparapi to automatically report the execution mode of all kernels to stdout.</p>
<h2>Why does Aparapi need me to compile my code with -g?</h2>
diff --git a/documentation/PrivateMemorySpace.html b/documentation/PrivateMemorySpace.html
index 5922790992d1dc56fe1537e07d1d5a7669b7e3ee..6c9aa9c093a9c1e8429f17e395df421e1aeb98be 100644
--- a/documentation/PrivateMemorySpace.html
+++ b/documentation/PrivateMemorySpace.html
@@ -86,7 +86,7 @@
<p>The Kernel.NoCL annotation exists to allow specialised code to be executed when running in Java (or JTP) which is not invoked when running on the GPU. A NoCL method can be inserted at the begining of a Kernel’s run() method which sets the private array to a value obtained from a static ThreadLocal<foo[]> where foo is the primitive type of the array in question. This will have no effect upon OpenCL execution, but will allow threadsafe execution when running in java.</p>
- <p>In the project samples, there is a package com.syncleus.aparapi.sample.median which gives an example of a median image filter which uses a private array of pixel data to apply a distructive median algorithm to a “window” of local pixels. This sample also demonstrates how to use the ThreadLocal trick to allow correct behaviour when running in JTP execution mode.</p>
+ <p>In the project samples, there is a package com.aparapi.sample.median which gives an example of a median image filter which uses a private array of pixel data to apply a distructive median algorithm to a “window” of local pixels. This sample also demonstrates how to use the ThreadLocal trick to allow correct behaviour when running in JTP execution mode.</p>
<p><a href="http://code.google.com/p/aparapi/source/browse/trunk/samples/median/src/com/amd/aparapi/sample/median/MedianDemo.java" rel="nofollow">http://code.google.com/p/aparapi/source/browse/trunk/samples/median/src/com/amd/aparapi/sample/median/MedianDemo.java</a></p>
</div>
diff --git a/documentation/ProfilingKernelExecution.html b/documentation/ProfilingKernelExecution.html
index 3a04557cc7e7af29cb0592dd6eb4b20a70bc6352..c0591945fc83594be616220e6b8d7d8bccc9fdb5 100644
--- a/documentation/ProfilingKernelExecution.html
+++ b/documentation/ProfilingKernelExecution.html
@@ -59,7 +59,7 @@
<p><em>Using Aparapi’s built in profiling APIs Updated May 7, 2013 by frost.g…@gmail.com</em></p>
<p>If you want to extract OpenCL performance info from a kernel at runtime you need to set the property :-</p>
- <pre class="highlight plaintext"><code>-Dcom.syncleus.aparapi.enableProfiling=true
+ <pre class="highlight plaintext"><code>-Dcom.aparapi.enableProfiling=true
</code></pre>
<p>Your application can then call kernel.getProfileInfo() after a successful call to kernel.execute(range) to extract a List List<ProfileInfo>.</p>
@@ -96,7 +96,7 @@
<p>And here is the tabular output from</p>
<pre class="highlight plaintext"><code> java
-Djava.library.path=${APARAPI_HOME}
- -Dcom.syncleus.aparapi.enableProfiling=true
+ -Dcom.aparapi.enableProfiling=true
-cp ${APARAPI_HOME}:.
MyClass
diff --git a/documentation/UnitTestGuide.html b/documentation/UnitTestGuide.html
index 2bd5ba743155b4a04aa02ada9ddb186c4a368a2a..f88bd5aedcd0387fe8162fa54410443183cf6cf3 100644
--- a/documentation/UnitTestGuide.html
+++ b/documentation/UnitTestGuide.html
@@ -65,14 +65,14 @@
<p>The initial open source tree includes the codegen subdirectory (test/codegen), which used to validate the Aparapi bytecode to OpenCLâ„¢ conversion.</p>
<pre class="highlight plaintext"><code>aparapi/trunk/
- com.syncleus.aparapi/
- src/java/com.syncleus.aparapi/
+ com.aparapi/
+ src/java/com.aparapi/
build.xml
test/
codegen/
src/java/
- com.syncleus.aparapi/
- com.syncleus.aparapi.test/
+ com.aparapi/
+ com.aparapi.test/
build.xml
build.xml
</code></pre>
@@ -80,7 +80,7 @@
<h2>Running the OpenCLâ„¢ code generation JUnit tests</h2>
- <p>Before executing the code generation tests, build the com.syncleus.aparapi sub-project and ensure that you have JUnit 4 installed.</p>
+ <p>Before executing the code generation tests, build the com.aparapi sub-project and ensure that you have JUnit 4 installed.</p>
<p>Edit the junit.jar property in test/codegen/build.xml to point to your install directory.</p>
<pre class="highlight plaintext"><code><property name="junit.jar" value="C:\JUnit4.9\junit-4.9.jar"/>
@@ -101,12 +101,12 @@
<p>The test cases for OpenCLâ„¢ code generation are not strictly JUnit tests. Instead the codegen Java tree contains a tool (CreateJUnitTests) to create JUnit test cases from specially formatted test source files.</p>
- <p>The package <code>com.syncleus.aparapi.test (codegen/src/java/com/amd/aparapi/test)</code> contains all of the existing code generation tests.</p>
+ <p>The package <code>com.aparapi.test (codegen/src/java/com/aparapi/test)</code> contains all of the existing code generation tests.</p>
- <p>Here is an example that tests the code generation resulting from a call to Kernel.getPassId(), this is taken from com.syncleus.aparapi.test.CallGetPassId</p>
- <pre class="highlight plaintext"><code>package com.syncleus.aparapi.test;
+ <p>Here is an example that tests the code generation resulting from a call to Kernel.getPassId(), this is taken from com.aparapi.test.CallGetPassId</p>
+ <pre class="highlight plaintext"><code>package com.aparapi.test;
- import com.syncleus.aparapi.Kernel;
+ import com.aparapi.Kernel;
public class CallGetPassId extends Kernel{
public void run() {
@@ -142,13 +142,13 @@
<ul>
<li>compiles the src/java tree. This compiles all the test cases as well as a few ‘utility’ classes.</li>
- <li>executes the com.syncleus.aparapi.test.CreateJUnitTests program. This iterates through all of the test source files and converts them to JUnit form. The generated source is written to the src/genjava tree.</li>
+ <li>executes the com.aparapi.test.CreateJUnitTests program. This iterates through all of the test source files and converts them to JUnit form. The generated source is written to the src/genjava tree.</li>
<li>compiles the src/genjava tree to create the required JUnit classes</li>
<li>initiates the JUnit test phase (result data in junit/data)</li>
<li>creates the JUnit report (in junit/html/junit from junit/data)</li>
</ul>
- <p>To create a new test case, just add your test case to the <code>codegen/src/java/com/amd/aparapi/test</code> package (including the expected OpenCL).</p>
+ <p>To create a new test case, just add your test case to the <code>codegen/src/java/com/aparapi/test</code> package (including the expected OpenCL).</p>
<p>Sometimes different javac implementations (such as Oracle and Eclipse) will generate different bytecode for the same source. When Aparapi converts this bytecode it may yield different (but equally acceptable) OpenCL forms. One example of this is the BooleanToggle test:</p>
<pre class="highlight plaintext"><code>public class BooleanToggle{
@@ -171,7 +171,7 @@
<p>Logically either of the above are correct. However, to accommodate the alternate acceptable forms we need to add two complete <code>/**{OpenCL{ and }OpenCL}**/</code> sections to the file. If either matches, the test will pass.</p>
<p>Here is the complete BooleanToggle code.</p>
- <pre class="highlight plaintext"><code>package com.syncleus.aparapi.test;
+ <pre class="highlight plaintext"><code>package com.aparapi.test;
public class BooleanToggle{
public void run() {
diff --git a/documentation/UsersGuide.html b/documentation/UsersGuide.html
index 929b8d60a39724312f3b2ec01379a863076ed0d3..7e6c8e8e3d3984c1404f674d710b7778d5dffbfe 100644
--- a/documentation/UsersGuide.html
+++ b/documentation/UsersGuide.html
@@ -109,7 +109,7 @@
thread.start();
thread.join();
</code></pre>
- <p>The Aparapi developer extends the com.syncleus.aparapi.Kernel and overrides the public void Kernel.run() method. It is this Kernel.run() method that is executed in parallel.</p>
+ <p>The Aparapi developer extends the com.aparapi.Kernel and overrides the public void Kernel.run() method. It is this Kernel.run() method that is executed in parallel.</p>
<p>The base class also exposes the Kernel.execute(range) method which is used to initiate the execution of Kernel.run() over the range 0…n.</p>
@@ -149,8 +149,8 @@
System.out.println(“Kernel nid not execute on the GPU!â€);
}
</code></pre>
- <p>To obtain a runtime report of the execution mode of all kernel executions, set the com.syncleus.aparapi.enableExecutionModeReporting property to true when the JVM is launched.</p>
- <pre class="highlight plaintext"><code>$ java –Djava.library.path=${APARAPI_DIR} –Dcom.syncleus.aparapi.enableExecutionModeReporting=true –cp ${APARAPI_DIR}/aparapi.jar;. Squares
+ <p>To obtain a runtime report of the execution mode of all kernel executions, set the com.aparapi.enableExecutionModeReporting property to true when the JVM is launched.</p>
+ <pre class="highlight plaintext"><code>$ java –Djava.library.path=${APARAPI_DIR} –Dcom.aparapi.enableExecutionModeReporting=true –cp ${APARAPI_DIR}/aparapi.jar;. Squares
</code></pre>
<h2>Running the sample applications</h2>
@@ -165,7 +165,7 @@
<p>Set the environment variable JAVA_HOME to point to the root of your JRE or JDK.
Change to the appropriate samples directory (samples/squares or samples/mandel)
Run either the .bat or .sh script. On Linux® , you might have to initially chmod +x script.sh to add execute permissions.
- The sample scripts pass the first arg (%1 or $1) to -Dcom.syncleus.aparapi.executionMode when the JVM is launched. This allows the sample to be tested in either GPU or JTP execution modes by passing the requested mode.</p>
+ The sample scripts pass the first arg (%1 or $1) to -Dcom.aparapi.executionMode when the JVM is launched. This allows the sample to be tested in either GPU or JTP execution modes by passing the requested mode.</p>
<pre class="highlight plaintext"><code>$ cd samples/mandel
$ bash ./mandel.sh GPU
<executes in GPU mode here>
diff --git a/documentation/UsingAparapiLambdaBranchWithHSASimulator.html b/documentation/UsingAparapiLambdaBranchWithHSASimulator.html
index 992fa939ea763d23c1f85eddea362d60b7e33828..464a9e3a09ee28e7f26d83b0edc6c1389b873b2e 100644
--- a/documentation/UsingAparapiLambdaBranchWithHSASimulator.html
+++ b/documentation/UsingAparapiLambdaBranchWithHSASimulator.html
@@ -98,7 +98,7 @@
$ cd /home/gfrost/aparapi/branches/lambda
$ ant
$ export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${OKRA}/dist/bin
- $ java -agentpath:com.syncleus.aparapi.jni/dist/libaparapi_x86_64.so -cp com.syncleus.aparapi/dist/aparapi.jar:${OKRA}/dist/okra.jar hsailtest.Squares
+ $ java -agentpath:com.aparapi.jni/dist/libaparapi_x86_64.so -cp com.aparapi/dist/aparapi.jar:${OKRA}/dist/okra.jar hsailtest.Squares
$
</code></pre>
</div>
diff --git a/documentation/UsingConstantMemory.html b/documentation/UsingConstantMemory.html
index 706f4676d95d2dfd364c8d844750e7fcf36581cc..4279beaed1680d5e8116b06474d5ef7bcf53039d 100644
--- a/documentation/UsingConstantMemory.html
+++ b/documentation/UsingConstantMemory.html
@@ -60,7 +60,7 @@
<h2>How to make use of new constant memory feature</h2>
- <p>By default all primitive arrays accessed by an Aparapi Kernel is considered global. If we look at the generated code using <code>-Dcom.syncleus.aparapi.enableShowGeneratedOpenCL=true</code> we will see that primitive arrays (such as <code>int buf[]</code>) are mapped to <code>__global</code> pointers (such as <code>__global int *buf</code>) in OpenCL.</p>
+ <p>By default all primitive arrays accessed by an Aparapi Kernel is considered global. If we look at the generated code using <code>-Dcom.aparapi.enableShowGeneratedOpenCL=true</code> we will see that primitive arrays (such as <code>int buf[]</code>) are mapped to <code>__global</code> pointers (such as <code>__global int *buf</code>) in OpenCL.</p>
<p>Although this makes Aparapi easy to use (especially to Java developers who are unfamiliar to tiered memory hierarchies), it does limit the ability of the ‘power developer’ wanting to extract more performance from Aparapi on the GPU.</p>
diff --git a/documentation/UsingLocalMemory.html b/documentation/UsingLocalMemory.html
index 3f31fd724177b7cbecd7609f70ccdd8babd7a631..5b9ba870696323c2f13b69e6c96e8416a4672a11 100644
--- a/documentation/UsingLocalMemory.html
+++ b/documentation/UsingLocalMemory.html
@@ -60,7 +60,7 @@
<h2>How to make use of new local memory feature</h2>
- <p>By default all primitive arrays accessed by an Aparapi Kernel is considered global. If we look at the generated code using -Dcom.syncleus.aparapi.enableShowGeneratedOpenCL=true we will see that primitive arrays (such as int buf[]) are mapped to _<em>global pointers (such as _</em>global int *buf) in OpenCL.</p>
+ <p>By default all primitive arrays accessed by an Aparapi Kernel is considered global. If we look at the generated code using -Dcom.aparapi.enableShowGeneratedOpenCL=true we will see that primitive arrays (such as int buf[]) are mapped to _<em>global pointers (such as _</em>global int *buf) in OpenCL.</p>
<p>Although this makes Aparapi easy to use (especially to Java developers who are unfamiliar to tiered memory hierarchies), it does limit the ability of the ‘power developer’ wanting to extract more performance from Aparapi on the GPU.</p>
diff --git a/documentation/UsingMultiDimExecutionRanges.html b/documentation/UsingMultiDimExecutionRanges.html
index 1c91283a70fb71f4abc551723a668bada53bfdcd..34eecb0ba96ef4c48dde38f9854dfb1f449dca46 100644
--- a/documentation/UsingMultiDimExecutionRanges.html
+++ b/documentation/UsingMultiDimExecutionRanges.html
@@ -60,7 +60,7 @@
<p>Aparapi now allows developers to execute over one, two or three dimensional ranges. OpenCL natively allows the user to execute over 1, 2 or 3 dimension grids via the clEnqueueNDRangeKernel() method.</p>
- <p>Initially we chose not to expose 2D or 3D ranges (Aparapi’s Kernel.execute(range) allowed only !d ranges, but following a specific request we added the notion of a Range via the new com.syncleus.aparapi.Range class.</p>
+ <p>Initially we chose not to expose 2D or 3D ranges (Aparapi’s Kernel.execute(range) allowed only !d ranges, but following a specific request we added the notion of a Range via the new com.aparapi.Range class.</p>
<p>A range is created using various static factory methods. For example to create a simple range {0..1024} we would use.</p>