From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: [EGCS] Re: double alignment patch for x86
Date: Mon, 18 Aug 1997 13:29:01 -0000 [thread overview]
Message-ID: <199708180820.KAA19291@radagast.iuk.tu-harburg.de> (raw)
Message-ID: <19970818132901.25KnTYF6Xs-Nl4Z0eEims3oD6e-SqBfhWvxwfeYfPZc@z> (raw)
In-Reply-To: Sun, 17 Aug 97 22:35:54 +0200"
>>>>> "Toon" == Toon Moene <toon@moene.indiv.nluug.nl> writes:
>> It takes 2 additional cycles per double access.. this can sum up
>> to 30% runtime penalty on important algorithms like matrix
>> multiply...
Toon> This is on a Pentium ?
It's about right for daxpy on my pentium.
-- Dave (recycled physicist)
next reply other threads:[~1997-08-18 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-18 8:22 Thomas Hiller [this message]
1997-08-18 9:11 ` Will egcs support MachTen? N8TM
1997-08-18 9:11 ` GCC Projects? Bernd Schmidt
1997-08-18 9:11 ` prototyping Andi Kleen
1997-08-18 10:42 ` front end interface Clive Nicolson
1997-08-18 13:29 ` [EGCS] Re: double alignment patch for x86 Dave Love
1997-08-18 18:22 2 (small?) problems Fergus Henderson
1997-08-18 18:22 prototyping Per Bothner
1997-08-18 18:22 ` 2 (small?) problems Jim Meyering
1997-08-19 2:36 Ian Lance Taylor
1997-08-25 23:43 Jim Wilson
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=199708180820.KAA19291@radagast.iuk.tu-harburg.de \
--to=d.love@dl.ac.uk \
--cc=egcs@cygnus.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).