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:reply-to:in-reply-to:references
	:from:date:message-id:subject:to:content-type; q=dns; s=default; b=
	sGTNbNXK8kenX0t9PSVXD6n9jTxw3T8UOcwukkUkkYv2iBL2thWj/0Smr/sgPccr
	7FXtB4UQ2g5N/uJWlGuWvcxK3pr5hpcCHC2ziZjikDMQepg7XFOngZs+taFLMtSu
	XtUWpGI7uNOVIHSmZmJqou5EWvPmB3hriofq75ITTNQ=
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:reply-to:in-reply-to:references
	:from:date:message-id:subject:to:content-type; s=default; bh=278
	Y9P1pLWbljxh3qtgCaLJa7PY=; b=kYFjxPRdA1Xo7VY7Qsu8PZdqyJC9bJsMeaB
	ql9y7MCfFG3tqSWwYbAWAGEMJMwgS5uQXJgSl6TGWrAVqRP+r7xMKHtVjftHEjro
	rbt6U4Kg2Xkyxwvp0nSkfu1r+EyKhe5ueY6EigyiHBRi5pm5jW8TydUDY//Q8sD3
	Nhkjv7tc=
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.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=knock, sk:corinna, corinna-cygwin AT cygwin DOT com, U*corinna-cygwin
X-HELO: mail-oi0-f52.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:reply-to:in-reply-to:references         :from:date:message-id:subject:to;        bh=SEavHJzR9f/wWbxeLEy8sMcOvbqn/9A9XY6qvVD/2Yo=;        b=IVK2jBEelJVHPqzqCaJkxg5ByLxm6sQXdEvFy0KsXeUM0xU7YodwIXJ672wCl70YaG         ksewyhoancPai7Do91k88rMQQeL+A3weIwwsV6QWnCHF8haZbM353Q8Uoi0Sw75ZOcA/         vek6WJgyjOV1TyjjDyK0jFwcZFZG/MuPjExhzxpQvTZtV8CfU5zQaXY8GCp/tkqnXwX8         0EbBdlHoqUtAY2KZ3yTF3ihnsJ2kKD0DtxXiIHelkNKR8Fis99+iZWhboQNdQsr60fjJ         m5SSBNdXV7SutiBQW+gf9GxJR9z2L5wOFDZLT5mr5dVVNw/CHew3iotEhTtllPwtLTiT         VaqQ==
X-Gm-Message-State: ALQs6tC0Syrz8S+9amEzGTXImtl5GTLscrKPYUIpgTGRj0XyJqGYN9xX	BbV4bJsrnkm/PT6H55CmlEovGI1H4hbxQc7RLTg/rbFZ
X-Google-Smtp-Source: AIpwx4/NGZ3H03i0ebybgC6mspkpUZRuKKz6UMEaLvEwoi3ZfyyUrc4Vd+Xzv3voAS1bX142XTU1M0BrTpZLYH16vWk=
X-Received: by 2002:aca:5cd7:: with SMTP id q206-v6mr9124116oib.154.1523666217279; Fri, 13 Apr 2018 17:36:57 -0700 (PDT)
MIME-Version: 1.0
Reply-To: noloader AT gmail DOT com
In-Reply-To: <20180413115120.GA27440@calimero.vinschen.de>
References: <CAH8yC8k4U-DO0n8r_K=93jPkXCQ=qH8ZMv8CasmkN5=K3UOMLA AT mail DOT gmail DOT com> <20180413115120 DOT GA27440 AT calimero DOT vinschen DOT de>
From: Jeffrey Walton <noloader AT gmail DOT com>
Date: Fri, 13 Apr 2018 20:36:56 -0400
Message-ID: <CAH8yC8ngb9RuWkAs-Ld6qFswsh0qjfm-mrWLBTtgKM-zWjiPPw@mail.gmail.com>
Subject: Re: Incorrect /proc/cpuinfo for AMD A6-9220
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

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?

Jeff

--
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