* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
*
You mean a std::string? I guess I could disallow std::string as the
format string and only allow const char *. This probably isn't overly
burdensome. Though the question is, what was in the string that
caused it to break? In theory, it should work, unless there are a lot
of %s in it. And I
changeset 5e1863e9afa2 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=5e1863e9afa2
description:
Output: Verify output files are open after opening them.
diffstat:
2 files changed, 1 insertion(+), 1 deletion(-)
src/base/stats/text.cc |1 -
src/sim/serialize.cc |
It was in a set of microops I made which just panic/warn/etc with a string you
pass as the argument. It lets you use that sort of functionality at the
microcode level of abstraction which is fairly handy. Anyway, the string was
just a regular English sentence with a ., a ( and a ) if I remember
changeset c2fd66e6a919 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=c2fd66e6a919
description:
stats: Fix small bug pointed out by unit testing.
diffstat:
1 file changed, 1 deletion(-)
src/base/statistics.hh |1 -
diffs (13 lines):
diff -r 5e1863e9afa2 -r
changeset 6c1f3155f16b in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=6c1f3155f16b
description:
unittest: Cleanup unit tests. Follow style. Garbage Collect.
diffstat:
14 files changed, 54 insertions(+), 271 deletions(-)
src/unittest/bitvectest.cc| 16
changeset e08e65fd0f76 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=e08e65fd0f76
description:
unittest: Add unit tests to the scons framework.
Also fix the unit tests so they actually compile correctly.
diffstat:
9 files changed, 38 insertions(+), 61
Just to let all the hackers know, there's been src/unittest for a long
time, but it's been basically defunct for quite some time. The
directory had a bunch of small test programs for testing out specific
features of M5. I just made it use all of our SCons machinery. The
one current downside is
Implementing shadow sets for the rdpgpr and wrpgpr is going to take
more than regfile and decoder changes.
Those instructions mean read/write from/to the previous shadow set,
so that means I would need to edit the threadcontext (tcBase()) or
execcontext to include functions that would allow the
This is probably the best thing to do in the short term, but in the long
term you don't need to change the threadcontext to access other sets of
registers. SPARC does something pretty similar with register window
manipulating instructions which access multiple windows. You'd use
register
10 matches
Mail list logo
