From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Alexandre Oliva <oliva@adacore.com>, gcc-patches@gcc.gnu.org
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Mike Stump <mikestump@comcast.net>
Subject: Re: [PATCH] [PR42093] [arm] [thumb2] disable tree-dce for test
Date: Thu, 12 Jan 2023 14:43:31 +0000 [thread overview]
Message-ID: <952ddb74-52e8-42f1-bad3-c07e3adc8c7f@foss.arm.com> (raw)
In-Reply-To: <orsfhyxik0.fsf@lxoliva.fsfla.org>
On 02/12/2022 09:26, Alexandre Oliva via Gcc-patches wrote:
>
> CD-DCE introduces blocks to share common PHI nodes, which replaces a
> backwards branch that used to prevent the thumb2 jump table shortening
> that PR42093 tested for. In order to keep on testing that the
> backward branch prevents the jumptable shortening, disable tree-dce.
>
> Regstraped on x86_64-linux-gnu, also tested with crosses to riscv64-elf
> and arm-eabi. Ok to install?
>
> > for gcc/testsuite/ChangeLog
>
> PR target/42093
> * gcc.target/arm/pr42093.c: Disable tree-dce.
OK.
R.
> ---
> gcc/testsuite/gcc.target/arm/pr42093.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.target/arm/pr42093.c b/gcc/testsuite/gcc.target/arm/pr42093.c
> index 7ba2f933eef81..69b1470607c7f 100644
> --- a/gcc/testsuite/gcc.target/arm/pr42093.c
> +++ b/gcc/testsuite/gcc.target/arm/pr42093.c
> @@ -1,4 +1,4 @@
> -/* { dg-options "-mthumb -O2 -fno-reorder-blocks" } */
> +/* { dg-options "-mthumb -O2 -fno-reorder-blocks -fno-tree-dce" } */
> /* { dg-require-effective-target arm_thumb2_ok } */
> /* { dg-final { scan-assembler-not "tbb" } } */
> /* { dg-final { scan-assembler-not "tbh" } } */
>
prev parent reply other threads:[~2023-01-12 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 9:26 Alexandre Oliva
2023-01-12 14:43 ` Richard Earnshaw [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=952ddb74-52e8-42f1-bad3-c07e3adc8c7f@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=ro@CeBiTec.Uni-Bielefeld.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).