| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Increase buffer size and rewind before reuse in every possible
place. This is to try to remove a couple of remaining failures on
some platforms. The failure causes an abnormal JVM exit without
a stack trace when System.gc() is called during teardown.
|
|
|
|
| |
Fixes transposed arguments in CLCommandQueue:putCopyBufferRect.
|
|
|
|
|
|
|
|
|
|
|
| |
programBinariesTest() failure was due to AMD drivers crashing
in clCreateKernelsInProgram() when the program is not built yet,
instead of returning error code CL_INVALID_PROGRAM_EXECUTABLE as they
should.
lowLevelVectorAddTest() failure was apparently due to the AMD drivers
writing past the end of a direct byte buffer in such a way that it made
System.gc() crash when called during teardown (this crash didn't even
dump stack). Making the buffer larger solved the problem.
|
|
|
|
|
|
| |
Remove all Java lint warnings, by fixing the code if possible, and if
not possible then by inserting @SuppressWarnings. Some of these
@SuppressWarnings can be replaced later with @SafeVarargs if we
eventually drop support for Java 6.
|
|
|
|
|
|
|
| |
Removed warnings due to memoryMaximumSize being ignored when javac isn't
forked. Turned on all linting. Changed the arguments of
uncomment-function-params so it will run from within Eclipse properly
(using basedir instead of user.dir, since only the former will be
properly set both inside Eclipse and on the command line).
|
|
|
|
|
|
|
|
| |
Turns off the warning about CL_ALIGNED not being
defined for the current compiler, but only inside
the gluegen preprocessor. If CL_ALIGNED isn't
defined for the real C compiler on the platform,
the warning will still show up during C compilation.
|
|
|
|
| |
Uses the new augmentation of gluegen's Ignore keyword.
|
|
|
|
|
|
|
| |
These pointers were showing up as uninitialized variables; on inspection
they just weren't being passed in from the Java side or assigned on
the C side. There are currently no tests of this function, which is how
we didn't notice this omission.
|
|
|
|
| |
This lets us build with debug information turned on.
|
|
|
|
|
|
| |
Fixes -fno-rtti and implicit cast warnings. After this commit,
all C warnings are gone except for one due to gluegen emitting
char pointers instead of unsigned char pointers.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The new OpenCL isAvailable() didn't make it into this test due to
a merge slipup.
Change-Id: I049388908b8f2f2869cc018dbf6be86d1a8dcb9d
|
| |\ |
|
|\ \ \
| |/ /
|/| /
| |/ |
Fix OpenCL test failures on Solaris for bug 978.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since nobody currently makes an OpenCL driver for Solaris, all the
tests used to fail, which told us nothing. This commit adds code
to check whether OpenCL is unavailable and the OS is Solaris, in
which case the test contents are skipped. If an OpenCL driver ever
appears for Solaris, or if we start testing on another platform
with no OpenCL driver, there's now one single place to add or remove
checks that will allow for this.
|
|\ \
| | |
| | |
| | | |
'wwalker/fix_jocl_bug_981_out_of_direct_buffer_memory'
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These tests now adaptively reduce the global work size until they
successfully allocate memory for their DirectByteBuffers. This
makes the tests work on JVMs where XX:MaxDirectMemorySize is
smaller than the modern defaults. These tests were failing on
OS X 10.6 for this reason.
|
| | |
| | |
| | |
| | |
| | |
| | | |
decorations to remove warnings.
Note 'static import' is evil .. :)
|
| | |
| | |
| | |
| | |
| | |
| | | |
to CLContext - Split CLBufferTest and use alignment.
See Bug 979 for remaining issues and discussion.
|
| | |
| | |
| | |
| | |
| | |
| | | |
generate.jdk7.autocloseable' in java.generate.impl
Regression of commit 46cc6ebfb2f53daebceb9a36b553ff01af56999f
|
| | |
| | |
| | |
| | | |
uptodate (use java.generate.skip); Put native code on gensrc/native/jocl
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All gluegen generated native function wrappers,
miss CL_API_CALL in the function declarations
similar to commit 569726132f622e290bebc5d40c96f8115dbcb5da.
Adding gluegen calling convention to cl-impl.cfg:
LocalProcAddressCallingConvention __ALL__ CL_API_CALL
All tests passed on windows 32bit now!
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The 'clGetExtensionFunctionAddress' function pointer declaration was faulty,
i.e. using CL_API_ENTRY instead of CL_API_CALL.
CL_API_CALL on windows is defined as '__stdcall' which impacts Window 32bit platforms.
Fixed same issue w/:
- clCreateContext
- clBuildProgram
Same issue occurs with _all_ gluegen generated native function wrappers,
i.e. CL_API_CALL is missing in the function declarations!
I will follow-up w/ this fix in a bit ..
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix copy2temp target and issue it before gluegen of cl-if.cfg.
Note: ${project.root}/build cannot be a hard-dependency since
${rootrel.build} is configurable hence
${project.root}/${rootrel.build}.
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|/
|
|
|
|
|
|
| |
This commit fixes bugs 959 (local work size set incorrectly),
960 (concurrencyTest() throws ConcurrentModificationException)
963 (programBinariesTest() causes SIGSEGV) and 964 (builderTest()
cases CL_INVALID_VALUE). After this commit, all JOCL tests should
pass on 64-bit Mac OS X.
|
| |
|
|
|
|
| |
package location (sorry)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(make) due to relative fileset access only!
Commit aac4c5fc4ab7c77eff3b71f518100dd182ec2c33 moved processed CL stub_includes
to 'build/includes', which would be 'nice to have'.
However, due to relative fileset restrictions, we must locate it from current folder 'make'.
Not detected, since an old 'make/includes/CL' was still around.
Using dedicated folder 'make/stub_includes.gen'.
|
| |
|
|
|
|
| |
Added main entry and listed in tests.sh for manual test.
|
|
|
|
| |
tests ; Fix setenv-jocl.sh: Add jocl-test.jar
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
JoclVersionActivity
Cleanup Build:
- Move gluegen config files into make/config (cleanup)
- Move stub_includes into respective folder make/stub_includes
and keep resources 'clean'
JoclVersion:
- Analoge to JoglVersion, replaces JOCLVersion (deprecated for now)
- Added text based CL info dump.
JoclVersionActivity:
- Analog to JoclVersionActivity
- Added full launch .. tested on Android (but no OpenCL avail.)
|
|
|
|
| |
rootrel.build (as gluegen does)
|
|
|
|
| |
and apk files in ${build}/jar (as it was before new build system)
|
| |
|
|
|
|
| |
file suffix ; Fix Jar Manifest: Move Sealed to bottom.
|
|\
| |
| |
| | |
'wwalker/bug_884_replace_netbeans_build_with_jogamp_standard_build'
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new make/build.xml successfully builds and tests the project. The
original NetBeans build files are still present, but won't work anymore
since the resources directory is now inside the make directory. The new
build files are based on those of JOAL. The new build is not yet minimized
and cleaned up, because this commit is meant to be the minimum way to get
things functional.
|
|/
|
|
| |
duh), add 'Application-Library-Allowable-Codebase: *'
|
|
|
|
| |
'gluegen-xcode_clang.properties' for OSX xcode-clang ; Add GNU/Linux LLVM/clang build scripts
|
| |
|
| |
|
| |
|