From: Palmer Dabbelt <palmer@dabbelt.com>
To: binutils@sourceware.org
To: Tristan Gingold <gingold@adacore.com>
Subject: binutils-2_28-branch: Assorted RISC-V Fixes
Date: Wed, 22 Mar 2017 23:04:00 -0000 [thread overview]
Message-ID: <20170322230408.8885-1-palmer@dabbelt.com> (raw)
Since 2.28 was released a few fixes have landed on master that I think are sane
for the 2.28 branch. The patches have better descriptions, but they are:
* Fixes to allow assembly of a half dozen or so compressed instructions.
* Debug info relocation fixes.
* Help text/documentation.
Are these OK for the 2.28 branch?
[PATCH 1/7] RISC-V: Fix [dis]assembly of srai/srli
[PATCH 2/7] RISC-V: Fix the offset of CFA relocation.
[PATCH 3/7] RISC-V: Fix DW_CFA_advance_loc relocation.
[PATCH 4/7] RISC-V: Define DWARF2_USE_FIXED_ADVANCE_PC.
[PATCH 5/7] RISC-V: Fix assembler for c.addi, rd can be x0
[PATCH 6/7] RISC-V: Fix assembler for c.li, c.andi and c.addiw
[PATCH 7/7] Sanitize RISC-V GAS help text, documentation
next reply other threads:[~2017-03-22 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 23:04 Palmer Dabbelt [this message]
2017-03-22 23:04 ` [PATCH 5/7] RISC-V: Fix assembler for c.addi, rd can be x0 Palmer Dabbelt
2017-03-22 23:04 ` [PATCH 6/7] RISC-V: Fix assembler for c.li, c.andi and c.addiw Palmer Dabbelt
2017-03-22 23:04 ` [PATCH 7/7] Sanitize RISC-V GAS help text, documentation Palmer Dabbelt
2017-03-22 23:04 ` [PATCH 2/7] RISC-V: Fix the offset of CFA relocation Palmer Dabbelt
2017-03-22 23:04 ` [PATCH 4/7] RISC-V: Define DWARF2_USE_FIXED_ADVANCE_PC Palmer Dabbelt
2017-03-22 23:04 ` [PATCH 3/7] RISC-V: Fix DW_CFA_advance_loc relocation Palmer Dabbelt
2017-03-22 23:04 ` [PATCH 1/7] RISC-V: Fix [dis]assembly of srai/srli Palmer Dabbelt
2017-03-23 10:53 ` binutils-2_28-branch: Assorted RISC-V Fixes gingold
2017-03-30 20:01 ` Palmer Dabbelt
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=20170322230408.8885-1-palmer@dabbelt.com \
--to=palmer@dabbelt.com \
--cc=binutils@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).