mailing list of musl libc
 help / color / mirror / code / Atom feed
From: James Y Knight <jyknight@google.com>
To: musl@lists.openwall.com
Cc: "Ram Nalamothu (QUIC)" <quic_vnalamot@quicinc.com>
Subject: Re: [musl] Integer only print functions support in MUSL
Date: Wed, 12 Jun 2024 15:21:45 -0400	[thread overview]
Message-ID: <CAA2zVHpHbeFq+o55EauSDjioA7jmh=aeoh7mRuLgHcw_6aaZiA@mail.gmail.com> (raw)
In-Reply-To: <ZmnvW2cQSxZjCxWm@voyager>

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

According to LLVM sources (LLVM knows how to transform printf variants into
iprintf variants), "iprintf and friends are only available on XCore, TCE,
and Emscripten."

I note that emscripten actually uses musl's printf implementation, and has
added iprintf support as a downstream patch.



On Wed, Jun 12, 2024 at 2:56 PM Markus Wichmann <nullplan@gmx.net> wrote:

> Am Wed, Jun 12, 2024 at 05:29:59PM +0000 schrieb Ram Nalamothu (QUIC):
> > Hi,
> >
> > On the subject line topic, is there a plan for integer only print
> functions support in MUSL upstream?
> >
> > The newlib seems to support the same since 2004 [1] and one immediate
> scenario using this capability is assert function [2] in the C library
> itself which needs to print only the non-float types.
> >
> > Applications that use integer only print functions can benefit from this
> capability in terms of reduced code size by avoiding floating point support
> implementation in the linked print functions.
> >
> > I tried a quick search on the mailing list but couldn't find any
> previous discussions on this topic.
> > Would it make sense to have the similar support in MUSL as well? Would
> the community be open to accept patches supporting integer only print
> functions?
> >
> > Regards,
> > Ram
> >
> > [1] https://sourceware.org/legacy-ml/newlib/2004/msg00577.html
> > [2]
> https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/stdlib/assert.c#l58
>
> Standard criteria for inclusion in musl have always been any kind of
> standardization effort at all. Otherwise there is a risk of future
> incompatible standardization. And iprintf() seems to be a newlib
> exclusive; I cannot find any reference to this function outside of it.
>
> Ciao,
> Markus
>

[-- Attachment #2: Type: text/html, Size: 2431 bytes --]

  reply	other threads:[~2024-06-12 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 17:29 Ram Nalamothu (QUIC)
2024-06-12 18:56 ` Markus Wichmann
2024-06-12 19:21   ` James Y Knight [this message]
2024-06-13  1:06 ` Rich Felker
2024-06-13 16:03   ` James Y Knight
2024-06-27  6:15     ` Ram Nalamothu (QUIC)

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='CAA2zVHpHbeFq+o55EauSDjioA7jmh=aeoh7mRuLgHcw_6aaZiA@mail.gmail.com' \
    --to=jyknight@google.com \
    --cc=musl@lists.openwall.com \
    --cc=quic_vnalamot@quicinc.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).