From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23847 invoked by alias); 4 Jun 2012 22:14:45 -0000 Received: (qmail 23817 invoked by uid 22791); 4 Jun 2012 22:14:43 -0000 X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_HW X-Spam-Check-By: sourceware.org Received: from mail-yx0-f169.google.com (HELO mail-yx0-f169.google.com) (209.85.213.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 Jun 2012 22:14:31 +0000 Received: by yenm7 with SMTP id m7so4044025yen.0 for ; Mon, 04 Jun 2012 15:14:30 -0700 (PDT) Received: by 10.50.169.73 with SMTP id ac9mr40355igc.29.1338848070343; Mon, 04 Jun 2012 15:14:30 -0700 (PDT) Received: from pebble.twiddle.home ([173.160.232.49]) by mx.google.com with ESMTPS id vi7sm13106547igb.10.2012.06.04.15.14.29 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 15:14:29 -0700 (PDT) Message-ID: <4FCD333E.3090107@twiddle.net> Date: Mon, 04 Jun 2012 22:14:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: "Ryan S. Arnold" CC: libc-alpha@sourceware.org, libc-ports@sourceware.org Subject: Re: Include hwcap as ifunc argument References: <4FBA744A.6000702@twiddle.net> <4FBFC4EC.1060209@twiddle.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00010.txt.bz2 On 06/04/2012 02:21 PM, Ryan S. Arnold wrote: > Peter Bergner reminded me today that on PowerPC the IFUNC resolver > will most likely/often use the value in AT_PLATFORM rather than > AT_HWCAP to determine which optimized function to use. I suppose this > would diminish the necessity of passing the hwcap to the ifunc > resolver. It depends on what's being tested, I suppose. Within glibc itself you've got lots of platform-specific tuning, so you may well use AT_PLATFORM more. Outside glibc, it might just be a test for Altivec or VDX or whatever. r~