Hi again!
> > Bottom line. Expect version 1.1 implemention after this weekend:-)
Find version 1.2 attached. There're *no* machine code changes, but some
gas (GNU assembler) specific clean-ups, documentation concerning v9
(i.e. Solaris 7 in 64 bit mode) updates and minor preprocessing
rearrangemen
Hi! In comments to my bn_asm.sparc.v8plus.S recently posted to the list
I wrote:
> * Q. What about 64-bit kernels?
> * A. What about 'em? Just kidding:-) I unfortunately didn't have a
> *chance to test it yet, but the below code is 64-bit safe and you
> *shouldn't have any problem wit
Hi again!
> Bottom line. Expect version 1.1 implemention after this weekend:-) And
> OK, I can cut-n-paste together v8 version as well if you want me to...
Yeah, it's "after this weekend" now... Find two attached files. One is
SPARC v9 and another one is SPARC v8 implementations. Even though I
in
Hi again!
>
> And finally.
I slept over it and want you to disregard the following statement of
mine:
> ... It (*) doesn't make any difference to my UltraSPARC-specific
> implementation (as I exploit branches on register condition with
> prediction) ...
> (*) unrolling loops in below way
be
> >> O.K. Then I propose deleting (rather then recreating) all those
> >> automatically generated assembler versions, with appropriate changes
> >> to the configuration script.
>
> > i don't get it! has anybody read my posts? does it get through at all?
> > well, it must, because i myself get my
On Wed, Mar 31, 1999 at 04:03:04PM +0200, Andy Polyako wrotev:
>> O.K. Then I propose deleting (rather then recreating) all those
>> automatically generated assembler versions, with appropriate changes
>> to the configuration script.
> i don't get it! has anybody read my posts? does it get thro
> >> sparc.s is one of those gcc-produced files (which is also why
> >> solaris-sparc-gcc does not use it); but crypto/bn/bn_mulw.c is just an
> >
> > gcc hasn't produced better code that Sun's cc for SPARC in eternities. If we
> > want to distribute fast crypto routines, we should either hand-cre
On Tue, Mar 30, 1999 at 05:23:33PM -0500, [EMAIL PROTECTED] wrote:
> Bodo Moeller <[EMAIL PROTECTED]>:
>> sparc.s is one of those gcc-produced files (which is also why
>> solaris-sparc-gcc does not use it); but crypto/bn/bn_mulw.c is just an
> *Snort*
>
> gcc hasn't produced better code that S
> Bodo> Quite a few of these files are just the assember output from gcc since on
> Bodo> quite a few machines they are 2 times faster than the system compiler.
>
> gcc hasn't produced better code that Sun's cc for SPARC in eternities.
Not if you tell gcc to generate v8 (meaning hardwar
> "Bodo" == Bodo Moeller <[EMAIL PROTECTED]> writes:
Bodo> Albert Max Lai <[EMAIL PROTECTED]>:
...
Bodo> Quite a few of these files are just the assember output from gcc since on
Bodo> quite a few machines they are 2 times faster than the system compiler.
...
Bodo> sparc.s is one o
Howdy, kind people! Long one, huh?
> >
> >> Undefined first referenced
> >> symbol in file
> >> bn_mul_comba4 ../libcrypto.a(bn_mul.o)
> >> bn_mul_comba8 ../libcrypto.a(bn_mul.o)
> >> bn_sqr_comba4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
you have to also put in the machine architecture
Sigh... yes,I worked this out about .1 nanoseconds after sending
my reply. To compound my idiocy, I found I was linking with cc but I
had built OpenSSL with gcc.
It didn't like it much.
Jon
-
Bodo Moeller wrote:
>
> On Mon, Mar 29, 1999 at 05:20:36PM +0200, Bodo Moeller wrote:
>
> > What I don't understand though is the redifinition of BN_ASM in
> > openssl-0.9.2b/crypto/bn/Makefile: [...]
> > The real definition is in openssl-0.9.2b/Makefile.ssl: [...]
> > What's this redefinition a
On Mon, Mar 29, 1999 at 05:20:36PM +0200, Bodo Moeller wrote:
> What I don't understand though is the redifinition of BN_ASM in
> openssl-0.9.2b/crypto/bn/Makefile: [...]
> The real definition is in openssl-0.9.2b/Makefile.ssl: [...]
> What's this redefinition about, and why does the make procedu
Albert Max Lai <[EMAIL PROTECTED]>:
> On Fri, 26 Mar 1999 [EMAIL PROTECTED] wrote:
>> [...]
> I've been having the same problems under sparc as you have. I've moved
> down to SSLeay-0.8.1b (since I can get it to compile), but would like to
> use openssl. I haven't gotten any responses as to why
you have to also put in the machine architecture
perl ./Configure no-asm
example:
perl ./Configure no-asm solaris-sparc-sc4
On Mon, 29 Mar 1999, Jon Parry-McCulloch wrote:
>
> > perl ./Configure no-asm ... worked for me with 0.9.2b
> > on Solaris 2.6.
> You're right. That does make it co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any ideas?
Yes, I'm a moron.
Don't ask... it's _far_ too embarrassing.
Jon
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.0.2i
iQA/AwUBNv+izngWiDO86u4+EQIzKQCeLVGgBCnlvPw8HJiLWqfCWU+vK6AAnioE
XErPNztWJ1YPtSYBmCn5OVl1
=4r3V
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -Original Message-
From: Albert Max Lai [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, March 27, 1999 9:45 AM
To: [EMAIL PROTECTED]
Subject:Re: 0.9.2b Sparc problem
On Fri, 26 Mar 1999, Ed Kubaitis wrote:
> perl ./Configure
On Fri, 26 Mar 1999, Ed Kubaitis wrote:
> perl ./Configure no-asm ... worked for me with 0.9.2b
> on Solaris 2.6.
You're right. That does make it compile, but I'm still having one more
problem. I need to build the SSLeay libraries as object files (or shared
libraries). I am getting the following
perl ./Configure no-asm ... worked for me with 0.9.2b
on Solaris 2.6.
--
Ed Kubaitis - [EMAIL PROTECTED]
CCSO - University of Illinois at Urbana-Champaign
Albert Max Lai wrote:
>
> On Fri, 26 Mar 1999 [EMAIL PROTECTED] wrote:
>
> I've been having the same problems under
On Fri, 26 Mar 1999 [EMAIL PROTECTED] wrote:
I've been having the same problems under sparc as you have. I've moved
down to SSLeay-0.8.1b (since I can get it to compile), but would like to
use openssl. I haven't gotten any responses as to why this is happening,
or how fo fix this. If anyone has i
OpenSSL 0.9.2b, Solaris 2.5.1, SunPRO C 5.0, ./Configure solaris-sparc-sc4
All of the SunPRO C Configure entries suffer from the delusion that
asm/sparc.o serves some useful purpose. This, of course, leads to:
cc -o openssl -DMONOLITH -I../include -xO5 -Xa -DB_ENDIAN openssl.o verify.o
asn1pars
22 matches
Mail list logo
