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 2E1053858421; Wed, 22 Mar 2023 15:32:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E1053858421
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1679499179;
	bh=KN4hDZ0Is1bLALkOCXsKZtKOHfpc986Mp17LnYmQShM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mZSRYlWJgXnU82iHxDYGWKg2bwl89pMW0mWi9kQsiNfOkTd+3Z4Rb3pec/aY+WULA
	 XQn21uB14fobgUBBfQFDh2++AjDUPaDvEq39HLCzYuqnPcVcx0UxpuF9JWiECzbeGe
	 qF1X+wx++HfgaUtz9VU+naAruHy3wfIRZVb4swN0=
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu':
 machine `loongarch64-unknown' not recognized
Date: Wed, 22 Mar 2023 15:32:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 12.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: WAITING
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-109250-4-MMiskDIknb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109250-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109250-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=3D109250

--- Comment #5 from Andreas Schwab <schwab@linux-m68k.org> ---
There is support for loongarch in longlong.h (added a year ago
https://gmplib.org/repo/gmp/rev/32dc4af70f95), which may be enough to build=
 it,
if config.sub is updated from upstream.=