2009/3/18 Korey Sewell :
>
> "1. Calculate EA
> 2. Initiate access
> 3. Complete access
>
> Right now execute() does 1-3, initiateAcc() does 1-2, completeAcc()
> does 3, EAComp::execute() does 1, and MemAcc::execute() does 2-3."
>
> - I agree that it makes sense to just write a separate function th
- In saying we should wack EAComp and MemAcc, I neglected to mention my
solution which was to create another function similar to "initiateAcc" and
"completeAcc" called "addrGen" which basically does what EAComp does but
doesnt write back the memory_access code but ensured the write operands
would g
* build/X86_SE/tests/fast/quick/00.hello/x86/linux/simple-timing passed.
* build/X86_SE/tests/fast/quick/00.hello/x86/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-at
