On Tue, Jul 11, 2023 at 06:02:18PM +0200, Christoph Müllner wrote: > Hi Kito, > > I take some of the blame because I have sent a series > that consisted of fixes followed by new features. > > You have ack'ed patches 1-9 from the series. > The last two patches (for XTheadMemIdx and XTheadFMemIdx) were > later reviewed by Jeff and need a bit rework and more testing. > > If it helps, you can find patches 1-9 rebased and retested here: > https://github.com/cmuellner/gcc/tree/riscv-thead-improvements > > I have also sent out a fix for two failing T-Head tests earlier today: > https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624049.html > It would be great if you could look at that and push that as well, if it is > ok. > > Thanks, > Christoph > > > > On Tue, Jul 11, 2023 at 5:51 PM Kito Cheng <kito.ch...@sifive.com> wrote: > > > > Hi Christoph: > > > > Ooops, I thought Philipp will push those patches, does here any other > > patches got approved but not committed? I can help to push those > > patches tomorrow. > > > > On Tue, Jul 11, 2023 at 11:42 PM Christoph Müllner > > <christoph.muell...@vrull.eu> wrote: > > > > > > Hi Cooper, > > > > > > I addressed this in April this year. > > > It even got an "ok", but nobody pushed it: > > > https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616972.html > > > > > > BR > > > Christoph > > >
Hi Christoph and Kito, That's great that this bug has been resolved. If you merge this patch, it would be best to also merge it to the gcc-13 branch. Thanks, Cooper
