On 12/29/2011 2:35 AM, Steve Reinhardt wrote:
I just updated my repository and ran these two commands:
scons -j 8 EXTRAS=../encumbered build/ALPHA_SE/tests/debug/quick
scons -j 8 build/ALPHA_SE/tests/opt/quick
and got no build errors and no test failures.
This was on our regression machine, so the EIO traces are in a common shared
directory there, not in
the repository. So it's no surprise that the EIO tests failed for you. Unless
you really want to
use EIO traces, I wouldn't worry about them. The fact that you had to copy the
headers is odd
though; I didn't need to do that.
I tried again, starting from checking out gem5 and encumbered, fresh from the
repo.
It seemed to make a difference to use a ../encumbered path in EXTRAS, and
perhaps
to use the specific name 'encumbered' (I had renamed the directory to
gem5-encumbered).
The build went through fine. My command line was:
scons CC=gcc44 CXX=g++44 EXTRAS=../encumbered build/ALPHA_SE/tests/debug/quick
The EIO tests indeed fail, but anagram isn't there so it's no surprise.
Where does it come from, by the way?
The memtest failure is more bothersome. Are you sure the test was rerun after
you updated to the
non-stable repository? If so, it might be worth doing a clean build (you can do
"scons -c", or just
"rm -rf build").
memtest still fails. Here is the exact contents of simerr:
gem5.debug: build/ALPHA_SE/mem/cache/cache_impl.hh:1257: void Cache<TagStore>::handleSnoop(Packet*,
typename TagStore::BlkType*, bool, bool, bool) [with TagStore = LRU]: Assertion
`!pkt->memInhibitAsserted()' failed.
Program aborted at cycle 409893
memtest-ruby passed.
Versions of programs are:
gcc44/g++44: 4.4.4
scons: 1.2.0
swig: 1.3.31 (I can install any particular one you like instead)
zlib: 1.2.3
m4: 1.4.5
python: 2.4.3
Regards -- Eliot
PS: Since the first, most basic, build is more or less passing,
what's the next thing up that I can test?
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
