<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/ppc, branch v1.4.1.1</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.4.1.1</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.4.1.1'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2006-06-19T03:12:20Z</updated>
<entry>
<title>Fix PPC SHA1 routine for large input buffers</title>
<updated>2006-06-19T03:12:20Z</updated>
<author>
<name>Paul Mackerras</name>
<email>paulus@samba.org</email>
</author>
<published>2006-06-18T23:25:16Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=b47f509ba59df5bd9a780745ca710272c6dd175b'/>
<id>urn:sha1:b47f509ba59df5bd9a780745ca710272c6dd175b</id>
<content type='text'>
The PPC SHA1 routine had an overflow which meant that it gave
incorrect results for input buffers &gt;= 512MB.  This fixes it by
ensuring that the update of the total length in bits is done using
64-bit arithmetic.

Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] PPC assembly implementation of SHA1</title>
<updated>2005-04-23T06:08:43Z</updated>
<author>
<name>Paul Mackerras</name>
<email>paulus@samba.org</email>
</author>
<published>2005-04-23T06:08:43Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=a6ef3518f9ac8a1c46a36c8d27173b1f73d839c4'/>
<id>urn:sha1:a6ef3518f9ac8a1c46a36c8d27173b1f73d839c4</id>
<content type='text'>
Here is a SHA1 implementation with the core written in PPC assembly.
On my 2GHz G5, it does 218MB/s, compared to 135MB/s for the openssl
version or 45MB/s for the mozilla version.

Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
