From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Add --devel-verify-dups (2)
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20191209114743.GA20222@delia> (raw)
Hi,
In commit 1bd7570 "Add --devel-verify-dups" I forgot to add in the actual
option handling.
Add the missing part.
Committed to trunk.
Thanks,
- Tom
Add --devel-verify-dups (2)
2019-12-09 Tom de Vries <tdevries@suse.de>
* dwz.c (dwz_options, usage): Add --devel-verify-dups entry.
---
dwz.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/dwz.c b/dwz.c
index 1a1186d..9f28186 100644
--- a/dwz.c
+++ b/dwz.c
@@ -13342,6 +13342,7 @@ static struct option dwz_options[] =
{ "devel-unoptimized-multifile",
no_argument, &unoptimized_multifile, 1 },
{ "devel-verify-edges",no_argument, &verify_edges_p, 1 },
+ { "devel-verify-dups", no_argument, &verify_dups_p, 1 },
{ "devel-dump-edges", no_argument, &dump_edges_p, 1 },
{ "devel-partition-dups-opt",
no_argument, &partition_dups_opt, 1 },
@@ -13369,6 +13370,7 @@ usage (void)
" --devel-save-temps\n"
" --devel-dump-dies\n"
" --devel-unoptimized-multifile\n"
+ " --devel-verify-dups\n"
" --devel-verify-edges\n"
" --devel-dump-edges\n"
" --devel-partition-dups-opt\n"
reply other threads:[~2019-12-09 11:47 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=20191209114743.GA20222@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).