Skip to content

Add support for aarch64 macos firtool binaries - #34

Merged
jackkoenig merged 1 commit into
mainfrom
jackkoenig/macos-aarch64
Apr 9, 2026
Merged

jackkoenig merged 1 commit into
mainfrom
jackkoenig/macos-aarch64

Conversation

@jackkoenig

Copy link
Copy Markdown
Collaborator

They will now be required by FindNewReleases for CD, but the firtool-resolver logic will still support falling back to x64 on macos aarch64 because users could use older versions of llvm-firtool that did not have the macos aarch64 binary available.

@seldridge seldridge left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment thread build.mill

case class Platform(os: String, arch: String) {
override def toString: String = s"$os-$arch"
// CIRCT release artifacts use "arm64" but FNDDS uses "aarch64"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is FNDDS?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why, it's the Firtool Native Dependency Distribution Specification of course!
https://github.com/chipsalliance/firtool-resolver?tab=readme-ov-file#firtool-native-dependency-distribution-specification-fndds

I picked aarch64 over arm64 for that because it's what the JVM distributions use and that seemed as as good as reason as any 🤷‍♀️

@jackkoenig
jackkoenig merged commit c714d73 into main Apr 9, 2026
7 checks passed
@jackkoenig
jackkoenig deleted the jackkoenig/macos-aarch64 branch April 9, 2026 21:36
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