From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 57120 invoked by alias); 17 Aug 2018 19:11:09 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 57106 invoked by uid 89); 17 Aug 2018 19:11:08 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,SPF_HELO_PASS autolearn=no version=3.3.2 spammy= X-HELO: mx1.redhat.com Subject: Re: RFC: Add to glibc 2.29 To: "H.J. Lu" Cc: GNU C Library References: <20180729161623.GA17944@gmail.com> <040ab157-8d0f-17e2-1421-a20d4c68d87a@redhat.com> From: Florian Weimer Message-ID: Date: Fri, 17 Aug 2018 19:11:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2018-08/txt/msg00403.txt.bz2 On 08/17/2018 06:43 PM, H.J. Lu wrote: >>>> Are these functions supposed to be usable in IFUNC resolvers? >>> >>> They have the same limitation as >>> >>> /* Used from outside of glibc to get access to the CPU features >>> structure. */ >>> extern const struct cpu_features *__get_cpu_features (void) >>> __attribute__ ((const)); >> >> Sorry, this does not answer my question. > Just like __get_cpu_features, they can be used in IFUNC resolvers. Then we need something like this: Thanks, Florian