On Sun, 2012-03-25 at 19:26 +0200, Olof Kindgren wrote: > > Regarding or1ksim, though, In my opinion what would be the > best > solution to all of this is keeping track of the register > accesses > after "power up" on the simulator and printing out a big error > message > if accesses to any register which should be initialised > (basically > just the GPRs) are accessed without. This would mean wrapping > them in > some accessor function and checking against a > "read_before_written" > bit once after or1ksim bringup.
Hi Julius, Olof, I'd like to see the overhead is adding an extra check to every register access. At present register access is an array lookup. Adding code to this, particularly with a flow-of-control, sounds expensive to me. Giving control over initialization (as per R Diez) is the way to go. One off penalty at start-up, but achieves most of what you want. Jeremy -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: jeremybennett Email: [email protected] Web: www.embecosm.com _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
