This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] RISC-V: Fix bad insn splits with paradoxical subregs.

From: Jim Wilson <jimw at sifive dot com>
To: Kito Cheng <kito dot cheng at gmail dot com>
Cc: Richard Biener <rguenther at suse dot de>, Jakub Jelinek <jakub at redhat dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 18 Sep 2019 13:34:13 -0700
Subject: Re: [PATCH] RISC-V: Fix bad insn splits with paradoxical subregs.
References: <20190905203409.759-1-jimw@sifive.com> <CA+yXCZBKi2yCG+RTN6z6i7MGF+LT6sX6ANF00Fct7RaJsj8DnA@mail.gmail.com> <nycvar.YFH.7.76.1909181224310.5566@zhemvz.fhfr.qr> <CA+yXCZCJQicNmTpLe50fmVzNRUHa0gQZnbw0HA2v2fOA2_yxDA@mail.gmail.com>

On Wed, Sep 18, 2019 at 3:27 AM Kito Cheng <kito.cheng@gmail.com> wrote:
> On Wed, Sep 18, 2019 at 6:25 PM Richard Biener <rguenther@suse.de> wrote:
> > Since it is target specific and for non-primary/secondary targets
> > it's the RISC-V maintainers call whether to allow backporting this.
> > Generally wrong-code issues can be backported even if they are not
> > regressions if the chance they introduce other issues is low.

Speaking as a RISC-V maintainer, I'd like to see it backported.  That
is why I left the bug report open.

Jim

References:
- [PATCH] RISC-V: Fix bad insn splits with paradoxical subregs.
  - From: Jim Wilson
- Re: [PATCH] RISC-V: Fix bad insn splits with paradoxical subregs.
  - From: Kito Cheng
- Re: [PATCH] RISC-V: Fix bad insn splits with paradoxical subregs.
  - From: Richard Biener
- Re: [PATCH] RISC-V: Fix bad insn splits with paradoxical subregs.
  - From: Kito Cheng

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]