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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=rCCFclPIL9+OO708 ZP0vCq8JyCj4SZ6yo1AXnpjX6MTTgpyUNZGVpyFxdvaxdbaXYwtphKwA0q0CTkxC KDh/q2jLNdl+/Y0qK2omnggUD7nXtle+Pcmku2g/I4HcPf7Gl6WVQgNajqzddtIU XZaXklGIGCEQChU+FokMTY4m6pM= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=LsgtWhn5XfXZqcqryKROeS pVVc0=; b=wIAovnBh9yxN/wIzOLDH8u/UhyHQKwYj8s9Hw0SDHdJurq1OgU1ExC AkS8gFHTomFZZetwmcmSaBXijR0ibgdwKRsN0D2ZSXDmDEvEyV6v1giTG23wk/UE uijElaSPoNKqT+/dq7BVcMv2G+AgtVCybexfQUuD6VSKIzuJhKX10= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Volume, H*Ad:D*ca, H*RU:!192.168.1.100!, Hx-languages-length:1909 X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.3 cv=cav8UELM c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=pGLkceISAAAA:8 a=w_pzkKWiAAAA:8 a=yMhMjlubAAAA:8 a=zd2uoN0lAAAA:8 a=-V-7nbmWxGdqE2QmC2wA:9 a=QEXdDO2ut3YA:10 a=sRI3_1zDfAgwuvI8zelB:22 Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: failure notice To: cygwin AT cygwin DOT com References: <5ad17051 DOT cf55650a DOT 73c5d DOT c3e7SMTPIN_ADDED_MISSING AT mx DOT google DOT com> From: Brian Inglis Message-ID: Date: Fri, 13 Apr 2018 21:51:43 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfGwKN3b1PKaZ1wj5e3J45eI8zxDHufYGdL/kC28reJe2WFNV/9Gu/UCAF9Itt+MU/vh/JfpHDmlaedAjG0RyahB6fl9BsBFvQ6v/IDFGdImO0HDqkaKv LcJxoK2IaqXflGTn9+eRNKGJFSpx16x2AKq8+DmtP3I2iVFNf9GIiC2MQlnKWoVTyw4flvyYHr1H2Q== X-IsSubscribed: yes 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 -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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