mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Model specific optimizations?
Date: Fri, 30 Sep 2016 00:05:15 +0200	[thread overview]
Message-ID: <20160929220514.GI1280@port70.net> (raw)
In-Reply-To: <34de22ab-4bbe-6d23-3dfd-57779c7c99d1@linaro.org>

* Adhemerval Zanella <adhemerval.zanella@linaro.org> [2016-09-29 11:52:44 -0700]:
> On 29/09/2016 11:13, Rich Felker wrote:
> > On Linux it's supposed to be the kernel which detects availability of
> > features (either by feature-specific cpu flags or translating a model
> > to flags) but I don't see anything for fsqrt on ppc. :-( How/why did
> > they botch this?
> 
> Maybe because recent power work on kernel is POWER oriented, where fsqrt
> is define since POWER4.  However some more recent freescale chips (such
> as e5500 and e6500) also decided to not add fsqrt instruction.
> 
> With GCC you can check for _ARCH_PPCSQ to see if current arch flags 
> allows fsqrt.  From runtine I presume programs can check for hwcap bit
> PPC_FEATURE_POWER4, however it does not help on non-POWER chips which
> do support fsqrt.
> 

how can distros deal with this?

do they require POWER4?


  reply	other threads:[~2016-09-29 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 14:21 Markus Wichmann
2016-09-29 14:57 ` Szabolcs Nagy
2016-09-29 15:23 ` Rich Felker
2016-09-29 17:08   ` Markus Wichmann
2016-09-29 18:13     ` Rich Felker
2016-09-29 18:52       ` Adhemerval Zanella
2016-09-29 22:05         ` Szabolcs Nagy [this message]
2016-09-29 23:14           ` Adhemerval Zanella
2016-09-30  4:56       ` Markus Wichmann
2016-10-01  5:50         ` Rich Felker
2016-10-01  8:52           ` Markus Wichmann
2016-10-01 15:10             ` Rich Felker
2016-10-01 19:53               ` Markus Wichmann
2016-10-02 13:59                 ` Adhemerval Zanella

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=20160929220514.GI1280@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).