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

Proposal: Add the MacOS support #11

Closed
hnes opened this issue Jul 16, 2018 · 1 comment
Closed

Proposal: Add the MacOS support #11

hnes opened this issue Jul 16, 2018 · 1 comment

Comments

@hnes
Copy link
Owner

hnes commented Jul 16, 2018

According to MacOS's IA-32 Function Calling Conventions:

The function calling conventions used in the IA-32 environment are the same as those used in the System V IA-32 ABI, with the following exceptions:

  • Different rules for returning structures

  • The stack is 16-byte aligned at the point of function calls

  • Large data types (larger than 4 bytes) are kept at their natural alignment

  • Most floating-point operations are carried out using the SSE unit instead of the x87 FPU, except when operating on long double values. (The IA-32 environment defaults to 64-bit internal precision for the x87 FPU.)

The content of this article is largely based in System V Application Binary Interface: Intel386 Architecture Processor Supplement, available at http://www.sco.com/developers/devspecs/abi386-4.pdf.

and MacOS's x86-64 Function Calling Conventions:

The OS X x86-64 function calling conventions are the same as the function calling conventions described in System V Application Binary Interface AMD64 Architecture Processor Supplement.

That means libaco already supports MacOS, but there still exist some build problems due to the differences of compiler toolchains between linux and mac.

The support for MacOS would be finally released in the v1.2.3 (would come in several days).

@hnes hnes self-assigned this Jul 16, 2018
@hnes hnes changed the title proposal: Add the MacOS support Proposal: Add the MacOS support Jul 16, 2018
hnes added a commit that referenced this issue Jul 24, 2018
@hnes
Copy link
Owner Author

hnes commented Jul 26, 2018

The v1.2.3 has already been released ;-)

@hnes hnes closed this as completed Jul 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant