From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] Move slow path out of 'scm_get_byte_or_eof' et al
Date: Tue, 02 Apr 2013 17:59:02 +0200 [thread overview]
Message-ID: <878v50yldl.fsf@gnu.org> (raw)
In-Reply-To: 1364906601.26753.YahooMailNeo@web120403.mail.ne1.yahoo.com
Mike Gran <spk121@yahoo.com> skribis:
>> From: Mark H Weaver <mhw@netris.org>
>>
>>Andy suggested this. Okay to push to stable-2.0?
>
> Hi Mark,
>
> I can't imagine any possible way that this patch could make
> performance worse, but, it is in the very core of the ports.
>
> I don't think you can get away without at least a bit of
> profiling.
Yes, it’s most likely the Right Thing, but figures to confirm this would
be nice.
Ludo’.
next prev parent reply other threads:[~2013-04-02 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 9:59 [PATCH] Move slow path out of 'scm_get_byte_or_eof' et al Mark H Weaver
2013-04-02 12:43 ` Mike Gran
2013-04-02 15:59 ` Ludovic Courtès [this message]
2013-04-02 17:54 ` Mark H Weaver
2013-04-02 18:10 ` Mike Gran
2013-04-03 8:12 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878v50yldl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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).