public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755
Date: Mon, 18 Jan 2021 17:45:18 +0000	[thread overview]
Message-ID: <bug-98716-4-QwttkprFNJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98716-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Mark Wielaard <mark at gcc dot gnu.org> ---
(In reply to Mark Wielaard from comment #7)
> (In reply to Ian Lance Taylor from comment #5)
> > I'm not seeing any failures in the Go testsuite with GNU binutils 2.35.1. 
> > Anybody know what changed in newer version of the binutils?
> 
> The difference is that with binutils 2.36 (not released yet) gas generates
> when asked to (with -gdwarf-5) DWARF 5 line tables. While 2.35.1 always
> generated DWARF 4 line tables.

Actually 2.35.1 does already have support for -gdwarf-5, but had some bugs
which are detected by gcc configure, so that it is not used. The bugs were
fixed on the 2.35 branch, but there is no 2.35.2 release (yet?). Anyway. The
difference is the gcc configure check for HAVE_AS_WORKING_DWARF_N_FLAG.

  parent reply	other threads:[~2021-01-18 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 21:45 [Bug debug/98716] New: " hjl.tools at gmail dot com
2021-01-18  6:02 ` [Bug debug/98716] " jakub at gcc dot gnu.org
2021-01-18  9:36 ` rguenth at gcc dot gnu.org
2021-01-18 10:41 ` jakub at gcc dot gnu.org
2021-01-18 13:18 ` jakub at gcc dot gnu.org
2021-01-18 13:33 ` jakub at gcc dot gnu.org
2021-01-18 17:08 ` ian at airs dot com
2021-01-18 17:10 ` ian at airs dot com
2021-01-18 17:37 ` mark at gcc dot gnu.org
2021-01-18 17:38 ` mark at gcc dot gnu.org
2021-01-18 17:45 ` mark at gcc dot gnu.org [this message]
2021-01-18 22:43 ` cvs-commit at gcc dot gnu.org
2021-01-18 23:10 ` ian at airs dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-98716-4-QwttkprFNJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).