[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC t
From: |
Alex Bennée |
Subject: |
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests |
Date: |
Wed, 10 Jul 2019 13:59:17 -0000 |
Fixed by:
Subject: [PATCH for-4.1] tcg: Fix constant folding of INDEX_op_extract2_i32
Date: Tue, 9 Jul 2019 14:19:00 +0200
Message-Id: <address@hidden>
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1834496
Title:
Regressions on arm target with some GCC tests
Status in QEMU:
In Progress
Bug description:
Hi,
After trying qemu master:
commit 474f3938d79ab36b9231c9ad3b5a9314c2aeacde
Merge: 68d7ff0 14f5d87
Author: Peter Maydell <address@hidden>
Date: Fri Jun 21 15:40:50 2019 +0100
I found several regressions compared to qemu-3.1 when running the GCC
testsuite.
I'm attaching a tarball containing several GCC tests (binaries), needed
shared libs, and a short script to run all the tests.
All tests used to pass w/o error (one of them is verbose), but with a
recent qemu, all of them make qemu crash:
qemu: uncaught target signal 6 (Aborted) - core dumped
This was noticed with GCC master configured with
--target arm-none-linux-gnueabi
--with-mode arm
--with-cpu cortex-a9
and calling qemu with --cpu cortex-a9 (the script uses "any", this
makes no difference).
I have noticed other failures with arm-v8 code, but this is probably
the same root cause. Since it's a bit tedious to manually rebuild &
extract the testcases, I'd prefer to start with this subset, and I can
extract more if needed later.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1834496/+subscriptions