clang compiler version do not include the latest versions

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

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

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:

  1. 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.
  2. Keeping all update versions would blow up the docker building.
  3. 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from compiler-explorer/compiler-workflows

All issues in compiler-explorer/compiler-workflows

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.