looking in src/cpu/inorder/SConstruct, I see that the inorder model
wants to compile these files from O3:
Source('../o3/btb.cc')
Source('../o3/tournament_pred.cc')
Source('../o3/2bit_local_pred.cc')
Source('../o3/free_list.cc')
Source('../o3/rename_map)
Of
typo:
*SConscript
AND
there is a TraceFlag('FreeList') in there that can be whacked as well.
On Fri, Feb 20, 2009 at 9:00 AM, Korey Sewell ksew...@umich.edu wrote:
looking in src/cpu/inorder/SConstruct, I see that the inorder model
wants to compile these files from O3:
# HG changeset patch
# User Korey Sewell ksew...@umich.edu
# Date 1235138771 18000
# Node ID b6e4240c46e429bf99fefd0d61fef1465de86e49
# Parent 7a74edaa8741dd7fb541ef6d404dac3a9ebc86f9
imported patch inorder-alpha-port
diff -r 7a74edaa8741 -r b6e4240c46e4 src/arch/SConscript
---
Before this ALPHA port for the InOrder model can make it to a
changeset, there are few issues that need to be resolved in this
patch:
- Adding member get/setReg functions to FloatRegFile:
The inorder model would like to instantiate multiple int/float
register files and just one miscellaneous
changeset 6fd7648e1b8d in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=6fd7648e1b8d
description:
Remove unnecessary building of FreeList/RenameMap in InOrder. Clean-up
comments and O3 extensions InOrder Thread Context
diffstat:
5 files changed, 4 insertions(+), 111
I haven't looked at this incredibly closely yet, but I have a few
questions. First, what's this mt.hh file? You made it an ISA switched
header, but I don't see anything by that name being added. What does
it do?
Second, you shouldn't add a comment out include of cpu/inorder/cpu.hh.
Third,
Why is the in order model asking for O3 source files to be compiled in
the first place?
Gabe
Quoting Korey Sewell ksew...@umich.edu:
changeset 6fd7648e1b8d in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=6fd7648e1b8d
description:
Remove unnecessary building of
Because things like branch predictors, return address stacks, and
branch target buffers are good for use in a InOrder model.
And originally, the inorder model (originally called 'mixie') was
something that would work for both inorder and out-of-order models.
It's supposed to be flexible enough
This is the mail system at host daystrom.m5sim.org.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete
Ok. I figured it was something like that. Rather than use those in
place in O3, we might want to try to put them in a neutral spot and
then make them available for both. It would probably be confusing for
someone working on o3 if they ended up changing in order accidentally
in the process.
10 matches
Mail list logo
