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 2AFE43858C5E; Mon, 10 Jul 2023 14:41:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2AFE43858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689000079;
	bh=tTfXRkOR+bQ9nL0txwk2Y/zqG2OK+w7y0IvLWzVvhVs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PK51ti+4zgZGIB+D0wQeM0MCDA9f+0R6GiTsgMQvcpZOWxgz5hd2iHDo8hbVnlSP0
	 f49r6lK5seqSqqQa0cU1sRzGcP5P/sOXYX1jpkl0mthH4KLTDS6mek/5tUvMCK4Vza
	 qzu6LZB6fz8eeDNEtD0rzmUrbffoVHq0HI+h2fLY=
From: "matoro_gcc_bugzilla at matoro dot tk" <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 14:41:17 +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: matoro_gcc_bugzilla at matoro dot tk
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-BHbu3CKxYI@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 #11 from matoro <matoro_gcc_bugzilla at matoro dot tk> ---
(In reply to Uro=C5=A1 Bizjak from comment #10)
> (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?
>=20
> I have already checked that it doesn't ICE with a crosscompiler. Regarding
> the bootstrap, please note that --enable-bootstrap is the default nowaday=
s,
> 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 oth=
er
> 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).

I was just checking because alpha hardware is quite antique, it's single-co=
re
so a full compile with bootstrap takes around ~72 hours.  I don't know how =
long
the test suite takes because I've never run it on this machine, but I would
expect it to add a couple additional days to that.  If that's fine I'll kic=
k it
off, just want to be clear on what exactly you'd like to see.=