From: Felix Lee <flee@teleport.com>
Subject: Re: Byte-compiling the line specs
Date: Thu, 02 Nov 1995 17:26:46 -0800 [thread overview]
Message-ID: <199511030126.RAA01151@desiree.teleport.com> (raw)
In-Reply-To: Your message of "02 Nov 1995 16:38:26 EST." <tx1wx9ir92l.fsf@cujo.cygnus.com>
Ken Raeburn:
> If you turn gc back on, with a decent amount of allocation done (say,
> do it after you've gotten into the gnus Group buffer -- not a freshly
> started emacs), does princ come out on top again?
well, I was going to write a function to monitor garbage production,
but I got distracted into trying to optimize the funcall code.
(conclusion: i486 architecture doesn't have enough registers. I
managed to get about 10% speedup in funcalls mainly by taking the
fragment that handles subr calls and putting it in a separate
function, which is odd (since subr calls were also sped up). my
current guess is there's too much register pressure in Ffuncall.)
so, umm, I'll try gc monitoring soon. but really, the best test is to
write a full-blown format-string compiler and see how it performs in
live cases.
--
next prev parent reply other threads:[~1995-11-03 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199510311028.LAA06365@ssv4.dina.kvl.dk>
[not found] ` <199510311052.CAA16806@desiree.teleport.com>
[not found] ` <199510311413.PAA06470@ssv4.dina.kvl.dk>
1995-11-01 16:34 ` Ken Raeburn
1995-11-01 20:39 ` Felix Lee
1995-11-02 21:38 ` Ken Raeburn
1995-11-03 1:26 ` Felix Lee [this message]
1995-11-06 13:32 ` Lars Magne Ingebrigtsen
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=199511030126.RAA01151@desiree.teleport.com \
--to=flee@teleport.com \
/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 NNTP newsgroup(s).