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/112340] [14 regression] assembler instruction counts off for gcc.target/powerpc/pr106550_1.c Date: Tue, 07 Nov 2023 08:14:15 +0000 [thread overview] Message-ID: <bug-112340-4-66lW4PPbFB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112340-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112340 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>: https://gcc.gnu.org/g:a5a76c6f8795f8072e8005e5ada741b69c742198 commit r14-5184-ga5a76c6f8795f8072e8005e5ada741b69c742198 Author: Jiufu Guo <guojiufu@linux.ibm.com> Date: Tue Nov 7 15:19:36 2023 +0800 rs6000,testcase: Add require-effective-target has_arch_ppc64 to pr106550_1.c With the latest trunk, case pr106550_1.c runs with failure on ppc under -m32. Previously, this case failed with ICE due to PR111971. Now, this emission is exposed. While, the case is testing 64bit constant building. So, "has_arch_ppc64" is required. PR target/112340 gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr106550_1.c: Add has_arch_ppc64 target require.
next prev parent reply other threads:[~2023-11-07 8:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 20:15 [Bug testsuite/112340] New: " seurer at gcc dot gnu.org 2023-11-02 10:03 ` [Bug testsuite/112340] " rguenth at gcc dot gnu.org 2023-11-07 2:23 ` linkw at gcc dot gnu.org 2023-11-07 8:14 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-08 7:20 ` guojiufu 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-112340-4-66lW4PPbFB@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: 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).