That would probably work.
Ali On 29.09.2013 22:43, Steve Reinhardt wrote: > I see... maybe we can add a flag to suppress that output, and then use that > flag in the switcheroo test? > > Steve > > On Sun, Sep 29, 2013 at 8:18 PM, Ali Saidi <[email protected]> wrote: > >> It's not really the switcher tests, is that simulation.py prints every time the CPU changes occurs. I'm not sure how to fix one without getting rid of that. Ali On Sep 28, 2013, at 2:35 PM, Steve Reinhardt <[email protected]> wrote: >> >>> I noticed that *by far* the bulk of the changes (in terms of line count) were in the simout files for the switcheroo tests, which print the cycle number on every switch, and thus are sensitive to small changes in >> timing. >> >>> These files are very large in general... in fact, I had to temporarily disable the 400K 'large file limit' on the server to be able to push >> these tests to not be so verbose by default, then update the reference outputs with the (much smaller) result >> >>> gmail.com">[email protected]> wrote: >> :5px; width:100%">changeset afd9ea6101d9 in /z/repo/gem5 details: > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev [1] Links: ------ [1] http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
