Date: Sun, 6 Oct 2019 11:55:34 +0400 From: Gleb Popov <arrowd@freebsd.org> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: CPUTYPE?= in make.conf Message-ID: <CALH631kYhiWGQ0d=fvd8oNqnuc7Ueov%2B9-kxUAThyQDz-XBGAw@mail.gmail.com> In-Reply-To: <20191006001031.GB24947@bastion.zyxst.net> References: <20191004141338.GA72749@bastion.zyxst.net> <CAD2Ti2-unfNJJViMJ5fuU-BD=jA_HPM_gXvmVZm0F4a-yF9eQA@mail.gmail.com> <20191006001031.GB24947@bastion.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 6, 2019 at 4:11 AM tech-lists <tech-lists@zyxst.net> wrote: > Hi, > > On Fri, Oct 04, 2019 at 11:14:28AM -0400, grarpamp wrote: > > >Intel.com says AVX extensions should be present in both. > > > >Does intel.com even publish per cpu or per family > >exhaustive lists of all the instructions present? > >ie: So users don't have to collate all the base instruction > >plus extension set terminology docs separately. > > I don't know about exhaustive. I was using this: > http://cpuboss.com/cpus/Intel-Xeon-E5-2690-vs-Intel-Core-i7-4770K > > The other way of getting them is installing sysutils/cpuid and running > that. > > You're right about AVX, that's my error. > Some time ago I wrote sysutils/hs-cputype utility, which infers you CPU type from clang's output, coerce it to CPUTYPE possible values and prints that to you. It also allows you to compare two CPUTYPEs in terms of features. > thanks, > -- > J. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631kYhiWGQ0d=fvd8oNqnuc7Ueov%2B9-kxUAThyQDz-XBGAw>