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] Remove write-only assignment in rs6000-tdep.c
Date: Thu, 21 Dec 2017 02:01:00 -0000 [thread overview]
Message-ID: <27e9ff87a627614fda7ddd89ddef745de5e988bb@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 27e9ff87a627614fda7ddd89ddef745de5e988bb ***
Author: Uros Bizjak <ubizjak@gmail.com>
Branch: master
Commit: 27e9ff87a627614fda7ddd89ddef745de5e988bb
Remove write-only assignment in rs6000-tdep.c
The result of this memory read is never used, so it can be removed.
gdb/ChangeLog:
* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Remove
write-only assignment to "insn" variable.
next reply other threads:[~2017-12-21 2:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 2:01 sergiodj+buildbot [this message]
2017-12-21 2:01 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2017-12-21 2:04 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-12-21 2:08 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-12-21 2:17 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-21 2:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-12-21 2:25 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-12-21 2:41 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-12-21 2:48 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-12-21 2:58 ` Failures on Ubuntu-AArch64-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=27e9ff87a627614fda7ddd89ddef745de5e988bb@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).