From: "Jin Ma" <jinma@linux.alibaba.com>
To: "Xi Ruoyao" <xry111@xry111.site>,
"gcc-patches" <gcc-patches@gcc.gnu.org>,
"Jeff Law" <jeffreyalaw@gmail.com>
Cc: "palmer" <palmer@dabbelt.com>,
"richard.sandiford" <richard.sandiford@arm.com>,
"kito.cheng" <kito.cheng@gmail.com>,
"philipp.tomsich" <philipp.tomsich@vrull.eu>,
"christoph.muellner" <christoph.muellner@vrull.eu>,
"rdapp.gcc" <rdapp.gcc@gmail.com>,
"juzhe.zhong" <juzhe.zhong@rivai.ai>,
"vineetg" <vineetg@rivosinc.com>,
"jinma.contrib" <jinma.contrib@gmail.com>
Subject: Re: [PATCH v2] In the pipeline, USE or CLOBBER should delay execution if it starts a new live range.
Date: Mon, 13 Nov 2023 10:16:55 +0800 [thread overview]
Message-ID: <d105ff79-3fa0-46bd-bb62-32b15bc6ad2a.jinma@linux.alibaba.com> (raw)
In-Reply-To: <68dc5f7e-2cc6-43ba-a1ec-bf17af244476@gmail.com>
> >
> > Unfortunately this patch has triggered a bootstrap comparison failure on
> > loongarch64-linux-gnu: https://gcc.gnu.org/PR112497.
> It's also causing simple build failures on other targets. For example
> c6x-elf aborts when compiling gcc.c-torture/execute/pr82210 (and others)
> with -O2 with that patch applied.
>
> I've reverted it for now. I'm not going to have time to investigate
> this week.
I'm sorry to have caused this and had a bad effect. This patch has
been a long time since I verified it, so I don't know what happened, I
will check it out :)
BR
Jin
> Jeff
> >
next prev parent reply other threads:[~2023-11-13 2:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 8:07 [PATCH] In the ready lists of pipeline, put unrecog insns (such as CLOBBER,USE) at the latest to issue Jin Ma
2023-03-27 17:01 ` [PATCH] In the ready lists of pipeline, put unrecog insns (such as CLOBBER, USE) " Richard Sandiford
2023-04-14 21:38 ` Jeff Law
2023-05-29 10:51 ` [PATCH] In the pipeline, UNRECOG INSN is not executed in advance if it starts a live range Jin Ma
2023-06-08 1:50 ` Jin Ma
2023-06-09 23:40 ` Jeff Law
2023-06-12 3:38 ` Jin Ma
2023-11-11 18:51 ` Jeff Law
2023-08-14 11:22 ` [PATCH v2] In the pipeline, USE or CLOBBER should delay execution if it starts a new " Jin Ma
2023-08-29 8:00 ` Jin Ma
2023-11-11 20:12 ` Jeff Law
2023-11-12 17:41 ` Xi Ruoyao
2023-11-12 18:02 ` Jeff Law
2023-11-12 18:11 ` Xi Ruoyao
2023-11-13 2:16 ` Jin Ma [this message]
2023-11-13 2:28 ` Jeff Law
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=d105ff79-3fa0-46bd-bb62-32b15bc6ad2a.jinma@linux.alibaba.com \
--to=jinma@linux.alibaba.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jinma.contrib@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=rdapp.gcc@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=vineetg@rivosinc.com \
--cc=xry111@xry111.site \
/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).