fix: use apple_a14 CPU model for iOS simulator NEON support

[apotema]

Summary

• Changed iOS simulator target CPU model from apple_m1 to apple_a14
• Ensures NEON SIMD intrinsics work correctly for box2d physics

Context

This was discovered during labelle-engine PR #248 (mobile CI work). The box2d physics library uses NEON SIMD intrinsics that require specific ARM features enabled. Using apple_a14 ensures these features are available.

Related

• test: Add CI workflow to verify iOS and Android builds with physics labelle-engine#248 - Mobile CI workflow
• feat: Add CLI support for mobile cross-compilation labelle-engine#250 - Mobile CLI support issue

🤖 Generated with Claude Code

[cursor]

PR Summary

Adjusts simulator target to ensure required ARM features are available during simulator builds.

• Updates cpu_model in generated build.zig for iOS simulator from apple_m1 to apple_a14
• Adds inline comment explaining NEON SIMD requirement for box2d

^{Written by Cursor Bugbot for commit 8bfc717. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Summary of Changes

Hello @apotema, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue preventing NEON SIMD intrinsics from functioning correctly within the iOS simulator environment on Apple Silicon Macs. By updating the target CPU model for the iOS simulator from apple_m1 to apple_a14, the necessary ARM features are now available, ensuring proper operation for components like the box2d physics library.

Highlights

• CPU Model Update: The iOS simulator target CPU model has been changed from apple_m1 to apple_a14.
• NEON SIMD Support: This change enables correct functionality of NEON SIMD intrinsics, specifically for the box2d physics library, on iOS simulators running on Apple Silicon Macs.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request addresses an issue with NEON SIMD intrinsics on the iOS simulator by changing the target CPU model from apple_m1 to apple_a14. The change is correct and well-justified in both the pull request description and the new code comment, ensuring that features required by the box2d physics library are available. The modification is properly targeted within the generateIosBuildZig function, which will affect the generated build.zig for iOS projects. While reviewing, I noticed that src/ios/build_ios.zig also defines an iOS simulator target but does not specify a cpu_model. This file is not part of the current changes, but it might be worth a separate look to ensure consistency and proper NEON support across all possible build configurations for the iOS simulator.