From: Brad Conroy <technosaurus@yahoo.com>
To: Musl <musl@lists.openwall.com>
Subject: Clang-3.9 regression
Date: Mon, 26 Sep 2016 07:12:00 +0000 (UTC) [thread overview]
Message-ID: <888923693.4612496.1474873920782@mail.yahoo.com> (raw)
In-Reply-To: <888923693.4612496.1474873920782.ref@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
It seems the latest versions of Clang default to unrolling loops.Even when -Os or -Oz is enabled (musl's default configuration)This significantly increases code size on many functions.I didn't do any bench-marking to determine how it affects speed.It can be prevented by adding: -fno-unroll-loops
-R,Brad Conroy
[-- Attachment #2: Type: text/html, Size: 887 bytes --]
parent reply other threads:[~2016-09-26 7:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <888923693.4612496.1474873920782.ref@mail.yahoo.com>]
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=888923693.4612496.1474873920782@mail.yahoo.com \
--to=technosaurus@yahoo.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).