From owner-freebsd-toolchain@freebsd.org  Tue Nov 29 00:28:02 2016
Return-Path: <owner-freebsd-toolchain@freebsd.org>
Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DB42C587BF
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Tue, 29 Nov 2016 00:28:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3F40C130B
 for <freebsd-toolchain@FreeBSD.org>; Tue, 29 Nov 2016 00:28:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAT0S1ug079776
 for <freebsd-toolchain@FreeBSD.org>; Tue, 29 Nov 2016 00:28:02 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 214863] lang/gcc + libc++ may fail due to spurious
 __cxa_throw_bad_array_new_length reference
Date: Tue, 29 Nov 2016 00:28:02 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: gerald@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-214863-29464-B0xVzbi3L4@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214863-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-214863-29464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2016 00:28:02 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214863

Ed Maste <emaste@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emaste@freebsd.org

--- Comment #5 from Ed Maste <emaste@freebsd.org> ---
> 10.1 and 10.2 have one month of life left... Do you really think this is =
worth
> the trouble?

Regardless of the branches still being supported today, some of our downstr=
eam
consumers continue to use FreeBSD releases long after they're no longer
supported. I think there is value in an EN even if the branch is EOL at the=
 end
of the year. I can't really say for sure that this is enough value to justi=
fy
the effort: I suspect those downstream users don't follow -pN releases dire=
ctly
anyhow and it's easy enough for them to incorporate the patch into their lo=
cal
tree.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=