Added AMD SDK 2.9 as a testsuite
Merge branch 'master' of ssh://github.com/pocl/pocl
Pass _CL_DISABLE_LONG via API mode too.
The affected devices, basic and pthread, check the result of ./configure,
and set a flag in _cl_device that is then checked when building the clang compilation.

However, with this setup, clang reports:
clang: warning: argument unused during compilation: '-D _CL_DISABLE_LONG'
but compiles the kernels just fine. Removing the _CL_DISABLE_LONG causes the static
assert (sizeof(long)!=8).
LLVM API mode: disable the automated libcall generation.
Allow overriding llc's detected host CPU.
Mangle 'armv7l' away from clang flags. Clang still doesn't recognize it.
Update host kernel file name to match the mangled hostname.
Auto-detect whether string literals are const char* or constant char*
Update declaration and definition of printf; implement in C instead of OpenCL C
Pass string literals as constant char* in test cases (for modern Clang versions)
Auto-detect how string literals are handled in the kernels to avoid having to rely on configure
Do not use attribute((format)) for the libc printf; there are slight differences in the meaning of the format string
Phase out OCL_KERNEL_TARGET; use llc_triple instead

This makes —enable-llvmapi work on OS X.
Do not use attribute((format)) with printf

Clang doesn’t support the OpenCL C format specifiers yet.
Use OCL_KERNEL_TARGET instead of HOST in scripts

This corrects a build problem with standalone.in with llvm 3.4.
Update Vecmathlib from upstream

I pushed changes made to pocl’s Vecmathlib copy upstream first.
Fix workgroup tests that declared an incompatible printf().
LLVM 3.4: all except 'block', 'bfs/PB', and 'lbm/PB' now pass.
Clang 3.4 adds a new diagnostics that correctly detects a typo in a macrodefine in lbm/PB. Ignore it.
Marked XFAILs (two of them) for LLVM 3.4. Now the suite passes for LLVM 3.4.
Added AMD SDK 2.9 testsuite nad bugfix to clFinish