From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] SH4 issue and fstat64
Date: Sat, 10 Jan 2009 00:07:05 +0100 [thread overview]
Message-ID: <761ea48b0901091507i30bf513fpef2cd8bdfb62e224@mail.gmail.com> (raw)
Hello,
after spending two hours to find and fix a simple hello world
program failed on sh4, I found the issue had already been found:
http://www.nabble.com/sh4-linux-user-emulation-on-an-x86_64-system-td19998891.html
I can confirm that the packing of the structure proposed by Takashi Yoshii
and Michael Trimarchi fixes the problem on my x86_64 system. I also
checked it does not break i386 qemu on my machine.
If someone needs a reproducer feel free to contact me.
This could have been frustrating, but now I know a little bit of sh4,
so that was not useless :-)
Laurent
next reply other threads:[~2009-01-09 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 23:07 Laurent Desnogues [this message]
2009-01-10 14:03 ` [Qemu-devel] Re: SH4 issue and fstat64 Måns Rullgård
-- strict thread matches above, loose matches on Subject: below --
2009-01-09 23:06 [Qemu-devel] " Laurent Desnogues
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=761ea48b0901091507i30bf513fpef2cd8bdfb62e224@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.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).