[m5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick
scons: *** [build/X86_SE/m5.fast.unstripped] Error 1 * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-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-atomic passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing-dual passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual passed. * build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing-ruby passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/o3-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/inorder-timing passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/simple-atomic passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/o3-timing passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_CMP_token passed. * build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-timing-ruby passed. * build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/simple-atomic-mp passed. * build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-timing passed. * build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-atomic passed. * build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/o3-timing-mp passed. * build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-atomic passed. * build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/o3-timing passed. * build/SPARC_SE/tests/fast/quick/40.m5threads-test-atomic/sparc/linux/simple-timing-mp passed. * build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-timing passed.
Re: [m5-dev] Review Request: configs: set default cache params
--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/#review867 --- Looks like a good idea. configs/common/Options.py http://reviews.m5sim.org/r/485/#comment1236 Did you intend to change this default value too? If so, why? - Steve On 2011-02-13 19:13:33, Korey Sewell wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/ --- (Updated 2011-02-13 19:13:33) Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. Summary --- configs: set default cache params It's confusing (especially to new users), when you are setting some standard parameters (as defined in Options.py) and they aren't reflected in the simulations so we might as well link the settings in CacheConfig.py to those in Options.py Diffs - configs/common/CacheConfig.py 68a5b8bba293 configs/common/Options.py 68a5b8bba293 Diff: http://reviews.m5sim.org/r/485/diff Testing --- Thanks, Korey ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: configs: set default cache params
On 2011-02-15 05:24:20, Steve Reinhardt wrote: configs/common/Options.py, line 41 http://reviews.m5sim.org/r/485/diff/1/?file=10324#file10324line41 Did you intend to change this default value too? If so, why? The default in CacheConfig.py was 64kB, but the default in Options.py was 32kB, so I figured since CacheConfig.py was hardcoding the config anyway, that the default parameters should match what the previous hardcoded values were. - Korey --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/#review867 --- On 2011-02-13 19:13:33, Korey Sewell wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/ --- (Updated 2011-02-13 19:13:33) Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. Summary --- configs: set default cache params It's confusing (especially to new users), when you are setting some standard parameters (as defined in Options.py) and they aren't reflected in the simulations so we might as well link the settings in CacheConfig.py to those in Options.py Diffs - configs/common/CacheConfig.py 68a5b8bba293 configs/common/Options.py 68a5b8bba293 Diff: http://reviews.m5sim.org/r/485/diff Testing --- Thanks, Korey ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: configs: set default cache params
--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/#review869 --- I seem to have submitted a diff exactly like this Don't care who commits it if you want to go. The 64kB - 32kB thing preserves the previous default config (although it probably changes Ruby's) - Ali On 2011-02-13 19:13:33, Korey Sewell wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/ --- (Updated 2011-02-13 19:13:33) Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. Summary --- configs: set default cache params It's confusing (especially to new users), when you are setting some standard parameters (as defined in Options.py) and they aren't reflected in the simulations so we might as well link the settings in CacheConfig.py to those in Options.py Diffs - configs/common/CacheConfig.py 68a5b8bba293 configs/common/Options.py 68a5b8bba293 Diff: http://reviews.m5sim.org/r/485/diff Testing --- Thanks, Korey ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: configs: set default cache params
On 2011-02-15 07:26:20, Ali Saidi wrote: I seem to have submitted a diff exactly like this Don't care who commits it if you want to go. The 64kB - 32kB thing preserves the previous default config (although it probably changes Ruby's) Whoops. Sorry about that Ali. I had just got a new M5 user expressing some frustration to me about this and when we figured out the fix I just fast-forwarded the patch rather then go through the uncommitted review board posts. I guess I can clean up the patch from the above comments and commit a little later if everyone's on board with this. - Korey --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/#review869 --- On 2011-02-13 19:13:33, Korey Sewell wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/485/ --- (Updated 2011-02-13 19:13:33) Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. Summary --- configs: set default cache params It's confusing (especially to new users), when you are setting some standard parameters (as defined in Options.py) and they aren't reflected in the simulations so we might as well link the settings in CacheConfig.py to those in Options.py Diffs - configs/common/CacheConfig.py 68a5b8bba293 configs/common/Options.py 68a5b8bba293 Diff: http://reviews.m5sim.org/r/485/diff Testing --- Thanks, Korey ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] CacheController's wakeup function
While I don't know anything about this code it looks a little suspect
to me. Is there really a while (true) or is there some sort of while
(!empty)? Can the queues be appended to while you drain? If these
are both true, then you'll lose some of your enqueued messages.
Sorry if I'm uninformed.
I thought of this a moment ago, so I have not confirmed this empirically.
The CacheController's wakeup function includes a while loop, in which all
the queues are checked. Consider the Hammer protocol's L1 Cache Controller.
It has four incoming queues - trigger, response, forward, mandatory. The
wakeup function looks like this --
while(true)
{
process trigger queue;
process response queue;
process forward queue;
process mandatory queue;
}
where process means processing a single message from the queue.
I expect most of the messages to be present in the mandatory queue which
processes the actually loads and stores issued by the associated processor.
Would the following be better --
while(true) process trigger queue;
while(true) process response queue;
while(true) process forward queue;
while(true) process mandatory queue;
I do not expect any improvement in case of FS profiling as most of the
times, the mandatory queue has only one single message. But for testing
protocols using ruby random tester, I do expect some improvement. In FS
profile, after the histogram function (which takes about 8% time), the
wakeup function's execution time is the highest (about 5%). For ruby random
tester profile, the wakeup function takes about 11% of the time.
--
Nilay
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] CacheController's wakeup function
On Tue, 15 Feb 2011, nathan binkert wrote:
While I don't know anything about this code it looks a little suspect
to me. Is there really a while (true) or is there some sort of while
(!empty)? Can the queues be appended to while you drain? If these
are both true, then you'll lose some of your enqueued messages.
Sorry if I'm uninformed.
It is a while(true), and there is break statement which is executed in
case none of the queues have any messages. I am almost certain that the
incoming queues do not get appended to while they are being drained, I
would like Brad to confirm this.
--
Nilay
I thought of this a moment ago, so I have not confirmed this empirically.
The CacheController's wakeup function includes a while loop, in which all
the queues are checked. Consider the Hammer protocol's L1 Cache Controller.
It has four incoming queues - trigger, response, forward, mandatory. The
wakeup function looks like this --
while(true)
{
process trigger queue;
process response queue;
process forward queue;
process mandatory queue;
}
where process means processing a single message from the queue.
I expect most of the messages to be present in the mandatory queue which
processes the actually loads and stores issued by the associated processor.
Would the following be better --
while(true) process trigger queue;
while(true) process response queue;
while(true) process forward queue;
while(true) process mandatory queue;
I do not expect any improvement in case of FS profiling as most of the
times, the mandatory queue has only one single message. But for testing
protocols using ruby random tester, I do expect some improvement. In FS
profile, after the histogram function (which takes about 8% time), the
wakeup function's execution time is the highest (about 5%). For ruby random
tester profile, the wakeup function takes about 11% of the time.
--
Nilay
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick
I looked at this error, and it seems to be another 4.2.4 oddity. It builds fine with my normal compiler, but if I switch to that version I get a linking issue that doesn't make sense. Basically it complains that the constructor for the MicroPanic microop doesn't exist even though it's built into the decoder and is easy to find in decoder.cc. Perhaps it's not figuring out how to resolve types of arguments properly or something. If anyone else wants to look at it as well it's easy to reproduce if you use 4.2.4 which is on zizzer. Gabe On 02/15/11 00:15, Cron Daemon wrote: scons: *** [build/X86_SE/m5.fast.unstripped] Error 1 * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-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-atomic passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing-dual passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual passed. * build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing-ruby passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/o3-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/inorder-timing passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/simple-atomic passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/o3-timing passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_CMP_token passed. * build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-timing-ruby passed. *
Re: [m5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick
Perhaps we should upgrade zizzer? Nate On Tue, Feb 15, 2011 at 7:40 PM, Gabe Black gbl...@eecs.umich.edu wrote: I looked at this error, and it seems to be another 4.2.4 oddity. It builds fine with my normal compiler, but if I switch to that version I get a linking issue that doesn't make sense. Basically it complains that the constructor for the MicroPanic microop doesn't exist even though it's built into the decoder and is easy to find in decoder.cc. Perhaps it's not figuring out how to resolve types of arguments properly or something. If anyone else wants to look at it as well it's easy to reproduce if you use 4.2.4 which is on zizzer. Gabe On 02/15/11 00:15, Cron Daemon wrote: scons: *** [build/X86_SE/m5.fast.unstripped] Error 1 * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-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-atomic passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing-dual passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual passed. * build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing-ruby passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/o3-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/inorder-timing passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/simple-atomic passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/o3-timing passed. *
Re: [m5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick
I wouldn't complain, although someone might try to use 4.2.4 so it's not necessarily a bad thing to fix this stuff. Gabe On 02/15/11 11:50, nathan binkert wrote: Perhaps we should upgrade zizzer? Nate On Tue, Feb 15, 2011 at 7:40 PM, Gabe Black gbl...@eecs.umich.edu wrote: I looked at this error, and it seems to be another 4.2.4 oddity. It builds fine with my normal compiler, but if I switch to that version I get a linking issue that doesn't make sense. Basically it complains that the constructor for the MicroPanic microop doesn't exist even though it's built into the decoder and is easy to find in decoder.cc. Perhaps it's not figuring out how to resolve types of arguments properly or something. If anyone else wants to look at it as well it's easy to reproduce if you use 4.2.4 which is on zizzer. Gabe On 02/15/11 00:15, Cron Daemon wrote: scons: *** [build/X86_SE/m5.fast.unstripped] Error 1 * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-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-atomic passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing-dual passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual passed. * build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-timing-ruby passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/o3-timing passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/inorder-timing passed. * build/POWER_SE/tests/fast/quick/00.hello/power/linux/simple-atomic passed. *
Re: [m5-dev] Cron m5test@zizzer /z/m5/regression/do-regression quick
Ah, ok, I figured it out. There was an errant inline before the constructor in the .cc. I don't know if that's supposed to allow the compiler to eliminate that symbol from the resulting object file, but that seems to be what it was doing sometimes. I'll make sure that fix is doing what I expect it to and then commit it. Gabe On 02/15/11 12:16, Gabe Black wrote: I wouldn't complain, although someone might try to use 4.2.4 so it's not necessarily a bad thing to fix this stuff. Gabe On 02/15/11 11:50, nathan binkert wrote: Perhaps we should upgrade zizzer? Nate On Tue, Feb 15, 2011 at 7:40 PM, Gabe Black gbl...@eecs.umich.edu wrote: I looked at this error, and it seems to be another 4.2.4 oddity. It builds fine with my normal compiler, but if I switch to that version I get a linking issue that doesn't make sense. Basically it complains that the constructor for the MicroPanic microop doesn't exist even though it's built into the decoder and is easy to find in decoder.cc. Perhaps it's not figuring out how to resolve types of arguments properly or something. If anyone else wants to look at it as well it's easy to reproduce if you use 4.2.4 which is on zizzer. Gabe On 02/15/11 00:15, Cron Daemon wrote: scons: *** [build/X86_SE/m5.fast.unstripped] Error 1 * build/ALPHA_SE/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-atomic-mp passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-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-atomic passed. * build/ALPHA_SE/tests/fast/quick/30.eio-mp/alpha/eio/simple-timing-mp passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE_MESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MESI_CMP_directory passed. * build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_directory/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_CMP_token/tests/fast/quick/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_token passed. * build/ALPHA_SE_MOESI_hammer/tests/fast/quick/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing-dual passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-timing passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual passed. * build/ALPHA_FS/tests/fast/quick/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic passed. * build/ALPHA_FS/tests/fast/quick/10.linux-boot/alpha/linux/tsunami-simple-atomic passed. * build/MIPS_SE/tests/fast/quick/00.hello/mips/linux/simple-atomic passed. *
[m5-dev] changeset in m5: X86: Get rid of inline on the MicroPanic cons...
changeset 4ddb6f13cf13 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=4ddb6f13cf13
description:
X86: Get rid of inline on the MicroPanic constructor in decoder.cc.
This was making certain versions of gcc omit the function from the
object file
which would break the build.
diffstat:
src/arch/x86/isa/microops/debug.isa | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diffs (12 lines):
diff -r 13692327bb0b -r 4ddb6f13cf13 src/arch/x86/isa/microops/debug.isa
--- a/src/arch/x86/isa/microops/debug.isa Mon Feb 14 21:36:37 2011 -0800
+++ b/src/arch/x86/isa/microops/debug.isa Tue Feb 15 15:58:16 2011 -0800
@@ -98,7 +98,7 @@
}};
def template MicroDebugConstructor {{
-inline %(class_name)s::%(class_name)s(
+%(class_name)s::%(class_name)s(
ExtMachInst machInst, const char * instMnem, uint64_t setFlags,
std::string _message, uint8_t _cc) :
%(base_class)s(machInst, %(func)s, instMnem,
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Info: Clean up some info files.
I did a little poking around in Google, and I wasn't able to find much discussion about having the license in the files vs. out of it, how you're supposed to refer to a license in another file, etc. Do you guys know how that's supposed to work? Does anybody have an opinion or information on the pros/cons of moving the licenses out? What I've gathered so far is that putting the license in the file has the advantage of making it harder to disassociate the two since you have to purposefully chop up a file to take the license out. If we were to do that, we'd probably want to leave in the copyright holder, the copyright date range, a reference to the file with the license text, and maybe a brief mention of m5 and m5sim.org in case the file ends up on its own in the wild somewhere. Also, even superficial changes to how we're handling licenses like this might need to make the rounds with the lawyer types in all the organizations involved. Gabe On 02/14/11 21:35, Gabe Black wrote: Yeah, that would probably be overkill to do at build time. It would probably be useful for initially extracting licenses to put in a LICENSES directory though. Gabe On 02/14/11 13:12, nathan binkert wrote: I do have code that can parse source files to extract licenses. We could write a script that sucks out all of the licenses automatically (collapsing common pieces as necessary). Seems like it could be overkill though. Nate On Mon, Feb 14, 2011 at 8:54 PM, Gabe Black gbl...@eecs.umich.edu mailto:gbl...@eecs.umich.edu wrote: This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/486/ On February 14th, 2011, 6:48 a.m., *Nathan Binkert* wrote: LICENSE http://reviews.m5sim.org/r/486/diff/1/?file=10325#file10325line1 (Diff revision 1) 1 Copyright (c) 2000-2008 The Regents of The University of Michigan 1 Copyright (c) 2000-2011 The Regents of The University of Michigan Should we put everyone in here? (And all licenses?) On February 14th, 2011, 7:58 a.m., *Ali Saidi* wrote: I think we should as most of the license text says in, source and binary forms. The LICENSE file gets sucked into the simulator as a string and can be printed with a command line parameter, so it probably should have all of them. That would tie back into my idea of having a directory for all the different licenses which could then all be sucked in and output together. I didn't want to mess with the license stuff too much in this change since IANAL and I'm sure there will be some diversity of opinion here. - Gabe On February 13th, 2011, 11:47 p.m., Gabe Black wrote: Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. By Gabe Black. /Updated 2011-02-13 23:47:40/ Description Info: Clean up some info files. Get rid of RELEASE_NOTES since we no longer do releases, update some of the information in README, and update the date in LICENSE. Diffs * LICENSE (e8f4bb35dca9) * README (e8f4bb35dca9) * RELEASE_NOTES (e8f4bb35dca9) * src/SConscript (e8f4bb35dca9) * src/python/m5/main.py (e8f4bb35dca9) View Diff http://reviews.m5sim.org/r/486/diff/ ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Util: Get rid of the make_release.py script.
Did you mean you just wanted a second opinion on the RELEASE_NOTES change before this went in, or that you wanted a second opinion on this too? The former has happened but not the later. Are you ok with this going in now? Gabe On 02/14/11 06:50, Nathan Binkert wrote: This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/488/ Fine with me, though I'd like a second opinion. (I would like a second opinion on the RELEASE_NOTES change). - Nathan On February 14th, 2011, 1:22 a.m., Gabe Black wrote: Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. By Gabe Black. /Updated 2011-02-14 01:22:11/ Description Util: Get rid of the make_release.py script. Since we're not doing releases any more we don't really need this script. If we need it in the future, we can resurrect it from the history. Diffs * util/make_release.py (e8f4bb35dca9) View Diff http://reviews.m5sim.org/r/488/diff/ ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Info: Clean up some info files.
I think that they're short enough that we should leave them in. The point of the LICENSING file is so that people can find out about all of the copyright holders and different licenses in one place. I wasn't intending to get rid of licenses on files. Nate On Wed, Feb 16, 2011 at 12:07 AM, Gabe Black gbl...@eecs.umich.edu wrote: I did a little poking around in Google, and I wasn't able to find much discussion about having the license in the files vs. out of it, how you're supposed to refer to a license in another file, etc. Do you guys know how that's supposed to work? Does anybody have an opinion or information on the pros/cons of moving the licenses out? What I've gathered so far is that putting the license in the file has the advantage of making it harder to disassociate the two since you have to purposefully chop up a file to take the license out. If we were to do that, we'd probably want to leave in the copyright holder, the copyright date range, a reference to the file with the license text, and maybe a brief mention of m5 and m5sim.org in case the file ends up on its own in the wild somewhere. Also, even superficial changes to how we're handling licenses like this might need to make the rounds with the lawyer types in all the organizations involved. Gabe On 02/14/11 21:35, Gabe Black wrote: Yeah, that would probably be overkill to do at build time. It would probably be useful for initially extracting licenses to put in a LICENSES directory though. Gabe On 02/14/11 13:12, nathan binkert wrote: I do have code that can parse source files to extract licenses. We could write a script that sucks out all of the licenses automatically (collapsing common pieces as necessary). Seems like it could be overkill though. Nate On Mon, Feb 14, 2011 at 8:54 PM, Gabe Black gbl...@eecs.umich.edu wrote: This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/486/ On February 14th, 2011, 6:48 a.m., *Nathan Binkert* wrote: LICENSEhttp://reviews.m5sim.org/r/486/diff/1/?file=10325#file10325line1 (Diff revision 1) 1 Copyright (c) 2000-2008 The Regents of The University of Michigan 1 Copyright (c) 2000-2011 The Regents of The University of Michigan Should we put everyone in here? (And all licenses?) On February 14th, 2011, 7:58 a.m., *Ali Saidi* wrote: I think we should as most of the license text says in, source and binary forms. The LICENSE file gets sucked into the simulator as a string and can be printed with a command line parameter, so it probably should have all of them. That would tie back into my idea of having a directory for all the different licenses which could then all be sucked in and output together. I didn't want to mess with the license stuff too much in this change since IANAL and I'm sure there will be some diversity of opinion here. - Gabe On February 13th, 2011, 11:47 p.m., Gabe Black wrote: Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. By Gabe Black. *Updated 2011-02-13 23:47:40* Description Info: Clean up some info files. Get rid of RELEASE_NOTES since we no longer do releases, update some of the information in README, and update the date in LICENSE. Diffs - LICENSE (e8f4bb35dca9) - README (e8f4bb35dca9) - RELEASE_NOTES (e8f4bb35dca9) - src/SConscript (e8f4bb35dca9) - src/python/m5/main.py (e8f4bb35dca9) View Diff http://reviews.m5sim.org/r/486/diff/ ___ m5-dev mailing listm5-dev@m5sim.orghttp://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing listm5-dev@m5sim.orghttp://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Util: Get rid of the make_release.py script.
Both. I like both changes, but I figure that we should allow others to weigh in. On Wed, Feb 16, 2011 at 12:09 AM, Gabe Black gbl...@eecs.umich.edu wrote: Did you mean you just wanted a second opinion on the RELEASE_NOTES change before this went in, or that you wanted a second opinion on this too? The former has happened but not the later. Are you ok with this going in now? Gabe On 02/14/11 06:50, Nathan Binkert wrote: This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/488/ Fine with me, though I'd like a second opinion. (I would like a second opinion on the RELEASE_NOTES change). - Nathan On February 14th, 2011, 1:22 a.m., Gabe Black wrote: Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. By Gabe Black. *Updated 2011-02-14 01:22:11* Description Util: Get rid of the make_release.py script. Since we're not doing releases any more we don't really need this script. If we need it in the future, we can resurrect it from the history. Diffs - util/make_release.py (e8f4bb35dca9) View Diff http://reviews.m5sim.org/r/488/diff/ ___ m5-dev mailing listm5-dev@m5sim.orghttp://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Alpha: Import the alpha-system files into the m5 repository.
Actually, I think we want to run HG convert (from hg to hg) first and then do a pull -f after that. I can take a look at this tonight. Ok. I think I've got this right. I'm not going to put it on reviewboard since there are so many changes. I think I've done it right. Check out the outgoing patches in the repo on daystrom at /tmp/m5as. I'd like Ali and Gabe to take a look to see if I did anything wrong. If not, I'll merge it in. I did verify that it at least compiles. Nate ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Alpha: Import the alpha-system files into the m5 repository.
It appears fine to me. Ali On Feb 16, 2011, at 12:38 AM, nathan binkert wrote: Actually, I think we want to run HG convert (from hg to hg) first and then do a pull -f after that. I can take a look at this tonight. Ok. I think I've got this right. I'm not going to put it on reviewboard since there are so many changes. I think I've done it right. Check out the outgoing patches in the repo on daystrom at /tmp/m5as. I'd like Ali and Gabe to take a look to see if I did anything wrong. If not, I'll merge it in. I did verify that it at least compiles. Nate ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Util: Get rid of the make_release.py script.
--- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/488/#review871 --- Ship it! - Ali On 2011-02-14 01:22:11, Gabe Black wrote: --- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/488/ --- (Updated 2011-02-14 01:22:11) Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan Binkert. Summary --- Util: Get rid of the make_release.py script. Since we're not doing releases any more we don't really need this script. If we need it in the future, we can resurrect it from the history. Diffs - util/make_release.py e8f4bb35dca9 Diff: http://reviews.m5sim.org/r/488/diff Testing --- Thanks, Gabe ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
Re: [m5-dev] Review Request: Alpha: Import the alpha-system files into the m5 repository.
I don't really know anything about that repository other than we wanted to consolidate it, so if it's ok with Ali it's ok with me. Gabe On 02/15/11 22:51, Ali Saidi wrote: It appears fine to me. Ali On Feb 16, 2011, at 12:38 AM, nathan binkert wrote: Actually, I think we want to run HG convert (from hg to hg) first and then do a pull -f after that. I can take a look at this tonight. Ok. I think I've got this right. I'm not going to put it on reviewboard since there are so many changes. I think I've done it right. Check out the outgoing patches in the repo on daystrom at /tmp/m5as. I'd like Ali and Gabe to take a look to see if I did anything wrong. If not, I'll merge it in. I did verify that it at least compiles. Nate ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
[m5-dev] changeset in m5: Util: Get rid of the make_release.py script.
changeset c6ba129c2764 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=c6ba129c2764
description:
Util: Get rid of the make_release.py script.
Since we're not doing releases any more we don't really need this
script. If
we need it in the future, we can resurrect it from the history.
diffstat:
util/make_release.py | 222 ---
1 files changed, 0 insertions(+), 222 deletions(-)
diffs (226 lines):
diff -r 4ddb6f13cf13 -r c6ba129c2764 util/make_release.py
--- a/util/make_release.py Tue Feb 15 15:58:16 2011 -0800
+++ /dev/null Thu Jan 01 00:00:00 1970 +
@@ -1,222 +0,0 @@
-#!/usr/bin/env python
-# Copyright (c) 2006-2008 The Regents of The University of Michigan
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met: redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer;
-# redistributions in binary form must reproduce the above copyright
-# notice, this list of conditions and the following disclaimer in the
-# documentation and/or other materials provided with the distribution;
-# neither the name of the copyright holders nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-#
-# Authors: Ali Saidi
-# Steve Reinhardt
-# Nathan Binkert
-
-import os
-import re
-import shutil
-import sys
-import time
-
-from glob import glob
-from os import system
-from os.path import basename, dirname, exists, isdir, isfile, join as joinpath
-
-def mkdir(*args):
-path = joinpath(*args)
-os.mkdir(path)
-
-def touch(*args, **kwargs):
-when = kwargs.get('when', None)
-path = joinpath(*args)
-os.utime(path, when)
-
-def rmtree(*args):
-path = joinpath(*args)
-for match in glob(path):
-if isdir(match):
-shutil.rmtree(match)
-else:
-os.unlink(match)
-
-def remove(*args):
-path = joinpath(*args)
-for match in glob(path):
-if not isdir(match):
-os.unlink(match)
-
-def movedir(srcdir, destdir, dir):
-src = joinpath(srcdir, dir)
-dest = joinpath(destdir, dir)
-
-if not isdir(src):
-raise AttributeError
-
-os.makedirs(dirname(dest))
-shutil.move(src, dest)
-
-if not isdir('.hg'):
-sys.exit('Not in the top level of an m5 tree!')
-
-usage = '%s destdir release name' % sys.argv[0]
-
-if len(sys.argv) != 3:
-sys.exit(usage)
-
-destdir = sys.argv[1]
-releasename = sys.argv[2]
-release_dest = joinpath(destdir, 'release')
-#encumbered_dest = joinpath(destdir, 'encumbered')
-release_dir = joinpath(release_dest, releasename)
-#encumbered_dir = joinpath(encumbered_dest, releasename)
-
-if exists(destdir):
-if not isdir(destdir):
-raise AttributeError, '%s exists, but is not a directory' % destdir
-else:
-mkdir(destdir)
-
-if exists(release_dest):
-if not isdir(release_dest):
-raise AttributeError, \
- '%s exists, but is not a directory' % release_dest
-rmtree(release_dest)
-
-#if exists(encumbered_dest):
-#if not isdir(encumbered_dest):
-# raise AttributeError, \
-# '%s exists, but is not a directory' % encumbered_dest
-# rmtree(encumbered_dest)
-
-mkdir(release_dest)
-#mkdir(encumbered_dest)
-mkdir(release_dir)
-#mkdir(encumbered_dir)
-
-system('hg update')
-system('rsync -av --exclude .hg* --exclude build . %s' % release_dir)
-# move the time forward on some files by a couple of minutes so we can
-# avoid building things unnecessarily
-when = int(time.time()) + 120
-
-# make sure scons doesn't try to run flex unnecessarily
-#touch(release_dir, 'src/encumbered/eio/exolex.cc', when=(when, when))
-
-# get rid of non-shipping code
-#rmtree(release_dir, 'src/encumbered/dev')
-rmtree(release_dir, 'src/cpu/ozone')
-#rmtree(release_dir, 'src/mem/cache/tags/split*.cc')
-#rmtree(release_dir, 'src/mem/cache/tags/split*.hh')
-#rmtree(release_dir,
