Date: Tue, 29 Nov 2016 00:28:02 +0000 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 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214863-29464-B0xVzbi3L4>