Changes

Windows build scripts: Bump ant to 1.8.2

Fix build.xml: Remove gluegen config dependency on ../build using build-temp

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}.

Fix windows test scripts (CP, D_ARGS, ..)

Fix Bug 920 - JOCL does not work on windows with 32 bit vm (1/2)

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 Bug 920 - JOCL does not work on windows with 32 bit vm (2/2)

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!

build.xml: Don't re-generate source (gluegen) if CLAbstractImpl_JNI.c uptodate (use java.generate.skip); Put native code on gensrc/native/jocl

Fix build.xml (regression): Re-activate 'generate.jdk6.autocloseable, generate.jdk7.autocloseable' in java.generate.impl

Regression of commit 46cc6ebfb2f53daebceb9a36b553ff01af56999f

Bug 979: Add 'CL_DEVICE_MEM_BASE_ADDR_ALIGN' to CLDevice and overal maximum to CLContext - Split CLBufferTest and use alignment.

See Bug 979 for remaining issues and discussion.

Minor editing: Remove static imports, using 'final' add some '@XXX' decorations to remove warnings.

Note 'static import' is evil .. :)

Fix memory problems in High/LowLevelBindingTests.

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.