From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-11294-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 8325 invoked by alias); 27 May 2010 04:51:40 -0000
Received: (qmail 8283 invoked by uid 48); 27 May 2010 04:51:25 -0000
Date: Thu, 27 May 2010 04:51:00 -0000
From: "hjl dot tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20100527045125.11640.hjl.tools@gmail.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug libc/11640] New: Incorrect x86 CPU family and model check
X-Bugzilla-Reason: CC
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2010-05/txt/msg00116.txt.bz2

Glibc trunk, 2.12, 2.11 has

      if (__cpu_features.family == 0x0f)
	{
	  family += extended_family;
	  model += extended_model;
	}
      else if (__cpu_features.family == 0x06)
	{
	  model += extended_model;
	  switch (__cpu_features.model)
...
  __cpu_features.family = family;
  __cpu_features.model = model;

__cpu_features.family and __cpu_features.family are checked
before they are set.  A patch is posted at

http://sourceware.org/ml/libc-alpha/2010-05/msg00048.html

It should be applied cleanly to trunk and 2.12. 2.11 needs
small changes.

-- 
           Summary: Incorrect x86 CPU family and model check
           Product: glibc
           Version: 2.12
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: hjl dot tools at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11640

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.