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 EC0EB3858C52; Wed,  9 Nov 2022 07:51:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC0EB3858C52
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1667980275;
	bh=sp5G3bSz4MA4DltliyZvw3XOY8vnfQZMZyeIDdDZgTg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hfPywx0wN8P79uhel9TLQeCbWhZ06wCxKeH1BDhpnt5jw5/+xG1FtvrwTgSb3Xo+D
	 plRstbE/h6EZYq8ouQGWdkg9qtkfk2XaSgmbW8Twnn3CW2eEZ5p9FZBBgAq+URvDHM
	 YULBZkXO8B9TPuay1ohTTiZ16jwPs0O89EyLd9ME=
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107581] ICE on sparc-leon-uclibc during go build
Date: Wed, 09 Nov 2022 07:51:15 +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: build, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dkm at gcc dot gnu.org
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: <bug-107581-4-XRJ9OVlEtD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107581-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107581-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=3D107581

--- Comment #3 from Marc Poulhi=C3=A8s <dkm at gcc dot gnu.org> ---
(In reply to Ian Lance Taylor from comment #1)
> This crash appears to be fairly deep in the middle-end.  Nothing has chan=
ged
> recently in the Go frontend.  Has this crash just started appearing, or is
> this the first time you are trying this?  If it is a relatively new crash
> then I think it must be related to some middle-end change.  Thanks.

This is a first try. I was trying 12.2.0 (ICE) then checked with trunk to s=
ee
if it was still crashing.


(In reply to Richard Biener from comment #2)
> I assume that reproducing with trunk is with checking enabled?  It would =
be
> nice if you can do a debugging session on the crashing go1 invocation and
> inspect the GIMPLE that's being expanded.  From the backtrace it looks li=
ke
> it's some

I don't think the build has any checking enabled but I have to check (that's
from a crosstool-ng build, so I doubt they are enabling checks).

I'll do a debug build and add the more detailed log here.

Thanks=