On 08/10/2012 03:24 PM, Uros Bizjak wrote: > + (eq_attr "isa" "fma") (symbol_ref "TARGET_FMA") > + (eq_attr "isa" "fma4") > + (symbol_ref "TARGET_FMA4 && !TARGET_FMA")
Why the !TARGET_FMA for fma4? If both ISAs are enabled, I don't see why we couldn't choose from either. If they really should be mutually exclusive, then that should happen elsewhere. I do see that fma3 is one byte smaller. So in the instances where we're concerned with code size, and we have both isas, and there does happen to be output overlap with one of the inputs, then we should use fma3. But we should also not have reload generate an extra move when fma4 is available. r~
