* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/minor-timing passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-atomic passed.
*
changeset 533ec854b2f1 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=533ec854b2f1
description:
stats: changes to x86 o3 fs and sparc fs regression tests.
diffstat:
tests/long/fs/10.linux-boot/ref/x86/linux/pc-o3-timing/stats.txt
| 54 +-
Hi all,
I was contemplating adding a src/mem/ram subdirectory and put the DRAM and
SimpleMemory files there.
I would also like to propose to move src/mem/protocol and src/mem/slicc into
the src/mem/ruby subdirectory as they are unique to Ruby. Does that make sense?
It might be worth creating
It might be worth thinking about the mem directory name in general as
well. A couple of the things in there are actually memory, but the
directory seems to be for a more general class of stuff. For instance,
interconnect isn't a type of memory, and it doesn't necessarily connected
to memory
I am fine with the proposed changes.
--
Nilay
On Tue, 11 Nov 2014, Andreas Hansson via gem5-dev wrote:
Hi all,
I was contemplating adding a src/mem/ram subdirectory and put the DRAM and
SimpleMemory files there.
I would also like to propose to move src/mem/protocol and src/mem/slicc into
I understand that protocol and slicc directories are logically underneath Ruby,
but I strongly content the small benefit of moving those directories does not
justify the work it will create downstream. There is a lot of code that works
on top of the current directory structure. I would really
Hi Brad,
I suspected there would be issues lurking. Mostly the benefit would be: 1)
clarity for people not familiar with the code base, and 2) work towards
building the entire memory system independent of the ISA (and put in a
libmem.a or similar). If moving the directories is causing significant
