public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Roger Sayle <sayle@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-7506] [Committed] Update gcc.dg/lower-subreg-1.c on ia32.
Date: Sun,  6 Mar 2022 11:06:46 +0000 (GMT)	[thread overview]
Message-ID: <20220306110646.081D73858D1E@sourceware.org> (raw)

https://gcc.gnu.org/g:98cd717fca9f21625b9c79c9231c2e909d1d93a3

commit r12-7506-g98cd717fca9f21625b9c79c9231c2e909d1d93a3
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Sun Mar 6 11:03:00 2022 +0000

    [Committed] Update gcc.dg/lower-subreg-1.c on ia32.
    
    This updates gcc.dg/lower-subreg-1.c to reflect that the i386 backend now
    lowers iordi3 itself, rather than relying on the middle-end's subreg1 pass.
    Committed as obvious.
    
    2022-03-06  Roger Sayle  <roger@nextmovesoftware.com>
    
    gcc/testsuite/ChangeLog
            * gcc.dg/lower-subreg-1.c: Update test case.  iordi3 is no longer
            lowered by the RTL subreg1 pass on ia32 [even with -mno-stv].

Diff:
---
 gcc/testsuite/gcc.dg/lower-subreg-1.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/lower-subreg-1.c b/gcc/testsuite/gcc.dg/lower-subreg-1.c
index 63a47106e27..8462992c7b9 100644
--- a/gcc/testsuite/gcc.dg/lower-subreg-1.c
+++ b/gcc/testsuite/gcc.dg/lower-subreg-1.c
@@ -1,7 +1,5 @@
-/* { dg-do compile { target { ! { mips64 || { aarch64*-*-* arm*-*-* ia64-*-* sparc*-*-* tilegx-*-* } } } } } */
+/* { dg-do compile { target { ! { mips64 || { aarch64*-*-* arm*-*-* i?86-*-* ia64-*-* sparc*-*-* tilegx-*-* x86_64-*-* } } } } } */
 /* { dg-options "-O -fdump-rtl-subreg1" } */
-/* { dg-additional-options "-mno-stv" { target ia32 } } */
-/* { dg-skip-if "" { { i?86-*-* x86_64-*-* } && x32 } } */
 /* { dg-require-effective-target ilp32 } */
 
 long long test (long long a, long long b) { return a | b; }


                 reply	other threads:[~2022-03-06 11:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220306110646.081D73858D1E@sourceware.org \
    --to=sayle@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).