From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: Re: cos changes
Date: Mon, 28 Sep 2009 16:28:00 -0000 [thread overview]
Message-ID: <4AC0E436.2040209@sebabeach.org> (raw)
In-Reply-To: <20090928025041.2D5CD6E3D9@sebabeach.org>
Doug Evans wrote:
> Hi.
>
> I checked in a few changes to cos (cgen's object system).
> Virtual methods (as implemented) are gone, as is multiple inheritance.
> Plus a few other simplifications.
>
> In trying to have something that is portable I now think the thing to do
> is keep cos, albeit greatly simplified.
> There's a few more cleanups I want to do, plus more portability work,
> but hopefully that's it for now.
>
One data point I found interesting.
Generating m32c opcodes files before /after (on my machine) went from ~8
min -> ~5 min.
[For completeness sake, it's still too slow, and there are other better
ways to improve this. And there were still untapped ways at improving
the existing cos implementation. But I thought the data was interesting
so I'm passing it on.]
prev parent reply other threads:[~2009-09-28 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 2:50 Doug Evans
2009-09-28 16:28 ` Doug Evans [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=4AC0E436.2040209@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@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).