[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnucap-devel] Build failure with version 2007-08-20

From: David Fang
Subject: Re: [Gnucap-devel] Build failure with version 2007-08-20
Date: Fri, 21 Sep 2007 10:13:07 -0400 (EDT)

Back to the 3.3 issue ... I need to decide where to draw the line on supporting old compilers. Using an enum here is no problem. If that was all that is needed, I would do it. I have concerns about the other problems with g++-3.3, particularly the stack overflow, which happens on both 32 and 64 bit systems. (Actually, all of the mentioned problems happen both on an AMD-64 and Intel-32.)

I'm getting a different (?) issue with powerpc-apple-darwin8-gcc-3.3 where a few generated model files
(d_mos5, d_mos8) crash the compiler with:

cc1plus(1685) malloc: *** vm_allocate(size=2210779136) failed (error code=3)
cc1plus(1685) malloc: *** error: can't allocate region
cc1plus(1685) malloc: *** set a breakpoint in szone_error to debug

The culprit seems to be the massive switch-case statements in MODEL::set_param_by_index(...) and friends. Does this occur on other gcc-3.3's, or is it just Apple's? (I'll hunt around for other gcc-3.3s..)
Might it be posssible to convert this to a function table?

any conclusions on this? Unfortunately most of the computers I use have gcc-3.2 or gcc-3.3.

If I can get it to compile, what needs to be done to reproduce the stack-overflow? (Test case +instructions?)

IMHO, gcc-3.3 is still a good compiler to support, but I personally draw the line at 3.2 because of C++ front-end bugs I've encountered.

David Fang
Computer Systems Laboratory
Electrical & Computer Engineering
Cornell University
        -- (2400 baud? Netscape 3.0?? lynx??? No problem!)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]