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/103586] New test case gcc.target/powerpc/pr101324.c fails on BE
Date: Fri, 11 Feb 2022 19:28:04 +0000 [thread overview]
Message-ID: <bug-103586-4-8nybaCoKJp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103586-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103586
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:4854985f13feac2d61c69c996c47af468f29c6c9
commit r11-9559-g4854985f13feac2d61c69c996c47af468f29c6c9
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Tue Dec 7 14:42:38 2021 -0600
testsuite: Fix check_effective_target_rop_ok [PR103556, PR103586]
The new rop_ok effective target test doesn't correctly compute its
expression
result because a new line starts a new statement. Solution is to remove
the new line.
2021-12-07 Peter Bergner <bergner@linux.ibm.com>
gcc/testsuite/
PR testsuite/103556
PR testsuite/103586
* lib/target-supports.exp (check_effective_target_rop_ok): Remove
'\n'.
(cherry picked from commit 4394fd67264f5de650c2c3509c001c5f7203449d)
prev parent reply other threads:[~2022-02-11 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 19:48 [Bug testsuite/103586] New: " seurer at gcc dot gnu.org
2021-12-07 8:07 ` [Bug testsuite/103586] " marxin at gcc dot gnu.org
2021-12-07 17:17 ` bergner at gcc dot gnu.org
2021-12-07 20:43 ` cvs-commit at gcc dot gnu.org
2021-12-07 20:49 ` bergner at gcc dot gnu.org
2022-02-11 19:28 ` cvs-commit at gcc dot gnu.org [this message]
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-103586-4-8nybaCoKJp@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).