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: Sun, 21 Jan 2024 03:27:50 +0000	[thread overview]
Message-ID: <CALtZhhNy6puez4m63emWUbAh9kqHiz8DKwHd4AhkcC2rGgyaog@mail.gmail.com> (raw)
In-Reply-To: <CALtZhhOu+7i2HmC3+mBQUzKXV01Z2Ds+Q0Qbq5Y7+nSBWKpFeA@mail.gmail.com>

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

On Sat, Jan 20, 2024 at 7:44 PM Frederick Virchanza Gotham wrote:
>
> Am I right in thinking that I should be looking in the file
"bfd/linker.c", Line 1382, at the function
"_bfd_generic_link_add_one_symbol"


I'm still a bit clueless here, but here's what I've got so far, I'm able to
print out a list of all the classes that have both a vtable and a typeinfo:

Here's the link to Github showing the changes I've made so far, I've
created two new files 'polymorphism.h' and 'polymorphism.c'.


https://github.com/bminor/binutils-gdb/compare/5a75433a122ea1037ccb4e948332f4886e242911...healytpk:linker-vtable:master

  reply	other threads:[~2024-01-21  3:28 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
2024-01-20 19:44   ` Frederick Virchanza Gotham
2024-01-21  3:27     ` Frederick Virchanza Gotham [this message]
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=CALtZhhNy6puez4m63emWUbAh9kqHiz8DKwHd4AhkcC2rGgyaog@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).