public inbox for
 help / color / mirror / Atom feed
From: Joel Sherrill <>
To: Newlib <>
Subject: Placement of signgam in libc instead of libm
Date: Thu, 20 Apr 2023 16:20:25 -0500	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]


While double some checking that all references used by the long double math
routines Jennifer are resolved when linking, we have found a small oddity.

The file libc/reent/signgam.c is implemented as follows:

int *
__signgam (void)

When TLS is enabled, the macro _REENT_SIGNGAM resolves to
_tls_gamma_signgam which is in the file libm/math/w_lgamma.c. This creates
the first reference from libc to libm that I have ever seen and requires
explicitly linking with -lm -lc when using lgamma().

Would anyone be opposed to moving this method to libm/math?


             reply	other threads:[~2023-04-20 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 21:20 Joel Sherrill [this message]
2023-04-24  8:52 ` Corinna Vinschen
2023-04-24 15:16   ` Jeff Johnston

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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).