compiler-explorer / compiler-explorer/infra

Find a better way to build libraries

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

Description

Currently, building trunk libraries for compilers can take a day or longer.

It might be a better idea to apply a priority system based on compiler and library usage to spread out builds and not spend time on building things that nobody uses anyway.

Would require a registry of some sort where we store statistics on compilers and libraries.

Would perhaps require storing/loading data about when a library has been last been built.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing process for building trunk compiler libraries and identify where build selection and timing are controlled. Clarify how compiler and library usage statistics, build timestamps, and a registry would fit that process. Done means a concrete, agreed design for prioritising builds and avoiding unused work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.