From owner-freebsd-toolchain@FreeBSD.ORG Mon Mar 11 11:06:51 2013 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5B66AB75 for ; Mon, 11 Mar 2013 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 337297E0 for ; Mon, 11 Mar 2013 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2BB6pCI089174 for ; Mon, 11 Mar 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2BB6ohR089172 for freebsd-toolchain@FreeBSD.org; Mon, 11 Mar 2013 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Mar 2013 11:06:50 GMT Message-Id: <201303111106.r2BB6ohR089172@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-toolchain@FreeBSD.org Subject: Current problem reports assigned to freebsd-toolchain@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/175930 toolchain [headers] clang does not define __STDC_ISO_10646__, de 1 problem total. From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 12 13:42:56 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BB8003C6 for ; Tue, 12 Mar 2013 13:42:55 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3D016A25 for ; Tue, 12 Mar 2013 13:42:54 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA18153 for ; Tue, 12 Mar 2013 15:41:26 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <513F3086.2070303@FreeBSD.org> Date: Tue, 12 Mar 2013 15:41:26 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130220 Thunderbird/17.0.3 MIME-Version: 1.0 To: toolchain@FreeBSD.org Subject: libdwarf X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 13:42:56 -0000 It seems that our in-tree libdwarf is not used for anything besides ctf manipulation tools (for dtrace support). I just would like to double-check that this is so. Thank you. -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Mar 15 11:09:29 2013 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8B8F38DD for ; Fri, 15 Mar 2013 11:09:29 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay005.isp.belgacom.be (mailrelay005.isp.belgacom.be [195.238.6.171]) by mx1.freebsd.org (Postfix) with ESMTP id 2727972E for ; Fri, 15 Mar 2013 11:09:28 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAFANcAQ1FtgWFu/2dsb2JhbABDxROBbRd0gioBAQVWIhELGAkWDwkDAgECASceEwYCAQGIFAjCLI8cFoMqA483gSiHGo9jgws7 Received: from 110.97-129-109.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([109.129.97.110]) by relay.skynet.be with ESMTP; 15 Mar 2013 12:08:19 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.6/8.14.6) with ESMTP id r2FB8Ic7001962 for ; Fri, 15 Mar 2013 12:08:19 +0100 (CET) (envelope-from tijl@coosemans.org) Message-ID: <5143011B.1000507@coosemans.org> Date: Fri, 15 Mar 2013 12:08:11 +0100 From: Tijl Coosemans User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130223 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-toolchain@freebsd.org Subject: Re: c89 broken on head? References: <5138CD6B.2050309@coosemans.org> <5138EA4C.1060001@FreeBSD.org> <5138F6EF.6020203@coosemans.org> <51390682.3020703@FreeBSD.org> <48120A0D-8A96-4D62-9C17-AE40E1DEF026@bsdimp.com> <51391CC1.5050200@coosemans.org> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2XINHRXXOKXTNLSRNASBU" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 11:09:29 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2XINHRXXOKXTNLSRNASBU Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2013-03-08 04:07, Eitan Adler wrote: > On 7 March 2013 18:03, Tijl Coosemans wrote: >> On 2013-03-07 22:36, Warner Losh wrote: >>> On Mar 7, 2013, at 2:28 PM, Dimitry Andric wrote: >>>> On 2013-03-07 21:22, Tijl Coosemans wrote: >>>> ... >>>>> Because it's the practical thing to do? Old code/makefiles >>>>> can't possibly be expected to know about compilers of the >>>>> future, while new code can be expected to add -std=3Dc11. >>>> >>>> I am not sure I buy that argument; if it were so, we should >>>> default to K&R C instead, since "old code" (for some arbitrary >>>> definition of "old") could never have been expected to know >>>> about gcc defaulting to gnu89. >> >> My argument was to be practical, i.e. don't change what doesn't >> have to change. >> >>> -std=3Dc11 is defintely too new, but maybe c89 is too old. >>> >>> I thought the c89 program actually was mandated by POSIX, no? >> >> Both were part of POSIX. c89 was a strict ISO c89 compiler, while >> cc was c89, but could additionally accept "an unspecified dialect >> of the C language". >> http://pubs.opengroup.org/onlinepubs/007908799/xcu/cc.html >> >> So, if practicality isn't a good enough argument, maybe POSIX >> compliance is? >=20 > cc is marked as "LEGACY" which is described as optional ("need not > be provided"). > However, I would not be surprised if a non-zero number > of ports depend on cc existing. >=20 > If we are to remove it or change it, I would like to see that > preceded by an exp-run. The autoconf macro AC_PROG_CC_C89 fails when cc is clang. It says no flags are needed to enable C89 mode. It is used by devel/gdb for instance which now had to be patched because inline means something different in gnu89 versus C99. C99 is *not* backward compatible with gnu89: http://svnweb.freebsd.org/ports/head/devel/gdb/files/patch-include-cgen-b= asic-ops.h?revision=3D314093&view=3Dmarkup ------enig2XINHRXXOKXTNLSRNASBU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iF4EAREIAAYFAlFDASIACgkQfoCS2CCgtiuXvwD/Zp09Xr/vhYw5rxIjhzWuZzJH 2ICI07PNiVirfwa/AGoA/iZtRD8g4crHZ9XSINMifsdsObm8LlcgLK5sKJwgct8K =TT2g -----END PGP SIGNATURE----- ------enig2XINHRXXOKXTNLSRNASBU--