From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25142] New: Add optimization levels
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-25142-11298@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25142
Bug ID: 25142
Summary: Add optimization levels
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: ---
Both for the purposes of:
- bug analysis (for the dwz developer)
- bug workaround (for the dwz user)
it would be good to be able to somehow control the optimization level.
So, it would be possible to work around bugs in -O<n> by using -O<n-1>.
A possible optimization level distribution could be:
- O1: read in and write out, no duplicate DIE elimination:
- rewrite .debug_abbrev sections (merging abbreviation tables for different
CUs to eliminate duplicate table entries),
- use minimal reference encoding (f.i., rewrite DW_FORM_ref8 into
DW_FORM_ref4)
- O2: eliminate duplicate DIEs intra-CU
- O3: eliminate duplicate DIEs inter-CU
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2019-10-28 14:13 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-25142-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).