This is the mail archive of the
mailing list for the Cygwin project.
Re: failure notice
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Fri, 13 Apr 2018 21:51:43 -0600
- Subject: Re: failure notice
- References: <CAH8yC8nrV4i1wOzeBbXDKMJpdfsN-8ZubiN=R7Yow4cBDmG5wQ@mail.gmail.com> <5ad17051.cf55650a.73c5d.c3e7SMTPIN_ADDED_MISSING@mx.google.com> <CAH8yC8=H9ZcZtJFSOmNFq4WXQN5S6FG_gNwurr7fJ=5-GwYCMg@mail.gmail.com>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
On 2018-04-13 21:10, Jeffrey Walton wrote:
>> On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton <email@example.com> wrote:
>>> On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen
>>> <firstname.lastname@example.org> 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
>>>>> 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:
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple