[apologies, I think I didn't reply from the right address, so this
wouldn't have got on the lists first time; plus I forgot to append
the complete log - which I'll do to Julius privately to avoid
spamming the list]
"Also sprach Julius Baxter:"
> majority of the tests are passing, it's probably in good health). Any
> chance you could pastebin the test failures?
=== libsim tests ===
Schedule of variations:
unix
Running target unix
Using ./config/unix.exp as board description file for target.
Running ./libsim.tests/int-edge.exp ...
FAIL: int-edge simple 1: hit EOF seeking match line 2
FAIL: int-edge simple 2: hit EOF seeking match line 2
FAIL: int-edge duplicated 1: hit EOF seeking match line 2
FAIL: int-edge duplicated 2: hit EOF seeking match line 2
FAIL: int-edge all upcall: hit EOF seeking match line 2
Running ./libsim.tests/int-level.exp ...
FAIL: int-level simple 1: hit EOF seeking match line 2
FAIL: int-level simple 2: hit EOF seeking match line 2
Running ./libsim.tests/jtag-basic.exp ...
Running ./libsim.tests/jtag-go-command-read.exp ...
Running ./libsim.tests/jtag-go-command-write.exp ...
Running ./libsim.tests/jtag-read-command.exp ...
Running ./libsim.tests/jtag-read-control.exp ...
Running ./libsim.tests/jtag-select-module.exp ...
Running ./libsim.tests/jtag-write-command.exp ...
Running ./libsim.tests/jtag-write-control.exp ...
Running ./libsim.tests/lib-iftest.exp ...
Running ./libsim.tests/upcalls.exp ...
FAIL: upcalls - basic: hit EOF seeking match line 2
FAIL: upcalls - misaligned: hit EOF seeking match line 2
=== libsim Summary ===
# of expected passes 253
# of unexpected failures 9
Test Run By ptb on Fri Oct 24 16:28:29 2014
Native configuration is i686-pc-linux-gnu
=== or1ksim tests ===
Schedule of variations:
unix
Running target unix
Using ./config/unix.exp as board description file for target.
Running ./or1ksim.tests/atomic.exp ...
Running ./or1ksim.tests/basic.exp ...
Running ./or1ksim.tests/cache.exp ...
Running ./or1ksim.tests/cbasic.exp ...
Running ./or1ksim.tests/cfg.exp ...
FAIL: cfg: hit EOF seeking match line 5
Running ./or1ksim.tests/dhry.exp ...
Running ./or1ksim.tests/dmatest.exp ...
FAIL: dmatest: hit EOF seeking match line 1
Running ./or1ksim.tests/eth.exp ...
FAIL: eth: hit EOF seeking match line 1
Running ./or1ksim.tests/except-test.exp ...
FAIL: except-test: hit EOF seeking match line 1
Running ./or1ksim.tests/exit.exp ...
Running ./or1ksim.tests/ext.exp ...
Running ./or1ksim.tests/fbtest.exp ...
Running ./or1ksim.tests/flag.exp ...
Running ./or1ksim.tests/fp.exp ...
Running ./or1ksim.tests/functest.exp ...
Running ./or1ksim.tests/inst-set-test.exp ...
Running ./or1ksim.tests/int-test.exp ...
FAIL: int-test: hit EOF seeking match line 1
Running ./or1ksim.tests/kbdtest.exp ...
FAIL: kbdtest: hit EOF seeking match line 1
Running ./or1ksim.tests/local-global.exp ...
Running ./or1ksim.tests/mem-test.exp ...
Running ./or1ksim.tests/mmu.exp ...
ERROR: Timeout
Running ./or1ksim.tests/mul.exp ...
FAIL: mul: hit EOF seeking match line 7
Running ./or1ksim.tests/mycompress.exp ...
FAIL: mycompress: hit EOF seeking match line 1005
Running ./or1ksim.tests/pcu.exp ...
Running ./or1ksim.tests/testfloat.exp ...
FAIL: testfloat: hit EOF seeking match line 1
Running ./or1ksim.tests/tick.exp ...
=== or1ksim Summary ===
# of expected passes 3654
# of unexpected failures 9
# of unresolved testcases 1
> Not exactly sure what "target specification" means, but I will guess
> that's a hangover from when or1ksim could target different
> architectures (I believe it supported DLX at some point, and various
> developmental versions
OK. No problem, then, except that --target seems to be used several
different ways in the configure scripts/docs: both for the native
architecture (my PC) that is the target of build, and the simulated
architecture (or1k-elf ?). That may be the start of a bug.
At any rate, a partial listing in that paragraph of what the values
might be would be a great help to understanding and clarity (you know,
"an example"!)... as would showing how to find them out and set them if
need be.
> > What is messed up here? The docs or my compile?
>
> Docs maybe a bit unclear. Compile is probably fine.
OK - that is a bit of a miracle, since I was guessing as to WHY I was
doing what I was doing.
I'm not at all sure how the or1ksim compile found the crosscompile
toolchain, or how I would have told it to if I hadn't had the
executables dir at the front of my PATH with exactly the binary names it
was looking for (or1k-elf-gcc, etc). That was about my 6th compile of
the toolchain.
Making the rationale clear in the docs would have helped, I think, as
well as future-proofing it.
I'm also compiling or1ksim-0.3,4,5. 0.3 didn't come near to compiling
(I forget why, but I'll do it again if somebody wants me to). 0.4
compiled but make check wouldn't run for reasons that again I can go and
look up. I am currently forcing my way slowly through the check
inserting an ="ranlib" in some Makefiles that lack it, and/or doing the
compile by hand and guesswork where it breaks. The makefiles also
thought my gcc has -mhard-div and -mhard-mul, and it doesn't. But they
also thought my gcc needed to be substituted by "compile" and weird
stuff brought in via config.h, apparently because the -Werror in the
configure script CCFLAGS causes gcc 4.7.2 to barf on some of the
compile tests (extra unused variables now are errors).
I did try remaking the makefiles with automake 1.14 (they were made with
1.11) but there are messes with INCLUDES being replaced by AM_CPPFLAGS
or some such. By the time I fought that through (anyone want source
files with correct relative paths in the references headers), the
simulator compiled, but the make check wouldn't run for much the same
reasosn as before, so I gave that up. The configure there does not seem
to have found the cross-compile toolchain binaries, but it does need
them.
Thanks for the input!
Peter
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc
