From: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
"noamca@mellanox.com" <noamca@mellanox.com>,
Francois Bedard <Francois.Bedard@synopsys.com>
Subject: RE: [PATCH 1/6] gas/arc: Modify structure used to hold opcodes
Date: Thu, 07 Apr 2016 13:08:00 -0000 [thread overview]
Message-ID: <098ECE41A0A6114BB2A07F1EC238DE896617D71D@DE02WEMBXB.internal.synopsys.com> (raw)
In-Reply-To: <20160407125045.GN25615@embecosm.com>
> Now I'm _adding_ extension instructions. If one of my extensions
> instructions happened to be an addition instruction that took 4
> registers, such that DST = SRC1 + SRC2 + SRC3, then this is clearly
> _not_ part of the core ARC700 architecture, but could live quite
> happily as an extension to ARC700.
My apologizes, I thought you would like to overwrite the current mnemonic syntax. I agree we can have extra syntax for cases which are like the one you pointed out.
> In the end I placed the comment into opcodes/arc-opc.c, at the head of
> the arc_opcodes table. I figured that anyone interested in adding new
> instructions would go there first, and any comment there was most
> likely to be found / read.
Nice.
Please go ahead. I am waiting for your patches to be upstreamed, as I have three patches which I would like to upstream after your commit (support for .extInstruction pseudo-ops).
Thanks,
Claudiu
next prev parent reply other threads:[~2016-04-07 13:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 22:51 Andrew Burgess
2016-04-02 22:51 ` [PATCH 6/6] arc/nps400: Add new control instructions Andrew Burgess
2016-04-04 7:52 ` Claudiu Zissulescu
2016-04-05 14:26 ` Nick Clifton
2016-04-02 22:51 ` [PATCH 3/6] gas/arc: Additional work to support multiple arc_opcode chains Andrew Burgess
2016-04-02 22:51 ` [PATCH 2/6] gas/arc: Remove preprocess_operands function Andrew Burgess
2016-04-05 14:23 ` Nick Clifton
2016-04-02 22:51 ` [PATCH 4/6] gas/arc: Handle multiple arc_opcode chains for same mnemonic Andrew Burgess
2016-04-02 22:51 ` [PATCH 5/6] gas/arc: Allow greater range of characters into flag names Andrew Burgess
2016-04-04 7:52 ` Claudiu Zissulescu
2016-04-05 14:25 ` Nick Clifton
2016-04-04 8:22 ` [PATCH 1/6] gas/arc: Modify structure used to hold opcodes Claudiu Zissulescu
2016-04-04 9:10 ` Andrew Burgess
2016-04-04 14:45 ` Claudiu Zissulescu
2016-04-07 12:51 ` Andrew Burgess
2016-04-07 13:08 ` Claudiu Zissulescu [this message]
2016-04-07 15:34 ` Nick Clifton
2016-04-07 12:57 ` [PATCHv2 2/4] gas/arc: Additional work to support multiple arc_opcode chains Andrew Burgess
2016-04-07 13:14 ` Claudiu Zissulescu
2016-04-07 15:36 ` Nick Clifton
2016-04-07 12:57 ` [PATCHv2 0/4] arc/nps: Add pipeline control instructions Andrew Burgess
2016-04-07 12:57 ` [PATCHv2 3/4] gas/arc: Handle multiple arc_opcode chains for same mnemonic Andrew Burgess
2016-04-07 13:16 ` Claudiu Zissulescu
2016-04-07 15:37 ` Nick Clifton
2016-04-07 12:57 ` [PATCHv2 4/4] arc/nps400: Add new instructions Andrew Burgess
2016-04-07 13:18 ` Claudiu Zissulescu
2016-04-07 15:38 ` Nick Clifton
2016-04-07 12:57 ` [PATCHv2 1/4] gas/arc: Modify structure used to hold opcodes Andrew Burgess
2016-04-07 13:10 ` Claudiu Zissulescu
2016-04-07 15:35 ` Nick Clifton
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=098ECE41A0A6114BB2A07F1EC238DE896617D71D@DE02WEMBXB.internal.synopsys.com \
--to=claudiu.zissulescu@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=andrew.burgess@embecosm.com \
--cc=binutils@sourceware.org \
--cc=noamca@mellanox.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).