From owner-freebsd-toolchain@FreeBSD.ORG Sun Oct 5 01:29:59 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B21B66E8; Sun, 5 Oct 2014 01:29:59 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (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 D6930C8A; Sun, 5 Oct 2014 01:29:58 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id p9so2708107lbv.33 for ; Sat, 04 Oct 2014 18:29:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=uyxAF/QOyt05h5Y4VPKQHoaeu/qrMPo5bRAb9soOtzo=; b=L6UYLHJxruHq+Nv9Klul5tphy99tkCpSJ3Jp4UFkcwgp7WT/5ZTShE9sETchgP9nX1 szbKCXvWYVS5X7Hn8E4dBR7L7zzhGX9TBOXUPOzug59/dyhFrN/5R7oWwPOdI8viJ6jx M5dAwBXvn3MYLb6v9TO2LFyP8wWty1F3uhTzlJ06iWG5r1ox8s0inVIO2iY6qcw0FWWE CsP47Zw0e7N9N9+mr1HAZbiGFPnYlWcUyXgMdW0b2xA7QGZuvaEbwKwDwKzmtEG1LMl2 X2Hyyos+69u/sn07D7tmWvRUJoXOnO7MZtU7UNgKMjPjrKAsroCU8yY/A9KJ7QfuLOEK 59PA== MIME-Version: 1.0 X-Received: by 10.152.7.208 with SMTP id l16mr15286547laa.48.1412472596643; Sat, 04 Oct 2014 18:29:56 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.131.66 with HTTP; Sat, 4 Oct 2014 18:29:56 -0700 (PDT) Date: Sat, 4 Oct 2014 18:29:56 -0700 X-Google-Sender-Auth: 49KLLtVsYqpqC-VnLnEoOVghtnk Message-ID: Subject: Jenkins and LLVM clang analyzer on FreeBSD From: Craig Rodrigues To: freebsd-current Current , freebsd-toolchain@freebsd.org, "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 05 Oct 2014 01:29:59 -0000 Hi, FYI, Li-Wen Hsu has set up this Jenkins job which builds FreeBSD with the clang analyzer ( https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-scan-build/ ): https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-scan-build/ This job runs once a week. Please view the results of this job, and provide feedback to: freebsd-testing@freebsd.org. Also, if you can see any bugs in FreeBSD identified by this tool, please feel free to submit patches to fix them! :) Thank you Li-Wen, for setting this up!! -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 19:26:27 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2452CDB; Tue, 7 Oct 2014 19:26:26 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 1B87E23CEED; Tue, 7 Oct 2014 21:26:25 +0200 (CEST) Message-ID: <54343E60.7050208@FreeBSD.org> Date: Tue, 07 Oct 2014 21:26:24 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-toolchain@freebsd.org, freebsd-current@freebsd.org Subject: 11-CURRENT redports builders miscompiling? (was: svn commit: r370388 - in head: devel/e2fsprogs-libss misc/e2fsprogs-libblkid misc/e2fsprogs-libuuid sysutils/e2fsprogs sysutils/e2fsprogs/files) References: <201410071915.s97JFrQo061043@svn.freebsd.org> In-Reply-To: <201410071915.s97JFrQo061043@svn.freebsd.org> X-Forwarded-Message-Id: <201410071915.s97JFrQo061043@svn.freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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, 07 Oct 2014 19:26:27 -0000 Greetings, I have just updated sysutils/e2fsprogs and its slave ports(*), and test drove them on redports. The self-test suite is failing on 11-CURRENT i386 and amd64, but not on 10 or older releases. 11-amd64: https://redports.org/buildarchive/20141007190638-31576 11-i386: https://redports.org/buildarchive/20141007185700-4151 I am now wondering - if there are issues with the toolchain on 11 that causes miscompilation, or - whether 11 is misbehaving on redports, or - if e2fsprogs has code bugs that don't show on older toolchains. Any insights into the 11-CURRENT tool chain quality? Thanks. (*) as of SVN ports revision 370388. Cheers, Matthias From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 19:32:44 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6ABEA35E; Tue, 7 Oct 2014 19:32:44 +0000 (UTC) Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (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 F4128382; Tue, 7 Oct 2014 19:32:43 +0000 (UTC) Received: by mail-yh0-f47.google.com with SMTP id c41so3280428yho.34 for ; Tue, 07 Oct 2014 12:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=RkRrVxDLe0oXCpIHWGvsxvC2DPJ5Ns5jz9w740hKPm0=; b=l9WeHfO4pB3bnhldBfOPmaFW1WIxUEaXkZpyTbXOS3dsSZNW1Ob19/ChQMfgmGuGmt qeeEz7nf7kPSUrLuqwk/UGGa0to5XwMT5XOg+ApVIsv9qQ2f8ToXzIM7dxMbbjMUr7y8 bWdX2V/VwQdna0ng+ALu6ansWjTajS5zqMu66AITsYgt1zrO3ePHqjrzWSua4Akn58Pd yo6MzXcS8hdjqqg1Sv0iiRoGcsouSwqBHqccUuOKoRbg2bLVJDYd0I+tqILP6sFJoLih oMHWCM2clYyenAq6tEMkxssSfjcGcJR1G2IOfcp1/MdSTKSlo/FWIc6l0LmqCXqdMQva pHuA== MIME-Version: 1.0 X-Received: by 10.236.70.229 with SMTP id p65mr8160136yhd.50.1412710363045; Tue, 07 Oct 2014 12:32:43 -0700 (PDT) Sender: antoine.brodin.freebsd@gmail.com Received: by 10.170.207.73 with HTTP; Tue, 7 Oct 2014 12:32:42 -0700 (PDT) In-Reply-To: <54343E60.7050208@FreeBSD.org> References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> Date: Tue, 7 Oct 2014 21:32:42 +0200 X-Google-Sender-Auth: nJtrR7AZx8wVoKsDfDkD3vFscjY Message-ID: Subject: Re: 11-CURRENT redports builders miscompiling? (was: svn commit: r370388 - in head: devel/e2fsprogs-libss misc/e2fsprogs-libblkid misc/e2fsprogs-libuuid sysutils/e2fsprogs sysutils/e2fsprogs/files) From: Antoine Brodin To: Matthias Andree Content-Type: text/plain; charset=UTF-8 Cc: freebsd-toolchain@freebsd.org, FreeBSD Current 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, 07 Oct 2014 19:32:44 -0000 On Tue, Oct 7, 2014 at 9:26 PM, Matthias Andree wrote: > Greetings, > > I have just updated sysutils/e2fsprogs and its slave ports(*), and test > drove them on redports. The self-test suite is failing on 11-CURRENT > i386 and amd64, but not on 10 or older releases. > > 11-amd64: https://redports.org/buildarchive/20141007190638-31576 > 11-i386: https://redports.org/buildarchive/20141007185700-4151 > > I am now wondering > - if there are issues with the toolchain on 11 that causes > miscompilation, or > - whether 11 is misbehaving on redports, or > - if e2fsprogs has code bugs that don't show on older toolchains. Hi, e2fsprogs version 1.42.10 tests were succeeding in a jail with a world from r272576 (1.5 day old) http://gohan2.ysv.freebsd.org/data/head-amd64-default-baseline/p370135_s272576/logs/e2fsprogs-1.42.10.log (this is poudriere, not tinderbox) Cheers, Antoine > > Any insights into the 11-CURRENT tool chain quality? > > Thanks. > > > (*) as of SVN ports revision 370388. > > Cheers, > Matthias > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 19:49:36 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14517B07; Tue, 7 Oct 2014 19:49:36 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 9F80223CEED; Tue, 7 Oct 2014 21:49:34 +0200 (CEST) Message-ID: <543443CE.6000900@FreeBSD.org> Date: Tue, 07 Oct 2014 21:49:34 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Antoine Brodin Subject: Re: 11-CURRENT redports builders miscompiling? References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@freebsd.org, FreeBSD Current 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, 07 Oct 2014 19:49:36 -0000 Am 07.10.2014 um 21:32 schrieb Antoine Brodin: > On Tue, Oct 7, 2014 at 9:26 PM, Matthias Andree wrote: >> Greetings, >> >> I have just updated sysutils/e2fsprogs and its slave ports(*), and test >> drove them on redports. The self-test suite is failing on 11-CURRENT >> i386 and amd64, but not on 10 or older releases. >> >> 11-amd64: https://redports.org/buildarchive/20141007190638-31576 >> 11-i386: https://redports.org/buildarchive/20141007185700-4151 >> >> I am now wondering >> - if there are issues with the toolchain on 11 that causes >> miscompilation, or >> - whether 11 is misbehaving on redports, or >> - if e2fsprogs has code bugs that don't show on older toolchains. > > Hi, > > e2fsprogs version 1.42.10 tests were succeeding in a jail with a world > from r272576 (1.5 day old) > > http://gohan2.ysv.freebsd.org/data/head-amd64-default-baseline/p370135_s272576/logs/e2fsprogs-1.42.10.log > > (this is poudriere, not tinderbox) Hi Antoine, merci for that. There are probably multiple changes, so if someone else can take the newer 1.42.12 for a test on 11-current, either on a naked system or with poudriere, that will be appreciated. What I find odd is that the redports logs also show output deviations from expected, for instance, here: > ==> /work/a/ports/sysutils/e2fsprogs/work/e2fsprogs-1.42.12/tests/r_resize_inode.failed <== > --- r_resize_inode/expect 2014-08-25 03:08:16.000000000 +0000 > +++ r_resize_inode.log 2014-10-07 19:10:00.000000000 +0000 > @@ -1,7 +1,7 @@ > mke2fs -q -F -O resize_inode -o Linux -b 1024 -g 1024 test.img 16384 > resize2fs test.img 65536 > Resizing the filesystem on test.img to 65536 (1k) blocks. > -The filesystem on test.img is now 65536 (1k) blocks long. > +The filesystem on test.img is now 65536 (1480342k) blocks long. > > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure The block size is bogus, and this happens on i386 and amd64 so is not /obviously/ an issue of sizeof(long) or thereabouts. Cheers, Matthias From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 20:17:05 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2AFB5668; Tue, 7 Oct 2014 20:17:05 +0000 (UTC) Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (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 ABA619F2; Tue, 7 Oct 2014 20:17:04 +0000 (UTC) Received: by mail-yk0-f174.google.com with SMTP id 142so3175200ykq.33 for ; Tue, 07 Oct 2014 13:17:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AsoxhWIvHrQ/FWUF6Nz89chVL1QbrrV4SgM3Hq6q4jg=; b=bFrFbxWyRS0RUYHLUdQvXQIhtcNp9kEVUnBr1dzpWhga9j0FxveWx9T0qG7NvBQ3au MXOQ5A0Hw46ZYvB3nhOAJEVWPGwQT2tEJv5GIGjA3TgmhBdXGt7GiIXD+M3I4RC27kOT EvpV0GiU8/05sJm/wroZMjPP6tPrnk6E+fCAoR3bdlWxP2MAx+CWU2jtYWKE7ey7lQPK z2RpTXGf43L7zvwCsYaQp9/PDSlIugAPBPYARBZWrNpua8FRRdJ6tMSc/+2gl7+XE42Y mVJjXlrhpaKwhep14wHRRe4mm3knWjzurMtE7eL2Vg/+oJTAaAf32hb5UOF3w8Il9FHM cwqg== MIME-Version: 1.0 X-Received: by 10.236.75.99 with SMTP id y63mr8461580yhd.105.1412713023722; Tue, 07 Oct 2014 13:17:03 -0700 (PDT) Sender: antoine.brodin.freebsd@gmail.com Received: by 10.170.207.73 with HTTP; Tue, 7 Oct 2014 13:17:03 -0700 (PDT) In-Reply-To: <543443CE.6000900@FreeBSD.org> References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> <543443CE.6000900@FreeBSD.org> Date: Tue, 7 Oct 2014 22:17:03 +0200 X-Google-Sender-Auth: _aoCqFNbCCoF55mm_TryCMCWMbM Message-ID: Subject: Re: 11-CURRENT redports builders miscompiling? From: Antoine Brodin To: Matthias Andree Content-Type: text/plain; charset=UTF-8 Cc: freebsd-toolchain@freebsd.org, FreeBSD Current 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, 07 Oct 2014 20:17:05 -0000 On Tue, Oct 7, 2014 at 9:49 PM, Matthias Andree wrote: > Am 07.10.2014 um 21:32 schrieb Antoine Brodin: >> On Tue, Oct 7, 2014 at 9:26 PM, Matthias Andree wrote: >>> Greetings, >>> >>> I have just updated sysutils/e2fsprogs and its slave ports(*), and test >>> drove them on redports. The self-test suite is failing on 11-CURRENT >>> i386 and amd64, but not on 10 or older releases. >>> >>> 11-amd64: https://redports.org/buildarchive/20141007190638-31576 >>> 11-i386: https://redports.org/buildarchive/20141007185700-4151 >>> >>> I am now wondering >>> - if there are issues with the toolchain on 11 that causes >>> miscompilation, or >>> - whether 11 is misbehaving on redports, or >>> - if e2fsprogs has code bugs that don't show on older toolchains. >> >> Hi, >> >> e2fsprogs version 1.42.10 tests were succeeding in a jail with a world >> from r272576 (1.5 day old) >> >> http://gohan2.ysv.freebsd.org/data/head-amd64-default-baseline/p370135_s272576/logs/e2fsprogs-1.42.10.log >> >> (this is poudriere, not tinderbox) > > Hi Antoine, > > merci for that. > > There are probably multiple changes, so if someone else can take the > newer 1.42.12 for a test on 11-current, either on a naked system or with > poudriere, that will be appreciated. What I find odd is that the > redports logs also show output deviations from expected, for instance, > here: > >> ==> /work/a/ports/sysutils/e2fsprogs/work/e2fsprogs-1.42.12/tests/r_resize_inode.failed <== >> --- r_resize_inode/expect 2014-08-25 03:08:16.000000000 +0000 >> +++ r_resize_inode.log 2014-10-07 19:10:00.000000000 +0000 >> @@ -1,7 +1,7 @@ >> mke2fs -q -F -O resize_inode -o Linux -b 1024 -g 1024 test.img 16384 >> resize2fs test.img 65536 >> Resizing the filesystem on test.img to 65536 (1k) blocks. >> -The filesystem on test.img is now 65536 (1k) blocks long. >> +The filesystem on test.img is now 65536 (1480342k) blocks long. >> >> Pass 1: Checking inodes, blocks, and sizes >> Pass 2: Checking directory structure > > The block size is bogus, and this happens on i386 and amd64 so is not > /obviously/ an issue of sizeof(long) or thereabouts. So, the test fail on head, but if you look carefully, 1480342*1024 = 0x5a5a... which looks like malloc junk. But when I turn off malloc debugging ( ln -s 'abort:false,junk:false' /etc/malloc.conf ) the tests succeed. So it looks like a bug in e2fsprogs. Cheers, Antoine From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 21:57:37 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31B3C225; Tue, 7 Oct 2014 21:57:37 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 85AB323CEED; Tue, 7 Oct 2014 23:57:35 +0200 (CEST) Message-ID: <543461CF.9040701@FreeBSD.org> Date: Tue, 07 Oct 2014 23:57:35 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Antoine Brodin Subject: Re: 11-CURRENT redports builders miscompiling? References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> <543443CE.6000900@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@freebsd.org, FreeBSD Current 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, 07 Oct 2014 21:57:37 -0000 Am 07.10.2014 um 22:17 schrieb Antoine Brodin: > So, the test fail on head, but if you look carefully, 1480342*1024 > = 0x5a5a... which looks like malloc junk. Bingo, thanks for the pointer. > But when I turn off malloc debugging ( ln -s 'abort:false,junk:false' > /etc/malloc.conf ) the tests succeed. > > So it looks like a bug in e2fsprogs. Yup, reproduced with "make post-build MALLOC_OPTIONS=J", and valgrind also has something to complain about, so I'll forward a report upstream. I haven't seen something in the "maint" branch since the release that looks like an obvious fix. This lets 11-CURRENT and redports off the hook for now. I wasn't aware redports-on-11 set MALLOC_OPTIONS=J or equivalent. Cheers, Matthias From owner-freebsd-toolchain@FreeBSD.ORG Tue Oct 7 23:29:21 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96F26E79; Tue, 7 Oct 2014 23:29:21 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id D6CE023CEED; Wed, 8 Oct 2014 01:29:19 +0200 (CEST) Message-ID: <5434774F.5020708@FreeBSD.org> Date: Wed, 08 Oct 2014 01:29:19 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Matthias Andree , Antoine Brodin Subject: Re: 11-CURRENT redports builders miscompiling? References: <201410071915.s97JFrQo061043@svn.freebsd.org> <54343E60.7050208@FreeBSD.org> <543443CE.6000900@FreeBSD.org> <543461CF.9040701@FreeBSD.org> In-Reply-To: <543461CF.9040701@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@freebsd.org, FreeBSD Current 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, 07 Oct 2014 23:29:21 -0000 Am 07.10.2014 um 23:57 schrieb Matthias Andree: > Am 07.10.2014 um 22:17 schrieb Antoine Brodin: > >> So, the test fail on head, but if you look carefully, 1480342*1024 >> = 0x5a5a... which looks like malloc junk. > > Bingo, thanks for the pointer. > >> But when I turn off malloc debugging ( ln -s 'abort:false,junk:false' >> /etc/malloc.conf ) the tests succeed. >> >> So it looks like a bug in e2fsprogs. > > Yup, reproduced with "make post-build MALLOC_OPTIONS=J", and valgrind > also has something to complain about, so I'll forward a report upstream. > > I haven't seen something in the "maint" branch since the release that > looks like an obvious fix. > > This lets 11-CURRENT and redports off the hook for now. I wasn't aware > redports-on-11 set MALLOC_OPTIONS=J or equivalent. I have bisected this on upstream's Git, and the failure-inducing change is apparently 47fee2ef I reported this in greater detail to the authors/reviewers of the patch. Let's see what we get. For -current/-toolchain and decke@ I consider this closed. Thanks to Antoine for setting me on the right track. Cheers, Matthias From owner-freebsd-toolchain@FreeBSD.ORG Thu Oct 9 02:43:02 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A7B6D42B for ; Thu, 9 Oct 2014 02:43:02 +0000 (UTC) Received: from vfemail.net (nine.vfemail.net [108.76.175.9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C89B24A for ; Thu, 9 Oct 2014 02:43:01 +0000 (UTC) Received: (qmail 82464 invoked by uid 89); 9 Oct 2014 02:36:11 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 9 Oct 2014 02:36:10 -0000 Received: (qmail 82394 invoked by uid 89); 9 Oct 2014 02:35:53 -0000 Received: by simscan 1.3.1 ppid: 82387, pid: 82391, t: 0.0155s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 9 Oct 2014 02:35:53 -0000 Received: (qmail 1948 invoked by uid 89); 9 Oct 2014 02:35:53 -0000 Received: by simscan 1.4.0 ppid: 1931, pid: 1945, t: 0.7153s scanners:none Received: from unknown (HELO nil) (amJlaWNoQHZmZW1haWwubmV0@172.16.100.27) by 172.16.100.62 with ESMTPA; 9 Oct 2014 02:35:52 -0000 From: Jan Beich To: "Jeremy C. Reed" Subject: Re: using code coverage with clang References: Date: Thu, 09 Oct 2014 04:35:49 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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: Thu, 09 Oct 2014 02:43:02 -0000 (redirected from -questions@ to -toolchain@) "Jeremy C. Reed" writes: > When I changed from FreeBSD 9.x to 10.0-RELEASE-p1, I went from gcc to > clang. But this causes > /usr/bin/ld: /usr/bin/../lib/libprofile_rt.a: No such file: No such file > or directory > > I don't have that library. Any suggestions on how to get it so I don't > have to maintain later during upgrades. I don't think the clang ports > have it either. With recent Clang the error may error slightly different: $ clang35 foo.c -fprofile-arcs -ftest-coverage /usr/local/bin/ld: cannot find /usr/local/llvm35/bin/../lib/clang/3.5.0/lib/freebsd/libclang_rt.profile-amd64.a: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) Try installing one of lang/gcc* and adding --rtlib=libgcc to link flags. --rtlib=compiler-rt requires more recent compiler-rt version than the one shipped with FreeBSD base. There's an upstream bug but the patches there have bitrotten to being mostly useless (predate --rtlib support). http://llvm.org/bugs/show_bug.cgi?id=6122 Anyway, freebsd-toolchain@ folk probably know more about the state of Clang coverage/profiling on FreeBSD such as: - devel/compiler-rt being more ancient than version in base on 10.0R - lang/clang* trying to use libgcc_p instead of libs from lang/gcc* - coverage/profiling not agreeing on whether to use libgcc/compiler-rt https://lists.freebsd.org/pipermail/freebsd-toolchain/2013-September/001030.html > > I'd prefer to not maintain all my dependencies (ports) using gcc. > (Currently I cannot use gcc with the clang-built ports as some libraries > appear to be built differently so references aren't seen the same.) > Try either converting USE_GCC=yes ports to USES=compiler:gcc-c++11-lib or adding -nostdinc++ -isystem/usr/include/c++/v1 to CXXFLAGS and creating /usr/lib/libstdc++.so -> libc++.so symlink. > Does anyone have suggestions for doing code coverage with clang? Maybe pmcannotate(8) or dtrace(1) as compiler-agnostic alternatives. > > Or are there binary packages available for 10.0 on amd64 built with gcc? > > (I found a forum discussion about it at > https://forums.freebsd.org/viewtopic.php?f=35&t=47260 and several other > reports about it.) ------------------------------------------------- VFEmail.net - http://www.vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! From owner-freebsd-toolchain@FreeBSD.ORG Fri Oct 10 20:37:00 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D34D3776 for ; Fri, 10 Oct 2014 20:37:00 +0000 (UTC) Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E9E5ED7 for ; Fri, 10 Oct 2014 20:37:00 +0000 (UTC) Received: from resomta-po-11v.sys.comcast.net ([96.114.154.235]) by resqmta-po-06v.sys.comcast.net with comcast id 1Ycl1p00954zqzk01YczWV; Fri, 10 Oct 2014 20:36:59 +0000 Received: from kirby.cyberbotx.com ([107.5.48.95]) by resomta-po-11v.sys.comcast.net with comcast id 1Ycx1p00123DSHF01Ycx8l; Fri, 10 Oct 2014 20:36:58 +0000 Message-ID: <54384368.1000707@cyberbotx.com> Date: Fri, 10 Oct 2014 16:36:56 -0400 From: Naram Qashat User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-toolchain@FreeBSD.org Subject: devel/mingw32-gcc problem Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1412973419; bh=2maG1XvUMGXALFjvXkqBoRrJDkpK3AQAVDi0J5QjOS0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=mxtKwXOJDoZxOvmXOS+6EwD1aN2zSNw3VCKzDGqbvc4xMODXndF+eqwWViJmTEHDF OdU5j1lqcjDo9NFXkGg8yfIKlj3ExjZPuklEGGLSsQBUVEepr4yGEE/3tY9ywiHeek epXbAGx8Hk/6LdIYG/Di3aCmFA4DAWz0J+Jcm3aeWyj2RsP0I5x9leGGq5AlNeG6D7 xU5JOBKD9Xgwm6COo+xz7ewxjaQajYZX8KhRrjnq0aZm6N/C66PRMNdxE1si9CMg6J M8BpBmigPdLYa/kRC+Q2f6TrD5i0E1jhbk+RVgKutEq1Lbl+F2wfP0+y37EF+LaOUy Yhced3hSU21nw== Cc: rene@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, 10 Oct 2014 20:37:00 -0000 Hi everyone, I've been trying to push out an update to devel/mingw32-gcc, but ran into a problem, and Rene suggested asking about it here. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191291 Long story short, some of the .a files installed by devel/mingw32-bin-msvcrt get clobbered (their contents becomes nothing but NUL bytes) during the build of mingw32-gcc. This only happens under 10.x and not under 9.x or earlier. I'm not subscribed to this mailing list, so please CC me on any replies. Thanks, Naram Qashat