From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>, Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Introduce --param logical-op-non-short-circuit (PR testsuite/85368)
Date: Fri, 30 Nov 2018 23:15:00 -0000 [thread overview]
Message-ID: <878260c2-9bc9-164f-460d-d0ab62952b94@redhat.com> (raw)
In-Reply-To: <20181130205036.GG12380@tucnak>
On 11/30/18 1:50 PM, Jakub Jelinek wrote:
> Hi!
>
> Until we stop depending on BRANCH_COST and LOGICAL_OP_NON_SHORT_CIRCUIT
> macros at least for early GIMPLE, I'm afraid the current state for the
> testsuite is terrible, on some targets it is enough to use
> -mbranch-cost={1,2} to pick either of the setting, but other targets,
> while they implement -mbranch-cost=, redefine LOGICAL_OP_NON_SHORT_CIRCUIT,
> so it ignores BRANCH_COST altogether, or sometimes, other targets don't
> implement -mbranch-cost= and have various complex definitions of BRANCH_COST
> or LOGICAL_OP_NON_SHORT_CIRCUIT depending on other command line options.
>
> The following patch introduces a new param (not an option, to make it
> clearer it is intended primarily for the testsuite and we can more easily
> remove it again) that overrides the target's LOGICAL_OP_NON_SHORT_CIRCUIT
> and adjusts the testsuite to use it.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, Christophe has kindly
> tested it on ARM. Ok for trunk?
>
> 2018-11-30 Jakub Jelinek <jakub@redhat.com>
>
> PR testsuite/85368
> * params.def (PARAM_LOGICAL_OP_NON_SHORT_CIRCUIT): New param.
> * tree-ssa-ifcombine.c (ifcombine_ifandif): If
> --param logical-op-non-short-circuit is present, override
> LOGICAL_OP_NON_SHORT_CIRCUIT value from the param.
> * fold-const.c (fold_range_test, fold_truth_andor): Likewise.
>
> * lib/target-supports.exp (logical_op_short_circuit): Remove.
> * gcc.dg/builtin-bswap-7.c: Remove logical_op_short_circuit
> effective target, drop -mbranch-cost= options from the test and
> instead pass --param logical-op-non-short-circuit=0 or
> --param logical-op-non-short-circuit=1 depending on what the
> tests meant to test.
> * gcc.dg/pr21643.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-ccmp-2.c: Likewise.
> * gcc.dg/tree-ssa/phi-opt-11.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-ccmp-1.c: Likewise.
> * gcc.dg/tree-ssa/ssa-dom-thread-4.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-ccmp-3.c: Likewise.
> * gcc.dg/tree-ssa/ssa-thread-14.c: Likewise.
> * gcc.dg/tree-ssa/vrp47.c: Likewise.
> * gcc.dg/tree-ssa/ssa-dom-thread-11.c: Likewise.
> * gcc.dg/tree-ssa/ssa-dom-thread-16.c: Likewise.
> * gcc.dg/tree-ssa/ssa-dom-thread-14.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-ccmp-5.c: Likewise.
> * gcc.dg/tree-ssa/vrp87.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-ccmp-6.c: Likewise.
> * gcc.dg/tree-ssa/phi-opt-2.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-13.c: Likewise.
> * gcc.dg/tree-ssa/ssa-thread-11.c: Likewise.
> * gcc.dg/tree-ssa/ssa-ifcombine-ccmp-4.c: Likewise.
> * gcc.dg/tree-ssa/forwprop-28.c: Likewise.
> * gcc.dg/binop-xor1.c: Likewise.
> * gcc.dg/pr46309.c: Likewise.
> * gcc.dg/tree-ssa/ssa-dom-thread-18.c: New test.
> * gcc.dg/tree-ssa/reassoc-32.c: Add
> --param logical-op-non-short-circuit=1 to dg-options.
> * gcc.dg/tree-ssa/reassoc-33.c: Likewise.
> * gcc.dg/tree-ssa/reassoc-34.c: Likewise.
> * gcc.dg/tree-ssa/reassoc-35.c: Likewise.
> * gcc.dg/tree-ssa/reassoc-36.c: Likewise.
OK.
Jeff
prev parent reply other threads:[~2018-11-30 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 20:50 Jakub Jelinek
2018-11-30 23:15 ` Jeff Law [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=878260c2-9bc9-164f-460d-d0ab62952b94@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).