public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Samir Droubi via Libc-help <libc-help@sourceware.org>
Cc: Samir Droubi <samirdr@mit.edu>
Subject: Re: ____wcstold_l_internal Question
Date: Fri, 02 Dec 2022 07:09:38 +0100	[thread overview]
Message-ID: <877czauyjh.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <PH0PR01MB6635AE916819A38676A76F3FA2179@PH0PR01MB6635.prod.exchangelabs.com> (Samir Droubi via Libc-help's message of "Fri, 2 Dec 2022 05:39:11 +0000")

* Samir Droubi via Libc-help:

> I was profiling a project that I have been working on and the function
> above shows up amongst other internal functions. I was wondering if
> you could shed a light on what could possibly be happening to cause
> calls to this function to be so frequent. Here is the profiling
> result:
>
>   13.72%  mitscriptbc  libc.so.6             [.] ____wcstold_l_internal
>    5.45%  mitscriptbc  libc.so.6             [.] ____wcstof_l_internal
>    2.46%  mitscriptbc  libc.so.6             [.] round_and_return
>    2.28%  mitscriptbc  libc.so.6             [.] ____wcstod_l_internal
>
> The libc version being used is 2.35.

The external name is wcstold or wcstold_l.  If your application isn't
calling that, the profiling data is wrong.  You might find out by
setting a breakpoint or probe on the function.

Thanks,
Florian


  reply	other threads:[~2022-12-02  6:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  5:39 Samir Droubi
2022-12-02  6:09 ` Florian Weimer [this message]
2022-12-03  7:57   ` Noah Goldstein
2022-12-03 19:20     ` Samir Droubi

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=877czauyjh.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=samirdr@mit.edu \
    /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).