This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Migrate from GCC 2.96 to GCC 3.0
- To: gcc at gcc dot gnu dot org, xyang at hns dot com
- Subject: Re: Migrate from GCC 2.96 to GCC 3.0
- From: mike stump <mrs at windriver dot com>
- Date: Fri, 22 Jun 2001 09:55:05 -0700 (PDT)
- Cc: nschley at hns dot com
> Date: Fri, 22 Jun 2001 11:52:57 -0400
> From: "Xuehong(Helen) Yang" <xyang@hns.com>
> Our question is how much effort we need to migrate our GCC 2.96
> compiled code to GCC 3.0 or some other GNU versions.
If you manage to find all the non-portable aspects of any particular
release and use them extensively, then you might be able to create
lots of problems for yourself. If you compile the portable part of
your code with 3.0 as you go along, you can help ensure that you're
using constructs that will move easily between the two.
For C, you will be hard pressed to create code that won't move easily
from 2.96 to 3.0. If you're using C++, then it is easier. The most
common things I've seen would be namespace related. Things like not
using std: when it is required. After that, header file spelling.