From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BFF4838708E2; Sun, 24 Jan 2021 21:55:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BFF4838708E2 From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/98811] [11 regression] All Go tests FAIL with abbrev offset out of range Date: Sun, 24 Jan 2021 21:55:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE 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: 11.0 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: Sun, 24 Jan 2021 21:55:52 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98811 --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #1 from Mark Wielaard --- > (In reply to Rainer Orth from comment #0) >> However, when I switched to >> the freshly released GNU as 2.36 today, the error vanished everywhere. > > Which GNU as were you using before? There were some bug fixes for 2.35 wh= ich > never made it into a released version: > https://sourceware.org/pipermail/binutils/2020-November/114152.html The unmodified 2.35 release. I stick with self-compiled versions to avoid depending on distributions making their own set of changes. If the DWARF-5 support depends on specific binutils versions/patches to work, this should both be documented and detected at configure time. Having users run into such complete failure as in the Go case is a very bad user experience IMO.=