From: Joern Wolfgang Rennecke <gnu@amylaar.uk>
To: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Francois Bedard <Francois.Bedard@synopsys.com>,
"jeremy.bennett@embecosm.com" <jeremy.bennett@embecosm.com>
Subject: Re: [PATCH 1/2][ARC] Add support for ARCv2 CPUs
Date: Tue, 10 Nov 2015 14:01:00 -0000 [thread overview]
Message-ID: <5641F8A8.5090503@amylaar.uk> (raw)
In-Reply-To: <098ECE41A0A6114BB2A07F1EC238DE896616912A@de02wembxa.internal.synopsys.com>
On 30/10/15 11:19, Claudiu Zissulescu wrote:
> Hi,
>
> Please find the updated patch. I will defer the secondary reload optimization which will use the ld instructions with LIMM, for the time being.
Apart from the gen_compare_reg change, the patch is OK.
If the v2 support mostly works like support for the other subtargets,
you may check it in without the gen_compare_reg
change.
If that change is required because of particular code paths taken with
the v2 port, you may check in the whole patch.
The operand-swapping in gen_compare_reg was not expected to be triggered
when re-generating a comparison,
as comparisons gleaned from existing instructions are supposed to
already have the operands in the right order.
Do you have a testcase that triggers the assert independently from the
v2 support?
If you can name a pre-existing testcase to trigger the assert, the patch
is approved for separate check-in.
If you have a new testcase, is it in a form and of a legal status that
it can be submitted for inclusion in the
gcc regression tests suite?
next prev parent reply other threads:[~2015-11-10 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 11:21 Claudiu Zissulescu
2015-10-23 17:49 ` Joern Wolfgang Rennecke
2015-10-30 11:22 ` Claudiu Zissulescu
2015-11-10 14:01 ` Joern Wolfgang Rennecke [this message]
2015-11-10 17:02 ` Claudiu Zissulescu
2015-11-11 12:32 ` Claudiu Zissulescu
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=5641F8A8.5090503@amylaar.uk \
--to=gnu@amylaar.uk \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeremy.bennett@embecosm.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).