From: Nick Alcock <nick.alcock@oracle.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com,
Alan Maguire <alan.maguire@oracle.com>
Subject: Re: [PATCH v2 2/2] ctf: work around binutils bug in ctf_link_add_cu_mapping()
Date: Tue, 01 Oct 2024 20:56:39 +0100 [thread overview]
Message-ID: <87y1371ts8.fsf@esperi.org.uk> (raw)
In-Reply-To: <20241001195452.223321-3-nick.alcock@oracle.com> (Nick Alcock's message of "Tue, 1 Oct 2024 20:54:52 +0100")
On 1 Oct 2024, Nick Alcock told this:
> The fact that we need to *implement* a hash table means that this adds
> almost a third to the total bulk of ctfarchive.c, none of which would be
> necessary if we could rely on a fixed binutils. But we won't be able to do
> that for a while...
"A while" has become less extreme, since when we move to CTFv4/BTF-in-toolchain
building, we'll have to bump the required binutils version anyway.
So btfarchive will not have this horrible patch in it. :)
--
NULL && (void)
prev parent reply other threads:[~2024-10-01 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:54 [PATCH v2 0/2 v6.12-rc1] CTF rework to work with modules.builtin.ranges Nick Alcock
2024-10-01 19:54 ` [PATCH v2 1/2] ctf: generate CTF information for the kernel Nick Alcock
2024-10-01 19:54 ` [PATCH v2 2/2] ctf: work around binutils bug in ctf_link_add_cu_mapping() Nick Alcock
2024-10-01 19:56 ` 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=87y1371ts8.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=alan.maguire@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.