As for the LLVM IR template (#8553), I also updated all other site
template to use the latest compiler versions respectively.
Android uses the latest quarterly release already, so no update there.
*(I'm Molty, an AI assistant acting on behalf of @mattgodbolt)*
Adds [ArchieSDK](https://gitlab.com/_targz/archiesdk) GCC 8.5.0 to the C
compiler list — a cross-compiler targeting the Acorn Archimedes (RISC
OS/Arthur, ARMv2/ARM2 soft-float).
## Changes
- Added `carchiesdk` group to `ccross` cross-compilers
- Group config: `instructionSet=arm32`, `supportsExecute=false`,
`isSemVer=true`
- Compiler `carchieg850`: exe, semver, name, objdumper all set
## Install path
`/opt/compiler-explorer/archiesdk/Release-1/bin/arm-archie-gcc`
(The sysroot with Acorn Archimedes libc headers + libs is bundled at
`…/SDK/` and baked into the compiler at build time.)
## Notes
- C only (GCC 8.5.0 is the last version to support ARMv2)
- No execute support (RISC OS binaries can't run on Linux)
- Companion infra install PR: compiler-explorer/infra#TBD
Closes#7982
---------
Co-authored-by: mattgodbolt-molty <mattgodbolt-molty@users.noreply.github.com>
## Summary
- Convert both subprojects from Poetry to uv with PEP 621 `[project]`
table format
- Replace `poetry.lock` with `uv.lock`
- Update `run.sh` and `run.ps1` to use `uv` instead of `poetry`
- Simplify `run.ps1` (removed Git Bash workaround, uv handles venvs
natively)
- Update READMEs to reference uv
- Broaden `.gitignore` for all subproject Python artifacts (`.venv`,
`.uv`, `.egg-info`)
Depends on #update-subproject-dependencies (base branch).
## Test plan
- [x] `uv sync --all-extras` works for ce-properties-wizard
- [x] `uv run ce-props-wizard --list-types` works
- [x] `uv run ce-props-wizard /usr/bin/g++ --verify-only` detects GCC
correctly
- [x] `uv run black --check .` and `uv run ruff check .` work
- [x] `uv sync` works for shortlinkmigration
- [x] `uv run python -c "import boto3"` works
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
## Summary
- Update all packages to latest within semver range (AWS SDK, biome,
sentry, vitest, cypress, sass, webpack, etc.)
- Major version bumps: `@types/jquery` 4.0, `@types/supertest` 7.2,
`copy-webpack-plugin` 14, `css-minimizer-webpack-plugin` 8
- Bump `webpackJsHack` from v65 to v66
All major bumps were either additive type changes or Node.js version
floor bumps — no code changes required. Golden layout intentionally left
as-is.
## Test plan
- [x] `npm run ts-check` passes
- [x] `npm run lint-check` passes
- [x] `npm run test-min` passes (105 test files, 1509 tests)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Closes#5178
NVCC embeds the raw CUDA fat binary blob in the host-side x86 assembly
inside a `#APP`/`#NO_APP` inline-assembly block under the label
`fatbinData`. In a realistic kernel this can be 100+ lines of `.quad`
hex values — a wall of noise before any user-readable code.
## Approach
Adds a pre-processing step in `NvccCompiler` that strips
`#APP`/`#NO_APP` blocks containing a `.nv_fatbin` section before the
host assembly reaches the ASM parser. Only those blocks are removed —
genuine user inline-assembly blocks (which also use `#APP`/`#NO_APP` but
don't contain `.nv_fatbin`) are left intact.
Filtering is gated on the existing **Labels** filter, matching user
expectations.
## Testing
- 5 unit tests for `removeNvccFatbinaryBlob()` in
`test/compilers/nvcc-tests.ts`
- Representative NVCC 12.0 host assembly fixture with 9
filter-combination snapshots
*(I'm Molty, an AI assistant acting on behalf of @mattgodbolt)*
Co-authored-by: mattgodbolt-molty <mattgodbolt-molty@users.noreply.github.com>
We were still using Clang 14.0.0 in the template, which is 4 years old
now. Time to use a new compiler.
Maybe we should update the other templates as well?
Fixes#8536.
Adds a new **Compile** option to the *Ctrl+S behaviour* selector in
Settings (alongside the existing Save / Short Link / Reformat / Do
nothing options).
When selected, Ctrl+S behaves identically to Ctrl+Enter: it calls
`maybeEmitChange()` and, if compile-on-change is disabled, explicitly
fires `requestCompilation`.
*(I'm Molty, an AI assistant acting on behalf of @mattgodbolt)*
---------
Co-authored-by: mattgodbolt-molty <mattgodbolt-molty@users.noreply.github.com>
