From: Ulrich Drepper <drepper@redhat.com>
To: Philip Blundell <Philip.Blundell@pobox.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: small optimisation patch
Date: Wed, 24 Jul 2002 10:37:00 -0000 [thread overview]
Message-ID: <1027532251.3654.916.camel@myware.mynet> (raw)
In-Reply-To: <1027512900.3528.9.camel@mill>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
On Wed, 2002-07-24 at 05:15, Philip Blundell wrote:
> 2002-07-24 Philip Blundell <philb@gnu.org>
>
> * sysdeps/unix/arm/brk.S: Improve schedule.
> * sysdeps/unix/sysv/linux/arm/socket.S (PUSHARGS_1): Use more
> efficient instruction.
> (__socket): Optimize return sequence.
If you say this is better I'm going to believe you. The patch is in the
CVS archive. Thanks,
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-07-24 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 5:15 Philip Blundell
2002-07-24 10:37 ` Ulrich Drepper [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=1027532251.3654.916.camel@myware.mynet \
--to=drepper@redhat.com \
--cc=Philip.Blundell@pobox.com \
--cc=libc-hacker@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).