diff options
| author | Tom Stellard <thomas.stellard@amd.com> | 2013-10-10 19:08:51 +0000 |
|---|---|---|
| committer | Tom Stellard <thomas.stellard@amd.com> | 2013-10-10 19:08:51 +0000 |
| commit | 6c7b86c1061994c07c9a0dc608f979b3a10fa9da (patch) | |
| tree | 0bc0ed8b6dc5ef1ef103b73fb3ad5369f2384b79 /libclc/configure.py | |
| parent | e36e9dec65626dcf54eb0ec2ac1bef6fd605a8f0 (diff) | |
| download | bcm5719-llvm-6c7b86c1061994c07c9a0dc608f979b3a10fa9da.tar.gz bcm5719-llvm-6c7b86c1061994c07c9a0dc608f979b3a10fa9da.zip | |
Implement nextafter() builtin
There are two implementations of nextafter():
1. Using clang's __builtin_nextafter. Clang replaces this builtin with
a call to nextafter which is part of libm. Therefore, this
implementation will only work for targets with an implementation of
libm (e.g. most CPU targets).
2. The other implementation is written in OpenCL C. This function is
known internally as __clc_nextafter and can be used by targets that
don't have access to libm.
llvm-svn: 192383
Diffstat (limited to 'libclc/configure.py')
| -rwxr-xr-x | libclc/configure.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libclc/configure.py b/libclc/configure.py index 1a986475ab2..dbb578bbdb6 100755 --- a/libclc/configure.py +++ b/libclc/configure.py @@ -145,6 +145,7 @@ for target in targets: clang_bc_flags = "-target %s -I`dirname $in` %s " \ "-Dcl_clang_storage_class_specifiers " \ "-Dcl_khr_fp64 " \ + "-D__CLC_INTERNAL " \ "-emit-llvm" % (target, clang_cl_includes) if device['gpu'] != '': clang_bc_flags += ' -mcpu=' + device['gpu'] |
