precheck: parallelise core_ext_boundary_check (the precheck's critical path, 17–35 s)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- build-system, cli, performance
Research direction
The script tools/core_ext_boundary_check.sh runs gcc -fsyntax-only on each core source file sequentially. Start by examining this script to understand the file list and the gcc command. Then, modify it to use xargs -P or a similar parallel execution method. Verify the change by running time bash tools/precheck.sh and ensuring the total time is under 40 seconds on a 2-core machine and that the precheck's output and self-tests remain unchanged.
Written by the indexing model from the issue text.
Description
Found while building make precheck (#1264, PR-B). Out of that PR's scope, so filed here.
tools/core_ext_boundary_check.sh runs gcc -fsyntax-only over every core source file, one at a time. At 17–35 s it is the precheck's critical path: precheck takes about 61 s on a loaded 2-core box, against a target of well under a minute. Parallelising it (for example xargs -P "$(nproc)") or caching per-file results keyed on content would put precheck comfortably under a minute. The contributor-facing loop is precheck → push, so every second here is paid on every contribution.
Bar: time bash tools/precheck.sh is under 40 s on a 2-core box, and the gate's verdict and self-test are unchanged. Self-contained: needs only the repo and gcc.
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 102
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a 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 InauguralSystems/EigenScript
-
area:lint-tooling bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1340 ·
Maintainers usually reply within 1 day
-
area:stdlib found-by:code-review kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1338 ·
Maintainers usually reply within 1 day
-
area:lint-tooling found-by:critic kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
InauguralSystems/EigenScript#1335 ·
Maintainers usually reply within 1 day
-
area:ci found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#1311 ·
Maintainers usually reply within 1 day
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetOpenarea:gates found-by:critic kind:decision
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
InauguralSystems/EigenScript#1280 · 1 comment ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
johnsonjh/emu2-cpm86#68 · 1 comment ·
Maintainers usually reply within 1 day
-
Zenmap CrashOpenZenmap
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
fastfetch-cli/fastfetch#2619 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Template: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
betaflight/betaflight#15759 ·
Maintainers usually reply within 1 day