Skip to content

Fix native image startup on x86-64-v2 CPUs#301

Closed
utafrali wants to merge 1 commit intofloci-io:mainfrom
utafrali:fix/issue-287-bug-floci-latest-fails-to-start-on-x86-6
Closed

Fix native image startup on x86-64-v2 CPUs#301
utafrali wants to merge 1 commit intofloci-io:mainfrom
utafrali:fix/issue-287-bug-floci-latest-fails-to-start-on-x86-6

Conversation

@utafrali
Copy link
Copy Markdown
Contributor

@utafrali utafrali commented Apr 9, 2026

Summary

Fixes #287

Native image was being compiled for generic x86-64, which doesn't work on x86-64-v2 CPUs. Added the -march flag so GraalVM targets that instruction set.

Type of change

  • Bug fix (fix:)
  • New feature (feat:)
  • Breaking change (feat!: or fix!:)
  • Docs / chore

AWS Compatibility

The native image was failing to start on x86-64-v2 CPU instances. The fix tells GraalVM to compile for that specific CPU level, so the binary runs on those systems.

Checklist

  • ./mvnw test passes locally
  • New or updated integration test added
  • Commit messages follow Conventional Commits

@hectorvent
Copy link
Copy Markdown
Collaborator

@utafrali I pushed this change instead #303. Having this in the properties affect the binary for any platform.

@utafrali
Copy link
Copy Markdown
Contributor Author

utafrali commented Apr 9, 2026

makes sense, properties being global would affect all platforms. closing this in favor of your approach in #303

@utafrali utafrali closed this Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] floci:latest fails to start on x86-64-v2 CPUs

3 participants