We currently hardcode this to true; we should use the CPUID-generated value for this instead. (Note that this is really a temporary fix: Bug 586472 will fix this in a more robust way, at the nanojit-backend level; this is just a band-aid for affected hardware until that fix is implemented.)
Created attachment 469621 [details] [diff] [review] Patch
pushed to TR as 5132:f0c53b160a00
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.