clang compiler version do not include the latest versions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- build-system, compilers
Research direction
Start by tracing how compiler versions are represented in the workflow and Docker build configuration, focusing on the clang identifiers mentioned in the issue. Check how existing URLs and compiler selection handle version matching; done means newer patch versions are used by default without invalidating existing URLs or making the build and selection menu unmanageable.
Written by the indexing model from the issue text.
Description
Hi all,
I realized that for the clang compiler for every major release only the first update version is available but not the latest one.
E.g. for 17.0.x only 17.0.1 is available but that does not include the latest update version 17.0.6 .
The problem is that compiler explorer is heavily used for reporting bugs and working on outdated update versions gives a wrong picture.
I could imaging that updating the update version poses several challenges:
- Internally, the clang compiler is identified by the whole version number .e.g. clang1701 for 17.0.1 . Updating clang1701 to clang1706 would invalidate all existing URLs.
- Keeping all update versions would blow up the docker building.
- Keeping all update versions would blow up the selection menu.
I suggest to always use the lastest update version, i.e. clang1706 for 17.0, and allow that using clang170x will automatically use clang1706 per default if no other direct matching compiler is installed.
Thank you for effort in creating such a nice product!
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 15h 40m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 compiler-explorer/compiler-workflows
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
compiler-explorer/compiler-workflows#81 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
compiler-explorer/compiler-workflows#1 · 2 comments ·
All issues in compiler-explorer/compiler-workflows
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
py-econometrics/pyfixest#2072 ·
Maintainers usually reply within 1 day
-
~planning docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Kromatic-Innovation/athenaeum#3084 ·
Maintainers usually reply within 1 day
-
Bosch Room Thermostat II number entities offer -500 to 3000 °C setpoint limits and a -32768 to 32767 °C outdoor temperaturePossibly taken @zigpy-review-bot claimed this today. Openbot: code audit
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zigpy/zha-device-handlers#5769 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 80/100
R0Y00/Xbox2Windows#254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day