On 8 April 2015 at 20:35, Peter Maydell wrote:
> Looking at the generated TCG, I suspect the problem
> is that tcg_gen_st_i64() isn't writing the two i32
> input values in the right order for the case where the
> host is a 32-bit bigendian system...
Yep. Commit 951c6300f7 out-of-lined the 32-bit-
On 8 April 2015 at 19:03, Andreas Färber wrote:
> I've resorted to setting up a ppc chroot on ppc64, and I can reproduce
> that qemu-system-i386 shows SeaBIOS okay, but qemu-system-x86_64
> immediately aborts with the quoted error.
Yeah, I can repro on the gcc compile farm's fedora ppc64 box.
(I
Am 08.04.2015 um 17:22 schrieb Peter Maydell:
> On 8 April 2015 at 16:19, Andreas Färber wrote:
>> Hello,
>>
>> With rcutorture fixed, I am still seeing the following failure in -rc2.
>> It is only for /x86_64/acpi/..., not for /i386/acpi/...; only on ppc
>> host, not on ppc64 or ppc64le (so not e
On Wed, 08 Apr 2015 17:19:21 +0200
Andreas Färber wrote:
> Hello,
>
> With rcutorture fixed, I am still seeing the following failure in -rc2.
> It is only for /x86_64/acpi/..., not for /i386/acpi/...; only on ppc
> host, not on ppc64 or ppc64le (so not endianness), nor on i586 (so not
> 32-bitne
On 8 April 2015 at 16:19, Andreas Färber wrote:
> Hello,
>
> With rcutorture fixed, I am still seeing the following failure in -rc2.
> It is only for /x86_64/acpi/..., not for /i386/acpi/...; only on ppc
> host, not on ppc64 or ppc64le (so not endianness), nor on i586 (so not
> 32-bitness alone).
Hello,
With rcutorture fixed, I am still seeing the following failure in -rc2.
It is only for /x86_64/acpi/..., not for /i386/acpi/...; only on ppc
host, not on ppc64 or ppc64le (so not endianness), nor on i586 (so not
32-bitness alone).
Alex was suggesting it may be a ppc TCG problem, but I'm no
