From owner-freebsd-toolchain@FreeBSD.ORG Tue Nov 18 20:05: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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E82F621; Tue, 18 Nov 2014 20:05:36 +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 0EB13C1D; Tue, 18 Nov 2014 20:05:35 +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=4oODG3rHltTqBvNcPsaxx94zQ25RIHBgFFKsLIRWeJU=; b=hH8FAEdNPflrUHUPMGeD8fiJZpTsx948zYVdU6PuBNKlFC0NA277k+El1E8f3mAZ5KQ5W6jKBTXC0Hzhph+26x6N72ipWgTScfcLqWQ7lrKC8AXv004g2ESXhcKkCcNMKR7QVndOhpR/iZMEVxpiSVfGnLyDyTisA9s6q+9Pcu0=; 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 1Xqp1l-000BrU-Sy; Tue, 18 Nov 2014 23:05:29 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 6A651779; Wed, 19 Nov 2014 00:05:29 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 608588E04; Tue, 18 Nov 2014 23:05:29 +0300 (MSK) Date: Tue, 18 Nov 2014 23:05:29 +0300 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20141118200529.GC62527@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, 18 Nov 2014 20:05:36 -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. > > 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? The bug seem to have been fixed: http://llvm.org/bugs/show_bug.cgi?id=20893 http://llvm.org/bugs/show_bug.cgi?id=19031 This is unfortunately too late for 10.1, but can we possibly have the fix backported into HEAD and 10-STABLE? -- 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 Nov 18 23:23:13 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 1B9A02D5; Tue, 18 Nov 2014 23:23:13 +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 "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C81702D3; Tue, 18 Nov 2014 23:23:12 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::609f:bb8:1285:c55d] (unknown [IPv6:2001:7b8:3a7:0:609f:bb8:1285:c55d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 4C0B2B80A; Wed, 19 Nov 2014 00:23:08 +0100 (CET) Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b1 From: Dimitry Andric In-Reply-To: <20141118200529.GC62527@hades.panopticon> Date: Wed, 19 Nov 2014 00:23:02 +0100 Message-Id: <80988786-733F-4633-ADFB-844FD0DF78EE@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> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> <20141118200529.GC62527@hades.panopticon> To: Dmitry Marakasov X-Mailer: Apple Mail (2.1993) 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, 18 Nov 2014 23:23:13 -0000 --Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Nov 2014, at 21:05, Dmitry Marakasov wrote: >=20 > * 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? >>=20 >> 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. >>=20 >> 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? >=20 > The bug seem to have been fixed: >=20 > http://llvm.org/bugs/show_bug.cgi?id=3D20893 > http://llvm.org/bugs/show_bug.cgi?id=3D19031 >=20 > This is unfortunately too late for 10.1, but can we possibly have the > fix backported into HEAD and 10-STABLE? Yes, I have already imported the fix in r274442; I will probably get the MFC reminder tomorrow. I'm sorry the fix could not make it into 10.1, but apparently the first version of it was not the proper way of solving the problem. The final version took quite a while, unfortunately. -Dimitry --Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A 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.26 iEYEARECAAYFAlRr1NoACgkQsF6jCi4glqPg+gCfYfnA2wiRUyiYpXB6R2adQxwR /7AAoMDJVUPsIjtPz9On+Y2RZLXUbYyl =LKwm -----END PGP SIGNATURE----- --Apple-Mail=_358C5AE6-0D02-41D0-AD0A-4AC148AB351A-- From owner-freebsd-toolchain@FreeBSD.ORG Wed Nov 19 00:54:50 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 099EDE06; Wed, 19 Nov 2014 00:54:50 +0000 (UTC) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (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 BD4C9DB6; Wed, 19 Nov 2014 00:54:49 +0000 (UTC) Received: by mail-ig0-f179.google.com with SMTP id r2so109923igi.12 for ; Tue, 18 Nov 2014 16:54:49 -0800 (PST) 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=/bjgFbIJ62oloQS9nRXmIqKBpfle9/1oQ5jL8+sOc34=; b=sJ/6LjM36c2k9eybmHt00GCD3Lk6YpEg8na4ZEubIk1x5JYQyJP1+aKz07p6cPNpqZ iTShI0wnsIabCzZIX7t9gAriIef4sD+BgsJqoxVXOrVdYLqXAb9iHhiphgdne8Wm6dkl XyEpINnNR3Qc9RbE07pdoq9C8GSldelBWruUvGutsMWoxfbwsDLbZ+amKMYtNf2OzQf3 ks5FUb62z9G7oVA58k/AEqyEkRgnfvPwsnlgBg8Lf1RMpuXL08Ql568B0FnQn8eOiRlW cRQXNIvvFzd35un+bETvw4E4b7z45IZfX7M6qRenfv4TLHKKTWUXgEnhYzDp3hDcJZxW aIDA== MIME-Version: 1.0 X-Received: by 10.43.172.6 with SMTP id nw6mr156850icc.89.1416358489153; Tue, 18 Nov 2014 16:54:49 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.7.169 with HTTP; Tue, 18 Nov 2014 16:54:49 -0800 (PST) In-Reply-To: <80988786-733F-4633-ADFB-844FD0DF78EE@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> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> <20141118200529.GC62527@hades.panopticon> <80988786-733F-4633-ADFB-844FD0DF78EE@FreeBSD.org> Date: Tue, 18 Nov 2014 16:54:49 -0800 X-Google-Sender-Auth: zYI_ryhhljpk4UBTMw63BXhDPIU Message-ID: Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD From: Kevin Oberman To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List , 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: Wed, 19 Nov 2014 00:54:50 -0000 On Tue, Nov 18, 2014 at 3:23 PM, Dimitry Andric wrote: > On 18 Nov 2014, at 21:05, Dmitry Marakasov wrote: > > > > * 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. > >> > >> 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? > > > > The bug seem to have been fixed: > > > > http://llvm.org/bugs/show_bug.cgi?id=20893 > > http://llvm.org/bugs/show_bug.cgi?id=19031 > > > > This is unfortunately too late for 10.1, but can we possibly have the > > fix backported into HEAD and 10-STABLE? > > Yes, I have already imported the fix in r274442; I will probably get > the MFC reminder tomorrow. > > I'm sorry the fix could not make it into 10.1, but apparently the first > version of it was not the proper way of solving the problem. The final > version took quite a while, unfortunately. > > -Dimitry > > This seems to me like something that deserves an errata note. At the least, it will greatly deduce the number error reports to this list and the bug reports to bugzilla. (Well, maybe not, but I can hope.) -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-toolchain@FreeBSD.ORG Wed Nov 19 08:04:40 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 8A8CE622; Wed, 19 Nov 2014 08:04:40 +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 "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FC18EB5; Wed, 19 Nov 2014 08:04:40 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::609f:bb8:1285:c55d] (unknown [IPv6:2001:7b8:3a7:0:609f:bb8:1285:c55d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 90680B80A; Wed, 19 Nov 2014 09:04:29 +0100 (CET) Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_6F32AAE7-F738-4773-9FBF-D9457B2250B0"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b1 From: Dimitry Andric In-Reply-To: Date: Wed, 19 Nov 2014 09:04:20 +0100 Message-Id: <66FD0611-16EE-4AA8-AD7D-479E63A1DCC3@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> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> <20141118200529.GC62527@hades.panopticon> <80988786-733F-4633-ADFB-844FD0DF78EE@FreeBSD.org> To: Kevin Oberman X-Mailer: Apple Mail (2.1993) Cc: freebsd-toolchain@freebsd.org, FreeBSD-STABLE Mailing List 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: Wed, 19 Nov 2014 08:04:40 -0000 --Apple-Mail=_6F32AAE7-F738-4773-9FBF-D9457B2250B0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 19 Nov 2014, at 01:54, Kevin Oberman wrote: > > On Tue, Nov 18, 2014 at 3:23 PM, Dimitry Andric wrote: ... >> Yes, I have already imported the fix in r274442; I will probably get >> the MFC reminder tomorrow. >> >> I'm sorry the fix could not make it into 10.1, but apparently the first >> version of it was not the proper way of solving the problem. The final >> version took quite a while, unfortunately. .. > This seems to me like something that deserves an errata note. At the > least, it will greatly deduce the number error reports to this list and the > bug reports to bugzilla. (Well, maybe not, but I can hope.) As far as I know, Errata Notes are only issued for security issues (and probably only severe ones, without a workaround). -Dimitry --Apple-Mail=_6F32AAE7-F738-4773-9FBF-D9457B2250B0 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.26 iEYEARECAAYFAlRsTwwACgkQsF6jCi4glqPVHwCdHmSrgb0q+3SlMRey0upLfYb/ 5SgAn06sCdg4SNLU8xGi7fipWY1bojzX =nYat -----END PGP SIGNATURE----- --Apple-Mail=_6F32AAE7-F738-4773-9FBF-D9457B2250B0-- From owner-freebsd-toolchain@FreeBSD.ORG Wed Nov 19 08:31:54 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 327F992A; Wed, 19 Nov 2014 08:31:54 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F10A11AC; Wed, 19 Nov 2014 08:31:53 +0000 (UTC) Received: from [192.168.0.106] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.9/8.14.9) with ESMTP id sAJ8VmPA026677 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Nov 2014 08:31:50 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52] claimed to be [192.168.0.106] Content-Type: text/plain; charset=us-ascii 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: David Chisnall In-Reply-To: <66FD0611-16EE-4AA8-AD7D-479E63A1DCC3@FreeBSD.org> Date: Wed, 19 Nov 2014 08:31:43 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <6C4E3AA9-5092-42DA-8BE7-4F303F0CA8ED@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> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> <20141118200529.GC62527@hades.panopticon> <80988786-733F-4633-ADFB-844FD0DF78EE@FreeBSD.org> <66FD0611-16EE-4AA8-AD7D-479E63A1DCC3@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1878.6) Cc: Kevin Oberman , freebsd-toolchain@freebsd.org, FreeBSD-STABLE Mailing List 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: Wed, 19 Nov 2014 08:31:54 -0000 On 19 Nov 2014, at 08:04, Dimitry Andric wrote: > As far as I know, Errata Notes are only issued for security issues = (and > probably only severe ones, without a workaround). Security Advisories are for security issues. Errata Notes are for... = errata. The confusion comes from the fact that ENs go via freebsd-update, which = is managed by secteam, so using them for anything is a bit harder than = it should be (should be fixed in 11). This seems like a fairly good = candidate though. David