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: x87-related adjustments
Date: Thu, 26 Apr 2018 10:29:00 -0000	[thread overview]
Message-ID: <0e0eea782025d92f894f6d132aae2507c6a90a7b@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 0e0eea782025d92f894f6d132aae2507c6a90a7b ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 0e0eea782025d92f894f6d132aae2507c6a90a7b

x86: x87-related adjustments

Neither 287 wrt 8087 nor 387 wrt 287 are proper supersets - in each case
some insns get removed from the ISA (they become NOPs, but code intended
for newer co-processors should not use them).

Furthermore with .no87, ST should not be recognized as a register name.


             reply	other threads:[~2018-04-26 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 10:29 sergiodj+buildbot [this message]
2018-04-26 10:33 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot
2018-04-26 10:49 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-04-26 10:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-26 11:16 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-04-26 11:41 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2018-04-27  0:26 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-27  1:03 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-04-27  1:51 ` Failures on Ubuntu-AArch32-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=0e0eea782025d92f894f6d132aae2507c6a90a7b@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).