From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 8a65d0: gcc: backport fixes that preserve FLAGS_FOR_TARGET
Date: Tue, 15 Mar 2016 16:59:00 -0000 [thread overview]
Message-ID: <56e83f4929e1b_22c13fd4e6be729c2273e2@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2379 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 8a65d08b275837052c497fc5db033b32f3fd5342
https://github.com/crosstool-ng/crosstool-ng/commit/8a65d08b275837052c497fc5db033b32f3fd5342
Author: Max Filippov <jcmvbkbc@gmail.com>
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed paths:
A patches/gcc/4.8.5/130-pr43538.patch
A patches/gcc/4.8.5/131-mt-ospace-preserve-FLAGS_FOR_TARGET.patch
A patches/gcc/4.9.3/130-pr43538.patch
A patches/gcc/4.9.3/131-mt-ospace-preserve-FLAGS_FOR_TARGET.patch
Log Message:
-----------
gcc: backport fixes that preserve FLAGS_FOR_TARGET
CFLAGS_FOR_TARGET and CXXFLAGS_FOR_TARGET are rewritten in gcc-4.8.x and
gcc-4.9.x, so libstdc++ does not get any flags passed to gcc configure.
Backport fixes for config/mt-gnu and config/mt-ospace that preserve these
flags. With these fixes libstdc++ gets built with flags specified in
CT_TARGET_CFLAGS.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Commit: 02d8e4a514773273443c213dab3954bdc626ecbc
https://github.com/crosstool-ng/crosstool-ng/commit/02d8e4a514773273443c213dab3954bdc626ecbc
Author: Max Filippov <jcmvbkbc@gmail.com>
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
scripts/build/cc: pass FLAGS_FOR_TARGET in do_gcc_core_backend
Pass CFLAGS_FOR_TARGET, CXXFLAGS_FOR_TARGET and LDFLAGS_FOR_TARGET to
gcc configure in do_gcc_core_backend as they may be used to build
libstdc++ for bare-metal target.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Commit: a41b269af6001e47df0c6f42cad13e32526b22cb
https://github.com/crosstool-ng/crosstool-ng/commit/a41b269af6001e47df0c6f42cad13e32526b22cb
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed paths:
A patches/gcc/4.8.5/130-pr43538.patch
A patches/gcc/4.8.5/131-mt-ospace-preserve-FLAGS_FOR_TARGET.patch
A patches/gcc/4.9.3/130-pr43538.patch
A patches/gcc/4.9.3/131-mt-ospace-preserve-FLAGS_FOR_TARGET.patch
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
Merge pull request #376 from jcmvbkbc/gcc-flags-for-target
Pass CFLAGS_FOR_TARGET/CXXFLAGS_FOR_TARGET for libstdc++ in baremetal build
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/d7339f50a2e8...a41b269af600
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-03-15 16:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56e83f4929e1b_22c13fd4e6be729c2273e2@hookshot-fe1-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).