From: James Greenhalgh <james.greenhalgh@arm.com>
To: Kugan <kugan.vivekanandarajah@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [AARCH64] Add missing entries in iterator vwcore
Date: Tue, 06 Oct 2015 08:15:00 -0000 [thread overview]
Message-ID: <20151006081546.GA2307@arm.com> (raw)
In-Reply-To: <5613268A.6010201@linaro.org>
On Tue, Oct 06, 2015 at 02:40:26AM +0100, Kugan wrote:
>
>
> On 05/10/15 21:33, James Greenhalgh wrote:
> > On Thu, Oct 01, 2015 at 09:41:20PM +0100, Kugan wrote:
> >> Hi,
> >>
> >> In "aarch64_get_lane<mode>" operand 0 is VEL, so for %<vwcore>0,
> >> iterator vwcore should (?) support all the modes in VEL.
> >>
> >> Ran into following error with a local patch for an existing test case.
> >> However it can also be reproduced with the attached test case.
> >>
> >> fnction ???fn1???:
> >> t.c:25:1: internal compiler error: output_operand: invalid %-code
> >> }
> >> ^
> >> 0x8198fb output_operand_lossage(char const*, ...)
> >> ../../base/gcc/final.c:3417
> >> 0x81a45b output_asm_insn(char const*, rtx_def**)
> >> ../../base/gcc/final.c:3782
> >> 0x81b9d3 output_asm_insn(char const*, rtx_def**)
> >> ../../base/gcc/final.c:2364
> >> 0x81b9d3 final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
> >> ../../base/gcc/final.c:3029
> >> 0x81be2b final(rtx_insn*, _IO_FILE*, int)
> >> ../../base/gcc/final.c:2058
> >> 0x81c6e7 rest_of_handle_final
> >> ../../base/gcc/final.c:4449
> >> 0x81c6e7 execute
> >> ../../base/gcc/final.c:4524
> >>
> >>
> >> Attached patch fixes this. Bootstrapped and regression tested for
> >> aarch64-none-linux-gnu with no new regression. Is this OK for trunk?
> >>
> >> gcc/ChangeLog:
> >>
> >> 2015-10-02 Kugan Vivekanandarajah <kuganv@linaro.org>
> >>
> >> * config/aarch64/iterators.md: Add missing core element mode for
> >> mode.
> >>
> >> gcc/testsuite/ChangeLog:
> >>
> >> 2015-10-02 Kugan Vivekanandarajah <kuganv@linaro.org>
> >>
> >> * gcc.target/aarch64/foo.c: New test.
> >>
> >
> > "foo.c" is not OK, please give this testcase a meaningful name.
> >
> Renamed the test case.
>
> Is this OK now?
It still doesn't quite look right. For one, the attribute causing the ICE
is "vwcore" not "vcore".
How about calling the test gcc.target/aarch64/get_lane_f16_1.c ?
> gcc/ChangeLog:
>
> 2015-10-06 Kugan Vivekanandarajah <kuganv@linaro.org>
>
> * config/aarch64/iterators.md: Add missing core element mode for
> mode.
This ChangeLog entry is incomplete:
* config/aarch64/iterators.md (vwcore): Add missing cases for
V4HF/V8HF modes.
>
> gcc/testsuite/ChangeLog:
>
> 2015-10-06 Kugan Vivekanandarajah <kuganv@linaro.org>
>
> * gcc.target/aarch64/vcore_ice_test.c: New test.
>
Please remeber to also update this with the new test name I suggested
above.
OK with those changes.
Thanks,
James
prev parent reply other threads:[~2015-10-06 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:41 Kugan
2015-10-05 10:33 ` James Greenhalgh
2015-10-06 1:40 ` Kugan
2015-10-06 8:15 ` James Greenhalgh [this message]
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=20151006081546.GA2307@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kugan.vivekanandarajah@linaro.org \
/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).