From: Stephen Hemminger <stephen@networkplumber.org>
To: Matteo Croce <mcroce@redhat.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>
Subject: Re: [PATCH iproute2-next] Makefile: pass -pipe to the compiler
Date: Tue, 11 Jun 2019 12:28:00 -0700 [thread overview]
Message-ID: <20190611122800.56d72eba@hermes.lan> (raw)
In-Reply-To: <20190611180513.30772-1-mcroce@redhat.com>
On Tue, 11 Jun 2019 20:05:13 +0200
Matteo Croce <mcroce@redhat.com> wrote:
> Pass the -pipe option to GCC, to use pipes instead of temp files.
> On a slow AMD G-T40E CPU we get a non negligible 6% improvement
> in build time.
>
> real 1m15,111s
> user 1m2,521s
> sys 0m12,465s
>
> real 1m10,861s
> user 1m2,520s
> sys 0m12,901s
>
> Signed-off-by: Matteo Croce <mcroce@redhat.com>
Why bother, on my machine (make -j12).
Before
real 0m6.320s
user 0m30.674s
sys 0m3.649s
After (with -pipe)
real 0m6.158s
user 0m31.197s
sys 0m3.532s
So it is slower. Get a faster disk :-)
Maybe allow "EXTRA_CFLAGS" to be passed to Makefile for those that
have a burning need for this.
next prev parent reply other threads:[~2019-06-11 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:05 [PATCH iproute2-next] Makefile: pass -pipe to the compiler Matteo Croce
2019-06-11 19:28 ` Stephen Hemminger [this message]
2019-07-14 16:36 ` Matteo Croce
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=20190611122800.56d72eba@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dsahern@kernel.org \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
/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.
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).