Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: Eli Zaretskii , djgpp-workers AT delorie DOT com, robert DOT hoehne AT gmx DOT net Date: Tue, 25 Aug 1998 12:42:49 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: GCC incompatibilities References: <199808241743 DOT AA247760603 AT typhoon DOT rose DOT hp DOT com> In-reply-to: Precedence: bulk Eli Zaretskii wrote: > > On Mon, 24 Aug 1998, Andrew Crabtree wrote: > > > > compatibility problems between object files produced by > > > different versions of GCC. > > In many cases, yes. Most seem to be related to c++ stuff. > > Are there *any* problems whatsoever related to C? For example, is the > stock libc.a good for GCC 2.8.1/EGCS/PGCC? > > > The biggest gotchas here have been exception handling and rtti I > > think. > > Is Robert's recommendation to use -fno-exceptions -fno-rtti at all > relevant to C programs which mix objects compiled by different > versions of GCC? Here is my limited experience (only gcc 2.7.2 to 2.8.0): It affects only C++ C libraries can be mixed. You can't mix C++ libraries because 2.8.0 adds some hidden members so when you link 2.8.0 code with 2.7.2 libraries the linker looks for these hidden members and the linkage fails. Looks like -fno-exceptions -fno-rtti avoids the hidden members and hence you can link without problems. SET ------------------------------------ 0 -------------------------------- Visit my home page: http://set-soft.home.ml.org/ or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013