public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Rodriguez Bahena, Victor" <victor.rodriguez.bahena@intel.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Add avx2 fake-capability, like tls
Date: Fri, 17 Mar 2017 19:18:00 -0000	[thread overview]
Message-ID: <D4F19280.122A5%victor.rodriguez.bahena@intel.com> (raw)
In-Reply-To: <20170317033949.GI24205@vapier>


On 3/16/17, 9:39 PM, "Mike Frysinger" <vapier@gentoo.org> wrote:

>On 03 Jan 2017 19:53, Victor Rodriguez wrote:
>> The idea of the patch is to provide AVX2 capability to glibc, original
>> patch from: Dimitri John Ledkov <dimitri.j.ledkov@intel.com>.
>> It has been proved that the use of AVX2 improves the performance of
>>current
>> numerical applications. With this patch the Linux distributions will be
>>able to
>> handle AVX2 in glibc
>
>i don't think this description is accurate/relevant.  looks like you're
>trying to add a new search path to ldconfig/ld.so.cache so that people
>can build libs w/-mavx2 turned on and then put them under a path e.g.
>/lib64/avx2/ ?
>
>you can't add arch-specific functionality to common code like this.
>this patch will break all non-x86 arches.
>
>i think you want to actually be updating these files:
>	sysdeps/i386/dl-procinfo.[ch]
>	sysdeps/x86_64/dl-procinfo.[ch]
>-mike

Thanks for the feedback , working on V2

>

  reply	other threads:[~2017-03-17 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 19:53 Victor Rodriguez
2017-01-11  0:56 ` Victor Rodriguez
2017-03-17  3:39 ` Mike Frysinger
2017-03-17 19:18   ` Rodriguez Bahena, Victor [this message]
2017-04-06 22:20     ` H.J. Lu

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=D4F19280.122A5%victor.rodriguez.bahena@intel.com \
    --to=victor.rodriguez.bahena@intel.com \
    --cc=libc-alpha@sourceware.org \
    --cc=vapier@gentoo.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).