This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: error using 3.3.2 in building apache-1.3.31

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Eric Botcazou <ebotcazou at libertysurf dot fr>
Cc: Edward Peschko <esp5 at pge dot com>, gcc at gcc dot gnu dot org
Date: Thu, 12 Aug 2004 10:59:41 -0700
Subject: Re: error using 3.3.2 in building apache-1.3.31
References: <20040808224527.GA18989@mdssdev05> <411A64C4.90605@specifixinc.com> <20040811121149.A31674@synopsys.com> <20040812044836.GA28632@mdssdev05> <02de01c48094$de620f20$4c989c53@magellan>

On Thu, Aug 12, 2004 at 07:49:16PM +0200, Eric Botcazou wrote:
> > True, but since most of the stuff I'm compiling is C code, I'm assuming
> > that I'm going to have no problems. Is this correct?
> 
> Your mileage may vary.  See http://gcc.gnu.org/gcc-3.4/changes.html

Good point; I had forgotten about the SPARC and MIPS ABI changes.
The changes should not affect most programs, but will affect some.

In the case of the SPARC changes, isn't it the case that programs
that see an incompatible ABI change (because they pass small structures
in registers, say) would also have compatibility problems between older
GCC compilers and Sun's proprietary compiler?

Follow-Ups:
- Re: error using 3.3.2 in building apache-1.3.31
  - From: Eric Botcazou

References:
- error using 3.3.2 in building apache-1.3.31
  - From: Edward Peschko
- Re: error using 3.3.2 in building apache-1.3.31
  - From: James E Wilson
- Re: error using 3.3.2 in building apache-1.3.31
  - From: Joe Buck
- Re: error using 3.3.2 in building apache-1.3.31
  - From: Edward Peschko
- Re: error using 3.3.2 in building apache-1.3.31
  - From: Eric Botcazou

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]