mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: spandsp testsuite, feenableexcept() is missing
Date: Fri, 14 Dec 2012 14:55:02 -0500	[thread overview]
Message-ID: <20121214195502.GN20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <50CB82C6.4010209@ojab.ru>

On Fri, Dec 14, 2012 at 11:49:26PM +0400, ojab wrote:
> On 14.12.2012 22:58, Rich Felker wrote:
> >On Fri, Dec 14, 2012 at 06:30:28PM +0400, ojab wrote:
> >>>Hi list,
> >>>
> >>>spandsp testsuite build fails with
> >>>> >/root/spandsp/tests/v17_tests.c:311: undefined reference to `feenableexcept'
> >>>
> >>>AFAIU all functions from fenv.h are not implemented. Is there plans
> >>>to implement them before 1.0/at all?
> >fenv.h is implemented. The issue is that feenableexcept is not part of
> >the standard for fenv.h; it's an extension added by glibc for turning
> >on trapping exceptions. This usage is non-portable (as far as I know,
> >many machines don't support trapping exceptions) and I've never seen a
> >program actually making use of them. It looks like spandsp is just
> >using this function in its test suite, probably to test some
> >exception-relted behavior. I think this should be fixed upstream,
> >since it won't work on other non-GNU systems either.
> >
> 
> Ouch, stupid me, I thought that I've checked posix about it.
> Sorry for the noise.

No problem. It's still useful to have a record that at least some
program was trying to use it, even if only for testing purposes; it
helps evaluate whether it would ever make sense to add it. However, if
you're going to support trapping exceptions, there are a few fenv
functions which become slightly more complicated or more expensive,
and as long as nothing actually wants trapping exceptions, I think it
makes the most sense just to say "they're not supported and we offer
no interface to turn them on"; then, the rest of fenv can safely
assume they're off.

Rich


      reply	other threads:[~2012-12-14 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 14:30 ojab
2012-12-14 18:58 ` Rich Felker
2012-12-14 19:49   ` ojab
2012-12-14 19:55     ` Rich Felker [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=20121214195502.GN20323@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).