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] Rename placed_size to kind
Date: Thu, 03 Nov 2016 15:46:00 -0000	[thread overview]
Message-ID: <579c6ad9830058ccebf9c592d692c25fac6285c7@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 579c6ad9830058ccebf9c592d692c25fac6285c7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 579c6ad9830058ccebf9c592d692c25fac6285c7

Rename placed_size to kind

This patch renames placed_size to kind.

gdb:

2016-11-03  Yao Qi  <yao.qi@linaro.org>

	* breakpoint.h (struct bp_target_info) <placed_size>: Remove.
	<kind>: New field.
	Update all users.


             reply	other threads:[~2016-11-03 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 15:46 sergiodj+buildbot [this message]
2016-11-03 15:46 ` *** COMPILATION FAILED *** Failures on Debian-i686-native-extended-gdbserver, branch master *** BREAKAGE *** sergiodj+buildbot
2016-11-03 15:49 ` *** COMPILATION FAILED *** Failures on Debian-i686, " sergiodj+buildbot
2016-11-03 18:23 ` *** COMPILATION FAILED *** Failures on Fedora-i686, " sergiodj+buildbot
2016-11-03 18:36 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2016-11-03 19:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-11-03 20:09 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-11-03 20:34 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-09 20:06 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-11-09 20:51 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-10 13:22 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-10 13:23 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-11-10 13:23 ` 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=579c6ad9830058ccebf9c592d692c25fac6285c7@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).