From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: philmd@linaro.org
Cc: qemu-devel@nongnu.org, richard.henderson@linaro.org
Subject: microblazeel-linux-user regression
Date: Sun, 24 Aug 2025 22:18:32 +0200 [thread overview]
Message-ID: <aKtzmNHYSFwf2TQI@zapote> (raw)
Hi Phil,
While trying microblazeel-linux-user on the master branch I hit this:
$ qemu-microblazeel ctest
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
Bisect found this commit:
415aae543edad19eda8f66955dde386c7fd7c680 is the first bad commit
commit 415aae543edad19eda8f66955dde386c7fd7c680
Author: Philippe Mathieu-Daudé <philmd@linaro.org>
Date: Tue Sep 24 23:45:54 2024 +0200
target/microblaze: Consider endianness while translating code
Consider the CPU ENDI bit, swap instructions when the CPU
endianness doesn't match the binary one.
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20241105130431.22564-17-philmd@linaro.org>
target/microblaze/cpu.h | 7 +++++++
target/microblaze/translate.c | 5 +++--
2 files changed, 10 insertions(+), 2 deletions(-)
bisect found first bad commit
It looks like we're getting the endianness wrong in this case.
This works:
qemu-microblazeel -cpu microblaze,little-endian=on ctest
Was this intended while moving towards single binary?
If yes, I wonder if we also should change the default to little-endian.
Big-endian MB is discontinued from newer Microblaze versions.
I'd rather have to type -cpu microblaze,little-endian=off for big-endian.
Cheers,
Edgar
next reply other threads:[~2025-08-24 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 20:18 Edgar E. Iglesias [this message]
2025-09-30 10:24 ` microblazeel-linux-user regression Philippe Mathieu-Daudé
2025-10-02 8:31 ` Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aKtzmNHYSFwf2TQI@zapote \
--to=edgar.iglesias@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).