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)] [arm] avoid aes-1742098 mitigation in combine tests
Date: Wed, 22 Feb 2023 14:49:38 +0000 (GMT)	[thread overview]
Message-ID: <20230222144938.57A9A3858436@sourceware.org> (raw)

https://gcc.gnu.org/g:8ed45ba9fc761713acaff114efd881eda7c17c06

commit 8ed45ba9fc761713acaff114efd881eda7c17c06
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Feb 16 06:52:25 2023 -0300

    [arm] avoid aes-1742098 mitigation in combine tests
    
    The expected asm output for aes-fuse-[12].c does not correspond to
    that which is generated when -mfix-cortex-a57-aes-1742098 is enabled.
    The mitigation was introduced after the test, and enabled by default
    for the selected processor, a72.  Select a53 instead, where the
    migitation is not enabled by default, and all the expected fusions can
    take place.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.target/arm/aes-fuse-1.c: Switch to -mcpu=cortex-a53.
            * gcc.target/arm/aes-fuse-2.c: Likewise.

Diff:
---
 gcc/testsuite/gcc.target/arm/aes-fuse-1.c | 2 +-
 gcc/testsuite/gcc.target/arm/aes-fuse-2.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.target/arm/aes-fuse-1.c b/gcc/testsuite/gcc.target/arm/aes-fuse-1.c
index 27b08aeef7b..a1bbe054e0a 100644
--- a/gcc/testsuite/gcc.target/arm/aes-fuse-1.c
+++ b/gcc/testsuite/gcc.target/arm/aes-fuse-1.c
@@ -1,7 +1,7 @@
 /* { dg-do compile } */
 /* { dg-require-effective-target arm_crypto_ok } */
 /* { dg-add-options arm_crypto } */
-/* { dg-additional-options "-mcpu=cortex-a72 -O3 -dp" } */
+/* { dg-additional-options "-mcpu=cortex-a53 -O3 -dp" } */
 
 #include <arm_neon.h>
 
diff --git a/gcc/testsuite/gcc.target/arm/aes-fuse-2.c b/gcc/testsuite/gcc.target/arm/aes-fuse-2.c
index 1266a287531..ede3237ce26 100644
--- a/gcc/testsuite/gcc.target/arm/aes-fuse-2.c
+++ b/gcc/testsuite/gcc.target/arm/aes-fuse-2.c
@@ -1,7 +1,7 @@
 /* { dg-do compile } */
 /* { dg-require-effective-target arm_crypto_ok } */
 /* { dg-add-options arm_crypto } */
-/* { dg-additional-options "-mcpu=cortex-a72 -O3 -dp" } */
+/* { dg-additional-options "-mcpu=cortex-a53 -O3 -dp" } */
 
 #include <arm_neon.h>

             reply	other threads:[~2023-02-22 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 14:49 Alexandre Oliva [this message]
2023-02-22 17:23 Alexandre Oliva
2023-02-23 13:48 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=20230222144938.57A9A3858436@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).