From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix powl on i386/x86_64 [BZ #258] (take 2)
Date: Fri, 16 Jul 2004 17:09:00 -0000 [thread overview]
Message-ID: <40F80B44.9020305@redhat.com> (raw)
In-Reply-To: <20040715093555.GA9816@sunsite.ms.mff.cuni.cz>
Jakub Jelinek wrote:
> -4: fldl MO(one) // 1 : x
> +4: fld1 // 1 : x
I deliberately avoided the use of fld1 since all my measurements showed
it is slower. Please some some measurements of your own. As far as I
remember the only time when it paid off to use fld1 is when the fld was
the only memory operation and therefore it could be avoided to load the
PIC register.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
next prev parent reply other threads:[~2004-07-16 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 18:17 [PATCH] Fix powl on x86_64 [BZ #258] Jakub Jelinek
2004-07-15 11:51 ` [PATCH] Fix powl on i386/x86_64 [BZ #258] (take 2) Jakub Jelinek
2004-07-16 17:09 ` Ulrich Drepper [this message]
2004-07-19 10:19 ` Jakub Jelinek
2004-07-20 7:07 ` Ulrich Drepper
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=40F80B44.9020305@redhat.com \
--to=drepper@redhat.com \
--cc=jakub@redhat.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).