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 4CF0B3858D3C; Mon, 10 Jul 2023 06:32:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4CF0B3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688970773;
	bh=5fN2Ss6ALNd/0hicN3kmmWOWXCS9FwuXT0yq/YSscwA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=j1O4/oyt7EQ0+tJ7YOHkeGgoNlSJv1PCUa6eXsww3pIO51TDbQ5bPmJiphx4esJoN
	 0vPxFDwiAsVS2dsCmjQScxLxmK7ta5IeFO1/tbrZitHIgbw9mTDFPV5fEybYGOPvw2
	 GW8i7dIeHOOpK7T6/ioLvxemYSnOPhZhk7NENHS8=
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106966] [12/13/14 Regression] alpha cross build crashes
 gcc-12 "internal compiler error: in emit_move_insn"
Date: Mon, 10 Jul 2023 06:32:53 +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: 12.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail 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: 12.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106966-4-M6XMELiKSQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106966-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=3D106966

--- Comment #10 from Uro=C5=A1 Bizjak <ubizjak at gmail dot com> ---
(In reply to matoro from comment #9)
> (In reply to Uro=C5=A1 Bizjak from comment #8)
> > Created attachment 55504 [details]
> > Proposed patch.
> >=20
> > Can someone please bootstrap and test the attached patch?
>=20
> I can queue this up to test on real hardware.  By bootstrap, do you mean
> with --enable-bootstrap, and by test do you mean a full testsuite run or
> just checking that it doesn't ICE on the reproducer here?

I have already checked that it doesn't ICE with a crosscompiler. Regarding =
the
bootstrap, please note that --enable-bootstrap is the default nowadays, so =
the
option it is not needed to make a full build ("bootstrap"). Also, "make -j =
N -k
check-gcc" should be enough to test the compiler, since other parts of the
compiler never exercise -mbuild-constants (N in the command should be
substituted with a number of processors to parallelize the testsuite run).=