Date: Thu, 22 Jun 2017 00:04:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220184] clang 4.0.0 segfaults on buildworld Message-ID: <bug-220184-8-0y4Q32FEYa@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220184-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220184-8@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=3D220184 --- Comment #4 from Chris Collins <chrysalis@chrysalisnet.org> --- I have considered it could be memory or other i/o issues. The fail point is not always the same spot. I did read elsewhere tho that clang 4.0 has a bug which when it uses too mu= ch memory it will segfault. I plan to test all this again on another machine, probably a VM I have runn= ing on a XEON which has ECC ram and nothing overclocked. I will try to do this before the end of this upcoming weekend. Interestingly the last 2 compile runs have succeeded. But they are mostly f= rom cached ccache. So not really much if any actual compiling was done. This system is overclocked on the cpu. All the ports have been recompiled without segfaults using clang39 from por= ts, and no previous segfaults when base was 3.8. However if I understand correctly when I first built 11-STABLE, it would ha= ve used clang40 compiled at the bootstrap stage to compile the rest of the wor= ld? --=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-220184-8-0y4Q32FEYa>