From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18895 invoked by alias); 28 Oct 2015 23:19:25 -0000 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 Received: (qmail 18886 invoked by uid 89); 28 Oct 2015 23:19:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: resqmta-ch2-11v.sys.comcast.net Received: from resqmta-ch2-11v.sys.comcast.net (HELO resqmta-ch2-11v.sys.comcast.net) (69.252.207.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 28 Oct 2015 23:19:24 +0000 Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-11v.sys.comcast.net with comcast id anJj1r0032TL4Rh01nKNNj; Wed, 28 Oct 2015 23:19:22 +0000 Received: from [IPv6:2001:558:6045:a4:40c6:7199:cd03:b02d] ([IPv6:2001:558:6045:a4:40c6:7199:cd03:b02d]) by resomta-ch2-17v.sys.comcast.net with comcast id anKL1r0062ztT3H01nKMyn; Wed, 28 Oct 2015 23:19:22 +0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [patch 2/6] scalar-storage-order merge: C front-end From: Mike Stump In-Reply-To: <3373064.npvgOm9vCi@polaris> Date: Wed, 28 Oct 2015 23:36:00 -0000 Cc: Joseph Myers , gcc-patches@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <397D9865-1C80-47D9-9F35-65BBD7D0B71C@comcast.net> References: <1475877.YmvvkeqT8x@polaris> <1818790.uuKnpis75z@polaris> <3373064.npvgOm9vCi@polaris> To: Eric Botcazou X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg03118.txt.bz2 On Oct 28, 2015, at 3:04 PM, Eric Botcazou wrote: >> Why is -fsso-struct=3D listed only for C and C++, not ObjC and ObjC++? >=20 > Because it was not tested with the latter 2 languages at all and may requ= ire=20 > specific adjustments in the respective front-ends to work. It won=92t. Fixing the language line for the options and a make to ensure = it still builds for you is enough testing. >> Almost all C options should be supported for ObjC and almost all C++ >> options should be supported for ObjC++ (and the existing cases that aren= 't >> in c.opt generally look dubious). >=20 > Sorry, I have zero experience with ObjC and objC++, let alone their front= -end. None is needed. One merely copies the string as found on other options for= your new options, and you=92re done. Indeed, the default should be to alw= ays include the objective languages unless one goes out of their way to exc= lude them.