From: Richard Henderson <richard.henderson@linaro.org>
To: Taylor Simpson <tsimpson@quicinc.com>, qemu-devel@nongnu.org
Cc: philmd@linaro.org, ale@rev.ng, anjo@rev.ng, bcain@quicinc.com,
quic_mathbern@quicinc.com
Subject: Re: [PATCH v2 0/9] Hexagon (target/hexagon) New architecture support
Date: Fri, 28 Apr 2023 22:44:46 +0100 [thread overview]
Message-ID: <3ee5308b-b25e-813b-4223-78aef99e93de@linaro.org> (raw)
In-Reply-To: <20230427224057.3766963-1-tsimpson@quicinc.com>
On 4/27/23 23:40, Taylor Simpson wrote:
> Add support for new Hexagon architecture versions v68/v69/v71/v73
Where can one find docs for this?
The latest Hexagon SDK I can find is 3.5, which still ends at v67.
r~
next prev parent reply other threads:[~2023-04-28 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 22:40 [PATCH v2 0/9] Hexagon (target/hexagon) New architecture support Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 1/9] Hexagon (target/hexagon) Add support for v68/v69/v71/v73 Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 2/9] Hexagon (target/hexagon) Add v68 scalar instructions Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 3/9] Hexagon (tests/tcg/hexagon) Add v68 scalar tests Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 4/9] Hexagon (target/hexagon) Add v68 HVX instructions Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 5/9] Hexagon (tests/tcg/hexagon) Add v68 HVX tests Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 6/9] Hexagon (target/hexagon) Add v69 HVX instructions Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 7/9] Hexagon (tests/tcg/hexagon) Add v69 HVX tests Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 8/9] Hexagon (target/hexagon) Add v73 scalar instructions Taylor Simpson
2023-04-27 22:40 ` [PATCH v2 9/9] Hexagon (tests/tcg/hexagon) Add v73 scalar tests Taylor Simpson
2023-04-28 21:44 ` Richard Henderson [this message]
2023-04-29 19:56 ` [PATCH v2 0/9] Hexagon (target/hexagon) New architecture support Taylor Simpson
2023-05-10 20:58 ` Taylor Simpson
2023-05-11 5:17 ` Richard Henderson
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=3ee5308b-b25e-813b-4223-78aef99e93de@linaro.org \
--to=richard.henderson@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bcain@quicinc.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=tsimpson@quicinc.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 NNTP newsgroup(s).