From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 1474E385841A; Fri, 23 Feb 2024 22:33:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1474E385841A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1708727605;
	bh=T/maBDzdO6OaVl1AGf3gMlOqSMjt0JG3wO9QojABnJ0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=fxqxBjOcVkjkMU83wdAleebVSAVk1/BMN91rwUqUs7SAFD6WlTOspS7HlfVAv61O1
	 WSiOJ5Wmf/ysZaeRzCGbW+OtsAHBZ0wSCdTMMv8FKbg8++LGCv5h91ngrkuqr+pxbb
	 gBtW/WjdvtqZE4AC6bd7YptcAD03tuBzFwJuOFaE=
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: Fri, 23 Feb 2024 22:33:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: macro at orcam dot me.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114083-4-hcNQhjC9yV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114083-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114083-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- 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=3D' setting
(either specified or inferred from the `-mtune=3D' setting in effect).

Normally the compiler only enables conditional-move operations where
directly provided by hardware, according to the `-march=3D' or `-mcpu=3D'
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?=