compiler-explorer / compiler-explorer/infra

Missing references to some nightly compilers

Open
#1,245 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
434
Forks
429
Avg merge
4d 21h
Merged PRs (30d)
38

Description

* [ ] `/opt/compiler-explorer/llvm-mos-trunk/bin/clang` - this is because we point to the various symlinks
* [ ] `/opt/compiler-explorer/bpf/gcc-trunk/bpf-unknown-none/bin/bpf-unknown-g++`
* [ ] `/opt/compiler-explorer/carbon-trunk/bin/carbon-explorer`
* [ ] `/opt/compiler-explorer/cobol/gcc-cobol-master/bin/gcobol`
* [ ] `/opt/compiler-explorer/dotnet-trunk/.dotnet/dotnet` - this might be because we use specific executables for the various languages
* [ ] `/opt/compiler-explorer/hook/hook-0.1.0/bin/hook`
* [x] `/opt/compiler-explorer/SPIRV-Tools-master/build/tools/spirv-dis` - we use this, but don't have it as a compiler, so this is expected
* [x] `/opt/compiler-explorer/llvm-spirv-trunk/bin/llvm-spirv` - same, not a compiler
* [x] `/opt/compiler-explorer/swift-5.10/usr/bin/swiftc` - fixed with https://github.com/compiler-explorer/compiler-explorer/commit/e45ba2d0892b45b3534937d4394ed5ef49441f86

Contributor guide

Open the contributing guide

Research direction

Use the six unchecked compiler paths as the checklist and locate the repository configuration that records compiler references. The work is done when each unchecked path is either included or explicitly accounted for, while the two checked non-compiler tools remain unchanged.

Written by the indexing model from the issue text.

Assessment

Domain
compilers, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.