new-ra excessive memory usage

new-ra excessive memory usage

[tm_gccmail]

version: CVS mainline
   host: i386-linux
 target: sh-elf
 
I have one testsample which was compiling properly on a 128 meg system
with:

-O2 -m4 -fnew-ra

I believe starting today, it started to be killed by the OS for excessive
memory usage:

[tm@localhost gcc]$ ./cc1 -O2 -m4 -fnew-ra -da  engine_c.i
 ustat
engine_c.i:2269: warning: conflicting types for built-in function
`vprintf'
engine_c.i:2270: warning: conflicting types for built-in function
`vsprintf'
engine_c.i:2274: warning: conflicting types for built-in function `vscanf'
engine_c.i:2275: warning: conflicting types for built-in function
`vsscanf'
engine_c.i:2308: warning: conflicting types for built-in function
`vsnprintf'
 __stat stat __lstat lstat __fstat fstat __mknod mknod check_breakpoints
get_memory8_io_stub get_memory16_pieces_stub get_memory24_pieces_stub
set_memory8_io_stub set_memory16_pieces_stub set_memory24_pieces_stub
get_memory_c get_memory16_c get_memory24_c set_memory_c set_memory16_c
set_memory24_c do_adc_sbc8 do_adc_sbc16 fixed_memory_ptrs_init get_itimer
set_halt_act clr_halt_act get_remaining_operands enter_engine {GC 28956k
-> 7052k} {GC 27981k -> 7323k}Killed

Has anything changed in the new regalloc on mainline to consume more
memory?

Toshi

Re: new-ra excessive memory usage

[Michael Matz]

Hi,

On Wed, 25 Jun 2003 tm_gccmail@mail.kloo.net wrote:

> Has anything changed in the new regalloc on mainline to consume more
> memory?

Not from me.  I also can't find anything directly related to ra-* or df.c,
which could explain any explosion in memory.  I fear it's an unrelated
change which affects new-ra in this way.


Ciao,
Michael.