Mike Frysinger c0c25232da sim: run: move linking into top-level ... Automake will run each subdir individually before moving on to the next one. This means that the linking phase, a single threaded process, will not run in parallel with anything else. When we have to link ~32 ports, that's 32 link steps that don't take advantage of parallel systems. On my really old 4-core system, this cuts a multi-target build from ~60 sec to ~30 sec. We eventually want to move all compile+link steps to this common dir anyways, so might as well move linking now for a nice speedup. We use noinst_PROGRAMS instead of bin_PROGRAMS because we're taking care of the install ourselves rather than letting automake process it.		2022-11-05 20:00:56 +07:00
..
arch.c
arch.h
ChangeLog-2021
cpuall.h
cpuv10.c
cpuv10.h
cpuv32.c
cpuv32.h
cris-sim.h
cris-tmpl.c
crisv10f.c
crisv32f.c
decodev10.c
decodev10.h
decodev32.c
decodev32.h
dv-cris_900000xx.c
dv-cris.c
dv-rv.c
local.mk	sim: run: move linking into top-level	2022-11-05 20:00:56 +07:00
Makefile.in
mloop.in
modelv10.c
modelv32.c
rvdummy.c
semcrisv10f-switch.c
semcrisv32f-switch.c
sim-if.c
sim-main.h
traps.c