From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17849 invoked by alias); 8 Nov 2011 18:56:25 -0000 Received: (qmail 17832 invoked by uid 22791); 8 Nov 2011 18:56:24 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ww0-f51.google.com (HELO mail-ww0-f51.google.com) (74.125.82.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 Nov 2011 18:56:11 +0000 Received: by wwf27 with SMTP id 27so1069190wwf.8 for ; Tue, 08 Nov 2011 10:56:10 -0800 (PST) Received: by 10.180.18.165 with SMTP id x5mr12491850wid.24.1320778569909; Tue, 08 Nov 2011 10:56:09 -0800 (PST) Received: from [192.168.2.99] (cpc2-cmbg8-0-0-cust61.5-4.cable.virginmedia.com. [82.6.108.62]) by mx.google.com with ESMTPS id bl10sm1422583wib.15.2011.11.08.10.56.07 (version=SSLv3 cipher=OTHER); Tue, 08 Nov 2011 10:56:08 -0800 (PST) Message-ID: <4EB97B39.5030503@gmail.com> Date: Tue, 08 Nov 2011 19:19:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Pedro Alves CC: gcc-patches@gcc.gnu.org, Kai Tietz , Richard Henderson Subject: Re: [patch i386 mingw g++.dg gcc.dg]: Set -mms-bitfields as default for native windows targets References: <201104131136.48795.pedro@codesourcery.com> <201104131149.35301.pedro@codesourcery.com> In-Reply-To: <201104131149.35301.pedro@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-11/txt/msg01230.txt.bz2 On 13/04/2011 11:49, Pedro Alves wrote: > On Wednesday 13 April 2011 11:43:43, Kai Tietz wrote: >>> This is a default ABI change (IIRC, when the option was >>> introduced, it was left off as default so to not break the ABI). >>> >>> Shouldn't we advertise it somewhere? > >> Yes, I did recently a lot of abi changing for mingw's targets. They >> all will need a nice description (and possible ways to get old default >> behavior) in changes.html >> >> I collect them for later. Or do you mean it should be noted earlier? > > As long as it's mentioned somewhere before a release, that's fine > with me. > > (Though mentioning changes as you do them has better chances of > something not getting forgotten, or in case you end up > unavailable. Hope not! :-) ) Now we're coming up for a release.... did this happen? cheers, DaveK