-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
24-bit addressing support #12
Comments
To my knowledge, PowerPC never implemented 24-bit addressing, so if it ends up being a launch-time switch, perhaps disabling PowerPC code translation could speed some things up. |
Yes, 24-bit was dead long before the PowerPC came along, so all PowerPC programs are definitely 32-bit compatible. I don't think it's even easy to make it a launch-time switch - the first attempt will be a compile time thing. The |
How does Apple cope with that on a 32bit clean system? |
@Godzil, cope with what exactly? They didn't have the |
Originally, Macs used 24-bit addressing. Apple introduced 32-bit addressing as an option with System 7 on 68020 and later processors, and made it mandatory some time later. This caused compatibility problems for quite a few applications.
Executor only implements 32-bit addressing and shows a warning for applications that are not explicitly marked as 32-bit compatible by their developers.
Background: The original 68000 processor ignored the upper 8 bits of every 32-bit address. Some programs took advantage of that and stored other information there, others even relied on the Memory Manager storing some information there in some situations.
TODO:
Affected Apps (that are known to crash for this reason):
The text was updated successfully, but these errors were encountered: