From: Trevor Woerner <trevor.woerner@linaro.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: crossgcc@sourceware.org, patches@linaro.org
Subject: [PATCH] gcc: skip core pass 1 when it is unnecessary
Date: Wed, 26 Feb 2014 16:15:00 -0000 [thread overview]
Message-ID: <e9f99d9bd902414c8e3f.1393431331@openSUSE-i7> (raw)
# HG changeset patch
# User Trevor Woerner <trevor.woerner@linaro.org>
# Date 1393431218 18000
# Wed Feb 26 11:13:38 2014 -0500
# Node ID e9f99d9bd902414c8e3f3c6fc36c0fc67f3a7593
# Parent c727adf1b7bd2c1e891db512871dbe7b26797fa6
gcc: skip core pass 1 when it is unnecessary
If neither the Linux headers nor the libc start files are required, skip gcc's
core pass 1 since the build will simply move from pass 1 to pass 2 without
doing any work in between.
Signed-off-by: Trevor Woerner <trevor.woerner@linaro.org>
diff -r c727adf1b7bd -r e9f99d9bd902 scripts/build/cc/gcc.sh
--- a/scripts/build/cc/gcc.sh Tue Feb 25 13:34:48 2014 -0500
+++ b/scripts/build/cc/gcc.sh Wed Feb 26 11:13:38 2014 -0500
@@ -88,6 +88,14 @@
return 0
fi
+ # skip gcc pass 1 if there are no Linux kernel headers
+ # nor libc start files to build/process
+ if [ "${CT_LIBC}" = "none" -o "${CT_LIBC}" = "newlib" ]; then
+ if [ "${CT_BARE_METAL}" = "y" ]; then
+ return 0
+ fi
+ fi
+
core_opts+=( "mode=static" )
core_opts+=( "host=${CT_BUILD}" )
core_opts+=( "complibs=${CT_BUILDTOOLS_PREFIX_DIR}" )
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2014-02-26 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 16:15 Trevor Woerner [this message]
2014-05-05 20:10 ` Yann E. MORIN
2014-05-05 20:59 ` Yann E. MORIN
2014-05-05 21:42 ` Yann E. MORIN
2014-05-06 3:25 ` Trevor Woerner
-- strict thread matches above, loose matches on Subject: below --
2014-02-26 16:00 Trevor Woerner
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=e9f99d9bd902414c8e3f.1393431331@openSUSE-i7 \
--to=trevor.woerner@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=patches@linaro.org \
--cc=yann.morin.1998@free.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).