From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D8F8C3844046; Mon, 19 Oct 2020 21:28:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D8F8C3844046 From: "euloanty at live dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97481] GCC ice when build with RISCV on msys2 Date: Mon, 19 Oct 2020 21:28:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: euloanty at live dot com X-Bugzilla-Status: UNCONFIRMED 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2020 21:28:34 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97481 --- Comment #4 from fdlbxtqi --- (In reply to Jim Wilson from comment #2) > riscv-unknown-linux-gnu is not a supported target. You must use either > riscv32-unknown-linux-gnu or riscv64-unknwon-linux-gnu. Both compilers > support both word sizes, the only difference is which is the default word > size. This may be part of the reason why it failed. >=20 > The attachment doesn't show any ICE. It is just a config.log file, and I > don't see anything interesting in there. >=20 > Note that mingw64 builds of a linux toolchain are unlikely to work as gli= bc > requires a case sensitive file system. I'd suggest using WSL2 as somethi= ng > more likely to work, but I haven't tried that myself. >=20 > It looks like you have a badly broken compiler build. You will need to > figure out why it is broken. This doesn't seem to be a gcc problem, but > rather a build problem on your side. Maybe I should try riscv64-linux-gnu. Thank you=