public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4102] Fix up 'g++.dg/abi/nvptx-ptrmem1.C' Date: Mon, 18 Sep 2023 14:37:13 +0000 (GMT) [thread overview] Message-ID: <20230918143713.8CD563858D32@sourceware.org> (raw) https://gcc.gnu.org/g:3049501db3a31d10c84fc42b306e29b6fe68330f commit r14-4102-g3049501db3a31d10c84fc42b306e29b6fe68330f Author: Thomas Schwinge <thomas@codesourcery.com> Date: Mon Sep 18 16:34:47 2023 +0200 Fix up 'g++.dg/abi/nvptx-ptrmem1.C' ..., which shortly after its inception in commit 44eba92d0a0594bda5b53fcb3c8f84f164c653b6 (Subversion r231628) "[PTX] parameters and return values" was forgotten to be updated in next day's commit 1f0659546bcf5b95c3263cdc73149f6c2a05ebe1 (Subversion r231663) "[PTX] more register cleanups". Fix it up now, as obvious, for the current state of things. gcc/testsuite/ * g++.dg/abi/nvptx-ptrmem1.C: Fix up. Diff: --- gcc/testsuite/g++.dg/abi/nvptx-ptrmem1.C | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/g++.dg/abi/nvptx-ptrmem1.C b/gcc/testsuite/g++.dg/abi/nvptx-ptrmem1.C index 08ffd7e373e..0c57f29fa21 100644 --- a/gcc/testsuite/g++.dg/abi/nvptx-ptrmem1.C +++ b/gcc/testsuite/g++.dg/abi/nvptx-ptrmem1.C @@ -9,7 +9,7 @@ struct A{}; typedef int A::*pmd; typedef void (A::*pmf) (); -// { dg-final { scan-assembler ".extern .func \\(.param.u64 %out_retval\\) _Z8dcl_rpmdv;" } } +// { dg-final { scan-assembler ".extern .func \\(.param.u64 %value_out\\) _Z8dcl_rpmdv;" } } pmd dcl_rpmd (); // { dg-final { scan-assembler ".extern .func _Z8dcl_rpmfv \\(.param.u64 %in_ar0\\);" } } @@ -29,7 +29,7 @@ void test_1 () dcl_apmf (0); } -// { dg-final { scan-assembler-times ".visible .func \\(.param.u64 %out_retval\\) _Z8dfn_rpmdv(?:;|\[\r\n\]+\{)" 2 } } +// { dg-final { scan-assembler-times ".visible .func \\(.param.u64 %value_out\\) _Z8dfn_rpmdv(?:;|\[\r\n\]+\{)" 2 } } pmd dfn_rpmd () { return 0;
reply other threads:[~2023-09-18 14:37 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=20230918143713.8CD563858D32@sourceware.org \ --to=tschwinge@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: linkBe 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).