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] x86/Intel: correct disassembly of fsub*/fdiv* Date: Thu, 08 Mar 2018 08:06:00 -0000 [thread overview] Message-ID: <d53e6b98a2599ba4ce6ad14f711b76e44a32eea5@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d53e6b98a2599ba4ce6ad14f711b76e44a32eea5 *** Author: Jan Beulich <jbeulich@novell.com> Branch: master Commit: d53e6b98a2599ba4ce6ad14f711b76e44a32eea5 x86/Intel: correct disassembly of fsub*/fdiv* fsub/fsubr/fsubp/fsubrp as well as fdiv/fdivr/fdivp/fdivrp disassembly should match (a) the Intel SDM and (b) respective input fed to gas (both of course with the exception of when we intentionally convert bogus insns, accompanied by a warning).
next reply other threads:[~2018-03-08 8:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-08 8:06 sergiodj+buildbot [this message] 2018-03-08 8:06 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-03-08 9:26 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-08 9:27 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-08 9:27 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-03-08 9:36 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-03-08 9:49 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-08 9:53 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-08 10:10 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-03-08 10:11 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-08 10:39 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-08 11:06 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " 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=d53e6b98a2599ba4ce6ad14f711b76e44a32eea5@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: linkBe 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).