From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Views on bare metal port
Date: Wed, 31 Jan 2018 14:11:09 -0500 [thread overview]
Message-ID: <20180131191109.GQ1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAOUYtQDu1A9hqs+dBQQVPcWnXpWr7j+srzYpAG_HLCjUadARdA@mail.gmail.com>
On Wed, Jan 31, 2018 at 06:37:24PM +0000, Jon Chesterfield wrote:
> Yep, that's the 5%! There's work on rounding modes happening in LLVM at
> present, but it doesn't work yet and I can't justify working on it :(
>
> There are a number of style warnings from clang related to operator
> precedence (suggesting more parentheses) - would patches for these be worth
> submitting?
No, they'll almost surely be rejected. What would be nice is a
proposal for getting the warnings we want, and only the ones we want,
by default on clang. Right now configure is well-tuned to do that for
gcc but not for clang.
I think what we need is probably first some way to detect if -w is
needed to turn off unwanted defaults (it's unsafe to use with gcc
because it overrides even -W's that come _after_ it), then using -w,
omitting -Wall, and manually building up the interesting warnings.
Rich
next prev parent reply other threads:[~2018-01-31 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOUYtQBwKmfwjmxUy+mfd0Qg+n78rCwKtK2=X6xgK-Cmt6EGXQ@mail.gmail.com>
[not found] ` <CAOUYtQB4+8Yey+Q2yT3GWqTiobgPNf60G6dZHjUyjbj1SUC0TA@mail.gmail.com>
[not found] ` <CAOUYtQD1LF03fbZ3U4e=s3uXiiY46jkuTjvzdfnz=c3mvzCrhw@mail.gmail.com>
[not found] ` <CAOUYtQAZ-90b39f0Okz+KsnYK9G1FwdpTGtMSwJsWtsPwEWM-Q@mail.gmail.com>
[not found] ` <CAOUYtQCNCU4rN74+HHmBTfgLTEdAhypWSL1L=Ooc1ocqjpEW_Q@mail.gmail.com>
[not found] ` <CAOUYtQCCwhp-RSmod+dzLrFzqrR_Om-p6dD5kEkNtMT2B48FjQ@mail.gmail.com>
[not found] ` <CAOUYtQDM4BW=WEXD5RK2YWf+3zj+opBuK8vsPwEPfyM3Hyo_6w@mail.gmail.com>
[not found] ` <CAOUYtQCsJU_qczmjpH8NHbgqSHVLEAYOdpHVu7nmkie3zWAAyw@mail.gmail.com>
[not found] ` <CAOUYtQDc8VHkH13Ah_+azk+goeOsthjFOhE4KfV6PCMoMKfukA@mail.gmail.com>
[not found] ` <CAOUYtQCJD1Y-xV2bbBiGxE-W8jSWA9Qm=bzn1ri5Lq9+ACKSLw@mail.gmail.com>
[not found] ` <CAOUYtQA3i8-z+LtzDbsUTJmLn76UXvDUpbKVHNfECSCMrPdiKA@mail.gmail.com>
[not found] ` <CAOUYtQBDV0_0hkjtT3A+uOqnDkuKD-ZDr_DLo=DVSO5B6YZ3AA@mail.gmail.com>
[not found] ` <CAOUYtQCHi6qR+=Jae--6M1VzeSiDBjj9_86hkpmN=XhSFDTTiQ@mail.gmail.com>
2018-01-31 13:38 ` Jon Chesterfield
2018-01-31 15:25 ` Rich Felker
2018-01-31 17:51 ` Jon Chesterfield
2018-01-31 18:25 ` Szabolcs Nagy
2018-01-31 18:37 ` Jon Chesterfield
2018-01-31 19:11 ` Rich Felker [this message]
2018-04-01 11:19 ` ardi
2018-04-01 14:29 ` Szabolcs Nagy
2018-04-01 20:12 ` ardi
2018-02-17 22:37 ` ardi
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=20180131191109.GQ1627@brightrain.aerifal.cx \
--to=dalias@libc.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).