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 07EFE39C076A; Mon, 25 Jan 2021 13:20:49 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 07EFE39C076A
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/98811] [11 regression] All Go tests FAIL with abbrev
 offset out of range
Date: Mon, 25 Jan 2021 13:20:49 +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: cvs-commit 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: 11.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-98811-4-LG3E7XNnt3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-98811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-98811-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 13:20:50 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98811

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:fe5cb7f94d4e9b6fc932017d4ee74ba4f9f417b9

commit r11-6893-gfe5cb7f94d4e9b6fc932017d4ee74ba4f9f417b9
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Jan 25 14:20:05 2021 +0100

    configure: Add workaround for buggy binutils 2.35 [PR98811]

    binutils since https://sourceware.org/bugzilla/show_bug.cgi?id=3D25612
    changes from March last year until the
    https://sourceware.org/pipermail/binutils/2020-August/112684.html
    fix in early August emits incorrect .debug_info when assembling files
    with --gdwarf-5.  Instead of emitting proper DWARF 5 .debug_info header,
    it emits DWARF 4 .debug_info header with 5 as the dwarf version instead=
 of
    4.  This results e.g. in libgcc.a (morestack.o) having garbage in its
    .debug_info sections and e.g. libbacktrace during pretty much all libgo
    tests fails miserably.

    The following patch adds a workaround for that, don't set
    HAVE_AS_GDWARF_5_DEBUG_FLAG if readelf can't read the .debug_info back.

    Built tested on x86_64-linux against both binutils 2.35 (buggy ones) and
    latest binutils trunk, the former with the patch now has DWARF 3
    .debug_line and DWARF 2 .debug_info in morestack.o, while the latter
    as before correct DWARF 5 .debug_line and .debug_info.

    2021-01-25  Jakub Jelinek  <jakub@redhat.com>

            PR debug/98811
            * configure.ac (HAVE_AS_GDWARF_5_DEBUG_FLAG): Only define if
            readelf -wi is able to read the emitted .debug_info back.
            * configure: Regenerated.=