public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Pop, Sebastian" <spop@amazon.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
	Christophe Lyon <christophe.lyon@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [aarch64] Backport missing NEON intrinsics to GCC8
Date: Wed, 16 Sep 2020 15:34:37 +0000	[thread overview]
Message-ID: <E225D374-C949-435A-9D61-B8597C8B07E2@amazon.com> (raw)

Thanks Christophe for reporting the errors.

On 9/16/20, 7:45 AM, "Kyrylo Tkachov" <Kyrylo.Tkachov@arm.com> wrote:
> > The new tests vld1x3 and vld1x4 fail on arm, I am seeing new failures
> > on gcc-8 and gcc-9 branches
> > after r8-10451, r8-10452 and r9-8874.
> > Is that expected/fixed later in the backport series?
> > (on the release branches, my validations are running for every commit)
>
> Hmm, IIRC they're not implemented for arm IIRC so they should be xfailed or skipped on arm.

When I look at the log for those files there are no additions.
Why does arm execute tests from gcc.target/aarch64/ on gcc9 and gcc8?
Why arm does not fail with those extra tests on gcc10 and on master?
I'm still trying to figure out how to properly fix this.

Thanks,
Sebastian


             reply	other threads:[~2020-09-16 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 15:34 Pop, Sebastian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-16  5:21 Pop, Sebastian
2020-09-16 12:42 ` Christophe Lyon
2020-09-16 12:44   ` Kyrylo Tkachov
2020-09-11 19:54 Pop, Sebastian
2020-09-15 12:45 ` Kyrylo Tkachov

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=E225D374-C949-435A-9D61-B8597C8B07E2@amazon.com \
    --to=spop@amazon.com \
    --cc=Kyrylo.Tkachov@arm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.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).