This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Odd things when change gcc from 3.3 to 3.4
- From: Mingjie Xing <mingjie dot xing at gmail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 16 Nov 2011 10:27:59 +0800
- Subject: Re: Odd things when change gcc from 3.3 to 3.4
- References: <CADNgcEyqj3gH922Y5AAj95_4N2OV9W0UqtKn4y=OKU_aEvHjYg@mail.gmail.com> <CAH6eHdT71hOn2YAF4xmOWVomQabArFYo+rq_Hh6REHO-PS05vA@mail.gmail.com>
2011/11/15 Jonathan Wakely <jwakely.gcc@gmail.com>:
> This question is inappropriate for this mailing list, questions about
> using GCC belong on the gcc-help@gcc.gnu.org mailing list, please take
> any follow up there.
>
> GCC 3.4 is ancient history, but shouldn't cause a problem like this so
> I assume it's caused by something in your program or something wrong
> with your GCC 3.4 installation. ?Is there any reason not to use a more
> recent version of GCC?
The problem is worked around according to the helpful suggestion off
line. BTW, not all such problems can be resolved by simply using a
more recent version of GCC.
Thanks,
Mingjie