More details on DRAM scrubbing in OpenSPARC T2

Question

I am trying to understand DRAM scrubbing on OpenSPARC T2.
I think I get the high-level idea but am confused by some word swapping that
seems to be going on before writing the corrected data back to memory.
In particular, this comment from mcu_wrdp_dp.v and the subsequent code...
// scrub_wdata
// [63:0] [127:64]
// | |
// v v
// 511:448 447:384
// v v
// 383:320 319:256
// v v
// 255:192 191:128
// v v
// 127:64 63:0
// | |
// v v
// write to memory
Does anyone have more info?
Thanks

Answer 1

Thanks for the feeback. I modified tools/bin/syn_command to include the '-64bit' flag and reran 'rsyn rtx'. I seem to encounter the same issues. All 6GB (I previously incorrectly stated 4GB) of ram on my machine is being utilized by dc while no cpu resources are used. Questions:
1) How can I verify that the 64bit dc binary is being called and not the 32bit (searching through dc_shell.log and command.log didn't yield anything conclusive)?
2) How much physical ram should be required to synthesize rtx? Even though nearly 6GB of ram is used by dc 15GB out of 16 GB of swap is still free. Is dc not able to take advantage of swap space?
Thanks for the info on the SPU. I was just curious if this kind of information is documented anywhere (in more detail than the DVGuide) so I can gain a better understanding of the design and the synthesis/simulation setup?