From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Fix --import-optimize/--no-import-optimize
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <20200213142729.GA397@delia> (raw)
Hi,
Commit 50c5518 "Add --import-optimize/--no-import-optimize" actually
introduced --import-optimization/--no-import-optimization:
...
$ dwz hello --import-optimize 2>/dev/null; echo $?
1
$ dwz hello --import-optimization 2>/dev/null; echo $?
0
...
Fix this by making dwz accepting --import-optimize:
...
$ dwz hello --import-optimize 2>/dev/null; echo $?
0
...
Committed to trunk.
Thanks,
- Tom
Fix --import-optimize/--no-import-optimize
2020-02-13 Tom de Vries <tdevries@suse.de>
* dwz.c (dwz_options, dwz_common_options_help): Fix
--import-optimization/--no-import-optimization entries.
---
dwz.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/dwz.c b/dwz.c
index 86d35b0..f08bf4e 100644
--- a/dwz.c
+++ b/dwz.c
@@ -14487,9 +14487,9 @@ static struct option dwz_options[] =
{ "multifile-name", required_argument, 0, 'M' },
{ "relative", no_argument, 0, 'r' },
{ "version", no_argument, 0, 'v' },
- { "import-optimization",
+ { "import-optimize",
no_argument, &import_opt_p, 1 },
- { "no-import-optimization",
+ { "no-import-optimize",
no_argument, &import_opt_p, 0 },
#if DEVEL
{ "devel-trace", no_argument, &tracing, 1 },
@@ -14544,9 +14544,9 @@ static struct option_help dwz_common_options_help[] =
"Enable/disable one definition rule optimization." },
{ NULL, "odr-mode", "<basic|link>", "link",
"Set aggressiveness level of one definition rule optimization." },
- { NULL, "import-optimization", NULL, NULL,
+ { NULL, "import-optimize", NULL, NULL,
NULL },
- { NULL, "no-import-optimization", NULL, "Enabled",
+ { NULL, "no-import-optimize", NULL, "Enabled",
"Enable/disable optimization that reduces the number of"
" DW_TAG_imported_unit DIEs." }
};
reply other threads:[~2020-02-13 14:27 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=20200213142729.GA397@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).