mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Pascal Cuoq <cuoq@trust-in-soft.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Cc: vilimp <vilimp@volny.cz>
Subject: Re: clarify bswap a bit more for gcc
Date: Sun, 24 Mar 2019 14:31:02 +0000	[thread overview]
Message-ID: <3B6039DA-8A3A-4E04-B7DD-43A5049E1698@trust-in-soft.com> (raw)
In-Reply-To: <20190324122618.D367D3A0@volny.cz>

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


On 24 Mar 2019, at 12:26, vilimp@volny.cz<mailto:vilimp@volny.cz> wrote:

i know nearly nothing about programing, but is it possible to upstream this
patch, please? It gets rid of gcc's warnings.

If you search around for discussion about this GCC warning, you will find a lot of opinions such as

“That's the one warning that I like to disable. I hate having to write superfluous parentheses around conjunctions. I mean, come on. It's just as lame as requiring them around multiplications would be.” https://news.ycombinator.com/item?id=15405045

“Fortunately I live by my own rule, to avoid unnecessary parentheses” http://wordaligned.org/articles/fixing-compiler-warnings-the-hard-way

There is no reason to think that people in the position of making this change have not already compiled musl with GCC, seen the warning and decided it wasn't useful. Do “git grep parentheses” in musl and you'll find:

configure:tryflag CFLAGS_AUTO -Wno-parentheses

Whatever you did to compile musl, if I were you I would just try to find how to do it in in a way that does not activate this warning.

Pascal


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

      reply	other threads:[~2019-03-24 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 11:26 vilimp
2019-03-24 14:31 ` Pascal Cuoq [this message]

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=3B6039DA-8A3A-4E04-B7DD-43A5049E1698@trust-in-soft.com \
    --to=cuoq@trust-in-soft.com \
    --cc=musl@lists.openwall.com \
    --cc=vilimp@volny.cz \
    /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).