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/106345] Some ppc64le tests fail with -mcpu=power9 -mtune=power9
Date: Tue, 13 Sep 2022 06:23:57 +0000 [thread overview]
Message-ID: <bug-106345-4-SVzl9fY0v4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106345-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:
https://gcc.gnu.org/g:12d28957b613d8c9b74e7841d73945025a7f0ccb
commit r10-10982-g12d28957b613d8c9b74e7841d73945025a7f0ccb
Author: Kewen Lin <linkw@linux.ibm.com>
Date: Tue Sep 6 20:37:57 2022 -0500
rs6000/test: Fix empty TU in some cases of effective targets [PR106345]
As the failure of test case gcc.target/powerpc/pr92398.p9-.c in
PR106345 shows, some test sources for some powerpc effective
targets use empty translation unit wrongly. The test sources
could go with options like "-ansi -pedantic-errors", then those
effective target checkings will fail unexpectedly with the
error messages like:
error: ISO C forbids an empty translation unit [-Wpedantic]
This patch is to fix empty TUs with one dummy function definition
accordingly.
PR testsuite/106345
gcc/testsuite/ChangeLog:
* lib/target-supports.exp (check_effective_target_has_arch_pwr5):
Add
a function definition to avoid pedwarn about empty translation
unit.
(check_effective_target_has_arch_pwr6): Likewise.
(check_effective_target_has_arch_pwr7): Likewise.
(check_effective_target_has_arch_pwr8): Likewise.
(check_effective_target_has_arch_pwr9): Likewise.
(check_effective_target_has_arch_ppc64): Likewise.
(check_effective_target_ppc_float128): Likewise.
(check_effective_target_ppc_float128_insns): Likewise.
(check_effective_target_powerpc_vsx): Likewise.
(cherry picked from commit 7a43e52a48b6403a99d3e8ab3105869b4b3c081e)
next prev parent reply other threads:[~2022-09-13 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 17:32 [Bug testsuite/106345] New: " mpolacek at gcc dot gnu.org
2022-07-19 6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org
2022-07-20 2:01 ` linkw at gcc dot gnu.org
2022-07-25 5:53 ` cvs-commit at gcc dot gnu.org
2022-07-26 12:13 ` linkw at gcc dot gnu.org
2022-08-02 3:53 ` cvs-commit at gcc dot gnu.org
2022-08-02 3:56 ` cvs-commit at gcc dot gnu.org
2022-08-02 3:58 ` cvs-commit at gcc dot gnu.org
2022-09-07 1:38 ` cvs-commit at gcc dot gnu.org
2022-09-13 5:21 ` cvs-commit at gcc dot gnu.org
2022-09-13 5:22 ` cvs-commit at gcc dot gnu.org
2022-09-13 6:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-13 6:24 ` linkw 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-106345-4-SVzl9fY0v4@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).