From: Nelson Chu <nelson.chu@sifive.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org,
jimw@sifive.com, andrew.burgess@embecosm.com,
kito.cheng@sifive.com, palmer@dabbelt.com, andrew@sifive.com
Subject: [PATCH v2 0/3] RISC-V: The series to supporting mapping symbols
Date: Fri, 9 Jul 2021 00:28:22 -0700 [thread overview]
Message-ID: <20210709072825.13709-1-nelson.chu@sifive.com> (raw)
Hi Guys,
See in advance what are the difference with v1,
* Support data mapping symbols with the data size, if they are added
by cons_worker, e.g. $d2, $d4.
* Support alignment mapping symbols, $a and $a1. If the instructions
are used for alignment, then we dump them with the prefix align.<insn>.
* Since the above two new features, we don't need to record all
mapping symbols of the fragments. Instead, only record the
first and last mapping symbols should be enough.
* Extend .insn directive to support hardcode encoding.
These are all binutils changes, but not sure if the changes will break
the gdb disassembler. Unfortunately I am not familiar with gdb, hope
gdb experts can give some suggestions, or warnings if something may be
broken.
Besides, the binutils readelf testcases in the second patch are affected
by the first patch, so I send them as the same series. But in fact the
first patch can be regarded as an independent issue. Therefore, I think
we can commit it separately first, if everything looks good.
The elf/linux toolchain regressions all passed, looks fine so far.
Thanks
Nelson
next reply other threads:[~2021-07-09 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 7:28 Nelson Chu [this message]
2021-07-09 7:28 ` [PATCH v2 1/3] RISC-V: Enable elf attributes when default configure option isn't set Nelson Chu
2021-07-09 8:00 ` Kito Cheng
2021-07-13 7:07 ` Nelson Chu
2021-07-13 20:38 ` Palmer Dabbelt
2021-07-15 1:47 ` Nelson Chu
2022-02-25 13:57 ` Sebastian Huber
2021-07-09 7:28 ` [PATCH v2 2/3] RISC-V: PR27916, Support mapping symbols Nelson Chu
2021-07-15 15:16 ` Palmer Dabbelt
2021-07-16 2:58 ` Nelson Chu
2021-07-09 7:28 ` [PATCH v2 3/3] RISC-V: PR27916, Extend .insn directive to support hardcode encoding Nelson Chu
2021-07-09 8:01 ` Kito Cheng
2021-07-14 20:38 ` 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=20210709072825.13709-1-nelson.chu@sifive.com \
--to=nelson.chu@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jimw@sifive.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
/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).