From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 69c2ca: add RISC-V architecture support
Date: Mon, 20 Nov 2017 05:44:00 -0000 [thread overview]
Message-ID: <5a126bb882c8c_39e13fb8c910bc44428f1@hookshot-fe-92cdb05.cp1-iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 69c2ca97fbb1137d0b5717de47fd91a917811818
https://github.com/crosstool-ng/crosstool-ng/commit/69c2ca97fbb1137d0b5717de47fd91a917811818
Author: Antony Pavlov <antonynpavlov@gmail.com>
Date: 2017-11-19 (Sun, 19 Nov 2017)
Changed paths:
A config/arch/riscv.in
A scripts/build/arch/riscv.sh
Log Message:
-----------
add RISC-V architecture support
Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Commit: cc342748ce231a860d46300363a789cfc330c002
https://github.com/crosstool-ng/crosstool-ng/commit/cc342748ce231a860d46300363a789cfc330c002
Author: Antony Pavlov <antonynpavlov@gmail.com>
Date: 2017-11-19 (Sun, 19 Nov 2017)
Changed paths:
A samples/riscv32-unknown-elf/crosstool.config
A samples/riscv32-unknown-elf/reported.by
Log Message:
-----------
add a bare metal RISC-V sample
Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
Commit: 8c581c25042301ee0ec4169e6fc3213d7f8cb35b
https://github.com/crosstool-ng/crosstool-ng/commit/8c581c25042301ee0ec4169e6fc3213d7f8cb35b
Author: Alexey Neyman <stilor@att.net>
Date: 2017-11-19 (Sun, 19 Nov 2017)
Changed paths:
A config/arch/riscv.in
A samples/riscv32-unknown-elf/crosstool.config
A samples/riscv32-unknown-elf/reported.by
A scripts/build/arch/riscv.sh
Log Message:
-----------
Merge pull request #868 from frantony/riscv
add RISC-V architecture support
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/0b1595acf2cc...8c581c250423
reply other threads:[~2017-11-20 5:44 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=5a126bb882c8c_39e13fb8c910bc44428f1@hookshot-fe-92cdb05.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).