Re: SIGILL when CPUTYPE set to anyting witjh avx and CFLAGS -O2

2023-12-29 Thread Harry Schmalzbauer
On 12/29/23 21:20, Konstantin Belousov wrote: On Fri, Dec 29, 2023 at 09:12:35PM +0100, Harry Schmalzbauer wrote: On 12/29/23 18:00, Dimitry Andric wrote: On 29 Dec 2023, at 11:14, Harry Schmalzbauer wrote: at least since 14-release, I can't compile base/ports with CPUTYPE post nehalem. An

Re: SIGILL when CPUTYPE set to anyting witjh avx and CFLAGS -O2

2023-12-29 Thread Konstantin Belousov
On Fri, Dec 29, 2023 at 09:12:35PM +0100, Harry Schmalzbauer wrote: > On 12/29/23 18:00, Dimitry Andric wrote: > > On 29 Dec 2023, at 11:14, Harry Schmalzbauer wrote: > > > > > > at least since 14-release, I can't compile base/ports with CPUTYPE post > > > nehalem. Any '-march' declaring AVX(*)

Re: SIGILL when CPUTYPE set to anyting witjh avx and CFLAGS -O2

2023-12-29 Thread Harry Schmalzbauer
On 12/29/23 18:00, Dimitry Andric wrote: On 29 Dec 2023, at 11:14, Harry Schmalzbauer wrote: at least since 14-release, I can't compile base/ports with CPUTYPE post nehalem. Any '-march' declaring AVX(*) capability leads to SIGILLing binaries with default -O2 CFLAGS. .. If I compile with

Re: SIGILL when CPUTYPE set to anyting witjh avx and CFLAGS -O2

2023-12-29 Thread Dimitry Andric
On 29 Dec 2023, at 11:14, Harry Schmalzbauer wrote: > > at least since 14-release, I can't compile base/ports with CPUTYPE post > nehalem. Any '-march' declaring AVX(*) capability leads to SIGILLing > binaries with default -O2 CFLAGS. > Not much of a help, but here's a ports example, but same

SIGILL when CPUTYPE set to anyting witjh avx and CFLAGS -O2

2023-12-29 Thread Harry Schmalzbauer
Hello, at least since 14-release, I can't compile base/ports with CPUTYPE post nehalem.  Any '-march' declaring AVX(*) capability leads to SIGILLing binaries with default -O2 CFLAGS. Not much of a help, but here's a ports example, but same result with base outcome too: zsh: illegal hardware