public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [PR42093] [arm] [thumb2] disable tree-dce for test
Date: Sat,  3 Dec 2022 07:33:03 +0000 (GMT)	[thread overview]
Message-ID: <20221203073303.EBD31385842A@sourceware.org> (raw)

https://gcc.gnu.org/g:328d9cf03dd2ad6c469478d2099f5eb16dbe617a

commit 328d9cf03dd2ad6c469478d2099f5eb16dbe617a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Fri Dec 2 03:28:05 2022 -0300

    [PR42093] [arm] [thumb2] disable tree-dce for test
    
    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.
    
    
    for  gcc/testsuite/ChangeLog
    
            PR target/42093
            * gcc.target/arm/pr42093.c: Disable tree-dce.

Diff:
---
 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 7ba2f933eef..69b1470607c 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" } } */

             reply	other threads:[~2022-12-03  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03  7:33 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-01  7:40 Alexandre Oliva

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=20221203073303.EBD31385842A@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@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).