Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 16 Mar 2003 21:01:23 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin gcc 3.4 and cygwin
Message-ID: <20030317020123.GA1109@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20030317015922 DOT 15816 DOT qmail AT web21401 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030317015922.15816.qmail@web21401.mail.yahoo.com>
User-Agent: Mutt/1.5.1i

On Mon, Mar 17, 2003 at 12:59:21PM +1100, Danny Smith wrote:
>Brian Ford wrote:
>
>> Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact.
>> I wanted to know why this was allowed to persist given the simple patch
>> required to fix it, question.  I had seen Mr. Faylor make statements
>> before to the effect of: doubles in structures are not that common so who
>> cares, so I advised caution in his use of that compiler for official
>> Cygwin released software.
>
>Regarding the structure alignment problem:
>
>Adding -malign-double to compile switches should provide forward/backward/MSVC
>compatibility.
>
>The other fix is to rebuild gcc from sources so that -malign-double is
>the default (as it is now on trunk for cygwin).

So did I get this backwards then?  Current cygwin gcc has it wrong,
trunk has it right?

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/