On Fri, 24 Oct 2014 17:44:09 -0400 Peter Gavin <[email protected]> wrote:
> Hm... I wonder if that's happening because you're compiling for > 32-bits. Is there a way you can try it out on 64-bits to see if > that's causing the test to fail? No need to recompile the whole > toolchain if you're doing this on a 64-bit host, recompiling or1ksim > should be enough. I can try that (AMD machine ...). > One other thing, I haven't updated my copy of the toolchain in a bit, > and it doesn't include Stefan's atomic instruction patches. I'll > have to recompile it if I'm going to test that properly (my gas > version won't assemble the atomic instructions). Could you perhaps > try backing that patch out of or1ksim to see if that has any effect? > You'd basically just need to do git checkout fdd700a in the or1ksim > tree, then recompile it. Also possible. I'll let you know ... no, no difference, but I'm not a git user and it appeared to me that that git command did nothing much [but it does, it's just quiet .. see lower down this post] % git checkout fdd700a M doc/or1ksim.info M doc/version.texi HEAD is now at fdd700a... fix l.div with dividend 0x8000000 and divisor 0xffffffff I suspect the one before is what git needs. % git checkout ad80538cdfc06230e263d8e940925a6d4cc1b3d5 M doc/or1ksim.info M doc/version.texi Previous HEAD position was fdd700a... fix l.div with dividend 0x8000000 and divisor 0xffffffff HEAD is now at ad80538... is-div-test.S: remove wrong code introduced in previous patch I still don't see anything happening from git - just those "M" lines. And no difference in the tests. I really don't know how to use git! I'm not convinced from the feel that there are any real changes ... but no, there are some: % diff -ur ../or1ksim-or1k-master . | diffstat | grep -v Makefile | grep -v configure ../or1ksim-or1k-master/testsuite/or1ksim.tests/atomic.exp |only ../or1ksim-or1k-master/testsuite/site.bak |only ../or1ksim-or1k-master/testsuite/test-code-or1k/atomic |only ./.git |only ./ChangeLog | 27 ./config.log | 17 ./config.status | 16 ./cpu/common/abstract.c | 14 ./cpu/common/execute.h | 3 ./cpu/or1k/except.c | 3 ./cpu/or32/insnset.c | 43 ./cpu/or32/or32.c | 4 ./cpu/or32/simpl32-defs.h | 2 ./cuc/load.c | 2 ./doc/stamp-vti | 4 ./doc/version.texi | 4 ./testsuite/ChangeLog | 12 ./testsuite/libsim.log | 1118 - ./testsuite/libsim.sum | 2 ./testsuite/or1ksim.log |10911 +------------- ./testsuite/or1ksim.sum | 84 ./testsuite/or1ksim.tests/inst-set-test.exp | 12 ./testsuite/site.exp | 2 ./testsuite/test-code-or1k/ChangeLog | 18 ./testsuite/test-code-or1k/autom4te.cache |only ./testsuite/test-code-or1k/config.log | 155 ./testsuite/test-code-or1k/config.status | 19 ./testsuite/test-code-or1k/inst-set-test/is-div-test.S | 18 ./testsuite/test-code-or1k/libtool | 2 106 files changed, 2978 insertions(+), 11005 deletions(-) You'll have to look harder for the origin of those two fails for the sim executable. Peter _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
