public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Visar Zejnullahu <visar@siva.mk>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Testing newlib
Date: Mon, 25 Jul 2011 18:02:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1107252046230.3160@sg-laptop> (raw)
In-Reply-To: <4E2D53B4.1060108@siva.mk>

On Mon, 25 Jul 2011, Visar Zejnullahu wrote:

> Hi.
> 
> As announced here:
> http://sourceware.org/ml/ecos-devel/2011-07/msg00003.html we are working
> on a port of Newlib's single precision floating point math library
> (float vs double...).
> 
> I know part of the questions should be addressed to the Newlib's mailing
> list (which I have done as well), but I am asking help on the Ecos part
> of the problems.

Hi Visar,

[cut set of Q that I do not have the expertise]

> And lastly, about the gamma function - I've used the tests provided
> from Newlib, and when I try to compile the test files about this
> function, I get the error
> ecos/packages/language/c/libm/current/src/double/ieee754-api/w_gamma.c:99:
> undefined reference to `signgam'. Can anyone help on this?

Look, please, at ecos math.h:160

  #ifdef CYGSEM_LIBM_THREAD_SAFE_GAMMA_FUNCTIONS

  // FIXME: these need to be documented and signgam mentioned as non-ISO
  // This returns the address of the signgam variable used by the gamma*() and
  // lgamma*() functions
  externC int *
  cyg_libm_get_signgam_p( void );

  #define signgam (*cyg_libm_get_signgam_p())


I think you will get it. Also, the next point to look on

libm.cdl:125:cdl_option CYGSEM_LIBM_THREAD_SAFE_GAMMA_FUNCTIONS

IMHO, the option's description attribute is the very informative.


Sergei

      reply	other threads:[~2011-07-25 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 11:30 Visar Zejnullahu
2011-07-25 18:02 ` Sergei Gavrikov [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=alpine.DEB.2.00.1107252046230.3160@sg-laptop \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=visar@siva.mk \
    /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).