[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

https://git.qemu.org/?p=qemu.git;a=commitdiff;h=3448d47b3172015006b7 ** Changed in: qemu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267 Title:

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

Great, thanks! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267 Title: armeb regression since qemu version 2.8 Status in QEMU: Fix Committed Bug description: Hi, I have noticed a

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

Fix committed and will be in 2.11.0 rc0. ** Changed in: qemu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267 Title: armeb regression since qemu

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg00155.html should fix this bug. ** Changed in: qemu Status: New => Incomplete ** Changed in: qemu Status: Incomplete => In Progress -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

I added printfs after each 'count++' statement, and here is what I got: qemu-2.7: ATOMIC_RELAXED OK ATOMIC_ACQUIRE OK ATOMIC_RELEASE OK ATOMIC_ACQ_REL OK ATOMIC_SEQ_CST OK ATOMIC_RELAXED OK ATOMIC_ACQUIRE OK ATOMIC_RELEASE OK ATOMIC_ACQ_REL OK ATOMIC_SEQ_CST OK ALL TESTS PASSED qemu-2.10.1:

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

** Attachment added: "instrumented executable" https://bugs.launchpad.net/qemu/+bug/1725267/+attachment/4979332/+files/atomic-exchange-4.exe -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

** Attachment added: "instrumented source testcase" https://bugs.launchpad.net/qemu/+bug/1725267/+attachment/4979333/+files/atomic-exchange-4.c -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

Re: [Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

On 20 October 2017 at 16:12, Christophe Lyon wrote: > I'll add some printfs and see what this says. I had a dig further in the logs and I suspect that we're either doing the two halves of strexd or the two halves of ldrexd wrong for linux-user bigendian.

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

Indeed I wish GCC tests printed information rather than just calling abort()... I'll add some printfs and see what this says. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267 Title: armeb

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

I think what's actually happening is that we're failing on one of the tests in main(). This would be much easier to diagnose if the test case code printed information about what it was doing and what the failed test case was... -- You received this bug notification because you are a member of

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

Ah, that's a false positive. We flipped the order we put entries in the AUXV in commit 7c4ee5bcc82e64, so the code divergence is just because now _dl_sysdep_start is processing the entries in the opposite order to what it used to. (The "addls pc, pc, r3, lsl #2" is jumping into the jump table for

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

I rather suspect something is going wrong when the dynamic loader attempts to paw through the ELF auxiliary vector... -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267 Title: armeb regression

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

Hi Christophe -- RTH posted a patchset yesterday which should fix this: https://lists.gnu.org/archive/html/qemu-devel/2017-10/msg04809.html -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

Oh, wait, different bug. Sorry for the noise... -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267 Title: armeb regression since qemu version 2.8 Status in QEMU: New Bug description: Hi,

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

** Attachment added: "execution trace with qemu-2.10.1" https://bugs.launchpad.net/qemu/+bug/1725267/+attachment/4978669/+files/trace.2.10.1 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267

[Qemu-devel] [Bug 1725267] Re: armeb regression since qemu version 2.8

** Attachment added: "execution trace with qemu-2.7" https://bugs.launchpad.net/qemu/+bug/1725267/+attachment/4978668/+files/trace.2.7 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725267