public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-8883] arm: Fix pr69245.c testcase for reorder assembler architecture directives [PR101723]
Date: Wed, 18 Aug 2021 15:23:29 +0000 (GMT)	[thread overview]
Message-ID: <20210818152329.80B5E388C022@sourceware.org> (raw)

https://gcc.gnu.org/g:b8a001599d21eaa77737df7efc6bc206e6964cdf

commit r11-8883-gb8a001599d21eaa77737df7efc6bc206e6964cdf
Author: Christophe Lyon <christophe.lyon@foss.st.com>
Date:   Fri Aug 6 14:25:47 2021 +0000

    arm: Fix pr69245.c testcase for reorder assembler architecture directives [PR101723]
    
    In gcc.target/arm/pr69245.c, to have a .fpu neon-vfpv4 directive, make
    sure code for fn1() is emitted, by removing the static keyword.
    
    Fix a typo in gcc.target/arm/pr69245.c, where \s should be \\s.
    
    2021-08-06  Christophe Lyon  <christophe.lyon@foss.st.com>
    
            gcc/testsuite/
    
            PR target/101723
            * gcc.target/arm/pr69245.c: Make sure to emit code for fn1, fix
            typo.
    
    (cherry picked from commit aff75af3b50f8c039ed6fbfa3f313ba45d44f6e6)

Diff:
---
 gcc/testsuite/gcc.target/arm/pr69245.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.target/arm/pr69245.c b/gcc/testsuite/gcc.target/arm/pr69245.c
index 34b97a22e15..58a6104e8f6 100644
--- a/gcc/testsuite/gcc.target/arm/pr69245.c
+++ b/gcc/testsuite/gcc.target/arm/pr69245.c
@@ -12,7 +12,7 @@
 #pragma GCC target "fpu=neon-vfpv4"
 int a, c, d;
 float b;
-static int fn1 ()
+ int fn1 ()
 {
   return 0;
 }
@@ -26,5 +26,5 @@ void fn2 ()
 /* Because we don't know the exact command-line options used to invoke the test
    we cannot expect these tests to match exactly once.  But they must appear at
    least once.  */
-/* { dg-final { scan-assembler "\.fpu\s+vfp\n" } } */
-/* { dg-final { scan-assembler "\.fpu\s+neon-vfpv4\n" } } */
+/* { dg-final { scan-assembler "\.fpu\\s+vfp\n" } } */
+/* { dg-final { scan-assembler "\.fpu\\s+neon-vfpv4\n" } } */


                 reply	other threads:[~2021-08-18 15:23 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=20210818152329.80B5E388C022@sourceware.org \
    --to=rearnsha@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).