mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] eliminate strict parentheses warnings for byteswaps
Date: Thu, 14 Feb 2019 19:55:50 -0600	[thread overview]
Message-ID: <ce05bebb-d97a-05aa-097f-40e4f32eb3fc@adelielinux.org> (raw)
In-Reply-To: <CANmYxDuccuwi4T0Fz4WtSOERJT3p9uouoqtwf0R44dfmD_2tgw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1406 bytes --]

On 02/14/19 18:24, Nick Bray wrote:
> Patch is attached.
> 
> The change was motivated by including Musl's headers from a project
> with -Werror -Wall enabled. I believe Fucshia ran into this, too.  I
> couldn't think of a good regression test, in part because warnings are
> somewhat compiler specific.  One possible approach would be to enable
> -Werror -Wall in the main build, but that runs into issues of which
> compilers are supported and what the core developers prefer.  Another
> approach would be to only lint the header files - generate a dummy .c
> file that includes all the header files and compile it with -Werror.
> This is complicated by the "redirection" header files that warn you
> should use the canonical version.  Which header files should be
> checked?  So for the moment I punted on regression testing.  I mention
> this line of thinking in case anyone has some perspective. 


This has a strong +1 from me, but changes like this have already been
rejected at least twice on this list because "compilers shouldn't warn
about system headers".

Perhaps at attempt #3, they will just accept that this happens regularly
enough that a few parens is not the end of the world.  (It also makes
more components of musl reusable in other libraries, if desired.)

Best,
--arw

-- 
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-02-15  1:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15  0:24 Nick Bray
2019-02-15  1:55 ` A. Wilcox [this message]
2019-02-15  2:27   ` Nick Bray
2019-02-15  2:38     ` Rich Felker
2019-02-19 22:54       ` Nick Bray

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=ce05bebb-d97a-05aa-097f-40e4f32eb3fc@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --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).