public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-10357] testsuite, jit: Handle whitespace in test-link-section-assembler.c.
Date: Sat, 20 Apr 2024 14:43:10 +0000 (GMT)	[thread overview]
Message-ID: <20240420144310.C1A783858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:12e4b9ce523bd60acfb3d5567e493822fcdcf698

commit r12-10357-g12e4b9ce523bd60acfb3d5567e493822fcdcf698
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sat Jan 13 12:49:28 2024 +0000

    testsuite, jit: Handle whitespace in test-link-section-assembler.c.
    
    Darwin has a different .section directive that has more fields and
    uses different whitespace.  Amend the whitespace in the scan-asm to
    be more flexible.
    
    gcc/testsuite/ChangeLog:
    
            * jit.dg/test-link-section-assembler.c: Accept any whitespace
            between the .section directive and its arguments.
    
    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
    (cherry picked from commit 2b0abfd3f8dbe3e9af79bb6bdc06d727d36f1946)

Diff:
---
 gcc/testsuite/jit.dg/test-link-section-assembler.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/jit.dg/test-link-section-assembler.c b/gcc/testsuite/jit.dg/test-link-section-assembler.c
index a90b00e9a82..a78e9fd26ef 100644
--- a/gcc/testsuite/jit.dg/test-link-section-assembler.c
+++ b/gcc/testsuite/jit.dg/test-link-section-assembler.c
@@ -34,4 +34,4 @@ create_code (gcc_jit_context *ctxt, void *user_data)
 }
 
 /* { dg-final { jit-verify-output-file-was-created "" } } */
-/* { dg-final { jit-verify-assembler-output ".section	.my_section" } } */
+/* { dg-final { jit-verify-assembler-output ".section\\s.my_section" } } */

                 reply	other threads:[~2024-04-20 14:43 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=20240420144310.C1A783858D37@sourceware.org \
    --to=iains@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).