public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27958] fatal error: bits/platform/x86.h: No such file or directory
Date: Fri, 23 Jul 2021 12:21:21 +0000	[thread overview]
Message-ID: <bug-27958-131-sxjfFzgBkh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27958-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27958

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7c124e3714c38157230ed1a5d743b37defe64dc2

commit 7c124e3714c38157230ed1a5d743b37defe64dc2
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sat Jun 5 06:42:20 2021 -0700

    x86: Install <bits/platform/x86.h> [BZ #27958]

    1. Install <bits/platform/x86.h> for <sys/platform/x86.h> which includes
    <bits/platform/x86.h>.
    2. Rename HAS_CPU_FEATURE to CPU_FEATURE_PRESENT which checks if the
    processor has the feature.
    3. Rename CPU_FEATURE_USABLE to CPU_FEATURE_ACTIVE which checks if the
    feature is active.  There may be other preconditions, like sufficient
    stack space or further setup for AMX, which must be satisfied before the
    feature can be used.

    This fixes BZ #27958.

    Reviewed-by: Carlos O'Donell <carlos@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-07-23 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05 13:40 [Bug libc/27958] New: " hjl.tools at gmail dot com
2021-07-23 12:21 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-25 17:46 ` [Bug libc/27958] " hjl.tools at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27958-131-sxjfFzgBkh@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).