public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: John David Anglin <danglin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-6172] Adjust shadd-2 and shadd-3 scan counts. Date: Sun, 2 Jan 2022 18:56:27 +0000 (GMT) [thread overview] Message-ID: <20220102185627.20E1C3858C27@sourceware.org> (raw) https://gcc.gnu.org/g:6bec6e3aaa306ca7b87d6e6654acca546fa25e90 commit r12-6172-g6bec6e3aaa306ca7b87d6e6654acca546fa25e90 Author: John David Anglin <danglin@gcc.gnu.org> Date: Sun Jan 2 18:55:50 2022 +0000 Adjust shadd-2 and shadd-3 scan counts. 2022-01-02 John David Anglin <danglin@gcc.gnu.org> gcc/testsuite/ChangeLog: * gcc.target/hppa/shadd-2.c: Adjust count to 3. * gcc.target/hppa/shadd-3.c: Likewise. Diff: --- gcc/testsuite/gcc.target/hppa/shadd-2.c | 2 +- gcc/testsuite/gcc.target/hppa/shadd-3.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/gcc.target/hppa/shadd-2.c b/gcc/testsuite/gcc.target/hppa/shadd-2.c index b92f782cf0d..74d4fcd146e 100644 --- a/gcc/testsuite/gcc.target/hppa/shadd-2.c +++ b/gcc/testsuite/gcc.target/hppa/shadd-2.c @@ -1,6 +1,6 @@ /* { dg-do compile } */ /* { dg-options "-O2" } */ -/* { dg-final { scan-assembler-times "sh.add" 4 } } */ +/* { dg-final { scan-assembler-times "sh.add" 3 } } */ typedef struct rtx_def *rtx; typedef const struct rtx_def *const_rtx; diff --git a/gcc/testsuite/gcc.target/hppa/shadd-3.c b/gcc/testsuite/gcc.target/hppa/shadd-3.c index 2d0b648f384..a0c1f663d56 100644 --- a/gcc/testsuite/gcc.target/hppa/shadd-3.c +++ b/gcc/testsuite/gcc.target/hppa/shadd-3.c @@ -10,7 +10,7 @@ over time we'll have to revisit the combine and/or postreload dumps. Note we have disabled delay slot filling to improve test stability. */ -/* { dg-final { scan-assembler-times "sh.add" 4 } } */ +/* { dg-final { scan-assembler-times "sh.add" 3 } } */ extern void oof (void); typedef struct simple_bitmap_def *sbitmap;
reply other threads:[~2022-01-02 18:56 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=20220102185627.20E1C3858C27@sourceware.org \ --to=danglin@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).