On 09/14/14 21:19, Chen Gang wrote:
On 9/15/14 11:03, Michael Eager wrote:
On 09/14/14 00:51, Chen Gang wrote:
Hello maintainers:
I also find some warnings during compiling microblaze, I also shall try
to fix them, but excuse me, I am not quite familiar the testsuite for
microblaze, could you provide any related information for it?
Hi Chen --
This is the gcc DejaGNU test suite. You can find info about DejaGNU
at http://www.gnu.org/software/dejagnu. There is also info about
testing GCC here: https://gcc.gnu.org/wiki/Testing_GCC
OK, thanks. I finished about x86_64 testsuite, and also tried microblaze
testsuite under x86_64 machine, but failed. Do I need any additional
information for microblaze testsuite?
I run tests using these options:
-mno-xl-soft-mul -mxl-barrel-shift -mcpu=v6.00.a
Configuring DejaGNU for cross-target testing requires creating a configuration
file describing the target board.
Rather than the standard "make check-gcc" described on the wiki
page and elsewhere, I use a script which sets some configuration
options and executes runtest directly. This uses a MicroBlaze processor
simulator called vpexec which was included with an older version of
Xilinx's EDK. Xilinx no longer supports vpexec.
You can use a hardware target board to test microblaze-gcc,
or a different simulator such as QEMU.
OK, thanks, I shall try Qemu (it is the additional chance for me to
familiar with Qemu).
And do you mean I need try testsuite under the related microblaze host (
e.g. Qemu microblaze simulator)?
After finish environments construction, I shall also try to test a patch
for "((void (*)(void)) 0)()" fixing.
Thanks.
--
Michael Eager ea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077