Date: Thu, 19 Jul 2018 19:30:06 +0000 From: bugzilla-noreply@freebsd.org To: office@FreeBSD.org Subject: [Bug 229888] devel/boost-libs: Fix undefined behavior in boost::filesystem::copy Message-ID: <bug-229888-25061-VmNhJaKMbe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229888-25061@https.bugs.freebsd.org/bugzilla/> References: <bug-229888-25061@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=3D229888 Jan Beich <jbeich@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback? | --- Comment #1 from Jan Beich <jbeich@FreeBSD.org> --- The provided example doesn't crash. Tested on 11.2 i386/amd64 with boost-libs-1.68.0 (beta1) built by clang 6.0.0 and boost-libs-1.67.0_2 buil= t on package cluster by clang 4.0.0. (In reply to Michael Gmelin from comment #0) > The same code worked on 10.3 with clang 3.9 (at least on an older ports t= ree), FreeBSD 10.* has Clang 3.4.1 in base while USES=3Dcompiler:c++14-lang has n= ever used devel/llvm39 by default. > that's why this is a ticking time bomb for people upgrading to 11.2. Was the issue exposed by -std=3Dgnu++14 being default since Clang 6 or can = you reproduce by building the consumer with -std=3Dgnu++98? Otherwise, I don't understand why the issue would hit 10.3 -> 11.2 users but not 11.1 -> 11.2. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229888-25061-VmNhJaKMbe>