Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Not using all threads during coreboot's make

Open
#1 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
build-system

Research direction

Start by tracing how the top-level make -j14 crossgcc-i386 iasl invokes make -C util/crossgcc build-i386 build_iasl SKIP_GDB=1. Check whether the job limit reaches the toolchain build, then verify that building GCC uses multiple CPUs rather than one.

Written by the indexing model from the issue text.

Description

"threads" is 14 on my machine, but the toolchain make that coreboot performs seems to be single-threaded. this might be a coreboot problem.

i can see the original make was called correctly from ps:

brho 253888 253487 0 14:54 pts/10 00:00:00 make -j14 crossgcc-i386 iasl

but i don't know if that's getting passed down correctly. here's the child:

`brho 253962 253888 0 14:54 pts/10 00:00:00 make -C util/crossgcc build-i386 build_iasl SKIP_GDB=1'

either way, it's been building GCC v8.1.0 for a long time now, and it's using at most one CPU.

Dominant language
Go
Stars
10
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 linuxboot/corebootnerf

All issues in linuxboot/corebootnerf

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.