On Mon, 2022-06-06 at 18:33 -0400, David Malcolm wrote:
> > On Thu, 2022-05-19 at 16:10 +0800, Yang Yujie wrote:
> > > This patch does not affect any other target architecture than
> > > loongarch,
> > > and has been bootstrapped and regression-tested on loongarch64-
> > > linux-
> > > gnuf64
> > >
On Mon, 2022-05-30 at 18:09 +0800, Xi Ruoyao wrote:
> Ping. I'd like to see libgccjit working on LoongArch so I would be
> able
> to submit a Rust port to upstream.
>
> If the result is NACK I'd like to know alternative approaches to fix
> the
> build failure.
>
> I doubt if "j...@gcc.gnu.org" i
Ping. I'd like to see libgccjit working on LoongArch so I would be able
to submit a Rust port to upstream.
If the result is NACK I'd like to know alternative approaches to fix the
build failure.
I doubt if "j...@gcc.gnu.org" is really used, so CC'ed the JIT maintainer
listed in MAINTAINERS.
On
Hello,
This patch fixes libgccjit build failure on loongarch* targets,
and could probably be useful for future ports.
For now, libgccjit is linked with objects from $(EXTRA_GCC_OBJS) and
libbackend.a, which contains object files from $(EXTRA_OBJS).
This effectively forbids any overlap between th
