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 tree-optimization/109925] [11/12/13/14 Regression] Wrong code at -O2 on x86_64-linux-gnu since GCC-12 Date: Thu, 28 Mar 2024 11:00:19 +0000 [thread overview] Message-ID: <bug-109925-4-LJxGyxVege@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109925-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109925 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7942558f27038461f948ca10140a156ae678cdf8 commit r14-9704-g7942558f27038461f948ca10140a156ae678cdf8 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Mar 28 11:58:26 2024 +0100 testsuite: Add testcase for already fixed PR [PR109925] This testcase was made latent by r14-4089 and got fixed both on the trunk and 13 branch with PR113372 fix. Adding testcase to the testsuite and will close the PR as a dup. 2024-03-28 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/109925 * gcc.c-torture/execute/pr109925.c: New test.
next prev parent reply other threads:[~2024-03-28 11:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-21 15:02 [Bug c/109925] New: " shaohua.li at inf dot ethz.ch 2023-05-21 15:17 ` [Bug tree-optimization/109925] [10/11/12/13/14 Regression] " jakub at gcc dot gnu.org 2023-05-26 6:33 ` rguenth at gcc dot gnu.org 2023-07-07 10:45 ` [Bug tree-optimization/109925] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-01-12 13:32 ` rguenth at gcc dot gnu.org 2024-03-27 16:50 ` jakub at gcc dot gnu.org 2024-03-28 11:00 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-28 11:01 ` jakub at gcc dot gnu.org 2024-03-30 3:55 ` cvs-commit 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-109925-4-LJxGyxVege@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).