From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
Cc: Nick Clifton <nickc@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"Cupertino.Miranda@synopsys.com" <Cupertino.Miranda@synopsys.com>,
"noamca@mellanox.com" <noamca@mellanox.com>
Subject: Re: [PATCH 1/2] opcodes/arc: Add more nps instructions
Date: Thu, 21 Apr 2016 14:50:00 -0000 [thread overview]
Message-ID: <20160421145016.GQ6589@embecosm.com> (raw)
In-Reply-To: <098ECE41A0A6114BB2A07F1EC238DE8966188A87@de02wembxa.internal.synopsys.com>
* Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com> [2016-04-20 13:19:26 +0000]:
> Those patches:
> > >
> > > * testsuite/gas/arc/nps400-4.d: New file.
> > > * testsuite/gas/arc/nps400-4.s: New file.
> > > * testsuite/gas/arc/nps400-5.d: New file.
> > > * testsuite/gas/arc/nps400-5.s: New file.
> > >
> Together with nps400-6.s are currently failing. Are they also fixed by your latest approved patches?
I've retested with targets arceb-elf and arc-elf, and I'm not seeing
any failures now. Let me know if you're still seeing issues, or if
you're using a different target that is showing failures.
Thanks,
Andrew
next prev parent reply other threads:[~2016-04-21 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 16:36 [PATCH 0/2] [ARC] Two additional sets of nps400 instructions Andrew Burgess
2016-04-14 16:36 ` [PATCH 1/2] opcodes/arc: Add more nps instructions Andrew Burgess
2016-04-18 11:23 ` Nick Clifton
2016-04-20 13:19 ` Claudiu Zissulescu
2016-04-21 13:34 ` Andrew Burgess
2016-04-21 14:50 ` Andrew Burgess [this message]
2016-04-22 6:56 ` Claudiu Zissulescu
2016-04-14 16:36 ` [PATCH 2/2] opcodes/arc: Add yet " Andrew Burgess
2016-04-19 16:05 ` 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=20160421145016.GQ6589@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--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).