From: Cut Hour <cuthour@gmail.com>
To: binutils@sourceware.org
Subject: Re: Old story (30 years ago)
Date: Wed, 18 Jan 2023 00:28:37 +0900 [thread overview]
Message-ID: <3a337aa1-032b-1d19-8c42-db8a117841c0@gmail.com> (raw)
In-Reply-To: <328bee46-edc9-3e33-abf6-42d907ba60b0@redhat.com>
Hi, Nick,
>> I don't know very well about Clang or LLVM. So this might be
>> already out of date. Any need for this extended ELF do you think?
>
> I would say probably not. Obviously support for high level languages
> is already working with ELF as it is. So if it isn't broken - don't
> fix it.
It might be broken if we want to only recompile basically touched source
files like the programming in C. Or is this cleared in LLVM?
> This is not to say that exploring the idea is not worthwhile. It
> might produce some interesting results. But I would be hesitant about
> applying it to a generic tool like the linker without a real need.
I myself had needed it. My plan was like this. Every instance has a
ptr to its class. Every class has a method table (array of ptr to
function). All methods are called via a ptr in the method table.
The syntax is almost the same as ObjC. Binutils (for the structured
programming) is what makes this simplest OO language so hard to come
by. Neither C++ nor ObjC nor Java pointed that out. Again, is this
cleared in LLVM?
next prev parent reply other threads:[~2023-01-17 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:21 Cut Hour
2023-01-17 13:55 ` Nick Clifton
2023-01-17 15:28 ` Cut Hour [this message]
2023-01-24 13:27 ` Nick Clifton
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=3a337aa1-032b-1d19-8c42-db8a117841c0@gmail.com \
--to=cuthour@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).