Date: Tue, 31 Dec 2019 17:28:10 -0800 From: Mark Millard <marklmi@yahoo.com> To: John Baldwin <jhb@freebsd.org> Cc: Gerald Pfeifer <gerald@pfeifer.com>, freebsd-toolchain@freebsd.org, freebsd-ppc@freebsd.org, freebsd-ports@freebsd.org Subject: Re: devel/freebsd-gcc9@powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang Message-ID: <BC1D871A-B0A2-44CB-AB9C-900ADEDF98FA@yahoo.com> In-Reply-To: <70ace2dc-ab93-3fee-8ecf-019730195d5a@FreeBSD.org> References: <BE95732C-A03D-47D6-969B-78966768AD5E.ref@yahoo.com> <BE95732C-A03D-47D6-969B-78966768AD5E@yahoo.com> <alpine.LSU.2.21.1912271441380.3227@anthias> <D9EFE02F-E9C4-4F78-9FFE-842938C10F13@yahoo.com> <70ace2dc-ab93-3fee-8ecf-019730195d5a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Dec-31, at 16:41, John Baldwin <jhb at freebsd.org> wrote: > On 12/26/19 11:39 PM, Mark Millard wrote: >>>> is missing the patch-clang-vec_step that is in: >>>> >>>> FBSDG5L2# ls -laT /usr/ports/lang/gcc9/files/ >>> >>> That is a hack that can be used to work around the issue; I strongly >>> recommend addressing this in clang properly, though. > > I think using the hack patch in devel/freebsd-gcc* is fine for now, but can > you confirm if both 6 and 9 need it or only 9? > devel/freebsd-gcc6 and devel/freebsd-gcc9 both need it. The vec_step identifier has been in use in gcc's gcc/tree-vect-loop.c for a long time and still is in use. Going the other way, reserving vec_step for opencl/altivec for PowerPc's has been in clang for a long time. I've had to have local patches for lang/gcc6 and later and in devel/powerpc64-gcc historically (2017+) because of my clang-targeting-PowerPc activities and trying to build gcc versions via clang as part of those activities. (Of course, some places have patches of their own now.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BC1D871A-B0A2-44CB-AB9C-900ADEDF98FA>