public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Frederick Virchanza Gotham <cauldwell.thomas@gmail.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Linker : Make a map of typeinfo to vtable
Date: Fri, 19 Jan 2024 22:52:52 +0000	[thread overview]
Message-ID: <CALtZhhP80W+LV3RjfB6UzKQjNwKAdrjKGg7EyAkn2w7W=kTShw@mail.gmail.com> (raw)
In-Reply-To: <CALtZhhMUxmUzWrHLB8xDA_0z0yjgZDLp8DqaofJvVk6rZznQ=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

On Friday, January 19, 2024, Frederick Virchanza Gotham wrote:

>
> Or, instead of waiting until after all the vtables and typeinfo's have
> been generated, I can populate my array as and when these things are
> generated (I imagine this might be easier than waiting until they're all
> generated, but whatever works).
>


Having thought about this a little more, I realise that it's the C++
compiler that generates the vtables and typeinfo's, and so, inside the
source code for the linker, what I'll need to do is:

(1) After all the object files have been loaded in, make a finite list of
all typeinfo's and vtables
(2) Generate my array that maps typeinfo's to vtable pointers
(3) Place my array somewhere inside a section inside the ELF binary
(4) Provide the two linker symbols __map_typeinfohash_vtable and
__map_typeinfohash_vtable_size

  reply	other threads:[~2024-01-19 22:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 22:29 Frederick Virchanza Gotham
2024-01-19 22:52 ` Frederick Virchanza Gotham [this message]
2024-01-20 19:44   ` Frederick Virchanza Gotham
2024-01-21  3:27     ` Frederick Virchanza Gotham
2024-01-21 22:35       ` Frederick Virchanza Gotham
2024-01-22 16:50 ` Michael Matz
2024-01-25 10:17   ` Frederick Virchanza Gotham
2024-01-25 23:02     ` Frederick Virchanza Gotham
2024-01-27 10:56       ` Frederick Virchanza Gotham

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='CALtZhhP80W+LV3RjfB6UzKQjNwKAdrjKGg7EyAkn2w7W=kTShw@mail.gmail.com' \
    --to=cauldwell.thomas@gmail.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).