linux.aarch64 release binary is ~3.5x slower than a native arm64 build of the same version
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- haskell, linux, ubuntu
- Domain
- build-system, release
Research direction
The release build for linux.aarch64 is produced by the project's CI or Makefile; inspect those to see the cross-compilation from x86_64 with GHC 9.12.2. First read the build scripts and run the benchmark on an arm64 host. Done means the aarch64 release is built natively or with optimised libraries and runs close to the Ubuntu package's 43.2s.
Written by the indexing model from the issue text.
Description
On an Ubuntu 26.04 arm64 host (Hetzner CAX21, 4 vCPU Ampere Altra), the v0.11.0 linux.aarch64 release binary is about 3.5x slower than Ubuntu's natively built package of the same version.
Same 158 scripts (36.8k lines), --severity=warning --format=gcc, LC_ALL=C, median of 3 runs:
| binary | seconds |
|---|---|
| v0.11.0 linux.aarch64 release (+RTS --info: GHC 9.12.2, cross-compiled from x86_64) | 151.5 |
| Ubuntu resolute shellcheck 0.11.0-2 arm64 (GHC 9.10.3, built natively on Launchpad) | 43.2 |
| v0.11.0 linux.x86_64 release, 2-vCPU x86 host, for reference | 24.1 |
All three gave byte-identical output at --severity=style (725 lines), and all three use the non-threaded RTS.
The gap looks like it comes from the cross-build: possibly the boot libraries the aarch64 builder links are not built optimised. Would it be possible to build the aarch64 release with optimised libraries, or natively on an arm64 runner?
- Dominant language
- Haskell
- Stars
- 40.2k
- Forks
- 2k
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 19
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from koalaman/shellcheck
-
shellcheck silently ignores --enable=unknown optionPossibly taken @eyadstein claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
koalaman/shellcheck#3593 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
koalaman/shellcheck#3465 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
koalaman/shellcheck#3600 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
koalaman/shellcheck#3599 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
koalaman/shellcheck#3592 ·
Maintainers usually reply within 2 days
All issues in koalaman/shellcheck
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
alunduil/siren-json.hs#264 ·
Maintainers usually reply within 1 day
-
console: no way to refresh row data in Browse Rows without a full page reloadPossibly taken @12fahed claimed this today. Openk/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hasura/graphql-engine#10895 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Possibly taken @renyamamoto2026-cmyk claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/phino#2107 ·
Maintainers usually reply within 1 day