7 replies
February 2020

oschonrock

Nice.
Small tweak:
find . -name "*.i" | xargs wc -l | sort -r

should probably be:
find . -name "*.i" | xargs wc -l | sort -rn

Note the -n

1 reply
February 2020

mbitsnbites

Regarding developer hardware: These days I see no reason to settle for anything less than 8 cores (actually, machines with 8 cores are labeled “slow” in our CI system).

February 2020

tyler

Good catch. Will make an edit. Thanks!

February 2020

asu

Clang has a -ftime-trace option that is really handy for this. It generates dumps that can be read by Chrom{e,ium}'s about:tracing.

1 reply
February 2020

tyler

That’s really cool! After some searching around, it looks like there is also some work underway to do the same for GCC. 92396 – -ftime-trace support

October 2022

Hach

Is it possible to compile 1gb file with gcc with system ram 4g in a day

1 reply
October 2022 ▶ Hach

francois

I don’t see why not. What is your concern?