On 14/04/18 06:00, R0b0t1 wrote: > On Fri, Apr 13, 2018 at 10:51 PM, Brian Inglis > wrote: >> On 2018-04-13 21:10, Jeffrey Walton wrote: >>>> On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton wrote: >>>>> On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen >>>>> wrote: >>>>>> On Apr 12 23:01, Jeffrey Walton wrote: >>>>>>> Hi Everyone, >>>>>>> >>>>>>> I'm working on an AMD A6-9220 and seeing unusual results from >>>>>>> /proc/cpuinfo. I think this may be an issue with the latest Cygwin. It >>>>>>> may be present in earlier versions, too. >>>>>>> >>>>>>> Russinovich's coreinfo is shown below >>>>>>> (https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo). >>>>>>> Notice /proc/cpuinfo is missing aesni, pclmul, rdrand, SSE4.1, SSE4.2, >>>>>>> AVX, etc. >>>>>> Note that, in theory, cpuinfo has to be extended for each new CPU >>>>>> generation. That's a lot of work for marginal gain (Cygwin's not a real >>>>>> kernel) so I'm doing this only very seldomly. >>>>>> >>>>>> Patches welcome, of course! >>>>> Thanks Corinna. I think I found the file of interest at fhandler_proc.cc. >>>>> >>>>> Whitespace is a bit off. It is a mix of tabs and space: >>>>> >>>>> if (features1 & (1 << 0)) >>>>> print (" fpu"); >>>>> if (features1 & (1 << 1)) >>>>> print (" vme"); >>>>> >>>>> Should I perform a whitespace check-in before things begin? Or can you >>>>> knock it out? >>>> The attachment is pp 572-74 from AMD's Programmer's Guide, Volume 3, >>>> General-Purpose and System Instructions (December 2017) >>>> (https://support.amd.com/TechDocs/24594.pdf). I believe it has the all >>>> the necessary information. >>>> >>>> Are there any objections to using it? >>> Any ideas how to get this through? It is a three page PDF extracted from the >>> AMD manual. It has the necessary information for the CPUID updates. >> Just include the link to Appendix D section 2 from the ToC: >> https://support.amd.com/TechDocs/24594.pdf#G14.931059 >> > He may be concerned about the longterm availability of the referenced passages. > By forwarding your failure notice, you've already sent it to the list in base64 text format, which is enough for anyone to recover the document :-) This list accepts bz2 attachments, so if you want to do this in the future then just compress it. For the archives, the attached *should* be your PDF recovered from base64 and then compressed. Dave.