Skip to content

Conversation

mostobriv
Copy link
Contributor

@mostobriv mostobriv commented Aug 27, 2025

This MR addressing #7311. A bit confused why hasn't it been done earlier.

As "macos-syscall" was never registered and used by any of platform types, it is safe to rename it to "apple-syscall" (as it applied to both macos and ios).

Also changed arguments for this cc from X0-X5 to X0-X8 as syscalls on ios/macos can handle up to 9 arguments

@mostobriv mostobriv force-pushed the apple_arm64_syscall_calling_convention branch from ccdc8d1 to 0aee11e Compare August 27, 2025 06:48
@mostobriv
Copy link
Contributor Author

mostobriv commented Aug 27, 2025

I didn't change anything in mac_kernel platform, as i'm not much familiar with osx kernel stuff, however i have a feeling that syscalls there behave the exact same way, so if i should add cc there lmk

@mostobriv mostobriv changed the title Apple arm64 syscall calling convention [Arm64, Mac] Apple arm64 syscall calling convention Aug 27, 2025
@mostobriv mostobriv changed the title [Arm64, Mac] Apple arm64 syscall calling convention [Arm64, Apple] Apple arm64 syscall calling convention Aug 27, 2025
@bdash bdash force-pushed the apple_arm64_syscall_calling_convention branch from 0aee11e to 4c1c871 Compare September 12, 2025 05:40
@bdash bdash merged commit 4c1c871 into Vector35:dev Sep 12, 2025
1 check passed
@bdash
Copy link
Contributor

bdash commented Sep 12, 2025

Thank you very much for the change!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants