Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Dec 2019 03:54:35 +0000
From:      Alexey Dokuchaev <danfe@freebsd.org>
To:        Jan Beich <jbeich@freebsd.org>
Cc:        svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Gleb Popov <arrowd@freebsd.org>, ports-committers@freebsd.org
Subject:   Re: svn commit: r520468 - in head/sysutils: . cpuid2cpuflags
Message-ID:  <20191221035434.GA14035@FreeBSD.org>
In-Reply-To: <k16r-dzeq-wny@FreeBSD.org>
References:  <201912200518.xBK5IHPq022253@repo.freebsd.org> <CALH631m10%2B0eDY_8BKQxErA2Bpo2dv6B6h7DRb77yO3cJCboSw@mail.gmail.com> <20191220084532.GA30042@FreeBSD.org> <v9qb-ff6r-wny@FreeBSD.org> <k16r-dzeq-wny@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 20, 2019 at 12:11:57PM +0100, Jan Beich wrote:
> Jan Beich <jbeich@FreeBSD.org> writes:
> > Neither supports non-x86 architectures[1] on FreeBSD. Even on x86 both
> > are incomplete compared to "cc -march=native -v" e.g., cpuid2cpuflags
> > lacks avx512bf16 while hs-cputype doesn't support avx512 at all.

Thanks, I'll see if I can convert some of the suggestions into a patch.

> > powerpc and powerpc64:
> > - sysctlbyname: kern.cpu_features + kern.cpu_features2

I'm actually surprised why we don't have standard `hw.cpu_features'
populated for specific CPU accordingly, in 2019 still.

> There's also hw.altivec as useful as hw.instruction_sse ;)

Both of these should of course be gone (replaced by hw.cpu_features).

./danfe



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191221035434.GA14035>