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 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
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
Hi,
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 just
choose
On Wednesday 2010-06-30 10:04, Jan Engelhardt wrote:
>sha256-sparcv9.s: Assembler messages:
>sha256-sparcv9.s:1849: Error: unaligned opcodes detected in executable
>segment
>
>---
> crypto/sha/sha256-sparcv9.s |1 +
> crypto/sha/sha512-sparcv9.s |1 +
> 2 fil
Hi,
openssl 0.9.8m was fine, but with 1.0.0 I get:
sha256-sparcv9.s: Assembler messages:
sha256-sparcv9.s:1849: Error: unaligned opcodes detected in executable
segment
I look around and noticed
http://rt.openssl.org/Ticket/Display.html?id=2190&user=guest&pass=guest
subsequently I came up wit
