public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: Jiong Wang <jiong.wang@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
		Richard Henderson <rth@redhat.com>
Subject: Re: [PATCH, AARCH64] Fix ICE in CCMP (PR64015)
Date: Sun, 18 Jan 2015 21:26:00 -0000	[thread overview]
Message-ID: <CAKdteOZ39W=gvVJykhMB_GVCc7z3VRzeqJ+2oX77O8qmVj5eFw@mail.gmail.com> (raw)
In-Reply-To: <CAFqB+PxD1njS_8Bah5trq9F_neZDuEn9nPFz2FxGP3xnYbhnLQ@mail.gmail.com>

On 16 January 2015 at 11:54, Marcus Shawcroft
<marcus.shawcroft@gmail.com> wrote:
> On 15 January 2015 at 18:18, Richard Henderson <rth@redhat.com> wrote:
>> On 12/15/2014 12:41 AM, Zhenqiang Chen wrote:
>>> +(define_expand "cmp<mode>"
>>> +  [(set (match_operand 0 "cc_register" "")
>>> +        (match_operator:CC 1 "aarch64_comparison_operator"
>>> +         [(match_operand:GPI 2 "register_operand" "")
>>> +          (match_operand:GPI 3 "aarch64_plus_operand" "")]))]
>>> +  ""
>>> +  "
>>> +  operands[1] = gen_rtx_fmt_ee (COMPARE, SELECT_CC_MODE (GET_CODE (operands[1]),
>>> +                                                      operands[2],
>>> +                                                      operands[3]),
>>> +                              operands[2], operands[3]);
>>> +  "
>>> +)
>>
>> Use { } not "" for the C portion.
>>
>> Otherwise ok.
>
> Jiong... this is fine with me. /Marcus

Jiong,

I have noticed regressions on aarch64 after this patch:

See: http://abe.tcwglab.linaro.org/logs/validations/cross-validation/gcc/trunk/219723/report-build-info.html
Passed now fails          [PASS => FAIL]:
  gcc.target/aarch64/test_frame_1.c scan-assembler-times ldr\tx30,
\\[sp\\], [0-9]+ 3
  gcc.target/aarch64/test_frame_2.c scan-assembler-times ldp\tx19,
x30, \\[sp\\], [0-9]+ 2
  gcc.target/aarch64/test_frame_4.c scan-assembler-times ldp\tx19,
x30, \\[sp\\], [0-9]+ 2
  gcc.target/aarch64/test_frame_6.c scan-assembler-times ldr\tx30,
\\[sp\\], [0-9]+ 3
  gcc.target/aarch64/test_frame_7.c scan-assembler-times ldp\tx19,
x30, \\[sp\\], [0-9]+ 2

Is this expected?

Thanks,

Christophe.

  reply	other threads:[~2015-01-18 19:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24  8:21 Zhenqiang Chen
2014-11-24  8:21 ` Andrew Pinski
2014-11-24  9:49 ` Richard Henderson
2014-11-25  9:11   ` Zhenqiang Chen
2014-11-25  9:37     ` Richard Henderson
2014-11-26 10:00       ` Zhenqiang Chen
2014-11-28 17:28         ` Richard Henderson
2014-12-12  7:52       ` Zhenqiang Chen
2014-12-12 19:25         ` Richard Henderson
2014-12-15  9:05           ` Zhenqiang Chen
2015-01-15 15:40             ` Jiong Wang
2015-01-15 18:28             ` Richard Henderson
2015-01-16 11:01               ` Marcus Shawcroft
2015-01-18 21:26                 ` Christophe Lyon [this message]
2015-01-18 22:12                   ` Andrew Pinski
2015-01-18 23:29                     ` Christophe Lyon

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='CAKdteOZ39W=gvVJykhMB_GVCc7z3VRzeqJ+2oX77O8qmVj5eFw@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jiong.wang@arm.com \
    --cc=marcus.shawcroft@gmail.com \
    --cc=rth@redhat.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).