From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Add --devel options to usage message
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20191128140942.GA2321@delia> (raw)
Hi,
Mention --devel-options in usage message if compiled with -DDEVEL:
...
$ make CC="gcc -DDEVEL"
$ ./dwz -?
./dwz: Usage:
dwz [-v] [-q] [-l <COUNT|none>] [-L <COUNT|none>] [-h] [-m COMMONFILE] [-M NAME] [-r] [FILES]
dwz [-v] [-q] [-l <COUNT|none>] [-L <COUNT|none>] -o OUTFILE FILE
Development options:
--devel-trace
--devel-ignore-size
--devel-ignore-locus
--devel-save-temps
--devel-dump-dies
--devel-unoptimized-multifile
--devel-verify-edges
--devel-dump-edges
--devel-partition-dups-opt
--devel-die-count-method
...
Committed to trunk.
Thanks,
- Tom
Add --devel options to usage message
2019-11-28 Tom de Vries <tdevries@suse.de>
* dwz.c (usage): Mention --devel options.
---
dwz.c | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/dwz.c b/dwz.c
index 93fc9de..e4b2548 100644
--- a/dwz.c
+++ b/dwz.c
@@ -12996,8 +12996,22 @@ usage (void)
error (1, 0,
"Usage:\n"
" dwz " COMMON_OPTS " [-h] [-m COMMONFILE] [-M NAME] [-r] [FILES]\n"
- " dwz " COMMON_OPTS " -o OUTFILE FILE\n");
+ " dwz " COMMON_OPTS " -o OUTFILE FILE\n"
#undef COMMON_OPTS
+#if DEVEL
+ "Development options:\n"
+ " --devel-trace\n"
+ " --devel-ignore-size\n"
+ " --devel-ignore-locus\n"
+ " --devel-save-temps\n"
+ " --devel-dump-dies\n"
+ " --devel-unoptimized-multifile\n"
+ " --devel-verify-edges\n"
+ " --devel-dump-edges\n"
+ " --devel-partition-dups-opt\n"
+ " --devel-die-count-method"
+#endif
+ );
}
/* Print version and exit. */
reply other threads:[~2019-11-28 14:09 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=20191128140942.GA2321@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).