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 middle-end/115534] intermediate stack use not eliminated Date: Tue, 18 Jun 2024 17:29:20 +0000 [thread overview] Message-ID: <bug-115534-4-2fHMot3GK2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115534-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115534 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This might be improved by https://gcc.gnu.org/pipermail/gcc-patches/2024-June/654819.html . Or it might be the case the vectorizer case needs to be improved afterwards. But I think that is the infrastructure for fixing this issue.
next prev parent reply other threads:[~2024-06-18 17:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-18 7:48 [Bug tree-optimization/115534] New: " tnfchris at gcc dot gnu.org 2024-06-18 12:36 ` [Bug tree-optimization/115534] " pinskia at gcc dot gnu.org 2024-06-18 12:36 ` [Bug middle-end/115534] " pinskia at gcc dot gnu.org 2024-06-18 12:49 ` tnfchris at gcc dot gnu.org 2024-06-18 17:26 ` pinskia at gcc dot gnu.org 2024-06-18 17:29 ` pinskia at gcc dot gnu.org [this message] 2024-06-18 18:11 ` tnfchris 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-115534-4-2fHMot3GK2@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).