[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
** 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/1834496 Title: Regressions on arm target with some GCC tests Status in QEMU: Fix Released Bug description: Hi, After trying qemu master: commit 474f3938d79ab36b9231c9ad3b5a9314c2aeacde Merge: 68d7ff0 14f5d87 Author: Peter Maydell 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
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
** 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/1834496 Title: Regressions on arm target with some GCC tests Status in QEMU: Fix Committed Bug description: Hi, After trying qemu master: commit 474f3938d79ab36b9231c9ad3b5a9314c2aeacde Merge: 68d7ff0 14f5d87 Author: Peter Maydell 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
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
I confirm this patch fixes the problem I reported. 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/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 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
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
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: <20190709121900.25644-1-richard.hender...@linaro.org> ** 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 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
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
I bisected a chunk of the errors to:
commit c6fb8c0cf704c4a1a48c3e99e995ad4c58150dab (refs/bisect/bad)
Author: Richard Henderson
Date: Mon Feb 25 11:42:35 2019 -0800
tcg/i386: Support INDEX_op_extract2_{i32,i64}
Signed-off-by: Richard Henderson
Specifically I think when tcg_gen_deposit_i32 handles the if (ofs + len
== 32) case.
--
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:
New
Bug description:
Hi,
After trying qemu master:
commit 474f3938d79ab36b9231c9ad3b5a9314c2aeacde
Merge: 68d7ff0 14f5d87
Author: Peter Maydell
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
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
** Changed in: qemu Assignee: (unassigned) => Richard Henderson (rth) -- 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: New Bug description: Hi, After trying qemu master: commit 474f3938d79ab36b9231c9ad3b5a9314c2aeacde Merge: 68d7ff0 14f5d87 Author: Peter Maydell 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
[Qemu-devel] [Bug 1834496] Re: Regressions on arm target with some GCC tests
** Tags added: arm testcases ** Tags removed: testcases ** Tags added: testcase -- 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: New Bug description: Hi, After trying qemu master: commit 474f3938d79ab36b9231c9ad3b5a9314c2aeacde Merge: 68d7ff0 14f5d87 Author: Peter Maydell 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
