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/112751] [14 regression] gcc.target/powerpc/pcrel-sibcall-1.c fails after r14-5628-g53ba8d669550d3 Date: Wed, 10 Jan 2024 05:09:48 +0000 [thread overview] Message-ID: <bug-112751-4-HQm98nqdHY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112751 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:57792c33042d17605a6b6ad9027f5e6d5199eb26 commit r14-7092-g57792c33042d17605a6b6ad9027f5e6d5199eb26 Author: Kewen Lin <linkw@linux.ibm.com> Date: Tue Jan 9 23:06:13 2024 -0600 testsuite, rs6000: Adjust pcrel-sibcall-1.c with noipa [PR112751] As PR112751 shows, commit r14-5628 caused pcrel-sibcall-1.c to fail as it enables ipa-vrp which makes return values of functions {x,y,xx} as known and propagated. This patch is to adjust it with noipa to make it not fragile. PR testsuite/112751 gcc/testsuite/ChangeLog: * gcc.target/powerpc/pcrel-sibcall-1.c: Replace noinline as noipa.
next prev parent reply other threads:[~2024-01-10 5:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-28 20:47 [Bug target/112751] New: " seurer at gcc dot gnu.org 2023-11-28 20:55 ` [Bug target/112751] " pinskia at gcc dot gnu.org 2023-11-29 6:36 ` linkw at gcc dot gnu.org 2023-11-29 6:54 ` [Bug testsuite/112751] " rguenth at gcc dot gnu.org 2024-01-08 3:32 ` linkw at gcc dot gnu.org 2024-01-10 5:09 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-10 5:21 ` 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-112751-4-HQm98nqdHY@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).