Skip to content

Add aburi compiler#2202

Open
likecrazy1 wants to merge 2 commits into
compiler-explorer:mainfrom
likecrazy1:aburi
Open

Add aburi compiler#2202
likecrazy1 wants to merge 2 commits into
compiler-explorer:mainfrom
likecrazy1:aburi

Conversation

@likecrazy1

Copy link
Copy Markdown

@mattgodbolt-molty

Copy link
Copy Markdown
Contributor

Thanks @likecrazy1! Picking up the build path for this. Two enabling fixes were needed before the aburi-atta-mills artifact this installable points at can be built and uploaded to S3:

  1. aburi: install x86_64 cmake, not aarch64 misc-builder#137Dockerfile.aburi fetched the aarch64 cmake; the builder runs on x86_64, so the compiler build would fail at cmake. Fixed to x86_64.
  2. bespoke-build: add aburi to builder image choices #2209aburi wasn't a selectable image in bespoke-build, so the artifact build couldn't be dispatched. Added it.

Once both merge (and the aburi-builder image rebuilds), I'll run bespoke-build -f image=aburi -f version=atta-mills -f command=build.sh to populate S3, after which this PR and compiler-explorer/compiler-explorer#8872 are unblocked.

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown

Build Required

The following additions require CE to build artifacts before deployment:

  • cpp.yaml: compilers/c++/aburi atta-mills (type: s3tarballs)

Please ensure these have been built and uploaded to S3 before merging, or coordinate with the CE team.

Build Commands

gh workflow run bespoke-build.yaml -f image=aburi -f version=atta-mills -f command=build.sh

The aburi installable was defined identically in both c.yaml and cpp.yaml.
Both resolve to the same S3 artifact and the same install path
(/opt/compiler-explorer/aburi/atta-mills), so the c.yaml copy is redundant —
one install serves both languages, and the C and C++ properties both point at
the same exe. Keep it in cpp.yaml (matching the gcc/clang convention) and drop
the duplicate from c.yaml.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mattgodbolt-molty

Copy link
Copy Markdown
Contributor

Pushed a maintainer edit removing the duplicate. The aburi: installable was defined identically in both c.yaml and cpp.yaml — both resolve to the same S3 artifact and the same install path (/opt/compiler-explorer/aburi/atta-mills), so it was one physical install described twice. Not harmful (the second is skipped as already-installed), just redundant/confusing. Kept it in cpp.yaml (gcc/clang convention); the C and C++ property groups in compiler-explorer#8872 both point at the same exe, so C is unaffected.

Verified end-to-end with a real local install:

bin/ce_install --dest ~/ce-test install 'compilers/c++/aburi'
→ 1 packages installed OK, 0 skipped, 0 failed
bin/aburi --version → Aburi 0.1.1-republic-day / LLVM 18.1.8 / aarch64-apple-darwin (exit 0)

So the installable is good to go. 👍

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