From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8186A3858C52; Wed, 24 May 2023 07:40:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8186A3858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684914015; bh=HIhegVkW+BfiTkOXLVLh/NCw/o5frMCTlaFreHjI+m8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oZcO05UMuVv2d4ulmjLK+m9vzOesa4e+ulXNGOYCr5UOXazuUm/dIbpSLMxnVmpvX 8K4OcAf/0PvuYhAJwYZxYkBKbEgBMx+V8096LwLg0htVSjwYCdVdPhl0Ltwj86ES4v vWKD+iBKqR4+ZuA9cpwkFNRFQnLjpvxEg4Fa9I44= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libffi/108682] libffi needs to merge upstream to get LoongArch support Date: Wed, 24 May 2023 07:40:14 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108682 --- Comment #10 from Xi Ruoyao --- (In reply to Ian Lance Taylor from comment #9) > If you really want to you can port the LoongArch changes back to 1.18. I > don'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. I'd wait for the next update. People can use the Google Go compiler for now anyway.=