jsm28@gcc.gnu.org wrote: > Does this problem still occur with GCC 3.0? No. With gcc-3.0, it just consumes so much memory that I terminate it, but that's ok, it's a huge function (and smaller versions already take much memory). So you can consider that fixed. - anton