From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27438] [dwz, odr, multifile] Multifile after odr not optimal
Date: Fri, 19 Feb 2021 12:10:03 +0000 [thread overview]
Message-ID: <bug-27438-11298-WBPHt2baRL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27438-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27438
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Alternatively, by ignoring locs, we get the desired optimization:
...
$ cp ../odr-struct 1; cp 1 2; ../dwz -m 3 1 2 --odr --devel-ignore-loc
$ readelf -wi 3 | egrep -A2 "DW_TAG_structure" | egrep
"DW_TAG|DW_AT_name|DW_AT_decl"
<1><14>: Abbrev Number: 15 (DW_TAG_structure_type)
<15> DW_AT_name : ccc
<1><2a>: Abbrev Number: 15 (DW_TAG_structure_type)
<2b> DW_AT_name : aaa
<1><46>: Abbrev Number: 15 (DW_TAG_structure_type)
<47> DW_AT_name : bbb
$ readelf -wi 1 | egrep -A2 "DW_TAG_structure" | egrep
"DW_TAG|DW_AT_name|DW_AT_decl"
$
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-19 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 8:45 [Bug default/27438] New: " vries at gcc dot gnu.org
2021-02-19 11:50 ` [Bug default/27438] " vries at gcc dot gnu.org
2021-02-19 12:08 ` vries at gcc dot gnu.org
2021-02-19 12:10 ` vries at gcc dot gnu.org [this message]
2021-02-19 12:24 ` vries at gcc dot gnu.org
2021-02-22 8:25 ` vries at gcc dot gnu.org
2021-02-22 15:12 ` vries at gcc dot gnu.org
2021-02-25 14:53 ` vries at gcc dot gnu.org
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-27438-11298-WBPHt2baRL@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).