search for: fpoptions

Hi, clang deals with #pragma STDC FP_CONTRACT and updates the setting of FPOptions::fp_contract, but how is this made use of in the back end? Is there some way to find out, for any given pair of floating-point operations, whether they can be contracted into one (according to their local pragma settings), or is this not yet implemented? Al -- IMPORTANT NOTICE: The contents of th...

...#39;t guess that since the -ffast-math option > would be compilation wide. fp_contract provides a very similar set of language features, with both a global flag and a #pragma that can be used at either global or local scope to control semantics thenceforth. We handle that in the AST by storing FPOptions on individual arithmetic expressions, and IRGen propagates that to the individual LLVM instructions it creates. I think that's still the right representation for the AST here, and in fact the way fp_contract implemented means that your job at the Sema will be very easy. The only difference is...

Hi Kevin, Thanks for reaching out about this, and thanks especially for offering to help. I've had some other priorities that have prevented me from making progress on this recently. As far as I know, there is no support at all in clang for handling the FENV_ACCESS pragma. I have a sample patch somewhere that I created to demonstrate how the front end would create the constrained intrinsics

> On Mar 16, 2017, at 4:04 PM, Adam Nemet via cfe-dev <cfe-dev at lists.llvm.org> wrote: > >> >> On Mar 16, 2017, at 3:25 PM, Hal Finkel <hfinkel at anl.gov <mailto:hfinkel at anl.gov>> wrote: >> >> >> >> On 03/16/2017 04:13 PM, Adam Nemet wrote: >>> >>>> On Mar 15, 2017, at 2:51 PM, Adam Nemet <anemet at