search for: optimizartions

I'm not aware of any additional bits needed. But putting us right at the edge leaves me uncomfortable. So an implementation that isn't limited by the 7 bits in SubclassOptionalData seems sensible. Thanks, -Warren From: Sanjay Patel [mailto:spatel at rotateright.com] Sent: Monday, October 2, 2017 12:06 AM To: Ristow, Warren Cc: Hal Finkel; llvm-dev at lists.llvm.org Subject: Re:

...). Check out the implementation of TargetLoweringBase::getRecipEstimateSqrtEnabled to see how it's setup in backend. This is, however, per function, so we don't currently have a per-operation control on this. > > The OpenCL spec defines a number of compile flags controlling > optimizartions. Some seem to map well onto the flags already discussed > here: > > -cl-mad-enable > -cl-no-signed-zeros > -cl-finite-math-only > > However it looks to me that the following ones don't presently map > well to LLVM: > > -cl-unsafe-math-optimizations > Allow opt...