Hi Jiayuan,
I've just briefly started looking at your patches. All of them compile
with the exception of SimpleMultiThreads.patch. When I attempt to
compile it I get the following errors:
In file included from build/ALPHA_FS/cpu/simple/atomic.hh:35,
from build/ALPHA_FS/cpu/simple/atomic.cc:37:
build/ALPHA_FS/cpu/simple/base.hh: In member function ‘void
BaseSimpleCPU::ev5_trap(Fault)’:
build/ALPHA_FS/cpu/simple/base.hh:450: error: ‘tc’ was not declared
in this scope
cc1plus: warnings being treated as errors
build/ALPHA_FS/sim/host.hh: At global scope:
build/ALPHA_FS/sim/host.hh:61: warning: ‘MaxTick’ defined but not
used
build/ALPHA_FS/arch/alpha/isa_traits.hh:164: warning:
‘AlphaISA::SyscallPseudoReturnReg’ defined but not used
distcc[24660] ERROR: compile build/ALPHA_FS/cpu/simple/atomic.cc on
@zizzer.pool/12 failed
scons: *** [build/ALPHA_FS/cpu/simple/atomic.o] Error 1
In file included from build/ALPHA_FS/cpu/simple/timing.hh:35,
from build/ALPHA_FS/cpu/simple/timing.cc:37:
build/ALPHA_FS/cpu/simple/base.hh: In member function ‘void
BaseSimpleCPU::ev5_trap(Fault)’:
build/ALPHA_FS/cpu/simple/base.hh:450: error: ‘tc’ was not declared
in this scope
cc1plus: warnings being treated as errors
build/ALPHA_FS/sim/host.hh: At global scope:
build/ALPHA_FS/sim/host.hh:61: warning: ‘MaxTick’ defined but not
used
build/ALPHA_FS/arch/alpha/isa_traits.hh:164: warning:
‘AlphaISA::SyscallPseudoReturnReg’ defined but not used
distcc[24671] ERROR: compile build/ALPHA_FS/cpu/simple/timing.cc on
@zizzer.pool/12 failed
scons: *** [build/ALPHA_FS/cpu/simple/timing.o] Error 1
In file included from build/ALPHA_FS/cpu/simple/base.cc:45:
build/ALPHA_FS/cpu/simple/base.hh: In member function ‘void
BaseSimpleCPU::ev5_trap(Fault)’:
build/ALPHA_FS/cpu/simple/base.hh:450: error: ‘tc’ was not declared
in this scope
cc1plus: warnings being treated as errors
build/ALPHA_FS/cpu/simple/base.cc: In constructor
‘BaseSimpleCPU::BaseSimpleCPU(BaseSimpleCPU::Params*)’:
build/ALPHA_FS/cpu/simple/base.cc:91: warning: unused variable
‘next_thread_id’
build/ALPHA_FS/sim/host.hh: At global scope:
build/ALPHA_FS/sim/host.hh:61: warning: ‘MaxTick’ defined but not
used
build/ALPHA_FS/arch/alpha/isa_traits.hh:164: warning:
‘AlphaISA::SyscallPseudoReturnReg’ defined but not used
distcc[24680] ERROR: compile build/ALPHA_FS/cpu/simple/base.cc on
@zizzer.pool/12 failed
scons: *** [build/ALPHA_FS/cpu/simple/base.o] Error 1
Is part of the patch missing?
Thanks,
Ali
On Jul 29, 2008, at 10:29 AM, Jiayuan Meng wrote:
> Hey Nathan and all,
>
> Thanks for the support! Here is a preview version, you can download
> the patches from:
> http://www.cs.virginia.edu/~jm6dg/fractal/m5patches.htm
>
> I'm open to any comments/suggestions.
> Let me know if you have any questions.
>
> Thanks!
>
> Jiayuan
>
> ----- Original Message -----
> From: "nathan binkert" <[EMAIL PROTECTED]>
> To: "M5 Developer List" <[email protected]>
> Sent: 2008年7月12日 7:50 AM
> Subject: Re: [m5-dev] submit patches: Mesh2D, directory
> coherence,and multithreading
>
>
>> Wow, that's fantastic. The best thing you can do is get your code
>> working with the new repository using mercurial and mercurial queues.
>> If you do that, then we can work with you to make sure that the code
>> meets all of the requirements (doesn't break things, is reasonably
>> organized, meets the style guidelines, etc.)
>>
>> Did you use a revision control system as you did your work?
>>
>> Thanks,
>> Nate
>>
>> 2008/7/11 jiayuan meng <[EMAIL PROTECTED]>:
>>> Dear all,
>>>
>>> I appreciate all your support to help me with M5. I really love
>>> it. I'm
>>> a graduate student working with Prof. Kevin Skadron at University of
>>> Virginia. And now,
>>> I'd like to submit patches to M5 that enables it to simulate CMP
>>> architecture.
>>>
>>> I have a mesh2D model that works well with an MSI directory
>>> coherence
>>> protocol.
>>> Both the interconnection and directory coherence models are
>>> extendable.
>>> Another patch is to support multithreading for simple CPUs. The
>>> cpu can
>>> switch to another HW thread context if it has a data access.
>>>
>>> However, atomic modes are not well tested. And I haven't considered
>>> checkpoints.
>>>
>>> The mercurial patches are based on changeset 5291:456a50cf2a67, a
>>> version
>>> after 2.0beta4 but before 2.0beta5.
>>> As an "external developer", how do you think I should submit the
>>> patches? An
>>> do you think it would be necessary to update the patches so they
>>> are based
>>> on a more recent changeset?
>>> If so, which changeset?
>>>
>>> Just hope it might be useful.
>>>
>>> Thanks!
>>>
>>> Jiayuan Meng
>>>
>>> ________________________________
>>> Need to know now? Get instant answers with Windows Live Messenger.
>>> IM on
>>> your terms.
>>> _______________________________________________
>>> m5-dev mailing list
>>> [email protected]
>>> http://m5sim.org/mailman/listinfo/m5-dev
>>>
>>>
>> _______________________________________________
>> m5-dev mailing list
>> [email protected]
>> http://m5sim.org/mailman/listinfo/m5-dev
>>
> _______________________________________________
> m5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/m5-dev
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev
