Displaying 2 results from an estimated 2 matches for "no_reorder".
2010 Jan 15
0
[LLVMdev] Presenting Unsafe Math Flag to Optimizer
...9;exact_precision' bit
3) exceptions, you might need to have the right number of exceptions
triggered in the right order so basically no optimizations are allowed.
- this can be represented with a 'trapping_math' and/or 'signaling_NaN' bit,
or maybe it can be encoded as 'no_reorder' 'no_duplicate'
see:
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Optimize-Options.html (look
for -ffloat-store)
http://msdn.microsoft.com/en-us/library/e7s85ffb.aspx (Title: /fp (Specify
Floating-Point Behavior))
- Morten
2010 Jan 14
2
[LLVMdev] Presenting Unsafe Math Flag to Optimizer
On Jan 14, 2010, at 2:01 AM, Duncan Sands wrote:
> Hi Bill,
>
>> The current implementation of the "allow unsafe math" option is to
>> specify it via the TargetOptions object. However, this prevents the
>> target-independent optimizer from using it. Are there any opinions
>> (ha!) on how this could be achieved in a nice clean manner which
>>