From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Subject: Re: [PATCH 2/2] libctf: impose an ordering on conflicting types
Date: Thu, 28 Apr 2022 12:08:10 +0100 [thread overview]
Message-ID: <87ee1hlb39.fsf@esperi.org.uk> (raw)
In-Reply-To: <20220427155130.238504-2-nick.alcock@oracle.com> (Nick Alcock via Binutils's message of "Wed, 27 Apr 2022 16:51:30 +0100")
On 27 Apr 2022, Nick Alcock via Binutils verbalised:
> When two types conflict and they are not types which can have forwards
> (say, two arrays of different sizes with the same name in two different
> TUs) the CTF deduplicator uses a popularity contest to decide what to
> do: the type cited by the most other types ends up put into the shared
> dict, while the others are relegated to per-CU child dicts.
(Installed. Original reporter says it fixes his bug -- internal or
there'd be a sourceware bug. Maybe I should ask for one in future
from internal reporters anyway, since it's user-visible?)
prev parent reply other threads:[~2022-04-28 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:51 [PATCH 1/2] libctf: add a comment explaining how to use ctf_*open Nick Alcock
2022-04-27 15:51 ` [PATCH 2/2] libctf: impose an ordering on conflicting types Nick Alcock
2022-04-28 11:08 ` Nick Alcock [this message]
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=87ee1hlb39.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@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).