From: Sebastian Macke <sebastian@macke.de>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: openrisc@lists.openrisc.net, openrisc@lists.opencores.org,
qemu-devel@nongnu.org, proljc@gmail.com
Subject: Re: [Qemu-devel] [PATCH_v2 9/9] target-openrisc: Correct carry flagcheck of l.addc and l.addic test casess
Date: Tue, 22 Oct 2013 08:45:59 -0700 [thread overview]
Message-ID: <52669DB7.7020801@macke.de> (raw)
In-Reply-To: <p1k3h5ityr.fsf@linaro.org>
Hi Alex,
I am using a cross-compiling toolchain. It's the easiest way as I have
to compile the image for QEMU anyhow.
http://opencores.org/or1k/OpenRISC_GNU_tool_chain
Then it's just an "make && make test" in the corresponding
tests/tcg/openrisc folder.
Inside the virtual machine it would be a little bit more complicated.
You have to compile Linux with the initramfs containing the QEMU test
sources. Another storage device is currently not supported by the
OpenRISC QEMU emulator.
Sebastian
On 22/10/2013 1:35 AM, Alex Bennée wrote:
> sebastian@macke.de writes:
>
>> The test cases did not correctly test for the carry flag.
> Out of interest how are you building your test cases, cross-compiling or
> from within the emulated environment?
>
> I want to clean-up and resurrect the TCG tests but one of the challenges
> is all the non-x86 targets need to be built somehow.
>
> Cheers,
>
next prev parent reply other threads:[~2013-10-22 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 0:12 [Qemu-devel] [PATCH_v2 0/9] target-openrisc: Corrections and speed improvements Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 1/9] target-openrisc: Speed up move instruction Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 2/9] target-openrisc: Remove unnecessary code generated by jump instructions Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 3/9] target-openrisc: Remove executable flag for every page Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 4/9] target-openrisc: Correct wrong epcr register in interrupt handler Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 5/9] openrisc-timer: Reduce overhead, Separate clock update functions Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 6/9] target-openrisc: Correct memory bounds checking for the tlb buffers Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 7/9] target-openrisc: Separate branch flag from Supervision register Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 8/9] target-openrisc: Complete remove of npc and ppc variables Sebastian Macke
2013-10-22 0:12 ` [Qemu-devel] [PATCH_v2 9/9] target-openrisc: Correct carry flag check of l.addc and l.addic test cases Sebastian Macke
2013-10-22 8:35 ` [Qemu-devel] [PATCH_v2 9/9] target-openrisc: Correct carry flagcheck of l.addc and l.addic test casess Alex Bennée
2013-10-22 15:45 ` Sebastian Macke [this message]
2013-10-22 16:01 ` Max Filippov
2013-10-22 16:12 ` Alex Bennée
2013-10-22 16:15 ` Sebastian Macke
2013-10-23 6:52 ` Max Filippov
2013-10-23 3:47 ` [Qemu-devel] [PATCH_v2 0/9] target-openrisc: Corrections and speed improvements Jia Liu
2013-10-24 23:23 ` Sebastian Macke
2013-10-26 0:21 ` Jia Liu
2013-10-28 1:56 ` Sebastian Macke
2013-10-29 7:32 ` Jia Liu
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=52669DB7.7020801@macke.de \
--to=sebastian@macke.de \
--cc=alex.bennee@linaro.org \
--cc=openrisc@lists.opencores.org \
--cc=openrisc@lists.openrisc.net \
--cc=proljc@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).