From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 01:19:53 2014 Return-Path: Delivered-To: freebsd-toolchain@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 283CBB69 for ; Mon, 22 Sep 2014 01:19:53 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E17D31E6 for ; Mon, 22 Sep 2014 01:19:52 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id s8M1Jkuw004325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 21 Sep 2014 18:19:46 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id s8M1JkoX004324 for freebsd-toolchain@freebsd.org; Sun, 21 Sep 2014 18:19:46 -0700 (PDT) (envelope-from sgk) Date: Sun, 21 Sep 2014 18:19:46 -0700 From: Steve Kargl To: freebsd-toolchain@freebsd.org Subject: Is this a compiler bug? Message-ID: <20140922011946.GA4317@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 01:19:53 -0000 #include #include int main(void) { uint16_t i; i = 0x3ff0+63; printf("%x\n", i); i = 0x3ff1+63; printf("%x\n", i); i = 0x3ff2+63; printf("%x\n", i); i = 0x3ff3+63; printf("%x\n", i); i = 0x3ff4+63; printf("%x\n", i); i = 0x3ff4+63; printf("%x\n", i); i = 0x3ff6+63; printf("%x\n", i); i = 0x3ff7+63; printf("%x\n", i); i = 0x3ff8+63; printf("%x\n", i); i = 0x3ff9+63; printf("%x\n", i); i = 0x3ffa+63; printf("%x\n", i); i = 0x3ffb+63; printf("%x\n", i); i = 0x3ffc+63; printf("%x\n", i); i = 0x3ffd+63; printf("%x\n", i); i = 0x3ffe+63; printf("%x\n", i); i = 0x3fff+63; printf("%x\n", i); return 0; } -- Steve From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 01:39:06 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 033E9CC4 for ; Mon, 22 Sep 2014 01:39:06 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (Client CN "smtp.me.com", Issuer "VeriSign Class 3 Extended Validation SSL SGC CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA8E5390 for ; Mon, 22 Sep 2014 01:39:05 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0NCA00B9S4KORC50@st11p02mm-asmtp001.mac.com> for freebsd-toolchain@freebsd.org; Mon, 22 Sep 2014 01:38:51 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.28,0.0.0000 definitions=2014-09-22_01:2014-09-19,2014-09-21,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409220017 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.0 \(1985.3\)) Subject: Re: Is this a compiler bug? From: Rui Paulo In-reply-to: <20140922011946.GA4317@troutmask.apl.washington.edu> Date: Sun, 21 Sep 2014 18:38:48 -0700 Content-transfer-encoding: quoted-printable Message-id: <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> References: <20140922011946.GA4317@troutmask.apl.washington.edu> To: Steve Kargl X-Mailer: Apple Mail (2.1985.3) Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 01:39:06 -0000 On Sep 21, 2014, at 18:19, Steve Kargl = wrote: >=20 > #include > #include >=20 > int > main(void) > { > uint16_t i; > i =3D 0x3ff0+63; printf("%x\n", i); > i =3D 0x3ff1+63; printf("%x\n", i); > i =3D 0x3ff2+63; printf("%x\n", i); > i =3D 0x3ff3+63; printf("%x\n", i); > i =3D 0x3ff4+63; printf("%x\n", i); > i =3D 0x3ff4+63; printf("%x\n", i); > i =3D 0x3ff6+63; printf("%x\n", i); > i =3D 0x3ff7+63; printf("%x\n", i); > i =3D 0x3ff8+63; printf("%x\n", i); > i =3D 0x3ff9+63; printf("%x\n", i); > i =3D 0x3ffa+63; printf("%x\n", i); > i =3D 0x3ffb+63; printf("%x\n", i); > i =3D 0x3ffc+63; printf("%x\n", i); > i =3D 0x3ffd+63; printf("%x\n", i); > i =3D 0x3ffe+63; printf("%x\n", i); > i =3D 0x3fff+63; printf("%x\n", i); > return 0; > } Looks like it. Please file a bug report with LLVM. -- Rui Paulo From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 01:43:34 2014 Return-Path: Delivered-To: freebsd-toolchain@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 C9C1BCFF for ; Mon, 22 Sep 2014 01:43:34 +0000 (UTC) Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtpout002.mac.com [17.172.220.237]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (Client CN "smtp.me.com", Issuer "VeriSign Class 3 Extended Validation SSL SGC CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C5B6614 for ; Mon, 22 Sep 2014 01:43:34 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0NCA00LVB4RQN0A0@st11p02mm-asmtp002.mac.com> for freebsd-toolchain@freebsd.org; Mon, 22 Sep 2014 01:43:05 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.28,0.0.0000 definitions=2014-09-22_01:2014-09-19,2014-09-21,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409220018 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.0 \(1985.3\)) Subject: Re: Is this a compiler bug? From: Rui Paulo In-reply-to: <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> Date: Sun, 21 Sep 2014 18:43:01 -0700 Content-transfer-encoding: quoted-printable Message-id: <3D7EBF64-43E5-4255-AC03-8663A52493CD@me.com> References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> To: Steve Kargl X-Mailer: Apple Mail (2.1985.3) Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 01:43:34 -0000 On Sep 21, 2014, at 18:38, Rui Paulo wrote: > On Sep 21, 2014, at 18:19, Steve Kargl = wrote: >>=20 >> #include >> #include >>=20 >> int >> main(void) >> { >> uint16_t i; >> i =3D 0x3ff0+63; printf("%x\n", i); >> i =3D 0x3ff1+63; printf("%x\n", i); >> i =3D 0x3ff2+63; printf("%x\n", i); >> i =3D 0x3ff3+63; printf("%x\n", i); >> i =3D 0x3ff4+63; printf("%x\n", i); >> i =3D 0x3ff4+63; printf("%x\n", i); >> i =3D 0x3ff6+63; printf("%x\n", i); >> i =3D 0x3ff7+63; printf("%x\n", i); >> i =3D 0x3ff8+63; printf("%x\n", i); >> i =3D 0x3ff9+63; printf("%x\n", i); >> i =3D 0x3ffa+63; printf("%x\n", i); >> i =3D 0x3ffb+63; printf("%x\n", i); >> i =3D 0x3ffc+63; printf("%x\n", i); >> i =3D 0x3ffd+63; printf("%x\n", i); >> i =3D 0x3ffe+63; printf("%x\n", i); >> i =3D 0x3fff+63; printf("%x\n", i); >> return 0; >> } >=20 > Looks like it. Please file a bug report with LLVM. Actually, the same compile error exists with gcc 4.7. I'm not sure why. -- Rui Paulo From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 01:48:54 2014 Return-Path: Delivered-To: freebsd-toolchain@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 DE868D8D for ; Mon, 22 Sep 2014 01:48:54 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB8F1636 for ; Mon, 22 Sep 2014 01:48:54 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id s8M1msNA004484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 21 Sep 2014 18:48:54 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id s8M1mshI004483; Sun, 21 Sep 2014 18:48:54 -0700 (PDT) (envelope-from sgk) Date: Sun, 21 Sep 2014 18:48:54 -0700 From: Steve Kargl To: Rui Paulo Subject: Re: Is this a compiler bug? Message-ID: <20140922014853.GA4469@troutmask.apl.washington.edu> References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 01:48:55 -0000 On Sun, Sep 21, 2014 at 06:38:48PM -0700, Rui Paulo wrote: > On Sep 21, 2014, at 18:19, Steve Kargl wrote: > > > > #include > > #include > > > > int > > main(void) > > { > > uint16_t i; > > i = 0x3ff0+63; printf("%x\n", i); > > i = 0x3ff1+63; printf("%x\n", i); > > i = 0x3ff2+63; printf("%x\n", i); > > i = 0x3ff3+63; printf("%x\n", i); > > i = 0x3ff4+63; printf("%x\n", i); > > i = 0x3ff4+63; printf("%x\n", i); > > i = 0x3ff6+63; printf("%x\n", i); > > i = 0x3ff7+63; printf("%x\n", i); > > i = 0x3ff8+63; printf("%x\n", i); > > i = 0x3ff9+63; printf("%x\n", i); > > i = 0x3ffa+63; printf("%x\n", i); > > i = 0x3ffb+63; printf("%x\n", i); > > i = 0x3ffc+63; printf("%x\n", i); > > i = 0x3ffd+63; printf("%x\n", i); > > i = 0x3ffe+63; printf("%x\n", i); > > i = 0x3fff+63; printf("%x\n", i); > > return 0; > > } > > Looks like it. Please file a bug report with LLVM. > Unfortunately, llvm requires an account to report bugs. -- Steve From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 02:21:08 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE67E28F for ; Mon, 22 Sep 2014 02:21:08 +0000 (UTC) Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtpout002.mac.com [17.172.220.237]) (using TLSv1 with cipher DES-CBC3-SHA (112/168 bits)) (Client CN "smtp.me.com", Issuer "VeriSign Class 3 Extended Validation SSL SGC CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0357987 for ; Mon, 22 Sep 2014 02:21:08 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit (built Jun 6 2014)) with ESMTPSA id <0NCA007TW6IPF800@st11p02mm-asmtp002.mac.com> for freebsd-toolchain@freebsd.org; Mon, 22 Sep 2014 02:20:52 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52,1.0.28,0.0.0000 definitions=2014-09-22_01:2014-09-19,2014-09-21,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409220025 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.0 \(1985.3\)) Subject: Re: Is this a compiler bug? From: Rui Paulo In-reply-to: <20140922014853.GA4469@troutmask.apl.washington.edu> Date: Sun, 21 Sep 2014 19:20:49 -0700 Content-transfer-encoding: quoted-printable Message-id: <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> <20140922014853.GA4469@troutmask.apl.washington.edu> To: Steve Kargl X-Mailer: Apple Mail (2.1985.3) Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 02:21:09 -0000 On Sep 21, 2014, at 18:48, Steve Kargl = wrote: > On Sun, Sep 21, 2014 at 06:38:48PM -0700, Rui Paulo wrote: >> On Sep 21, 2014, at 18:19, Steve Kargl = wrote: >>>=20 >>> #include >>> #include >>>=20 >>> int >>> main(void) >>> { >>> uint16_t i; >>> i =3D 0x3ff0+63; printf("%x\n", i); >>> i =3D 0x3ff1+63; printf("%x\n", i); >>> i =3D 0x3ff2+63; printf("%x\n", i); >>> i =3D 0x3ff3+63; printf("%x\n", i); >>> i =3D 0x3ff4+63; printf("%x\n", i); >>> i =3D 0x3ff4+63; printf("%x\n", i); >>> i =3D 0x3ff6+63; printf("%x\n", i); >>> i =3D 0x3ff7+63; printf("%x\n", i); >>> i =3D 0x3ff8+63; printf("%x\n", i); >>> i =3D 0x3ff9+63; printf("%x\n", i); >>> i =3D 0x3ffa+63; printf("%x\n", i); >>> i =3D 0x3ffb+63; printf("%x\n", i); >>> i =3D 0x3ffc+63; printf("%x\n", i); >>> i =3D 0x3ffd+63; printf("%x\n", i); >>> i =3D 0x3ffe+63; printf("%x\n", i); >>> i =3D 0x3fff+63; printf("%x\n", i); >>> return 0; >>> } >>=20 >> Looks like it. Please file a bug report with LLVM. >>=20 >=20 > Unfortunately, llvm requires an account to report bugs. I think I know what's happening: "e" is being parsed as scientific = notation. -- Rui Paulo From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 05:46:55 2014 Return-Path: Delivered-To: freebsd-toolchain@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 7A327C56 for ; Mon, 22 Sep 2014 05:46:55 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C4EB9D52 for ; Mon, 22 Sep 2014 05:46:54 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA18820; Mon, 22 Sep 2014 08:46:44 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XVwSS-0005hA-5c; Mon, 22 Sep 2014 08:46:44 +0300 Message-ID: <541FB79F.1070002@FreeBSD.org> Date: Mon, 22 Sep 2014 08:46:07 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Rui Paulo , Steve Kargl Subject: Re: Is this a compiler bug? References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> <20140922014853.GA4469@troutmask.apl.washington.edu> <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> In-Reply-To: <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 05:46:55 -0000 On 22/09/2014 05:20, Rui Paulo wrote: > On Sep 21, 2014, at 18:48, Steve Kargl wrote: >> On Sun, Sep 21, 2014 at 06:38:48PM -0700, Rui Paulo wrote: >>> On Sep 21, 2014, at 18:19, Steve Kargl wrote: >>>> >>>> #include >>>> #include >>>> >>>> int >>>> main(void) >>>> { >>>> uint16_t i; >>>> i = 0x3ff0+63; printf("%x\n", i); >>>> i = 0x3ff1+63; printf("%x\n", i); >>>> i = 0x3ff2+63; printf("%x\n", i); >>>> i = 0x3ff3+63; printf("%x\n", i); >>>> i = 0x3ff4+63; printf("%x\n", i); >>>> i = 0x3ff4+63; printf("%x\n", i); >>>> i = 0x3ff6+63; printf("%x\n", i); >>>> i = 0x3ff7+63; printf("%x\n", i); >>>> i = 0x3ff8+63; printf("%x\n", i); >>>> i = 0x3ff9+63; printf("%x\n", i); >>>> i = 0x3ffa+63; printf("%x\n", i); >>>> i = 0x3ffb+63; printf("%x\n", i); >>>> i = 0x3ffc+63; printf("%x\n", i); >>>> i = 0x3ffd+63; printf("%x\n", i); >>>> i = 0x3ffe+63; printf("%x\n", i); >>>> i = 0x3fff+63; printf("%x\n", i); >>>> return 0; >>>> } >>> >>> Looks like it. Please file a bug report with LLVM. >>> >> >> Unfortunately, llvm requires an account to report bugs. > > I think I know what's happening: "e" is being parsed as scientific notation. Interesting! One of the cases where the whitespace matters? -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 05:51:16 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1CEC7D93 for ; Mon, 22 Sep 2014 05:51:16 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CBF6EDFE for ; Mon, 22 Sep 2014 05:51:15 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::3123:1b4d:9ccf:5d38] (unknown [IPv6:2001:7b8:3a7:0:3123:1b4d:9ccf:5d38]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id ED3A3B803; Mon, 22 Sep 2014 07:51:09 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_F81B6876-05B0-4F20-A886-279FA219CE07"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Is this a compiler bug? From: Dimitry Andric In-Reply-To: <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> Date: Mon, 22 Sep 2014 07:50:56 +0200 Message-Id: <8B883BB9-8A59-4197-A69D-210229F8EA86@FreeBSD.org> References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> <20140922014853.GA4469@troutmask.apl.washington.edu> <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> To: Rui Paulo X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-toolchain@freebsd.org, Steve Kargl X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 05:51:16 -0000 --Apple-Mail=_F81B6876-05B0-4F20-A886-279FA219CE07 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 22 Sep 2014, at 04:20, Rui Paulo wrote: > On Sep 21, 2014, at 18:48, Steve Kargl = wrote: >> On Sun, Sep 21, 2014 at 06:38:48PM -0700, Rui Paulo wrote: >>> On Sep 21, 2014, at 18:19, Steve Kargl = wrote: >>>>=20 >>>> #include >>>> #include >>>>=20 >>>> int >>>> main(void) >>>> { >>>> uint16_t i; >>>> i =3D 0x3ff0+63; printf("%x\n", i); >>>> i =3D 0x3ff1+63; printf("%x\n", i); >>>> i =3D 0x3ff2+63; printf("%x\n", i); >>>> i =3D 0x3ff3+63; printf("%x\n", i); >>>> i =3D 0x3ff4+63; printf("%x\n", i); >>>> i =3D 0x3ff4+63; printf("%x\n", i); >>>> i =3D 0x3ff6+63; printf("%x\n", i); >>>> i =3D 0x3ff7+63; printf("%x\n", i); >>>> i =3D 0x3ff8+63; printf("%x\n", i); >>>> i =3D 0x3ff9+63; printf("%x\n", i); >>>> i =3D 0x3ffa+63; printf("%x\n", i); >>>> i =3D 0x3ffb+63; printf("%x\n", i); >>>> i =3D 0x3ffc+63; printf("%x\n", i); >>>> i =3D 0x3ffd+63; printf("%x\n", i); >>>> i =3D 0x3ffe+63; printf("%x\n", i); >>>> i =3D 0x3fff+63; printf("%x\n", i); >>>> return 0; >>>> } >>>=20 >>> Looks like it. Please file a bug report with LLVM. >>>=20 >>=20 >> Unfortunately, llvm requires an account to report bugs. >=20 > I think I know what's happening: "e" is being parsed as scientific = notation. Yes, this is an unfortunate side effect of hexadecimal float notation (either in C99, or as a gcc extension [1]). -Dimitry [1] https://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html --Apple-Mail=_F81B6876-05B0-4F20-A886-279FA219CE07 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQfuMsACgkQsF6jCi4glqOC5QCeL64bAJ76XcUVZPm3zn2GplKj rz0Anir6ua7NijYzURLGn4ooOLLrxpEJ =oDxV -----END PGP SIGNATURE----- --Apple-Mail=_F81B6876-05B0-4F20-A886-279FA219CE07-- From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 16:20:36 2014 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D110CE0; Mon, 22 Sep 2014 16:20:36 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EACCFFC; Mon, 22 Sep 2014 16:20:36 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id s8MGKYAH007965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Sep 2014 09:20:34 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id s8MGKYBL007964; Mon, 22 Sep 2014 09:20:34 -0700 (PDT) (envelope-from sgk) Date: Mon, 22 Sep 2014 09:20:34 -0700 From: Steve Kargl To: Andriy Gapon Subject: Re: Is this a compiler bug? Message-ID: <20140922162034.GA7918@troutmask.apl.washington.edu> References: <20140922011946.GA4317@troutmask.apl.washington.edu> <670269FD-F75F-4044-8F3C-0260F58A70E2@me.com> <20140922014853.GA4469@troutmask.apl.washington.edu> <2EB3354D-0F65-4A79-A378-7F397911284A@me.com> <541FB79F.1070002@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <541FB79F.1070002@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@FreeBSD.org, Rui Paulo X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 16:20:36 -0000 On Mon, Sep 22, 2014 at 08:46:07AM +0300, Andriy Gapon wrote: > On 22/09/2014 05:20, Rui Paulo wrote: > > On Sep 21, 2014, at 18:48, Steve Kargl wrote: > >> On Sun, Sep 21, 2014 at 06:38:48PM -0700, Rui Paulo wrote: > >>> On Sep 21, 2014, at 18:19, Steve Kargl wrote: > >>>> > >>>> #include > >>>> #include > >>>> > >>>> int > >>>> main(void) > >>>> { > >>>> uint16_t i; > >>>> i = 0x3ffe+63; printf("%x\n", i); > >>>> return 0; > >>>> } > >>> > >>> Looks like it. Please file a bug report with LLVM. > >>> > >> > >> Unfortunately, llvm requires an account to report bugs. > > > > I think I know what's happening: "e" is being parsed as > > scientific notation. > > Interesting! One of the cases where the whitespace matters? > In a discussion on a GCC list, I was pointed to the section of n1256.pdf where preprocessing numbers are discussed. 0x3ffe+63 is preprocessed as a single token. When the parser finally gets around to classifying this token, it is neither a valid integer constant nor floating point constant. It's just a weird feature (idiosyncrasy?) of the C language. -- Steve From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 22 23:10:28 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE81DA9F; Mon, 22 Sep 2014 23:10:28 +0000 (UTC) Received: from smtpout1.timeweb.ru (smtpout1.timeweb.ru [92.53.117.15]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F4D776C; Mon, 22 Sep 2014 23:10:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=B6Z3FikSfrl55baKNfiUysZCDcmpPt43pbYapnh6iJI=; b=Y/YQ1zHiBahOdDhUq18BoXiWIap5N11ByQnUwu+dl/YBDhPmzxncJv3NLEYDt+twFi5ef2Gi79D8Ispx/BTlt8NCd2ZHusDlaCSWXnvk6NnYXgVhBElx2kwvKkG8OqzxyA9SfM+Ob35wQj+EMyAcSgFtprU73oIgtFihbQqvnNQ=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWCkL-0005h1-FB; Tue, 23 Sep 2014 03:10:17 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 0E8C1FC9; Tue, 23 Sep 2014 03:10:17 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id DD4F826785; Tue, 23 Sep 2014 03:10:16 +0400 (MSK) Date: Tue, 23 Sep 2014 03:10:16 +0400 From: Dmitry Marakasov To: freebsd-stable@FreeBSD.org Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140922231016.GA1301@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140228154328.GA13454@hades.panopticon> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Sep 2014 23:10:28 -0000 * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > > > I've been getting some failure mails from pkg building cluster related > > > to clang crashes: > > > > > > http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s/logs/arx-libertatis-1.0.3_2.log > > > http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/logs/supertuxkart-0.8.1.log > > > > > > At first I thought they'll go away with clang 3.4, but recently I've > > > added HEAD jail to my tinderbox and reproduced these. Also a reason > > > of crashes become apparent: c++ eats all available memoty (15G RSS > > > in my case). > > > > > > I though of investigating these further, but wanted to check if it's > > > already known first. > > > > There are a few known OOM bugs in 3.4, but from the logs it is not > > immediately apparent if you are hitting those, or if they are new bugs. > > Note that it affects both 3.3 and 3.4. I think it was triggered by > something unrelated to clang update, maybe libc++ update. > > > To be able to figure that out, we need the files mentioned in clang's > > diagnostic messages, e.g. for arx-libertatis: > > > > /tmp/Input-XkKTNq.cpp > > /tmp/Input-XkKTNq.sh > > Here's one from arx-libertatis: > > http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 > > The bug is reproducible on my 10.x with both system clang 3.3 (after > removing -vectorize-loops -vectorize-slp options) and with clang 3.4 > from ports. I'll just remind that this is still an issue, and it's getting into 10.1. Could we maybe disable compiler features with lead to these crashes? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-toolchain@FreeBSD.ORG Tue Sep 23 05:32:50 2014 Return-Path: Delivered-To: freebsd-toolchain@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 D5559BC5; Tue, 23 Sep 2014 05:32:50 +0000 (UTC) Received: from smtp1.tnnet.fi (smtp1.tnnet.fi [IPv6:2001:40e8:10:11:89:236:117:164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.tnnet.fi", Issuer "Go Daddy Secure Certification Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B79AE27; Tue, 23 Sep 2014 05:32:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.tnnet.fi (Postfix) with ESMTP id DE265181AE7; Tue, 23 Sep 2014 08:32:36 +0300 (EEST) X-Virus-Scanned: amavisd-new at tnnet.fi Received: from smtp1.tnnet.fi ([127.0.0.1]) by localhost (mx2.tnnet.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fL8BKzVn0ncW; Tue, 23 Sep 2014 08:32:34 +0300 (EEST) Received: from [192.168.0.2] (unknown [213.185.47.6]) by smtp1.tnnet.fi (Postfix) with ESMTP id 5B3EE1812CE; Tue, 23 Sep 2014 08:32:34 +0300 (EEST) Message-ID: <542105A3.4090507@iki.fi> Date: Tue, 23 Sep 2014 08:31:15 +0300 From: Pasi Parviainen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Dmitry Marakasov Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> In-Reply-To: <20140922231016.GA1301@hades.panopticon> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Dimitry Andric , freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Sep 2014 05:32:50 -0000 On 23.9.2014 2:10, Dmitry Marakasov wrote: > * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > >>>> I've been getting some failure mails from pkg building cluster related >>>> to clang crashes: >>>> >>>> http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s/logs/arx-libertatis-1.0.3_2.log >>>> http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/logs/supertuxkart-0.8.1.log >>>> >>>> At first I thought they'll go away with clang 3.4, but recently I've >>>> added HEAD jail to my tinderbox and reproduced these. Also a reason >>>> of crashes become apparent: c++ eats all available memoty (15G RSS >>>> in my case). >>>> >>>> I though of investigating these further, but wanted to check if it's >>>> already known first. >>> >>> There are a few known OOM bugs in 3.4, but from the logs it is not >>> immediately apparent if you are hitting those, or if they are new bugs. >> >> Note that it affects both 3.3 and 3.4. I think it was triggered by >> something unrelated to clang update, maybe libc++ update. >> >>> To be able to figure that out, we need the files mentioned in clang's >>> diagnostic messages, e.g. for arx-libertatis: >>> >>> /tmp/Input-XkKTNq.cpp >>> /tmp/Input-XkKTNq.sh >> >> Here's one from arx-libertatis: >> >> http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 >> >> The bug is reproducible on my 10.x with both system clang 3.3 (after >> removing -vectorize-loops -vectorize-slp options) and with clang 3.4 >> from ports. > > I'll just remind that this is still an issue, and it's getting into > 10.1. Could we maybe disable compiler features with lead to these > crashes? > This seems to be same issue as in http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch review going on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html. Your test case is reproducible with the trunk of llvm/clang and the patch in review resolves it. Other workaround is to disable generation of debug information by removing -g flag. Pasi From owner-freebsd-toolchain@FreeBSD.ORG Tue Sep 23 09:59:10 2014 Return-Path: Delivered-To: freebsd-toolchain@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 1359AC39; Tue, 23 Sep 2014 09:59:10 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C45ADDCD; Tue, 23 Sep 2014 09:59:09 +0000 (UTC) Received: from [192.168.2.2] (unknown [77.243.161.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1A5F8B803; Tue, 23 Sep 2014 11:58:58 +0200 (CEST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD From: Dimitry Andric In-Reply-To: <542105A3.4090507@iki.fi> Date: Tue, 23 Sep 2014 11:58:49 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> To: Pasi Parviainen X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-stable@FreeBSD.org, freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Sep 2014 09:59:10 -0000 On 23 Sep 2014, at 07:31, Pasi Parviainen = wrote: > On 23.9.2014 2:10, Dmitry Marakasov wrote: >> * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: >>>>> I've been getting some failure mails from pkg building cluster = related >>>>> to clang crashes: >>>>>=20 >>>>> = http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s= /logs/arx-libertatis-1.0.3_2.log >>>>> = http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/= logs/supertuxkart-0.8.1.log ... >>> http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 >>>=20 >>> The bug is reproducible on my 10.x with both system clang 3.3 (after >>> removing -vectorize-loops -vectorize-slp options) and with clang 3.4 >>> from ports. >>=20 >> I'll just remind that this is still an issue, and it's getting into >> 10.1. Could we maybe disable compiler features with lead to these >> crashes? >>=20 >=20 > This seems to be same issue as in = http://llvm.org/bugs/show_bug.cgi?id=3D20893 for which there is patch = review going = onhttp://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236= 415.html. >=20 > Your test case is reproducible with the trunk of llvm/clang and the = patch in review resolves it. Other workaround is to disable generation = of debug information by removing -g flag. Hm, I had assumed this problem was fixed by importing r203311 from upstream llvm trunk, in head r263313. But apparently it is not. The upstream patch seems to fix your specific test case, but it is still in review, so I prefer to wait until it is actually committed, before I import it. -Dimitry From owner-freebsd-toolchain@FreeBSD.ORG Tue Sep 23 11:45:01 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7958A1F9; Tue, 23 Sep 2014 11:45:01 +0000 (UTC) Received: from smtpout7.timeweb.ru (smtpout7.timeweb.ru [92.53.117.21]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2761ED56; Tue, 23 Sep 2014 11:45:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=VjhwBVHyACAK9MgfbNoN9HjfiGxKi9fp4AxfNm4WZ2o=; b=JoY1Q6rM/OzxoEm/SzoikTAJCdrD3t89AZjPD8Z1BMQj9IiD8Yavn5Ia7g4HPg4y4saZehC2DXQwOdzMcB2FCWyxr0R8CC0V/pTKPSyfQLwSBNgFSL/LD61RMCOtnDsjK1od0nIuwJkliMLdougaXFSkkAKXfXAfgZGiHCYJN9k=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWOWX-0004pW-9w; Tue, 23 Sep 2014 15:44:49 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id A6F472CA; Tue, 23 Sep 2014 15:44:48 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 5A88E44755; Tue, 23 Sep 2014 15:44:48 +0400 (MSK) Date: Tue, 23 Sep 2014 15:44:48 +0400 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140923114447.GB1301@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Sep 2014 11:45:01 -0000 * Dimitry Andric (dim@FreeBSD.org) wrote: > > This seems to be same issue as in > > http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch > > review going > > on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html. > > > > Your test case is reproducible with the trunk of llvm/clang and > > the patch in review resolves it. Other workaround is to disable > > generation of debug information by removing -g flag. > > Hm, I had assumed this problem was fixed by importing r203311 from > upstream llvm trunk, in head r263313. But apparently it is not. > > The upstream patch seems to fix your specific test case, but it is still > in review, so I prefer to wait until it is actually committed, before I > import it. Which worries me is what we do if it's not reviewd until the release. We can't just tell users to "remove -g flag", can't we? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-toolchain@FreeBSD.ORG Tue Sep 23 13:05:49 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3430FA2A; Tue, 23 Sep 2014 13:05:49 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0AF3AAC; Tue, 23 Sep 2014 13:05:48 +0000 (UTC) Received: from [192.168.2.2] (unknown [77.243.161.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B972AB803; Tue, 23 Sep 2014 15:05:42 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD From: Dimitry Andric In-Reply-To: <20140923114447.GB1301@hades.panopticon> Date: Tue, 23 Sep 2014 15:05:29 +0200 Message-Id: <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> <20140923114447.GB1301@hades.panopticon> To: Dmitry Marakasov X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Sep 2014 13:05:49 -0000 --Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23 Sep 2014, at 13:44, Dmitry Marakasov wrote: > * Dimitry Andric (dim@FreeBSD.org) wrote: >=20 >>> This seems to be same issue as in >>> http://llvm.org/bugs/show_bug.cgi?id=3D20893 for which there is = patch >>> review going >>> on = http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/23641= 5.html. >>>=20 >>> Your test case is reproducible with the trunk of llvm/clang and >>> the patch in review resolves it. Other workaround is to disable >>> generation of debug information by removing -g flag. >>=20 >> Hm, I had assumed this problem was fixed by importing r203311 from >> upstream llvm trunk, in head r263313. But apparently it is not. >>=20 >> The upstream patch seems to fix your specific test case, but it is = still >> in review, so I prefer to wait until it is actually committed, before = I >> import it. >=20 > Which worries me is what we do if it's not reviewd until the release. = We > can't just tell users to "remove -g flag", can't we? I don't expect the review to take very long, but this is how it goes with releases. At some point, the release is cut, some bugs don't get fixed, and you will simply have to live with them. In any case, it entirely depends on how many ports it affects. I have the impression it is just a few particular ports having this issue? -Dimitry --Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQhcB4ACgkQsF6jCi4glqOiwgCg82MucrJ2w4sSohXqrG7Yb6jT VwQAn1ueoLb/j54vQEjbTMyhV/d3AqS7 =9Jdh -----END PGP SIGNATURE----- --Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52-- From owner-freebsd-toolchain@FreeBSD.ORG Tue Sep 23 17:59:31 2014 Return-Path: Delivered-To: freebsd-toolchain@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 62026F90; Tue, 23 Sep 2014 17:59:31 +0000 (UTC) Received: from smtpout1.timeweb.ru (smtpout1.timeweb.ru [92.53.117.15]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F315A7; Tue, 23 Sep 2014 17:59:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=PFr/udPhUhdHcqCxWxva2GKdwN7gKpXdEG7L3eIAd24=; b=OjlLP5PluI9U6UE7lP7I9qfB/ZcR6utZnTyopr0TO/7HDfMAXz4q5shoAR270zRACt0pC01tWMHuYqyAzOAlViatr9A/jskskzOpU84cRe73jisaqiHGPcQX5ouLyUQBSxVek7uGJySgbZJMzTgg79qPuc4QpAm4NhEC3c3LZJI=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWUN1-0006qx-8D; Tue, 23 Sep 2014 21:59:23 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 93557549; Tue, 23 Sep 2014 21:59:22 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 6DFF619213; Tue, 23 Sep 2014 21:59:22 +0400 (MSK) Date: Tue, 23 Sep 2014 21:59:22 +0400 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140923175922.GA98560@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> <20140923114447.GB1301@hades.panopticon> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 23 Sep 2014 17:59:31 -0000 * Dimitry Andric (dim@FreeBSD.org) wrote: > >>> This seems to be same issue as in > >>> http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch > >>> review going > >>> on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html. > >>> > >>> Your test case is reproducible with the trunk of llvm/clang and > >>> the patch in review resolves it. Other workaround is to disable > >>> generation of debug information by removing -g flag. > >> > >> Hm, I had assumed this problem was fixed by importing r203311 from > >> upstream llvm trunk, in head r263313. But apparently it is not. > >> > >> The upstream patch seems to fix your specific test case, but it is still > >> in review, so I prefer to wait until it is actually committed, before I > >> import it. > > > > Which worries me is what we do if it's not reviewd until the release. We > > can't just tell users to "remove -g flag", can't we? > > I don't expect the review to take very long, but this is how it goes > with releases. At some point, the release is cut, some bugs don't get > fixed, and you will simply have to live with them. That seems too critical for me to live with it. > In any case, it entirely depends on how many ports it affects. I have > the impression it is just a few particular ports having this issue? Probably yes, but more important is user's private code which may be also affected. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-toolchain@FreeBSD.ORG Thu Sep 25 22:46:46 2014 Return-Path: Delivered-To: freebsd-toolchain@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 2CA3DCD2; Thu, 25 Sep 2014 22:46:46 +0000 (UTC) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD7FBC6F; Thu, 25 Sep 2014 22:46:45 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id x13so5990440qcv.9 for ; Thu, 25 Sep 2014 15:46:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=a76s+FYI6vw0sM8t7jrFD1TR/coYIoN7TvXrCYwZ2Qg=; b=srr9pQyj1j+B1JDvbc338cfmTJV1zMAsW7jkQ5dTKXMODxmo05FE1sJEDazx3YUWzi FSADcfmWf2aLII6fTLLn1SN04n452S1xl6qX+yVFWnnVTbVXzeC3z7rl69ehL/2iyzKm z0CKAgGrYNmAYcfFGtKAbMoB6QuYgG7J+fK+dNRe+sUwzVhxmxwT6HV77YvU+XwBrnSi Nx4Wv/NqwCuTav1QdLhoYQNrh+4xPI0YxseIDvb2NzFG3prh/io7gcsArfyn+jmV2TuD +tcGrvMup3TeGWOUWynTRcC/RjJi/0xWo1Uw/ZYUVIf0DGtuToIe4YGLNSgT79cXylZT 6kXg== X-Received: by 10.140.102.215 with SMTP id w81mr25589102qge.67.1411685204868; Thu, 25 Sep 2014 15:46:44 -0700 (PDT) Received: from ip-172-31-25-62.ec2.internal (ec2-54-85-57-1.compute-1.amazonaws.com. [54.85.57.1]) by mx.google.com with ESMTPSA id h30sm3192266qge.38.2014.09.25.15.46.43 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Sep 2014 15:46:44 -0700 (PDT) Sender: Mark Johnston Date: Thu, 25 Sep 2014 22:51:42 +0000 From: Mark Johnston To: Andriy Gapon Subject: Re: WITH_CTF vs -g Message-ID: <20140925225142.GC2501@ip-172-31-25-62.ec2.internal> References: <54108909.7050908@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54108909.7050908@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@FreeBSD.org, freebsd-dtrace@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 22:46:46 -0000 On Wed, Sep 10, 2014 at 08:23:21PM +0300, Andriy Gapon wrote: > > In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as I can see, > there is nothing to generate CTF data from. Forcing an end-user to remember to > additionally pass -g is not nice. > > Also, I think that we can always have -g in CTFFLAGS, because the stripping step > takes care of the original DWARF data in any case. But I am not 100% sure about > this. > > What do you think? > Thanks! Hi Andriy, Are you planning to go through with this? I was just about to post this exact question, but then I remembered that you already have. :) FWIW, the diff I have in mind is below. It also removes some checks that I think are unnecessary from bsd.{lib,prog}.mk. It is not fully tested, but seems to work for me. I'm also not sure about unconditionally passing -g to ctfconvert and ctfmerge. Thanks, -Mark diff --git a/share/mk/bsd.lib.mk b/share/mk/bsd.lib.mk index f0acf16..c6b689d 100644 --- a/share/mk/bsd.lib.mk +++ b/share/mk/bsd.lib.mk @@ -36,7 +36,7 @@ NO_WERROR= .if defined(DEBUG_FLAGS) CFLAGS+= ${DEBUG_FLAGS} -.if ${MK_CTF} != "no" && ${DEBUG_FLAGS:M-g} != "" +.if ${MK_CTF} != "no" CTFFLAGS+= -g .endif .else diff --git a/share/mk/bsd.own.mk b/share/mk/bsd.own.mk index 486914b..32556a1 100644 --- a/share/mk/bsd.own.mk +++ b/share/mk/bsd.own.mk @@ -128,6 +128,7 @@ ____: .if ${MK_CTF} != "no" CTFCONVERT_CMD= ${CTFCONVERT} ${CTFFLAGS} ${.TARGET} +DEBUG_FLAGS?= -g .elif defined(.PARSEDIR) || (defined(MAKE_VERSION) && ${MAKE_VERSION} >= 5201111300) CTFCONVERT_CMD= .else diff --git a/share/mk/bsd.prog.mk b/share/mk/bsd.prog.mk index 340950a..e4f7104 100644 --- a/share/mk/bsd.prog.mk +++ b/share/mk/bsd.prog.mk @@ -20,7 +20,7 @@ NO_WERROR= CFLAGS+=${DEBUG_FLAGS} CXXFLAGS+=${DEBUG_FLAGS} -.if ${MK_CTF} != "no" && ${DEBUG_FLAGS:M-g} != "" +.if ${MK_CTF} != "no" CTFFLAGS+= -g .endif .endif From owner-freebsd-toolchain@FreeBSD.ORG Fri Sep 26 14:52:33 2014 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88B6ACF5; Fri, 26 Sep 2014 14:52:33 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57C607AA; Fri, 26 Sep 2014 14:52:32 +0000 (UTC) Received: from [92.247.20.226] (port=1327 helo=[172.16.19.1]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1XXWsp-0003Px-6W; Fri, 26 Sep 2014 10:52:31 -0400 From: "George Neville-Neil" To: "Mark Johnston" Subject: Re: WITH_CTF vs -g Date: Fri, 26 Sep 2014 17:52:24 +0300 Message-ID: <47C2BB52-E2DB-45B2-B6E1-3D05DAEFE32F@neville-neil.com> In-Reply-To: <20140925225142.GC2501@ip-172-31-25-62.ec2.internal> References: <54108909.7050908@FreeBSD.org> <20140925225142.GC2501@ip-172-31-25-62.ec2.internal> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_5AB27897-19E1-4FA4-AD53-58C31E8A8A55_="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Mailer: MailMate (1.8r4469) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com Cc: freebsd-toolchain@FreeBSD.org, freebsd-dtrace@FreeBSD.org, Andriy Gapon X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Sep 2014 14:52:33 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_5AB27897-19E1-4FA4-AD53-58C31E8A8A55_= Content-Type: text/plain On 26 Sep 2014, at 1:51, Mark Johnston wrote: > On Wed, Sep 10, 2014 at 08:23:21PM +0300, Andriy Gapon wrote: >> >> In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as I can see, >> there is nothing to generate CTF data from. Forcing an end-user to remember to >> additionally pass -g is not nice. >> >> Also, I think that we can always have -g in CTFFLAGS, because the stripping step >> takes care of the original DWARF data in any case. But I am not 100% sure about >> this. >> >> What do you think? >> Thanks! > > Hi Andriy, > > Are you planning to go through with this? I was just about to post this > exact question, but then I remembered that you already have. :) > > FWIW, the diff I have in mind is below. It also removes some checks that > I think are unnecessary from bsd.{lib,prog}.mk. It is not fully tested, > but seems to work for me. I'm also not sure about unconditionally > passing -g to ctfconvert and ctfmerge. > Mark, Can you put this up in Phabricator? reviews.freebsd.org Best, George > Thanks, > -Mark > > diff --git a/share/mk/bsd.lib.mk b/share/mk/bsd.lib.mk > index f0acf16..c6b689d 100644 > --- a/share/mk/bsd.lib.mk > +++ b/share/mk/bsd.lib.mk > @@ -36,7 +36,7 @@ NO_WERROR= > .if defined(DEBUG_FLAGS) > CFLAGS+= ${DEBUG_FLAGS} > > -.if ${MK_CTF} != "no" && ${DEBUG_FLAGS:M-g} != "" > +.if ${MK_CTF} != "no" > CTFFLAGS+= -g > .endif > .else > diff --git a/share/mk/bsd.own.mk b/share/mk/bsd.own.mk > index 486914b..32556a1 100644 > --- a/share/mk/bsd.own.mk > +++ b/share/mk/bsd.own.mk > @@ -128,6 +128,7 @@ ____: > > .if ${MK_CTF} != "no" > CTFCONVERT_CMD= ${CTFCONVERT} ${CTFFLAGS} ${.TARGET} > +DEBUG_FLAGS?= -g > .elif defined(.PARSEDIR) || (defined(MAKE_VERSION) && ${MAKE_VERSION} >= 5201111300) > CTFCONVERT_CMD= > .else > diff --git a/share/mk/bsd.prog.mk b/share/mk/bsd.prog.mk > index 340950a..e4f7104 100644 > --- a/share/mk/bsd.prog.mk > +++ b/share/mk/bsd.prog.mk > @@ -20,7 +20,7 @@ NO_WERROR= > CFLAGS+=${DEBUG_FLAGS} > CXXFLAGS+=${DEBUG_FLAGS} > > -.if ${MK_CTF} != "no" && ${DEBUG_FLAGS:M-g} != "" > +.if ${MK_CTF} != "no" > CTFFLAGS+= -g > .endif > .endif > _______________________________________________ > freebsd-dtrace@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace > To unsubscribe, send any mail to "freebsd-dtrace-unsubscribe@freebsd.org" --=_MailMate_5AB27897-19E1-4FA4-AD53-58C31E8A8A55_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEUEARECAAYFAlQlfagACgkQYdh2wUQKM9J8jACeKY01jUvP0JfdM2puK0ma8gyC YC0AmL8Jvyeb2cPVUMWJE8zUKuHvuPE= =08RQ -----END PGP SIGNATURE----- --=_MailMate_5AB27897-19E1-4FA4-AD53-58C31E8A8A55_=-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Sep 26 15:59:40 2014 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4AA67C4D; Fri, 26 Sep 2014 15:59:40 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1F36DE50; Fri, 26 Sep 2014 15:59:38 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA10883; Fri, 26 Sep 2014 18:59:36 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XXXvk-000NvE-F1; Fri, 26 Sep 2014 18:59:36 +0300 Message-ID: <54258D30.8040107@FreeBSD.org> Date: Fri, 26 Sep 2014 18:58:40 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Mark Johnston Subject: Re: WITH_CTF vs -g References: <54108909.7050908@FreeBSD.org> <20140925225142.GC2501@ip-172-31-25-62.ec2.internal> In-Reply-To: <20140925225142.GC2501@ip-172-31-25-62.ec2.internal> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@FreeBSD.org, freebsd-dtrace@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Sep 2014 15:59:40 -0000 On 26/09/2014 01:51, Mark Johnston wrote: > On Wed, Sep 10, 2014 at 08:23:21PM +0300, Andriy Gapon wrote: >> >> In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as I can see, >> there is nothing to generate CTF data from. Forcing an end-user to remember to >> additionally pass -g is not nice. >> >> Also, I think that we can always have -g in CTFFLAGS, because the stripping step >> takes care of the original DWARF data in any case. But I am not 100% sure about >> this. >> >> What do you think? >> Thanks! > > Hi Andriy, > > Are you planning to go through with this? I was just about to post this > exact question, but then I remembered that you already have. :) > > FWIW, the diff I have in mind is below. It also removes some checks that > I think are unnecessary from bsd.{lib,prog}.mk. It is not fully tested, > but seems to work for me. I'm also not sure about unconditionally > passing -g to ctfconvert and ctfmerge. Mark, your change looks like what I was thinking of. I will it a whirl here. Thank you! > diff --git a/share/mk/bsd.lib.mk b/share/mk/bsd.lib.mk > index f0acf16..c6b689d 100644 > --- a/share/mk/bsd.lib.mk > +++ b/share/mk/bsd.lib.mk > @@ -36,7 +36,7 @@ NO_WERROR= > .if defined(DEBUG_FLAGS) > CFLAGS+= ${DEBUG_FLAGS} > > -.if ${MK_CTF} != "no" && ${DEBUG_FLAGS:M-g} != "" > +.if ${MK_CTF} != "no" > CTFFLAGS+= -g > .endif > .else > diff --git a/share/mk/bsd.own.mk b/share/mk/bsd.own.mk > index 486914b..32556a1 100644 > --- a/share/mk/bsd.own.mk > +++ b/share/mk/bsd.own.mk > @@ -128,6 +128,7 @@ ____: > > .if ${MK_CTF} != "no" > CTFCONVERT_CMD= ${CTFCONVERT} ${CTFFLAGS} ${.TARGET} > +DEBUG_FLAGS?= -g > .elif defined(.PARSEDIR) || (defined(MAKE_VERSION) && ${MAKE_VERSION} >= 5201111300) > CTFCONVERT_CMD= > .else > diff --git a/share/mk/bsd.prog.mk b/share/mk/bsd.prog.mk > index 340950a..e4f7104 100644 > --- a/share/mk/bsd.prog.mk > +++ b/share/mk/bsd.prog.mk > @@ -20,7 +20,7 @@ NO_WERROR= > CFLAGS+=${DEBUG_FLAGS} > CXXFLAGS+=${DEBUG_FLAGS} > > -.if ${MK_CTF} != "no" && ${DEBUG_FLAGS:M-g} != "" > +.if ${MK_CTF} != "no" > CTFFLAGS+= -g > .endif > .endif > -- Andriy Gapon From owner-freebsd-toolchain@FreeBSD.ORG Fri Sep 26 17:32:23 2014 Return-Path: Delivered-To: freebsd-toolchain@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 08F9A3AD for ; Fri, 26 Sep 2014 17:32:23 +0000 (UTC) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE949B8A for ; Fri, 26 Sep 2014 17:32:22 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id i13so6044448qae.20 for ; Fri, 26 Sep 2014 10:32:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=GimN+mWLPjMIab/dm5Djl6A1+j3IBSL/OvWbEPUL8WE=; b=Ol+FgRrzYborf6rzQaLYMXPlFWdSfBDiB7ykYnv2Wf0fY76RJGyxb8GdGcYuWHxQDd g5QaEd+EKnlX5jEtSb6yxj3VBAlHdI45DU1g362u4GANerLKNRMd+XXRpalX0BAnmwXZ PGY4eiRB2W0HihJzFnvOn5CC2+0Si0sId3aBJoamr3Ywm6wPha556FpXwXtaWvBot0dS uo5vVS0Khn2aXjidaZ0ZAF6wCrAkMasqoGNzH3FqPqVvcL3S0qYIGKlW0XqLrQ6I2n6T gxU8CEQSInnZNzkk/Gd0yX6BBb3RQHot9InbPiOgXPduT8I9NBApWbkAwZNJhZ03HLWw joMw== X-Gm-Message-State: ALoCoQmnSPkY2pF3gJHUbF1A4m+a+EOx5FnHPGsYlDnr3clL0oj+iVqp7RsI89CmThGxmCfp65zA MIME-Version: 1.0 X-Received: by 10.224.32.138 with SMTP id c10mr18189167qad.1.1411752741041; Fri, 26 Sep 2014 10:32:21 -0700 (PDT) Received: by 10.140.16.183 with HTTP; Fri, 26 Sep 2014 10:32:20 -0700 (PDT) Date: Fri, 26 Sep 2014 11:32:20 -0600 Message-ID: Subject: Re: elftoolchain update? From: Will Andrews To: jkoshy@freebsd.org, kaiw@freebsd.org, freebsd-toolchain@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Sep 2014 17:32:23 -0000 Hi, I've created a git-svn clone of the current elftoolchain, and applied some fixes in a branch: https://github.com/wca/elftoolchain/tree/freebsd Any objections if I update the copy in head using this branch? I've heard nothing from either Kai or Joseph. I'm not done testing yet -- it looks like there are some more bugfixes needed to get ctfconvert to at least run against C++ object files without bailing. Just wanted to know if there are any specific concerns that people might have. A related review involves an update for the ELF headers: https://reviews.freebsd.org/D844 I haven't finished testing this either (need to do an universe build to check for conflicts), but my goal here is to achieve header parity with from elftoolchain, which is largely duplicate. The elftoolchain header exports many more symbols that are used by its userland programs. This would include arch-specific interpretations of some ELF structures. I believe it's appropriate to export these on a global basis, given that userland programs can legitimately be run on object files built for architectures other than the system they're running on. Thanks! --Will. On Wed, Sep 17, 2014 at 5:01 PM, Will Andrews wrote: > Hi, > > I see there have been a lot of updates & fixes to elftoolchain since > the last import into FreeBSD/head nearly 8 months ago. Are there any > plans to update the import? > > I'm asking because it appears that ctfconvert currently crashes > (specifically, due to a bug in dwarf_attrval_unsigned()), if you try > to use it on C++ object files. > > This is easily demonstrated by applying this patch to FreeBSD/head and > building sbin/devd with WITH_CTF=1: > http://people.freebsd.org/~will/add-ctfconvert-to-cpp-object-files.diff > > Justin Gibbs (cc'd) posted about this issue in February, and it's > still a problem: > http://lists.freebsd.org/pipermail/freebsd-toolchain/2014-February/001121.html > > Thanks, > --Will. From owner-freebsd-toolchain@FreeBSD.ORG Fri Sep 26 17:33:16 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBAAF430 for ; Fri, 26 Sep 2014 17:33:16 +0000 (UTC) Received: from nm6-vm5.bullet.mail.gq1.yahoo.com (nm6-vm5.bullet.mail.gq1.yahoo.com [98.136.218.196]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D6D5B9C for ; Fri, 26 Sep 2014 17:33:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1411752790; bh=YV9iCRUuMBfh3l8OeIsqVujmbg/2Q7/+ZckI6+n7okc=; h=Received:Received:Received:X-Yahoo-Newman-Id:Message-ID:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:From:Subject:To:Content-Type:MIME-Version:Reply-To:Date:From:Subject; b=dMgMxUzIGmb5QR4AtL0ttJ/+U80xSnbRQe2+AoLoVOLZY7eaDSs7p53ha3DkkxB7iae5A52fajSLjv2x4nA3HpOFsBZ3vsnwO4OU28qhP2etJ0VOTW377zBOiWP0+191r6YZRGeFJ5fmYT+gs2re1fQfa3qh8CzXV4A4tMleaFPAfg6PXgdqXGwv9a5FQV7BxBjM6kkEThtzUnupCc0636be5J2yJ2QX6/eEqYlDWijjil5kskrHV9IDpfFnoSI8N9VE7IrnXHPnwbTCy82EkRQu94LwQKyvJtxaiMatjqC/Zw7cGAo5mlVVf7h94UTp7kUSn/ual2CJ21F5476oqA== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com; b=EOCXSPi30S9IgzJg3e88IBEfPqwMzsTdQT5llbWNPTJzOcY8myPu1+dOGDBQLAG1jKo29svhkDTEV+fV6yUaUFb8z5xQGVDG3qLmPlCaRuKXrqLr2PdTT1SZjNDfn+f89+zJS5c9hqVGxeHd7Igu8dyP/bMVF1panrWJZ+C8ycOIb4aE0EOSAFtaqgnmAqYu1atEBdwGOaBv061FkpLwxHNvhtTqbjEPU1Rw05HQnwKApwxnoi7MABo9SP46oy9iXNsG4hrA/bcsyZo9Q/jRB6R3A35McdlMkHIyYKZJ9exqDyyDVjfkzmYBE9Uq6ppBSFsZ8CV4s9sTMnwAfTiN1g==; Received: from [216.39.60.182] by nm6.bullet.mail.gq1.yahoo.com with NNFMP; 26 Sep 2014 17:33:10 -0000 Received: from [98.136.164.72] by tm18.bullet.mail.gq1.yahoo.com with NNFMP; 26 Sep 2014 17:33:10 -0000 Received: from [127.0.0.1] by smtp234.mail.gq1.yahoo.com with NNFMP; 26 Sep 2014 17:33:10 -0000 X-Yahoo-Newman-Id: 547211.45875.bm@smtp234.mail.gq1.yahoo.com Message-ID: <547211.45875.bm@smtp234.mail.gq1.yahoo.com> X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: LhIYdJoVM1mU0tOxEWJ4KHIUuUj9tQxdkOVXqnUn2TewUEF AWivkF5RAdfzPxw2Tlb3SKL7k3D_7Omhl63fnn_sGg9OF80MEmqr4WWfRpQA ehc8patJ0D0lJZhA0ZGCqkpLGrN9FcjJPOJCrdOaXUJ5VjiV9oFq9B4BXosI GBS_4vtAIwbeX64z7a4NBYtiGViFBGA6akoyhMPK3V.ocRVVHHF53Ba1F8ux biMhg9Jm0eeeQONlstrSW7JX7JoWKb_Y1w7XJ0VPL6d5EXX3sN3LIZxiDz7Y XK9xA49pN_N0v7BfyldqKojObG5VOXWl4MJTlOLpMhbdZuWB24gg7XxFQRd8 YKRuuYFtx3m.C5ZJbqLoXNHwa9kwGkG1Aany_1swERp9odc9MktFB_pW.yLK 7eOahjbeH3oHXH5YutdwtLTX3_tpTualSGyQaq01ULfaFPcZF53w0Bz9LIBZ NFYQUu9JKEwLD7Qzlftf4YlaNyjAbq3qFa2SUzgbegRHn11GUFEp5StMYjXK pPDpqOLx.kglp6IAJcaHG.RMVcmeCwj9lfqw9OsTn7rNDkiQNE2zH_KGPbqd kTuqtEG4.cPnda2NYesFj9TK3uByBZb_p0rF6mzP9eHSeSa_ZI0qXg6G5Nxx kX8VZpwHfi4A- X-Yahoo-SMTP: hGgPbF6swBAlWp1yb4JJJurNfnI0Kbvn1VyGYCSJvEJmTOiLEqeI From: "Sahar alGhrarri" Subject: I await your response To: "freebsd-toolchain" MIME-Version: 1.0 Reply-To: "Sahar alGhrarri" Date: Fri, 26 Sep 2014 18:33:08 +0100 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 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, 26 Sep 2014 17:33:16 -0000 =EF=BB=BFGreetings, I am Mrs. Sahar alGhrarri, the only surviving member of a family that = was crushed in a bomb-blast during the war in Libya. Currently, I am b= attling with a (partial stroke) which resulted from the shock gotten f= rom the incident. Please view the below link for details: http://www.= wsws.org/articles/2011/jun2011/liby-j20.shtml When my husband whom was a crude oil merchant was alive, we had plans = to use the last days of our lives to disburse part of our resources to= charity organization and several unknown individuals because when we = were much younger in life as a couple, we received financial help from= an unknown individual whom we have not met till this day. The impact = we got from such gesture made us want to do same. Unfortunately, my husband is not alive today to do this with me and my= health is deteriorating so fast; hence I have decided it on our behal= f. Having donated to several individuals and charity organization from= our savings, I have decided to anonymously donate the last of our fam= ily savings to you. Irrespective of your previous financial status, please do accept this = kind and peaceful offer on behalf of my beloved family. Please acknowl= edge Mrs. Sahar Email: sahar-alghram102@gmx.com May war and pains never come close to your dwelling place. Regards Mrs. Sahar alGhrarri