From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: V8: [PATCH] x86: Support usable check for all CPU features
Date: Tue, 07 Jul 2020 13:18:12 +0200 [thread overview]
Message-ID: <87fta3zi8b.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200706142805.GA3116282@gmail.com> (H. J. Lu's message of "Mon, 6 Jul 2020 07:28:05 -0700")
* H. J. Lu:
> Good point. Here is the updated patch to only copy known bits.
I see a build failure. What other patches do I need to apply before
this one?
In file included from ../sysdeps/x86/ldsodefs.h:24,
from ../sysdeps/gnu/ldsodefs.h:46,
from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
from ../sysdeps/x86/init-arch.h:21,
from ../sysdeps/x86/cacheinfo.c:26:
../sysdeps/x86/cacheinfo.c: In function ‘init_cacheinfo’:
../sysdeps/x86/cpu-features.h:123:20: error: ‘index_arch_AVX512F_Usable’ undeclared (first use in this function)
123 | ((ptr->preferred[index_arch_##name] & bit_arch_##name) != 0)
| ^~~~~~~~~~~
../sysdeps/x86/cpu-features.h:143:3: note: in expansion of macro ‘CPU_FEATURE_PREFERRED_P’
143 | CPU_FEATURE_PREFERRED_P (ptr, name)
| ^~~~~~~~~~~~~~~~~~~~~~~
../sysdeps/x86/cacheinfo.c:886:7: note: in expansion of macro ‘CPU_FEATURES_ARCH_P’
886 | if (CPU_FEATURES_ARCH_P (cpu_features, AVX512F_Usable)
| ^~~~~~~~~~~~~~~~~~~
../sysdeps/x86/cpu-features.h:123:20: note: each undeclared identifier is reported only once for each function it appears in
123 | ((ptr->preferred[index_arch_##name] & bit_arch_##name) != 0)
| ^~~~~~~~~~~
../sysdeps/x86/cpu-features.h:143:3: note: in expansion of macro ‘CPU_FEATURE_PREFERRED_P’
143 | CPU_FEATURE_PREFERRED_P (ptr, name)
| ^~~~~~~~~~~~~~~~~~~~~~~
../sysdeps/x86/cacheinfo.c:886:7: note: in expansion of macro ‘CPU_FEATURES_ARCH_P’
886 | if (CPU_FEATURES_ARCH_P (cpu_features, AVX512F_Usable)
| ^~~~~~~~~~~~~~~~~~~
../sysdeps/x86/cpu-features.h:123:41: error: ‘bit_arch_AVX512F_Usable’ undeclared (first use in this function)
123 | ((ptr->preferred[index_arch_##name] & bit_arch_##name) != 0)
| ^~~~~~~~~
../sysdeps/x86/cpu-features.h:143:3: note: in expansion of macro ‘CPU_FEATURE_PREFERRED_P’
143 | CPU_FEATURE_PREFERRED_P (ptr, name)
| ^~~~~~~~~~~~~~~~~~~~~~~
../sysdeps/x86/cacheinfo.c:886:7: note: in expansion of macro ‘CPU_FEATURES_ARCH_P’
886 | if (CPU_FEATURES_ARCH_P (cpu_features, AVX512F_Usable)
| ^~~~~~~~~~~~~~~~~~~
I'm particularly interested in the size of the data structure.
Thanks,
Florian
next prev parent reply other threads:[~2020-07-07 11:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 4:35 V7: [PATCH 0/2] x86: Install <sys/platform/x86.h> H.J. Lu
2020-06-30 4:35 ` V7: [PATCH 1/2] x86: Support usable check for all CPU features H.J. Lu
2020-07-04 17:17 ` H.J. Lu
2020-07-06 10:45 ` Florian Weimer
2020-07-06 14:28 ` V8: [PATCH] " H.J. Lu
2020-07-07 11:18 ` Florian Weimer [this message]
2020-07-07 11:46 ` V9 " H.J. Lu
2020-07-08 15:49 ` Florian Weimer
2020-07-08 16:32 ` V10 " H.J. Lu
2020-07-12 12:36 ` H.J. Lu
2020-07-13 11:19 ` Florian Weimer
2020-07-13 12:40 ` H.J. Lu
2021-03-08 14:26 ` Andreas Schwab
2021-03-08 14:29 ` Florian Weimer
2020-06-30 4:35 ` V7: [PATCH 2/2] x86: Install <sys/platform/x86.h> [BZ #26124] H.J. Lu
2020-07-15 14:55 ` PING: " H.J. Lu
2020-07-15 14:58 ` H.J. Lu
2020-07-16 20:15 ` Carlos O'Donell
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=87fta3zi8b.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).