Skip to content
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

Fix OSX "Data element too large" error #1

Closed
wants to merge 1 commit into from

Conversation

sideshowbarker
Copy link
Contributor

See http://stackoverflow.com/a/32349608/441757

On OSX this compiles and runs/works in the http://github.com/whatwg/html build as expected without any errors or additional/unexpected warnings—both without the -Px86_64 specified, and with it specified.

Would be good to test it on other platforms.

Despite what Marco says at http://stackoverflow.com/a/32349608/441757 about disabling runtime (range) checks in the source in order to make this work, in my testing in my environment at least, it doesn’t require that. But if needed I can add the pragmas (or whatever Pascal calls them) to turn off/on the range checks at the appropriate place in the code.

@sideshowbarker
Copy link
Contributor Author

See also http://mantis.freepascal.org/view.php?id=28588 for the related issue that fpc binary on OS X generates 32-bit code by default.

There is no such thing as a 32 bit or 64 bit "host" on OS X, as even a Mac OS X 10.6 system running a 32 bit Intel kernel can perfectly execute 64 bit applications. It's completely mixed/transparent.

The "fpc" binary on OS X always has and for the foreseeable future always will generate 32 bit code by default (both on Intel and PowerPC systems). If you want 64 bit code, use "fpc -Px86_64" or ppcx64.

@Hixie
Copy link
Member

Hixie commented Sep 3, 2015

Yeah, using 0..0 should be fine.

@sideshowbarker
Copy link
Contributor Author

Closed by fc38b65

@sideshowbarker sideshowbarker deleted the array-range branch September 4, 2015 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants