public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/110206] [14 Regression] wrong code with -Os -march=cascadelake since r14-1246 Date: Fri, 14 Jul 2023 06:26:15 +0000 [thread overview] Message-ID: <bug-110206-4-iGdJ4PLD7V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110206-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110206 --- Comment #16 from Uroš Bizjak <ubizjak at gmail dot com> --- v2 patch at [1]. [1] https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624491.html
next prev parent reply other threads:[~2023-07-14 6:26 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-11 11:27 [Bug target/110206] New: [14 Regression] wrong code with -Os -march=cascadelake zsojka at seznam dot cz 2023-06-11 16:24 ` [Bug target/110206] " pinskia at gcc dot gnu.org 2023-06-11 16:39 ` pinskia at gcc dot gnu.org 2023-06-11 17:37 ` [Bug target/110206] [14 Regression] wrong code with -Os -march=cascadelake since r14-1246 jakub at gcc dot gnu.org 2023-06-12 8:22 ` rguenth at gcc dot gnu.org 2023-06-12 8:55 ` ubizjak at gmail dot com 2023-06-12 9:09 ` ubizjak at gmail dot com 2023-06-12 9:11 ` [Bug rtl-optimization/110206] " ubizjak at gmail dot com 2023-06-12 9:15 ` ubizjak at gmail dot com 2023-06-12 9:18 ` ubizjak at gmail dot com 2023-07-08 14:07 ` ubizjak at gmail dot com 2023-07-08 16:56 ` ubizjak at gmail dot com 2023-07-08 17:36 ` ubizjak at gmail dot com 2023-07-09 8:54 ` ubizjak at gmail dot com 2023-07-10 11:54 ` rguenth at gcc dot gnu.org 2023-07-10 12:33 ` ubizjak at gmail dot com 2023-07-10 12:37 ` ubizjak at gmail dot com 2023-07-13 17:51 ` ubizjak at gmail dot com 2023-07-14 6:26 ` ubizjak at gmail dot com [this message] 2023-07-14 15:17 ` cvs-commit at gcc dot gnu.org 2023-07-14 20:03 ` cvs-commit at gcc dot gnu.org 2023-07-14 22:38 ` cvs-commit at gcc dot gnu.org 2023-07-14 22:39 ` ubizjak at gmail dot com
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-110206-4-iGdJ4PLD7V@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).