From: Martin Galvan <omgalvan.86@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Re: #define __MUSL__ in features.h
Date: Thu, 15 Mar 2018 16:02:03 -0300 [thread overview]
Message-ID: <CAN19L9Ec-scDcGzrOOg3cAvEUBjfSD3uhwXTt6eshYaX50U0Jw@mail.gmail.com> (raw)
In-Reply-To: <20180315185358.GJ1436@brightrain.aerifal.cx>
2018-03-15 15:53 GMT-03:00 Rich Felker <dalias@libc.org>:
> In any case it's not a bug in musl. The code is perfectly valid C. If
> the compiler is producing a warning for it, either ignore it or ask
> the compiler to stop.
Just because some code is valid C, it doesn't mean it's not buggy.
>> The compiler warnings aren't being wrongly produced. musl will indeed
>> perform a signed-to-unsigned conversion here.
>
> Because that's how the C language works.
Yes. And gcc has checks to try and make up for C's weak typing.
While your definition of "bug" is debatable, IMHO if a commonly used
option causes application builds to break due to some library, the
library has a usability issue. The issue is even bigger when we're
talking about something as core as the standard C library.
>> So whenever we find a bug on musl we should just stop all our
>> development until you've fixed the bug?
>
> No. As noted above, if you need to support systems that might have bug
> X, you write a test (configure-time or run-time as appropriate) to
> detect bug X and handle it.
Precisely, and __MUSL__ would be really useful for this.
next prev parent reply other threads:[~2018-03-15 19:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 15:55 dgutson .
2018-03-15 18:39 ` Rich Felker
2018-03-15 18:48 ` Martin Galvan
2018-03-15 18:53 ` Rich Felker
2018-03-15 19:00 ` dgutson .
2018-03-15 19:13 ` dgutson .
2018-03-15 19:42 ` Rich Felker
2018-03-15 20:16 ` u-uy74
2018-03-15 20:44 ` u-uy74
2018-03-15 19:37 ` Rich Felker
2018-03-15 19:42 ` dgutson .
2018-03-15 19:02 ` Martin Galvan [this message]
2018-03-15 19:32 ` Rich Felker
2018-03-15 19:37 ` dgutson .
2018-03-15 19:43 ` Rich Felker
2018-03-15 19:52 ` dgutson .
2018-03-15 21:46 ` Szabolcs Nagy
2018-03-15 22:38 ` Rich Felker
2018-03-15 18:51 ` dgutson .
2018-03-15 21:06 ` Markus Wichmann
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=CAN19L9Ec-scDcGzrOOg3cAvEUBjfSD3uhwXTt6eshYaX50U0Jw@mail.gmail.com \
--to=omgalvan.86@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).