Currently we have RH7.3 with compiler gcc 2.96.x
My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x
Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1
I don't know how many fatal fits, as some disguise others etc. "Can't find register to spill" is a common exit-barf from gcc 3.x.
What I'd like to find is a comparison of gcc 2.96.x to 3.x from the perspective of porting something from RH7.x to CentOS/RHEL 4.x
What I did was make a fresh install of CentOS 4.1 and then load the source code for the application and try to make. What gcc 2.96 compiler assumed about the underlying OS, and what gcc 3.x assumes about the underlying OS, may be relatively skew. Whether any of the application code assumes a 2.96 set of assumptions, where this set of assumptions is broken under 3.x, is unknown (and is the kind of detail I'd like to see in the above-hinted-at porting guide).
Links? Pointers? Tips? Clues?
Brian Brunner brian.t.brunner@gai-tronics.com (610)796-5838
******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept for the presence of computer viruses.
www.hubbell.com - Hubbell Incorporated
On Mon, 2005-09-19 at 11:53 -0700, Brian T. Brunner wrote:
Currently we have RH7.3 with compiler gcc 2.96.x
My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x
Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1
I don't know how many fatal fits, as some disguise others etc. "Can't find register to spill" is a common exit-barf from gcc 3.x.
What I'd like to find is a comparison of gcc 2.96.x to 3.x from the perspective of porting something from RH7.x to CentOS/RHEL 4.x
What I did was make a fresh install of CentOS 4.1 and then load the source code for the application and try to make. What gcc 2.96 compiler assumed about the underlying OS, and what gcc 3.x assumes about the underlying OS, may be relatively skew. Whether any of the application code assumes a 2.96 set of assumptions, where this set of assumptions is broken under 3.x, is unknown (and is the kind of detail I'd like to see in the above-hinted-at porting guide).
Links? Pointers? Tips? Clues?
Brian,
There is a compat-libstdc++-296-2.96-132.7.2 ... so you might be able to install that and run your applications.
Brian T. Brunner wrote:
Currently we have RH7.3 with compiler gcc 2.96.x
My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x
Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1
I don't know how many fatal fits, as some disguise others etc. "Can't find register to spill" is a common exit-barf from gcc 3.x.
Frankly, that sounds like an internal error in the compiler. Either the register allocater, the temporary creator, or the register spiller seems to be failing to do its job.
This does not appear to me to be a porting problem, but a defective compiler. Is there any reason you must use the later compiler?
[snip]
Mike
Brian T. Brunner wrote:
What I'd like to find is a comparison of gcc 2.96.x to 3.x from the perspective of porting something from RH7.x to CentOS/RHEL 4.x
You're probably better off asking on the gcc list or some other C/developer oriented forum. This list is mainly sysadmins.
-jim