mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Daniel Sabogal <dsabogalcc@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Header conformance/improvements
Date: Thu, 20 Oct 2016 19:19:50 -0400	[thread overview]
Message-ID: <CAFhhQJQu4o++-U2ocFC5i24rgPMsstOUx7SBPKRUK61gDY-5Aw@mail.gmail.com> (raw)
In-Reply-To: <20161020213058.GT19318@brightrain.aerifal.cx>

On Thu, Oct 20, 2016 at 5:30 PM, Rich Felker <dalias@libc.org> wrote:
> On Tue, Oct 11, 2016 at 06:44:14PM -0400, Daniel Sabogal wrote:
>> namespace/feature testing
>> -------------------------
>> sys/time.h:13-29: sys/time.h - XSI header
>
> Not sure what you mean here. If the whole header is XSI there's no
> obligation to check FTMs; a conforming non-XSI program doesn't include
> it.

Sorry, I should have been more descriptive with this one. The issue here is
that there are unnecessary checks for _XOPEN_SOURCE.

>> misc
>> ----
>> stdlib.h:155-8:
>> glibc provides locale_t under _GNU_SOURCE. maybe it should
>> be provided and used in place of struct __locale_struct.
>
> Do you have in mind a scenario where this would be useful, i.e. where
> you might need locale_t to be defined but not have included another
> header that defines it?

I was really only thinking along the lines of keeping it consistent with
how all other headers provide locale_t via __NEED_locale_t.
I don't believe there are any real benefits and that any software package
already doing this should be easily patch-able.

>> string.h:88:
>> gcc generates an implicit-function-declaration warning from alloca
>> when using strdupa. aside: glibc also provides strndupa.
>
> We discussed making this definition depend on __GNUC__ and then it
> could use __builtin_alloca and GCC extensions needed to make strndupa
> work. There might be an old patch floating around to do something like
> that.

OK.


  reply	other threads:[~2016-10-20 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 22:44 Daniel Sabogal
2016-10-20 21:30 ` Rich Felker
2016-10-20 23:19   ` Daniel Sabogal [this message]
2016-11-07 16:50     ` Rich Felker

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=CAFhhQJQu4o++-U2ocFC5i24rgPMsstOUx7SBPKRUK61gDY-5Aw@mail.gmail.com \
    --to=dsabogalcc@gmail.com \
    --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).