[m5-dev] Cron m5t...@zizzer /z/m5/regression/do-regression quick

2009-04-07 Thread Cron Daemon
* do-regression: qsub timed out, retrying locally * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed.

Re: [m5-dev] Memory corruption in m5 dev repository when using --trace-flags=ExecEnable

2009-04-07 Thread nathan binkert
Does this problem really have anything to do with tracing, or is it just more apparent with it? On Sat, Apr 4, 2009 at 1:49 PM, Gabe Black gbl...@eecs.umich.edu wrote: Oooh. I see what's broken. This is a result of my changes to allow delaying translation. What happens is that Stl_c

Re: [m5-dev] Memory corruption in m5 dev repository when using --trace-flags=ExecEnable

2009-04-07 Thread Gabriel Michael Black
It's broader than tracing and not caused by the tracing mechanism itself, but I think it will only show up with tracing. The pointer to the trace data will be NULL otherwise and the instruction won't attempt to use it. Nothing else that exists currently to my knowledge is in a position to