From: Richard Sandiford <richard.sandiford@arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH][armeb] PR 91060 gcc.c-torture/execute/scal-to-vec1.c fails since r272843
Date: Mon, 08 Jul 2019 09:06:00 -0000 [thread overview]
Message-ID: <mptv9wcsxqh.fsf@arm.com> (raw)
In-Reply-To: <CAKdteOY2Y-HNAMabBkKDo_t8gSyATTyyhvYDv8o3KScnJ5iZEQ@mail.gmail.com> (Christophe Lyon's message of "Mon, 8 Jul 2019 11:01:42 +0200")
Christophe Lyon <christophe.lyon@linaro.org> writes:
> Hi,
>
> This patch fixes PR 91060 where the lane ordering was no longer the
> right one (GCC's vs architecture's).
Sorry, we clashed :-)
I'd prefer to go with the version I attached to bugzilla just now.
Thanks,
Richard
next prev parent reply other threads:[~2019-07-08 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 9:04 Christophe Lyon
2019-07-08 9:06 ` Richard Sandiford [this message]
2019-07-08 9:10 ` Christophe Lyon
2019-07-10 10:20 ` Richard Sandiford
2019-07-10 11:25 ` Ramana Radhakrishnan
2019-07-08 9:09 ` Kyrill Tkachov
2019-07-08 9:16 ` 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=mptv9wcsxqh.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).