From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] b06864: Pull in fixes for ARM v8m support in gcc 8.2.0
Date: Thu, 27 Sep 2018 21:42:00 -0000 [thread overview]
Message-ID: <5bad4edbef024_54922af7166fcec093029@hookshot-fe-7191cb1.cp1-iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: b06864f7df7fc1037f8002a64ba66296bdaf24d6
https://github.com/crosstool-ng/crosstool-ng/commit/b06864f7df7fc1037f8002a64ba66296bdaf24d6
Author: Kumar Gala <kumar.gala@linaro.org>
Date: 2018-09-27 (Thu, 27 Sep 2018)
Changed paths:
A packages/gcc/8.2.0/0020-ARM-fix-cmse.patch
A packages/gcc/8.2.0/0021-arm-Make-arm_cmse.h-C99-compatible.patch
Log Message:
-----------
Pull in fixes for ARM v8m support in gcc 8.2.0
There are some fixes to the cmse code in mainline gcc that we need to
build an embedded toolchain targetting Cortex-M cpus that support the
v8m extensions.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Commit: f7c2952419bd8aae95169ea1e95f6e327b28d62b
https://github.com/crosstool-ng/crosstool-ng/commit/f7c2952419bd8aae95169ea1e95f6e327b28d62b
Author: Alexey Neyman <stilor@att.net>
Date: 2018-09-27 (Thu, 27 Sep 2018)
Changed paths:
A packages/gcc/8.2.0/0020-ARM-fix-cmse.patch
A packages/gcc/8.2.0/0021-arm-Make-arm_cmse.h-C99-compatible.patch
Log Message:
-----------
Merge pull request #1037 from galak/gcc-8.2.0-arm-fixes
Pull in fixes for ARM v8m support in gcc 8.2.0
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/b82b8adb4410...f7c2952419bd
**NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
reply other threads:[~2018-09-27 21:42 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=5bad4edbef024_54922af7166fcec093029@hookshot-fe-7191cb1.cp1-iad.github.net.mail \
--to=stilor@att.net \
--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).