From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 19:58:23 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBEB17A9 for ; Wed, 2 Apr 2014 19:58:23 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B83983FB for ; Wed, 2 Apr 2014 19:58:23 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s32JvwC9058258 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Apr 2014 19:58:22 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: gcc compilation broken with SVN r264042 From: David Chisnall In-Reply-To: <533C6ABE.2000801@protected-networks.net> Date: Wed, 2 Apr 2014 20:58:21 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <307BA2CF-E02A-4D82-B9E5-23AECAEA89DC@FreeBSD.org> References: <533C61B8.7060809@protected-networks.net> <509CAA08-8F00-4ED8-81FF-A51F1ECDC15C@FreeBSD.org> <533C6ABE.2000801@protected-networks.net> To: Michael Butler X-Mailer: Apple Mail (2.1874) Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 19:58:24 -0000 On 2 Apr 2014, at 20:53, Michael Butler = wrote: > cc (GCC) 4.2.1 20070831 patched [FreeBSD] >=20 > .. on .. >=20 > FreeBSD 11.0-CURRENT #22 r263969: Mon Mar 31 10:45:56 EDT 2014 >=20 > Splitting it like .. >=20 > - fn.fn_ptr.cxa_func =3D = (void(*)(void*))GET_BLOCK_FUNCTION(func); > + fn.fn_ptr.cxa_func =3D > + (void(*)(void*)) > + GET_BLOCK_FUNCTION(func); >=20 > .. causes the reported error to point at the GET_BLOCK_FUNCTION. Sorry, I meant split it into different statements. Along the lines of: struct generic_block *b =3D (struct generic_block*)func; void (*fn)(void*,...) =3D b->invoke; fn.fn_ptr.cxa_func =3D (void (*)(void*))fn; > I guess it's time for me to migrate that box to clang :-) Well, I wouldn't object to that, but it would be good to fix this - we = still want to be able to build the base system with gcc (or another = compiler), even if we don't encourage it... David