Large resources required to build profiled gcc

lucier@math.purdue.edu lucier@math.purdue.edu
Fri Mar 22 13:43:00 GMT 2002


I'm trying to build a profiled gcc on sparcv9-sun-solaris2.8
with BOOT_CFLAGS=' -O2 -pg -g -m64 -mcmodel=medlow' and
BOOT_LDFLAGS=' -O2 -pg -g -m64 -mcmodel=medlow'.

A parallel build failed with the remark:

./gencheck > tmp-check.h
./genpreds > tmp-preds.h
No space for profiling buffer(s)
/bin/sh ../../gcc/move-if-change tmp-mlib.h multilib.h
multilib.h is unchanged
echo timestamp > s-mlib
./gengenrtl -h > tmp-genrtl.h
No space for profiling buffer(s)
Segmentation Fault
Segmentation Fault

So I reran it serially, and got this information from top:

 23017 lucier     1  20    0 3075M 1680M cpu/1    0:46 20.77% gengenrtl

It's fairly remarkable that gengenrtl takes 3 GB of swap space,
no wonder it ran out of virtual memory.

Is there some way to reduce these resource requirements?  If not, only
people with fairly large machines will be able to build/test/run these
profiled programs.

Brad



More information about the Gcc mailing list