>> SIGBUS normally denotes unaligned access, but instruction in qustion
>> pulls 16-bit value and effective address is 16-bit aligned...
>>> I just tried a test .S file with
>>>
>>> ldda[%sp+0+16]%asi, %f0
>>> ldda[%sp+0+8]%asi, %f0
>>> ldda[%sp+0+4]%asi, %f0
>>>
On Thursday 2010-07-01 11:31, Andy Polyakov wrote:
> SIGBUS normally denotes unaligned access, but instruction in qustion
> pulls 16-bit value and effective address is 16-bit aligned...
>>
>> I just tried a test .S file with
>>
>> ldda[%sp+0+16]%asi, %f0
>> ldda[%sp+0+8
On Thu, Jul 01, 2010, Rahul Srinivas wrote:
> Hi,
>
> Are there any plans to include SRP support (RFC 5054) in OpenSSL ? I saw
> that a patch was available at
> http://rt.openssl.org/Ticket/Display.html?id=1794 .
>
It is likely to be included at some point. That is a complex contribution
which
SIGBUS normally denotes unaligned access, but instruction in qustion
pulls 16-bit value and effective address is 16-bit aligned...
>
> I just tried a test .S file with
>
> ldda[%sp+0+16]%asi, %f0
> ldda[%sp+0+8]%asi, %f0
> ldda[%sp+0+4]%asi, %f0
> ldd
On Thursday 2010-07-01 10:09, Andy Polyakov wrote:
>>> SIGBUS normally denotes unaligned access, but instruction in qustion
>>> pulls 16-bit value and effective address is 16-bit aligned...
I just tried a test .S file with
ldda[%sp+0+16]%asi, %f0
ldda[%sp+0+8]%asi, %f0
Hi,
Are there any plans to include SRP support (RFC 5054) in OpenSSL ? I saw
that a patch was available at
http://rt.openssl.org/Ticket/Display.html?id=1794 .
Thanks,
-Rahul
__
OpenSSL Project htt
>>> Since the inclusion of sparcv9a-mont.s/.pl, I get a SIGBUS error when
>>> running bntest. Package is openssl 1.0.0 with sparcv9a on Linux 2.6.34
>>> with a sparcv9 environment (64-bit kernel, 32-bit userspace/v8/v8plus)
>>> on a sun4v US T1 CPU. I am aware of the FPU implications - openssl ju
On Wednesday 2010-06-30 16:04, Andy Polyakov wrote:
>> Since the inclusion of sparcv9a-mont.s/.pl, I get a SIGBUS error when
>> running bntest. Package is openssl 1.0.0 with sparcv9a on Linux 2.6.34
>> with a sparcv9 environment (64-bit kernel, 32-bit userspace/v8/v8plus)
>> on a sun4v US T1 CPU