public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/101654] [12 regression] new test case UNRESOLVED problem in r12-2524
Date: Mon, 09 Aug 2021 15:37:10 +0000 [thread overview]
Message-ID: <bug-101654-4-00sMJg2cAo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101654-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101654
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>:
https://gcc.gnu.org/g:d55d3f5b04e81b79f34ccf23f7e2c1e736ad3b0d
commit r12-2823-gd55d3f5b04e81b79f34ccf23f7e2c1e736ad3b0d
Author: Martin Jambor <mjambor@suse.cz>
Date: Mon Aug 9 17:35:39 2021 +0200
ipa: Fix testsuite/gcc.dg/ipa/remref-6.c
I forgot to add -fdump-ipa-inline to options of
testsuite/gcc.dg/ipa/remref-6.c and so the dump scan test were not
PASSing but ended up as UNRESOLVED. Fixing that revealed that the one
of the dumps it was looking for had a double space, so I removed it
too.
gcc/ChangeLog:
2021-08-09 Martin Jambor <mjambor@suse.cz>
PR testsuite/101654
* ipa-prop.c (propagate_controlled_uses): Removed a spurious space.
gcc/testsuite/ChangeLog:
2021-08-09 Martin Jambor <mjambor@suse.cz>
PR testsuite/101654
* gcc.dg/ipa/remref-6.c: Added missing -fdump-ipa-inline option.
next prev parent reply other threads:[~2021-08-09 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 23:00 [Bug testsuite/101654] New: " seurer at gcc dot gnu.org
2021-07-28 6:36 ` [Bug testsuite/101654] " rguenth at gcc dot gnu.org
2021-07-28 9:32 ` jamborm at gcc dot gnu.org
2021-07-29 6:23 ` rguenth at gcc dot gnu.org
2021-08-09 15:37 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-09 15:37 ` jamborm at gcc dot gnu.org
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=bug-101654-4-00sMJg2cAo@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).