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 4664E3858D35; Tue, 23 May 2023 16:22:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4664E3858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1684858951;
	bh=6ha2M50FteZ0SwqplQZaPBzUP5943hSByJ77AvPP12Y=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QTJ6MKcHYZd+MBkdgYYR58mQJFu9cqV05Jqb4oSOgr3IC+HV25JbzPrQ2uk0gy+57
	 1/tT346Un2fSbHQVD/BD3I8cpG37/iWjUjoTC51Chf5SbceA/t0A6OTj7bVPDR38/C
	 zKxmYyDIylBBa/gTwUjWfn8rh0XcCkEWhcvAu2Yo=
From: "ian at airs dot com" <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 16:22:30 +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: ian at airs dot com
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-mYxZqaLZpW@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 #9 from Ian Lance Taylor <ian at airs dot com> ---
If you really want to you can port the LoongArch changes back to 1.18.  I d=
on't
think that would be too hard--it's mostly a matter of adding build tags in
various places.  But it's up to you.=