Skip to content

Conversation

ringabout
Copy link
Member

@ringabout ringabout commented Oct 11, 2025

ref #25217

The issues is actually that there is a hard limit for max cpus in niminst: #25219, which set to 20 while there is a 21 cpus now

@ringabout
Copy link
Member Author

ringabout commented Oct 11, 2025

And we build nim c -d:danger -r tools/niminst/niminst, which allows -d:danger to live up to its name. We should probably change it to -d:release in the following PRs

@ringabout ringabout changed the title fixes nightlies; fixes maxCPU hard limits fixes nightlies; fixes maxCPU hard limits caused by UB errors Oct 11, 2025
@ringabout ringabout changed the title fixes nightlies; fixes maxCPU hard limits caused by UB errors fixes nightlies due to UB errors; increase maxCPU hard limits Oct 11, 2025
@ringabout ringabout requested a review from Araq October 12, 2025 06:17
@Araq Araq merged commit c0fa868 into devel Oct 13, 2025
21 checks passed
@Araq Araq deleted the pr_max_cpus branch October 13, 2025 11:47
Copy link
Contributor

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from c0fa868

Hint: mm: orc; opt: speed; options: -d:release
183144 lines; 8.288s; 661.699MiB peakmem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants