browndeer
commented
10 years ago Thanks. Fortunately there is a place where flags are blocked. I believe this can be addressed at that point.
Sent via BlackBerry by AT&T
-----Original Message----- From: sctincman notifications@github.com Date: Fri, 27 Jun 2014 12:40:38 To: browndeer/coprthrcoprthr@noreply.github.com Reply-To: browndeer/coprthr reply@reply.github.com Subject: [coprthr] libcoprthr_opencl: OpenCL specific compiler flags interupt build and crash in elfcl routines (#21)
If an application passes in OpenCL specific compiler flags when using libcoprthr_opencl (such as "-cl-strict-aliasing" or any of the ones listed here https://www.khronos.org/registry/cl/sdk/1.0/docs/man/xhtml/clBuildProgram.html), these will be passed straight to gcc/g++, which will throw an "unrecognized option" error and not output the needed program.
This seems to result in an empty elf file that causes elfcl_write to signal SIGABRT from malloc (at least from my cursory backtraces and stracing).
Reply to this email directly or view it on GitHub: https://github.com/browndeer/coprthr/issues/21
If an application passes in OpenCL specific compiler flags when using libcoprthr_opencl (such as "-cl-strict-aliasing" or any of the ones listed here https://www.khronos.org/registry/cl/sdk/1.0/docs/man/xhtml/clBuildProgram.html), these will be passed straight to gcc/g++, which will throw an "unrecognized option" error and not output the needed program.
This seems to result in an empty elf file that causes elfcl_write to signal SIGABRT from malloc (at least from my cursory backtraces and stracing).