[Bug target/114083] Possible word play on conditional/unconditional
roland.illig at gmx dot de
gcc-bugzilla@gcc.gnu.org
Mon Mar 4 22:00:45 GMT 2024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083
--- Comment #6 from Roland Illig <roland.illig at gmx dot de> ---
(In reply to Maciej W. Rozycki from comment #4)
> The flag enables the use of the conditional-move operations even with
> hardware that has no support for such operations, hence unconditionally.
Thank you for your explanation, that made the intention much clearer to me.
There's a problem with the wording though. On a platform that doesn't support
conditional-move operations, it's not possible to _use_ conditional-move
operations. Period. It's only possible to _emulate_ the behavior of these
operations.
I'm not sure how consistently the words 'operation' and 'instruction' are used
in the GCC code base and documentation, but I mixed them up in my mind when I
tried to translate this option.
> if someone has
> a better proposal, then please feel free to submit a patch. Or would:
>
> Enable conditional-move operations unconditionally.
>
> be preferable?
No. Above, you wrote that the branchless instructions would be selected _if_
they are cheaper than the equivalent branch instructions. This is a condition,
thus the word 'unconditionally' doesn't fit.
What about this?
> Prefer branchless move instructions where cheaper.
More information about the Gcc-bugs
mailing list