From: Alex Huang <huangalex409@gmail.com>
To: jacob navia <naviajacob7@gmail.com>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Mystery instructions
Date: Tue, 23 Jan 2024 09:16:07 -0500 [thread overview]
Message-ID: <13BC6943-32E4-43F3-8AD6-6F40CA84DB00@gmail.com> (raw)
In-Reply-To: <B5487F99-A25A-48FB-A4E9-9C0842BE21CF@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
Hi,
These instructions looks to be part of the T-head vendor extension instruction set. With the spec here https://github.com/T-head-Semi/thead-extension-spec.
Best regards
Alex
> On Jan 23, 2024, at 8:42 AM, jacob navia via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hi
> The GNU assembler supports two instructions for the T-Head risk machines called:
>
> th.ipop
> th.ipush
>
> With no arguments. These instructions (they are no macros or aliases) are UNDOCUMENTED in the T-Head instruction manuals that I have, and a google search yields absolutely nothing.
>
> Can anyone here point me to some documentation that describes what these instructions do?
>
> Thanks in advance.
next prev parent reply other threads:[~2024-01-23 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 20:16 jacob navia
2024-01-23 14:16 ` Alex Huang [this message]
2024-01-26 17:28 ` jacob navia
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=13BC6943-32E4-43F3-8AD6-6F40CA84DB00@gmail.com \
--to=huangalex409@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=naviajacob7@gmail.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).