search

compiler-explorer / compiler-workflows

Workflows to build daily and ad hoc compilers for Compiler Explorer
BSD 2-Clause "Simplified" License
18 stars 18 forks source link

clang compiler version do not include the latest versions #23

Open strimo378 opened 8 months ago

strimo378 commented 8 months ago

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!

mattgodbolt commented 1 month ago

Hi there: Our approach has always been to keep all versions of the compilers. This is why we have so many listed in the dropdown. We just don't tent to add clang revisions unless someone asks for them or adds a PR for them.

You correctly identify some of the challenges: but for the same bug-reproduction reason we tend to keep all versions forever (so historic bug reports still work).