Date: Sun, 04 Dec 2016 05:14:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 214904] head -r309179 clang 3.9.0 TARGET_ARCH=powerpc64 cross-built buildkernel stops for: rejected assembler notation Message-ID: <bug-214904-29464-VV89y04mxW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214904-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-214904-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=3D214904 --- Comment #1 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mark Millard from comment #0) I've now also tried this on a powerpc64 running a minor variant of head -r309179 and it gets the same result that the amd64 cross build for TARGET_ARCH=3Dpowerpc64 does --unlike the buildworld WITH_LIB32=3D issue now listed in bugzilla 215037. Here it seems that the "BOOK E" specific instructions are missing from the assembler notation that clang 3.9.0 supports for TARGET_ARCH=3Dpowerpc64. There might be other non-classic PowerPc instructions also missing for all I know. I've sent a note asking Justin Hibbits what he thinks the proper classification of this is. Does llvm need to support the BOOK E specific instructions on the assembler notation in order for FreeBSD to use clang as the system compiler? Even if GENERIC64 could avoid including such things there would still be the issue of how to allow more specialized builds to target BOOK E (or other variants with special instructions for the variant). This may need a related llvm bugzilla submittal to be listed in the: [META] Using Clang as the FreeBSD/ppc system compiler (25780 for llvm). --=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-214904-29464-VV89y04mxW>