From: Christophe Lyon <christophe.lyon@linaro.org>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: One more path to fix PR70478
Date: Tue, 11 Apr 2017 07:30:00 -0000 [thread overview]
Message-ID: <CAKdteOY9RhmDU1K6ZxchhNhavbdjqndYq6GX3N=A3ombMW=K9w@mail.gmail.com> (raw)
In-Reply-To: <930934bd-0341-6607-3d7e-96c34cebbabc@redhat.com>
Hi Vladimir,
On 10 April 2017 at 17:05, Vladimir Makarov <vmakarov@redhat.com> wrote:
> This is the second try to fix
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70478
>
> The first try patch triggered a latent bug and broke one Fortran testcase
> on x86-64.
>
> The patch was successfully bootstrapped on x86-64 and tested on x86-64,
> ppc64, and aarch64.
>
> Committed as rev. 246808.
>
>
This patch causes regression on arm*hf configurations:
Executed from: gcc.target/arm/arm.exp
gcc.target/arm/armv8_2-fp16-move-1.c scan-assembler-times ldrh\\tr[0-9]+ 2
gcc.target/arm/armv8_2-fp16-move-1.c scan-assembler-times strh\\tr[0-9]+ 2
gcc.target/arm/armv8_2-fp16-move-1.c scan-assembler-times
vld1\\.16\\t{d[0-9]+\\[[0-9]+\\]}, \\[r[0-9]+\\] 2
gcc.target/arm/armv8_2-fp16-move-1.c scan-assembler-times
vmov\\.f16\\tr[0-9]+, s[0-9]+ 4
gcc.target/arm/armv8_2-fp16-move-1.c scan-assembler-times
vmov\\.f16\\ts[0-9]+, r[0-9]+ 4
gcc.target/arm/armv8_2-fp16-move-1.c scan-assembler-times
vst1\\.16\\t{d[0-9]+\\[[0-9]+\\]}, \\[r[0-9]+\\] 2
See http://people.linaro.org/~christophe.lyon/cross-validation/gcc/trunk/246809/report-build-info.html
Is it just a matter of adjusting the testcases? (note that there is no
regression when forcing either:
-march=armv5t
-mthumb/-march=armv8-a/-mfpu=crypto-neon-fp-armv8/-mfloat-abi=hard
in the runtestflags.
I would have to re--run the build/test manually to get the generated
code, let me know if it's needed.
Thanks,
Christophe
next prev parent reply other threads:[~2017-04-11 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:05 Vladimir Makarov
2017-04-11 7:30 ` Christophe Lyon [this message]
2017-04-11 15:42 ` Vladimir Makarov
2017-04-11 16:26 ` Christophe Lyon
2017-04-11 16:31 ` Ramana Radhakrishnan
2017-04-11 17:27 ` Vladimir Makarov
2017-04-11 19:43 ` Vladimir Makarov
2017-04-12 6:10 ` 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='CAKdteOY9RhmDU1K6ZxchhNhavbdjqndYq6GX3N=A3ombMW=K9w@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@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).