OpenCL extensions handling

[Tanya Lattner]

Guy,

Are you familiar with the work that Bill is doing for encoding frontend compilation options in LLVM IR? This may be the route that should be taken for OpenCL extensions that are set during compilation and you want to record somehow. It might worth talking to him about it.
http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-January/058812.html
 
I need to look at the patch closer to provide detailed comments.. but

- Why are you setting fp_contract_disabled in the class? There is already code to handle the fp contract pragma. Is this not sufficient?
- Can you please explain your proposal for this infrastructure you are thinking of?

-Tanya



On Apr 9, 2013, at 6:04 AM, "Benyei, Guy" <guy.benyei at intel.com> wrote:

> Hi all,
> I need an option to generate metadata including the list of OpenCL extensions that were used during compilation. The current extension handling mechanism is implemented in the Sema, so it’s not accessible in CodeGen.
> Also, I’d like to create an infrastructure for OpenCL extensions that would enable us to define which extensions are supported for a given target.
> To make this possible, I used the ASTContext.
>  
> Please review.
>  
> Thanks
> <image001.png>
>  
> <opencl_extensions.patch>
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130411/27e1d63c/attachment.html>