From: "jakub at redhat dot com" <firstname.lastname@example.org>
Subject: [Bug default/27480] New: Consider .debug_loclists optimizations
Date: Sat, 27 Feb 2021 10:45:45 +0000 [thread overview]
Message-ID: <email@example.com/bugzilla/> (raw)
Bug ID: 27480
Summary: Consider .debug_loclists optimizations
Assignee: nobody at sourceware dot org
Reporter: jakub at redhat dot com
CC: dwz at sourceware dot org
Target Milestone: ---
As mentioned in
GCC for non-partitioned TUs emits DW_LLE_offset_pair which will be likely a win
for small TUs, but might be too large for very large TUs - both operands are
offsets from base, so say 256KB TU would near the end of the .text section have
3 bytes for each of the operands, and for 2MB TU even 4 bytes for each operand.
Compared to one DW_LLE_base_address with 4 (or 8) byte operand and then
DW_LLE_offset_pair with likely just 1 byte operands.
Similarly, for partitioned TUs, we emit DW_LLE_start_end or DW_LLE_base_address
+ DW_LLE_offset_pair, but maybe DW_LLE_offset_pair would be smaller.
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-27 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 10:45 jakub at redhat dot com [this message]
2021-03-02 7:51 ` [Bug default/27480] " vries at gcc dot gnu.org
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).