public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 80dc53f6b38d697b169fad9ce3b8787ce1c6768c
Date: Tue, 2 Mar 2021 17:45:38 +0000 (GMT) [thread overview]
Message-ID: <20210302174538.3D9F03950408@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".
The branch, master has been updated
via 80dc53f6b38d697b169fad9ce3b8787ce1c6768c (commit)
from 57190618a8884fbf1ae7f48a6968dab84b2837fa (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 80dc53f6b38d697b169fad9ce3b8787ce1c6768c
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Feb 19 18:02:19 2021 +0100
Document the GCC11 change to DWARF5 default.
* gcc-11/changes.html (General Improvements): Add a section on
the DWARF version 5 default.
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 6a47b0b8..9734eee8 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -139,6 +139,37 @@ a work-in-progress.</p>
<li><code>-fsanitize=kernel-hwaddress</code> to instrument kernel code.</li>
</ul>
</li>
+ <li>
+ <p>
+ For targets that produce DWARF debugging information GCC now
+ defaults to <a href="http://dwarfstd.org/doc/DWARF5.pdf">DWARF
+ version 5</a> (with the exception of VxWorks and Darwin/Mac OS X
+ which default to version 2 and AIX which defaults to version 4).
+ This can produce up to 25% more compact debug information
+ compared to earlier versions.
+ <p>
+ To take full advantage of DWARF version 5 GCC needs to be build
+ against binutils version 2.35.2 or higher. When GCC is build
+ against earlier versions of binutils GCC will still emit DWARF
+ version 5 for most debuginfo data, but will generate version 4
+ debug line tables (even when explicitly given <code>-gdwarf-5</code>).
+ <p>
+ The following debug information consumers can process DWARF version 5:
+ <ul>
+ <li>GDB 8.0, or higher
+ <li>valgrind 3.17.0
+ <li>elfutils 0.172, or higher (for use with systemtap,
+ dwarves/pahole, perf and libabigail)
+ <li>dwz 0.14
+ </ul>
+ <p>
+ Programs embedding libbacktrace are urged to upgrade to the version
+ shipping with GCC 11.
+ <p>
+ To make GCC 11 generate an older DWARF version
+ use <code>-g</code> together with <code>-gdwarf-2</code>,
+ <code>-gdwarf-3</code> or <code>-gdwarf-4</code>.
+ </li>
</ul>
<!-- .................................................................. -->
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-11/changes.html | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2021-03-02 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210302174538.3D9F03950408@sourceware.org \
--to=mark@sourceware.org \
--cc=gcc-cvs-wwwdocs@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).