From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BE36538708EE; Tue, 9 Jun 2020 17:00:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE36538708EE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591722019; bh=U1HyaQcefAFAZMFuHAyoO6UqR3dUtqOOYHcP/vjREzc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=tidead7LRxDhms6rDUCgPv/zhyOwvy9kWwXwrjIupFvKHu74AjuF8iqYn6m+HOpw5 +EkmgxnjnxjyjlU0Z0fQreHHy3D+f/GsAzV74l4sNGmEiJoS/sL++b3jEERBDeOSYd YgKQGGq8YWixD/H3x5ej+MUX1cLuyNVhj+RQYb14= From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95381] [11 Regression]: Bootstrap on m68k fails with ICE: in operator[], at vec.h:867 Date: Tue, 09 Jun 2020 17:00:19 +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: X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com 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: 11.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: Tue, 09 Jun 2020 17:00:19 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95381 Jeffrey A. Law changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |law at redhat dot com --- Comment #4 from Jeffrey A. Law --- FWIW, I bootstrapped m68k within qemu on May30 with no testsuite regression= s.=20 Jun 6 also bootstrapped, but with some regressions with -fprofile-generate. So clearly you're builds are doing something different than mine. What Richi is asking for is a backtrace from the compiler itself. Without = that or some way to reproduce the problem, then there's not much we can do.=