public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105903] Missed optimization for __synth3way Date: Fri, 01 Jul 2022 22:04:03 +0000 [thread overview] Message-ID: <bug-105903-4-JqaTCbisKj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105903-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105903 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Created attachment 53237 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53237&action=edit testcase Even though it was included in comment #0, I am attaching it as it easier to figure out what the testcase was.
next prev parent reply other threads:[~2022-07-01 22:04 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-08 23:43 [Bug c++/105903] New: " barry.revzin at gmail dot com 2022-06-08 23:53 ` [Bug tree-optimization/105903] " pinskia at gcc dot gnu.org 2022-06-29 1:40 ` luoxhu at gcc dot gnu.org 2022-06-29 1:51 ` pinskia at gcc dot gnu.org 2022-07-01 22:04 ` pinskia at gcc dot gnu.org [this message] 2022-07-01 22:10 ` pinskia at gcc dot gnu.org 2022-07-02 5:18 ` pinskia at gcc dot gnu.org 2023-05-24 0:01 ` pinskia at gcc dot gnu.org 2023-05-24 0:06 ` pinskia at gcc dot gnu.org 2023-06-07 2:46 ` pinskia at gcc dot gnu.org 2023-06-07 2:47 ` pinskia at gcc dot gnu.org 2023-07-30 6:10 ` pinskia at gcc dot gnu.org 2023-07-30 6:12 ` pinskia at gcc dot gnu.org 2023-07-30 6:32 ` pinskia at gcc dot gnu.org 2023-07-30 21:14 ` pinskia at gcc dot gnu.org 2023-07-31 17:14 ` pinskia 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-105903-4-JqaTCbisKj@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).