X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=ERlkiHl
	0ZfDYetBuSXiuo/66WixEBmZflqd2efJ+LLOjKDG9DR+j8XNwXIA9fcx2Q7EX3U3
	w7QDfJn49+OW3P0/1PdjQiNk69+E0dNx7zYtKjvIwbHxXf/H1x+uxaOnwN+9Y0Jd
	EgLKswFH/PBBaL8S2uo6UqE8O7c0yaY2tFZE=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=rDBvmG5BjguoV
	JnmoiOhOGKje9s=; b=rOpgOm9uXLQOsJucCfPxfbLKFCJ/KJx1V2zckPHl3g27e
	NTT3t+ZiUmAUXYZGNNl6ihAYA+6aTvkBrAbd4SVQrV4wH50IdCr3C3inCaum9Rom
	82GRhtkkBA6XmhQzNhf4D+j6AXxSjHjcC9VznivbLpfIIaiWNb+JeFGZVNd4xY=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=H*Ad:D*ca
X-HELO:	mail-lf0-f41.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=av3u5c1xKwK8lrtYcQ91mxMwvrPfPhT2dCHi4PARlW4=; b=ovjpJ7tcTq1SMbLJccF960LAFLmxdj98lxQnlUbFlAEH5d4MGozIQb1WxtWXzHwkX8 id+DrD8IegQ0yg4CPtTdvaH5VqqcwwFF6nQtxyLV/Ui6YET64YBtdRh//6Q3ZRdy6SWn oEOiNJkXdiu+UA3I31VmcVOiEkMobk75ev9Ers4Kpkj8wpC2+3HQA5dU7PnBzGwwyzDW +ue2M7CMcLdrfcO3Dd0CL1L68x4gmFk/1ie6pvTCmzBRCsnHozdfm6V+vk3l2Av1VBL/ ssVXyzY8CL5NtMxIiPKrt4wZKkqPa31XC0NcpIEpNa0QAQF2BsadBZsWdzZGLZ6gPeM6 flTw==
X-Gm-Message-State:	ALQs6tC78TGVQaoJzeRllPl0ojddnEF9M7y0DEoGVzspnJ0htve0Thqg k5sdTvu2KZeFKZ1HkDlmuIeov5/DtLeHAuJ9SwU=
X-Google-Smtp-Source:	AIpwx48IowFTXzRle1/ycOYVCZ2GhA8GNIFO3cOV6R65S7DJhVXBIo6LDNSD1DFoCmcUktMK8723cnPjfZEq+lYiOtE=
X-Received:	by 2002:a19:5211:: with SMTP id m17-v6mr1549936lfb.72.1523682002029; Fri, 13 Apr 2018 22:00:02 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<a37c0e51-d617-51a1-ffa0-4fa650268082@SystematicSw.ab.ca>
References:	<CAH8yC8nrV4i1wOzeBbXDKMJpdfsN-8ZubiN=R7Yow4cBDmG5wQ AT mail DOT gmail DOT com> <5ad17051 DOT cf55650a DOT 73c5d DOT c3e7SMTPIN_ADDED_MISSING AT mx DOT google DOT com> <CAH8yC8=H9ZcZtJFSOmNFq4WXQN5S6FG_gNwurr7fJ=5-GwYCMg AT mail DOT gmail DOT com> <a37c0e51-d617-51a1-ffa0-4fa650268082 AT SystematicSw DOT ab DOT ca>
From:	R0b0t1 <r030t1 AT gmail DOT com>
Date:	Sat, 14 Apr 2018 00:00:01 -0500
Message-ID:	<CAAD4mYh+Yy0K1WMdsbGk-LwBUdFB5q9_05J4TzGv0xxyGD28ug@mail.gmail.com>
Subject:	Re: failure notice
To:	Brian DOT Inglis AT systematicsw DOT ab DOT ca, cygwin AT cygwin DOT com
X-IsSubscribed:	yes

On Fri, Apr 13, 2018 at 10:51 PM, Brian Inglis
<Brian DOT Inglis AT systematicsw DOT ab DOT ca> wrote:
> On 2018-04-13 21:10, Jeffrey Walton wrote:
>>> On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton <noloader AT gmail DOT com> wrote:
>>>> On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen
>>>> <corinna-cygwin AT cygwin DOT com> 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.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -