I talked to Gabe and took a look at the problem more closely, and I'm now wondering if we really need the ~0x3 mask at all anymore. It seems like the only thing that mask does on Alpha is allow us to have a single PC-based event that works whether we execute the given instruction in PAL mode or not. I find it hard to believe we ever really rely on that. Do we ever use PC events in PAL mode at all? Even if we do, can't we just add the PAL bit to the event before we schedule it? I realize this might not always be easy (e.g., it might make setting breakpoints interactively in PAL code via the remotegdb interface harder) but given the extent to which anyone uses Alpha anymore I don't think this is an issue.
So unless someone can explain why we really need it, I propose just deleting the " & ~0x03" from both of the places it appears in doService() and moving on. Steve _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
