https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083
--- Comment #4 from Maciej W. Rozycki <macro at orcam dot me.uk> --- The flag enables the use of the conditional-move operations even with hardware that has no support for such operations, hence unconditionally. Such operations, where unavailable, are then synthesized as sequences of instructions from other operations, avoiding the use of branches where they'd turn out more costly according to the `-mbranch-cost=' setting (either specified or inferred from the `-mtune=' setting in effect). Normally the compiler only enables conditional-move operations where directly provided by hardware, according to the `-march=' or `-mcpu=' options used for compilation (either specified or defaulted). The help line is too short to provide a more elaborate explanation and merely serves as a quick reminder saving one from reaching for the manual. I hope this is good enough for this purpose, but if someone has a better proposal, then please feel free to submit a patch. Or would: Enable conditional-move operations unconditionally. be preferable? Last but not least, did my explanation help with the translation?
