From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25451] New: [dwz] Add --devel-no-import
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <bug-25451-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25451
Bug ID: 25451
Summary: [dwz] Add --devel-no-import
Product: dwz
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: nobody at sourceware dot org
Reporter: vries at gcc dot gnu.org
CC: dwz at sourceware dot org
Target Milestone: ---
It would be interesting to have a switch in dwz that:
- skips the generation of DW_TAG_import_unit/DW_AT_import for factored out
partial units.
- takes this into account in the heuristics
This would allows us:
- to measure what the impact is of having to generate
DW_TAG_import_unit/DW_AT_import.
- test behaviour of DWARF client in absence of those imports
[ Additionally, it would allow us to speed up create_import_tree (although that
could be achieved more easily by adding an option that skips the optimizations
there). ]
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2020-01-23 20:24 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=bug-25451-11298@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.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).