Date: Tue, 22 Jul 2014 20:55:27 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: current@freebsd.org Subject: Re: clang assertion failure+coredump in clang 3.4.1 Message-ID: <8B11DC31-9BAC-4C46-89C7-8F13ABCCD07D@FreeBSD.org> In-Reply-To: <alpine.GSO.1.10.1407211828030.21571@multics.mit.edu>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 22 Jul 2014, at 00:34, Benjamin Kaduk <kaduk@MIT.EDU> wrote: > Building some out-of-tree software with a rather long set of compiler flags, I can reliably get our clang to crash. > The system is current as of r267362 (June 11), with clang reporting itself as FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > Target: x86_64-unknown-freebsd11.0 > (freefall's clang crashes as well.) > > Unfortunately, I don't have debug symbols around for that clang binary. > If someone does have a clang with debug symbols handy, I'd be interested in seeing the backtrace. > > The processed source file and invocation shell script may be found at: > http://web.mit.edu/kaduk/Public/clang/dumptool-09e584.c (1.1M) > http://web.mit.edu/kaduk/Public/clang/dumptool-09e584.sh Hi Ben, I was able to reproduce the assertion, even with clang trunk. It is apparently caused by the implementation of the -Wconsumed warning, which is enabled in your case because you had used -Weverything. I have reported an upstream bug with a reduced test case here: http://llvm.org/PR20402 Meanwhile, you can work around the assertion by adding -Wno-consumed to your compilation flags. -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlPOs6oACgkQsF6jCi4glqN+uwCg9X2ufyvW0ECzd9iaAYVQVsKQ h+UAoM5WYdLcw6sY5pXiey7CSbnc6giy =T0aB -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8B11DC31-9BAC-4C46-89C7-8F13ABCCD07D>