public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed 13/13][odr] Add --odr/--no-odr and --odr-mode entries to man page
Date: Wed, 01 Jan 2020 00:00:00 -0000	[thread overview]
Message-ID: <20200106161036.GA20145@delia> (raw)

Hi,

Add an --odr/--no-odr entry and a --odr-mode entry to the man page, advertising
the optimization to the user.

Committed to trunk.

Thanks,
- Tom

[odr] Add --odr/--no-odr and --odr-mode entries to man page

2020-01-06  Tom de Vries  <tdevries@suse.de>

	* dwz.1: Add --odr/--no-odr and --odr-mode entries.

---
 dwz.1 | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/dwz.1 b/dwz.1
index a5a1ef6..3df7e59 100644
--- a/dwz.1
+++ b/dwz.1
@@ -88,6 +88,23 @@ containing more than
 \fICOUNT\fR DIEs at all.  The default is 50 million DIEs.  Specifying none as
 argument disables the limit.
 .TP
+.B \-\-odr / \-\-no-odr
+Enable/disable One-Definition-Rule optimization for C++ compilation units.
+This optimization causes struct/union/class DIEs with the same name to be
+considered equal.  This has the effect that DIEs referring to distinct DIEs
+representing the same type (like f.i. pointer type DIEs) are considered equal,
+and may be deduplicated.
+Enabled by default.
+.TP
+.B \-\-odr-mode=<basic|link>
+Set the One-Definition-Rule optimization aggressiveness: basic or link.
+When using the link setting, the optimization will attempt to replace
+declarations of a struct/union/class with a corresponding definition.  When
+using the basic setting, that part of the optimization is disabled.
+In normal operation, the link setting should be used.  The basic setting is
+provided only as fallback in case of problems with the link setting.  Set to
+link by default.
+.TP
 .B \-? \-\-help
 Print short help and exit.
 .TP

                 reply	other threads:[~2020-01-06 16:10 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=20200106161036.GA20145@delia \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    /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).