public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "macro at orcam dot me.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114083] Possible word play on conditional/unconditional
Date: Wed, 06 Mar 2024 22:15:38 +0000	[thread overview]
Message-ID: <bug-114083-4-6ogFADdosY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114083-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083

--- Comment #7 from Maciej W. Rozycki <macro at orcam dot me.uk> ---
(In reply to Roland Illig from comment #6)
> 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.
There's just too much implementer's speak in the option description
here.  Sorry about this.

What the option internally enables it is a set of named RTL machine
description patterns that implement the respective conditional-move
operations.  So in terms of RTL the operations are indeed available
unconditionally.  But I guess the compiler's internal representation
is less of an interest from the user's point of view.

What do you think of Andreas's suggestion for the English wording?

      parent reply	other threads:[~2024-03-06 22:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 19:48 [Bug target/114083] New: " roland.illig at gmx dot de
2024-02-23 19:56 ` [Bug target/114083] " pinskia at gcc dot gnu.org
2024-02-23 20:13 ` roland.illig at gmx dot de
2024-02-23 20:51 ` redi at gcc dot gnu.org
2024-02-23 22:33 ` macro at orcam dot me.uk
2024-02-24  9:36 ` schwab@linux-m68k.org
2024-03-04 22:00 ` roland.illig at gmx dot de
2024-03-06 22:15 ` macro at orcam dot me.uk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-114083-4-6ogFADdosY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).