From: Vali Cobelea <valentin.cobelea@enea.com>
To: <openembedded-core@lists.openembedded.org>
Subject: GCC PARALLEL_MAKE changed
Date: Thu, 8 Aug 2013 10:55:53 +0300 [thread overview]
Message-ID: <52034F09.1090904@enea.com> (raw)
Hi,
We noticed that the GCC parallel make flag (PARALLEL_MAKE, located in
"meta/recipes-devtools/gcc/gcc-cross-canadian_4.?.bb") got changed from
"-j 32" to simply nothing.
We are wondering what was the reason for this change, which seems to
have been made somewhere before the fall of 2012, while the GCC was
around version 4.6 or earlier (for each we dont have the repository to
track down the change).
After several builds where the compile time for GCC got measured, I can
say that this flag indeed reduces the build time, when it is put at "-j
32" (using a proper build machine).
In average the build time frame was reduced by 18%.
Much appreciated any thoughts on this, I know that it has been a while
since this change happen.
Thank you very much,
Vali
next reply other threads:[~2013-08-08 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 7:55 Vali Cobelea [this message]
2013-08-08 20:06 ` GCC PARALLEL_MAKE changed Khem Raj
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=52034F09.1090904@enea.com \
--to=valentin.cobelea@enea.com \
--cc=openembedded-core@lists.openembedded.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