public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109035] meaningless memory store on RISC-V and LoongArch
Date: Fri, 03 Nov 2023 06:52:26 +0000 [thread overview]
Message-ID: <bug-109035-4-ImG3skCvrO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109035-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109035
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #9 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #7)
> For last 2 weeks I pushed several patches for better dealing with
> equivalences in RA.
>
> It seems the patches solves the current PR. I checked the test code
> generation for loongarch and aarch64 and did not find spilled pseudos which
> are reported here.
>
> I think the PR should closed as fixed.
Thanks! For LoongArch this issue has been "papered over" since r14-19 though
it's a completely unrelated change.
I'm closing the PR as fixed anyway.
next prev parent reply other threads:[~2023-11-03 6:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 7:51 [Bug rtl-optimization/109035] New: " xry111 at gcc dot gnu.org
2023-03-06 7:52 ` [Bug rtl-optimization/109035] " xry111 at gcc dot gnu.org
2023-03-06 8:02 ` xry111 at gcc dot gnu.org
2023-03-08 3:16 ` chenglulu at loongson dot cn
2023-03-08 3:37 ` xry111 at gcc dot gnu.org
2023-03-08 3:55 ` chenglulu at loongson dot cn
2023-03-11 6:44 ` chenglulu at loongson dot cn
2023-03-11 7:00 ` chenglulu at loongson dot cn
2023-11-02 19:25 ` vmakarov at gcc dot gnu.org
2023-11-02 19:47 ` law at gcc dot gnu.org
2023-11-03 6:52 ` xry111 at gcc dot gnu.org [this message]
2023-11-03 7:46 ` xry111 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-109035-4-ImG3skCvrO@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: link
Be 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).