Quoting nathan binkert <[email protected]>: >> Yes and yes. All the bugs I fixed last night I found with a massaged >> version of the main test program from there and more will be coming. I'm >> definitely planning on using it as a regression in SE, and also as the >> program to run in FS once the kernel is booted because it can use some >> syscalls we don't support in SE. I want to wait until things aren't >> changing so much, aka until the output matches and more of the phases of >> the test run, before making it into a regression. > > This sounds great. Are you basically just implementing missing > instructions right now? > > Nate > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
The changes I pushed already mostly fix condition codes on existing instructions, plus rotates by more than the width of the target, plus a few minor fixes to multiply related microops. Moving forward in the short term, division instructions aren't getting the answers they should, and the test has a form of shift that shift one register out while shifting another one in that I don't have implemented. After that, I'm going to need to figure out how I want the various forms of FP instructions to work, aka microcoded or not, if so broken down how, how the register management will work, etc. Then I'd need to go in and implement a bunch of instructions. After that, there are sections of the test I commented out because I either suspect or know they won't work currently, perhaps because I'm using SE mode. I'd like to look at those more carefully and turn on the ones that are useful. There will potentially be things in there that are broken, and also things that are just incomplete or missing entirely. Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
