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: replace Reg8, Reg16, Reg32, and Reg64 Date: Mon, 18 Dec 2017 08:56:00 -0000 [thread overview] Message-ID: <dc821c5f9ae5208ad1ec438718f75e224f856deb@gdb-build> (raw) *** TEST RESULTS FOR COMMIT dc821c5f9ae5208ad1ec438718f75e224f856deb *** Author: Jan Beulich <jbeulich@novell.com> Branch: master Commit: dc821c5f9ae5208ad1ec438718f75e224f856deb x86: replace Reg8, Reg16, Reg32, and Reg64 Use a combination of a single new Reg bit and Byte, Word, Dword, or Qword instead. Besides shrinking the number of operand type bits this has the benefit of making register handling more similar to accumulator handling (a generic flag is being accompanied by a "size qualifier"). It requires, however, to split a few insn templates, as it is no longer correct to have combinations like Reg32|Reg64|Byte. This slight growth in size will hopefully be outweighed by this change paving the road for folding a presumably much larger number of templates later on.
next reply other threads:[~2017-12-18 8:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-18 8:56 sergiodj+buildbot [this message] 2017-12-18 8:56 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2017-12-18 8:58 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-12-18 9:17 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-18 9:19 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-12-18 9:19 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-12-18 9:31 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-18 9:36 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-18 10:15 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-12-18 10:50 ` 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=dc821c5f9ae5208ad1ec438718f75e224f856deb@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).