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] gas/arc: Handle multiple arc_opcode chains for same mnemonic Date: Thu, 07 Apr 2016 17:52:00 -0000 [thread overview] Message-ID: <1328504b287b2c284419d989e0d05e7d6d3ffa59@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 1328504b287b2c284419d989e0d05e7d6d3ffa59 *** Author: Andrew Burgess <andrew.burgess@embecosm.com> Branch: master Commit: 1328504b287b2c284419d989e0d05e7d6d3ffa59 gas/arc: Handle multiple arc_opcode chains for same mnemonic This commit completes support for having multiple instructions with the same mnemonic in non-contiguous blocks within the arc_opcodes table. The commit adds an iterator mechanism for the arc_opcode_hash_entry structure, which is then used in find_opcode_match to consider all arc_opcode entries with the same mnemonic, even when these instructions are stored in non-contiguous blocks. I extend the comment on the arc_opcodes table to discuss how entries within the table are organised, and to mention how instructions can be split into multiple groups if needed, but that the table is still searched in table order. There should be no user visible changes after this commit. gas/ChangeLog: * config/tc-arc.c (struct arc_opcode_hash_entry_iterator): New structure. (arc_opcode_hash_entry_iterator_init): New function. (arc_opcode_hash_entry_iterator_next): New function. (find_opcode_match): Iterate over all arc_opcode entries referenced by the arc_opcode_hash_entry passed in as a parameter. opcodes/ChangeLog: * arc-opc.c (arc_opcodes): Extend comment to discus table layout.
next reply other threads:[~2016-04-07 17:52 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-07 17:52 sergiodj+buildbot [this message] 2016-04-07 17:52 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2016-04-07 18:03 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-04-07 18:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-04-07 18:55 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-04-07 19:22 ` Failures on Debian-i686, " sergiodj+buildbot 2016-04-07 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-07 19:47 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-04-07 19:55 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2016-04-07 21:54 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-04-07 22:33 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-04-08 0:06 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2016-04-08 0:26 ` Failures on Fedora-ppc64le-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=1328504b287b2c284419d989e0d05e7d6d3ffa59@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).