From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, master, updated. v2.1.0-68-g79eb47e
Date: Sun, 26 Feb 2012 23:02:42 +0100 [thread overview]
Message-ID: <87vcmt8d8d.fsf@pobox.com> (raw)
In-Reply-To: <87mx852s3c.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 26 Feb 2012 22:38:15 +0100")
Hi!
On Sun 26 Feb 2012 22:38, ludo@gnu.org (Ludovic Courtès) writes:
> "Andy Wingo" <wingo@pobox.com> skribis:
>
>> commit 79eb47ea47650ef42c545931726277a7118a0210
>> Author: Andy Wingo <wingo@pobox.com>
>> Date: Fri Feb 24 23:05:02 2012 +0100
>>
>> port i/o optimizations for iso-8859-1
>>
> The problems with fast paths is that they become less fast when there
> are many of them.
>
> How does this change influence ‘benchmark-suite/benchmarks/ports.bm’?
Dunno, that wasn't my benchmark. It makes the web server go faster
(e.g. guile examples/web/debug-sxml.scm).
The reason it makes sense to optimize for this encoding is because it's
our narrow encoding. If we switch to utf-8 internally (for example),
this path doesn't make sense any more.
>> +/* Read an ISO-8859-1 codepoint (a byte) from PORT. On success, return
>> + *0 and set CODEPOINT to the codepoint that was read, fill BUF with
>> + *its UTF-8 representation, and set *LEN to the length in bytes.
>> + *Return `EILSEQ' on error. */
>
> ESTARS
:) Will fix.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-02-26 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1S13IJ-0005nd-Rk@vcs.savannah.gnu.org>
2012-02-26 21:38 ` [Guile-commits] GNU Guile branch, master, updated. v2.1.0-68-g79eb47e Ludovic Courtès
2012-02-26 22:02 ` Andy Wingo [this message]
2012-02-27 15:57 ` Ludovic Courtès
2012-02-27 18:05 ` Andy Wingo
2012-03-07 21:01 ` 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=87vcmt8d8d.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).