Date: Wed, 13 Feb 2019 20:14:43 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 234671] clang faults while compiling new GlusterFS source code Message-ID: <bug-234671-29464-lMEpwyN5Qa@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234671-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-234671-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=3D234671 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: dim Date: Wed Feb 13 20:13:40 UTC 2019 New revision: 344112 URL: https://svnweb.freebsd.org/changeset/base/344112 Log: Pull in r353907 from upstream llvm trunk (by Reid Kleckner): [MC] Make symbol version errors non-fatal We stil don't have a source location, which is pretty lame, but at least we won't tell the user to file a clang bug report anymore. Fixes PR40712 This will make errors for symbols with @@ versions that are not defined non-fatal. For example: void f(void) { __asm__(".symver foo,bar@@baz"); } will now result in: error: versioned symbol bar@@baz must be defined instead of clang crashing with a diagnostic report. PR: 234671 Upstream PR: https://bugs.llvm.org/show_bug.cgi?id=3D40712 MFC after: 3 days Changes: head/contrib/llvm/lib/MC/ELFObjectWriter.cpp --=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-234671-29464-lMEpwyN5Qa>