From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [PATCH] Add --devel-skip-producer
Date: Tue, 16 Mar 2021 22:27:49 +0100 [thread overview]
Message-ID: <20210316212749.GC3054@wildebeest.org> (raw)
In-Reply-To: <20210316141919.GA24635@delia>
Hi Tom,
On Tue, Mar 16, 2021 at 03:19:20PM +0100, Tom de Vries wrote:
> In PR27588 a test-case was reported where dwz did not optimize due
> to illegal DWARF produced by nasm:
> ...
> $ dwz libxul.so -o libxul.so.z
> dwz: libxul.so: loclistptr attribute, yet no .debug_loc section
> ...
>
> Add an option --devel-skip-producer <producer> such that we can filter out
> CUs coming from a particular producer, such that we have instead:
> ...
> $ readelf -wi libxul.so | grep DW_AT_producer \
> | sed 's/.*: //' | sort | uniq -c
> 176 clang LLVM (rustc version 1.50.0)
> 2 GNU AS 2.36.1
> 2 GNU C11 11.0.1 20210315 (experimental) <SNIP>
> 16 NASM 2.15.05
> 76 yasm 1.3.0
> $ dwz libxul.so -o libxul.so.z --devel-skip-producer NASM
> $ readelf -wi libxul.so.z | grep DW_AT_producer \
> | sed 's/.*: //' | sort | uniq -c
> 176 clang LLVM (rustc version 1.50.0)
> 2 GNU AS 2.36.1
> 2 GNU C11 11.0.1 20210315 (experimental) <SNIP>
> 76 yasm 1.3.0
> ...
>
> Any comments?
So this skips and then removes the whole CU (because we set die_remove
on the cu_die)?
It is useful as --devel option, but I would be against it as non-devel
option.
Cheers,
Mark
next prev parent reply other threads:[~2021-03-16 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 14:19 Tom de Vries
2021-03-16 21:27 ` Mark Wielaard [this message]
2021-03-17 10:46 ` Tom de Vries
2021-03-17 11:14 ` Mark Wielaard
2021-03-17 12:44 ` Tom de Vries
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=20210316212749.GC3054@wildebeest.org \
--to=mark@klomp.org \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=tdevries@suse.de \
/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).