public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-1606] Fix expected test output on hppa Date: Wed, 7 Jun 2023 14:48:24 +0000 (GMT) [thread overview] Message-ID: <20230607144824.6AFA4385842C@sourceware.org> (raw) https://gcc.gnu.org/g:c0b88e9e8bbe15f0c2167371b49521b748c6da19 commit r14-1606-gc0b88e9e8bbe15f0c2167371b49521b748c6da19 Author: Jeff Law <jlaw@ventanamicro.com> Date: Wed Jun 7 07:55:32 2023 -0600 Fix expected test output on hppa Recent changes in the hoisting code change the optimized gimple for the shadd-3 testcase on the PA. That in turn changes the number of expected shadd instructions. I'm not entirely sure the test is actually testing what we want anymore since I don't see a CSE for postreload to discover. But I did verify that the number of shadd instructions is sane, so I just changed the count in the obvious way. gcc/testsuite * gcc.target/hppa/shadd-3.c: Update expected output. Diff: --- gcc/testsuite/gcc.target/hppa/shadd-3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/hppa/shadd-3.c b/gcc/testsuite/gcc.target/hppa/shadd-3.c index a0c1f663d56..2d0b648f384 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" 3 } } */ +/* { dg-final { scan-assembler-times "sh.add" 4 } } */ extern void oof (void); typedef struct simple_bitmap_def *sbitmap;
reply other threads:[~2023-06-07 14:48 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=20230607144824.6AFA4385842C@sourceware.org \ --to=law@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).