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/109778] [10/11/12/13 Regression] Wrong code at -O1 and above on x86_64-linux-gnu Date: Tue, 09 May 2023 10:56:11 +0000 [thread overview] Message-ID: <bug-109778-4-eTOAQiWGmG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109778-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109778 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7408a0b93e6f6b3ce9b6be17bb9b5d2307f5ecf1 commit r12-9524-g7408a0b93e6f6b3ce9b6be17bb9b5d2307f5ecf1 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue May 9 12:14:18 2023 +0200 testsuite: Add further testcase for already fixed PR [PR109778] I came up with a testcase which reproduces all the way to r10-7469. LTO to avoid early inlining it, so that ccp handles rotates and not shifts before they are turned into rotates. 2023-05-09 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/109778 * gcc.dg/lto/pr109778_0.c: New test. * gcc.dg/lto/pr109778_1.c: New file. (cherry picked from commit c2cf2dc988eb93551fa1c01d3f8d73ef21f39dc5)
next prev parent reply other threads:[~2023-05-09 10:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 19:18 [Bug c/109778] New: Wrong code at -O3 on x86_64-linux-gnu since GCC-12.2 shaohua.li at inf dot ethz.ch 2023-05-08 19:30 ` [Bug tree-optimization/109778] [12/13/14 Regression] Wrong code at -O1 and above " pinskia at gcc dot gnu.org 2023-05-08 19:31 ` [Bug tree-optimization/109778] [13/14 Regression] Wrong code at -O1 and above on x86_64-linux-gnu pinskia at gcc dot gnu.org 2023-05-08 19:36 ` jakub at gcc dot gnu.org 2023-05-08 22:09 ` jakub at gcc dot gnu.org 2023-05-09 7:38 ` rguenth at gcc dot gnu.org 2023-05-09 10:11 ` cvs-commit at gcc dot gnu.org 2023-05-09 10:19 ` cvs-commit at gcc dot gnu.org 2023-05-09 10:23 ` [Bug tree-optimization/109778] [10/11/12/13 " jakub at gcc dot gnu.org 2023-05-09 10:49 ` cvs-commit at gcc dot gnu.org 2023-05-09 10:49 ` cvs-commit at gcc dot gnu.org 2023-05-09 10:56 ` cvs-commit at gcc dot gnu.org 2023-05-09 10:56 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-09 11:04 ` cvs-commit at gcc dot gnu.org 2023-05-09 11:04 ` cvs-commit at gcc dot gnu.org 2023-05-09 11:10 ` cvs-commit at gcc dot gnu.org 2023-05-09 11:10 ` cvs-commit at gcc dot gnu.org 2023-05-21 16:56 ` jakub 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-109778-4-eTOAQiWGmG@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).