[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Gnubg on MacOS High Sierra

From: Marcell Fulop
Subject: Re: [Bug-gnubg] Gnubg on MacOS High Sierra
Date: Mon, 11 Dec 2017 09:59:53 +1100

Hi Philippe,

To clarify, I have no background in C and Make and the likes other
than being a software engineer and advanced Linux user I built several
C programs and resolved many conflicts but these are mostly trial and
error based experiments.

> You wrote earlier that you built it with gcc 7. A few months ago, I
> tried to build gnubg on FreeBSD with its gcc 7 port (that was tagged as
> a development version at the time) and the evaluations were broken when
> using SIMD instructions (SSE or AVX).

That's right, I did use gcc-7 but I tried different compilers during a
number of attempts. (System compiler and gcc, g++ from the homebrew
gcc7 package.) I didn't make it quite clear which compiler was used
for the build I was referring to so I will clarify that.

> Other cases (gcc 7 when not using SIMD instructions, clang or earlier
> gcc versions, gcc 7 with SIMD instructions on Linux) worked fine. I
> didn't pursue the matter (the compiler was a development version...) and
> gave up on gcc 7 on FreeBSD.
> I think gcc creates the include files it uses from the system files.
> Since MacOS and FreeBSD both use clang as system compiler, could it be
> possible that its SIMD intrinsics include files are somehow broken when
> generated from clang's ones ? Or that we use them in a subtly wrong way
> and don't get away with it any more in this configuration ?
> You could try to build gnubg configured with --enable-simd=no with gcc 7
> (it will be 2-3 times slower), or in the default configuration with
> another compiler and see if it makes a difference.

Definitely will give a try building it w/o SIMD and also different
compilers and compare any successful builds.

As a note, I built 1.04.000 with board3d, OpenGL and GLU successfully
for the first time yesterday. I'll start another thread about that.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]