[cfe-dev] [OpenCL] Turn on -fblocks by default for OpenCL 2.0

[Anastasia Stulova via cfe-dev]

Yes, the blocks issue has to be sorted indeed.

I don't feel strongly about the vector types as it's rather useful than necessary to define them in Clang I think.

Thanks,
Anastasia

From: Bader, Alexey [mailto:alexey.bader at intel.com]
Sent: 12 May 2016 11:12
To: Liu, Yaxun (Sam); cfe-dev (cfe-dev at lists.llvm.org); Anastasia Stulova; Pan, Xiuli
Subject: RE: [OpenCL] Turn on -fblocks by default for OpenCL 2.0

Hi Sam,

Enabling blocks for OpenCL 2.0 by default makes sense to me.
I think it would be useful to define built-in vector types for OpenCL too. Right now they are defined in the header file.

Thanks,
Alexey

From: Liu, Yaxun (Sam) [mailto:Yaxun.Liu at amd.com]
Sent: Wednesday, May 11, 2016 9:51 PM
To: cfe-dev (cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>) <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>>; 'anastasia.stulova at arm.com' <anastasia.stulova at arm.com<mailto:anastasia.stulova at arm.com>>; Pan, Xiuli <xiuli.pan at intel.com<mailto:xiuli.pan at intel.com>>; Bader, Alexey <alexey.bader at intel.com<mailto:alexey.bader at intel.com>>
Subject: [OpenCL] Turn on -fblocks by default for OpenCL 2.0

OpenCL 2.0 supports blocks as core feature. However, Clang does not turn on blocks support by default for OpenCL 2.0. An option -fblocks has to be used to turn on blocks.

Should this be changed?

Thanks.

Sam

--------------------------------------------------------------------
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
Russian Federation

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160512/c2f04514/attachment.html>