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 target/108308] [13 Regression] wrong code at -Os and -O2 with "-fno-tree-ccp" on x86_64-linux-gnu Date: Fri, 06 Jan 2023 09:54:04 +0000 [thread overview] Message-ID: <bug-108308-4-2JLSBnUPD7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108308-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108308 --- Comment #2 from CVS 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:b990e80e39b41ec028d018eac7d2d040a537b681 commit r13-5043-gb990e80e39b41ec028d018eac7d2d040a537b681 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Jan 6 10:52:34 2023 +0100 testsuite: Add testcases from PR108292 and PR108308 These PRs were for now fixed by reversion of the r13-4977 patch, but so that the problems don't reappear during stage 1, I'm adding testcase coverage from those PRs. 2023-01-06 Jakub Jelinek <jakub@redhat.com> PR target/108292 PR target/108308 * gcc.c-torture/execute/pr108292.c: New test. * gcc.target/i386/pr108292.c: New test. * gcc.dg/pr108308.c: New test.
next prev parent reply other threads:[~2023-01-06 9:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-05 23:28 [Bug tree-optimization/108308] New: " zhendong.su at inf dot ethz.ch 2023-01-06 6:29 ` [Bug tree-optimization/108308] [13 Regression] " pinskia at gcc dot gnu.org 2023-01-06 9:37 ` jakub at gcc dot gnu.org 2023-01-06 9:54 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-11 12:08 ` [Bug target/108308] " 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-108308-4-2JLSBnUPD7@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).