From: Takashi Iwai <tiwai@suse.de>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Mersad Jelacic <mersad@axis.com>
Subject: Re: alsa-lib and floating point support
Date: Wed, 20 Sep 2017 18:10:07 +0200 [thread overview]
Message-ID: <s5hmv5pcpwg.wl-tiwai@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1709201642470.14549@lnxricardw1.se.axis.com>
On Wed, 20 Sep 2017 16:45:46 +0200,
Ricard Wanderlof wrote:
>
>
> On Wed, 20 Sep 2017, Takashi Iwai wrote:
>
> > > I'm trying to understand why it is critical to have hardware floating
> > > point support in this case. The pow() function is very resource hungry,
> > > true, but the function is only called when the plugin is loaded, and not
> > > for instance on every sample while the stream is running, so on the whole
> > > I would expect the impact to be minimal. Is there some other rationale
> > > that I'm missing?
> >
> > The softfloat option is to avoid calculation in float as much as
> > possible, i.e. alsa-lib will be built without any usage of math
> > library.
>
> "as much as possible" sounds like the softvol case would be a reasonable
> exception, on the other hand, if the goal is to completely avoid using the
> softfloat library I can see the point. Is the reason to avoid dependency
> issues, or to minimize the total resulting code size, especially on
> systems with limited memory?
Well, actually no, because we don't link with -lm when the option is
specified, so far. That is, the softfloat option is for controlling
whether to allow the usage of math function or not.
Takashi
prev parent reply other threads:[~2017-09-20 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 10:55 alsa-lib and floating point support Ricard Wanderlof
2017-09-20 11:26 ` Takashi Iwai
2017-09-20 14:45 ` Ricard Wanderlof
2017-09-20 16:10 ` Takashi Iwai [this message]
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=s5hmv5pcpwg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=mersad@axis.com \
--cc=ricard.wanderlof@axis.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.