Re: devel/freebsd-gcc9@powerpc (for example) : it has the clang vs. gcc vec_step name conflict (for powerpc families): build fails under clang

[Mark Millard via freebsd-ports]

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)

_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"