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: Wed, 17 Mar 2021 12:14:29 +0100 [thread overview]
Message-ID: <223c53f1c8c2c93dfc49e16ea00c7a3c015a746b.camel@klomp.org> (raw)
In-Reply-To: <0956da43-2f83-83a8-1da2-63916d4b49f6@suse.de>
Hi Tom,
On Wed, 2021-03-17 at 11:46 +0100, Tom de Vries wrote:
> On 3/16/21 10:27 PM, Mark Wielaard wrote:
> > It is useful as --devel option, but I would be against it as non-
> > devel
> > option.
>
> Could you explain in more detail why you would be against this as a
> non-devel option? F.i., I'm curious, is it an abstract objection, or
> do
> you foresee concrete problems with the approach?
Of course I would never call my own objections abstract :)
But it partly is. I think it is questionable if we have to rely on the
producer string to do the right thing. But specifically just dropping a
whole CU DIE tree seems the wrong thing to do (what about the ranges,
loclists, stmt_lists left behind for example).
Cheers,
Mark
next prev parent reply other threads:[~2021-03-17 11:14 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
2021-03-17 10:46 ` Tom de Vries
2021-03-17 11:14 ` Mark Wielaard [this message]
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=223c53f1c8c2c93dfc49e16ea00c7a3c015a746b.camel@klomp.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).