public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fx at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/100725] dwarf error with --whole-program
Date: Mon, 24 May 2021 10:36:35 +0000	[thread overview]
Message-ID: <bug-100725-4-bB8LcNLlhW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100725-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Dave Love <fx at gnu dot org> ---
(In reply to Jakub Jelinek from comment #1)
> Those binutils are too old for dwarf5.
> When the linker doesn't print any diagnostics, that isn't a big deal, but if
> it needs to diagnose something and parse DWARF for that, you need 2.35 or
> later.

Does that mean you can't reasonably use 11 on most distributions without
explicitly using -gdwarf-4?  The release notes suggested to me it would still
work, just not with full functionality somehow, and there is some adjustment
for the binutils version.  Is there some way to configure it to default to
DWARF 4 other than, I guess, adding specs to treat -g as -gdwarf-4?

  parent reply	other threads:[~2021-05-24 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 14:37 [Bug debug/100725] New: " fx at gnu dot org
2021-05-23 11:12 ` [Bug debug/100725] " jakub at gcc dot gnu.org
2021-05-24 10:36 ` fx at gnu dot org [this message]
2021-05-25  7:19 ` rguenth at gcc dot gnu.org

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-100725-4-bB8LcNLlhW@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).