g++ serious bug in Ubuntu Lucid Lynx
Fri Jun 4 02:49:00 GMT 2010
Bah! It didn't really get sent to the list the first time.
-------- Original Message --------
Subject: Re: g++ serious bug in Ubuntu Lucid Lynx
Date: Thu, 03 Jun 2010 14:30:06 -0700
From: David Daney <email@example.com>
To: David R. Doucette <firstname.lastname@example.org>
CC: 'Ian Lance Taylor' <email@example.com>, firstname.lastname@example.org
On 06/03/2010 01:51 PM, David R. Doucette wrote:
> I believe all that stuff was in the tar file I sent you. I followed the
> instructions on the Web site. However, some of the stuff from the earlier
> versions (Karmic and Jaunty) might be from 32 bit systems since our 64 bit
> systems were the first to be upgraded before we hit the wall. However, the
> version numbers should be the same.
Well, Ian did say that 32-bit and 64-bit ABIs differ with respect to how
they do structure layout. When you switched from 32-bit to 64-bit, you
saw exactly this. So it is probably not really a 'g++ serious bug', but
rather the intended behavior.
Probably your best bet would be to settle on a single ABI (say 32-bit
since that is apparently how your legacy data files are formatted). An
alternative would be to change the way your application reads and writes
its data, so that it doesn't depend on the ABI in use.
> -----Original Message-----
> From: Ian Lance Taylor [mailto:email@example.com]
> Sent: Thursday, June 03, 2010 4:17 PM
> To: David R. Doucette
> Cc: firstname.lastname@example.org
> Subject: Re: g++ serious bug in Ubuntu Lucid Lynx
> "David R. Doucette"<email@example.com> writes:
>> Both gcc and g++ came straight from the Ubuntu distribution.
> We're not Ubuntu developers. We need to know the version of the
> compiler, not the version of Ubuntu. We also need to know how the
> compiler was configured. You can get both pieces of information by
> running "g++ -v".
More information about the Gcc-help