From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6901 invoked by alias); 26 Sep 2014 17:55:50 -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 6890 invoked by uid 89); 26 Sep 2014 17:55:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Message-ID: <5425A89F.1070103@redhat.com> Date: Fri, 26 Sep 2014 17:55:00 -0000 From: "Carlos O'Donell" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: "H.J. Lu" CC: Andrew Senkevich , "Joseph S. Myers" , libc-alpha Subject: Re: [RFC] How to add vector math functions to Glibc References: <54246CB5.7020908@redhat.com> <5424733D.6010305@redhat.com> <54247FAB.6050002@redhat.com> <54258AD4.7000604@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2014-09/txt/msg00602.txt.bz2 On 09/26/2014 12:08 PM, H.J. Lu wrote: >> I think this chioce may actually be larger than just Intel. >> >> For example IBM, and particularly their Power vector math >> functions were explained to me as being callable directly >> by developers. Thus Power might want libmvec.so in glibc? > > Does Power have the same API as x86? If not, how will they > be used by programmers? Power does not have the same API. I expect that David Edhelson was talking about these: http://pic.dhe.ibm.com/infocenter/compbg/v121v141/index.jsp?topic=%2Fcom.ibm.xlcpp121.bg.doc%2Fproguide%2Fvector.html Though I haven't verified. > Again, we need to decide > > 1. Who is the main user. Normal developers. > 2. How it is used by the main user. They call those functions. > 3. What is the impact on the programmers. If the functions are in glibc, we can deploy them independent of compiler. > If we put it in GLIBC, we should have a API with a generic > implementation and each target can have optimized implementation. I disagree. Each target will likely have two APIs: (a) The legacy API supported for compatibility with existing applications following the existing published APIs. e.g. IBM and Intel vector functions. (b) A generic GNU implemetnation that all targets can have. We aren't even talking about (b) yet. Cheers, Carlos.