search for: getfaststring

...tDefaultFPMathTag(MDNode *FPMathTag) { DefaultFPMathTag = FPMathTag; } This should be 'setDefault...' much like 'getDefault...' above. + Instruction *AddFPMathTag(Instruction *I, MDNode *FPMathTag) const { Another bad case, but I think this instruction is gone... + MDString *GetFastString() const { + return CreateString("fast"); + } 'getFastString'. + /// CreateFastFPMath - Return metadata with appropriate settings for 'fast + /// math'. I would prefer the more modern doxygen style: /// \brief Return metadata ... + MDNode *CreateFastFP...

...ing to be consistent here. > > + Instruction *AddFPMathTag(Instruction *I, MDNode *FPMathTag) const { > > Another bad case, but I think this instruction is gone... It still exists, and is also capitalized like that for consistency with the rest of IRBuilder. > > + MDString *GetFastString() const { > + return CreateString("fast"); > + } > > 'getFastString'. OK, done - same for the others that are not in IRBuilder. > + /// CreateFastFPMath - Return metadata with appropriate settings for 'fast > + /// math'. > > I would...

Here's a revised patch, plus patches showing how fpmath metadata could be turned on in clang and dragonegg (it seemed safest for the moment to condition on -ffast-math rather than on one of the flags implied by -ffast-math). Major changes: - The FPMathOperator class can no longer be used to change math settings, only to read them. Currently it can be queried for accuracy info. I split the

The attached patch is a first attempt at representing "-ffast-math" at the IR level, in fact on individual floating point instructions (fadd, fsub etc). It is done using metadata. We already have a "fpmath" metadata type which can be used to signal that reduced precision is OK for a floating point operation, eg %z = fmul float %x, %y, !fpmath !0 ... !0 = metadata