public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions
Date: Wed, 16 Mar 2016 16:29:00 -0000 [thread overview]
Message-ID: <cc9333013723880949a1e07a3e04bdbc1a3c3032@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT cc9333013723880949a1e07a3e04bdbc1a3c3032 ***
Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: cc9333013723880949a1e07a3e04bdbc1a3c3032
[ARM] Support ARMv8.2 FP16 simd instructions
gas/
* config/tc-arm.c (N_S_32): New.
(N_F_16_32): Likewise.
(N_SUF_32): Support N_F16.
(N_IF_32): Likewise.
(neon_dyadic_misc): Likewise.
(do_neon_cmp): Likewise.
(do_neon_cmp_inv): Likewise.
(do_neon_mul): Likewise.
(do_neon_fcmp_absolute): Likewise.
(do_neon_step): Likewise.
(do_neon_abs_neg): Likewise.
(CVT_FLAVOR_VAR): Likewise.
(do_neon_cvt_1): Likewise.
(do_neon_recip_est): Likewise.
(do_vmaxnm): Likewise.
(do_vrint_1): Likewise.
(neon_check_type): Check architecture support for FP16 extension.
(insns): Update comments.
* testsuite/gas/arm/armv8-2-fp16-simd.s: New test source.
* testsuite/gas/arm/armv8-2-fp16-simd.d: New testcase for arm mode.
* testsuite/gas/arm/armv8-2-fp16-simd-thumb.d: Likewise for thumb mode.
* testsuite/gas/arm/armv8-2-fp16-simd-warning.d: New rejection test for
arm mode.
* testsuite/gas/arm/armv8-2-fp16-simd-warning-thumb.d: Likewise for
thumb mode.
* testsuite/gas/arm/armv8-2-fp16-simd-warning.l: New expected rejection
error file.
opcode/
* arm-dis.c (neon_opcodes): Support new FP16 instructions.
next reply other threads:[~2016-03-16 16:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 16:29 sergiodj+buildbot [this message]
2016-03-16 16:39 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot
2016-03-16 16:41 ` Failures on Debian-i686, " sergiodj+buildbot
2016-03-16 16:43 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-03-16 16:44 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-03-16 16:48 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-03-16 16:55 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-03-16 16:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-16 16:56 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-03-16 16:59 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-03-16 17:00 ` Failures on Fedora-x86_64-cxx-build-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2016-03-16 17:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2016-03-16 17:23 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-03-16 17:26 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-16 17:28 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-16 17:32 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2016-03-16 17:40 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2016-03-16 17:48 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-03-16 18:27 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-03-16 18:49 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-16 19:09 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-03-16 19:36 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-03-16 19:42 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-03-17 1:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-17 9:39 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-03-17 10:58 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
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=cc9333013723880949a1e07a3e04bdbc1a3c3032@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@sourceware.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).