From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id DD48A3AA9403; Tue, 23 May 2023 08:17:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD48A3AA9403
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1684829837;
	bh=PllSG+kTz/zkf+zzUDRhI5hogXdRrAkz1IbRh5D2ZIg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gSKcGOFSSQGJrhmRSUlMKbOjUcSBoPgFA69CZpT0iRwc0W2fHWGP2G7oEPXlexRim
	 8YrJ12V38PckmSyPVd7zxPA2FiyLCzKrKirTx8Q0XO/LSy88T1pzWhVPi2gm8UXBl7
	 /tQzHZrWr1Od3QK+L+m3+PlIsFanZwCN6UkyJUK8=
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/108682] libffi needs to merge upstream to get LoongArch
 support
Date: Tue, 23 May 2023 08:17:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xry111 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108682-4-XG5qCRJBUg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108682

--- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Ian Lance Taylor from comment #6)
> libgo is running behind right now, but in any case I personally don't have
> plans to add LoongARCH support.  I would be happy to review any patches,
> which would ideally be sent using the process described at
> https://go.dev/doc/gccgo_contribute.

The Go runtime already contains LoongArch support since 1.19 release.  I (a=
nd
Xuerui, and some Loongson employees) can help for integrating it with gccgo,
but I guess we cannot do a thing until libgo is updated to use Go runtime >=
=3D
1.19.=