public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in
@ 2015-07-27 16:26 sergiodj+buildbot
  2015-07-27 16:26 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
                   ` (15 more replies)
  0 siblings, 16 replies; 3232+ messages in thread
From: sergiodj+buildbot @ 2015-07-27 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 206350da0f99b9a50fe6405613b3b05561a55aae ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 206350da0f99b9a50fe6405613b3b05561a55aae

Remove REMOTE_EXAMPLES from gdb/Makefile.in
I happen to see REMOTE_EXAMPLES isn't used anywhere, so this patch
removes it.

REMOTE_EXAMPLES was added in the following commit in 1991,

commit 86bbb439c8fa01fd55d6cbce102483a471ffd0c4
Author: John Gilmore <gnu@cygnus>
Date:   Fri May 3 19:57:13 1991 +0000

    There should be a Makefile in the cvs main directory, configured
    for "./config.gdb none", so that things like "make tags" and "make tar"
    will work.

and it was used like:

TARFILES = ${TAGFILES_MAINDIR} ${OTHERS} ${REMOTE_EXAMPLES}

However TARFILES was removed by the change latter in 1994,

Tue Aug 16 15:24:03 1994  Jim Kingdon  (kingdon@lioth.cygnus.com)

	* symtab.c (decode_line_1): If funfirstline and we get a
	non-LOC_BLOCK symbol (e.g. variable or type), then error().

	* Makefile.in (TARFILES, NONSRC, SFILES_STAND, SFILES_KGDB):
	Remove; unused.

Since then, REMOTE_EXAMPLES is not used any more.

gdb:

2015-07-27  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (REMOTE_EXAMPLES): Remove it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in warning/internal_error
@ 2016-04-12 20:57 sergiodj+buildbot
  2016-04-13 15:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5ac15402a894e87a118526a066880f596b3c78d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c5ac15402a894e87a118526a066880f596b3c78d

Use target_terminal_ours_for_output in warning/internal_error

We're only doing output here, so leave raw/cooked mode alone, as well
as the SIGINT handler.

And restore terminal settings, while at it.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* utils.c (vwarning, internal_vproblem): Use
	make_cleanup_restore_target_terminal and
	target_terminal_ours_for_output.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Decouple target_interrupt from all-stop/non-stop modes
@ 2016-04-12 23:43 sergiodj+buildbot
  2016-04-13  9:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 23:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e42de8c7f8e7326d284f8b53f3bd6971fbf6e7b7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e42de8c7f8e7326d284f8b53f3bd6971fbf6e7b7

Decouple target_interrupt from all-stop/non-stop modes

In non-stop mode, "interrupt" results in a "stop with no signal",
while in all-stop mode, it results in a remote interrupt request /
stop with SIGINT.  This is currently implemented in both the Linux and
remote target backends.  Move it to the core code instead, making
target_interrupt specifically always about "Interrupting as if with
Ctrl-C", just like it is documented.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* infcmd.c (interrupt_target_1): Call target_stop is in non-stop
	mode.
	* linux-nat.c (linux_nat_interrupt): Delete.
	(linux_nat_add_target): Don't install linux_nat_interrupt.
	* remote.c (remote_interrupt_ns): Change return type to void.
	Throw error if interrupting the target is not supported.
	(remote_interrupt): Don't call the remote_stop_ns/remote_stop_as.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ada-lang.c: Introduce type_as_string and use it
@ 2016-04-13  1:16 sergiodj+buildbot
  2016-04-13 12:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  1:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99bbb428d4412b79e59df321f9e83c13342e4612 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 99bbb428d4412b79e59df321f9e83c13342e4612

ada-lang.c: Introduce type_as_string and use it

A couple wrong things here

  - We should not use target_terminal_ours when all we want is output.
    We should use target_terminal_ours_for_output instead, which
    preserves raw/cooked terminal modes, and SIGINT forwarding.

  - Most importantly, relying on stderr output immediately preceding
    the error/exception print isn't correct.  The exception could be
    caught and handled, for example; MI frontends won't display the
    stderr part in an error dialog box.  Etc.

This commit introduces a type_as_string helper that allows building a
full error string including type info.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (type_as_string, type_as_string_and_cleanup): New
	functions.
	(ada_lookup_struct_elt_type): Use type_as_string_and_cleanup.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix inconsistent handling of EINTR in ser-*.c backends
@ 2016-04-13  2:05 sergiodj+buildbot
  2016-04-13 11:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  2:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75ee59252d49dffb017905125cdf826f89a6baf9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 75ee59252d49dffb017905125cdf826f89a6baf9

Fix inconsistent handling of EINTR in ser-*.c backends

- If serial->write_prim returns EINTR, ser_bas_write returns it to the
  caller.  This just looks wrong to me -- part of the output may have
  already been sent, and there's no way for the caller to know that,
  and thus no way for a caller to handle a partial write correctly.

- While ser-unix.c:ser_unix_read_prim retries on EINTR,
  ser-tcp.c:net_read_prim does not.

This commit moves EINTR handling to the ser_base_write and
ser_base_readchar level, so all serial backends (at least those that
use it) end up handling EINTR consistently.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* ser-base.c (fd_event): Retry read_prim on EINTR.
	(do_ser_base_readchar): Retry read_prim on EINTR.
	(ser_base_write): Retry write_prim on EINTR.
	* ser-unix.c (ser_unix_read_prim): Don't retry on EINTR here.
	(ser_unix_write_prim): Remove comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in exceptions.c
@ 2016-04-13  2:29 sergiodj+buildbot
  2016-04-13 13:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  2:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 481ac8c9bbbfc4b7506dfdb4a5b92b859d5c47d9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 481ac8c9bbbfc4b7506dfdb4a5b92b859d5c47d9

Use target_terminal_ours_for_output in exceptions.c

We're only doing output here, so leave raw/cooked mode alone, as well
as the SIGINT handler.

Restore terminal settings after output, while at it.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* exceptions.c (print_flush): Use target_terminal_ours_for_output
	instead of target_terminal_ours, and restore target terminal with
	a cleanup.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in MI
@ 2016-04-13  5:01 sergiodj+buildbot
  2016-04-13 17:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  5:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fe966540d6b748f825774868463003700f0c878 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5fe966540d6b748f825774868463003700f0c878

Use target_terminal_ours_for_output in MI

The MI code only does output, so leave raw/cooked mode alone, as well
as the SIGINT handler.  Restore terminal settings after output, while
at it.  Also, a couple events missed calling target_terminal_ours
before output, even.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* mi/mi-interp.c (mi_new_thread): Put
	target_terminal_ours_for_output in effect while outputting.
	(mi_thread_exit): Use target_terminal_ours_for_output instead of
	target_terminal_ours.
	(mi_record_changed, mi_inferior_added, mi_inferior_appeared)
	(mi_inferior_exit, mi_inferior_removed, mi_traceframe_changed)
	(mi_tsv_created, mi_tsv_deleted, mi_tsv_modified)
	(mi_breakpoint_created, mi_breakpoint_deleted)
	(mi_breakpoint_modified, mi_solib_loaded, mi_solib_unloaded)
	(mi_command_param_changed, mi_memory_changed)
	(report_initial_inferior): Use target_terminal_ours_for_output
	instead of target_terminal_ours.  Restore terminal settings.
	* mi/mi-main.c (mi_execute_command): Use
	target_terminal_ours_for_output instead of target_terminal_ours.
	Restore terminal settings.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in infcmd.c
@ 2016-04-13  5:12 sergiodj+buildbot
  2016-04-13 14:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  5:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8e3ef9dc4d803729a8f0e0cafb2c995b576c44e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f8e3ef9dc4d803729a8f0e0cafb2c995b576c44e

Use target_terminal_ours_for_output in infcmd.c

We're only doing output here, so leave raw/cooked mode alone, as well
as the SIGINT handler.

No need to restore terminal settings, we'll set inferior modes on the
following resume.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* infcmd.c (post_create_inferior, prepare_one_step): Use
	target_terminal_ours_for_output instead of target_terminal_ours.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] target remote: Don't rely on immediate_quit (introduce quit handlers)
@ 2016-04-13  5:54 sergiodj+buildbot
  2016-04-13 19:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  5:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 048094accce2110432bf7d44c34acc17865cf85a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 048094accce2110432bf7d44c34acc17865cf85a

target remote: Don't rely on immediate_quit (introduce quit handlers)

remote.c is the last user of immediate_quit.  It's relied on to
immediately break the initial remote connection sync up, if the user
does Ctrl-C, assuming that was because the target isn't responding.
At that stage, since the connection isn't synced yet, disconnecting is
the only safe thing to do.  This commit reworks that, to not rely on
throwing from the SIGINT signal handler.

So, this commit:

- Introduces the concept of a "quit handler".  This is used to
  override what does the QUIT macro do when the quit flag is set.

- Makes the "struct serial" reachar / write code call QUIT in the
  partial read/write loops, so the current quit handler is invoked
  whenever a serial->read_prim / serial->write_prim returns EINTR.

- Makes the "struct serial" reachar / write code call
  interruptible_select instead of gdb_select, so that QUITs are
  detected in a race-free manner.

- Stops remote.c from setting immediate_quit during the initial
  connection.

- Instead, we install a custom quit handler whenever we're calling
  into the serial code.  This custom quit handler knows to immediately
  throw a quit when we're in the initial connection setup, and
  otherwise defer handling the quit/Ctrl-C request to later, when
  we're safely out of a packet command/response sequence.  This also
  is what is now responsible for handling "double Ctrl-C because
  target connection is stuck/wedged."

- remote.c no longer installs a specialized SIGINT handlers, and
  instead re-uses the quit flag.  Since we want to rely on the QUIT
  macro, the SIGINT handler must also set the quit.  And the easiest
  is just to not install custom SIGINT handler in remote.c.  Let the
  standard SIGINT handler do its job of setting the quit flag.
  Centralizing SIGINT handlers seems like a good thing to me, anyway.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* defs.h (quit_handler_ftype, quit_handler)
	(make_cleanup_override_quit_handler, default_quit_handler): New.
	(QUIT): Adjust comments.
	* event-top.c (default_quit_handler): New function.
	(quit_handler): New global.
	(struct quit_handler_cleanup_data): New.
	(restore_quit_handler, restore_quit_handler_dtor)
	(make_cleanup_override_quit_handler): New.
	(async_request_quit): Call QUIT.
	* remote.c (struct remote_state) <got_ctrlc_during_io>: New field.
	(async_sigint_remote_twice_token, async_sigint_remote_token):
	Delete.
	(remote_close): Update comments.
	(remote_start_remote): Don't set immediate_quit.  Set starting_up
	earlier.
	(remote_serial_quit_handler, remote_unpush_and_throw): New
	functions.
	(remote_open_1): Clear got_ctrlc_during_io.  Set
	remote_async_terminal_ours_p unconditionally.
	(async_initialize_sigint_signal_handler)
	(async_handle_remote_sigint, async_handle_remote_sigint_twice)
	(remote_check_pending_interrupt, async_remote_interrupt)
	(async_remote_interrupt_twice)
	(async_cleanup_sigint_signal_handler, ofunc)
	(sync_remote_interrupt, sync_remote_interrupt_twice): Delete.
	(remote_terminal_inferior, remote_terminal_ours): Remove async
	checks.
	(remote_wait_as): Don't install a SIGINT handler in sync mode.
	(readchar, remote_serial_write): Override the quit handler with
	remote_serial_quit_handler.
	(getpkt_or_notif_sane_1): Don't call QUIT.
	(initialize_remote_ops): Don't install
	remote_check_pending_interrupt.
	(_initialize_remote): Don't create async_sigint_remote_token and
	async_sigint_remote_twice_token.
	* ser-base.c (ser_base_wait_for): Call QUIT and use
	interruptible_select.
	(ser_base_write): Call QUIT.
	* ser-go32.c (dos_readchar, dos_write): Call QUIT.
	* ser-unix.c (wait_for): Don't use VTIME.  Always take the
	gdb_select path, but call QUIT and interruptible_select.
	* utils.c (maybe_quit): Call the current quit handler.  Don't call
	target_check_pending_interrupt.
	(defaulted_query, prompt_for_continue): Override the quit handler
	with the default quit handler.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Eliminate immediate_quit
@ 2016-04-13  6:32 sergiodj+buildbot
  2016-04-13 20:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  6:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 585a46a2d01d25181926329f258f1d1374f93e99 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 585a46a2d01d25181926329f258f1d1374f93e99

Eliminate immediate_quit

This finally gets rid of immediate_quit (and surrounding
infrustruture), as nothing sets it anymore.

gdb_call_async_signal_handler was only necessary in order to handle
immediate_quit.  We can just call mark_async_signal_handler directly
on all hosts now.

In turn, we can clean up mingw-hdep.c's gdb_select a bit, as
sigint_event / sigint_handler is no longer needed.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* defs.h: Update comments on SIGINT handling.
	(immediate_quit): Delete declaration.
	* event-loop.c (call_async_signal_handler): Delete.
	* event-loop.h (call_async_signal_handler): Delete declaration.
	(mark_async_signal_handler): Update comments.
	(gdb_call_async_signal_handler): Delete declaration.
	* event-top.c (handle_sigint): Call mark_async_signal_handler
	instead of gdb_call_async_signal_handler.
	* exceptions.c (prepare_to_throw_exception): Remove reference to
	immediate_quit.
	(exception_fprintf): Remove comments about immediate_quit.
	* mingw-hdep.c (sigint_event, sigint_handler): Delete.
	(gdb_select): Don't wait on sigint_event.
	(gdb_call_async_signal_handler): Delete.
	(_initialize_mingw_hdep): Delete.
	* posix-hdep.c (gdb_call_async_signal_handler): Delete.
	* utils.c (immediate_quit): Delete.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Eliminate target_check_pending_interrupt
@ 2016-04-13  6:59 sergiodj+buildbot
  2016-04-13 20:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  6:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfd0fbddb025d36228d02fe23e06039acc6104e4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: cfd0fbddb025d36228d02fe23e06039acc6104e4

Eliminate target_check_pending_interrupt

This is no longer called anywhere.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* target.c (target_check_pending_interrupt): Delete.
	* target.h (struct target_ops) <to_check_pending_interrupt>:
	Remove method.
	(target_check_pending_interrupt): Remove declaration.
	* target-delegates.c: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Eliminate prepare_to_throw_exception
@ 2016-04-13  7:30 sergiodj+buildbot
  2016-04-13 21:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2afc13ff80492278154c0f2156a9d32dd5ba675a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2afc13ff80492278154c0f2156a9d32dd5ba675a

Eliminate prepare_to_throw_exception

No longer necessary.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.c (exception_rethrow): Remove
	prepare_to_throw_exception call.
	* common/common-exceptions.h (prepare_to_throw_exception): Delete
	declaration.
	* exceptions.c (prepare_to_throw_exception): Delete.

gdb/gdbserver/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* utils.c (prepare_to_throw_exception): Delete.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Do target_terminal_ours in query & friends instead of in all callers
@ 2016-04-13  8:11 sergiodj+buildbot
  2016-04-13 16:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  8:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 651ce16aa7c2bd5e9f634e91e73790dc3e01a5c0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 651ce16aa7c2bd5e9f634e91e73790dc3e01a5c0

Do target_terminal_ours in query & friends instead of in all callers

Any time a caller calls query & friends / prompt_for_continue without
ensuring that gdb owns the terminal for input is a bug.  So do that in
defaulted_query / prompt_for_continue directly instead.

An example of a case where we currently miss calling
target_terminal_ours is internal_error.  Ever since defaulted_query
was made to use gdb_readline_callback, there's no way to answer the
internal error query if the internal error happens while the target is
has the terminal:

  (gdb) c
  Continuing.
  .../src/gdb/linux-nat.c:1676: internal-error: linux_nat_resume: Assertion `dummy_counter < 10' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) _

Entering 'y' or 'n' does not work, GDB does not respond.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* gnu-nat.c (inf_validate_task_sc): Don't call
	target_terminal_ours / target_terminal_inferior around query.
	* i386-tdep.c (i386_record_lea_modrm, i386_process_record): Don't
	call target_terminal_ours / target_terminal_inferior around
	yquery.
	* linux-record.c (record_linux_system_call): Don't call
	target_terminal_ours / target_terminal_inferior around yquery.
	* nto-procfs.c (interrupt_query): Don't call target_terminal_ours
	/ target_terminal_inferior around query.
	* record-full.c (record_full_check_insn_num): Remove
	'set_terminal' parameter.  Don't call target_terminal_ours /
	target_terminal_inferior around query.
	(record_full_message, record_full_registers_change)
	(record_full_xfer_partial): Adjust.
	* remote.c (interrupt_query): Don't call target_terminal_ours /
	target_terminal_inferior around query.
	* utils.c (defaulted_query): Install cleanup to restore target
	terminal.  Put target_terminal_ours_for_output in effect while
	defaulted producing, and target_terminal_ours in in effect while
	handling input.
	(prompt_for_continue): Install cleanup to restore target terminal.
	Put target_terminal_ours in in effect while handling input.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use setjmp/longjmp for TRY/CATCH instead of sigsetjmp/siglongjmp
@ 2016-04-13  8:30 sergiodj+buildbot
  2016-04-13 22:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  8:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 173981bc49c9e8fce9271cb47714952dbe2ec627 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 173981bc49c9e8fce9271cb47714952dbe2ec627

Use setjmp/longjmp for TRY/CATCH instead of sigsetjmp/siglongjmp

Now that we don't ever throw GDB exceptions from signal handlers [1],
we can switch to have TRY/CATCH implemented in terms of plain
setjmp/longjmp instead of sigsetjmp/siglongjmp.

In https://sourceware.org/ml/gdb-patches/2015-02/msg00114.html, Yichun
Zhang mentions a 11%/14%+ speedup in his GDB python scripts with a
patch that did something similar to only a specific set of TRY/CATCH
calls.

[1] - https://sourceware.org/ml/gdb-patches/2016-03/msg00351.html

Tested on x86_64 Fedora 23, native and gdbserver.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.c (struct catcher) <buf>: Now a
	'jmp_buf' instead of SIGJMP_BUF.
	(exceptions_state_mc_init): Change return type to 'jmp_buf'.
	(throw_exception): Use longjmp instead of SIGLONGJMP.
	* common/common-exceptions.h: Include <setjmp.h> instead of
	"gdb_setjmp.h".
	(exceptions_state_mc_init): Change return type to 'jmp_buf'.
	[GDB_XCPT == GDB_XCPT_SJMP] (TRY): Use setjmp instead of
	SIGSETJMP.
	* cp-support.c: Include "gdb_setjmp.h".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] TUI: GC tui_target_has_run
@ 2016-04-13  9:19 sergiodj+buildbot
  2016-04-13 18:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a12ac51333cf97f4da0597d049cc694b4535e7dd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a12ac51333cf97f4da0597d049cc694b4535e7dd

TUI: GC tui_target_has_run

Nothing actually uses this global.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* tui/tui-hooks.c (tui_target_has_run): Delete.
	(tui_about_to_proceed): Delete.
	(tui_about_to_proceed_observer): Delete.
	(tui_install_hooks, tui_remove_hooks): Don't install/remove an
	about_to_proceed observer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [C++] Switch TRY/CATCH to real C++ try/catch by default again
@ 2016-04-13 12:28 sergiodj+buildbot
  2016-04-13 23:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 12:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f41b320edb93e2c0cdd76f218811e197156b052 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0f41b320edb93e2c0cdd76f218811e197156b052

[C++] Switch TRY/CATCH to real C++ try/catch by default again

Now that we don't ever throw GDB exceptions from signal handlers [1],
we can switch back to having TRY/CATCH implemented in terms of C++
try/catch instead of sigjmp/longjmp.

[1] - https://sourceware.org/ml/gdb-patches/2016-03/msg00351.html

Tested on x86_64 Fedora 23, native and gdbserver.

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (GDB_XCPT_TRY): Update comment.
	[__cplusplus] (GDB_XCPT): Define as GDB_XCPT_TRY.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix typo in ftrace.exp condition testing
@ 2016-04-13 13:01 sergiodj+buildbot
  2016-04-14  0:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 13:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ce09462959bbc2af15e8088c5e54c8668cf8ccb ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 8ce09462959bbc2af15e8088c5e54c8668cf8ccb

Fix typo in ftrace.exp condition testing

This obvious patch replaces "ond" wiht "cond" as the test prefix for
conditional tests.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp (proc): Change test prefix from "ond" to "cond".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] btrace: fix test build error in gdb.btrace/instruction_history.c
@ 2016-04-13 13:43 sergiodj+buildbot
  2016-04-14  2:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 13:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e26b7e41652e288dfdb4c48121bba470c4774150 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: e26b7e41652e288dfdb4c48121bba470c4774150

btrace: fix test build error in gdb.btrace/instruction_history.c

On systems with a newer version of GCC the gdb.btrace/instruction_history.exp
test fails to build like this:

    Running .../gdb.btrace/instruction_history.exp ...
    gdb compile failed, .../gdb.btrace/instruction_history.c:
    In function 'main': .../gdb.btrace/instruction_history.c:24:3: warning:
    implicit declaration of function 'loop' [-Wimplicit-function-declaration]
       loop ();
       ^

Declare loop to fix it.

testsuite/
	* gdb.btrace/instruction_history.c (loop): Add declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR remote/19840: gdb crashes on reverse-stepi
@ 2016-04-13 14:46 sergiodj+buildbot
  2016-04-14  7:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a00c80277a54abe0b286a6e8babc8fe50120205 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3a00c80277a54abe0b286a6e8babc8fe50120205

Fix PR remote/19840: gdb crashes on reverse-stepi

Reverse debugging against a remote target that does reverse debugging
itself (with the bs/bc packets) always trips on:

 (gdb) target remote localhost:...
 (gdb) reverse-stepi
 ../../gdb/target.c:602: internal-error: default_execution_direction: to_execution_direction must be implemented for reverse async

I missed adding a to_execution_direction method to remote.c in commit
3223143295b5 (Adds target_execution_direction to make record targets
support async mode), GDB 7.4 time.  Later, GDB 7.8 switched to
target-async on by default, making the regression user-visible by
default too.

Fix is simply to add the missing to_execution_direction implementation
to target remote.

Tested by Andi Kleen against Simics.

gdb/ChangeLog:
2016-04-13  Pedro Alves  <palves@redhat.com>

	PR remote/19840
	* remote.c (struct remote_state) <last_resume_exec_dir>: New
	field.
	(new_remote_state): Default last_resume_exec_dir to EXEC_FORWARD.
	(remote_open_1): Reset last_resume_exec_dir to EXEC_FORWARD.
	(remote_resume): Store the last execution direction.
	(remote_execution_direction): New function.
	(init_remote_ops): Install it as to_execution_direction target_ops
	method.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix aarch64 ftrace JIT condition testcase
@ 2016-04-13 15:21 sergiodj+buildbot
  2016-04-14  8:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 15:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45e3745ed0e034fdec5beee0738f383bd6e2e045 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 45e3745ed0e034fdec5beee0738f383bd6e2e045

Fix aarch64 ftrace JIT condition testcase

This patch fixes the following failure:
FAIL: gdb.trace/trace-condition.exp: ftrace: -(21 << 1) == -42: check 10
frames were collected.

This was due to aarch64_emit_sub using the wrong order in its operands, so the
operation would end up being 42 - 0 rather than 0 - 42.

This patch also fixes the order of aarch64_emit_add for clarity.

The test case for emit_sub is fixed so that the proper order of
the operands is needed for the test to pass.

Tested on aarch64-native-extended-gdbserver.

Note: trace-condition.exp was broken a bit so I had to modify it to run
the test. A fix is coming for that in another patch.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_emit_add): Switch x1 and x0.
	(aarch64_emit_sub): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp (foreach): Fix emit_sub testcase.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix disassembly of the V850's LD.BU instruction.
@ 2016-04-13 16:19 sergiodj+buildbot
  2016-04-14  9:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT accc018020dd329d99b50335ad168d35650b7f09 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: accc018020dd329d99b50335ad168d35650b7f09

Fix disassembly of the V850's LD.BU instruction.

	PR target/19937
opcode	* v850-opc.c (v850_opcodes): Correct masks for long versions of
	the LD.B and LD.BU instructions.

gas	* testsuite/gas/v850/pr19937.s: New test.
	* testsuite/gas/v850/pr19937.d: New test control file.
	* testsuite/gas/v850/basic.exp: Run the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix and improve comment in gdb_remote_download
@ 2016-04-13 17:17 sergiodj+buildbot
  2016-04-14 10:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8392fa22d69113602407281cbb364f29557c39b1 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8392fa22d69113602407281cbb364f29557c39b1

Fix and improve comment in gdb_remote_download

This patch fixes the current comment in gdb_remote_download, which is
false (the "except if that's already where it is" part).  It also
improves it, by explaining why pass TOFILE through standard_output_file,
even it is an absolute path.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_remote_download): Fix and extend comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Test GDB connection to GDBserver with no symbol files
@ 2016-04-13 21:23 sergiodj+buildbot
  2016-04-14 12:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 21:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d49b1d0b08426c650a69a6c4971cba56a4e6af1 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 7d49b1d0b08426c650a69a6c4971cba56a4e6af1

Test GDB connection to GDBserver with no symbol files

This test exercises the scenarios where we attempt to connect GDB to GDBserver
in standard remote mode, query the symbol file path, attempt to open said
symbol file on GDB's end and fail, causing the connection to drop abruptly.

Regression-tested on x86-64/Ubuntu.

With an unpatched GDB we should see this:

FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=permission: connection to GDBserver succeeded (the program is no longer running)
FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=delete: connection to GDBserver succeeded (the program is no longer running)
FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=target:: action=permission: connection to GDBserver succeeded (the program is no longer running)
FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=target:: action=delete: connection to GDBserver succeeded (the program is no longer running)

A patched GDB should have full passes.

gdb/testsuite/ChangeLog:

2016-04-13  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.server/connect-with-no-symbol-file.c: New file.
	* gdb.server/connect-with-no-symbol-file.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Avoid implicit float <-> integer conversion warnings
@ 2016-04-14 12:27 sergiodj+buildbot
  2016-04-14 14:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 12:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aebf07fc1483b0bda9bbc1c0b7d7184b7e840677 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: aebf07fc1483b0bda9bbc1c0b7d7184b7e840677

Avoid implicit float <-> integer conversion warnings

On:

 $ uname -a
 NetBSD gcc70.fsffrance.org 5.1 NetBSD 5.1 (GENERIC) #0: Sat Nov  6 13:19:33 UTC 2010  builds@b6.netbsd.org:/home/builds/ab/netbsd-5-1-RELEASE/amd64/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sys/arch/amd64/compile/GENERIC amd64

With:

 $ g++ -v
 Using built-in specs.
 Target: x86_64--netbsd
 Configured with: /usr/src/tools/gcc/../../gnu/dist/gcc4/configure --enable-long-long --disable-multilib --enable-threads --disable-symvers --build=x86_64-unknown-netbsd4.99.72 --host=x86_64--netbsd --target=x86_64--netbsd --enable-__cxa_atexit
 Thread model: posix
 gcc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120)

I saw:

 ../../src/gdb/ada-typeprint.c: In function 'void print_fixed_point_type(type*, ui_file*)':
 ../../src/gdb/ada-typeprint.c:366: warning: passing 'float' for argument 2 to 'DOUBLEST ada_fixed_to_float(type*, LONGEST)'

 ../../src/gdb/value.c: In function 'LONGEST unpack_long(type*, const gdb_byte*)':
 ../../src/gdb/value.c:2833: warning: converting to 'LONGEST' from 'DOUBLEST'
 ../../src/gdb/value.c:2838: warning: converting to 'LONGEST' from 'DOUBLEST'

gdb/ChangeLog:
2016-04-14  Pedro Alves  <palves@redhat.com>

	* ada-typeprint.c (print_fixed_point_type): Don't pass float as
	argument to function expecting LONGEST.
	* value.c (unpack_long): Add casts to LONGEST.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Avoid "format not a string literal" warnings
@ 2016-04-14 12:49 sergiodj+buildbot
  2016-04-14 14:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 12:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f31862a8d9f3eea51fc58bd66abeb70c730feaf ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7f31862a8d9f3eea51fc58bd66abeb70c730feaf

Avoid "format not a string literal" warnings

On:

 $ uname -a
 NetBSD gcc70.fsffrance.org 5.1 NetBSD 5.1 (GENERIC) #0: Sat Nov  6 13:19:33 UTC 2010  builds@b6.netbsd.org:/home/builds/ab/netbsd-5-1-RELEASE/amd64/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sys/arch/amd64/compile/GENERIC amd64

With:

 $ g++ -v
 Using built-in specs.
 Target: x86_64--netbsd
 Configured with: /usr/src/tools/gcc/../../gnu/dist/gcc4/configure --enable-long-long --disable-multilib --enable-threads --disable-symvers --build=x86_64-unknown-netbsd4.99.72 --host=x86_64--netbsd --target=x86_64--netbsd --enable-__cxa_atexit
 Thread model: posix
 gcc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120)

I saw:

 cc1plus: warnings being treated as errors
 ../../src/gdb/ctf.c: In function 'void ctf_save_metadata_header(trace_write_handler*)':
 ../../src/gdb/ctf.c:267: warning: format not a string literal, argument types not checked
 cc1plus: warnings being treated as errors
 ../../src/gdb/cli/cli-cmds.c: In function 'void alias_command(char*, int)':
 ../../src/gdb/cli/cli-cmds.c:1428: warning: format not a string literal and no format arguments
 ../../src/gdb/cli/cli-cmds.c:1457: warning: format not a string literal and no format arguments

gdb/ChangeLog:
2016-04-14  Pedro Alves  <palves@redhat.com>

	* cli/cli-cmds.c (alias_usage_error): New function.
	(alias_command): Use it.
	* ctf.c (ctf_save_metadata_header): Inline metadata_fmt local in
	ctf_save_write_metadata call.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Replace "link" with "sh_link"
@ 2016-04-14 15:50 sergiodj+buildbot
  2016-04-14 16:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7634c4e679156fc6a93ccb8b33898f5cf41eb233 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7634c4e679156fc6a93ccb8b33898f5cf41eb233

Replace "link" with "sh_link"

On Linux/x86, GCC 4.2 issues a warning:

bfd/elf.c: In function _bfd_elf_copy_private_bfd_data:
bfd/elf.c:1334: warning: declaration of link shadows a global declaration
/usr/include/unistd.h:757: warning: shadowed declaration is here
make[6]: *** [elf.lo] Error 1

Replace "link" with "sh_link" fixes it.

	* elf.c (_bfd_elf_copy_private_bfd_data): Replace "link" with
	"sh_link".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd/arc: Rename enum entries to avoid conflicts
@ 2016-04-14 16:59 sergiodj+buildbot
  2016-04-14 17:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33cbe6c07ed7e66d65c106cffb496eff5d7e8fb5 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 33cbe6c07ed7e66d65c106cffb496eff5d7e8fb5

bfd/arc: Rename enum entries to avoid conflicts

In bfd/elf32-arc.c an enum is created that contains entries with generic
names like 'NONE' and 'OFF'.  This has been fine for now, but I had a
need to include opcode/arc.h into bfd/elf32-arc.c.  Unfortunately
opcode/arc.h includes a different enum with identical generic names.

Given that changing the enum in the header file could mean wide-ranging
changes, while changing the enum in the .c file is limited to only
changing the one file, I've added a prefix to the enum in the .c file.

This commit does not add the new include, that will come later.  There
should be no functional change with this commit.

bfd/ChangeLog:

	* elf32-arc.c (tls_got_entries): Add 'TLS_GOT_' prefix to all
	entries.
	(elf_arc_relocate_section): Update enum uses.
	(elf_arc_check_relocs): Likewise.
	(elf_arc_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] arc/nps400 : New cmem instructions and associated relocation
@ 2016-04-14 17:59 sergiodj+buildbot
  2016-04-14 18:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 17:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b0c052e456421a3c6d7b4c98be3ad0b3bd2ad27 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 4b0c052e456421a3c6d7b4c98be3ad0b3bd2ad27

arc/nps400 : New cmem instructions and associated relocation

Add support for arc/nps400 cmem instructions, these load and store
instructions are hard-wired to access "0x57f00000 + 16-bit-offset".

Supporting this relocation required some additions to the arc relocation
handling in the bfd library, as well as the standard changes required to
add a new relocation type.

There's a test of the new instructions in the assembler, and a test of
the relocation in the linker.

bfd/ChangeLog:

	* reloc.c: Add BFD_RELOC_ARC_NPS_CMEM16 entry.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
	* elf32-arc.c: Add 'opcode/arc.h' include.
	(struct arc_relocation_data): Add symbol_name.
	(arc_special_overflow_checks): New function.
	(arc_do_relocation): Use arc_special_overflow_checks, reindent as
	required, add an extra comment.
	(elf_arc_relocate_section): Setup symbol_name in reloc_data.

gas/ChangeLog:

	* testsuite/gas/arc/nps400-3.d: New file.
	* testsuite/gas/arc/nps400-3.s: New file.

include/ChangeLog:

	* elf/arc-reloc.def: Add ARC_NPS_CMEM16 reloc.
	* opcode/arc.h (NPS_CMEM_HIGH_VALUE): Define.

ld/ChangeLog:

	* testsuite/ld-arc/arc.exp: New file.
	* testsuite/ld-arc/nps-1.s: New file.
	* testsuite/ld-arc/nps-1a.d: New file.
	* testsuite/ld-arc/nps-1b.d: New file.
	* testsuite/ld-arc/nps-1b.err: New file.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Add xldb, xldw, xld, xstb, xstw, and xst
	instructions.
	* arc-opc.c (insert_nps_cmem_uimm16): New function.
	(extract_nps_cmem_uimm16): New function.
	(arc_operands): Add NPS_XLDST_UIMM16 operand.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] minor opt in thumb_stack_frame_destroyed_p
@ 2016-04-15 14:55 sergiodj+buildbot
  2016-04-15 14:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-15 14:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 415fa612334afb70600c2a7dbd2c2ff56ebbc4f3 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 415fa612334afb70600c2a7dbd2c2ff56ebbc4f3

[ARM] minor opt in thumb_stack_frame_destroyed_p

thumb_stack_frame_destroyed_p scans the instructions from PC to the
end of the function, but if PC is far from the end of pc, we don't
have to scan, because PC should be in epilogue if it is still
far from the end of the function.  The criterion I use here is 16
bytes, which is more than 4 instructions.

Regression tested on aarch64-linux with mutli-arch debug.

gdb:

2016-04-15  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (thumb_stack_frame_destroyed_p): Return zero if
	PC is far from the end of function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT
@ 2016-04-15 23:19 sergiodj+buildbot
  2016-04-15 23:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-15 23:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77770d832135a252d22eb95166c5ccfd40ca6a69 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 77770d832135a252d22eb95166c5ccfd40ca6a69

MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT

This makes the MIPS Linux backends recognize TRAP_BRKPT and
TRAP_HWBKPT in siginfo.si_code in addition to SI_KERNEL, since Linux
4.6 now reports the finer-grained si_code values too.

Refs:
 https://sourceware.org/ml/gdb-patches/2016-02/msg00756.html
 https://sourceware.org/ml/gdb-patches/2016-04/msg00090.html

On kernels that report SI_KERNEL (<= 4.5), we'll enter the "ambiguous"
path of save_stop_reason:

	  if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code)
	      && GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
	    {
	      /* The si_code is ambiguous on this arch -- check debug
		 registers.  */
	      if (!check_stopped_by_watchpoint (lp))
		lp->stop_reason = TARGET_STOPPED_BY_SW_BREAKPOINT;
	    }

while on kernels that report the finer-grained si_code values (>= 4.6),
we'll enter the corresponding branches:

	  else if (GDB_ARCH_IS_TRAP_BRKPT (siginfo.si_code))
	    {
	    }
	  else if (GDB_ARCH_IS_TRAP_HWBKPT (siginfo.si_code))
	    {
	      ...

gdb/ChangeLog:
2016-04-15  Pedro Alves  <palves@redhat.com>

	* nat/linux-ptrace.h [__mips__] (GDB_ARCH_IS_TRAP_BRKPT): Also
	accept TRAP_BRKPT.
	 [__mips__] (GDB_ARCH_IS_TRAP_HWBKPT): Also accept TRAP_HWBKPT.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Regenerate Makefile.in/aclocal.m4 automake 1.11.6
@ 2016-04-16  0:51 sergiodj+buildbot
  2016-04-16  5:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-16  0:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6fd8e7c249dcefd937897f743e886751adb90c90 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6fd8e7c249dcefd937897f743e886751adb90c90

Regenerate Makefile.in/aclocal.m4 automake 1.11.6

bfd/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.
	* doc/Makefile.in: Likewise.

binutils/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.
	* doc/Makefile.in: Likewise.

gas/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.
	* doc/Makefile.in: Likewise.

gold/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.
	* testsuite/Makefile.in: Likewise.

gprof/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.

ld/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.

opcodes/

	* Makefile.in: Regenerated with automake 1.11.6.
	* aclocal.m4: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix gdb C++ build when libipt is available
@ 2016-04-16  1:25 sergiodj+buildbot
  2016-04-16  7:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-16  1:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7abe1019dbff66b6abfb32df90d0c13328710ee ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d7abe1019dbff66b6abfb32df90d0c13328710ee

Fix gdb C++ build when libipt is available

With libipt's headers installed, a build with --enable-build-with-cxx
fails with:

 .../src/gdb/btrace.c: In function btrace_insn_flag pt_btrace_insn_flags(const pt_insn*):
 .../src/gdb/btrace.c:734:33: error: invalid conversion from int to btrace_insn_flag [-fpermissive]
    enum btrace_insn_flag flags = 0;
				  ^
 .../src/gdb/btrace.c:737:11: error: invalid conversion from int to btrace_insn_flag [-fpermissive]
      flags |= BTRACE_INSN_FLAG_SPECULATIVE;
	    ^

gdb/ChangeLog:
2016-04-15  Pedro Alves  <palves@redhat.com>

	* btrace.c (pt_btrace_insn_flags): Change return type to
	btrace_insn_flags.  Use btrace_insn_flags for local.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/ada-exp.y: Remap yydefred
@ 2016-04-16  2:42 sergiodj+buildbot
  2016-04-16 11:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-16  2:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58484447ed8e1c64bbd73f224c8c9452a7420beb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 58484447ed8e1c64bbd73f224c8c9452a7420beb

gdb/ada-exp.y: Remap yydefred

On:

 $ uname -a
 NetBSD gcc70.fsffrance.org 5.1 NetBSD 5.1 (GENERIC) #0: Sat Nov  6 13:19:33 UTC 2010  builds@b6.netbsd.org:/home/builds/ab/netbsd-5-1-RELEASE/amd64/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sys/arch/amd64/compile/GENERIC amd64

The link fails with:

 (...)
 d-exp.o: In function `parse_number':
 ../../src/gdb/d-exp.y:762: multiple definition of `yydefred'
 ada-exp.o:/home/palves/gdb/build/gdb/ada-lex.c:925: first defined here
 ld: Warning: size of symbol `yydefred' changed from 464 in ada-exp.o to 336 in d-exp.o
 Makefile:1404: recipe for target 'gdb' failed

NetBSD's yacc uses a "yydefred" symbol that we missed renaming in the
Ada parser.  All other gdb parsers do this already.

gdb/ChangeLog:
2016-04-16  Pedro Alves  <palves@redhat.com>

	* ada-exp.y (yydefred): Define as ada_yydefred.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Revert 415fa612
@ 2016-04-18  8:16 sergiodj+buildbot
  2016-04-18  8:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-18  8:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5947319ef398728052a22575e1d0de0e94e4220f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5947319ef398728052a22575e1d0de0e94e4220f

Revert 415fa612

2016-04-18  Yao Qi  <yao.qi@linaro.org>

	Revert:
	2016-04-15  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (thumb_stack_frame_destroyed_p): Return zero if
	PC is far from the end of function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Support detection of Intel compilers via test_compiler_version.
@ 2016-04-18 12:17 sergiodj+buildbot
  2016-04-18 12:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-18 12:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a14d1f4dfc08edc8fe92b17b36a55d89203fb89f ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: a14d1f4dfc08edc8fe92b17b36a55d89203fb89f

testsuite: Support detection of Intel compilers via test_compiler_version.

Add Intel specific preprocessor macros to query the version of the compiler.

2016-04-18  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Testsuite/Changelog:
	* lib/compiler.c: Add Intel specific preprocessor macros.
	* lib/compiler.cc: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Testsuite: Fix compiling of shared libraries with ICC.
@ 2016-04-18 13:05 sergiodj+buildbot
  2016-04-18 13:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-18 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b9b09e9020aa32ade1a86461804a1950d967abb ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 9b9b09e9020aa32ade1a86461804a1950d967abb

Testsuite: Fix compiling of shared libraries with ICC.

We are missing "-fpic" flag when compiling shared libraries with ICC.

2016-04-18  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Testsuite/Changelog:
	* lib/gdb.exp (gdb_compile_shlib): Add flag for ICC compiler.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] fortran: Testsuite, fix different type naming across compilers.
@ 2016-04-18 13:32 sergiodj+buildbot
  2016-04-18 13:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-18 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c13f7e559afe5f973a59311b0e401296c48d96c ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 0c13f7e559afe5f973a59311b0e401296c48d96c

fortran: Testsuite, fix different type naming across compilers.

Gfortran and ifort have different names for data types.  Encapsulate
type names in a library to increase number of supported compilers.
gfortran -4.2 : int4
gfortran>=4.3 : integer(kind=4)
ifort         : INTEGER(4)

2016-04-18  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:
	* gdb.fortran/common-block.exp: Use type naming defined in lib fortran.
	* gdb.fortran/derived-type.exp: Use type naming defined in lib fortran.
	* gdb.fortran/multi-dim.exp: Use type naming defined in lib fortran.
	* gdb.fortran/vla-datatypes.exp: Use type naming defined in lib fortran.
	* gdb.fortran/vla-ptype-sub.exp: Use type naming defined in lib fortran.
	* gdb.fortran/vla-ptype.exp: Use type naming defined in lib fortran.
	* gdb.fortran/whatis_type.exp: Use type naming defined in lib fortran.
	* lib/fortran.exp (fortran_int4): New procedure.
	(fortran_real4, fortran_real8, fortran_complex4): Likewise.
	(fortran_logical4): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix gdb crash when trying to print the address of a synthetic C++ reference
@ 2016-04-18 14:16 sergiodj+buildbot
  2016-04-18 14:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-18 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a22df60ad216517bbca4b391bec09f9ded06ab7b ***

Author: Martin Galvan <martin.galvan@tallertechnologies.com>
Branch: master
Commit: a22df60ad216517bbca4b391bec09f9ded06ab7b

Fix gdb crash when trying to print the address of a synthetic C++ reference

After compiling a program which uses C++ references some optimizations may
convert the references into synthetic "pointers".  Trying to print the address
of one of such synthetic references causes gdb to crash with the following
error:

(gdb) print &ref
/build/buildd/gdb-7.7.1/gdb/dwarf2loc.c:1624: internal-error: Should not be able to create a lazy value with an enclosing type
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Apparently, what was causing it was that value_addr returns a copy of the value
that represents the reference with its type set to T* instead of T&.  However,
its enclosing_type is left untouched, which fails a check made in
read_pieced_value.  We only see the crash happen for references that are
synthetic because they're treated as pieced values, thus the call to
read_pieced_value.

On a related note, it seems that in general there are all sorts of breakage
when working with synthetic references.  This is reported here:

https://sourceware.org/bugzilla/show_bug.cgi?id=19893

gdb/ChangeLog:
2016-04-18  Martin Galvan  <martin.galvan@tallertechnologies.com>

	* valops.c (value_addr): For C++ references, set the copied value's
	enclosing_type as well.

gdb/testsuite/ChangeLog:
2016-04-18  Martin Galvan  <martin.galvan@tallertechnologies.com>

	* gdb.dwarf2/implref.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Sync Makefile.tpl with gcc.
@ 2016-04-19  8:50 sergiodj+buildbot
  2016-04-19  8:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19  8:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb7dc663abaa72601edfdce3ca7aff6fdb43bffe ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: bb7dc663abaa72601edfdce3ca7aff6fdb43bffe

Sync Makefile.tpl with gcc.

	2016-04-13  Segher Boessenkool  <segher@kernel.crashing.org>

	PR bootstrap/70173
	* Makefile.tpl (local-distclean): Delete the libcc1, gnattools,
	and gotools directories.  Delete the stage_final file.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add target descriptions for AVX + MPX
@ 2016-04-19 14:07 sergiodj+buildbot
  2016-04-19 14:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b863f512dce3c2469cf40e4559fb571b1b01658 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 2b863f512dce3c2469cf40e4559fb571b1b01658

Add target descriptions for AVX + MPX

The current MPX target descriptions assume that MPX is always combined
with AVX, however that's not correct.  We can have machines with MPX
and without AVX; or machines with AVX and without MPX.

This patch adds new target descriptions for machines that support
both MPX and AVX, as duplicates of the existing MPX descriptions.

The following commit will remove AVX from the MPX-only descriptions.


2016-04-16  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* amd64-linux-tdep.c (features/i386/amd64-avx-mpx-linux.c):
	New include.
	(amd64_linux_core_read_description): Add case for
	 X86_XSTATE_AVX_MPX_MASK.
	(_initialize_amd64_linux_tdep): Call initialize_tdesc_amd64_avx_mpx_linux.
	* amd64-linux-tdep.h (tdesc_amd64_avx_mpx_linux): New definition.
	* amd64-tdep.c (features/i386/amd64-avx-mpx.c): New include.
	(amd64_target_description): Add case for  X86_XSTATE_AVX_MPX_MASK.
	(_initialize_amd64_tdep): Call initialize_tdesc_amd64_avx_mpx.
	* common/x86-xstate.h (X86_XSTATE_MPX_MASK): Remove AVX bits.
	(X86_XSTATE_AVX_MPX_MASK): New case.
	* features/Makefile (i386/i386-avx-mpx, i386/i386-avx-mpx-linux)
	(i386/amd64-avx-mpx, i386/amd64-avx-mpx-linux): New rules.
	(i386/i386-avx-mpx-expedite, i386/i386-avx-mpx-linux-expedite)
	(i386/amd64-avx-mpx-expedite, i386/amd64-avx-mpx-linux-expedite):
	New expedites.
	* i386-linux-tdep.c (features/i386/i386-avx-mpx-linux.c): New
	include.
	(i386_linux_core_read_description): Add case
	X86_XSTATE_AVX_MPX_MASK.
	(_initialize_i386_linux_tdep): Call
	initialize_tdesc_i386_avx_mpx_linux.
	* i386-linux-tdep.h (tdesc_i386_avx_mpx_linux): New include.
	* i386-tdep.c (features/i386/i386-avx-mpx.c): New include.
	(i386_target_description): Add case for X86_XSTATE_AVX_MPX_MASK.
	* x86-linux-nat.c (x86_linux_read_description): Add case for
	X86_XSTATE_AVX_MPX_MASK.
	* features/i386/amd64-avx-mpx-linux.xml: New file.
	* features/i386/i386-avx-mpx-linux.xml: New file.
	* features/i386/i386-avx-mpx.xml: New file.
	* features/i386/amd64-avx-mpx.xml: New file.
	* features/i386/amd64-avx-mpx-linux.c: Generated.
	* features/i386/amd64-avx-mpx.c: Generated.
	* features/i386/i386-avx-mpx-linux.c: Generated.
	* features/i386/i386-avx-mpx.c: Generated.
	* regformats/i386/amd64-avx-mpx-linux.dat: Generated.
	* regformats/i386/amd64-avx-mpx.dat: Generated.
	* regformats/i386/i386-avx-mpx-linux.dat: Generated.
	* regformats/i386/i386-avx-mpx.dat: Generated.

gdb/gdbserver/ChangeLog:

	* Makefile.in (clean): Add removal for i386-avx-mpx.c,
	i386-avx-mpx-linux.c, amd64-avx-mpx.c and amd64-avx-mpx-linux.c.
	(i386-avx-mpx.c, i386-avx-mpx-linux.c, amd64-avx-mpx.c)
	(amd64-avx-mpx-linux.c): New rules.
	(amd64-avx-mpx-linux-ipa.o, i386-avx-mpx-linux-ipa.o): New rule.
	* configure.srv (srv_i386_regobj): Add i386-avx-mpx.o.
	(srv_i386_linux_regobj): Add i386-avx-mpx-linux.o.
	(srv_amd64_regobj): Add amd64-avx-mpx.o.
	(srv_amd64_linux_regobj): Add amd64-avx-mpx-linux.o.
	(srv_i386_xmlfiles): Add i386/i386-avx-mpx.xml.
	(srv_amd64_xmlfiles): Add i386/amd64-avx-mpx.xml.
	(srv_i386_linux_xmlfiles): Add i386/i386-avx-mpx-linux.xml.
	(srv_amd64_linux_xmlfiles): Add i386/amd64-avx-mpx-linux.xml.
	(ipa_i386_linux_regobj): Add i386-avx-mpx-linux-ipa.o.
	(ipa_amd64_linux_regobj): Add amd64-avx-mpx-linux-ipa.o.
	* linux-x86-low.c (x86_linux_read_description): Add case for
	X86_XSTATE_AVX_MPX_MASK.
	(x86_get_ipa_tdesc_idx): Add cases for avx_mpx.
	(initialize_low_arch): Call init_registers_amd64_avx_mpx_linux and
	init_registers_i386_avx_mpx_linux.
	* linux-i386-ipa.c (get_ipa_tdesc): Add case for avx_mpx.
	(initialize_low_tracepoint): Call
	init_registers_i386_avx_mpx_linux.
	* linux-amd64-ipa.c (get_ipa_tdesc):  Add case for avx_mpx.
	(initialize_low_tracepoint): Call
	init_registers_amd64_avx_mpx_linux.
	* linux-x86-tdesc.h (X86_TDESC_AVX_MPX): New enum value.
	(init_registers_amd64_avx_mpx_linux, tdesc_amd64_avx_mpx_linux)
	(init_registers_i386_avx_mpx_linux, tdesc_i386_avx_mpx_linux): New
	declarations.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Re-factor (i386|amd64)mpx target descriptions.
@ 2016-04-19 14:47 sergiodj+buildbot
  2016-04-19 15:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f42bf748e417cf9120fc57d144b6eaaf3adda247 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: f42bf748e417cf9120fc57d144b6eaaf3adda247

Re-factor (i386|amd64)mpx target descriptions.

In the previous patch a new set of target descriptions
(i386|amd64)-avx-mpx were added  being same as the (i386|amd64)-mpx.
This patch removes AVX feature from  (i386|amd64)-mpx target
description set.

This way the (i386|amd64)avx_mpx(_linux|) set has AVX and MPX features
and (i386|amd64)mpx(_linux|) only MPX.

2016-04-14  Walfred Tedeschi  <walfred.tedeschi@intel.com>

	* features/i386/amd64-mpx-linux.xml: Remove AVX feature.
	* features/i386/amd64-mpx.xml: Remove AVX feature.
	* features/i386/i386-mpx-linux.xml: Remove AVX feature.
	* features/i386/i386-mpx.xml: Remove AVX feature.
	* features/i386/amd64-mpx-linux.c: Regenerate.
	* features/i386/amd64-mpx.c: Regenerate.
	* features/i386/i386-mpx-linux.c: Regenerate.
	* features/i386/i386-mpx.c: Regenerate.
	* regformats/i386/amd64-mpx-linux.dat: Regenerate.
	* regformats/i386/amd64-mpx.dat: Regenerate.
	* regformats/i386/i386-mpx-linux.dat: Regenerate.
	* regformats/i386/i386-mpx.dat: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] linux-record: Squash cases with identical handling
@ 2016-04-19 15:07 sergiodj+buildbot
  2016-04-19 15:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 15:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73e6209faecc21516a981ed86a27b259f506098c ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 73e6209faecc21516a981ed86a27b259f506098c

linux-record: Squash cases with identical handling

In record_linux_system_call there are some cases with identical
handling.  These are merged together to reduce code duplication.

gdb/ChangeLog:

	* linux-record.c (record_linux_system_call): Merge handling for
	readlink/recv/read and pipe/pipe2.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] * source.c (is_regular_file): New arg errno_ptr.
@ 2016-04-19 16:33 sergiodj+buildbot
  2016-04-19 16:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 16:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a55411b9ff672c73172fff98319eb87af5a5fb4c ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: a55411b9ff672c73172fff98319eb87af5a5fb4c

* source.c (is_regular_file): New arg errno_ptr.

gdb/ChangeLog:

	* source.c (is_regular_file): New arg errno_ptr.
	All callers updated.

gdb/testsuite/ChangeLog:

	* gdb.base/bad-file.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix copyright year, remove linux only test.
@ 2016-04-19 16:46 sergiodj+buildbot
  2016-04-19 17:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85c10f77b70007a0c528bdc9dbba1add947b3085 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 85c10f77b70007a0c528bdc9dbba1add947b3085

Fix copyright year, remove linux only test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] symmisc.c (dump_symtab_1, dump_symtab): Delete arg objfile.
@ 2016-04-19 17:34 sergiodj+buildbot
  2016-04-19 18:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d04c1a59f3b6ae23f16988961cd74b561ed6f8d6 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: d04c1a59f3b6ae23f16988961cd74b561ed6f8d6

symmisc.c (dump_symtab_1, dump_symtab): Delete arg objfile.

gdb/ChangeLog:

	* symmisc.c (dump_symtab_1, dump_symtab): Delete arg objfile.
	All callers updated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes/arc: Add more nps instructions
@ 2016-04-19 22:17 sergiodj+buildbot
  2016-04-19 22:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 22:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8f785f220bab3c17fc93445ac509495d00d5afe ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: c8f785f220bab3c17fc93445ac509495d00d5afe

opcodes/arc: Add more nps instructions

Add dctcp, dcip, dcet, and dcacl instructions.

gas/ChangeLog:

	* testsuite/gas/arc/nps400-4.d: New file.
	* testsuite/gas/arc/nps400-4.s: New file.
	* testsuite/gas/arc/nps400-5.d: New file.
	* testsuite/gas/arc/nps400-5.s: New file.

include/ChangeLog:

	* opcode/arc.h (insn_class_t): Add NET and ACL class.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Add dctcp, dcip, dcet, and dcacl instructions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Handle void * conversions in FreeBSD/x86 native code to fix C++ build.
@ 2016-04-19 23:53 sergiodj+buildbot
  2016-04-20  2:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 23:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21002a635bf3da33367592e3a3ab3cce24fe5299 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 21002a635bf3da33367592e3a3ab3cce24fe5299

Handle void * conversions in FreeBSD/x86 native code to fix C++ build.

gdb/ChangeLog:

	* amd64bsd-nat.c (amd64bsd_fetch_inferior_registers): Change xstateregs
	to void *.
	(amd64bsd_store_inferior_registers): Likewise.
	* fbsd-nat.c (resume_one_thread_cb): Explicitly cast data to ptid_t *.
	(resume_all_threads_cb): Likewise.
	* i386bsd-nat.c (i386bsd_supply_gregset): Cast gregs to char *.
	(i386bsd_collect_gregset): Likewise.
	(i386bsd_fetch_inferior_registers): Change xstateregs to void *.
	(i386bsd_store_inferior_registers): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] arc: Fix relocation formula for ARC_NPS_CMEM16 relocation
@ 2016-04-20 11:08 sergiodj+buildbot
  2016-04-20 11:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 11:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52176c676da5f4b7339f254dc83cb35a0789bf20 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 52176c676da5f4b7339f254dc83cb35a0789bf20

arc: Fix relocation formula for ARC_NPS_CMEM16 relocation

The ME modifier was missing from the relocation formula for the
ARC_NPS_CMEM16 relocation, and as such the relocation would not patch
correctly on little endian targets.

include/ChangeLog:

	* elf/arc-reloc.def (ARC_NPS_CMEM16): Add ME modifier to formula.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] change argument type to bfd_byte
@ 2016-04-20 11:27 sergiodj+buildbot
  2016-04-20 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 11:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b98e6871247e1ef764360f6d042254ce4af62ca4 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: b98e6871247e1ef764360f6d042254ce4af62ca4

change argument type to bfd_byte

We operate on the pointer's target as a set of bytes, and this avoids doing
arithmetic on void * which is undefined in ISO C.

bfd/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-arm.c (put_thumb2_insn): Change argument type to bfd_byte *.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] update many old style function definitions
@ 2016-04-20 12:15 sergiodj+buildbot
  2016-04-20 12:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 12:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c7cdec063514bb9ffe2a62fb280e5ec676cac0 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: e6c7cdec063514bb9ffe2a62fb280e5ec676cac0

update many old style function definitions

This includes regenerating a bunch of files in opcodes/ with trunk cgen.

gprof/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* basic_blocks.c: Update old style function definitions.
	* cg_arcs.c: Likewise.
	* cg_print.c: Likewise.
	* gen-c-prog.awk: Likewise.
	* gmon_io.c: Likewise.
	* hertz.c: Likewise.
	* hist.c: Likewise.
	* sym_ids.c: Likewise.

bfd/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* cache.c: Update old style function definitions.
	* elf32-m68k.c: Likewise.
	* elf64-mmix.c: Likewise.
	* stab-syms.c: Likewise.

opcodes/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* alpha-dis.c: Regenerate.
	* crx-dis.c: Likewise.
	* disassemble.c: Likewise.
	* epiphany-opc.c: Likewise.
	* fr30-opc.c: Likewise.
	* frv-opc.c: Likewise.
	* ip2k-opc.c: Likewise.
	* iq2000-opc.c: Likewise.
	* lm32-opc.c: Likewise.
	* lm32-opinst.c: Likewise.
	* m32c-opc.c: Likewise.
	* m32r-opc.c: Likewise.
	* m32r-opinst.c: Likewise.
	* mep-opc.c: Likewise.
	* mt-opc.c: Likewise.
	* or1k-opc.c: Likewise.
	* or1k-opinst.c: Likewise.
	* tic80-opc.c: Likewise.
	* xc16x-opc.c: Likewise.
	* xstormy16-opc.c: Likewise.

ld/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* emultempl/scoreelf.em: Likewise.

binutils/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* resres.c: Likewise.

gas/ChangeLog:

2016-04-20  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* cgen.c: Likewise.
	* config/tc-bfin.c: Likewise.
	* config/tc-ia64.c: Likewise.
	* config/tc-mep.c: Likewise.
	* config/tc-metag.c: Likewise.
	* config/tc-nios2.c: Likewise.
	* config/tc-rl78.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Move ARM_CPSR_GREGNUM to arch/arm-linux.h
@ 2016-04-20 12:32 sergiodj+buildbot
  2016-04-20 13:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 12:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6885166d994162c92dc9053bdf2d87e67a452db3 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6885166d994162c92dc9053bdf2d87e67a452db3

Move ARM_CPSR_GREGNUM to arch/arm-linux.h

This patch moves macro ARM_CPSR_GREGNUM to arch/arm-linux.h so that it
can be used in GDBserver side.

gdb:

2016-04-20  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.h (ARM_CPSR_GREGNUM): Move it to ...
	* arch/arm-linux.h: ... here.

gdb/gdbserver:

2016-04-20  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.c: Include "arch/arm-linux.h".
	(arm_fill_gregset): Use ARM_CPSR_GREGNUM rather than magic
	number 16.
	(arm_store_gregset): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Check ELF relocs after opening all input files
@ 2016-04-20 13:16 sergiodj+buildbot
  2016-04-20 14:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 13:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d968975277ba280372002800c6c25bb1b29f496e ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d968975277ba280372002800c6c25bb1b29f496e

Check ELF relocs after opening all input files

Delaying checking ELF relocations until opening all input files so
that symbol information is final when relocations are checked.  This
is only enabled for x86 targets.

bfd/

	* elf-bfd.h (_bfd_elf_link_check_relocs): New.
	* elflink.c (_bfd_elf_link_check_relocs): New function.
	(elf_link_add_object_symbols): Call _bfd_elf_link_check_relocs
	if check_relocs_after_open_input is FALSE.

include/

	* bfdlink.h (bfd_link_info): Add check_relocs_after_open_input.

ld/

	* emulparams/elf32_x86_64.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	New.
	* emulparams/elf_i386.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emulparams/elf_i386_be.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emulparams/elf_i386_chaos.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emulparams/elf_i386_ldso.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emulparams/elf_i386_vxworks.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emulparams/elf_x86_64.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emulparams/i386nto.sh (CHECK_RELOCS_AFTER_OPEN_INPUT):
	Likewise.
	* emultempl/elf32.em (gld${EMULATION_NAME}_before_parse):
	Set check_relocs_after_open_input to TRUE if
	CHECK_RELOCS_AFTER_OPEN_INPUT is yes.
	(gld${EMULATION_NAME}_after_open): Call
	_bfd_elf_link_check_relocs on all inputs if
	check_relocs_after_open_input is TRUE.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Call _bfd_elf_create_ifunc_sections only for ifunc
@ 2016-04-20 13:35 sergiodj+buildbot
  2016-04-20 15:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 13:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 466ee2af4a927fc6aaaaa62b0abd3b0cff9bcef7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 466ee2af4a927fc6aaaaa62b0abd3b0cff9bcef7

Call _bfd_elf_create_ifunc_sections only for ifunc

Since x86 check_relocs is called after opening all input files, we
need to call _bfd_elf_create_ifunc_sections only for STT_GNU_IFUNC
symbols.

	* elf32-i386.c (elf_i386_check_relocs): Call
	_bfd_elf_create_ifunc_sections only for STT_GNU_IFUNC symbol.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] symmisc.c (dump_symtab_1): Print owning compunit for identical blockvectors.
@ 2016-04-20 17:31 sergiodj+buildbot
  2016-04-20 17:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c739336e5aadd6670909059fba889f50caa9cea ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: 6c739336e5aadd6670909059fba889f50caa9cea

symmisc.c (dump_symtab_1): Print owning compunit for identical blockvectors.

	* symmisc.c (dump_symtab_1): Print owning compunit for identical
	blockvectors.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Check run-time R_X86_64_32 relocation overflow
@ 2016-04-20 18:32 sergiodj+buildbot
  2016-04-20 18:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 18:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 338c190a92871c063847caef51bdc066372d4550 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 338c190a92871c063847caef51bdc066372d4550

Check run-time R_X86_64_32 relocation overflow

Since elf_x86_64_check_relocs is called after opening all input files,
we can detect dynamic R_X86_64_32 relocation overflow there.

bfd/

	PR ld/19969
	* elf64-x86-64.c (check_relocs_failed): New.
	(elf_x86_64_need_pic): Moved before elf_x86_64_check_relocs.
	Support relocation agaist local symbol.  Set check_relocs_failed.
	(elf_x86_64_check_relocs): Use elf_x86_64_need_pic.  Check
	R_X86_64_32 relocation overflow.
	(elf_x86_64_relocate_section): Skip if check_relocs failed.
	Update one elf_x86_64_need_pic and remove one elf_x86_64_need_pic.

ld/

	PR ld/19969
	* testsuite/ld-x86-64/pr19969.d: New file.
	* testsuite/ld-x86-64/pr19969a.S: Likewise.
	* testsuite/ld-x86-64/pr19969b.S: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run pr19969 tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/darwin-nat.c: Fix "cast to pointer from integer of different size" warning
@ 2016-04-20 21:09 sergiodj+buildbot
  2016-04-20 21:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 21:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 597e448caf30996be7e4583847da720f8021b20c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 597e448caf30996be7e4583847da720f8021b20c

gdb/darwin-nat.c: Fix "cast to pointer from integer of different size" warning

Fixes, with gcc 5.3.0:

 .../src/gdb/darwin-nat.c: In function 'void darwin_resume_thread(inferior*, darwin_thread_t*, int, int)':
 .../src/gdb/darwin-nat.c:731:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
     (caddr_t)thread->gdb_port, nsignal);
		      ^
 .../src/gdb/darwin-nat.c:84:35: note: in definition of macro 'PTRACE'
   darwin_ptrace(#CMD, CMD, (PID), (ADDR), (SIG))
				    ^

thread->gdb_port is an unsigned int, caddr_t is a void pointer.

gdb/ChangeLog:
2016-04-20  Pedro Alves  <palves@redhat.com>

	* darwin-nat.c (darwin_resume_thread): Add uintptr_t cast.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix "incompatible pointer type" warning in gdb/aarch64-tdep.c
@ 2016-04-20 22:24 sergiodj+buildbot
  2016-04-20 22:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 22:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9436c7c71f13df84182371c6b2fb6e356051d14 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d9436c7c71f13df84182371c6b2fb6e356051d14

Fix "incompatible pointer type" warning in gdb/aarch64-tdep.c

Fixes, with x86_64-apple-darwin15-gcc (gcc 5.3.0):

 .../src/gdb/aarch64-tdep.c: In function 'aarch64_record_load_store':
 .../src/gdb/aarch64-tdep.c:3479:67: error: passing argument 3 of 'regcache_raw_read_unsigned' from incompatible pointer type [-Werror=incompatible-pointer-types]
		       bits (aarch64_insn_r->aarch64_insn, 16, 20), &reg_rm_val);
								    ^
 In file included from .../src/gdb/regcache.h:23:0,
		  from .../src/gdb/gdbarch.h:69,
		  from .../src/gdb/defs.h:620,
		  from .../src/gdb/aarch64-tdep.c:21:
 .../src/gdb/common/common-regcache.h:60:29: note: expected 'ULONGEST * {aka long unsigned int *}' but argument is of type 'uint64_t * {aka long long unsigned int *}'
  extern enum register_status regcache_raw_read_unsigned
			      ^

gdb/ChangeLog:
2016-04-20  Pedro Alves  <palves@redhat.com>

	* aarch64-tdep.c (aarch64_record_load_store): Change type of
	'reg_rm_val' local to ULONGEST.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix host signal vs gdb signal mixup in gdb/darwin-nat.c
@ 2016-04-20 22:56 sergiodj+buildbot
  2016-04-20 23:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 22:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ae0055212a4835793815dbd8fa120d8c63fc7e8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5ae0055212a4835793815dbd8fa120d8c63fc7e8

Fix host signal vs gdb signal mixup in gdb/darwin-nat.c

Building in C++ mode caught a bug here:

 .../src/gdb/darwin-nat.c: In function 'ptid_t darwin_decode_message(mach_msg_header_t*, darwin_thread_t**, inferior**, target_waitstatus*)':
 .../src/gdb/darwin-nat.c:1016:25: error: invalid conversion from 'int' to 'gdb_signal' [-fpermissive]
      status->value.sig = WTERMSIG (wstatus);
			  ^

gdb/ChangeLog:
2016-04-20  Pedro Alves  <palves@redhat.com>

	* darwin-nat.c (darwin_decode_message): Use gdb_signal_from_host.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add missing sentinel 'char *' casts in concat/reconcat calls
@ 2016-04-21 10:39 sergiodj+buildbot
  2016-04-21 10:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-21 10:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36cec19e826c19648964576ef2d20d63f99e888 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b36cec19e826c19648964576ef2d20d63f99e888

Add missing sentinel 'char *' casts in concat/reconcat calls

The wildebeest-debian-wheezy-i686 buildslave's build is broken due to:

 ../../binutils-gdb/gdb/python/python.c: In function void _initialize_python():
 ../../binutils-gdb/gdb/python/python.c:1709:36: error: missing sentinel in function call [-Werror=format]

Reproduced on Fedora 23 by sticking a few:

 #undef NULL
 #define 0

in build/gdb/build-gnulib/{stddef|signal|stdio}.h.  Hopefully this
caught all instances.

gdb/ChangeLog:
2016-04-21  Pedro Alves  <palves@redhat.com>

	* dwarf2read.c (try_open_dwop_file, open_dwo_file)
	(file_file_name, file_full_name): Add char * cast to sentinel in
	concat/reconcat calls.
	* event-top.c (top_level_prompt): Likewise.
	* guile/guile.c (initialize_scheme_side): Likewise.
	* linux-tdep.c (linux_fill_prpsinfo): Likewise.
	* macrotab.c (macro_source_fullname): Likewise.
	* main.c (get_init_files, captured_main): Likewise.
	* psymtab.c (psymtab_to_fullname): Likewise.
	* python/python.c (_initialize_python)
	(gdbpy_finish_initialization): Likewise.
	* source.c (symtab_to_fullname): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix s390 GNU/Linux gdb and gdbserver builds
@ 2016-04-21 11:15 sergiodj+buildbot
  2016-04-21 12:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-21 11:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3451269c4128c4b74f4614d9781cb75207c5ee34 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3451269c4128c4b74f4614d9781cb75207c5ee34

Fix s390 GNU/Linux gdb and gdbserver builds

Now that gdb/gdbserver compile as C++ programs by default, the s390
GNU/Linux build started failing with:

 In file included from ../../src/gdb/common/common-defs.h:64:0,
		  from ../../src/gdb/defs.h:28,
		  from ../../src/gdb/s390-linux-nat.c:22:
 ../../src/gdb/s390-linux-nat.c: In function void fetch_regset(regcache*, int, int, int, const regset*):
 ../../src/gdb/../include/libiberty.h:711:38: error: invalid conversion from void* to gdb_byte* {aka unsigned char*} [-fpermissive]
  # define alloca(x) __builtin_alloca(x)
				       ^
 ../../src/gdb/s390-linux-nat.c:297:19: note: in expansion of macro alloca
    gdb_byte *buf = alloca (regsize);
		    ^

etc.

gdb/ChangeLog:
2016-04-21  Pedro Alves  <palves@redhat.com>

	* s390-linux-nat.c (fetch_regset, store_regset, check_regset): Use
	void * instead of gdb_byte *.

gdb/gdbserver/ChangeLog:
2016-04-21  Pedro Alves  <palves@redhat.com>

	* linux-s390-low.c (s390_collect_ptrace_register)
	(s390_supply_ptrace_register, s390_get_hwcap): Use gdb_byte * and
	add casts.
	(s390_check_regset): Use void * instead of gdb_byte *.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix AIX gdb build with C++ compiler
@ 2016-04-21 13:06 sergiodj+buildbot
  2016-04-21 13:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-21 13:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71829b1a3f9b4825150747b138b5cfadf0c5fcba ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 71829b1a3f9b4825150747b138b5cfadf0c5fcba

Fix AIX gdb build with C++ compiler

We currently get:

 ../../src/gdb/aix-thread.c: In function 'int pdc_read_data(pthdb_user_t, void*, pthdb_addr_t, size_t)':
 ../../src/gdb/aix-thread.c:465:46: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
    status = target_read_memory (addr, buf, len);
					       ^


 ../../src/gdb/aix-thread.c: In function 'void aix_thread_resume(target_ops*, ptid_t, int, gdb_signal)':
 ../../src/gdb/aix-thread.c:1010:46: error: invalid conversion from 'void*' to 'int*' [-fpermissive]
	 gdb_signal_to_host (sig), (void *) tid);
					       ^
 ../../src/gdb/aix-thread.c:243:1: error:   initializing argument 5 of 'int ptrace64aix(int, int, long long int, int, int*)' [-fpermissive]
  ptrace64aix (int req, int id, long long addr, int data, int *buf)


 ../../src/gdb/rs6000-nat.c: In function 'gdb_byte* rs6000_ptrace_ldinfo(ptid_t)':
 ../../src/gdb/rs6000-nat.c:596:36: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
    gdb_byte *ldi = xmalloc (ldi_size);
				     ^
 ../../src/gdb/rs6000-nat.c:615:36: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
	ldi = xrealloc (ldi, ldi_size);
				     ^

(and more instances of the same).

gdb/ChangeLog:
2016-04-21  Pedro Alves  <palves@redhat.com>

	* aix-thread.c (pdc_read_data, pdc_write_data): Add cast.
	(aix_thread_resume): Use PTRACE_TYPE_ARG5.
	* rs6000-nat.c (rs6000_ptrace64): Use PTRACE_TYPE_ARG5.
	(rs6000_ptrace_ldinfo): Change type of 'ldi' local to void
	pointer, and cast return to gdb_byte pointer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for non-ELF targets to check their relocs.
@ 2016-04-21 14:48 sergiodj+buildbot
  2016-04-21 15:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-21 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f3b23b390640efdc36c575dbda2175e61154bc9 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4f3b23b390640efdc36c575dbda2175e61154bc9

Add support for non-ELF targets to check their relocs.

bfd	* aout-adobe.c: Use _bfd_generic_link_check_relocs.
	* aout-target.h: Likewise.
	* aout-tic30.c: Likewise.
	* binary.c: Likewise.
	* bout.c: Likewise.
	* coff-alpha.c: Likewise.
	* coff-rs6000.c: Likewise.
	* coff64-rs6000.c: Likewise.
	* coffcode.h: Likewise.
	* i386msdos.c: Likewise.
	* i386os9k.c: Likewise.
	* ieee.c: Likewise.
	* ihex.c: Likewise.
	* libbfd-in.h: Likewise.
	* libecoff.h: Likewise.
	* mach-o-target.c: Likewise.
	* mmo.c: Likewise.
	* nlm-target.h: Likewise.
	* oasys.c: Likewise.
	* pef.c: Likewise.
	* plugin.c: Likewise.
	* ppcboot.c: Likewise.
	* som.c: Likewise.
	* srec.c: Likewise.
	* tekhex.c: Likewise.
	* versados.c: Likewise.
	* vms-alpha.c: Likewise.
	* xsym.c: Likewise.
	* elfxx-target.h: Use _bfd_elf_link_check_relocs.
	* linker.c (bfd_link_check_relocs): New function.
	(_bfd_generic_link_check_relocs): New function.
	* targets.c (BFD_JUMP_TABLE_LINK): Add initialization of
	_bfd_link_check_relocs field.
	(struct bfd_target)L Add _bfd_link_check_relocs field.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.

ld	* ldlang.c (lang_check_relocs): Use bfd_link_check_relocs in
	prefernce to _bfd_elf_link_check_relocs.  Drop test for ELF
	targets.  Do not stop the checks when problems are encountered.

include	* bfdlink.h: Add prototype for bfd_link_check_relocs.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Switch gdb's TRY/CATCH to sjlj again
@ 2016-04-21 16:36 sergiodj+buildbot
  2016-04-21 16:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-21 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88c3cd8dcb60606a25a16ea11149219db00f847b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 88c3cd8dcb60606a25a16ea11149219db00f847b

Switch gdb's TRY/CATCH to sjlj again

We don't currently handle the case of gdb's readline callback throwing
gdb C++ exceptions across a readline that wasn't built with
-fexceptions.  The end result is:

 (gdb) whatever-command-that-causes-an-error
 terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'
 Aborted
 $

Until that is fixed, revert back to sjlj-based exceptions again.

gdb/ChangeLog:
2016-04-21  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (GDB_XCPT_TRY): Add comment.
	(GDB_XCPT): Always define as GDB_XCPT_SJMP.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS: Go back with the default Linux # of registers to 90
@ 2016-04-22  0:52 sergiodj+buildbot
  2016-04-22  1:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22  0:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3877922e56a9e44fed0ca72e64cad7578e6b1ed5 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 3877922e56a9e44fed0ca72e64cad7578e6b1ed5

MIPS: Go back with the default Linux # of registers to 90

Set the number of registers for non-XML-described Linux targets to 90,
reverting a change made here with the addition of DSP register support:

commit 1faeff088bbbd037d7769d214378b4faf805fa2e
Author: Maciej W. Rozycki <macro@linux-mips.org>
Date:   Thu Mar 1 22:19:48 2012 +0000

and fixing a regression introduced for legacy `gdbserver' targets
causing a "Remote 'g' packet reply is too long" error message where the
amount of register data received with a `g' packet (90) exceeds the
maximum number of registers expected (79).

Update the setting for XML-described targets, reflecting the actual
number of registers which have been assigned numbers, matching the:

      gdb_assert (gdbarch_num_regs (gdbarch) <= MIPS_RESTART_REGNUM);

requirement in `mips_linux_init_abi'.

	gdb/
	* mips-tdep.c (mips_gdbarch_init): For GDB_OSABI_LINUX set
	`num_regs' to 90 rather than 79.  Where a target description is
	present adjust the setting appropriately.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set dynobj to a normal input file if possible
@ 2016-04-22  2:30 sergiodj+buildbot
  2016-04-22  3:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22  2:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cd255ca1f03550291bd05ac4548e383bca88c5f ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6cd255ca1f03550291bd05ac4548e383bca88c5f

Set dynobj to a normal input file if possible

When check_relocs is called after gc-sections has run,
_bfd_elf_link_create_dynstrtab may be called with an dynamic object
and hash_table->dynobj may be NULL.  We may not set dynobj, an input
file holding linker created dynamic sections to the dynamic object,
which has its own dynamic sections.  We need to find a normal input
file to hold linker created sections if possible.  Otherwise ld will
crash during LTO input rescan when linker created dynamic section
overrides input dynamic section.

	* elflink.c (_bfd_elf_link_create_dynstrtab): Set dynobj to a
	normal input file if possible.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Exclude linker created file from dynobj
@ 2016-04-22  5:18 sergiodj+buildbot
  2016-04-22  5:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22  5:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6645479e9dc9470d22393d5bc4ef2ef2d391e848 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6645479e9dc9470d22393d5bc4ef2ef2d391e848

Exclude linker created file from dynobj

Some ELF targets create a "linker stubs" fake bfd.  Don't use it to
set dynobj.

	* elflink.c (_bfd_elf_link_create_dynstrtab): Exclude linker
	created file from dynobj.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Deliver signal in hardware single step
@ 2016-04-22 11:40 sergiodj+buildbot
  2016-04-22 12:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 11:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b061e98860ad84315704c732a1a43525f494946 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5b061e98860ad84315704c732a1a43525f494946

Deliver signal in hardware single step

GDBserver doesn't deliver signal when stepping over a breakpoint even
hardware single step is used.  When GDBserver started to step over
(thread creation) breakpoint for mutlit-threaded debugging in 2002 [1],
GDBserver behaves this way.

This behavior gets trouble on conditional breakpoints on branch to
self instruction like this,

   0x00000000004005b6 <+29>:	jmp    0x4005b6 <main+29>

and I set breakpoint

$(gdb) break branch-to-self.c:43 if counter > 3

and the variable counter will be set to 5 in SIGALRM signal handler.
Since GDBserver keeps stepping over breakpoint, the SIGALRM can never
be dequeued and delivered to the inferior, so the program can't stop.
The test can be found in gdb.base/branch-to-self.exp.

GDBserver didn't deliver signal when stepping over a breakpoint because
a tracepoint is collected twice if GDBserver does so in the following
scenario, which can be reproduced by gdb.trace/signal.exp.

 - program stops at tracepoint, and tracepoint is collected,
 - gdbserver starts a step-over,
 - a signal arrives, step-over is canceled, and signal should be passed,
 - gdbserver starts a new step-over again, pass the signal as well,
 - program stops at the entry of signal handler, step-over finished,
 - gdbserver proceeds,
 - program returns from the signal handler, again to the tracepoint,
   and thus is collected again.

The spurious collection isn't that harmful, IMO, so it should be OK
to let GDBserver deliver signal when stepping over a breakpoint.

gdb/gdbserver:

2016-04-22  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (lwp_signal_can_be_delivered): Don't deliver
	signal when stepping over breakpoint with software single
	step.

gdb/testsuite:

2016-04-22  Yao Qi  <yao.qi@linaro.org>

	* gdb.trace/signal.exp: Also pass if
	$tracepoint_hits($i) > $iterations.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [obv] [PR gdb/19980] Typo in gdbserver/configure.srv
@ 2016-04-22 12:44 sergiodj+buildbot
  2016-04-22 13:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 12:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7915f48c28e24927d2842cc66ad001947776dcd8 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 7915f48c28e24927d2842cc66ad001947776dcd8

[obv] [PR gdb/19980] Typo in gdbserver/configure.srv

Simple exchange of mpx-avx for avx-mpx.
Other occurrences were not found.

2016-04-22  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/gdbserver/ChangeLog:

	* configure.srv (srv_amd64_xmlfiles): Exchange
	i386/amd64-mpx-avx.xml for i386/amd64-avx-mpx.xml.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Joel Brobecker stepping down as AIX Maintainer
@ 2016-04-22 14:40 sergiodj+buildbot
  2016-04-22 14:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f60e29b5a13066f7625dfeadcc329aeefd9d5a5 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 0f60e29b5a13066f7625dfeadcc329aeefd9d5a5

Joel Brobecker stepping down as AIX Maintainer

gdb/ChangeLog:

        * MAINTAINERS: Remove myself as AIX Maintainer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix fail in gdb.base/annota1.exp and gdb.base/annota3.exp
@ 2016-04-22 15:00 sergiodj+buildbot
  2016-04-22 15:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 495346f6f07ea711662106f0e6f8d684fe489cd8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 495346f6f07ea711662106f0e6f8d684fe489cd8

Fix fail in gdb.base/annota1.exp and gdb.base/annota3.exp

Hi,

I am seeing the fail below on aarch64-linux with gcc 4.9.2,

break main
Breakpoint 1 at 0x4006e8: file binutils-gdb/gdb/testsuite/gdb.base/annota1.c, line 14.^M
(gdb) FAIL: gdb.base/annota1.exp: breakpoint main

the test expects the breakpoint is set on line 15.  Let us look at
the main function,

12	int
13	main (void)
14	{
15	  int my_array[3] = { 1, 2, 3 };  /* break main */
16
17	  value = 7;
18
19	#ifdef SIGUSR1
20	  signal (SIGUSR1, handle_USR1);
21	#endif

(gdb) disassemble main
Dump of assembler code for function main:
   0x00000000004006e0 <+0>:	stp	x29, x30, [sp,#-48]!
   0x00000000004006e4 <+4>:	mov	x29, sp
   0x00000000004006e8 <+8>:	adrp	x0, 0x411000 <signal@got.plt>
   0x00000000004006ec <+12>:	add	x0, x0, #0x40

the breakpoint is set on the right address after skipping prologue, but
0x00000000004006e8 is mapped to the line 14, as shown below,

(gdb) maintenance info line-table
objfile: /home/yao.qi/source/build-aarch64/gdb/testsuite/outputs/gdb.base/annota1/annota1 ((struct objfile *) 0x2b0e1850)
compunit_symtab: ((struct compunit_symtab *) 0x2b0ded50)
symtab: /home/yao.qi/source/binutils-gdb/gdb/testsuite/gdb.base/annota1.c ((struct symtab *) 0x2b0dedd0)
linetable: ((struct linetable *) 0x2b12c8b0):
INDEX    LINE ADDRESS
0           7 0x00000000004006d0
1           8 0x00000000004006d8
2          14 0x00000000004006e0
3          14 0x00000000004006e8
4          15 0x00000000004006fc

so GDB does nothing wrong.  Program hits breakpoint on either line 14
or line 15 is right to me.  With anther gcc (4.9.3), the line-table looks
correct, and no test fail.  Instead of setting breakpoint on main and
assuming the line is what we get from the source, we can set breakpoint
on that line.  On the other hand, the test prints the values of the
array and check, so we need to set breakpoint on the line setting the
values of array and "next", rather than setting the breakpoint on main.

gdb/testsuite:

2016-04-22  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/annota1.exp: Set breakpoint on line $main_line.
	* gdb.base/annota3.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] Clear reserved bits in CPSR
@ 2016-04-22 15:39 sergiodj+buildbot
  2016-04-22 16:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3539aa13fbcadd930b0b6d8a97f9f125f02a73dc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3539aa13fbcadd930b0b6d8a97f9f125f02a73dc

[ARM] Clear reserved bits in CPSR

Bits 20 ~ 23 of CPSR are reserved (RAZ, read as zero), but they are not
zero if the arm program runs on aarch64-linux.  AArch64 tracer gets PSTATE
from arm 32-bit tracee as CPSR, but bits 20 ~ 23 are used in PSTATE.  I
think kernel should clear these bits when it is read through ptrace, but
the fix in user space is still needed.

This patch fixes these two fails,

-FAIL: gdb.reverse/insn-reverse.exp: ext_reg_push_pop: compare registers on insn 0:vldr	d7, [r11, #-12]
-FAIL: gdb.reverse/insn-reverse.exp: ext_reg_push_pop: compare registers on insn 0:vldr	d7, [r7]

gdb:

2016-04-22  Yao Qi  <yao.qi@linaro.org>

	* aarch32-linux-nat.c (aarch32_gp_regcache_supply): Clear CPSR
	bits 20 to 23.

gdb/gdbserver:

2016-04-22  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.c (arm_store_gregset): Clear CPSR bits 20
	to 23.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Rename rl_callback_read_char_wrapper -> gdb_rl_callback_read_char_wrapper
@ 2016-04-22 16:05 sergiodj+buildbot
  2016-04-22 17:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c610247abdf7fd6d22d21f11552d223be1e12cd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3c610247abdf7fd6d22d21f11552d223be1e12cd

Rename rl_callback_read_char_wrapper -> gdb_rl_callback_read_char_wrapper

Use the "gdb_rl_" prefix like other gdb readline function wrappers to
make it clear this is a gdb function, not a readline function.

gdb/ChangeLog:
2016-04-22  Pedro Alves  <palves@redhat.com>

	* event-top.c (rl_callback_read_char_wrapper): Rename to ...
	(gdb_rl_callback_read_char_wrapper): ... this.
	(change_line_handler, gdb_setup_readline): Adjust.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CATCH
@ 2016-04-22 16:34 sergiodj+buildbot
  2016-04-22 17:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 89525768cd086a0798a504c81fdf7ebcd4c904e1 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 89525768cd086a0798a504c81fdf7ebcd4c904e1

Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CATCH

If we map GDB'S TRY/CATCH macros to C++ try/catch, GDB breaks on
systems where readline isn't built with exceptions support.  The
problem is that readline calls into GDB through the callback
interface, and if GDB's callback throws a C++ exception/error, the
system unwinder won't manage to unwind past the readline frame, and
ends up calling std::terminate(), which aborts the process:

 (gdb) whatever-command-that-causes-an-error
 terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR'
 Aborted
 $

This went unnoticed for so long because:

- the x86-64 ABI requires -fasynchronous-unwind-tables, making it
  possible for exceptions to cross readline with no special handling.
  But e.g., on ARM or AIX, unless you build readline with
  -fexceptions, you trip on the problem.

- TRY/CATCH was mapped to setjmp/longjmp, even in C++ mode, until
  quite recently.

The fix is to catch and save any GDB exception that is thrown inside
the GDB readline callback, and then once the callback returns back to
the GDB code that called into readline in the first place, rethrow the
saved GDB exception.

This is similar in spirit to how we catch/map GDB exceptions at the
GDB/Python and GDB/Guile API boundaries.

The next question is then: if we intercept all exceptions within GDB's
readline callback, should we simply return normally to readline?  The
callback prototype has no way to signal an error back to readline (*).
The answer is no -- if we return normally, we'll be returning to a
loop inside rl_callback_read_char that continues processing pending
input, calling into GDB again, redisplaying the prompt, etc.  Thus if
we want to error out of rl_callback_read_char, we need to long jump
across it, just like we always did before TRY/CATCH were ever mapped
to C++ exceptions.

My first approach built a specialized API to handle this, with a
couple macros to hide the setjmp/longjmp and the struct gdb_exception
saving/rethrowing.

However, I realized that we need to:

 - Handle multiple active rl_callback_read_char invocations.  If,
   while processing input something triggers a secondary prompt, we
   end up in a nested rl_callback_read_char call, through
   gdb_readline_wrapper.

 - Propagate a struct gdb_exception along with the longjmp.

... and that this is exactly what the setjmp/longjmp-based TRY/CATCH
does.

So the fix makes the setjmp/longjmp TRY/CATCH always available under
new TRY_SJLJ/CATCH_SJLJ aliases, even when TRY/CATCH is mapped to C++
try/catch, and then uses TRY_SJLJ/CATCH_SJLJ to propagate GDB
exceptions across the readline callback.

This turns out to be a much better looking fix than my bespoke API
attempt, even.  We'll probably be able to simplify TRY_SJLJ/CATCH_SJLJ
when we finally get rid of TRY/CATCH all over the tree, but until
then, this reuse seems quite nice for avoiding a second parallel
setjmp/longjmp mechanism.

(*) - maybe we could propose a readline API change, but we still need
      to handle current readline, anyway.

gdb/ChangeLog:
2016-04-22  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.c (enum catcher_state, struct catcher)
	(current_catcher): Define in C++ mode too.
	(exceptions_state_mc_catch): Call throw_exception_sjlj instead of
	throw_exception.
	(throw_exception_sjlj, throw_exception_cxx): New functions,
	factored out from throw_exception.
	(throw_exception): Reimplement.
	* common/common-exceptions.h (exceptions_state_mc_init)
	(exceptions_state_mc_action_iter)
	(exceptions_state_mc_action_iter_1, exceptions_state_mc_catch):
	Declare in C++ mode too.
	(TRY): Rename to ...
	(TRY_SJLJ): ... this.
	(CATCH): Rename to ...
	(CATCH_SJLJ): ... this.
	(END_CATCH): Rename to ...
	(END_CATCH_SJLJ): ... this.
	[GDB_XCPT == GDB_XCPT_SJMP] (TRY, CATCH, END_CATCH): Map to SJLJ
	equivalents.
	(throw_exception): Update comments.
	(throw_exception_sjlj): Declare.
	* event-top.c (gdb_rl_callback_read_char_wrapper): Extend intro
	comment.  Wrap body in TRY_SJLJ/CATCH_SJLJ and rethrow any
	intercepted exception.
	(gdb_rl_callback_handler): New function.
	(gdb_rl_callback_handler_install): Always install
	gdb_rl_callback_handler as readline callback.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Switch gdb's TRY/CATCH to C++ try/catch
@ 2016-04-22 17:51 sergiodj+buildbot
  2016-04-22 18:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 17:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6290672f89d5638a9da5ce10b2f4ba793dcc6396 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6290672f89d5638a9da5ce10b2f4ba793dcc6396

Switch gdb's TRY/CATCH to C++ try/catch

The exceptions-across-readline issue was fixed by the previous commit.
Let's try this again.

gdb/ChangeLog:
2016-04-22  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (GDB_XCPT_TRY): Remove mention of
	the foreign frames issue.
	[__cplusplus] (GDB_XCPT): Define as GDB_XCPT_TRY.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Centralize yacc interface names remapping (yyparse, yylex, yyerror, etc)
@ 2016-04-22 18:39 sergiodj+buildbot
  2016-04-22 19:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3f11165aad39586cca0352ed5fe32b721699c76 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b3f11165aad39586cca0352ed5fe32b721699c76

Centralize yacc interface names remapping (yyparse, yylex, yyerror, etc)

This factors out all the yy-variables remapping to a single file,
instead of each parser having to do the same, with different prefixes.

With this, a parser just needs to define the prefix they want and
include yy-remap.h, which does the dirty job.

Note this renames the c_error, ada_error, etc. functions.  Writing the
remapping pattern as:

 #define yyerror GDB_YY_REMAP (error)

instead of:

 #define yyerror GDB_YY_REMAP (yyerror)

would have avoided the renaming.  However, that would be problematic
if we have a macro 'foo' in scope, when we write:

 #define yyfoo GDB_YY_REMAP (foo)

as that would expand 'foo'.

The c_yyerror etc. naming end ups indicating that this is a yacc
related function more clearly, so feels like a good change, anyway.

gdb/ChangeLog:
2016-04-22  Pedro Alves  <palves@redhat.com>

	* ada-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* ada-lang.c (ada_language_defn): Adjust.
	* ada-lang.h (ada_error): Rename to ...
	(ada_yyerror): ... this.
	* c-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* c-lang.c (c_language_defn, cplus_language_defn)
	(asm_language_defn, minimal_language_defn): Adjust.
	* c-lang.h (c_error): Rename to ...
	(c_yyerror): ... this.
	* d-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* d-lang.c (d_language_defn): Adjust.
	* d-lang.h (d_error): Rename to ...
	(d_yyerror): ... this.
	* f-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* f-lang.c (f_language_defn): Adjust.
	* f-lang.h (f_error): Rename to ...
	(f_yyerror): ... this.
	* go-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* go-lang.c (go_language_defn): Adjust.
	* go-lang.h (go_error): Rename to ...
	(go_yyerror): ... this.
	* jv-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* jv-lang.c (java_language_defn): Adjust.
	* jv-lang.h (java_error): Rename to ...
	(java_yyerror): ... this.
	* m2-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* m2-lang.c (m2_language_defn): Adjust.
	* m2-lang.h (m2_error): Rename to ...
	(m2_yyerror): ... this.
	* objc-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* objc-lang.c (objc_language_defn): Adjust.
	* opencl-lang.c (opencl_language_defn): Adjust.
	* p-exp.y: Remove all yy symbol remappings.
	(GDB_YY_REMAP_PREFIX): Define.
	Include "yy-remap.h".
	* p-lang.c (pascal_language_defn): Adjust.
	* p-lang.h (pascal_error): Rename to ...
	(pascal_yyerror): ... this.
	* yy-remap.h: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix fails in gdb.trace/unavailable.exp
@ 2016-04-22 19:48 sergiodj+buildbot
  2016-04-22 21:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a5d52f0ec8dd56b7953764a9bc1dc71ff6b69ca ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0a5d52f0ec8dd56b7953764a9bc1dc71ff6b69ca

Fix fails in gdb.trace/unavailable.exp

I am seeing some test fails in gdb.trace/unavailable.exp on aarch64-linux,
like this,

print derived_whole^M
$43 = (Derived) {<Middle> = {<Base> = {x = 2}, _vptr.Middle = 0x401860 <VTT for Derived>, y = 3}, _vptr.Derived = 0x401848 <vtable for Derived+32>, z = 4}^M
(gdb) FAIL: gdb.trace/unavailable.exp: collect globals: print object on: print derived_whole

print derived_whole^M
$47 = {<Middle> = {<Base> = {x = 2}, _vptr.Middle = 0x401860 <VTT for Derived>, y = 3}, _vptr.Derived = 0x401848 <vtable for Derived+32>, z = 4}^M
(gdb) FAIL: gdb.trace/unavailable.exp: collect globals: print object off: print derived_whole

these fails are also found by recent x86_64-linux buildbot,
https://sourceware.org/ml/gdb-testers/2016-q2/msg00622.html

The fix is exactly the same as this one
http://www.sourceware.org/ml/gdb-patches/2015-10/msg00252.html (the
extra "VTT" after hex), in which we match extra things after $hex.

gdb/testsuite:

2016-04-22  Yao Qi  <yao.qi@linaro.org>

	* gdb.trace/unavailable.exp (gdb_collect_globals_test_1): Match
	more after $hex.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip if size of bfd_vma is smaller than address size
@ 2016-04-23 17:00 sergiodj+buildbot
  2016-04-23 17:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-23 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0f92bf9430546707f2154b8a2656974e5c7093c ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c0f92bf9430546707f2154b8a2656974e5c7093c

Skip if size of bfd_vma is smaller than address size

Disassembler won't work properly when size of bfd_vma is smaller than
address size.

	PR binutils/19983
	PR binutils/19984
	* i386-dis.c (print_insn): Return -1 if size of bfd_vma is
	smaller than address size.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Force to insert software single step breakpoint
@ 2016-04-25  8:34 sergiodj+buildbot
  2016-04-25  8:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-25  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21edc42f4e1ec6fe8cfce171232bab27ad4af372 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 21edc42f4e1ec6fe8cfce171232bab27ad4af372

Force to insert software single step breakpoint

GDB doesn't insert software single step breakpoint if the instruction
branches to itself, so that the program can't stop after command "si".

(gdb) b 32
Breakpoint 2 at 0x8680: file git/gdb/testsuite/gdb.base/branch-to-self.c, line 32.
(gdb) c
Continuing.

Breakpoint 2, main () at gdb/git/gdb/testsuite/gdb.base/branch-to-self.c:32
32	  asm (".Lhere: " BRANCH_INSN " .Lhere"); /* loop-line */
(gdb) si
infrun: clear_proceed_status_thread (Thread 3991.3991)
infrun: proceed (addr=0xffffffff, signal=GDB_SIGNAL_DEFAULT)
infrun: step-over queue now empty
infrun: resuming [Thread 3991.3991] for step-over
infrun: skipping breakpoint: stepping past insn at: 0x8680
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sending packet: $Z0,8678,4#f3...Packet received: OK
infrun: skipping breakpoint: stepping past insn at: 0x8680
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sending packet: $Z0,b6fe86c8,4#82...Packet received: OK
infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=1, current thread [Thread 3991.3991] at 0x868

breakpoint.c:should_be_inserted thinks the breakpoint shouldn't be
inserted, which is wrong.  This patch restrict the condition that
only skip the non-single-step breakpoints if they are inserted at
the place we are stepping over, however we don't want to skip
single-step breakpoint if its thread is the thread we are stepping
over, so in this patch, I add a thread num in 'struct step_over_info'
to record the thread we're stepping over.

gdb:

2016-04-25  Yao Qi  <yao.qi@linaro.org>

	* breakpoint.c (should_be_inserted): Return 0 if the location's
	owner is not single step breakpoint or single step breakpoint's
	thread isn't the thread which is stepping past a breakpoint.
	* gdbarch.sh (software_single_step): Update comments.
	* gdbarch.h: Regenerated.
	* infrun.c (struct step_over_info) <thread>: New field.
	(set_step_over_info): New argument 'thread'.  Callers updated.
	(clear_step_over_info): Set field thread to -1.
	(thread_is_stepping_over_breakpoint): New function.
	* infrun.h (thread_is_stepping_over_breakpoint): Declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Insert breakpoint even when the raw breakpoint is found
@ 2016-04-25  9:03 sergiodj+buildbot
  2016-04-25  9:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-25  9:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20249ae4551ae7b2193caed73d9ce8d594f38754 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 20249ae4551ae7b2193caed73d9ce8d594f38754

Insert breakpoint even when the raw breakpoint is found

When GDBserver inserts a breakpoint, it looks for raw breakpoint, if
the raw breakpoint is found, increase its refcount, and return.  This
doesn't work when it steps over a breakpoint using software single
step and the underneath instruction of breakpoint is branch to self.

When stepping over a breakpoint on ADDR using software single step,
GDBserver uninsert the breakpoint, so the corresponding raw breakpoint
RAW's 'inserted' flag is zero.  Then, GDBserver insert single step
breakpoint at the same address ADDR because the instruction is branch
to self, the same raw brekapoint RAW is found, and increase the
refcount.  However, the raw breakpoint is not inserted, and the
program won't stop.

gdb/gdbserver:

2016-04-25  Pedro Alves  <palves@redhat.com>
	    Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (set_raw_breakpoint_at): Create a raw breakpoint
	object.  Insert it if it is not inserted yet.  Increase the
	refcount and link it into the proc's raw breakpoint list.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [GDBserver] Don't error in reinsert_raw_breakpoint if bp->inserted
@ 2016-04-25  9:46 sergiodj+buildbot
  2016-04-25 10:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-25  9:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85ba7d867af39fe1408accd1f9ea4ca3dcb84b99 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 85ba7d867af39fe1408accd1f9ea4ca3dcb84b99

[GDBserver] Don't error in reinsert_raw_breakpoint if bp->inserted

GDBserver steps over a breakpoint while the single step breakpoint
is inserted at the same address, there are two breakpoint objects
using single raw breakpoint, which is inserted (for single step).
When step over is finished, GDBserver reinsert the breakpoint, but
it finds the raw breakpoint is already inserted, and error out
"Breakpoint already inserted at reinsert time."  Even if I change the
order to delete reinsert breakpoints first (which only decreases the
refcount, but leave inserted flag unchanged), the error is still
there.

The fix is to remove the error and return instead.

gdb/gdbserver:

2016-04-25  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (reinsert_raw_breakpoint): If bp->inserted is true
	return instead of error.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Always count the NULL entry in dynamic symbol table
@ 2016-04-26 11:09 sergiodj+buildbot
  2016-04-26 11:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-26 11:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5486c43728b4fa17c111a301c30a1e072eaec6a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d5486c43728b4fa17c111a301c30a1e072eaec6a

Always count the NULL entry in dynamic symbol table

There is an unused NULL entry at the head of dynamic symbol table which
we must account for in our count even if the table is empty or unused
since it is intended for the mandatory DT_SYMTAB tag (.dynsym section)
in .dynamic section.

	* elf-bfd.h (elf_link_hash_table): Update comments for
	dynsymcount.
	* elflink.c (_bfd_elf_link_renumber_dynsyms): Always count for
	the unused NULL entry at the head of dynamic symbol table.
	(bfd_elf_size_dynsym_hash_dynstr): Remove dynsymcount != 0
	checks.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] fort_dyn_array: Enable dynamic member types inside a structure.
@ 2016-04-26 14:47 sergiodj+buildbot
  2016-04-26 14:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-26 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9920b4348edbdd83e3f91c85d7174cb92bba204d ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 9920b4348edbdd83e3f91c85d7174cb92bba204d

fort_dyn_array: Enable dynamic member types inside a structure.

Fortran supports dynamic types for which bounds, size and location
can vary during their lifetime. As a result of the dynamic
behaviour, they have to be resolved at every query.
This patch will resolve the type of a structure field when it
is dynamic.

2016-04-26  Bernhard Heckel  <bernhard.heckel@intel.com>
2016-04-26  Keven Boell  <keven.boell@intel.com>

Before:
(gdb) print threev%ivla(1)
Cannot access memory at address 0x3
(gdb) print threev%ivla(5)
no such vector element

After:
(gdb) print threev%ivla(1)
$9 = 1
(gdb) print threev%ivla(5)
$10 = 42

gdb/Changelog:

	* NEWS: Add new supported features for fortran.
	* gdbtypes.c (remove_dyn_prop): New.
	(resolve_dynamic_struct): Keep type length for fortran structs.
	* gdbtypes.h: Forward declaration of new function.
	* value.c (value_address): Return dynamic resolved location of a value.
	(set_value_component_location): Adjust the value address
	for single value prints.
	(value_primitive_field): Support value types with a dynamic location.
	(set_internalvar): Remove dynamic location property of
	internal variables.

gdb/testsuite/Changelog:

	* gdb.fortran/vla-type.f90: New file.
	* gdb.fortran/vla-type.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] fort_dyn_array: Use value constructor instead of raw-buffer manipulation.
@ 2016-04-26 15:59 sergiodj+buildbot
  2016-04-26 16:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-26 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e2e34f8623d9eeb6710d8f3883f26af8b07bbd1 ***

Author: Keven Boell <keven.boell@intel.com>
Branch: master
Commit: 3e2e34f8623d9eeb6710d8f3883f26af8b07bbd1

fort_dyn_array: Use value constructor instead of raw-buffer manipulation.

Instead of pre-computing indices into a fortran array re-use
the value_* interfaces to subscript a fortran array.
The benefit of using the new interface is that it takes care of
dynamic types and resolve them when needed.
This fixes issues when printing structures with dynamic arrays from toplevel.

Before:
(gdb) p twov
$1 = ( (( ( 6352320, 0, -66, -1, 267) ( 343476, 1, -15, 1, 0) ( 5, 0, 5, 0, 1) ...

After:
(gdb) p twov
$1 = ( (( ( 1, 1, 1, 1, 1) ( 1, 1, 321, 1, 1) ( 1, 1, 1, 1, 1) ...

2016-04-26  Sanimir Agovic  <sanimir.agovic@intel.com>
            Keven Boell  <keven.boell@intel.com>
            Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* f-valprint.c (f77_create_arrayprint_offset_tbl): Remove
	function.
	(F77_DIM_SIZE, F77_DIM_OFFSET): Remove macro.
	(f77_print_array_1): Use value_subscript to subscript a
	value array.
	(f77_print_array): Remove call to f77_create_arrayprint_offset_tbl.
	(f_val_print): Use value_field to construct a field value.

gdb/testsuite/Changelog:
	* vla-type.exp: Print structure from toplevel.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] add casts to avoid arithmetic on void *
@ 2016-04-27  0:26 sergiodj+buildbot
  2016-04-27  2:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28cc9170c3d0bc0c5e82b45a10015e4bbcb01125 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 28cc9170c3d0bc0c5e82b45a10015e4bbcb01125

add casts to avoid arithmetic on void *

arithmetic on void * is undefined in ISO C, so we should avoid it.  In
GNU C sizeof void * is defined as 1, and that is pretty clearly what
this code wants, so change it to do arithmetic on bfd_byte *.
Unfortunately most of the argument types come from virtual function
interfaces so changing the types to bfd_byte * isn't trivial though it
might make the code clearer.  So for the moment its easiest to leave the
variable types as void * and cast before doing arithmetic.

bfd/ChangeLog:

2016-04-26  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-rx.c (rx_set_section_contents): Avoid arithmetic on void *.
	* mmo.c (mmo_get_section_contents): Likewise.
	(mmo_set_section_contents): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Cache result of scan for __start_* and __stop_* sections
@ 2016-04-27  7:52 sergiodj+buildbot
  2016-04-27  8:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27  7:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6a4679fc0ad12e99e0d8374752ecce9ef097ec2 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: a6a4679fc0ad12e99e0d8374752ecce9ef097ec2

Cache result of scan for __start_* and __stop_* sections

include/
	* bfdlink.h (struct bfd_link_hash_entry): Add "section" field to
	undef.  Formatting.
bfd/
	* elflink.c (_bfd_elf_is_start_stop): New function.
	(_bfd_elf_gc_mark_rsec): Use it.
	* elf-bfd.h (_bfd_elf_is_start_stop): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for the --trace-decode option to the AArch64 simulator.
@ 2016-04-27 10:52 sergiodj+buildbot
  2016-04-27 11:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2cdad34c4fba2c6319584d6bb42b84020a9244ac ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 2cdad34c4fba2c6319584d6bb42b84020a9244ac

Add support for the --trace-decode option to the AArch64 simulator.

	* simulator.c: Add TRACE_DECODE statements to all emulation
	functions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix a typo in the check for SNANs in the RX simulator.
@ 2016-04-27 12:00 sergiodj+buildbot
  2016-04-27 12:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 12:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7881f69ee902b06433f071fd8cbdee1b401c9b76 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 7881f69ee902b06433f071fd8cbdee1b401c9b76

Fix a typo in the check for SNANs in the RX simulator.

	PR target/20000
	* fpu.c (check_exceptions): Fix typo checking for signalling
	NANs.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] c_value_print: Revert 'val' to a reference for TYPE_CODE_STRUCT
@ 2016-04-27 15:34 sergiodj+buildbot
  2016-04-27 15:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 476350ba4800f1144b125f6511a5e25b223cc90b ***

Author: Martin Galvan <martin.galvan@tallertechnologies.com>
Branch: master
Commit: 476350ba4800f1144b125f6511a5e25b223cc90b

c_value_print: Revert 'val' to a reference for TYPE_CODE_STRUCT

Currently c_value_print will turn struct reference values into pointers before
doing a set of RTTI checks.  This was introduced as a fix to PR c++/15401.
If there's RTTI the pointer will be adjusted and converted back to a reference.
However, if there's no RTTI the value will still be treated as a pointer during
the remainder of the function.
This patch moves the conversion down so that it's always performed when needed.

Notice this currently has not user-visible effects, so can be seen as a small
code cleanup.  However, it'll be necessary for the bug-fix for handling
synthetic C++ references.  It causes no testsuite regressions.

gdb/ChangeLog:
2016-04-26  Martin Galvan  <martin.galvan@tallertechnologies.com>

	* c-valprint.c (c_value_print): Always convert val back to reference
	type if we converted it to a pointer type.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip gdb.base/branch-to-self.exp if gdb, nosignals exists
@ 2016-04-27 15:46 sergiodj+buildbot
  2016-04-27 17:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 15:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11cf4ffb5e256d268a8f4cea0fc88a0a46bf824c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 11cf4ffb5e256d268a8f4cea0fc88a0a46bf824c

Skip gdb.base/branch-to-self.exp if gdb,nosignals exists

I get a timeout fail in branch-to-self.exp when it is compiled by a
bare-mental target running qemu, which doesn't have signal.

The test should be skipped if gdb,nosignals exists, and that is
what this patch does.

gdb/testsuite:

2016-04-27  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/branch-to-self.exp: Skip it if gdb,nosignals
	exists.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip debug sections when estimating distances
@ 2016-04-27 16:28 sergiodj+buildbot
  2016-04-27 18:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91f8bf69a526912f86da81070407bba6a050e27f ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 91f8bf69a526912f86da81070407bba6a050e27f

Skip debug sections when estimating distances

Skip debug sections when estimating distances between output sections
since compressed_size is used to compress debug sections and debug
sections aren't excluded from distances between output sections.

bfd/

	PR ld/20006
	* elf64-x86-64.c (elf_x86_64_convert_load): Skip debug sections
	when estimating distances between output sections.

ld/

	PR ld/20006
	* testsuite/ld-elfvsb/elfvsb.exp (COMPRESS_LDFLAG): New.
	(visibility_run): Pass COMPRESS_LDFLAG to visibility_test on
	ELF targets.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Workaround gdbserver<7.7 for setfs
@ 2016-04-27 19:55 sergiodj+buildbot
  2016-04-27 19:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 19:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57809e5e5a506664eb54433ded81ab0785168a83 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 57809e5e5a506664eb54433ded81ab0785168a83

Workaround gdbserver<7.7 for setfs

With current FSF GDB HEAD and old FSF gdbserver I expected I could do:
	gdb -ex 'file target:/root/redhat/threadit' -ex 'target remote :1234'
(supplying that unsupported qXfer:exec-file:read by "file")
But that does not work because:
	Sending packet: $vFile:setfs:0#bf...Packet received: OK
	Packet vFile:setfs (hostio-setfs) is supported
	...
	Sending packet: $vFile:setfs:104#24...Packet received: OK
	"target:/root/redhat/threadit": could not open as an executable file: Invalid argument

GDB documentation says:
	The valid responses to Host I/O packets are:
	An empty response indicates that this operation is not recognized.

This "empty response" vs. "OK" was a bug in gdbserver < 7.7.  It was fixed by:
	commit e7f0d979dd5cc4f8b658df892e93db69d6d660b7
	Author: Yao Qi <yao@codesourcery.com>
	Date:   Tue Dec 10 21:59:20 2013 +0800
	    Fix a bug in matching notifications.
	Message-ID: <1386684626-11415-1-git-send-email-yao@codesourcery.com>
	https://sourceware.org/ml/gdb-patches/2013-12/msg00373.html
	2013-12-10  Yao Qi  <yao@codesourcery.com>
		* notif.c (handle_notif_ack): Return 0 if no notification
		matches.

with unpatched old FSF gdbserver and patched FSF GDB HEAD:
	gdb -ex 'file target:/root/redhat/threadit' -ex 'target remote :1234'
	Sending packet: $vFile:setfs:0#bf...Packet received: OK
	Packet vFile:setfs (hostio-setfs) is NOT supported
	...
	(gdb) info sharedlibrary
	From                To                  Syms Read   Shared Object Library
	0x00007ffff7ddbae0  0x00007ffff7df627a  Yes (*)     target:/lib64/ld-linux-x86-64.so.2
	0x00007ffff7bc48a0  0x00007ffff7bcf514  Yes (*)     target:/lib64/libpthread.so.0

gdb/ChangeLog
2016-04-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* remote.c (remote_start_remote): Detect PACKET_vFile_setfs.support.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb_load_shlibs return the destination path of the library
@ 2016-04-27 22:25 sergiodj+buildbot
  2016-04-27 22:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fca4cfd9ec8f28d0883cb8bbd55b82aa3418576b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: fca4cfd9ec8f28d0883cb8bbd55b82aa3418576b

Make gdb_load_shlibs return the destination path of the library

This patch makes gdb_load_shlibs return the destination path of the
copied library.  To make the procedure implementation and interface more
straightforward, it also changes it so that it accepts a single shared
library path at the time.  Therefore, calls that are passed multiple
libraries:

  gdb_load_shlibs $lib1 $lib2

must be changed to separate calls:

  gdb_load_shlibs $lib1
  gdb_load_shlibs $lib2

A subtle impact is the solib-search-path handling.  In the former
version, solib-search-path is set using the directory of the first
passed lib (further calls overwrite the value).  In the later version,
the directory of the library passed to the last call to gdb_load_shlibs
remnains.  I don't think that's a problem in practice, since if we had
tests that needed multiple different paths in solib-search-path, they
wouldn't work in the first place.

Changed in v2:

	* Split behavioural and rename changes in two separate patches.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_load_shlibs):  Accept a single argument.  Return
	result of gdb_remote_download.
	* gdb.base/ctxobj.exp: Split gdb_load_shlibs call.
	* gdb.base/dso2dso.exp: Likewise.
	* gdb.base/global-var-nested-by-dso.exp: Likewise.
	* gdb.base/print-file-var.exp: Likewise.
	* gdb.base/shlib-call.exp: Likewise.
	* gdb.base/shreloc.exp: Likewise.
	* gdb.base/solib-overlap.exp: Likewise.
	* gdb.base/solib-weak.exp (do_test): Likewise.
	* gdb.base/unload.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove need_step_over from struct lwp_info
@ 2016-04-28 11:08 sergiodj+buildbot
  2016-04-28 11:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 11:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f166f943f30a91792e8754cbca9d7652fc400aae ***

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

Remove need_step_over from struct lwp_info

Hi,
I happen to see that field need_step_over in struct lwp_info is only
used to print a debug info.  need_step_over is set in linux_wait_1
when breakpoint_here is true, however, we check breakpoint_here too in
need_step_over_p and do the step over.  I think we don't need field
need_step_over, and check breakpoint_here directly in need_step_over_p.

This field was added in this patch
https://sourceware.org/ml/gdb-patches/2010-03/msg00605.html and the code
wasn't changed much since then.

This patch is to remove it.

gdb/gdbserver:

2016-04-28  Yao Qi  <yao.qi@linaro.org>

	* linux-low.h (struct lwp_info) <need_step_over>: Remove.
	* linux-low.c (linux_wait_1): Update.
	(need_step_over_p): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Updated Chinese (simplified) translations for bfd, binutils and gold.
@ 2016-04-28 13:24 sergiodj+buildbot
  2016-04-28 13:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 13:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 786a118cdf1aa33a8c232c63307e6711a0c00dfb ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 786a118cdf1aa33a8c232c63307e6711a0c00dfb

Updated Chinese (simplified) translations for bfd, binutils and gold.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ftrace tests: Use gdb_load_shlib result to lookup IPA in info sharedlibrary
@ 2016-04-28 15:16 sergiodj+buildbot
  2016-04-28 15:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 952ebca5831911a8ef2a79f6e1e7a2c24f71a388 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 952ebca5831911a8ef2a79f6e1e7a2c24f71a388

ftrace tests: Use gdb_load_shlib result to lookup IPA in info sharedlibrary

Some fast tracepoints tests make sure that the in-process agent library
is properly loaded, by searching for the library name in "info
sharedlibrary".

Originally, it would search for the full path.  Since patch "Make ftrace
tests work with remote targets" [1], the "runtime" location of the IPA,
in the standard output directory, is not the same as the original
location, in the gdbserver build directory.  Therefore, the patch
changed the checks:

  gdb_test "info sharedlibrary" ".*${libipa}.*" "IPA loaded"

to

  gdb_test "info sharedlibrary" ".*[file tail ${libipa}].*" "IPA loaded"

so that only the "libinproctrace.so" part would be searched for.
Antoine (in CC) pointed out that I missed some, so I have to update
them.  In the mean time, I noticed that I missed a few test failures:
adding the SONAME to the IPA makes it possible for the test executable
to erroneously pick up libinproctrace.so from /usr/lib if the test
harness failed to put the libinproctrace.so we want to test in the right
place.  To mitigate that kind of error in the future, we can use the
return value of gdb_load_shlib (the path of the "runtime" version of the
library) and use that to search in the output of info sharedlibrary.

When testing locally, gdb_load_shlib returns the full normalized path of
the destination library, which the test executable should use e.g.:

  /path/to/gdb/testsuite/outputs/gdb.trace/thetest/libinproctrace.so

My testing showed that it was the same path that gdb displayed in info
sharedlibrary.  If the test executable picks up another
libinproctrace.so, the test will fail.

When testing remotely, gdb_load_shlib/gdb_remote_download only returns
us "libinproctrace.so", so the situation doesn't really change.  If
there is a rogue libinproctrace.so in /usr/lib on the target and we fail
to download ours, it might cover up a test failure.  But that situation
is probably still better than the original one, where it wasn't possible
to test remotely using the IPA at all.

[1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=6e774b13c3b81ac2599812adf058796948ce7e95

gdb/testsuite/ChangeLog:

	* gdb.arch/ftrace-insn-reloc.exp: Save gdb_load_shlib result,
	use it in info sharedlibrary test.
	* gdb.trace/ftrace-lock.exp: Likewise.
	* gdb.trace/ftrace.exp: Likewise.
	* gdb.trace/range-stepping.exp: Likewise.
	* gdb.trace/trace-break.exp: Likewise.
	* gdb.trace/trace-condition.exp: Likewise.
	* gdb.trace/trace-mt.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix write endianness/size problem for fast tracepoint enabled flag
@ 2016-04-28 17:19 sergiodj+buildbot
  2016-04-28 17:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35fd2deb6916e972248d52b1bc1d584fa9059f8f ***

Author: Par Olsson <par.olsson@windriver.com>
Branch: master
Commit: 35fd2deb6916e972248d52b1bc1d584fa9059f8f

Fix write endianness/size problem for fast tracepoint enabled flag

I am sending this fix on behalf of Par Olsson, as a follow-up of this
one:

https://www.sourceware.org/ml/gdb-patches/2015-10/msg00196.html

This problem is exposed when enabling/disabling fast tracepoints on big
endian machines.  The flag is defined as an int8_t, but is written from
gdbserver as an integer (usually 32 bits).  When the agent code reads it
as an int8_t, it only considers the most significant byte, which is
always 0.

Also, we were writing 32 bits in an 8 bits field, so the write would
overflow, but since the following bytes are padding (the next field is
an uint64_t), it luckily didn't cause any issue on little endian
systems.

The fix was originally tested on ARM big endian systems, but I don't
have access to such a system.  However, thanks to Marcin's PowerPC fast
tracepoint patches and gcc110 (big endian Power7) on the gcc compile
farm, I was able to reproduce the problem, test the fix and write a
test (the following patch).

gdb/gdbserver/ChangeLog:

YYYY-MM-DD  Par Olsson  <par.olsson@windriver.com>

	* tracepoint.c (write_inferior_int8): New function.
	(cmd_qtenable_disable): Write enable flag using
	write_inferior_int8.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add test for tracepoint enable/disable
@ 2016-04-28 17:38 sergiodj+buildbot
  2016-04-28 18:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 17:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9080ac9d99e5326286a7df806955a326fcd655b2 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 9080ac9d99e5326286a7df806955a326fcd655b2

Add test for tracepoint enable/disable

This patch adds a test for tracepoints enabling/disabling, which
didn't work properly for fast tracepoints on big endian systems.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-enable-disable.exp: New file.
	* gdb.trace/trace-enable-disable.c: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't show deprecated commands in help
@ 2016-04-28 18:29 sergiodj+buildbot
  2016-04-28 19:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-28 18:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0400cf2f56c41896ecf52b88baa1d6178eb10432 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 0400cf2f56c41896ecf52b88baa1d6178eb10432

Don't show deprecated commands in help

Just like completion doesn't show deprecated commands, I think that help
should not list them, so that we don't incite users to use them.

gdb/ChangeLog:

	* cli/cli-decode.c (help_cmd_list): Do not list commands that
	are deprecated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enhance support for copying and stripping Solaris and ARM binaries.
@ 2016-04-29  8:54 sergiodj+buildbot
  2016-04-29  9:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-29  8:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5522f910cb539905d6adfdceab208ddfa5e84557 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 5522f910cb539905d6adfdceab208ddfa5e84557

Enhance support for copying and stripping Solaris and ARM binaries.

	PR 19938
bfd	* elf-bfd.h (struct elf_backend_data): Rename
	elf_backend_set_special_section_info_and_link to
	elf_backend_copy_special_section_fields.
	* elfxx-target.h: Likewise.
	* elf.c (section_match): Ignore the SHF_INFO_LINK flag when
	comparing section flags.
	(copy_special_section_fields): New function.
	(_bfd_elf_copy_private_bfd_data): Copy the EI_ABIVERSION field.
	Perform two scans over special sections.  The first one looks for
	a direct mapping between the output section and an input section.
	The second scan looks for a possible match based upon section
	characteristics.
	* elf32-arm.c (elf32_arm_copy_special_section_fields): New
	function.  Handle setting the sh_link field of SHT_ARM_EXIDX
	sections.
	* elf32-i386.c (elf32_i386_set_special_info_link): Rename to
	elf32_i386_copy_solaris_special_section_fields.
	* elf32-sparc.c (elf32_sparc_set_special_section_info_link):
	Rename to elf32_sparc_copy_solaris_special_section_fields.
	* elf64-x86-64.c (elf64_x86_64_set_special_info_link): Rename to
	elf64_x86_64_copy_solaris_special_section_fields.

binutils* readelf.c (get_solaris_segment_type): New function.
	(get_segment_type): Call it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] X86-64: Set check_relocs_failed on error
@ 2016-04-29 12:01 sergiodj+buildbot
  2016-04-29 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-29 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afd9acee15d55fccf2a25b72c99303f7cbaaa1c2 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: afd9acee15d55fccf2a25b72c99303f7cbaaa1c2

X86-64: Set check_relocs_failed on error

When checking relocations, set check_relocs_failed on error.

	* elf64-x86-64.c (elf_x86_64_check_relocs): Set
	check_relocs_failed on error.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] i386: Don't relocate section when check_relocs failed
@ 2016-04-29 12:43 sergiodj+buildbot
  2016-04-29 13:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-29 12:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c337a1627c7e0edf6d46e66dee513c56975d0625 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c337a1627c7e0edf6d46e66dee513c56975d0625

i386: Don't relocate section when check_relocs failed

No need to relocate section when check_relocs failed.

	* elf32-i386.c (check_relocs_failed): New.
	(elf_i386_check_relocs): Set check_relocs_failed on error.
	(elf_i386_relocate_section): Skip if check_relocs failed.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO
@ 2016-04-29 15:45 sergiodj+buildbot
  2016-04-29 15:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-29 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e62b9723fdfcf655ecbd46ea455567593e333f47 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e62b9723fdfcf655ecbd46ea455567593e333f47

Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO

When UNDEFINED_WEAK_RESOLVED_TO_ZERO is checked to convert load via
GOT, has_got_reloc is always TRUE.  This patch adds GOT_RELOC, which
is TRUE in x86 convert_load, to UNDEFINED_WEAK_RESOLVED_TO_ZERO.

	* elf32-i386.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): Take GOT_RELOC
	and replace (EH)->has_got_reloc with GOT_RELOC.
	(elf_i386_fixup_symbol): Pass has_got_reloc to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.
	(elf_i386_allocate_dynrelocs): Likewise.
	(elf_i386_relocate_section): Likewise.
	(elf_i386_finish_dynamic_symbol): Likewise.
	(elf_i386_convert_load): Pass TRUE to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.
	* elf64-x86-64.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): Take
	GOT_RELOC and replace (EH)->has_got_reloc with GOT_RELOC.
	(elf_x86_64_fixup_symbol): Pass has_got_reloc to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.
	(elf_x86_64_allocate_dynrelocs): Likewise.
	(elf_x86_64_relocate_section): Likewise.
	(elf_x86_64_finish_dynamic_symbol): Likewise.
	(elf_x86_64_convert_load): Pass TRUE to
	UNDEFINED_WEAK_RESOLVED_TO_ZERO.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set interpreter in x86 create_dynamic_sections
@ 2016-04-29 16:02 sergiodj+buildbot
  2016-04-29 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-04-29 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 493f652c956f2037c1c638c1887b634d67da0835 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 493f652c956f2037c1c638c1887b634d67da0835

Set interpreter in x86 create_dynamic_sections

Set interpreter in x86 create_dynamic_sections to make this information
available to x86 check_relocs.

	* elf32-i386.c (elf_i386_size_dynamic_sections): Move interp
	setting to ...
	(elf_i386_create_dynamic_sections): Here.
	* elf64-x86-64.c (elf_x86_64_size_dynamic_sections): Move
	interp setting to ...
	(elf_x86_64_create_dynamic_sections): Here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix annota-input-while-running.exp remote check
@ 2016-05-02 17:20 sergiodj+buildbot
  2016-05-02 17:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-02 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 740feeaa2049d0f9a7e5928191124583a1a8c645 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 740feeaa2049d0f9a7e5928191124583a1a8c645

Fix annota-input-while-running.exp remote check

The comment says that we can't use runto_main here becore it doesn't
know how to handle annotation.  Instead, the test puts a breakpoint at
main and calls run by hand.  Therefore, it can't work with stub targets,
since they can't "run".  The check should be then changed to check the
use_gdb_stub variable instead of [is_remote target].

But as an alternative, we can just use runto_main and enable annotations
after, since the "run to main" part is not really part of what we want
to test.

I also removed the "set test..." line that is unused.

gdb/testsuite/ChangeLog:

	* gdb.base/annota-input-while-running.exp: Don't check for
	[is_remote target].  Enable annotations after running to main.
	Remove unused "set test..." line.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix detach.exp remote check
@ 2016-05-02 18:22 sergiodj+buildbot
  2016-05-02 19:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-02 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 444e826c911693e6dad1cf907d81eb9dc1bef7d2 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 444e826c911693e6dad1cf907d81eb9dc1bef7d2

Fix detach.exp remote check

This test seems to work with both native-gdbserver and
native-extended-gdbserver, so I removed the remote check.

When running with native-gdbserver (a stub-like target), detach makes
gdbserver stop and gdb disconnect.  runto_main just spawns a brand new
gdbserver.  So it tests the exact same thing twice.  It doesn't hurt
though.

With native-extended-gdbserver, the test is probably a bit more useful
(and similar to native).  It tests running/detaching twice using the
same gdb/gdbserver instances, since with extended-remote, you can
detach/attach/run all you want, unlike with remote.

gdb/testsuite/ChangeLog:

	* gdb.base/detach.exp: Remove is_remote check.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [gdb] Fix -Wparentheses warnings
@ 2016-05-03  9:05 sergiodj+buildbot
  2016-05-03  9:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-03  9:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b631e59ba05af7c888838d3e2d6d408bfe60b57f ***

Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Branch: master
Commit: b631e59ba05af7c888838d3e2d6d408bfe60b57f

[gdb] Fix -Wparentheses warnings

2016-05-03  Kyrylo Tkachov  <kyrylo.tkachov@arm.com>

	* symfile.c (find_pc_overlay): Add braces to avoid -Wparentheses
	warning.
	(find_pc_mapped_section): Likewise.
	(list_overlays_command): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix "-Wl,--dynamic-list" gdb/configure test
@ 2016-05-03  9:56 sergiodj+buildbot
  2016-05-03 11:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-03  9:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b4f615e4087a3ae9feba5912312cdcabc25e6a5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1b4f615e4087a3ae9feba5912312cdcabc25e6a5

Fix "-Wl,--dynamic-list" gdb/configure test

The -Wl,--dynamic-list test is currently broken on Fedora 23, when you
configure with --with-python=python3.4.  We see:

 configure:13741: checking for the dynamic export flag
 configure:13796: gcc -o conftest -g3 -O0  -fno-strict-aliasing -DNDEBUG -fwrapv    -Wl,--dynamic-list=/home/pedro/gdb/mygit/src/gdb/proc-service.list conftest.c -ldl -lncurses -lm -ldl  -lpthread -ldl -lutil -lm -lpython3.4m -Xlinker -export-dynamic >&5
 conftest.c:182:30: fatal error: python3.4/Python.h: No such file or directory
 compilation terminated.
 configure:13796: $? = 1

The correct -I path is in PYTHON_CPPFLAGS:

 PYTHON_CPPFLAGS='-I/usr/include/python3.4m -I/usr/include/python3.4m'

(Other Python-related tests in the file are already doing this.)

gdb/ChangeLog:
2016-05-03  Pedro Alves  <palves@redhat.com>

	* configure.ac (checking for the dynamic export flag): Add
	$PYTHON_CPPFLAGS to CPPFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix generation of AArhc64 instruction table.
@ 2016-05-03 11:07 sergiodj+buildbot
  2016-05-03 13:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 11:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20f55f3866ab70778d08fec2c09626cff9ed781d ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 20f55f3866ab70778d08fec2c09626cff9ed781d

Fix generation of AArhc64 instruction table.

	* aarch64-gen.c (VERIFIER): Define.
	* aarch64-opc.c (VERIFIER): Define.
	(verify_ldpsw): Use static linkage.
	* aarch64-opc.h (verify_ldpsw): Remove.
	* aarch64-tbl.h: Use VERIFIER for verifiers.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Also puts value in place for R_AARCH64_RELATIVE
@ 2016-05-03 11:27 sergiodj+buildbot
  2016-05-03 14:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 11:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f56df9d0d5ad89806c24e71f296576d82344613 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 1f56df9d0d5ad89806c24e71f296576d82344613

[AArch64] Also puts value in place for R_AARCH64_RELATIVE

When handling absolute relocations for global symbols bind within the
shared object, AArch64 will generate one dynamic RELATIVE relocation,
but won't apply the value for this absolution relocations at static
linking stage. This is different from AArch64 gold linker and x86-64.

This is not a bug as AArch64 is RELA, there is only guarantee that
relocation addend is placed in the relocation entry.  But some
system softwares originally writen for x86-64 might assume AArch64
bfd linker gets the same behavior as x86-64, then they could take
advantage of this buy skipping those RELATIVE dynamic relocations
if the load address is the same as the static linking address.

This patch makes AArch64 BFD linker applies absolution relocations at
static linking stage for scenario described above.  Meanwhile old AArch64
android loader has a bug (PR19163) which relies on current linker behavior
as a workaround, so the same option --no-apply-dynamic-relocs added.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR 10549: MIPS/LD: Handle OSABI setting for STB_GNU_UNIQUE
@ 2016-05-03 23:21 sergiodj+buildbot
  2016-05-03 23:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 23:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d6a648c0789fb227ee2adfb089fe0ce8174708d ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 6d6a648c0789fb227ee2adfb089fe0ce8174708d

PR 10549: MIPS/LD: Handle OSABI setting for STB_GNU_UNIQUE

Add missing OSABI handling for MIPS/LD, complementing:

commit f64b2e8d60f277b705c96d4b4e585f5f7c847cc4
Author: Nick Clifton <nickc@redhat.com>
Date:   Mon Apr 11 08:13:22 2011 +0000

Adjust test coverage accordingly.

	bfd/
	PR 10549
	* elfxx-mips.c (_bfd_mips_elf_add_symbol_hook): Handle
	STB_GNU_UNIQUE.

	ld/
	PR 10549
	* testsuite/ld-unique/unique.exp: Also run for `mips*-*-*'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix typos in gdb_pipe function comment
@ 2016-05-03 23:36 sergiodj+buildbot
  2016-05-04  0:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 23:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1ec3d244a75a6e6a2f54235c26e6b1e3b8a2482 ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: a1ec3d244a75a6e6a2f54235c26e6b1e3b8a2482

Fix typos in gdb_pipe function comment

gdb/ChangeLog:
2016-05-03  Don Breazeal <donb@codesourcery.com>

	* serial.h (gdb_pipe): Fix argument names in comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR symtab/19914 fix handling of dwp + split debug
@ 2016-05-04  0:22 sergiodj+buildbot
  2016-05-04  1:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-04  0:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c4474237ab3356b100ebbdd6ff1a8839745023d ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 6c4474237ab3356b100ebbdd6ff1a8839745023d

PR symtab/19914 fix handling of dwp + split debug

	PR symtab/19914
	* dwarf2read.c (open_and_init_dwp_file): Look at backlink if objfile
	is separate debug file.

	testsuite/
	* gdb.dwarf2/dwp-sepdebug.c: New file.
	* gdb.dwarf2/dwp-sepdebug.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce procedure use_gdb_stub
@ 2016-05-04 13:48 sergiodj+buildbot
  2016-05-04 13:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-04 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8929ad8bbca9a8b036eba0397992d6f3b4d1966b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8929ad8bbca9a8b036eba0397992d6f3b4d1966b

Introduce procedure use_gdb_stub

This patch introduces the use_gdb_stub procedure, which allows getting
the right value of the use_gdb_stub variable/property in any all
situations.

When calling it before the $use_gdb_stub global variable has been set,
it will return the value of the use_gdb_stub property from the board
file.  This happens when tests want to bail out early (even before gdb
has been started) when the current test setup is a stub.

Otherwise, it returns the value of the $use_gdb_stub global.

It's possible for these two to differ when a test file overrides the
value of the global.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (use_gdb_stub): New procedure.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix solib-display.exp remote check
@ 2016-05-04 14:35 sergiodj+buildbot
  2016-05-04 14:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-04 14:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02e370d94ee3abc6f910602e79c6d4515d9c720d ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 02e370d94ee3abc6f910602e79c6d4515d9c720d

Fix solib-display.exp remote check

This test currently uses [is_remote target] to check if the test is
supported.  This is not quite correct, as the limitation is actually
that it requires support for "running", ruling out stub-like targets.
Therefore, it should check for use_gdb_stub.

This has no visible effect right now, but it will once we make the
native-gdbserver board non-dejagnu-remote.

gdb/testsuite/ChangeLog:

	* gdb.base/solib-display.exp: Check for [use_gdb_stub]instead
	of [is_remote target],


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Throw NOT_AVAILABLE_ERROR in read_stack and read_code
@ 2016-05-04 14:42 sergiodj+buildbot
  2016-05-04 15:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-04 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edf689f02787121a49ea0e36cfaa051b06852c8b ***

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

Throw NOT_AVAILABLE_ERROR in read_stack and read_code

Nowadays, read_memory may throw NOT_AVAILABLE_ERROR (it is done by
patch http://sourceware.org/ml/gdb-patches/2013-08/msg00625.html)
however, read_stack and read_code still throws MEMORY_ERROR only.  This
causes PR 19947, that is prologue unwinder is unable unwind because
code memory isn't available, but MEMORY_ERROR is thrown, while unwinder
catches NOT_AVAILABLE_ERROR.

 #0  memory_error (err=err@entry=TARGET_XFER_E_IO, memaddr=memaddr@entry=140737349781158) at /home/yao/SourceCode/gnu/gdb/git/gdb/corefile.c:217
 #1  0x000000000065f5ba in read_code (memaddr=memaddr@entry=140737349781158, myaddr=myaddr@entry=0x7fffffffd7b0 "\340\023<\001", len=len@entry=1)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/corefile.c:288
 #2  0x000000000065f7b5 in read_code_unsigned_integer (memaddr=memaddr@entry=140737349781158, len=len@entry=1, byte_order=byte_order@entry=BFD_ENDIAN_LITTLE)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/corefile.c:363
 #3  0x00000000004717e0 in amd64_analyze_prologue (gdbarch=gdbarch@entry=0x13c13e0, pc=140737349781158, current_pc=140737349781165, cache=cache@entry=0xda0cb0)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/amd64-tdep.c:2267
 #4  0x0000000000471f6d in amd64_frame_cache_1 (cache=0xda0cb0, this_frame=0xda0bf0) at /home/yao/SourceCode/gnu/gdb/git/gdb/amd64-tdep.c:2437
 #5  amd64_frame_cache (this_frame=0xda0bf0, this_cache=<optimised out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/amd64-tdep.c:2508
 #6  0x000000000047214d in amd64_frame_this_id (this_frame=<optimised out>, this_cache=<optimised out>, this_id=0xda0c50)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/amd64-tdep.c:2541
 #7  0x00000000006b94c4 in compute_frame_id (fi=0xda0bf0) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:481
 #8  get_prev_frame_if_no_cycle (this_frame=this_frame@entry=0xda0b20) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1809
 #9  0x00000000006bb6c9 in get_prev_frame_always_1 (this_frame=0xda0b20) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1983
 #10 get_prev_frame_always (this_frame=this_frame@entry=0xda0b20) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1999
 #11 0x00000000006bbe11 in get_prev_frame (this_frame=this_frame@entry=0xda0b20) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:2241
 #12 0x00000000006bc13c in unwind_to_current_frame (ui_out=<optimised out>, args=args@entry=0xda0b20) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1485

The fix is to let read_stack and read_code throw NOT_AVAILABLE_ERROR too,
in order to align with read_memory.

gdb:

2016-05-04  Yao Qi  <yao.qi@linaro.org>

	PR gdb/19947
	* corefile.c (read_memory): Rename it to ...
	(read_memory_object): ... it.  Add parameter object.
	(read_memory): Call read_memory_object.
	(read_stack): Likewise.
	(read_code): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Add SYNTAX_NOP and SYNTAX_1OP for extension instructions
@ 2016-05-04 15:43 sergiodj+buildbot
  2016-05-04 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-04 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 945e0f82dad31db89a107b496532886fe215c011 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 945e0f82dad31db89a107b496532886fe215c011

[ARC] Add SYNTAX_NOP and SYNTAX_1OP for extension instructions

gas/
2016-05-03  Claudiu Zissulescu  <claziss@synopsys.com>

	* config/tc-arc.c (syntaxclass): Add SYNTAX_NOP and SYNTAX_1OP.
	(arc_extinsn): Handle new introduced syntax.
	* testsuite/gas/arc/textinsn1op.d: New file.
	* testsuite/gas/arc/textinsn1op.s: Likewise.
	* doc/c-arc.texi: Document SYNTAX_NOP and SYNTAX_1OP.

opcodes/
2016-05-03  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-ext.c (dump_ARC_extmap): Handle SYNATX_NOP and SYNTAX_1OP.
	(arcExtMap_genOpcode): Likewise.
	* arc-opc.c (arg_32bit_rc): Define new variable.
	(arg_32bit_u6): Likewise.
	(arg_32bit_limm): Likewise.

include/
2016-05-03  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (ARC_SYNTAX_1OP): Declare
	(ARC_SYNTAX_NOP): Likewsie.
	(ARC_OP1_MUST_BE_IMM): Update defined value.
	(ARC_OP1_IMM_IMPLIED): Likewise.
	(arg_32bit_rc, arg_32bit_u6, arg_32bit_limm): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [spu] Fix C++ build problems
@ 2016-05-05  0:11 sergiodj+buildbot
  2016-05-05  0:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-05  0:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1aebf87fd3887ae02e5e62fb41889c9fa37a8a9 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: c1aebf87fd3887ae02e5e62fb41889c9fa37a8a9

[spu] Fix C++ build problems

ChangeLog:

	* spu-linux-nat.c (spu_bfd_iovec_pread): Add pointer cast for C++.
	(spu_bfd_open): Likewise.

gdbserver/ChangeLog:

	* spu-low.c (fetch_ppc_register): Cast PowerPC-Linux-specific value
	used as first ptrace argument to PTRACE_TYPE_ARG1 for C++.
	(fetch_ppc_memory_1, store_ppc_memory_1): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change type of cpsr in arm_sigreturn_next_pc
@ 2016-05-05  8:19 sergiodj+buildbot
  2016-05-05  8:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-05  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf2ebb6e0958c9193c7c65620cd7a8b990d8b316 ***

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

Change type of cpsr in arm_sigreturn_next_pc

Variable cpsr holds the value of cpsr register, which is 32-bit.  It
is better to explicitly use uint32_t.

gdb/gdbserver:

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

	* linux-arm-low.c (arm_sigreturn_next_pc): Change type of cpsr
	to uint32_t.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Initialize res in get_next_pcs_read_memory_unsigned_integer
@ 2016-05-05  9:13 sergiodj+buildbot
  2016-05-05  9:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-05  9:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e78496443ec1525ee94c54249779639b4cded0b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9e78496443ec1525ee94c54249779639b4cded0b

Initialize res in get_next_pcs_read_memory_unsigned_integer

This patch initialize res to zero, otherwise, it may have some garbage
bits after the *the_target->read_memory call.

gdb/gdbserver:

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

	* linux-arm-low.c (get_next_pcs_read_memory_unsigned_integer):
	Initialize res to zero.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Cache the section contents in x86 check_relocs
@ 2016-05-05 11:45 sergiodj+buildbot
  2016-05-05 11:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-05 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bedfd056d4d58a3ebaf8d396c8453f0d0468576f ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bedfd056d4d58a3ebaf8d396c8453f0d0468576f

Cache the section contents in x86 check_relocs

Cache the section contents in x86 check_relocs for sections without
TLS relocations.

	* elf32-i386.c (elf_i386_check_tls_transition): Remove abfd.
	Don't check if contents == NULL.
	(elf_i386_tls_transition): Add from_relocate_section.  Check
	from_relocate_section instead of contents != NULL.  Update
	elf_i386_check_tls_transition call.
	(elf_i386_check_relocs): Cache the section contents if
	keep_memory is FALSE.  Pass FALSE as from_relocate_section to
	elf_i386_tls_transition.
	(elf_i386_relocate_section): Pass TRUE as from_relocate_section
	to elf_i386_tls_transition.
	(elf_backend_caches_rawsize): New.
	* elf64-x86-64.c (elf_x86_64_check_tls_transition): Don't check
	if contents == NULL.
	(elf_x86_64_tls_transition): Add from_relocate_section.  Check
	from_relocate_section instead of contents != NULL.
	(elf_x86_64_check_relocs): Cache the section contents if
	keep_memory is FALSE.  Pass FALSE as from_relocate_section to
	elf_x86_64_tls_transition.
	(elf_x86_64_relocate_section): Pass TRUE as from_relocate_section
	to elf_x86_64_tls_transition.
	(elf_backend_caches_rawsize): New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Extract convert_load_reloc from x86 convert_load
@ 2016-05-05 12:11 sergiodj+buildbot
  2016-05-05 12:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-05 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c175a65796a6f1d6a69ed0d7e3bce6f048c8e983 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: c175a65796a6f1d6a69ed0d7e3bce6f048c8e983

Extract convert_load_reloc from x86 convert_load

	* elf32-i386.c (elf_i386_convert_load): Extract the GOT load
	conversion to ...
	(elf_i386_convert_load_reloc): This.  New function.
	* elf64-x86-64.c (elf_x86_64_convert_load): Extract the GOT load
	conversion to ...
	(elf_x86_64_convert_load_reloc): This.  New function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Define elf_backend_add_symbol_hook for Intel MCU
@ 2016-05-06 15:44 sergiodj+buildbot
  2016-05-06 15:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-06 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 030e823caf4243a3337c2134a4a2f38490d3cf3d ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 030e823caf4243a3337c2134a4a2f38490d3cf3d

Define elf_backend_add_symbol_hook for Intel MCU

elf_backend_add_symbol_hook is undefined for FreeBSD.  Define it for
Intel MCU to support STB_GNU_UNIQUE for Intel MCU and NaCl.

	* elf32-i386.c (elf_backend_add_symbol_hook): Defined for Intel
	MCU.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] remove trivialy unused variables
@ 2016-05-08  0:20 sergiodj+buildbot
  2016-05-08  1:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-08  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 870f88f7551b0f2d6aaaa36fb684b5ff8f468107 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 870f88f7551b0f2d6aaaa36fb684b5ff8f468107

remove trivialy unused variables

gdb/ChangeLog:

2016-05-07  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* aarch64-linux-tdep.c (aarch64_linux_sigframe_init): Remove unused
	variables.
	* aarch64-tdep.c (aarch64_skip_prologue): Likewise.
	(aarch64_scan_prologue): Likewise.
	(aarch64_prologue_prev_register): Likewise.
	(aarch64_dwarf2_prev_register): Likewise.
	(pass_in_v): Likewise.
	(aarch64_push_dummy_call): Likewise.
	(aarch64_breakpoint_from_pc): Likewise.
	(aarch64_return_in_memory): Likewise.
	(aarch64_return_value): Likewise.
	(aarch64_displaced_step_b_cond): Likewise.
	(aarch64_displaced_step_cb): Likewise.
	(aarch64_displaced_step_tb): Likewise.
	(aarch64_gdbarch_init): Likewise.
	(aarch64_process_record): Likewise.
	* alpha-mdebug-tdep.c (alpha_mdebug_init_abi): Likewise.
	* alpha-tdep.c (_initialize_alpha_tdep): Likewise.
	* amd64-dicos-tdep.c (amd64_dicos_init_abi): Likewise.
	* amd64-linux-tdep.c (amd64_dtrace_parse_probe_argument): Likewise.
	* amd64-tdep.c (fixup_riprel): Likewise.
	* amd64-windows-tdep.c (amd64_windows_frame_decode_epilogue): Likewise.
	(amd64_windows_frame_decode_insns): Likewise.
	(amd64_windows_frame_cache): Likewise.
	(amd64_windows_frame_prev_register): Likewise.
	(amd64_windows_frame_this_id): Likewise.
	(amd64_windows_init_abi): Likewise.
	* arm-linux-tdep.c (arm_linux_get_syscall_number): Likewise.
	(arm_linux_get_next_pcs_syscall_next_pc): Likewise.
	* arm-symbian-tdep.c (arm_symbian_init_abi): Likewise.
	* arm-tdep.c (arm_make_epilogue_frame_cache): Likewise.
	(arm_epilogue_frame_prev_register): Likewise.
	(arm_record_vdata_transfer_insn): Likewise.
	(arm_record_exreg_ld_st_insn): Likewise.
	* auto-load.c (execute_script_contents): Likewise.
	(print_scripts): Likewise.
	* avr-tdep.c (avr_frame_prev_register): Likewise.
	(avr_push_dummy_call): Likewise.
	* bfin-linux-tdep.c (bfin_linux_sigframe_init): Likewise.
	* bfin-tdep.c (bfin_gdbarch_init): Likewise.
	* blockframe.c (find_pc_partial_function_gnu_ifunc): Likewise.
	* break-catch-throw.c (fetch_probe_arguments): Likewise.
	* breakpoint.c (breakpoint_xfer_memory): Likewise.
	(breakpoint_init_inferior): Likewise.
	(breakpoint_inserted_here_p): Likewise.
	(software_breakpoint_inserted_here_p): Likewise.
	(hardware_breakpoint_inserted_here_p): Likewise.
	(bpstat_what): Likewise.
	(break_range_command): Likewise.
	(save_breakpoints): Likewise.
	* coffread.c (coff_symfile_read): Likewise.
	* cris-tdep.c (cris_push_dummy_call): Likewise.
	(cris_scan_prologue): Likewise.
	(cris_register_size): Likewise.
	(_initialize_cris_tdep): Likewise.
	* d-exp.y: Likewise.
	* dbxread.c (dbx_read_symtab): Likewise.
	(process_one_symbol): Likewise.
	(coffstab_build_psymtabs): Likewise.
	(elfstab_build_psymtabs): Likewise.
	* dicos-tdep.c (dicos_init_abi): Likewise.
	* disasm.c (do_mixed_source_and_assembly): Likewise.
	(gdb_disassembly): Likewise.
	* dtrace-probe.c (dtrace_process_dof): Likewise.
	* dwarf2read.c (error_check_comp_unit_head): Likewise.
	(build_type_psymtabs_1): Likewise.
	(skip_one_die): Likewise.
	(process_imported_unit_die): Likewise.
	(dwarf2_physname): Likewise.
	(read_file_scope): Likewise.
	(setup_type_unit_groups): Likewise.
	(create_dwo_cu_reader): Likewise.
	(create_dwo_cu): Likewise.
	(create_dwo_unit_in_dwp_v1): Likewise.
	(create_dwo_unit_in_dwp_v2): Likewise.
	(lookup_dwo_unit_in_dwp): Likewise.
	(free_dwo_file): Likewise.
	(check_producer): Likewise.
	(dwarf2_add_typedef): Likewise.
	(dwarf2_add_member_fn): Likewise.
	(read_unsigned_leb128): Likewise.
	(read_signed_leb128): Likewise.
	(dwarf2_const_value): Likewise.
	(follow_die_sig_1): Likewise.
	(dwarf_decode_macro_bytes): Likewise.
	* extension.c (restore_active_ext_lang): Likewise.
	* frv-linux-tdep.c (frv_linux_sigtramp_frame_cache): Likewise.
	* ft32-tdep.c (ft32_analyze_prologue): Likewise.
	* gdbtypes.c (lookup_typename): Likewise.
	(resolve_dynamic_range): Likewise.
	(check_typedef): Likewise.
	* h8300-tdep.c (h8300_is_argument_spill): Likewise.
	(h8300_gdbarch_init): Likewise.
	* hppa-tdep.c (hppa32_push_dummy_call): Likewise.
	(hppa_frame_this_id): Likewise.
	(_initialize_hppa_tdep): Likewise.
	* hppanbsd-tdep.c (hppanbsd_sigtramp_cache_init): Likewise.
	* hppaobsd-tdep.c (hppaobsd_supply_fpregset): Likewise.
	* i386-dicos-tdep.c (i386_dicos_init_abi): Likewise.
	* i386-tdep.c (i386_bnd_type): Likewise.
	(i386_gdbarch_init): Likewise.
	(i386_mpx_bd_base): Likewise.
	* i386nbsd-tdep.c (i386nbsd_sigtramp_cache_init): Likewise.
	* i386obsd-tdep.c (i386obsd_elf_init_abi): Likewise.
	* ia64-tdep.c (examine_prologue): Likewise.
	(ia64_frame_cache): Likewise.
	(ia64_push_dummy_call): Likewise.
	* infcmd.c (finish_command_fsm_async_reply_reason): Likewise.
	(default_print_one_register_info): Likewise.
	* infrun.c (infrun_thread_ptid_changed): Likewise.
	(thread_still_needs_step_over): Likewise.
	(stop_all_threads): Likewise.
	(restart_threads): Likewise.
	(keep_going_stepped_thread): Likewise.
	* iq2000-tdep.c (iq2000_scan_prologue): Likewise.
	* language.c (language_init_primitive_type_symbols): Likewise.
	* linespec.c (add_sal_to_sals): Likewise.
	* linux-nat.c (status_callback): Likewise.
	(kill_unfollowed_fork_children): Likewise.
	(linux_nat_kill): Likewise.
	* linux-tdep.c (linux_fill_prpsinfo): Likewise.
	* linux-thread-db.c (thread_db_notice_clone): Likewise.
	(record_thread): Likewise.
	* location.c (string_to_event_location_basic): Likewise.
	* m32c-tdep.c (m32c_prev_register): Likewise.
	* m32r-linux-tdep.c (m32r_linux_init_abi): Likewise.
	* m32r-tdep.c (decode_prologue): Likewise.
	* m68klinux-tdep.c (m68k_linux_sigtramp_frame_cache): Likewise.
	* machoread.c (macho_symtab_read): Likewise.
	(macho_symfile_read): Likewise.
	(macho_symfile_offsets): Likewise.
	* maint.c (set_per_command_cmd): Likewise.
	* mi/mi-cmd-stack.c (mi_cmd_stack_list_locals): Likewise.
	(mi_cmd_stack_list_variables): Likewise.
	* mi/mi-main.c (mi_cmd_exec_run): Likewise.
	(output_register): Likewise.
	(mi_cmd_execute): Likewise.
	(mi_cmd_trace_define_variable): Likewise.
	(print_variable_or_computed): Likewise.
	* minsyms.c (prim_record_minimal_symbol_full): Likewise.
	* mn10300-tdep.c (mn10300_frame_prev_register): Likewise.
	* msp430-tdep.c (msp430_pseudo_register_write): Likewise.
	* mt-tdep.c (mt_registers_info): Likewise.
	* nios2-tdep.c (nios2_analyze_prologue): Likewise.
	(nios2_push_dummy_call): Likewise.
	(nios2_frame_unwind_cache): Likewise.
	(nios2_stub_frame_cache): Likewise.
	(nios2_stub_frame_sniffer): Likewise.
	(nios2_gdbarch_init): Likewise.
	* ppc-ravenscar-thread.c: Likewise.
	* ppcfbsd-tdep.c (ppcfbsd_sigtramp_frame_cache): Likewise.
	* python/py-evts.c (add_new_registry): Likewise.
	* python/py-finishbreakpoint.c (bpfinishpy_init): Likewise.
	(bpfinishpy_detect_out_scope_cb): Likewise.
	* python/py-framefilter.c (py_print_value): Likewise.
	* python/py-inferior.c (infpy_write_memory): Likewise.
	* python/py-infevents.c (create_inferior_call_event_object): Likewise.
	* python/py-infthread.c (thpy_get_ptid): Likewise.
	* python/py-linetable.c (ltpy_get_pcs_for_line): Likewise.
	(ltpy_get_all_source_lines): Likewise.
	(ltpy_is_valid): Likewise.
	(ltpy_iternext): Likewise.
	* python/py-symtab.c (symtab_and_line_to_sal_object): Likewise.
	* python/py-unwind.c (pyuw_object_attribute_to_pointer): Likewise.
	(unwind_infopy_str): Likewise.
	* python/py-varobj.c (py_varobj_get_iterator): Likewise.
	* ravenscar-thread.c (ravenscar_inferior_created): Likewise.
	* rs6000-aix-tdep.c (rs6000_push_dummy_call): Likewise.
	* rs6000-lynx178-tdep.c (rs6000_lynx178_push_dummy_call): Likewise.
	* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Likewise.
	* s390-linux-tdep.c (s390_supply_tdb_regset): Likewise.
	(s390_frame_prev_register): Likewise.
	(s390_dwarf2_frame_init_reg): Likewise.
	(s390_record_vr): Likewise.
	(s390_process_record): Likewise.
	* score-tdep.c (score_push_dummy_call): Likewise.
	(score3_analyze_prologue): Likewise.
	* sh-tdep.c (sh_extract_return_value_nofpu): Likewise.
	* sh64-tdep.c (sh64_analyze_prologue): Likewise.
	(sh64_push_dummy_call): Likewise.
	(sh64_extract_return_value): Likewise.
	(sh64_do_fp_register): Likewise.
	* solib-aix.c (solib_aix_get_section_offsets): Likewise.
	* solib-darwin.c (darwin_read_exec_load_addr_from_dyld): Likewise.
	(darwin_solib_read_all_image_info_addr): Likewise.
	* solib-dsbt.c (enable_break): Likewise.
	* solib-frv.c (enable_break2): Likewise.
	(frv_fdpic_find_canonical_descriptor): Likewise.
	* solib-svr4.c (svr4_handle_solib_event): Likewise.
	* sparc-tdep.c (sparc_skip_stack_check): Likewise.
	* sparc64-linux-tdep.c (sparc64_linux_get_longjmp_target): Likewise.
	* sparcobsd-tdep.c (sparc32obsd_init_abi): Likewise.
	* spu-tdep.c (info_spu_dma_cmdlist): Likewise.
	* stack.c (read_frame_local): Likewise.
	* symfile.c (symbol_file_add_separate): Likewise.
	(remove_symbol_file_command): Likewise.
	* symmisc.c (maintenance_print_one_line_table): Likewise.
	* symtab.c (symbol_cache_flush): Likewise.
	(basic_lookup_transparent_type): Likewise.
	(sort_search_symbols_remove_dups): Likewise.
	* target.c (target_memory_map): Likewise.
	(target_detach): Likewise.
	(target_resume): Likewise.
	(acquire_fileio_fd): Likewise.
	(target_store_registers): Likewise.
	* thread.c (print_thread_info_1): Likewise.
	* tic6x-tdep.c (tic6x_analyze_prologue): Likewise.
	* tilegx-linux-tdep.c (tilegx_linux_sigframe_init): Likewise.
	* tilegx-tdep.c (tilegx_push_dummy_call): Likewise.
	(tilegx_analyze_prologue): Likewise.
	(tilegx_stack_frame_destroyed_p): Likewise.
	(tilegx_frame_cache): Likewise.
	* tracefile.c (trace_save): Likewise.
	* tracepoint.c (encode_actions_and_make_cleanup): Likewise.
	(start_tracing): Likewise.
	(print_one_static_tracepoint_marker): Likewise.
	* tui/tui.c (tui_enable): Likewise.
	* valops.c (value_struct_elt_bitpos): Likewise.
	(find_overload_match): Likewise.
	(find_oload_champ): Likewise.
	* value.c (value_contents_copy_raw): Likewise.
	* windows-tdep.c (windows_get_tlb_type): Likewise.
	* x86-linux-nat.c (x86_linux_enable_btrace): Likewise.
	* xcoffread.c (record_minimal_symbol): Likewise.
	(scan_xcoff_symtab): Likewise.
	* xtensa-tdep.c (execute_code): Likewise.
	(xtensa_gdbarch_init): Likewise.
	(_initialize_xtensa_tdep): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Redundant hash table check
@ 2016-05-09  8:25 sergiodj+buildbot
  2016-05-09  8:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-09  8:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae1bb197269ca8f7aa560168c0dfd0bb80730e0f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ae1bb197269ca8f7aa560168c0dfd0bb80730e0f

Redundant hash table check

	* elf64-ppc.c (ppc64_elf_init_stub_bfd): Remove redundant NULL check.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Regenerate configure
@ 2016-05-09  8:38 sergiodj+buildbot
  2016-05-09  9:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-09  8:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6eb7d83039db70127a6eb3e4b64ecae782c42f00 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 6eb7d83039db70127a6eb3e4b64ecae782c42f00

Regenerate configure


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes,gas: sparc: fix mnemonic of faligndatai
@ 2016-05-09 11:17 sergiodj+buildbot
  2016-05-09 11:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-09 11:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d751b79ea6bd7721367f1d78d22b70cee161fc26 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: d751b79ea6bd7721367f1d78d22b70cee161fc26

opcodes,gas: sparc: fix mnemonic of faligndatai

opcodes/ChangeLog:

2016-05-09  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-opc.c (sparc_opcodes): Fix mnemonic of faligndatai.

gas/ChangeLog:

2016-05-09  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* testsuite/gas/sparc/sparc5vis4.s: Fix mnemonic of faligndatai.
	* testsuite/gas/sparc/sparc5vis4.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Revert accidental commit.
@ 2016-05-09 12:01 sergiodj+buildbot
  2016-05-09 12:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-09 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73597c183c78ed0bea291897de6d8867ec640208 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 73597c183c78ed0bea291897de6d8867ec640208

Revert accidental commit.

	PR 19938
	* elf32-arm.c (elf32_arm_adjust_dynamic_symbol): Revert accidental
	commit.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM/STM32L4XX] PR 20030: --fix-stm32l4xx-629360 fails to create vldm/vpop veneers for double-precision registers
@ 2016-05-09 13:29 sergiodj+buildbot
  2016-05-09 14:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-09 13:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9239bbd3a6bf901dba1c0170622c50c78f6d1096 ***

Author: Christophe Monat <christophe.monat@st.com>
Branch: master
Commit: 9239bbd3a6bf901dba1c0170622c50c78f6d1096

[ARM/STM32L4XX] PR 20030: --fix-stm32l4xx-629360 fails to create vldm/vpop veneers for double-precision registers

bfd/
	PR ld/20030
	* elf32-arm.c (is_thumb2_vldm): Account for T1 (DP) encoding.
	(stm32l4xx_need_create_replacing_stub): Rename ambiguous nb_regs
	to nb_words.
	(create_instruction_vldmia): Add is_dp to disambiguate SP/DP
	encoding.
	(create_instruction_vldmdb): Likewise.
	(stm32l4xx_create_replacing_stub_vldm): is_dp detects DP encoding,
	uses it to re-encode.

ld/
	PR ld/20030
	* testsuite/ld-arm/arm-elf.exp: Run new stm32l4xx-fix-vldm-dp
	tests. Fix misnamed stm32l4xx-fix-all.
	* testsuite/ld-arm/stm32l4xx-fix-vldm-dp.s: New tests for multiple
	loads with DP registers.
	* testsuite/ld-arm/stm32l4xx-fix-vldm-dp.d: New reference file.
	* testsuite/ld-arm/stm32l4xx-fix-vldm.s: Add missing comment.
	* testsuite/ld-arm/stm32l4xx-fix-all.s: Add tests for multiple
	loads with DP registers.
	* testsuite/ld-arm/stm32l4xx-fix-all.d: Update reference.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix seg fault objdumping a corrupt binary with an invalid sh_link field.
@ 2016-05-09 16:52 sergiodj+buildbot
  2016-05-09 16:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-09 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 315350be6598235df12a0190a5a4c21447eead36 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 315350be6598235df12a0190a5a4c21447eead36

Fix seg fault objdumping a corrupt binary with an invalid sh_link field.

	PR binutils/20063
	* elf.c (bfd_elf_get_elf_syms): Check for out of range sh_link
	field before accessing sections array.

	* readelf.c (get_32bit_section_headers): Warn if an out of range
	sh_link or sh_info field is encountered.
	(get_64bit_section_headers): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR 20059 _bfd_elf_copy_link_hash_symbol_type segfault
@ 2016-05-10  2:02 sergiodj+buildbot
  2016-05-10  2:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10  2:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 66a368220cc109070a30ac2bbf24057c8b07a2b0 ***

Author: Pip Cet <pipcet@gmail.com>
Branch: master
Commit: 66a368220cc109070a30ac2bbf24057c8b07a2b0

PR 20059 _bfd_elf_copy_link_hash_symbol_type segfault

	PR ld/20059
	* elfxx-target.h (bfd_elfNN_bfd_copy_link_hash_symbol_type):
	Define as _bfd_generic_copy_link_hash_symbol_type when using
	generic hash table.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow extension availability to depend on several architecture bits
@ 2016-05-10 16:24 sergiodj+buildbot
  2016-05-10 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d942732e829030b8eab483dd48b979f8eed7c9e2 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: d942732e829030b8eab483dd48b979f8eed7c9e2

Allow extension availability to depend on several architecture bits

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
	* config/tc-arm.c (struct arm_option_extension_value_table): Make
	allowed_archs an array with 2 entries.
	(ARM_EXT_OPT): Adapt to only fill the first entry of allowed_archs.
	(ARM_EXT_OPT2): New macro filling the two entries of allowed_archs.
	(arm_extensions): Use separate entries in allowed_archs when several
	archs are allowed to use an extension and change ARCH_ANY in
	ARM_ARCH_NONE in allowed_archs.
	(arm_parse_extension): Check that, for each allowed_archs entry, all
	bits are set in the current architecture, ignoring ARM_ANY entries.
	(s_arm_arch_extension): Likewise.

include/
	* arm.h (ARM_FSET_CPU_SUBSET): Define macro.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for ARMv8-M Mainline with DSP extension
@ 2016-05-10 16:40 sergiodj+buildbot
  2016-05-10 17:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 16:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15afaa63f39a44563e49bb3b9fb38ed43e8b48ed ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 15afaa63f39a44563e49bb3b9fb38ed43e8b48ed

Add support for ARMv8-M Mainline with DSP extension

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	(elf32_arm_merge_eabi_attributes): Add merging logic for
	Tag_DSP_extension.

binutils/
	* readelf.c (display_arm_attribute): Add output for Tag_DSP_extension.
	(arm_attr_public_tags): Define DSP_extension attribute.

gas/
	* NEWS: Document ARMv8-M and ARMv8-M Security and DSP Extensions.
	* config/tc-arm.c (arm_ext_dsp): New feature for Thumb DSP
	instructions.
	(arm_extensions): Add dsp extension for ARMv8-M Mainline.
	(aeabi_set_public_attributes): Memorize the feature bits of the
	architecture selected for Tag_CPU_arch.  Use it to set
	Tag_DSP_extension to 1 for ARMv8-M Mainline with DSP extension.
	(arm_convert_symbolic_attribute): Define Tag_DSP_extension.
	* testsuite/gas/arm/arch7em-bad.d: Rename to ...
	* testsuite/gas/arm/arch7em-bad-1.d: This.
	* testsuite/gas/arm/arch7em-bad-2.d: New file.
	* testsuite/gas/arm/arch7em-bad-3.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-1.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-2.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-3.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-4.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-5.d: Likewise.
	* testsuite/gas/arm/attr-march-armv8m.main.dsp.d: Likewise.

include/
	* elf/arm.h (Tag_DSP_extension): Define.

ld/
	* testsuite/ld-arm/arm-elf.exp (EABI attribute merging 10 (DSP)): New
	test.
	* testsuite/ld-arm/attr-merge-10b-dsp.s: New file.
	* testsuite/ld-arm/attr-merge-10-dsp.attr: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Refactor Cortex-A8 erratum workaround in preparation
@ 2016-05-10 17:24 sergiodj+buildbot
  2016-05-10 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d9d9490142a0cd6edb7cfec820a7c8f28b88395 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 8d9d9490142a0cd6edb7cfec820a7c8f28b88395

Refactor Cortex-A8 erratum workaround in preparation

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (enum elf32_arm_stub_type): Delete
	arm_stub_a8_veneer_lwm enumerator.
	(arm_stub_a8_veneer_lwm): New unsigned constant to replace
	aforementioned enumerator.
	(struct elf32_arm_stub_hash_entry): Delete target_addend
	field and add source_value.
	(struct a8_erratum_fix): Delete addend field and add target_offset.
	(stub_hash_newfunc): Initialize source_value field amd remove
	initialization for target_addend.
	(arm_build_one_stub): Stop special casing Thumb relocations: promote
	the else to being always executed, moving the
	arm_stub_a8_veneer_b_cond specific code in it.  Remove
	stub_entry->target_addend from points_to computation.
	(cortex_a8_erratum_scan): Store in a8_erratum_fix structure the offset
	to target symbol from start of section rather than the offset from the
	stub address.
	(elf32_arm_size_stubs): Set stub_entry's source_value and target_value
	fields from struct a8_erratum_fix's offset and target_offset
	respectively.
	(make_branch_to_a8_stub): Rename target variable to loc.  Compute
	veneered_insn_loc and loc using stub_entry's source_value.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Factor our stub creation in ARM backend
@ 2016-05-10 17:37 sergiodj+buildbot
  2016-05-10 19:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 17:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b715f643ef3810bd77d50cc97fe4f7a3116b1556 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: b715f643ef3810bd77d50cc97fe4f7a3116b1556

Factor our stub creation in ARM backend

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (elf32_arm_create_stub): New function.
	(elf32_arm_size_stubs): Use elf32_arm_create_stub for stub creation.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow stubs without associated input section in ARM backend
@ 2016-05-10 18:12 sergiodj+buildbot
  2016-05-10 20:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 18:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6bde4c52fb2d49572d365612f222a42b4d316f09 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 6bde4c52fb2d49572d365612f222a42b4d316f09

Allow stubs without associated input section in ARM backend

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* bfd-in.h (elf32_arm_size_stubs): Add an output section parameter.
	* bfd-in2.h: Regenerated.
	* elf32-arm.c (struct elf32_arm_link_hash_table): Add an output section
	parameter to add_stub_section callback.
	(elf32_arm_create_or_find_stub_sec): Get output section from link_sec
	and pass it down to add_stub_section.
	(elf32_arm_add_stub): Set section to stub_sec if NULL before using it
	for error message.
	(elf32_arm_size_stubs): Add output section parameter to
	add_stub_section function pointer parameter.

ld/
	* emultempl/armelf.em (elf32_arm_add_stub_section): Add output_section
	parameter and rename input_section parameter to after_input_section.
	Append input stub section to the output section if after_input_section
	is NULL.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use getters/setters to access ARM branch type
@ 2016-05-10 18:49 sergiodj+buildbot
  2016-05-10 21:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39d911fc3c6519799ca1af4365d4b56f9d71ca94 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 39d911fc3c6519799ca1af4365d4b56f9d71ca94

Use getters/setters to access ARM branch type

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (elf32_arm_size_stubs): Use new macros
	ARM_GET_SYM_BRANCH_TYPE and ARM_SET_SYM_BRANCH_TYPE to respectively get
	and set branch type of a symbol.
	(bfd_elf32_arm_process_before_allocation): Likewise.
	(elf32_arm_relocate_section): Likewise and fix identation along the
	way.
	(allocate_dynrelocs_for_symbol): Likewise.
	(elf32_arm_finish_dynamic_symbol): Likewise.
	(elf32_arm_swap_symbol_in): Likewise.
	(elf32_arm_swap_symbol_out): Likewise.

gas/
	* config/tc-arm.c (arm_adjust_symtab): Use ARM_SET_SYM_BRANCH_TYPE to
	set branch type of a symbol.

gdb/
	* arm-tdep.c (arm_elf_make_msymbol_special): Use
	ARM_GET_SYM_BRANCH_TYPE to get branch type of a symbol.

include/
	* arm.h (enum arm_st_branch_type): Add new ST_BRANCH_ENUM_SIZE
	enumerator.
	(NUM_ENUM_ARM_ST_BRANCH_TYPE_BITS): New macro.
	(ENUM_ARM_ST_BRANCH_TYPE_BITMASK): Likewise.
	(ARM_SYM_BRANCH_TYPE): Replace by ...
	(ARM_GET_SYM_BRANCH_TYPE): This and ...
	(ARM_SET_SYM_BRANCH_TYPE): This in two versions depending on whether
	BFD_ASSERT is defined or not.

ld/
	* emultempl/armelf.em (gld${EMULATION_NAME}_finish): Use
	ARM_GET_SYM_BRANCH_TYPE to get branch type of a symbol.

opcodes/
	* arm-dis.c (get_sym_code_type): Use ARM_GET_SYM_BRANCH_TYPE to get
	branch type of a symbol.
	(print_insn): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow veneers to claim veneered symbols
@ 2016-05-10 19:10 sergiodj+buildbot
  2016-05-10 22:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 19:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f4faa4d43aeaf5dd0a5fe0aff2fde89df3e5b8c ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 4f4faa4d43aeaf5dd0a5fe0aff2fde89df3e5b8c

Allow veneers to claim veneered symbols

2016-05-10  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (enum elf32_arm_stub_type): New max_stub_type
	enumerator.
	(arm_stub_sym_claimed): New function.
	(elf32_arm_create_stub): Use veneered symbol name and section if
	veneer needs to claim its symbol, and keep logic unchanged otherwise.
	(arm_stub_claim_sym): New function.
	(arm_map_one_stub): Call arm_stub_claim_sym if veneer needs to claim
	veneered symbol, otherwise create local symbol as before.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable Intel RDPID instruction.
@ 2016-05-10 19:42 sergiodj+buildbot
  2016-05-10 23:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-10 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8bc526963edde8cf8789ce82072d05fd2bcc90c4 ***

Author: Alexander Fomin <alexander.fomin@intel.com>
Branch: master
Commit: 8bc526963edde8cf8789ce82072d05fd2bcc90c4

Enable Intel RDPID instruction.

This patch enables Intel RDPID instruction described in Intel64 and
IA-32 Architectures Software Developer's Manual, April 2016.

gas/

	* config/tc-i386.c (cpu_arch): Add RDPID.
	* doc/c-i386.texi: Document RDPID.

gas/testsuite/

	* gas/i386/i386.exp: Run RDPID tests.
	* gas/i386/prefix.d: Adjust.
	* gas/i386/rdpid.s: New test.
	* gas/i386/rdpid.d: Ditto.
	* gas/i386/rdpid-intel.d: Ditto.
	* gas/i386/x86-64-rdpid.s: Ditto.
	* gas/i386/x86-64-rdpid.d: Ditto.
	* gas/i386/x86-64-rdpid-intel.d: Ditto.

opcodes/

	* i386-dis.c (prefix_table): Add RDPID instruction.
	* i386-gen.c (cpu_flag_init): Add RDPID flag.
	(cpu_flags): Add RDPID bitfield.
	* i386-opc.h (enum): Add RDPID element.
	(i386_cpu_flags): Add RDPID field.
	* i386-opc.tbl: Add RDPID instruction.
	* i386-init.h: Regenerate.
	* i386-tbl.h: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] fix up two issues with the removal of unused variables
@ 2016-05-11  1:45 sergiodj+buildbot
  2016-05-11  1:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-11  1:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df140a0bc3140bca133cd7ced6e18903db69c396 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: df140a0bc3140bca133cd7ced6e18903db69c396

fix up two issues with the removal of unused variables

gdb/ChangeLog:

2016-05-10  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* iq2000-tdep.c (iq2000_scan_prologue): Remove if that shouldn't guard
	anything.
	* linespec.c (add_sal_to_sals): Restore call to symtab_to_fullname.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Remove redundant tls relax in elfNN_aarch64_final_link_relocate
@ 2016-05-11 11:26 sergiodj+buildbot
  2016-05-11 11:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-11 11:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e7fbb34f0546360e86b56dcd32b4d6478662b41 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 4e7fbb34f0546360e86b56dcd32b4d6478662b41

[AArch64] Remove redundant tls relax in elfNN_aarch64_final_link_relocate

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Remove redundant
  aarch64_tls_transition check.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [HPPA] Attach linker created dynamic sections to stub bfd
@ 2016-05-11 14:06 sergiodj+buildbot
  2016-05-11 14:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-11 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a464198b013940745d43cff029330b9e7dda71c2 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: a464198b013940745d43cff029330b9e7dda71c2

[HPPA] Attach linker created dynamic sections to stub bfd

bfd/
	* elf32-hppa.c (elf32_hppa_init_stub_bfd): New function.
	(elf32_hppa_check_relocs): Don't set dynobj.
	(elf32_hppa_size_stubs): Test !SEC_LINKER_CREATED for stub sections.
	(elf32_hppa_build_stubs): Likewise.
	* elf32-hppa.h (elf32_hppa_init_stub_bfd): Declare.
ld/
	* emultempl/hppaelf.em (hppaelf_create_output_section_statements):
	Call elf32_hppa_init_stub_bfd.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add MIPS32 DSPr3 support.
@ 2016-05-11 16:26 sergiodj+buildbot
  2016-05-11 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-11 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f4f9071ad5fe6076c3554a75d59536e74e6a3fe ***

Author: Matthew Fortune <matthew.fortune@imgtec.com>
Branch: master
Commit: 8f4f9071ad5fe6076c3554a75d59536e74e6a3fe

Add MIPS32 DSPr3 support.

bfd/

	* elfxx-mips.c (print_mips_ases): Add DSPR3.

binutils/

	* readelf.c (print_mips_ases): Add DSPR3.

gas/

	* config/tc-mips.c (options): Add OPTION_DSPR3 and
	OPTION_NO_DSPR3.
	(md_longopts): Likewise.
	(md_show_usage): Add help for -mdspr3 and -mno-dspr3.
	(mips_ases): Define availability for DSPr3.
	(mips_ase_groups): Add ASE_DSPR3 to the DSP group.
	(mips_convert_ase_flags): Map ASE_DSPR3 to AFL_ASE_DSPR3.
	* doc/as.texinfo: Document -mdspr3, -mno-dspr3.  Fix -mdspr2
	formatting.
	* doc/c-mips.texi: Document -mdspr3, -mno-dspr3, .set dspr3 and
	.set nodspr3.  Fix -mdspr2 formatting.
	* testsuite/gas/mips/mips32-dspr3.d: New file.
	* testsuite/gas/mips/mips32-dspr3.s: Likewise.
	* testsuite/gas/mips/mips.exp: Run mips32-dspr3 test.

include/

	* elf/mips.h (AFL_ASE_DSPR3): New macro.
	(AFL_ASE_MASK): Update to include AFL_ASE_DSPR3.
	* opcode/mips.h (ASE_DSPR3): New macro.

opcodes/

	* mips-dis.c (mips_arch_choices): Add ASE_DSPR3 to mips32r6 and
	mips64r6.
	* mips-opc.c (D34): New macro.
	(mips_builtin_opcodes): Define bposge32c for DSPr3.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ld -z combreloc reloc sorting
@ 2016-05-12 15:11 sergiodj+buildbot
  2016-05-12 15:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-12 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1997c9943a1979a7407f3c70ead92493a799e13e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1997c9943a1979a7407f3c70ead92493a799e13e

ld -z combreloc reloc sorting

PLT relocs don't appear in .rela.dyn, at least not when using
normal linker scripts.  However, if they do, then they ought to be
placed last rather than in the middle of other relocs.

	* elf-bfd.h (elf_reloc_type_class): Put reloc_class_plt last.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set dynamic tag VMA and size from dynamic section when possible
@ 2016-05-13  6:13 sergiodj+buildbot
  2016-05-13  6:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-13  6:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ade44b727ee77adaa9c22719935d012e253a5e6 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4ade44b727ee77adaa9c22719935d012e253a5e6

Set dynamic tag VMA and size from dynamic section when possible

Rather than searching the output for a specific named section, it's
better, where possible, to use a linker created dynamic section to set
a dynamic tag's value.  That way ld doesn't depend on the output
section name, making it possibile to map dynamic sections differently.

bfd/
	* elf-m10300.c (_bfd_mn10300_elf_finish_dynamic_sections): Use
	linker dynamic sections in calculating size and address of
	* dynamic tags rather than using output sections.  Remove asserts.
	* elf32-arm.c (elf32_arm_finish_dynamic_sections): Likewise.
	* elf32-cr16.c (_bfd_cr16_elf_finish_dynamic_sections): Likewise.
	* elf32-cris.c (elf_cris_finish_dynamic_sections): Likewise.
	* elf32-i370.c (i370_elf_finish_dynamic_sections): Likewise.
	* elf32-lm32.c (lm32_elf_finish_dynamic_sections): Likewise.
	* elf32-m32r.c (m32r_elf_finish_dynamic_sections): Likewise.
	* elf32-m68k.c (elf_m68k_finish_dynamic_sections): Likewise.
	* elf32-metag.c (elf_metag_finish_dynamic_sections): Likewise.
	* elf32-microblaze.c (microblaze_elf_finish_dynamic_sections): Likewise.
	* elf32-nds32.c (nds32_elf_finish_dynamic_sections): Likewise.
	* elf32-nios2.c (nios2_elf32_finish_dynamic_sections): Likewise.
	* elf32-or1k.c (or1k_elf_finish_dynamic_sections): Likewise.
	* elf32-s390.c (elf_s390_finish_dynamic_sections): Likewise.
	* elf32-score.c (s3_bfd_score_elf_finish_dynamic_sections): Likewise.
	* elf32-score7.c (s7_bfd_score_elf_finish_dynamic_sections): Likewise.
	* elf32-vax.c (elf_vax_finish_dynamic_sections): Likewise.
	* elf32-xtensa.c (elf_xtensa_finish_dynamic_sections): Likewise.
	* elf64-alpha.c (elf64_alpha_finish_dynamic_sections): Likewise.
	* elf64-s390.c (elf_s390_finish_dynamic_sections): Likewise.
	* elf64-sh64.c (sh64_elf64_finish_dynamic_sections): Likewise.
	* elflink.c (bfd_elf_final_link): Likewise.
	* elfxx-mips.c (_bfd_mips_elf_finish_dynamic_sections): Likewise.
	* elfxx-sparc.c (sparc_finish_dyn): Likewise.  Adjust error message.
	* elf32-arc.c (GET_SYMBOL_OR_SECTION): Remove ASSERT arg and
	don't set doit.  Look up dynobj section.
	(elf_arc_finish_dynamic_sections): Adjust GET_SYMBOL_OR_SECTION
	invocation and dynamic tag vma calculation.  Don't test
	boolean var == TRUE.
	* elfnn-aarch64.c (elfNN_aarch64_finish_dynamic_sections): Fix
	DT_JMPREL calc.
ld/
	* testsuite/ld-arm/arm-elf.exp: Adjust for arm-no-rel-plt now passing.
	Use different output file name for static app without .rel.plt.
	* testsuite/ld-arm/arm-no-rel-plt.ld: Align .rel.dyn and .rela.dyn.
	* testsuite/ld-arm/arm-no-rel-plt.out: Delete.
	* testsuite/ld-arm/arm-no-rel-plt.r: New.
	* testsuite/ld-arm/arm-static-app.d: Don't check file name.
	* testsuite/ld-arm/arm-static-app.r: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't convert GOTPCREL relocation against large section
@ 2016-05-13 18:25 sergiodj+buildbot
  2016-05-13 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-13 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2168b2688ae343a61c467450068503295a5e3deb ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 2168b2688ae343a61c467450068503295a5e3deb

Don't convert GOTPCREL relocation against large section

bfd/

	PR ld/20093
	* elf64-x86-64.c (elf_x86_64_convert_load_reloc): Don't convert
	GOTPCREL relocation against large section.

ld/

	PR ld/20093
	* testsuite/ld-x86-64/pr20093-1.d: New file.
	* testsuite/ld-x86-64/pr20093-1.s: Likewise.
	* testsuite/ld-x86-64/pr20093-2.d: Likewise.
	* testsuite/ld-x86-64/pr20093-2.s: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run pr20093-1 and pr20093-2.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Accept valid one byte signed and unsigned values for the IMM8 operand.
@ 2016-05-13 20:38 sergiodj+buildbot
  2016-05-13 20:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-13 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1178da445ad5faf37f9cc2be3aaa69d916f10f62 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 1178da445ad5faf37f9cc2be3aaa69d916f10f62

Accept valid one byte signed and unsigned values for the IMM8 operand.

opcodes/
	* ppc-opc.c (IMM8): Use PPC_OPERAND_SIGNOPT.

gas/
	* testsuite/gas/ppc/power9.d <xxspltib>: Add additional operand tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use unsuspend_all_lwps
@ 2016-05-17  8:00 sergiodj+buildbot
  2016-05-17  8:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17  8:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fcdad592cd1f76046c5e4b7a2b0337e146d1e796 ***

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

Use unsuspend_all_lwps

This patch is to replace find_inferior (&all_threads, unsuspend_one_lwp, NULL)
with unsuspend_all_lwps (NULL), which is shorter.  They are equivalent
to each other.

gdb/gdbserver:

2016-05-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_stabilize_threads): Call unsuspend_all_lwps
	instead of find_inferior.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] LD/ELF: Unify STB_GNU_UNIQUE handling
@ 2016-05-17 11:40 sergiodj+buildbot
  2016-05-17 11:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 11:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a43942db49b07a457ee4f960d0f118b23641ec38 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: a43942db49b07a457ee4f960d0f118b23641ec38

LD/ELF: Unify STB_GNU_UNIQUE handling

Take STB_GNU_UNIQUE handling scattered across targets and gather it in
the generic ELF linker.  Update test suite infrastructure accordingly.

	bfd/
	* elf-s390-common.c (elf_s390_add_symbol_hook): Remove
	STB_GNU_UNIQUE handling.
	* elf32-arc.c (elf_arc_add_symbol_hook): Likewise.
	* elf32-arm.c (elf32_arm_add_symbol_hook): Likewise.
	* elf32-m68k.c (elf_m68k_add_symbol_hook): Likewise.
	* elf32-ppc.c (ppc_elf_add_symbol_hook): Likewise.
	* elf32-sparc.c (elf32_sparc_add_symbol_hook): Likewise.
	* elf64-ppc.c (ppc64_elf_add_symbol_hook): Likewise.
	* elf64-sparc.c (elf64_sparc_add_symbol_hook): Likewise.
	* elf64-x86-64.c (elf_x86_64_add_symbol_hook): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_add_symbol_hook): Likewise.
	* elfxx-mips.c (_bfd_mips_elf_add_symbol_hook): Likewise.
	* elf32-i386.c (elf_i386_add_symbol_hook): Remove function.
	(elf_backend_add_symbol_hook): Remove macro.
	* elflink.c (elf_link_add_object_symbols): Set `has_gnu_symbols'
	for STB_GNU_UNIQUE symbols.

	binutils/
	* testsuite/lib/binutils-common.exp (supports_gnu_unique): New
	procedure.
	* testsuite/binutils-all/objcopy.exp: Use `supports_gnu_unique'
	with the `strip-10' test.

	ld/
	* testsuite/ld-unique/unique.exp: Use `is_elf_format' and
	`supports_gnu_unique' to qualify testing.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix latent yacc-related bug in gdb/Makefile.in init.c rule
@ 2016-05-17 20:49 sergiodj+buildbot
  2016-05-17 20:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 20:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ab0bb2a673875ba15d6956f2c587c9c31f40357 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9ab0bb2a673875ba15d6956f2c587c9c31f40357

Fix latent yacc-related bug in gdb/Makefile.in init.c rule

gdb's Makefile.in does not currently scan .y files to add global
initializers from these files to init.c.  However, at least ada-exp.y
tries to use this feature.

This patch fixes the problem.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* Makefile.in (init.c): Search .y files for initialization
	functions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb expression debugging handle OP_F90_RANGE
@ 2016-05-17 21:21 sergiodj+buildbot
  2016-05-17 21:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4b8a1c839b88c345b82c37c90814a89c7f0c3c2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: e4b8a1c839b88c345b82c37c90814a89c7f0c3c2

Make gdb expression debugging handle OP_F90_RANGE

print_subexp_standard and dump_subexp_body_standard did not handle
OP_F90_RANGE.  Attempting to dump an expression using this opcode
would fail.

This patch adds support for this opcode to these functions.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* expprint.c: Include f-lang.h.
	(print_subexp_standard, dump_subexp_body_standard): Handle
	OP_F90_RANGE.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update gdb test suite for Rust
@ 2016-05-17 21:36 sergiodj+buildbot
  2016-05-18  4:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 21:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 67218854b1987d89593ccaf5feaf5b29b1b976f2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 67218854b1987d89593ccaf5feaf5b29b1b976f2

Update gdb test suite for Rust

This updates the gdb test suite for Rust.

2016-05-17  Tom Tromey  <tom@tromey.com>
	    Manish Goregaokar <manishsmail@gmail.com>

	* lib/rust-support.exp: New file.
	* lib/gdb.exp (skip_rust_tests): New proc.
	(build_executable_from_specs): Handle rust.
	* lib/future.exp (gdb_find_rustc): New proc.
	(gdb_default_target_compile): Handle rust.
	* gdb.rust/expr.exp: New file.
	* gdb.rust/generics.exp: New file.
	* gdb.rust/generics.rs: New file.
	* gdb.rust/methods.exp: New file.
	* gdb.rust/methods.rs: New file.
	* gdb.rust/modules.exp: New file.
	* gdb.rust/modules.rs: New file.
	* gdb.rust/simple.exp: New file.
	* gdb.rust/simple.rs: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add self-test framework to gdb
@ 2016-05-17 21:52 sergiodj+buildbot
  2016-05-17 22:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 21:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dcd1f97951b432032fd0728992b1384064663701 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: dcd1f97951b432032fd0728992b1384064663701

Add self-test framework to gdb

I wanted to unit test the Rust lexer, so I added a simple unit testing
command to gdb.

The intent is that self tests will only be compiled into gdb in
development mode.  In release mode they simply won't exist.  So, this
exposes $development to C code as GDB_SELF_TEST.

In development mode, test functions are registered with the self test
module.  A test function is just a function that does some checks, and
throws an exception on failure.

Then this adds a new "maint selftest" command which invokes the test
functions, and a new dejagnu test case that invokes it.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* NEWS: Add "maint selftest" entry.
	* selftest.h: New file.
	* selftest.c: New file.
	* maint.c: Include selftest.h.
	(maintenance_selftest): New function.
	(_initialize_maint_cmds): Add "maint selftest" command.
	* configure.ac (GDB_SELF_TEST): Maybe define.
	* config.in, configure: Rebuild.
	* Makefile.in (SFILES): Add selftest.c.
	(COMMON_OBS): Add selftest.o.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* gdb.texinfo (Maintenance Commands): Document "maint selftest".

2016-05-17  Tom Tromey  <tom@tromey.com>

	* gdb.gdb/unittest.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add array start and end strings to generic_val_print_decorations
@ 2016-05-17 22:37 sergiodj+buildbot
  2016-05-17 23:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 22:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00272ec4b0cc22c1b9d60d39ce7bf5b2d5512582 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 00272ec4b0cc22c1b9d60d39ce7bf5b2d5512582

Add array start and end strings to generic_val_print_decorations

For Rust value-printing, I wanted to use generic_val_print_array, but
I also wanted to control the starting and ending strings.

This patch adds new strings to generic_val_print_decorations, updates
generic_val_print_array to use them, and updates all the existing
instances of generic_val_print_decorations.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* valprint.h (struct generic_val_print_array) <array_start,
	array_end>: New fields.
	* valprint.c (generic_val_print_array): Add "decorations"
	parameter.  Use "array_start", "array_end".
	(generic_val_print) <TYPE_CODE_ARRAY>: Update.
	* p-valprint.c (p_decorations): Update.
	* m2-valprint.c (m2_decorations): Update.
	* f-valprint.c (f_decorations): Update.
	* c-valprint.c (c_decorations): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for the Rust language
@ 2016-05-17 22:44 sergiodj+buildbot
  2016-05-18  1:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 22:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c44af4ebc000f606d16b42224cba2cfe80391d5c ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: c44af4ebc000f606d16b42224cba2cfe80391d5c

Add support for the Rust language

This patch adds support for the Rust language.

2016-05-17  Tom Tromey  <tom@tromey.com>
	    Manish Goregaokar <manishsmail@gmail.com>

	* symtab.c (symbol_find_demangled_name): Handle Rust.
	* symfile.c (init_filename_language_table): Treat ".rs" as Rust.
	* std-operator.def (STRUCTOP_ANONYMOUS, OP_RUST_ARRAY): New
	constants.
	* rust-lang.h: New file.
	* rust-lang.c: New file.
	* rust-exp.y: New file.
	* dwarf2read.c (read_file_scope): Add Rust producer sniffing.
	(dwarf2_compute_name, read_func_scope, read_structure_type)
	(read_base_type, read_subrange_type, set_cu_language)
	(new_symbol_full, determine_prefix): Handle Rust.
	* defs.h (enum language) <language_rust>: New constant.
	* Makefile.in (SFILES): Add rust-exp.y, rust-lang.c.
	(COMMON_OBS): Add rust-exp.o, rust-lang.o.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* gdb.base/default.exp (set language): Add rust.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add Rust documentation
@ 2016-05-17 23:52 sergiodj+buildbot
  2016-05-18  6:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-17 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bdfa368bc8dbea2f39706e34306c9b67883bbb1 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0bdfa368bc8dbea2f39706e34306c9b67883bbb1

Add Rust documentation

This patch adds documentation for the new Rust support in gdb.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* NEWS: Add Rust item.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* gdb.texinfo (Supported Languages): Mention Rust.  Update menu.
	(Rust): New node.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Rename OP_F90_RANGE to OP_RANGE.
@ 2016-05-18  0:39 sergiodj+buildbot
  2016-05-18  9:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01739a3b6a564f6552acf6c01617aa21ab4d8833 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 01739a3b6a564f6552acf6c01617aa21ab4d8833

Rename OP_F90_RANGE to OP_RANGE.

This renames OP_F90_RANGE to OP_RANGE, and similarly renames the
f90_range_type enum.

2016-05-17  Tom Tromey  <tom@tromey.com>

	* std-operator.def (OP_RANGE): Rename from OP_F90_RANGE.
	* rust-lang.c: Don't include f-lang.h.
	(rust_range, rust_compute_range, rust_subscript)
	(rust_evaluate_subexp): Update.
	* rust-exp.y: Don't include f-lang.h.
	(ast_range, convert_ast_to_expression): Update.
	* parse.c (operator_length_standard): Update.
	* f-lang.h (enum f90_range_type): Move to expression.h.
	* f-exp.y: Use OP_RANGE.
	* expression.h (enum range_type): New enum; renamed from
	f90_range_type.
	* expprint.c: Don't include f-lang.h.
	(print_subexp_standard, dump_subexp_body_standard): Use OP_RANGE.
	* eval.c (value_f90_subarray, evaluate_subexp_standard): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)
@ 2016-05-18  1:09 sergiodj+buildbot
  2016-05-18 10:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18  1:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61c6156df6e3c638eb3bdb4a6e3d418a43a6eb70 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 61c6156df6e3c638eb3bdb4a6e3d418a43a6eb70

Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077)

When doing -exec-run on a freshly started GDB, the only target on the
target stack at the time the dummy one.  When mi_async_p is called to
know whether the run should be async, it queries whether the current
target (dummy) supports async, and the answer is no.  The fix is to make
the code query the target that will be used for the run, which is not
necessarily the current target.

No regressions in the gdb.mi directory using the unix, native-gdbserver
and native-extended-gdbserver boards.  The test doesn't pass when
forcing maint set target-async off, obviously, since it makes mi-async
have no effect.  It doesn't seem like other tests are checking for that
eventuality, so I didn't in the new test.

gdb/ChangeLog:

	* mi/mi-main.c (run_one_inferior): Use run target to determine
	whether to run async or not.
	(mi_cmd_exec_run): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-async-run.exp: New file.
	* gdb.mi/mi-async-run.c: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] elf32-arm.c build breakage
@ 2016-05-18  6:45 sergiodj+buildbot
  2016-05-18 13:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18  6:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f9919700d0023db7d66fee9f437251a263f5d53 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7f9919700d0023db7d66fee9f437251a263f5d53

elf32-arm.c build breakage

	* elf32-arm.c (elf32_arm_size_stubs): Free or cache local syms
	for each BFD.  Don't goto error_ret_free_local from outside loop.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Updated Swedish translations for bfd and binutils
@ 2016-05-18 12:06 sergiodj+buildbot
  2016-05-18 14:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 12:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5049806017a546184b87fc3282a586d686b8d98f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 5049806017a546184b87fc3282a586d686b8d98f

Updated Swedish translations for bfd and binutils


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix double prompt output after run control MI commands with mi-async on (PR 20045)
@ 2016-05-18 14:45 sergiodj+buildbot
  2016-05-18 16:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28addb40c77db5a5873172b62b6b7b43e5e05014 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 28addb40c77db5a5873172b62b6b7b43e5e05014

Fix double prompt output after run control MI commands with mi-async on (PR 20045)

When you use a run control command (-exec-run, -exec-continue,
-exec-next, ...) with mi-async on, an extra (gdb) prompt is displayed:

  -exec-continue
  ^running
  *running,thread-id="all"
  (gdb)
  (gdb)

It doesn't seem to be a big problem for front-ends, since this behavior
started in gdb 7.9 and we haven't heard anything about that.  However,
it caused me some trouble while writing a test for PR 20039 [1].

The problem comes from an extra (gdb) prompt that we write when running
in mi-async off mode to emulate a past buggy behavior.  When executing a
run control command synchronously, previous gdbs always printed a prompt
right away, even though they are not ready to accept new MI commands
until the target stops.  Only at this time should they display a prompt.
But to keep backwards compatibility apparently, we print it anyway.
Since commit 198297aaf, the condition that decides whether we should
print that "bogus" prompt or not has become true, even when running with
mi-async on.  Since we already print a prompt at the end of the
asynchronous command execution, it results in two prompts for one
command.

The proposed fix is to call target_can_async_p instead of
target_is_async_p, to make the condition:

  if (!target_can_async_p () || sync_execution)
    ... show prompt ...

That shows the prompt if we are emulating a synchronous command on top
of an asynchronous target (sync_execution) or if the target simply can't
run asynchronously (!target_can_async_p ()).

Note that this code is changed and this bug fixed by Pedro's separate
console series, but I think it would be nice to have it fixed in the
mean time.

I ran the gdb.mi directory of the testsuite with mi-async on and off, I
didn't see any regressions.

gdb/ChangeLog:

	* mi/mi-main.c (mi_on_resume): Call target_can_async_p instead
	of target_is_async_p.

[1] https://sourceware.org/ml/gdb-patches/2016-05/msg00075.html


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add mi-threads-interrupt.exp test (PR 20039)
@ 2016-05-18 15:15 sergiodj+buildbot
  2016-05-18 17:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 15:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e8f9b05add4517189d7724ff3ed7c16f7b04daf ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 9e8f9b05add4517189d7724ff3ed7c16f7b04daf

Add mi-threads-interrupt.exp test (PR 20039)

Add a new test for PR 20039.  The test spawns new threads, then tries to
interrupt, continue, and interrupt again.  This use case was fixed by
commit 5fe966540d6b748f825774868463003700f0c878 in master, but gdb 7.11
is affected (so if you try it on the gdb-7.11-branch right now, the test
will fail).

New in v2, the test now handles mi-async on mode properly.  The failure
was specific to mi-async off, but I don't think it's bad to test the
same thing under async on mode.  I added a little hack when running in
async mode to work around bug 20045.

I also removed one continue/interrupt pair, as a single one was enough to
trigger the problem.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-threads-interrupt.c: New file.
	* gdb.mi/mi-threads-interrupt.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix build failure with GCC 4.1.
@ 2016-05-18 17:49 sergiodj+buildbot
  2016-05-18 20:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-18 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45f4ed92d14ddf891be1470556f53de6c94c8dc2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 45f4ed92d14ddf891be1470556f53de6c94c8dc2

Fix build failure with GCC 4.1.

2016-05-18  Tom Tromey  <tom@tromey.com>

	* rust-lang.c (rust_subscript): Initialize "high".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix ppc64le S-record test fail
@ 2016-05-19  5:14 sergiodj+buildbot
  2016-05-19  5:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19  5:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f284bf9da3ecc689405cb7b698c7714acdf1ab0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9f284bf9da3ecc689405cb7b698c7714acdf1ab0

Fix ppc64le S-record test fail

Segfaults on --defsym symbol (__stack_chk_fail in this instance).

	* elf64-ppc.c (ppc64_elf_branch_reloc): Check for NULL owner
	before dereferencing.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix powerpc subis range
@ 2016-05-19  5:57 sergiodj+buildbot
  2016-05-19  6:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19  5:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e43de63c8fd11a15d7c6c852747c81664c0beb2a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e43de63c8fd11a15d7c6c852747c81664c0beb2a

Fix powerpc subis range

	* ppc-opc.c: Formatting.
	(NSISIGNOPT): Define.
	(powerpc_opcodes <subis>): Use NSISIGNOPT.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Correct "Fix powerpc subis range"
@ 2016-05-19  7:41 sergiodj+buildbot
  2016-05-19  7:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19  7:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 514e58b726338c24b672d96bd48f8ce8a47f7803 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 514e58b726338c24b672d96bd48f8ce8a47f7803

Correct "Fix powerpc subis range"

	* ppc-opc.c (NSISIGNOPT): Use insert_nsi and extract_nsi.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove unsupported `am34-*-linux*' target triplet
@ 2016-05-19 10:25 sergiodj+buildbot
  2016-05-19 10:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b200de0f7a7008f74cde68fe87aa62b7729cd9a ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 6b200de0f7a7008f74cde68fe87aa62b7729cd9a

Remove unsupported `am34-*-linux*' target triplet

The `am34-*-linux*' target cannot be configured for, `am34' is not a CPU
name recognized by `config.sub'.  It has never been, required code has
not been contributed to GNU config, neither before nor since the
addition of the target triplet to our configury with commit bfff16424942
("Add MN10300 linker relaxation support for symbol differences") back in
2007.  Also there is no difference in actual tool configuration between
the `am34-*-linux*' and `am33_2.0-*-linux*' targets, except from a
different executable prefix and tooldir name.

Given the above remove the target triplet from our configuration.

	bfd/
	* config.bfd: Remove `am34-*-linux*' support.

	ld/
	* configure.tgt: Remove `am34-*-linux*' support.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] BFD fixes.
@ 2016-05-19 13:20 sergiodj+buildbot
  2016-05-19 13:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c8adacaf910480e3cda19ac9566133864a781d1 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 3c8adacaf910480e3cda19ac9566133864a781d1

[ARC] BFD fixes.

2016-05-19  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (arc_elf_final_write_processing): Changed.
	(debug_arc_reloc): Likewise.
	(elf_arc_relocate_section): Likewise.
	(elf_arc_check_relocs): Likewise.
	(elf_arc_adjust_dynamic_symbol): Likewise.
	(elf_arc_add_symbol_hook): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix invalid implicit conversions from void *
@ 2016-05-19 13:44 sergiodj+buildbot
  2016-05-19 14:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfb0d950a58edc4eb1f102174af38a364f4f43f7 ***

Author: Andreas Schwab <schwab@suse.de>
Branch: master
Commit: bfb0d950a58edc4eb1f102174af38a364f4f43f7

Fix invalid implicit conversions from void *

	* ia64-libunwind-tdep.c (libunwind_descr): Add cast from void *.
	(libunwind_frame_set_descr): Likewise.
	(libunwind_frame_cache): Likewise.
	(libunwind_frame_dealloc_cache): Likewise.
	(libunwind_frame_sniffer): Likewise.
	(libunwind_search_unwind_table): Likewise.
	(libunwind_sigtramp_frame_sniffer): Likewise.
	(libunwind_get_reg_special): Likewise.
	(libunwind_load): Likewise.
	* ia64-linux-nat.c (ia64_linux_fetch_register): Likewise.
	(ia64_linux_store_register): Likewise.
	(ia64_linux_xfer_partial): Likewise.
	* ia64-tdep.c (ia64_access_reg): Likewise.
	(ia64_access_fpreg): Likewise.
	(ia64_access_rse_reg): Likewise.
	(ia64_access_rse_fpreg): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set sh_entsize for .init_array and similar.
@ 2016-05-19 15:18 sergiodj+buildbot
  2016-05-19 15:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 15:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 606851fbf66c4a9e47c958014579dd363a74ba76 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 606851fbf66c4a9e47c958014579dd363a74ba76

Set sh_entsize for .init_array and similar.

	PR gas/20118
	* elf.c (elf_fake_sections): Set sh_entsize for SHT_INIT_ARRAY,
	SHT_FINI_ARRAY, and SHT_PREINIT_ARRAY.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't convert R_386_GOT32 relocation
@ 2016-05-19 20:17 sergiodj+buildbot
  2016-05-19 20:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-19 20:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d4d970973c4735dcdd2a69d645309f167a1d9d4 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7d4d970973c4735dcdd2a69d645309f167a1d9d4

Don't convert R_386_GOT32 relocation

Don't convert R_386_GOT32 since we can't tell if it is applied
to "mov $foo@GOT, %reg" which isn't a load via GOT.

bfd/

	PR ld/20117
	* elf32-i386.c (elf_i386_convert_load_reloc): Don't check
	R_386_GOT32X.
	(elf_i386_convert_load): Don't convert R_386_GOT32.

ld/

	PR ld/20117
	* testsuite/ld-i386/i386.exp: Run pr20117.
	* testsuite/ld-i386/pr19609-1i.d: Updated.
	* testsuite/ld-i386/pr20117.d: New file.
	* testsuite/ld-i386/pr20117.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS: Fix the encoding of immediates with microMIPS JALX
@ 2016-05-20 13:05 sergiodj+buildbot
  2016-05-20 13:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-20 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17c6c9d9f3e71459edb4b6af5ec75125f0d06f87 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 17c6c9d9f3e71459edb4b6af5ec75125f0d06f87

MIPS: Fix the encoding of immediates with microMIPS JALX

The microMIPS JALX instruction shares the R_MICROMIPS_26_S1 relocation
with microMIPS J/JAL/JALS instructions, however unlike the latters its
encoded immediate argument is unusually shifted left by 2 rather than 1
in calculating the value used for the operation requested.

We already handle this exception in `mips_elf_calculate_relocation' in
LD, in a scenario where JALX is produced as a result of relaxing JAL for
the purpose of making a cross-mode jump.  We also get it right in the
disassembler in `decode_micromips_operand'.

What we don't correctly do however is processing microMIPS JALX produced
by GAS from an assembly source, where a non-zero constant argument or a
symbol reference with a non-zero in-place addend has been used.  In this
case the same calculation is made as for microMIPS J/JAL/JALS, causing
the wrong encoding to be produced by GAS on making an object file, and
then again by LD in the final link.  The latter in particular causes the
calculation, where the addend fits in the relocatable field, to produce
different final addresses for the same source code depending on whether
REL or RELA relocations are used.

Correct these issues by special-casing microMIPS JALX in the places that
have been previously missed.

	bfd/
	* elfxx-mips.c (mips_elf_read_rel_addend): Adjust the addend for
	microMIPS JALX.

	gas/
	* config/tc-mips.c (append_insn): Correct the encoding of a
	constant argument for microMIPS JALX.
	(tc_gen_reloc): Correct the encoding of an in-place addend for
	microMIPS JALX.
	* testsuite/gas/mips/jalx-addend.d: New test.
	* testsuite/gas/mips/jalx-addend-n32.d: New test.
	* testsuite/gas/mips/jalx-addend-n64.d: New test.
	* testsuite/gas/mips/jalx-imm.d: New test.
	* testsuite/gas/mips/jalx-imm-n32.d: New test.
	* testsuite/gas/mips/jalx-imm-n64.d: New test.
	* testsuite/gas/mips/jalx-addend.s: New test source.
	* testsuite/gas/mips/jalx-imm.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/jalx-addend.d: New test.
	* testsuite/ld-mips-elf/jalx-addend-n32.d: New test.
	* testsuite/ld-mips-elf/jalx-addend-n64.d: New test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't check R_386_GOT32 when setting need_convert_load
@ 2016-05-20 17:00 sergiodj+buildbot
  2016-05-20 17:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-20 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52bf37dd91e5dd983ed20d1329293d077fe71e41 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 52bf37dd91e5dd983ed20d1329293d077fe71e41

Don't check R_386_GOT32 when setting need_convert_load

Since we no longer convert R_386_GOT32, don't check R_386_GOT32 when
setting need_convert_load.

	* elf32-i386.c (elf_i386_check_relocs): Don't check R_386_GOT32
	when setting need_convert_load.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tic54x: rename typedef of struct symbol_
@ 2016-05-23  5:30 sergiodj+buildbot
  2016-05-23  5:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23  5:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d207518c117df7a6c58f20bc2693171b7690650 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 3d207518c117df7a6c58f20bc2693171b7690650

tic54x: rename typedef of struct symbol_

generic gas code has a struct symbol, and tic54x typedefs a struct to symbol.
This seems at least rather confusing, and it seems like target specific headers
shouldn't  put such generic names in the global namespace preventing other
generic code from using them.

opcodes/ChangeLog:

2016-05-23  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* tic54x-dis.c (sprint_mmr): Adjust.
	* tic54x-opc.c: Likewise.

gas/ChangeLog:

2016-05-23  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-tic54x.c (tic54x_mmregs): Adjust.
	(md_begin): Likewise.
	(encode_condition): Likewise.
	(encode_cc3): Likewise.
	(encode_cc2): Likewise.
	(encode_operand): Likewise.
	(tic54x_undefined_symbol): Likewise.

include/ChangeLog:

2016-05-23  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/tic54x.h (struct symbol_): typedef to tic54x_symbol instead of
	plain symbol.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Search for libutil-freebsd as alternative to libutil
@ 2016-05-23  8:08 sergiodj+buildbot
  2016-05-23  8:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23  8:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37773e7803b370802302719a48c9c46f64c602b4 ***

Author: Jon Boden <jon@ubuntubsd.org>
Branch: master
Commit: 37773e7803b370802302719a48c9c46f64c602b4

Search for libutil-freebsd as alternative to libutil

GDB needs kinfo_getvmmap() on GNU/kFreeBSD systems same as on
pure FreeBSD.  However on these systems the FreeBSD version of libutil
is renamed to libutil-freebsd.

2016-05-23  Jon Boden  <jon@ubuntubsd.org>

	* configure.ac: Search for libutil-freebsd as alternative to libutil.
	* configure: Re-generated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support for dedicated output section for some ARM veneer types
@ 2016-05-23  8:59 sergiodj+buildbot
  2016-05-23  9:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23  8:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT daa4adae63f91377fe9b3e8d7421a0ceb4a51e26 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: daa4adae63f91377fe9b3e8d7421a0ceb4a51e26

Support for dedicated output section for some ARM veneer types

2016-05-23  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* bfd-in.h (bfd_elf32_arm_keep_private_stub_output_sections): Declare
	bfd hook.
	* bfd-in2.h: Regenerate.
	* elf32-arm.c (arm_dedicated_stub_output_section_required): New
	function.
	(arm_dedicated_stub_output_section_required_alignment): Likewise.
	(arm_dedicated_stub_output_section_name): Likewise.
	(arm_dedicated_stub_input_section_ptr): Likewise.
	(elf32_arm_create_or_find_stub_sec): Add stub type parameter and
	function description comment. Add support for dedicated output stub
	section to given stub types.
	(elf32_arm_add_stub): Add a stub type parameter and pass it down to
	elf32_arm_create_or_find_stub_sec.
	(elf32_arm_create_stub): Pass stub type down to elf32_arm_add_stub.
	(elf32_arm_size_stubs): Pass stub type when calling
	elf32_arm_create_or_find_stub_sec for Cortex-A8 erratum veneers.
	(bfd_elf32_arm_keep_private_stub_output_sections): New function.

ld/
	* emultempl/armelf.em (arm_elf_before_allocation): Call
	bfd_elf32_arm_keep_private_stub_output_sections before generic
	before_allocation function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Sync config.guess and config.sub with FSF GCC mainline versions
@ 2016-05-23 11:03 sergiodj+buildbot
  2016-05-23 11:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b43b853577ed4fb6cc19b1faa17e8fbea3c58be7 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: b43b853577ed4fb6cc19b1faa17e8fbea3c58be7

Sync config.guess and config.sub with FSF GCC mainline versions


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove unused libthread_db td_thr_validate reference
@ 2016-05-23 12:49 sergiodj+buildbot
  2016-05-23 13:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 12:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0571b9934241e58a5325fc6e09298d0e3396280 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: d0571b9934241e58a5325fc6e09298d0e3396280

Remove unused libthread_db td_thr_validate reference

Native GDB looks up the function td_thr_validate from libthread_db.so
on Linux, but the value is never used.  This commit removes this dead
code.

gdb/ChangeLog:

	* nat/gdb_thread_db.h (td_thr_validate_ftype): Remove typedef.
	* linux-thread-db.c (struct thread_db_info) <td_thr_validate_p>:
	Remove field.
	(try_thread_db_load_1): Remove td_thr_validate initialization.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use standard_testfile in gdb.arch/thumb-prologue.exp and gdb.arch/thumb2-it.exp
@ 2016-05-23 15:08 sergiodj+buildbot
  2016-05-23 15:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ffd19d610b3807bd5e2622440e225adb12a6766b ***

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

Use standard_testfile in gdb.arch/thumb-prologue.exp and gdb.arch/thumb2-it.exp

This patch fixes the errors below:

Running /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.arch/thumb-prologue.exp ...
gdb compile failed, arm-linux-gnueabihf/bin/ld: cannot open output file /scratch/yao/gdb/build-git/arm-linux-gnueabihf/gdb/testsuite/gdb.arch/thumb-prologue: No such file or directory
collect2: error: ld returned 1 exit status
Running /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.arch/thumb2-it.exp ...
gdb compile failed, arm-linux-gnueabihf/bin/ld: cannot open output file /scratch/yao/gdb/build-git/arm-linux-gnueabihf/gdb/testsuite/gdb.arch/thumb2-it: No such file or directory

gdb/testsuite:

2016-05-23  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/thumb-prologue.exp: Use standard_testfile.
	* gdb.arch/thumb2-it.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Rename "class" named attributes.
@ 2016-05-23 15:43 sergiodj+buildbot
  2016-05-23 16:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c810e0b87a2084656af944fe269d8c2680ba5469 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: c810e0b87a2084656af944fe269d8c2680ba5469

[ARC] Rename "class" named attributes.

gas/
2016-05-23  Cupertino Miranda  <cmiranda@synopsys.com>

	* config/tc-arc.c (attributes_t): Renamed attribute class to
	attr_class.
	(find_opcode_match, assemble_insn, tokenize_extinsn): Changed.

opcode/
2016-05-23  Cupertino Miranda  <cmiranda@synopsys.com>

	* arc-dis.c (find_format, find_format, get_auxreg)
	(print_insn_arc): Changed.
	* arc-ext.h (INSERT_XOP): Likewise.

include/
2016-05-23  Cupertino Miranda  <cmiranda@synopsys.com>

	* opcode/arc.h (struct arc_opcode): Renamed attribute class to
	insn_class.
	(struct arc_flag_class): Renamed attribute class to flag_class.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Add XY registers, update neg instruction.
@ 2016-05-23 16:28 sergiodj+buildbot
  2016-05-23 16:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87789e08e5cb2191af1122ed98af2d6c023b3a0a ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 87789e08e5cb2191af1122ed98af2d6c023b3a0a

[ARC] Add XY registers, update neg instruction.

gas/
2016-05-23  Claudiu Zissulescu  <claziss@synopsys.com>

	* config/tc-arc.c (md_begin): Add XY registers.
	(cpu_types): Code density is default off for ARC EM.

opcodes/
2016-05-23  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-tbl.h (neg): New instruction variant.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable R_AARCH64_NONE for 64-bit code.
@ 2016-05-23 23:52 sergiodj+buildbot
  2016-05-24  0:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7f28d873c8bb26500e46828d34445cebfab7fd4 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: b7f28d873c8bb26500e46828d34445cebfab7fd4

Enable R_AARCH64_NONE for 64-bit code.

	* elfnn-aarch64.c: Unconditionally enable R_AARCH64_NULL and
	R_AARCH64_NONE.  Use HOWTO64 for R_AARCH64_NULL.
	* relocs.c: Add BFD_RELOC_AARCH64_NULL.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add myself as a write-after-approval GDB maintainer
@ 2016-05-24  9:33 sergiodj+buildbot
  2016-05-24 10:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24  9:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00a3cb9c7c69cf65fdce73079a445cb379ae7842 ***

Author: Yan-Ting Lin <currygt52@gmail.com>
Branch: master
Commit: 00a3cb9c7c69cf65fdce73079a445cb379ae7842

Add myself as a write-after-approval GDB maintainer

gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add "Yan-Ting Lin".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix syntax error in annota-input-while-running.exp
@ 2016-05-24 11:32 sergiodj+buildbot
  2016-05-24 12:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e70a7231e6347212258d43d2a46a20f7f7584386 ***

Author: Francis Ricci <francisjricci@gmail.com>
Branch: master
Commit: e70a7231e6347212258d43d2a46a20f7f7584386

Fix syntax error in annota-input-while-running.exp

This patch fixes a syntax error which caused a failure in
annota-input-while-running.exp to crash the test suite runner.

2016-05-24  Francis Ricci  <francisjricci@gmail.com>

	* gdb.base/annota-input-while-running.exp: Fix syntax error.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [Linux] Read vDSO range from /proc/PID/task/PID/maps instead of /proc/PID/maps
@ 2016-05-24 14:15 sergiodj+buildbot
  2016-05-24 15:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95e94c3f18aaf34fadcd9a2a882ffe6147b9acc3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 95e94c3f18aaf34fadcd9a2a882ffe6147b9acc3

[Linux] Read vDSO range from /proc/PID/task/PID/maps instead of /proc/PID/maps

... as it's _much_ faster.

Hacking the gdb.threads/attach-many-short-lived-threads.exp test to
spawn thousands of threads instead of dozens to stress and debug
timeout problems with gdb.threads/attach-many-short-lived-threads.exp,
I saw that GDB would spend several seconds just reading the
/proc/PID/smaps file, to determine the vDSO mapping range.  GDB opens
and reads the whole file just once, and caches the result, but even
that is too slow.  For example, with almost 8000 threads:

 $ ls /proc/3518/task/ | wc -l
 7906

reading the /proc/PID/smaps file grepping for "vdso" takes over 15
seconds :

 $ time cat /proc/3518/smaps | grep vdso
 7ffdbafee000-7ffdbaff0000 r-xp 00000000 00:00 0                          [vdso]

 real    0m15.371s
 user    0m0.008s
 sys     0m15.017s

Looking around the web for hints, I found a nice description of the
issue here:

 http://backtrace.io/blog/blog/2014/11/12/large-thread-counts-and-slow-process-maps/

The problem is that /proc/PID/smaps wants to show the mappings as
being thread stack, and that has the kernel iterating over all threads
in the thread group, for each mapping.

The fix is to use the "map" file under /proc/PID/task/PID/ instead of
the /proc/PID/ one, as the former doesn't mark thread stacks for all
threads.

That alone drops the timing to the millisecond range on my machine:

 $ time cat /proc/3518/task/3518/smaps | grep vdso
 7ffdbafee000-7ffdbaff0000 r-xp 00000000 00:00 0                          [vdso]

 real    0m0.150s
 user    0m0.009s
 sys     0m0.084s

And since we only need the vdso mapping's address range, we can use
"maps" file instead of "smaps", and it's even cheaper:

/proc/PID/task/PID/maps :

 $ time cat /proc/3518/task/3518/maps | grep vdso
 7ffdbafee000-7ffdbaff0000 r-xp 00000000 00:00 0                          [vdso]

 real    0m0.027s
 user    0m0.000s
 sys     0m0.017s

gdb/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-tdep.c (find_mapping_size): Delete.
	(linux_vsyscall_range_raw): Rewrite reading from
	/proc/PID/task/PID/maps directly instead of using
	gdbarch_find_memory_regions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [Linux] Avoid refetching core-of-thread if thread hasn't run
@ 2016-05-24 14:24 sergiodj+buildbot
  2016-05-24 16:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ad3de988d2f41c72de66613c68ed78507a3abbd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1ad3de988d2f41c72de66613c68ed78507a3abbd

[Linux] Avoid refetching core-of-thread if thread hasn't run

Hacking the gdb.threads/attach-many-short-lived-threads.exp test to
spawn thousands of threads instead of dozens, I saw GDB having trouble
keeping up with threads being spawned too fast, when it tried to stop
them all.  This was because while gdb is doing that, it updates the
thread list to make sure no new thread has sneaked in that might need
to be paused.  It does this a few times until it sees no-new-threads
twice in a row.  The thread listing update itself is not that
expensive, however, in the Linux backend, updating the threads list
calls linux_common_core_of_thread for each LWP to record on which core
each LWP was last seen running, which opens/reads/closes a /proc file
for each LWP which becomes expensive when you need to do it for
thousands of LWPs.

perf shows gdb in linux_common_core_of_thread 44% of the time, in the
stop_all_threads -> update_thread_list path in this use case.

This patch simply makes linux_common_core_of_thread avoid updating the
core the thread is bound to if the thread hasn't run since the last
time we updated that info.  This makes linux_common_core_of_thread
disappear into the noise in the perf report.

gdb/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (linux_resume_one_lwp_throw): Clear the LWP's core
	field.
	(linux_nat_update_thread_list): Don't fetch the core if already
	known.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [Linux] Optimize PID -> struct lwp_info lookup
@ 2016-05-24 14:34 sergiodj+buildbot
  2016-05-24 17:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 774113b02f41ded4d9ba4d18571ee5024312ad1b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 774113b02f41ded4d9ba4d18571ee5024312ad1b

[Linux] Optimize PID -> struct lwp_info lookup

Hacking the gdb.threads/attach-many-short-lived-threads.exp test to
spawn thousands of threads instead of dozens, and running gdb under
perf, I saw that GDB was spending most of the time in find_lwp_pid:

   - captured_main
      - 93.61% catch_command_errors
         - 87.41% attach_command
            - 87.40% linux_nat_attach
               - 87.40% linux_proc_attach_tgid_threads
                  - 82.38% attach_proc_task_lwp_callback
                     - 81.01% find_lwp_pid
                          5.30% ptid_get_lwp
                        + 0.10% ptid_lwp_p
                     + 0.64% add_thread
                     + 0.26% set_running
                     + 0.24% set_executing
                       0.12% ptid_get_lwp
                     + 0.01% ptrace
                     + 0.01% add_lwp

attach_proc_task_lwp_callback is called once for each LWP that we
attach to, found by listing the /proc/PID/task/ directory.  In turn,
attach_proc_task_lwp_callback calls find_lwp_pid to check whether the
LWP we're about to try to attach to is already known.  Since
find_lwp_pid does a linear walk over the whole LWP list, this becomes
quadratic.  We do the /proc/PID/task/ listing until we get two
iterations in a row where we found no new threads.  So the second and
following times we walk the /proc/PID/task/ dir, we're going to take
an even worse find_lwp_pid hit.

Fix this by adding a hash table keyed by LWP PID, for fast lookup.

The linked list embedded in the LWP structure itself is kept, and made
a double-linked list, so that removals from that list are O(1).  An
earlier version of this patch got rid of this list altogether, but
that revealed hidden dependencies / assumptions on how the list is
sorted.  For example, killing a process and then waiting for all the
LWPs status using iterate_over_lwps only works as is because the
leader LWP is always last in the list.  So I thought it better to take
an incremental approach and make this patch concern itself _only_ with
the PID lookup optimization.

gdb/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (lwp_lwpid_htab): New htab.
	(lwp_info_hash, lwp_lwpid_htab_eq, lwp_lwpid_htab_create)
	(lwp_lwpid_htab_add_lwp): New functions.
	(lwp_list): Tweak comment.
	(lwp_list_add, lwp_list_remove, lwp_lwpid_htab_remove_pid): New
	functions.
	(purge_lwp_list): Rewrite, using htab_traverse_noresize.
	(add_initial_lwp): Add lwp to htab too.  Use lwp_list_add.
	(delete_lwp): Use lwp_list_remove.  Remove htab too.
	(find_lwp_pid): Search in htab.
	(_initialize_linux_nat): Call lwp_lwpid_htab_create.
	* linux-nat.h (struct lwp_info) <prev>: New field.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side
@ 2016-05-24 14:44 sergiodj+buildbot
  2016-05-24 19:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72b049d38ce85c51fc9f97ee64b00a47be5ebe94 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 72b049d38ce85c51fc9f97ee64b00a47be5ebe94

Make gdb/linux-nat.c consider a waitstatus pending on the infrun side

Working on the fix for gdb/19828, I saw
gdb.threads/attach-many-short-lived-threads.exp fail once in an
unusual way.  Unfortunately I didn't keep debug logs, but it's an
issue similar to what's been fixed in remote.c a while ago --
linux-nat.c was not fetching the pending status from the right place.

gdb/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (get_pending_status): If the thread reported the
	event to the core and it's pending, use the pending status signal
	number.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR gdb/19828: gdb -p <process from a container>: internal error
@ 2016-05-24 14:54 sergiodj+buildbot
  2016-05-24 19:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 026a91747567565bf2956fae98fed6a958151aab ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 026a91747567565bf2956fae98fed6a958151aab

Fix PR gdb/19828: gdb -p <process from a container>: internal error

When GDB attaches to a process, it looks at the /proc/PID/task/ dir
for all clone threads of that process, and attaches to each of them.

Usually, if there is more than one clone thread, it means the program
is multi threaded and linked with pthreads.  Thus when GDB soon after
attaching finds and loads a libthread_db matching the process, it'll
add a thread to the thread list for each of the initially found
lower-level LWPs.

If, however, GDB fails to find/load a matching libthread_db, nothing
is adding the LWPs to the thread list.  And because of that, "detach"
hits an internal error:

  (gdb) PASS: gdb.threads/clone-attach-detach.exp: fg attach 1: attach
  info threads
    Id   Target Id         Frame
  * 1    LWP 6891 "clone-attach-de" 0x00007f87e5fd0790 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:84
  (gdb) FAIL: gdb.threads/clone-attach-detach.exp: fg attach 1: info threads shows two LWPs
  detach
  .../src/gdb/thread.c:1010: internal-error: is_executing: Assertion `tp' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)
  FAIL: gdb.threads/clone-attach-detach.exp: fg attach 1: detach (GDB internal error)

>From here:

  ...
  #8  0x00000000007ba7cc in internal_error (file=0x98ea68 ".../src/gdb/thread.c", line=1010, fmt=0x98ea30 "%s: Assertion `%s' failed.")
      at .../src/gdb/common/errors.c:55
  #9  0x000000000064bb83 in is_executing (ptid=...) at .../src/gdb/thread.c:1010
  #10 0x00000000004c23bb in get_pending_status (lp=0x12c5cc0, status=0x7fffffffdc0c) at .../src/gdb/linux-nat.c:1235
  #11 0x00000000004c2738 in detach_callback (lp=0x12c5cc0, data=0x0) at .../src/gdb/linux-nat.c:1317
  #12 0x00000000004c1a2a in iterate_over_lwps (filter=..., callback=0x4c2599 <detach_callback>, data=0x0) at .../src/gdb/linux-nat.c:899
  #13 0x00000000004c295c in linux_nat_detach (ops=0xe7bd30, args=0x0, from_tty=1) at .../src/gdb/linux-nat.c:1358
  #14 0x000000000068284d in delegate_detach (self=0xe7bd30, arg1=0x0, arg2=1) at .../src/gdb/target-delegates.c:34
  #15 0x0000000000694141 in target_detach (args=0x0, from_tty=1) at .../src/gdb/target.c:2241
  #16 0x0000000000630582 in detach_command (args=0x0, from_tty=1) at .../src/gdb/infcmd.c:2975
  ...

Tested on x86-64 Fedora 23.  Also confirmed the test passes against
gdbserver with "maint set target-non-stop".

gdb/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (attach_proc_task_lwp_callback): Mark the lwp
	resumed, and add the thread to GDB's thread list.

testsuite/ChangeLog:
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* gdb.threads/clone-attach-detach.c: New file.
	* gdb.threads/clone-attach-detach.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR python/17981
@ 2016-05-24 16:15 sergiodj+buildbot
  2016-05-24 20:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 16:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1957f6b89f3db02d51e3e3361de6af073a03f19d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1957f6b89f3db02d51e3e3361de6af073a03f19d

Fix PR python/17981

PR python/17981 notes that gdb.breakpoints() returns None when there
are no breakpoints; whereas an empty list or tuple would be more in
keeping with Python and the documentation.

This patch fixes the bug by changing the no-breakpoint return to make
an empty tuple.

Built and regtested on x86-64 Fedora 23.

2016-05-23  Tom Tromey  <tom@tromey.com>

	PR python/17981:
	* python/py-breakpoint.c (gdbpy_breakpoints): Return a new tuple
	when there are no breakpoints.

2016-05-23  Tom Tromey  <tom@tromey.com>

	* python.texi (Basic Python): Document gdb.breakpoints return.

2016-05-23  Tom Tromey  <tom@tromey.com>

	PR python/17981:
	* gdb.python/py-breakpoint.exp (test_bkpt_basic): Add test for
	no-breakpoint case.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] add nb_inplace_divide for python 2
@ 2016-05-24 16:24 sergiodj+buildbot
  2016-05-24 21:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2b7f516fc688975ea22ad3cf2066c6972454fdc ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: e2b7f516fc688975ea22ad3cf2066c6972454fdc

add nb_inplace_divide for python 2

Python 2's PyNumberMethods has nb_inplace_divide, but Python 3 does
not.  This patch adds it for Python 2.

This buglet didn't cause much fallout because the only non-NULL entry
in value_object_as_number after this is for valpy_divide; and the
missing slot caused it to slide up to nb_floor_divide (where
nb_true_divide was intended).

2016-05-24  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (value_object_as_number): Add
	nb_inplace_divide for Python 2.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR python/17386 - add __index__ method to gdb.Value
@ 2016-05-24 16:34 sergiodj+buildbot
  2016-05-24 22:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddae946278bf4269370f7d945732485ad13469fa ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: ddae946278bf4269370f7d945732485ad13469fa

Fix PR python/17386 - add __index__ method to gdb.Value

This patch fixes PR python/17386.

The bug is that gdb.Value does not implement the Python __index__
method.  This method is needed to convert a Python object to an index
and is used by various operations in Python, such as indexing an
array.

The fix is to implement the nb_index method for gdb.Value.

nb_index was added in Python 2.5.  I don't have a good way to test
Python 2.4, but I made an attempt to accomodate it.

I chose to use valpy_long in all cases because this simplifies porting
to Python 3, and because there didn't seem to be any harm.

Built and regtested on x86-64 Fedora 23.

2016-05-24  Tom Tromey  <tom@tromey.com>

	PR python/17386:
	* python/py-value.c (value_object_as_number): Add
	nb_inplace_floor_divide, nb_inplace_true_divide, nb_index.

2016-05-24  Tom Tromey  <tom@tromey.com>

	PR python/17386:
	* gdb.python/py-value.exp (test_value_numeric_ops): Add tests that
	use value as an index.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Unify `bfd_reloc_outofrange' error reporting code
@ 2016-05-24 20:01 sergiodj+buildbot
  2016-05-24 23:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7db9a74e9f03427ed2844a17cebecc5e793f38ef ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 7db9a74e9f03427ed2844a17cebecc5e793f38ef

MIPS/BFD: Unify `bfd_reloc_outofrange' error reporting code

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_relocate_section)
	<bfd_reloc_outofrange>: Unify error reporting code.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fortran, typeprint: Fix wrong indentation when ptype nested structures.
@ 2016-05-25  7:20 sergiodj+buildbot
  2016-05-25  8:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72b1705502a891e07d40ad215146c71193920801 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 72b1705502a891e07d40ad215146c71193920801

Fortran, typeprint: Fix wrong indentation when ptype nested structures.

Level of indentation was not proper handled when printing
the elements type's name.

Before:
type = Type t1
integer(kind=4) :: var_1
integer(kind=4) :: var_2
End Type t1

After:
type = Type t1
    integer(kind=4) :: var_1
    integer(kind=4) :: var_2
End Type t1

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* f-typeprint.c (f_type_print_base): Take print level into account.

gdb/testsuite/Changelog:
	* gdb.fortran/print_type.exp: Fix expected output.
	* gdb.fortran/whatis_type.exp: Fix expected output.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fortran, typeprint: Take level of details into account when printing elements of a structure.
@ 2016-05-25  7:30 sergiodj+buildbot
  2016-05-25  9:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b2db1fd27cea1323a7ae0beb9399c8e1c4a3741 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 9b2db1fd27cea1323a7ae0beb9399c8e1c4a3741

Fortran, typeprint: Take level of details into account when printing elements of a structure.

According to the typeprint's description, elements of a structure
should not be printed when show is < 1.
This variable is also used to distinguish the level of details
between "ptype" and "whatis" expressions.

Before:
(gdb) whatis t1v
type = Type t1
    integer(kind=4) :: t1_i
    real(kind=4) :: t1_r
End Type t1

After:
(gdb) whatis t1v
type = Type t1

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* f-typeprint.c (f_type_print_base): Don't print fields when show < 0.

gdb/testsuite/Changelog:
	* gdb.fortran/whatis_type.exp: Adapt expected output.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fortran, typeprint: Decrease level of details when printing elements of a structure.
@ 2016-05-25  7:40 sergiodj+buildbot
  2016-05-25 10:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e188eb36215c031304aa7d2630447e2d0726adf5 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: e188eb36215c031304aa7d2630447e2d0726adf5

Fortran, typeprint: Decrease level of details when printing elements of a structure.

According to the typeprint's description, the level of details is
decreased by one for the typeprint of elements of a structure.

Before:
(gdb) ptype t3v
type = Type t3
    integer(kind=4) :: t3_i
    Type t2
        integer(kind=4) :: t2_i
        Type t1
            integer(kind=4) :: t1_i
            real(kind=4) :: t1_r
        End Type t1 :: t1_n
    End Type t2 :: t2_n
End Type t3

After:
(gdb) ptype t3v
type = Type t3
    integer(kind=4) :: t3_i
    Type t2 :: t2_n
End Type t3

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* f-typeprint.c (f_type_print_base): Decrease show by one.

gdb/testsuite/Changelog:
	* gdb.fortran/type.f90: Add nested structures.
	* gdb.fortran/whatis-type.exp: Whatis/ptype nested structures.
	* gdb.fortran/derived-type.exp: Adapt expected output.
	* gdb.fortran/vla-type.exp: Adapt expected output.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fortran, testsuite: Add testcases for nested structures.
@ 2016-05-25  7:51 sergiodj+buildbot
  2016-05-25 11:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  7:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86d8a84882643db4d8c28cea8e4a358465cb11f5 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 86d8a84882643db4d8c28cea8e4a358465cb11f5

Fortran, testsuite: Add testcases for nested structures.

As as result of printing only the outer elements of nested structures,
some testcases have to be added to check for corner cases with VLA's.

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:
	* gdb.fortran/vla-type.exp: Access elements in nested structs.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fortran, testsuite: Fix duplicate testcase name.
@ 2016-05-25  8:02 sergiodj+buildbot
  2016-05-25 12:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25  8:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b70175dfa76c97e28d83cd09f3604933a7c05f5 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 8b70175dfa76c97e28d83cd09f3604933a7c05f5

Fortran, testsuite: Fix duplicate testcase name.

2016-05-25  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:
	* gdb.fortran/vla-type.exp: Fix testcase name.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] fix spelling of HAVE_LIBPYTHON2_4 in py-value.c
@ 2016-05-25 14:18 sergiodj+buildbot
  2016-05-25 15:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 14:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bd787e8774f96712d2e15a4094f094e00ff45ba ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 7bd787e8774f96712d2e15a4094f094e00ff45ba

fix spelling of HAVE_LIBPYTHON2_4 in py-value.c

Ulrich pointed out that an earlier patch had misspelled
HAVE_LIBPYTHON2_4, adding an extra "_".  This caused a build failure.
This patch fixes the bug.

2016-05-25  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (value_object_as_number): Use correct spelling
	of HAVE_LIBPYTHON2_4.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip an archive element if not added by linker
@ 2016-05-25 15:55 sergiodj+buildbot
  2016-05-25 16:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b95a0a3177bcf797c8f5ad6a7d276fb6275352b7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: b95a0a3177bcf797c8f5ad6a7d276fb6275352b7

Skip an archive element if not added by linker

During archive rescan to resolve symbol references for files added by
LTO, linker add_archive_element callback is called to check if an
archive element should added.  After all IR symbols have been claimed,
linker won't claim new IR symbols and shouldn't add the LTO archive
element.  This patch updates linker add_archive_element callback to
return FALSE when seeing an LTO archive element during rescan and
changes ELF linker to skip such archive element.

bfd/

	PR ld/20103
	* cofflink.c (coff_link_check_archive_element): Return TRUE if
	linker add_archive_element callback returns FALSE.
	* ecoff.c (ecoff_link_check_archive_element): Likewise.
	* elf64-ia64-vms.c (elf64_vms_link_add_archive_symbols): Skip
	archive element if linker add_archive_element callback returns
	FALSE.
	* elflink.c (elf_link_add_archive_symbols): Likewise.
	* pdp11.c (aout_link_check_ar_symbols): Likewise.
	* vms-alpha.c (alpha_vms_link_add_archive_symbols): Likewise.
	* xcofflink.c (xcoff_link_check_dynamic_ar_symbols): Likewise.
	(xcoff_link_check_ar_symbols): Likewise.

ld/

	PR ld/20103
	* ldmain.c (add_archive_element): Don't claim new IR symbols
	after all IR symbols have been claimed.
	* plugin.c (plugin_call_claim_file): Remove no_more_claiming
	check.
	* testsuite/ld-plugin/lto.exp (pr20103): New proc.
	Run PR ld/20103 tests.
	* testsuite/ld-plugin/pr20103a.c: New file.
	* testsuite/ld-plugin/pr20103b.c: Likewise.
	* testsuite/ld-plugin/pr20103c.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable 64-bit archives in ar and ranlib
@ 2016-05-25 17:04 sergiodj+buildbot
  2016-05-25 17:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6cc316af931911da20249e19f9342e5cf8aeeff ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e6cc316af931911da20249e19f9342e5cf8aeeff

Enable 64-bit archives in ar and ranlib

Since existing ld and gold support the 64-bit (MIPS) ELF archives, we
can use the 64-bit (MIPS) ELF archives as 64-bit archives.  Since the
plugin target is used to create archive in plugin-enabled ar, we need
a way to enable 64-bit archives in the plugin target.  This patch adds
--enable-64-bit-archive to bfd to force 64-bit archives in ar and
ranlib.  Since both 64-bit MIPS and s390 ELF targets currently use
64-bit archives, 64-bit archives are enabled by default for them.
64-bit archive is generated automatically if the archive is too big.

Tested on Linux/x86 and Linux/x86-64 with existing ld and gold.

bfd/

	PR binutils/14625
	* archive.c (bfd_slurp_armap): Replace
	bfd_elf64_archive_slurp_armap with
	_bfd_archive_64_bit_slurp_armap.
	(bsd_write_armap): Call _bfd_archive_64_bit_write_armap if
	BFD64 is defined and the archive is too big.
	(coff_write_armap): Likewise.
	* archive64.c (bfd_elf64_archive_slurp_armap): Renamed to ...
	(_bfd_archive_64_bit_slurp_armap): This.
	(bfd_elf64_archive_write_armap): Renamed to ...
	(_bfd_archive_64_bit_write_armap): This.
	* configure.ac: Add --enable-64-bit-archive.
	(want_64_bit_archive): New.  Set to true by default for 64-bit
	MIPS and s390 ELF targets.
	(USE_64_BIT_ARCHIVE): New AC_DEFINE.
	* config.in: Regenerated.
	* configure: Likewise.
	* elf64-mips.c (bfd_elf64_archive_functions): Removed.
	(bfd_elf64_archive_slurp_armap): Likewise.
	(bfd_elf64_archive_write_armap): Likewise.
	(bfd_elf64_archive_slurp_extended_name_table): Likewise.
	(bfd_elf64_archive_construct_extended_name_table): Likewise.
	(bfd_elf64_archive_truncate_arname): Likewise.
	(bfd_elf64_archive_read_ar_hdr): Likewise.
	(bfd_elf64_archive_write_ar_hdr): Likewise.
	(bfd_elf64_archive_openr_next_archived_file): Likewise.
	(bfd_elf64_archive_get_elt_at_index): Likewise.
	(bfd_elf64_archive_generic_stat_arch_elt): Likewise.
	(bfd_elf64_archive_update_armap_timestamp): Likewise.
	* elf64-s390.c (bfd_elf64_archive_functions): Removed.
	(bfd_elf64_archive_slurp_armap): Likewise.
	(bfd_elf64_archive_write_armap): Likewise.
	(bfd_elf64_archive_slurp_extended_name_table): Likewise.
	(bfd_elf64_archive_construct_extended_name_table): Likewise.
	(bfd_elf64_archive_truncate_arname): Likewise.
	(bfd_elf64_archive_read_ar_hdr): Likewise.
	(bfd_elf64_archive_write_ar_hdr): Likewise.
	(bfd_elf64_archive_openr_next_archived_file): Likewise.
	(bfd_elf64_archive_get_elt_at_index): Likewise.
	(bfd_elf64_archive_generic_stat_arch_elt): Likewise.
	(bfd_elf64_archive_update_armap_timestamp): Likewise.
	* elfxx-target.h (TARGET_BIG_SYM): Use _bfd_archive_64_bit on
	BFD_JUMP_TABLE_ARCHIVE if USE_64_BIT_ARCHIVE is defined and
	bfd_elfNN_archive_functions isn't defined.
	(TARGET_LITTLE_SYM): Likewise.
	* libbfd-in.h (_bfd_archive_64_bit_slurp_armap): New prototype.
	(_bfd_archive_64_bit_write_armap): Likewise.
	(_bfd_archive_64_bit_slurp_extended_name_table): New macro.
	(_bfd_archive_64_bit_construct_extended_name_table): Likewise.
	(_bfd_archive_64_bit_truncate_arname): Likewise.
	(_bfd_archive_64_bit_read_ar_hdr): Likewise.
	(_bfd_archive_64_bit_write_ar_hdr): Likewise.
	(_bfd_archive_64_bit_openr_next_archived_file): Likewise.
	(_bfd_archive_64_bit_get_elt_at_index): Likewise.
	(_bfd_archive_64_bit_generic_stat_arch_elt): Likewise.
	(_bfd_archive_64_bit_update_armap_timestamp): Likewise.
	* libbfd.h: Regenerated.
	* plugin.c (plugin_vec): Use _bfd_archive_64_bit on
	BFD_JUMP_TABLE_ARCHIVE if USE_64_BIT_ARCHIVE is defined.

binutils/

	PR binutils/14625
	* NEWS: Mention --enable-64-bit-archive.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Reimplement .no87/.nommx/.nosse/.noavx directives
@ 2016-05-25 17:39 sergiodj+buildbot
  2016-05-25 19:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 293f5f65435c4d309cbf463e941a8bd5ae50c02d ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 293f5f65435c4d309cbf463e941a8bd5ae50c02d

Reimplement .no87/.nommx/.nosse/.noavx directives

Move all .noXXX directives to cpu_noarch.

gas/

	* config/tc-i386.c (arch_entry): Remove negated.
	(noarch_entry): New struct.
	(cpu_arch): Updated.  Remove .no87, .nommx, .nosse and .noavx.
	(cpu_noarch): New.
	(set_cpu_arch): Check cpu_noarch after cpu_arch.
	(md_parse_option): Allow -march=+nosse.  Check cpu_noarch after
	cpu_arch.
	(output_message): New function.
	(show_arch): Use it.  Handle cpu_noarch.
	* testsuite/gas/i386/i386.exp: Run nommx-1, nommx-2, nommx-3,
	nosse-1, nosse-2, nosse-3, noavx-1 and noavx-2.
	* testsuite/gas/i386/noavx-1.l: New file.
	* testsuite/gas/i386/noavx-1.s: Likewise.
	* testsuite/gas/i386/noavx-2.s: Likewise.
	* testsuite/gas/i386/noavx-2.l: Likewise.
	* testsuite/gas/i386/nommx-1.s: Likewise.
	* testsuite/gas/i386/nommx-1.l: Likewise.
	* testsuite/gas/i386/nommx-2.s: Likewise.
	* testsuite/gas/i386/nommx-2.l: Likewise.
	* testsuite/gas/i386/nommx-3.s: Likewise.
	* testsuite/gas/i386/nommx-3.l: Likewise.
	* testsuite/gas/i386/nosse-1.s: Likewise.
	* testsuite/gas/i386/nosse-1.l: Likewise.
	* testsuite/gas/i386/nosse-2.s: Likewise.
	* testsuite/gas/i386/nosse-2.l: Likewise.
	* testsuite/gas/i386/nosse-3.s: Likewise.
	* testsuite/gas/i386/nosse-3.l: Likewise.

opcodes/

	* i386-gen.c (cpu_flag_init): Rename CPU_ANY87_FLAGS to
	CPU_ANY_X87_FLAGS.  Add CPU_ANY_MMX_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable VREX for AVX512 directives
@ 2016-05-25 18:50 sergiodj+buildbot
  2016-05-25 22:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1360d5830fc7695cd26214257c62f34b73070c8 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f1360d5830fc7695cd26214257c62f34b73070c8

Enable VREX for AVX512 directives

Enable VREX for AVX512 instructions with upper 16 vector registers.

gas/

	PR gas/20141
	* testsuite/gas/i386/i386.exp: Run x86-64-pr20141.
	* testsuite/gas/i386/x86-64-pr20141.d: New file.
	* testsuite/gas/i386/x86-64-pr20141.s: Likewise.

opcodes/

	PR gas/20141
	* i386-gen.c (cpu_flag_init): Add CpuVREX to CPU_AVX512F_FLAGS,
	CPU_AVX512CD_FLAGS, CPU_AVX512ER_FLAGS and CPU_AVX512PF_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable VREX for all AVX512 directives
@ 2016-05-25 19:18 sergiodj+buildbot
  2016-05-25 23:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 19:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3ad76370f8c79e4ae74ca6826e23bf417d5283a ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f3ad76370f8c79e4ae74ca6826e23bf417d5283a

Enable VREX for all AVX512 directives

Add all AVX512 bits to CPU_ANY_AVX_FLAGS.

	* i386-gen.c (cpu_flag_init): Add CpuVREX to CPU_AVX512DQ_FLAGS,
	CPU_AVX512BW_FLAGS, CPU_AVX512VL_FLAGS, CPU_AVX512IFMA_FLAGS
	and CPU_AVX512VBMI_FLAGS.  Add CpuAVX512DQ, CpuAVX512BW,
	CpuAVX512VL, CpuAVX512IFMA and CpuAVX512VBMI to
	CPU_ANY_AVX_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Report `bfd_reloc_outofrange' errors as such
@ 2016-05-25 20:20 sergiodj+buildbot
  2016-05-26  0:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-25 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de341542a60f7d3a80cc339db7d341b615cfa52f ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: de341542a60f7d3a80cc339db7d341b615cfa52f

MIPS/BFD: Report `bfd_reloc_outofrange' errors as such

A `bfd_reloc_outofrange' condition from `mips_elf_calculate_relocation'
currently triggers the warning callback, which in the case of LD prints
messages like:

foo.o: In function `foo':
(.text+0x0): warning: JALX to a non-word-aligned address

or:

foo.o: In function `foo':
(.text+0x0): warning: PC-relative load from unaligned address

and nothing else, which suggests this is a benign condition and link has
otherwise successfully run to completion.  This is however not the case,
the link terminates right away with no further messages and no output
produced.

Use the general error or warning info callback then, preserving the
message format.  Also set a BFD error condition so that a failure is
unambiguously reported.  Complement the change with a set of suitable
test suite additions.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_relocate_section)
	<bfd_reloc_outofrange>: Call `->einfo' rather than `->warning'.
	Call `bfd_set_error'.

	ld/
	* testsuite/ld-mips-elf/unaligned-jalx-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-lwpc-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-lwpc-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-lwpc-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-lwpc-3.d: New test.
	* testsuite/ld-mips-elf/unaligned-ldpc-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-ldpc-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-ldpc-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-ldpc-3.d: New test.
	* testsuite/ld-mips-elf/unaligned-ldpc-4.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-0.s: New test source.
	* testsuite/ld-mips-elf/unaligned-jalx-1.s: New test source.
	* testsuite/ld-mips-elf/unaligned-jalx-2.s: New test source.
	* testsuite/ld-mips-elf/unaligned-insn.s: New test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-0.s: New test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-1.s: New test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-2.s: New test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-3.s: New test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-0.s: New test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-1.s: New test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-2.s: New test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-3.s: New test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-4.s: New test source.
	* testsuite/ld-mips-elf/unaligned-syms.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] metag: add extern C to header
@ 2016-05-26 10:15 sergiodj+buildbot
  2016-05-26 11:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94740f9c4b20ec88a5e33823a4da13d6da311a22 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 94740f9c4b20ec88a5e33823a4da13d6da311a22

metag: add extern C to header

include/ChangeLog:

2016-05-26  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/metag.h: wrap declarations in extern "C".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Don't stop processing on `bfd_reloc_outofrange'
@ 2016-05-26 11:56 sergiodj+buildbot
  2016-05-26 12:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-26 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed53407eec9eba3b55a3a00fb7eaa7eddbf01363 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: ed53407eec9eba3b55a3a00fb7eaa7eddbf01363

MIPS/BFD: Don't stop processing on `bfd_reloc_outofrange'

Upon a `bfd_reloc_outofrange' error continue processing so that any
further issues are also reported, similarly to how `bfd_reloc_overflow'
is handled.  Adjust message formatting accordingly, using `%X' to abort
processing at conclusion.

Reduce the number of test cases by grouping relocations the handling of
which can now be verified together with a single source and dump.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_relocate_section)
	<bfd_reloc_outofrange>: Use the `%X%H' rather than `%C' format
	for message.  Continue processing rather than returning failure.

	ld/
	* testsuite/ld-mips-elf/unaligned-jalx-0.d: Fold
	`unaligned-jalx-2' here.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-0.d: Fold
	`unaligned-jalx-mips16-2' here.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-0.d: Fold
	`unaligned-jalx-micromips-2' here.
	* testsuite/ld-mips-elf/unaligned-jalx-0.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-jalx-1.d: Update error
	message.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-2.d: Remove
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-2.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-0.d: Fold
	`unaligned-lwpc-3' here.
	* testsuite/ld-mips-elf/unaligned-lwpc-0.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-lwpc-1.d: Fold
	`unaligned-lwpc-2' here.
	* testsuite/ld-mips-elf/unaligned-lwpc-1.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-lwpc-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-lwpc-2.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-lwpc-3.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-lwpc-3.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-0.d: Fold
	`unaligned-ldpc-4' here.
	* testsuite/ld-mips-elf/unaligned-ldpc-0.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-ldpc-1.d: Update error
	message.  Fold `unaligned-ldpc-2' and `unaligned-ldpc-3' here.
	* testsuite/ld-mips-elf/unaligned-ldpc-1.s: Update accordingly.
	* testsuite/ld-mips-elf/unaligned-ldpc-2.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-ldpc-2.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-3.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-ldpc-3.s: Remove test source.
	* testsuite/ld-mips-elf/unaligned-ldpc-4.d: Remove test.
	* testsuite/ld-mips-elf/unaligned-ldpc-4.s: Remove test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Delete removed tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for new POWER ISA 3.0 instructions.
@ 2016-05-27  0:21 sergiodj+buildbot
  2016-05-27  2:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27  0:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 19dfcc89e8d94526f011242041b700ede8834996 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 19dfcc89e8d94526f011242041b700ede8834996

Add support for new POWER ISA 3.0 instructions.

opcodes/

	* ppc-opc.c (CY): New define.  Document it.
	(powerpc_opcodes) <addex[.], lwzmx, vmsumudm>: New mnemonics.

gas/
	* testsuite/gas/ppc/altivec3.d <vmsumudm>: Add test.
	* testsuite/gas/ppc/altivec3.s: Likewise.
	* testsuite/gas/ppc/power9.d <addex[.], lwzmx, vmsumudm>: Add tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT
@ 2016-05-27 12:58 sergiodj+buildbot
  2016-05-27 15:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51415b9f309443261016ad1b63b9e350bbe3903d ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 51415b9f309443261016ad1b63b9e350bbe3903d

gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT

When evaluating an expression with EVAL_AVOID_SIDE_EFFECTS if the value
we return is forced to be of type not_lval then GDB will be unable to
take the address of the returned value.

Instead, we should properly initialise the LVAL of the returned value.

This commit builds on two previous commits 2520f728b710 (Forward
VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT) and
ac775bf4d35b (gdb: Forward VALUE_LVAL when avoiding side effects for
STRUCTOP_PTR), which in turn build on ac1ca910d74d (Fixes for PR
exp/15364).

This commit is currently untested due to my lack of access to an OpenCL
compiler, however, if follows the same pattern as the first two commits
mentioned above and so I believe that it is correct.

gdb/ChangeLog:

	* opencl-lang.c (evaluate_subexp_opencl): If
	EVAL_AVOID_SIDE_EFFECTS mode, forward the VALUE_LVAL attribute to
	the returned value in the STRUCTOP_STRUCT case.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Improve the MSP430 disassembler's handling of memory read errors.
@ 2016-05-27 13:08 sergiodj+buildbot
  2016-05-27 16:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 13:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77d66e7b303f6fa65dd2ca4abce6393d6ea70a8f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 77d66e7b303f6fa65dd2ca4abce6393d6ea70a8f

Improve the MSP430 disassembler's handling of memory read errors.

	PR target/20150
	* msp430-dis.c (msp430dis_read_two_bytes): New function.
	(msp430dis_opcode_unsigned): New function.
	(msp430dis_opcode_signed): New function.
	(msp430_singleoperand): Use the new opcode reading functions.
	Only disassenmble bytes if they were successfully read.
	(msp430_doubleoperand): Likewise.
	(msp430_branchinstr): Likewise.
	(msp430x_callx_instr): Likewise.
	(print_insn_msp430): Check that it is safe to read bytes before
	attempting disassembly.  Use the new opcode reading functions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Correct CpuMax in i386-opc.h
@ 2016-05-27 14:08 sergiodj+buildbot
  2016-05-27 19:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 14:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e89c5eaa7208f06e927a79facff0316f4e550f6f ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e89c5eaa7208f06e927a79facff0316f4e550f6f

Correct CpuMax in i386-opc.h

CpuMax should be CpuIntel64, not CpuNo64.  i386-gen.c is updated to
verify that CpuMax is correct.  X86 assembler is updated to properly
set cpuamd64 and cpuintel64.

gas/

	PR gas/20154
	* config/tc-i386.c (intel64): New.
	(cpu_flags_match): Set cpuamd64 and cpuintel64.
	(md_parse_option): Set intel64 instead of cpuamd64 and
	cpuintel64.

opcodes/

	PR gas/20154
	* i386-gen.c (main): Fail if CpuMax is incorrect.
	* i386-opc.h (CpuMax): Set to CpuIntel64.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
@ 2016-05-27 15:15 sergiodj+buildbot
  2016-05-27 20:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 15:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e92bae62606702c1c07e095789ffed103e0e34c5 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e92bae62606702c1c07e095789ffed103e0e34c5

Replace CpuAMD64/CpuIntel64 with AMD64/Intel64

AMD64 vs CpuIntel64 ISA should be handled similar as AT&T vs Intel
syntax.  Since cpu_flags isn't sorted by position, we need to check
the whole cpu_flags array for the maximum position when verifying
CpuMax.

gas/

	PR gas/20154
	* config/tc-i386.c (cpu_flags_match): Don't set cpuamd64 nor
	cpuintel64.
	(match_template): Check Intel64/AMD64 ISA.

opcodes/

	PR gas/20154
	* i386-gen.c (cpu_flags): Remove CpuAMD64 and CpuIntel64.
	(opcode_modifiers): Add AMD64 and Intel64.
	(main): Properly verify CpuMax.
	* i386-opc.h (CpuAMD64): Removed.
	(CpuIntel64): Likewise.
	(CpuMax): Set to CpuNo64.
	(i386_cpu_flags): Remove cpuamd64 and cpuintel64.
	(AMD64): New.
	(Intel64): Likewise.
	(i386_opcode_modifier): Add amd64 and intel64.
	(i386-opc.tbl): Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
	on call and jmp.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Fix section symbol name fetching in relocation
@ 2016-05-27 21:56 sergiodj+buildbot
  2016-05-27 23:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ceab86af75e9870ecf2da772a0d867ca12521a24 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: ceab86af75e9870ecf2da772a0d867ca12521a24

MIPS/BFD: Fix section symbol name fetching in relocation

Symbol table entries for section symbols are different between IRIX and
traditional MIPS ELF targets in that IRIX entries have their `st_name'
member pointing at the section's name in the string table section, while
traditional entries have 0 there and the section header string table has
to be referred via the relevant section header's `shn_name' member
instead.

This is chosen with the `elf_backend_name_local_section_symbols' backend
and can be observed with `readelf -s' output for an IRIX object:

Symbol table '.symtab' contains 12 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00000000     0 SECTION LOCAL  DEFAULT    1 .text
     2: 00000000     0 SECTION LOCAL  DEFAULT    3 .data
     3: 00000000     0 SECTION LOCAL  DEFAULT    4 .bss
     4: 00000000     0 SECTION LOCAL  DEFAULT    5 .reginfo
     5: 00000000     0 SECTION LOCAL  DEFAULT    6 .MIPS.abiflags
     6: 00000000     0 SECTION LOCAL  DEFAULT    7 .pdr
     7: 00000000     0 SECTION LOCAL  DEFAULT    9 .gnu.attributes
     8: 00002000    16 FUNC    GLOBAL DEFAULT    1 foo
     9: 00004008     0 FUNC    LOCAL  DEFAULT    1 abar
    10: 00002008     0 FUNC    LOCAL  DEFAULT    1 afoo
    11: 00004000    16 FUNC    GLOBAL DEFAULT    1 bar

and a corresponding traditional object:

Symbol table '.symtab' contains 12 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00000000     0 SECTION LOCAL  DEFAULT    1
     2: 00000000     0 SECTION LOCAL  DEFAULT    3
     3: 00000000     0 SECTION LOCAL  DEFAULT    4
     4: 00004008     0 FUNC    LOCAL  DEFAULT    1 abar
     5: 00002008     0 FUNC    LOCAL  DEFAULT    1 afoo
     6: 00000000     0 SECTION LOCAL  DEFAULT    5
     7: 00000000     0 SECTION LOCAL  DEFAULT    6
     8: 00000000     0 SECTION LOCAL  DEFAULT    7
     9: 00000000     0 SECTION LOCAL  DEFAULT    9
    10: 00002000    16 FUNC    GLOBAL DEFAULT    1 foo
    11: 00004000    16 FUNC    GLOBAL DEFAULT    1 bar

respectively.  Consequently the right way to retrieve a section symbol's
name has to be chosen in `mips_elf_calculate_relocation' for the purpose
of error reporting.

Originally we produced symbol tables in the traditional object format
only and we handled it correctly until it was lost in a rewrite with:

commit 7403cb6305f5660fccc8869d3333a731102ae978
Author: Mark Mitchell <mark@codesourcery.com>
Date:   Wed Jun 30 20:13:43 1999 +0000

probably because of the extra pointer indirection added which made the
same expression have a different meaning.

With the addition of IRIX symbol table format with:

commit 174fd7f9556183397625dbfa99ef68ecd325c74b
Author: Richard Sandiford <rdsandiford@googlemail.com>
Date:   Mon Feb 9 08:04:00 2004 +0000

the bug has been partially covered and now when a relocation error is
triggered with an IRIX object the offending section symbol is correctly
reported:

tmpdir/dump0.o: In function `foo':
(.text+0x2000): relocation truncated to fit: R_MIPS_26 against `.text'
tmpdir/dump0.o: In function `bar':
(.text+0x4000): relocation truncated to fit: R_MIPS_26 against `.text'

because `bfd_elf_string_from_elf_section' retrieves the name from the
string table section.  With a traditional object however the function
returns an empty string and consequently `no symbol' is printed instead:

tmpdir/dump0.o: In function `foo':
(.text+0x2000): relocation truncated to fit: R_MIPS_26 against `no symbol'
tmpdir/dump0.o: In function `bar':
(.text+0x4000): relocation truncated to fit: R_MIPS_26 against `no symbol'

Restore the original semantics so that the section name is always
correctly retrieved.

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation): Also use the
	section name if `bfd_elf_string_from_elf_section' returns an
	empty string.

	ld/
	* testsuite/ld-mips-elf/reloc-local-overflow.d: New test.
	* testsuite/ld-mips-elf/reloc-local-overflow.s: Source for the
	new test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Include the addend in JALX's target alignment verification
@ 2016-05-27 22:07 sergiodj+buildbot
  2016-05-28  0:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 22:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc27bb0573a5e1ce1a6365fc06aeab9bd891fc3a ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: bc27bb0573a5e1ce1a6365fc06aeab9bd891fc3a

MIPS/BFD: Include the addend in JALX's target alignment verification

On RELA targets the addend can affect JALX target's alignment, so only
verify it once the whole relocation calculation has completed.

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation) <R_MIPS16_26>
	<R_MIPS_26, R_MICROMIPS_26_S1>: Include the addend in JALX's
	target alignment verification.

	ld/
	* testsuite/ld-mips-elf/unaligned-jalx-addend-0.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-mips16-0.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-mips16-1.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-micromips-0.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-micromips-1.d: New
	test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-0.s: New test
	source.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-1.s: New test
	source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Return void from linker callbacks
@ 2016-05-28  2:08 sergiodj+buildbot
  2016-05-28  3:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-28  2:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a72702bb30ec3f94627cfcae684823b413f20b9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1a72702bb30ec3f94627cfcae684823b413f20b9

Return void from linker callbacks

The ldmain.c implementation of these linker callback functions always
return true, so any code handling a false return is dead.  What's
more, some of the bfd backends abort if ever a false return is seen,
and there seems to be some confusion in gdb's compile-object-load.c.
The return value was never meant to be "oh yes, a multiple_definition
error occurred", but rather "out of memory or other catastrophic
failure".

This patch removes the status return on the callbacks that always
return true.  I kept the return status for "notice" because that one
does happen to need to return "out of memory".

include/
	* bfdlink.h (struct bfd_link_callbacks): Update comments.
	Return void from multiple_definition, multiple_common,
	add_to_set, constructor, warning, undefined_symbol,
	reloc_overflow, reloc_dangerous and unattached_reloc.
bfd/
	* aoutx.h: Adjust linker callback calls throughout file,
	removing dead code.
	* bout.c: Likewise.
	* coff-alpha.c: Likewise.
	* coff-arm.c: Likewise.
	* coff-h8300.c: Likewise.
	* coff-h8500.c: Likewise.
	* coff-i960.c: Likewise.
	* coff-mcore.c: Likewise.
	* coff-mips.c: Likewise.
	* coff-ppc.c: Likewise.
	* coff-rs6000.c: Likewise.
	* coff-sh.c: Likewise.
	* coff-tic80.c: Likewise.
	* coff-w65.c: Likewise.
	* coff-z80.c: Likewise.
	* coff-z8k.c: Likewise.
	* coff64-rs6000.c: Likewise.
	* cofflink.c: Likewise.
	* ecoff.c: Likewise.
	* elf-bfd.h: Likewise.
	* elf-m10200.c: Likewise.
	* elf-m10300.c: Likewise.
	* elf32-arc.c: Likewise.
	* elf32-arm.c: Likewise.
	* elf32-avr.c: Likewise.
	* elf32-bfin.c: Likewise.
	* elf32-cr16.c: Likewise.
	* elf32-cr16c.c: Likewise.
	* elf32-cris.c: Likewise.
	* elf32-crx.c: Likewise.
	* elf32-d10v.c: Likewise.
	* elf32-epiphany.c: Likewise.
	* elf32-fr30.c: Likewise.
	* elf32-frv.c: Likewise.
	* elf32-ft32.c: Likewise.
	* elf32-h8300.c: Likewise.
	* elf32-hppa.c: Likewise.
	* elf32-i370.c: Likewise.
	* elf32-i386.c: Likewise.
	* elf32-i860.c: Likewise.
	* elf32-ip2k.c: Likewise.
	* elf32-iq2000.c: Likewise.
	* elf32-lm32.c: Likewise.
	* elf32-m32c.c: Likewise.
	* elf32-m32r.c: Likewise.
	* elf32-m68hc1x.c: Likewise.
	* elf32-m68k.c: Likewise.
	* elf32-mep.c: Likewise.
	* elf32-metag.c: Likewise.
	* elf32-microblaze.c: Likewise.
	* elf32-moxie.c: Likewise.
	* elf32-msp430.c: Likewise.
	* elf32-mt.c: Likewise.
	* elf32-nds32.c: Likewise.
	* elf32-nios2.c: Likewise.
	* elf32-or1k.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-s390.c: Likewise.
	* elf32-score.c: Likewise.
	* elf32-score7.c: Likewise.
	* elf32-sh.c: Likewise.
	* elf32-sh64.c: Likewise.
	* elf32-spu.c: Likewise.
	* elf32-tic6x.c: Likewise.
	* elf32-tilepro.c: Likewise.
	* elf32-v850.c: Likewise.
	* elf32-vax.c: Likewise.
	* elf32-visium.c: Likewise.
	* elf32-xstormy16.c: Likewise.
	* elf32-xtensa.c: Likewise.
	* elf64-alpha.c: Likewise.
	* elf64-hppa.c: Likewise.
	* elf64-ia64-vms.c: Likewise.
	* elf64-mmix.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elf64-s390.c: Likewise.
	* elf64-sh64.c: Likewise.
	* elf64-x86-64.c: Likewise.
	* elflink.c: Likewise.
	* elfnn-aarch64.c: Likewise.
	* elfnn-ia64.c: Likewise.
	* elfxx-mips.c: Likewise.
	* elfxx-sparc.c: Likewise.
	* elfxx-tilegx.c: Likewise.
	* linker.c: Likewise.
	* pdp11.c: Likewise.
	* pe-mips.c: Likewise.
	* reloc.c: Likewise.
	* reloc16.c: Likewise.
	* simple.c: Likewise.
	* vms-alpha.c: Likewise.
	* xcofflink.c: Likewise.
	* elf32-rl78.c (get_symbol_value, get_romstart, get_ramstart): Delete
	status param.  Adjust calls to these and linker callbacks throughout.
	* elf32-rx.c: (get_symbol_value, get_gp, get_romstart,
	get_ramstart): Delete status param.  Adjust calls to these and
	linker callbacks throughout.
ld/
	* ldmain.c (multiple_definition, multiple_common, add_to_set,
	constructor_callback, warning_callback, undefined_symbol,
	reloc_overflow, reloc_dangerous, unattached_reloc): Return void.
	* emultempl/elf32.em: Adjust callback calls.
gdb/
	* compile/compile-object-load.c (link_callbacks_multiple_definition,
	link_callbacks_warning, link_callbacks_undefined_symbol,
	link_callbacks_undefined_symbol, link_callbacks_reloc_overflow,
	link_callbacks_reloc_dangerous,
	link_callbacks_unattached_reloc): Return void.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Enable local R_MIPS_26 overflow detection
@ 2016-05-28 10:13 sergiodj+buildbot
  2016-05-28 11:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 10:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7743482350c9c97484a429070db7d994a643a9eb ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 7743482350c9c97484a429070db7d994a643a9eb

MIPS/BFD: Enable local R_MIPS_26 overflow detection

The original MIPS SVR4 psABI defines the calculation for the R_MIPS_26
relocation in a complex way, as follows[1]:

Name        Value Field    Symbol   Calculation
R_MIPS_26     4   T-targ26 local    (((A << 2) | \
                                      (P & 0xf0000000)) + S) >> 2
              4   T-targ26 external (sign-extend(A << 2) + S) >> 2

This is further clarified, by correcting typos (already applied in the
excerpt above) in the 64-bit psABI extension[2].  A note is included in
both documents to specify that for the purpose of relocation processing
a local symbol is one with binding STB_LOCAL and type STT_SECTION, and
otherwise, a symbol is external.

We have both calculations implemented for the R_MIPS_26 relocation, and
by extension also for the R_MIPS16_26 and R_MICROMIPS_26_S1 relocations,
from now on collectively called jump relocations.  However our code uses
a different condition to tell local and external symbols apart, that is
it only checks for the STB_LOCAL binding and ignores the symbol type,
however for REL relocations only.  The external calculation is used for
all RELA jump relocations.

In reality the difference matters for jump relocations referring local
MIPS16 and, as from recent commit 44d3da233815 ("MIPS/GAS: Treat local
jump relocs the same no matter if REL or RELA"), also local microMIPS
symbols.  Such relocations are not converted to refer to corresponding
section symbols instead and retain the original local symbol reference.

It can be inferred from the relocation calculation definitions that the
addend is effectively unsigned for the local case and explicitly signed
for the external case.  With the REL relocation format it makes sense
given the limited range provided for by the field being relocated: the
use of an unsigned addend expands the range by one bit for the local
case, because a negative offset from a section symbol makes no sense,
and any usable negative offset from the original local symbol will have
worked out positive if converted to a section-relative reference.  In
the external case a signed addend gives more flexibility as offsets both
negative and positive can be used with a symbol.  Any such offsets will
typically have a small value.

The inclusion of the (P & 0xf0000000) component, ORed in the calculation
in the local case, seems questionable as bits 31:28 are not included in
the relocatable field and are masked out as the relocation is applied.
Their value is therefore irrelevant for output processing, the relocated
field ends up the same regardless of their value.  They could be used
for overflow detection, however this is precluded by adding them to bits
31:28 of the symbol referred, as the sum will not correspond to the
value calculated by the processor at run time whenever bits 31:28 of the
symbol referred are not all zeros, even though it is valid as long they
are the same as bits 31:28 of P.

We deal with this problem by ignoring any overflow resulting from the
local calculation.  This however makes us miss genuine overflow cases,
where 31:28 of the symbol referred are different from bits 31:28 of P,
and non-functional code is produced.

Given the situation, for the purpose of overflow detection we can change
our code to follow the original psABI and only treat the in-place addend
as unsigned in the section symbol case, permitting jumps to offsets
128MiB and above into section.  Sections so large may be uncommon, but
still a reasonable use case.  On the other hand such large offsets from
regular local symbols are not expected and it makes sense to support
(possibly small) negative offsets instead, also in consistency with what
we do for global symbols.

Drop the (P & 0xf0000000) component then, treat the addend as signed
with local non-section symbols and also detect an overflow in the result
of such calculation with local symbols.  NB it does not affect the value
computed for the relocatable field, it only affects overflow detection.

References:

[1] "SYSTEM V APPLICATION BINARY INTERFACE, MIPS RISC Processor
    Supplement, 3rd Edition", Figure 4-11: "Relocation Types", p. 4-19
    <http://www.linux-mips.org/pub/linux/mips/doc/ABI/mipsabi.pdf>

[2] "64-bit ELF Object File Specification, Draft Version 2.5", Table 32
    "Relocation Types", p. 45
    <http://techpubs.sgi.com/library/manuals/4000/007-4658-001/pdf/007-4658-001.pdf>

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation): <R_MIPS16_26>
	<R_MIPS_26, R_MICROMIPS_26_S1>: Drop the region bits of the
	reloc location from calculation, treat the addend as signed with
	local non-section symbols and enable overflow detection.

	ld/
	* testsuite/ld-mips-elf/jal-global-overflow-0.d: New test.
	* testsuite/ld-mips-elf/jal-global-overflow-1.d: New test.
	* testsuite/ld-mips-elf/jal-local-overflow-0.d: New test.
	* testsuite/ld-mips-elf/jal-local-overflow-1.d: New test.
	* testsuite/ld-mips-elf/jal-global-overflow.s: New test source.
	* testsuite/ld-mips-elf/jal-local-overflow.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Correctly handle `bfd_reloc_outofrange' with branches
@ 2016-05-28 10:23 sergiodj+buildbot
  2016-05-28 12:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 10:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99aefae6818be07a77739e0366121f2032916d9c ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 99aefae6818be07a77739e0366121f2032916d9c

MIPS/BFD: Correctly handle `bfd_reloc_outofrange' with branches

Fix internal errors like:

ld: BFD (GNU Binutils) 2.26.51.20160526 internal error, aborting at .../bfd/elfxx-mips.c:10278 in _bfd_mips_elf_relocate_section

ld: Please report this bug.

triggered by the `bfd_reloc_outofrange' condition on branch relocations.

	bfd/
	* elfxx-mips.c (b_reloc_p): New function.
	(_bfd_mips_elf_relocate_section) <bfd_reloc_outofrange>: Handle
	branch relocations.

	ld/
	* testsuite/ld-mips-elf/unaligned-branch.d: New test.
	* testsuite/ld-mips-elf/unaligned-branch.s: New test source.
	* testsuite/ld-mips-elf/unaligned-text.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add .noavx512XX directives to x86 assembler
@ 2016-05-29 15:10 sergiodj+buildbot
  2016-05-29 16:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 144b71e2a88e02d0b54d4f09cc652f353b46e455 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 144b71e2a88e02d0b54d4f09cc652f353b46e455

Add .noavx512XX directives to x86 assembler

Add .noavx512f, .noavx512cd, .noavx512er, .noavx512pf, .noavx512dq,
.noavx512bw, .noavx512vl, .noavx512ifma, .noavx512vbmi directives to x86
assembler.

gas/

	PR gas/20145
	* config/tc-i386.c (cpu_noarch): Add noavx512f, noavx512cd,
	noavx512er, noavx512pf, noavx512dq, noavx512bw, noavx512vl,
	noavx512ifma and noavx512vbmi.
	* doc/c-i386.texi: Mention noavx512f, noavx512cd, noavx512er,
	noavx512pf, noavx512dq, noavx512bw, noavx512vl, noavx512ifma
	and noavx512vbmi.
	* testsuite/gas/i386/i386.exp: Run noavx512-1 and noavx512-2.
	* testsuite/gas/i386/noavx512-1.l: New file.
	* testsuite/gas/i386/noavx512-1.s: Likewise.
	* testsuite/gas/i386/noavx512-2.l: Likewise.
	* testsuite/gas/i386/noavx512-2.s: Likewise.

opcodes/

	PR gas/20145
	* i386-gen.c (cpu_flag_init): Add CPU_ANY_AVX512F_FLAGS,
	CPU_ANY_AVX512CD_FLAGS, CPU_ANY_AVX512ER_FLAGS,
	CPU_ANY_AVX512PF_FLAGS, CPU_ANY_AVX512DQ_FLAGS,
	CPU_ANY_AVX512BW_FLAGS, CPU_ANY_AVX512VL_FLAGS,
	CPU_ANY_AVX512IFMA_FLAGS and CPU_ANY_AVX512VBMI_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] NEWS: Remove empty line.
@ 2016-05-29 16:52 sergiodj+buildbot
  2016-05-29 18:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c64e0f6165537efda112a9744e588f4ecac8ca41 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: c64e0f6165537efda112a9744e588f4ecac8ca41

NEWS: Remove empty line.

gdb/ChangeLog
2016-05-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* NEWS (N stop reply): Remove empty line.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] NEWS: QCatchSyscalls: simplify
@ 2016-05-29 18:59 sergiodj+buildbot
  2016-05-29 19:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-29 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aab3c527d779a8e833a469203336afcc17512559 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: aab3c527d779a8e833a469203336afcc17512559

NEWS: QCatchSyscalls: simplify

Standardize the QCatchSyscalls NEWS entry.

gdb/ChangeLog
2016-05-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* NEWS (QCatchSyscalls): Remove the parameter.  Include ...
	(QCatchSyscalls:1 in qSupported) ... this separate entry which got
	deleted.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum
@ 2016-05-30 12:29 sergiodj+buildbot
  2016-05-30 13:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a2b436ae9958a1029545c03201b7223ff33c150 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 3a2b436ae9958a1029545c03201b7223ff33c150

Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum

Make the code (maybe) more readable + primarily prepare it for [patch 2/2]
enum extension.

This change should have no code change impact.

gdb/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum
	* dwarf2read.c (enum pc_bounds_kind) New.
	(dwarf2_get_pc_bounds): Use it in the declaration.
	(process_psymtab_comp_unit_reader): Adjust caller.  Rename has_pc_info
	to cu_bounds_kind.
	(read_func_scope, read_lexical_block_scope, read_call_site_scope):
	Adjust callers.
	(dwarf2_get_pc_bounds): Use enum pc_bounds_kind in the definition.
	(dwarf2_get_subprogram_pc_bounds, get_scope_pc_bounds): Adjust callers.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR 15231: import bare DW_TAG_lexical_block
@ 2016-05-30 12:38 sergiodj+buildbot
  2016-05-30 14:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 12:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e385593eef98ac92be57159e141f4b805dadbbb3 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: e385593eef98ac92be57159e141f4b805dadbbb3

PR 15231: import bare DW_TAG_lexical_block

Local variables in lambdas are not accessible
https://sourceware.org/bugzilla/show_bug.cgi?id=15231

GDB: read_lexical_block_scope
  /* Ignore blocks with missing or invalid low and high pc attributes.  */
[...]
  if (!dwarf2_get_pc_bounds (die, &lowpc, &highpc, cu, NULL))
    return;

But sometimes there is:

FAIL: gcc-5.3.1-6.fc23.x86_64
 <2><92>: Abbrev Number: 11 (DW_TAG_lexical_block)
 <3><9c>: Abbrev Number: 13 (DW_TAG_structure_type)
    <9d>   DW_AT_name        : (indirect string, offset: 0x3c): <lambda()>
    [...]

Where DW_TAG_lexical_block has no attributes.  Such whole subtree is currently
dropped by GDB while I think it should just import all its children DIEs.

It even XFAIL->XPASSes gdb.ada/out_of_line_in_inlined.exp:
	commit 0fa7fe506c242b459c4c05d331e7c7d66fb52390
	Author: Joel Brobecker <brobecker@adacore.com>
	    out of line functions nested inside inline functions.
So I have removed that xfail.

gdb/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR c++/15231
	* dwarf2read.c (enum pc_bounds_kind): Add PC_BOUNDS_INVALID.
	(process_psymtab_comp_unit_reader, read_func_scope): Adjust callers.
	(read_lexical_block_scope): Import DIEs from bare DW_TAG_lexical_block.
	(read_call_site_scope): Adjust callers.
	(dwarf2_get_pc_bounds): Implement pc_bounds_invalid.
	(dwarf2_get_subprogram_pc_bounds, get_scope_pc_bounds): Adjust callers.

gdb/testsuite/ChangeLog
2016-05-30  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR c++/15231
	* gdb.ada/out_of_line_in_inlined.exp: Remove xfails.
	* gdb.dwarf2/dw2-lexical-block-bare.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add counter-cases for trace-condition.exp tests
@ 2016-05-30 17:04 sergiodj+buildbot
  2016-05-30 17:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7faeb45ae36426b827c49457cf7186d73756cccc ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7faeb45ae36426b827c49457cf7186d73756cccc

Add counter-cases for trace-condition.exp tests

In trace-condition.exp, tests are done by doing a conditional tracepoint
and validating that the trace contains all the frames that could be
collected if that condition is true.

E.g. test_tracepoints $trace_command "21 + 21 == 42" 10

This will always return true and collect the 10 frames possible to collect
with the test program.

However, if the condition evaluation is broken such that the condition is
unconditional we will not notice this problem.

This patch adds counter-cases to such conditions like so:

$trace_command "21 + 11 == 42" 0

This way such a problem would be noticed.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp: Add counter-case tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Move trace conditions tests from ftrace.exp to trace-condition.exp
@ 2016-05-30 17:13 sergiodj+buildbot
  2016-05-30 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d33646690c2e88624cd9646539d63d4144d03e8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 0d33646690c2e88624cd9646539d63d4144d03e8

Move trace conditions tests from ftrace.exp to trace-condition.exp

This patch moves conditional tests that were done in ftrace.exp to
trace-condition.exp.

Note that emit_ref is now tested by the anarg local variable there is no
need to test the register directly.

All emit calls have been tested using asserts before / after the move, to
ensure that the tests cover the same functions.

Note that these function were not covered before and are still not:
emit_gt_goto, emit_lt_goto, emit_pop, emit_unsigned_less.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp (test_ftrace_condition): Remove.
	Move condition tests...
	* gdb.trace/trace-condition.exp: Here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add emit_less_unsigned test in trace-condition.exp
@ 2016-05-30 17:22 sergiodj+buildbot
  2016-05-30 19:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a781823347ec9cd84e5ccc0bb8ddde48f8d302b6 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: a781823347ec9cd84e5ccc0bb8ddde48f8d302b6

Add emit_less_unsigned test in trace-condition.exp

This patch adds coverage for emit_less_unsigned.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.exp: Add emit_less_unsigned test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add variable length tests for emit_ref in trace-condition.exp
@ 2016-05-30 17:30 sergiodj+buildbot
  2016-05-30 20:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-30 17:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2320162a6219c664a8da2e2ff68b08d6f6c2ffcc ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 2320162a6219c664a8da2e2ff68b08d6f6c2ffcc

Add variable length tests for emit_ref in trace-condition.exp

This patch add variable length tests for emit_ref by reading the variable
passed as argument of 8 to 64 bit.

gdb/testsuite/ChangeLog:

	* gdb.trace/trace-condition.c (marker): Adapt signature to 8 to 64
	bits types.
	(main): Adapt to 8 to 64 bits types.
	* gdb.trace/trace-condition.exp: Add new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't needlessly clear xmemdup allocated memory.
@ 2016-05-31 11:20 sergiodj+buildbot
  2016-05-31 12:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-31 11:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c12969f8b53659f0d70b5e049c49b97a96826a3f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: c12969f8b53659f0d70b5e049c49b97a96826a3f

Don't needlessly clear xmemdup allocated memory.

	* xmemdup.c (xmemdup): Use xmalloc rather than xcalloc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [PR gdb/19893] Fix handling of synthetic C++ references
@ 2016-05-31 19:07 sergiodj+buildbot
  2016-05-31 20:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-05-31 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3326303bf5ae4c92f2fbbff387ce231a16c1c8bf ***

Author: Martin Galvan <martin.galvan@tallertechnologies.com>
Branch: master
Commit: 3326303bf5ae4c92f2fbbff387ce231a16c1c8bf

[PR gdb/19893] Fix handling of synthetic C++ references

https://sourceware.org/bugzilla/show_bug.cgi?id=19893

I've traced the main source of the problem to pieced_value_funcs.coerce_ref not being
implemented. Since gdb always assumes references are implemented as pointers, this
causes it to think that it's dealing with a NULL pointer, thus breaking any operations
involving synthetic references.

What I did here was implementing pieced_value_funcs.coerce_ref using some of the synthetic
pointer handling code from indirect_pieced_value, as Pedro suggested. I also made a few
adjustments to the reference printing code so that it correctly shows either the address
of the referenced value or (if it's non-addressable) the "<synthetic pointer>" string.

I also wrote some unit tests based on Dwarf::assemble; these took a while to make
because in most cases I needed a synthetic reference to a physical variable. Additionally,
I started working on a unit test for classes that have a vtable, but ran into a few issues
so that'll probably go in a future patch. One thing that should definitely be fixed is that
proc function_range (called for MACRO_AT_func) will always try to compile/link using gcc
with the default options instead of g++, thus breaking C++ compilations that require e.g. libstdc++.

gdb/ChangeLog:

	* dwarf2loc.c (coerce_pieced_ref, indirect_synthetic_pointer,
	fetch_const_value_from_synthetic_pointer): New functions.
	(indirect_pieced_value): Move lower half to indirect_synthetic_pointer.
	(pieced_value_funcs): Implement coerce_ref.
	* valops.c (value_addr): Call coerce_ref for synthetic references.
	* valprint.c (valprint_check_validity): Return true for synthetic
	references.  Also, don't show "<synthetic pointer>" if they reference
	addressable values.
	(generic_val_print_ref): Handle synthetic references.  Also move some
	code to print_ref_address.
	(print_ref_address, get_value_addr_contents): New functions.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/implref.exp: Rename to...
	* gdb.dwarf2/implref-const.exp: ...this.  Also add more test statements.
	* gdb.dwarf2/implref-array.c: New file.
	* gdb.dwarf2/implref-array.exp: Likewise.
	* gdb.dwarf2/implref-global.c: Likewise.
	* gdb.dwarf2/implref-global.exp: Likewise.
	* gdb.dwarf2/implref-struct.c: Likewise.
	* gdb.dwarf2/implref-struct.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sh: make constant unsigned to avoid narrowing
@ 2016-06-01  3:22 sergiodj+buildbot
  2016-06-01  8:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a2b5fccc630a7cb7e1c241e5249bf6e8917d917d ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: a2b5fccc630a7cb7e1c241e5249bf6e8917d917d

sh: make constant unsigned to avoid narrowing

Shifting into the sign bit of a 32 bit int and then converting to a unsigned
type is less straight forward than just shifting an unsigned value.

opcodes/ChangeLog:

2016-05-31  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* sh-opc.h (ARCH_SH_HAS_DSP): Make the shifted value an unsigned
	constant.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Wake up interruptible_select in remote_fileio ctrl-c handler
@ 2016-06-01  8:46 sergiodj+buildbot
  2016-06-01  9:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  8:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03d73f1fd9d89d89bdd021cad26693e4f6abc07a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 03d73f1fd9d89d89bdd021cad26693e4f6abc07a

Wake up interruptible_select in remote_fileio ctrl-c handler

As reported in PR 19998, after type ctrl-c, GDB hang there and does
not send interrupt.  It causes a fail in gdb.base/interrupt.exp.
All targets support remote fileio should be affected.

When we type ctrc-c, SIGINT is handled by remote_fileio_sig_set,
as shown below,

 #0  remote_fileio_sig_set (sigint_func=0x4495d0 <remote_fileio_ctrl_c_signal_handler(int)>) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:325
 #1  0x00000000004495de in remote_fileio_ctrl_c_signal_handler (signo=<optimised out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:349
 #2  <signal handler called>
 #3  0x00007ffff647ed83 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:81
 #4  0x00000000005530ce in interruptible_select (n=10, readfds=readfds@entry=0x7fffffffd730, writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0,
    timeout=timeout@entry=0x0) at /home/yao/SourceCode/gnu/gdb/git/gdb/event-top.c:1017
 #5  0x000000000061ab20 in stdio_file_read (file=<optimised out>, buf=0x12d02e0 "\n\022-\001", length_buf=16383)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/ui-file.c:577
 #6  0x000000000044a4dc in remote_fileio_func_read (buf=0x12c0360 "") at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:583
 #7  0x0000000000449598 in do_remote_fileio_request (uiout=<optimised out>, buf_arg=buf_arg@entry=0x12c0340)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/remote-fileio.c:1179

we don't set quit_serial_event,

  do
    {
      res = gdb_select (n, readfds, writefds, exceptfds, timeout);
    }
  while (res == -1 && errno == EINTR);

  if (res == 1 && FD_ISSET (fd, readfds))
    {
      errno = EINTR;
      return -1;
    }
  return res;

we can't go out of the loop above, and that is why GDB can't send
interrupt.

Recently, we stop throwing exception from SIGINT handler
(remote_fileio_ctrl_c_signal_handler)
https://sourceware.org/ml/gdb-patches/2016-03/msg00372.html, which
is correct, because gdb_select is interruptible.  However, in the
same patch series, we add interruptible_select later as a wrapper
to gdb_select, https://sourceware.org/ml/gdb-patches/2016-03/msg00375.html
and it is not interruptible (because of the loop in it) unless
select/poll-able file descriptors are marked.

This fix in this patch is to call quit_serial_event_set, so that we can
go out of the loop above, return -1 and set errno to EINTR.

2016-06-01  Yao Qi  <yao.qi@linaro.org>

	PR remote/19998
	* remote-fileio.c (remote_fileio_ctrl_c_signal_handler): Call
	quit_serial_event_set.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] infcmd, btrace: fix crash in 'finish' for tailcall-only frames
@ 2016-06-01  9:27 sergiodj+buildbot
  2016-06-01 10:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01  9:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3b5daf9f735999259c5a8f68b422850c59897e5 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: e3b5daf9f735999259c5a8f68b422850c59897e5

infcmd, btrace: fix crash in 'finish' for tailcall-only frames

Patch 7eb895307f53 Skip unwritable frames in command "finish"
skips non-writable frames in addition to tailcall frames.

If skip_tailcall_frames already returns NULL, skip_unwritable_frames
will be called with a NULL frame and crash in get_frame_arch.  This is
caught by gdb.btrace/tailcall-only.exp.

Further, if we ever end up with a mixture of tailcall and non-writable
frames, we may not skip all of them, as intended.

Loop over skip_tailcall_frames and skip_unwritable_frames as long as at least
one of them makes progress.

gdb/
	* infcmd.c (skip_finish_frames): New.
	(finish_command): Call skip_finish_frames.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add xmalloc_failed() function to common-utils.c in to avoid the need to link in libiberty's xmalloc code.
@ 2016-06-01 10:56 sergiodj+buildbot
  2016-06-01 11:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 10:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51403f74d96cc69f391fbd31389a9153a230b431 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 51403f74d96cc69f391fbd31389a9153a230b431

Add xmalloc_failed() function to common-utils.c in to avoid the need to link in libiberty's xmalloc code.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for some variants of the ARC nps400 rflt instruction.
@ 2016-06-01 15:39 sergiodj+buildbot
  2016-06-01 16:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 315f180f2f0a59af561180e4ed9387f4c7bada78 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 315f180f2f0a59af561180e4ed9387f4c7bada78

Add support for some variants of the ARC nps400 rflt instruction.

gas     * testsuite/gas/arc/nps-400-1.s: Add rflt variants with
        operands of types a,b,u6, 0,b,u6, and 0,b,limm.
        * testsuite/gas/arc/nps-400-1.d: Likewise.

opcodes * arc-nps400-tbl.h: Add operands a,b,u6, 0,b,u6, and
        0,b,limm to the rflt instruction.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/remote-fileio.c: Eliminate custom SIGINT signal handler
@ 2016-06-01 15:48 sergiodj+buildbot
  2016-06-01 17:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 15:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb7c96deb1a14ef7e8b51d5339a65a8064515c78 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bb7c96deb1a14ef7e8b51d5339a65a8064515c78

gdb/remote-fileio.c: Eliminate custom SIGINT signal handler

... and fix Ctrl-C races.

The current remote-fileio.c SIGINT/EINTR code can lose Ctrl-C --
there's a period where SIG_IGN is installed as signal handler, for
example.

Since:

 - remote.c no longer installs a custom SIGINT handler;

 - The current remote-fileio.c SIGINT handler is basically the same as
   the default SIGINT handler (event-top.c:handle_sigint), in
   principle, except that instead of setting the quit flag, it sets a
   separate flag.

I think we should be able to completely remove the remote-fileio.c
SIGINT handler, and centralize on the quit flag, thus fixing the
Ctrl-C race.

gdb/ChangeLog:
yyyy-mm-dd  Pedro Alves  <palves@redhat.com>

	* remote-fileio.c (remote_fio_ctrl_c_flag, remote_fio_sa)
	(remote_fio_osa)
	(remote_fio_ofunc, remote_fileio_sig_init, remote_fileio_sig_set)
	(remote_fileio_sig_exit, remote_fileio_ctrl_c_signal_handler):
	Delete.
	(remote_fileio_o_quit_handler): New global.
	(remote_fileio_quit_handler): New function.
	(remote_fileio_reply): Check the quit flag instead of the custom
	'remote_fio_ctrl_c_flag' flag.  Restore the quit handler instead
	of changing the SIGINT handler.
	(do_remote_fileio_request): Override the quit handler instead of
	changing the SIGINT handler.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add new Serbian translation for the bfd library.
@ 2016-06-01 16:03 sergiodj+buildbot
  2016-06-01 18:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-01 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 885a10879eea3cf7ccbb324109a56f0bc391dcfa ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 885a10879eea3cf7ccbb324109a56f0bc391dcfa

Add new Serbian translation for the bfd library.

	* po/sr.po: New Serbian translation.
	* configure.ac (ALL_LINGUAS): Add sr.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] add more extern C
@ 2016-06-02  1:33 sergiodj+buildbot
  2016-06-02  2:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02  1:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1fe0971e41a4097610862acabf54a896695fe834 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 1fe0971e41a4097610862acabf54a896695fe834

add more extern C

opcodes/ChangeLog:

2016-06-01  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* nds32-asm.h: Add extern "C".
	* sh-opc.h: Likewise.

bfd/ChangeLog:

2016-06-01  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-hppa.h: Add extern "C".
	* elf32-nds32.h: Likewise.
	* elf32-tic6x.h: Likewise.

include/ChangeLog:

2016-06-01  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf/mips.h: Likewise.
	* elf/sh.h: Likewise.
	* opcode/d10v.h: Likewise.
	* opcode/d30v.h: Likewise.
	* opcode/ia64.h: Likewise.
	* opcode/mips.h: Likewise.
	* opcode/ppc.h: Likewise.
	* opcode/sparc.h: Likewise.
	* opcode/tic6x.h: Likewise.
	* opcode/v850.h: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Revert PR16467 change
@ 2016-06-02  3:32 sergiodj+buildbot
  2016-06-02 13:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02  3:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b677558bc6c7b2477bb33c709e6017e68e7ae8c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 5b677558bc6c7b2477bb33c709e6017e68e7ae8c

Revert PR16467 change

This reverts the pr16467 change, which was incorrect due to faulty
analysis of the pr16467 testcase.  The failure was not due to a
mismatch in symbol type (ifunc/non-ifunc) but due to a symbol loop
being set up.

See https://sourceware.org/ml/binutils/2016-06/msg00013.html for some
rambling on versioned symbols and ELF shared library symbol overriding
that explain this patch.

bfd/
	PR ld/20159
	PR ld/16467
	* elflink.c (_bfd_elf_merge_symbol): Revert PR16467 change.
	(_bfd_elf_add_default_symbol): Don't indirect to/from defined
	symbol given a version by a script different to the version
	of the symbol being added.
	(elf_link_add_object_symbols): Use _bfd_elf_strtab_save and
	_bfd_elf_strtab_restore.  Don't fudge dynstr references.
	* elf-strtab.c (_bfd_elf_strtab_restore_size): Delete.
	(struct strtab_save): New.
	(_bfd_elf_strtab_save, _bfd_elf_strtab_restore): New functions.
	* elf-bfd.h (_bfd_elf_strtab_restore_size): Delete.
	(_bfd_elf_strtab_save, _bfd_elf_strtab_restore): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for 48 and 64 bit ARC instructions.
@ 2016-06-02 13:17 sergiodj+buildbot
  2016-06-02 14:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4eb6f892502bad1ec4e1828d0140959bb004a3b6 ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 4eb6f892502bad1ec4e1828d0140959bb004a3b6

Add support for 48 and 64 bit ARC instructions.

gas	* config/tc-arc.c (parse_opcode_flags): New function.
	(find_opcode_match): Move flag parsing code out to new function.
	Ignore operands marked IGNORE.
	(build_fake_opcode_hash_entry): New function.
	(find_special_case_long_opcode): New function.
	(find_special_case): Lookup long opcodes.
	* testsuite/gas/arc/nps400-7.d: New file.
	* testsuite/gas/arc/nps400-7.s: New file.

include	* opcode/arc.h (MAX_INSN_ARGS): Increase to 16.
	(struct arc_long_opcode): New structure.
	(arc_long_opcodes): Declare.
	(arc_num_long_opcodes): Declare.

opcodes	* arc-dis.c (struct arc_operand_iterator): New structure.
	(find_format_from_table): All the old content from find_format,
	with some minor adjustments, and parameter renaming.
	(find_format_long_instructions): New function.
	(find_format): Rewritten.
	(arc_insn_length): Add LSB parameter.
	(extract_operand_value): New function.
	(operand_iterator_next): New function.
	(print_insn_arc): Use new functions to find opcode, and iterator
	over operands.
	* arc-opc.c (insert_nps_3bit_dst_short): New function.
	(extract_nps_3bit_dst_short): New function.
	(insert_nps_3bit_src2_short): New function.
	(extract_nps_3bit_src2_short): New function.
	(insert_nps_bitop1_size): New function.
	(extract_nps_bitop1_size): New function.
	(insert_nps_bitop2_size): New function.
	(extract_nps_bitop2_size): New function.
	(insert_nps_bitop_mod4_msb): New function.
	(extract_nps_bitop_mod4_msb): New function.
	(insert_nps_bitop_mod4_lsb): New function.
	(extract_nps_bitop_mod4_lsb): New function.
	(insert_nps_bitop_dst_pos3_pos4): New function.
	(extract_nps_bitop_dst_pos3_pos4): New function.
	(insert_nps_bitop_ins_ext): New function.
	(extract_nps_bitop_ins_ext): New function.
	(arc_operands): Add new operands.
	(arc_long_opcodes): New global array.
	(arc_num_long_opcodes): New global.
	* arc-nps400-tbl.h: Add comments referencing arc_long_opcodes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Replace data32 with data16 in comments
@ 2016-06-02 14:30 sergiodj+buildbot
  2016-06-02 15:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 14:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ddf1bdd423a127564d5d13cabde8863431576a3 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 3ddf1bdd423a127564d5d13cabde8863431576a3

Replace data32 with data16 in comments

The 0x66 prefix is data16, not data32 in 64-bit.

	* elf64-x86-64.c: Replace data32 with data16 in comments.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow ARC Linux targets that do not use uclibc.
@ 2016-06-02 15:31 sergiodj+buildbot
  2016-06-02 16:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 15:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ad0bb5f3a5b2d03079819cf419b174a762c2d52 ***

Author: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Branch: master
Commit: 4ad0bb5f3a5b2d03079819cf419b174a762c2d52

Allow ARC Linux targets that do not use uclibc.

bfd    * config.bfd: Replace -uclibc with *.

gas    * configure.tgt: Replace -uclibc with *.

ld     * configure.tgt: Replace -uclibc with *.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] mi-memory-changed.exp: Fix filename passed to untested
@ 2016-06-02 15:40 sergiodj+buildbot
  2016-06-02 17:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 15:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 193bd37899bc7e301b195929bc7e335bea03d4e4 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 193bd37899bc7e301b195929bc7e335bea03d4e4

mi-memory-changed.exp: Fix filename passed to untested

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-memory-changed.exp: Fix filename passed to untested.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add "arm_any" architecture type to allow -m option to various binutils to match any ARM architecture.
@ 2016-06-02 16:28 sergiodj+buildbot
  2016-06-02 18:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99914dfd71d74bc700bb6d15647895ac0c8cc8e1 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 99914dfd71d74bc700bb6d15647895ac0c8cc8e1

Add "arm_any" architecture type to allow -m option to various binutils to match any ARM architecture.

	PR target/20088
	* cpu-arm.c (processors): Add "arm_any" type to match any ARM
	architecture.
	(arch_info_struct): Likewise.
	(architectures): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR python/18984
@ 2016-06-02 19:39 sergiodj+buildbot
  2016-06-03 11:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-02 19:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b40ec0559f4b24ccdf6b073610c526c4aa33c4d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1b40ec0559f4b24ccdf6b073610c526c4aa33c4d

Fix PR python/18984

This fixes PR python/18984.

The bug is that gdbpy_solib_name uses GDB_PY_LL_ARG, whereas it should
use GDB_PY_LLU_ARG to avoid overflow.

Built and tested on x86-64 Fedora 23.

2016-06-02  Tom Tromey  <tom@tromey.com>

	PR python/18984:
	* python/python.c (gdbpy_solib_name): Use GDB_PY_LLU_ARG.

2016-06-02  Tom Tromey  <tom@tromey.com>

	PR python/18984:
	* gdb.python/py-shared.exp: Add solib_name test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix C++ build for Cygwin
@ 2016-06-03 11:47 sergiodj+buildbot
  2016-06-03 12:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 11:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae534d2cfef358bcde3166ce3a29faf85bc632a ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 0ae534d2cfef358bcde3166ce3a29faf85bc632a

Fix C++ build for Cygwin

gdb/ChangeLog:

2016-06-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (handle_output_debug_string): Return type of
	gdb_signal_from_host() is gdb_signal, not an int.
	(windows_get_exec_module_filename): Add pointer casts for C++.

gdb/gdbserver/ChangeLog:

2016-06-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* win32-low.c (win32_create_inferior): Add pointer casts for C++.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Re-add support for lbarx, lharx, stbcx. and sthcx. insns back to the E6500 cpu.
@ 2016-06-03 23:50 sergiodj+buildbot
  2016-06-04  1:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 23:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 026122a670440bc51266f8e013e5c5877c19b54e ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 026122a670440bc51266f8e013e5c5877c19b54e

Re-add support for lbarx, lharx, stbcx. and sthcx. insns back to the E6500 cpu.

opcodes/
	PR binutils/20196
	* ppc-opc.c (powerpc_opcodes <lbarx, lharx, stbcx., sthcx.>): Enable
	opcodes for E6500.

gas/
	PR binutils/20196
	* gas/testsuite/gas/ppc/e6500.s <lbarx, lharx, lwarx, ldarx,
	stbcx., sthcx., stwcx., stdcx.>: Add tests.
	* gas/testsuite/gas/ppc/e6500.d: Likewise.
	* gas/testsuite/gas/ppc/power8.s: Likewise.
	* gas/testsuite/gas/ppc/power8.d: Likewise.
	* gas/testsuite/gas/ppc/power4.s <lwarx, ldarx, stwcx.,
	stdcx.>: Add tests.
	* gas/testsuite/gas/ppc/power4.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add z8k ld testsuite and fix range check in coff-z8k.c
@ 2016-06-04 20:35 sergiodj+buildbot
  2016-06-04 21:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-04 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac27cd3c16ad828f96991f8f7b83a4bc10cae6c ***

Author: Christian Groessler <chris@groessler.org>
Branch: master
Commit: 2ac27cd3c16ad828f96991f8f7b83a4bc10cae6c

Add z8k ld testsuite and fix range check in coff-z8k.c

bfd/
	* coff-z8k.c (extra_case): Fix range check for R_JR relocation.

ld/
	* ld/testsuite/ld-z8k/0filler.s: New file.
	* ld/testsuite/ld-z8k/branch-target.s: New file.
	* ld/testsuite/ld-z8k/branch-target2.s: New file.
	* ld/testsuite/ld-z8k/calr-back-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-back-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/calr-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/calr-opcode.s: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/dbjnz-opcode.s: New file.
	* ld/testsuite/ld-z8k/djnz-back-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-back-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/djnz-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/djnz-opcode.s: New file.
	* ld/testsuite/ld-z8k/filler.s: New file.
	* ld/testsuite/ld-z8k/jr-back-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-back-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/jr-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/jr-opcode.s: New file.
	* ld/testsuite/ld-z8k/ldr-back-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-back-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-back-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-back-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/ldr-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/ldr-opcode.s: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-8001.d: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-8002.d: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-fail-8001.d: New file.
	* ld/testsuite/ld-z8k/ldrb-forw-fail-8002.d: New file.
	* ld/testsuite/ld-z8k/ldrb-opcode.s: New file.
	* ld/testsuite/ld-z8k/ldrb-opcode2.s: New file.
	* ld/testsuite/ld-z8k/other-file.s: New file.
	* ld/testsuite/ld-z8k/reloc.dd: New file.
	* ld/testsuite/ld-z8k/reloc.ld: New file.
	* ld/testsuite/ld-z8k/relocseg.dd: New file.
	* ld/testsuite/ld-z8k/relocseg.ld: New file.
	* ld/testsuite/ld-z8k/relocseg1.dd: New file.
	* ld/testsuite/ld-z8k/test-ld.sh: New file.
	* ld/testsuite/ld-z8k/this-file.s: New file.
	* ld/testsuite/ld-z8k/z8k.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support x86-64 TLS code sequences without PLT
@ 2016-06-06 18:25 sergiodj+buildbot
  2016-06-06 18:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-06 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2cbcd9156d1606a9f2153aecd93a89fe6e29180 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: e2cbcd9156d1606a9f2153aecd93a89fe6e29180

Support x86-64 TLS code sequences without PLT

We can generate x86-64 TLS code sequences for general and local dynamic
models without PLT, which uses indirect call via GOT:

call *__tls_get_addr@GOTPCREL(%rip)

instead of direct call:

call __tls_get_addr[@PLT]

Since direct call is 4-byte long and indirect call, is 5-byte long, the
extra one byte must be handled properly.

For general dynamic model, one 0x66 prefix before call instruction is
removed to make room for indirect call.  For local dynamic model, we
simply use 5-byte indirect call.

TLS linker optimization is updated to recognize new instruction patterns.
For local dynamic model to local exec model transition, we generate
4 0x66 prefixes, instead of 3, before mov instruction in 64-bit and
generate a 5-byte nop, instead of 4-byte, before mov instruction in
32-bit.  Since linker may convert

call *__tls_get_addr@GOTPCREL(%rip)

to

addr32 call __tls_get_addr

when producing static executable, both patterns are recognized.

bfd/

	* elf64-x86-64.c (elf_x86_64_link_hash_entry): Add tls_get_addr.
	(elf_x86_64_link_hash_newfunc): Initialize tls_get_addr to 2.
	(elf_x86_64_check_tls_transition): Check indirect call and
	direct call with the addr32 prefix for general and local dynamic
	models.  Set the tls_get_addr feild.
	(elf_x86_64_convert_load_reloc): Always use addr32 prefix for
	indirect __tls_get_addr call via GOT.
	(elf_x86_64_relocate_section): Handle GD->LE, GD->IE and LD->LE
	transitions with indirect call and direct call with the addr32
	prefix.

ld/

	* testsuite/ld-x86-64/pass.out: New file.
	* testsuite/ld-x86-64/tls-def1.c: Likewise.
	* testsuite/ld-x86-64/tls-gd1.S: Likewise.
	* testsuite/ld-x86-64/tls-ld1.S: Likewise.
	* testsuite/ld-x86-64/tls-main1.c: Likewise.
	* testsuite/ld-x86-64/tls.exp: Likewise.
	* testsuite/ld-x86-64/tlsbin2-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.dd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.rd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.sd: Likewise.
	* testsuite/ld-x86-64/tlsbin2.td: Likewise.
	* testsuite/ld-x86-64/tlsbinpic2.s: Likewise.
	* testsuite/ld-x86-64/tlsgd10.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd10.s: Likewise.
	* testsuite/ld-x86-64/tlsgd11.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd11.s: Likewise.
	* testsuite/ld-x86-64/tlsgd12.d: Likewise.
	* testsuite/ld-x86-64/tlsgd12.s: Likewise.
	* testsuite/ld-x86-64/tlsgd13.d: Likewise.
	* testsuite/ld-x86-64/tlsgd13.s: Likewise.
	* testsuite/ld-x86-64/tlsgd14.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd14.s: Likewise.
	* testsuite/ld-x86-64/tlsgd5c.s: Likewise.
	* testsuite/ld-x86-64/tlsgd6c.s: Likewise.
	* testsuite/ld-x86-64/tlsgd9.dd: Likewise.
	* testsuite/ld-x86-64/tlsgd9.s: Likewise.
	* testsuite/ld-x86-64/tlsld4.dd: Likewise.
	* testsuite/ld-x86-64/tlsld4.s: Likewise.
	* testsuite/ld-x86-64/tlsld5.dd: Likewise.
	* testsuite/ld-x86-64/tlsld5.s: Likewise.
	* testsuite/ld-x86-64/tlsld6.dd: Likewise.
	* testsuite/ld-x86-64/tlsld6.s: Likewise.
	* testsuite/ld-x86-64/tlspic2-nacl.rd: Likewise.
	* testsuite/ld-x86-64/tlspic2.dd: Likewise.
	* testsuite/ld-x86-64/tlspic2.rd: Likewise.
	* testsuite/ld-x86-64/tlspic2.sd: Likewise.
	* testsuite/ld-x86-64/tlspic2.td: Likewise.
	* testsuite/ld-x86-64/tlspic3.s: Likewise.
	* testsuite/ld-x86-64/tlspie2.s: Likewise.
	* testsuite/ld-x86-64/tlspie2a.d: Likewise.
	* testsuite/ld-x86-64/tlspie2b.d: Likewise.
	* testsuite/ld-x86-64/tlspie2c.d: Likewise.
	* testsuite/ld-x86-64/tlsgd5.dd: Updated.
	* testsuite/ld-x86-64/tlsgd6.dd: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run libtlspic2.so, tlsbin2,
	tlsgd5b, tlsgd6b, tlsld4, tlsld5, tlsld6, tlsgd9, tlsgd10,
	tlsgd11, tlsgd14, tlsgd12, tlsgd13, tlspie2a, tlspie2b and
	tlspie2c.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add method/format information to =record-started
@ 2016-06-06 21:21 sergiodj+buildbot
  2016-06-06 21:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-06 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38b022b4452f996fb5a8598f80d850b594621bcf ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 38b022b4452f996fb5a8598f80d850b594621bcf

Add method/format information to =record-started

Eclipse CDT now supports enabling execution recording using two methods
(full and btrace) and both formats for btrace (bts and pt).  In the
event that recording is enabled behind the back of the GUI (by the user
on the command line, or a script), we need to know which method/format
are being used, so it can be correctly reflected in the interface.  This
patch adds this information to the =record-started async record.

Before:

  =record-started,thread-group="i1"

After:

  =record-started,thread-group="i1",method="btrace",format="bts"
  =record-started,thread-group="i1",method="btrace",format="pt"
  =record-started,thread-group="i1",method="full"

The "format" field is only present when the current method supports
multiple formats (only the btrace method as of now).

gdb/ChangeLog:

	* NEWS: Mention the new fields in =record-started.
	* common/btrace-common.h (btrace_format_short_string): New function
	declaration.
	* common/btrace-common.c (btrace_format_short_string): New
	function.
	* mi/mi-interp.c (mi_record_changed): Output method and format
	fields in the =record-started record.
	* record-btrace.c (record_btrace_open): Adapt record_changed
	notification.
	* record-full.c (record_full_open): Likewise.
	* record.c (cmd_record_stop): Likewise.

gdb/doc/ChangeLog:

	* gdb.texinfo (GDB/MI Async Records): Document method and
	format fields in =record-started.
	* observer.texi (record_changed): Add method and format
	parameters.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-record-changed.exp: Adjust =record-started output
	matching.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] Add command line option for RAS extension.
@ 2016-06-07  9:09 sergiodj+buildbot
  2016-06-07  9:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-07  9:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d1464f294405a064d84e3d4f15c1ceff3639add ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 4d1464f294405a064d84e3d4f15c1ceff3639add

[ARM] Add command line option for RAS extension.

This patch adds the architecture extension "+ras" to enable RAS
support. It is enabled by default for -march=armv8.2-a and available but
disabled by default for armv8-a and armv8.1-a.

gas/
	* config/tc-arm.c (arm_ext_v8_2): Rename to arm_ext_ras.
	(arm_ext_ras): Renamed from arm_ext_v8_2.
	(insns): Update for arm_ext_v8_2 renaming.
	(arm_extensions): Add "ras".
	* doc/c-arm.texi (ARM Options): Add an entry for "ras".
	* testsuite/gas/arm/armv8-a+ras.d: New.
	* testsuite/gas/arm/armv8_2-a.d: Add explicit command line
	options.

include/
	* opcode/arm.h (ARM_EXT2_RAS): New.  Also align preceding
	entries.
	(ARM_AEXT_V8_2A): Add ARM_EXT2_RAS.

opcodes/
	* arm-dis.c (arm_opcodes): Replace ARM_EXT_V8_2A with
	ARM_EXT_RAS in relevant entries.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Frame static link: Handle null pointer.
@ 2016-06-07 11:49 sergiodj+buildbot
  2016-06-07 12:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 11:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2091da296fd563f62d856dcb5a049a63484ed65e ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 2091da296fd563f62d856dcb5a049a63484ed65e

Frame static link: Handle null pointer.

2016-06-07  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* findvar.c (follow_static_link): Check for valid pointer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PLT first entry GOT operand calculation.
@ 2016-06-07 15:04 sergiodj+buildbot
  2016-06-07 15:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 161db2790500827b74ef835ebe515dce04021316 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 161db2790500827b74ef835ebe515dce04021316

Fix PLT first entry GOT operand calculation.

Embedding the .plt section in another revealed a bug in the way the
larl operand of the first magic plt entry is being calculated.  Fixed
with the attached patch.

bfd/ChangeLog:

	* elf64-s390.c (elf_s390_finish_dynamic_sections): Subtract plt
	section offset when calculation the larl operand in the first PLT
	entry.

ld/ChangeLog:

	* testsuite/ld-s390/pltoffset-1.dd: New test.
	* testsuite/ld-s390/pltoffset-1.ld: New test.
	* testsuite/ld-s390/pltoffset-1.s: New test.
	* testsuite/ld-s390/s390.exp: Run new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd/s390: Misc minor fixes.
@ 2016-06-07 16:28 sergiodj+buildbot
  2016-06-07 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b67f09464f771466473e64d44aa258f832d8b2d ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 3b67f09464f771466473e64d44aa258f832d8b2d

bfd/s390: Misc minor fixes.

The only non-comment fix here is in the code writing out the 3 fixed
.got.plt entries - it mistakenly put a 64-bit 0 at offsets 8 and 12
instead of 8 and 16.

bfd/ChangeLog:

	* elf32-s390.c (elf_s390_finish_dynamic_symbol): Fix comment.
	* elf64-s390.c (elf_s390x_plt_entry): Fix comment.
	(elf_s390_relocate_section): Fix comment.
	(elf_s390_finish_dynamic_sections): Fix initialization of fixed
	.got.plt entries.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support i386 TLS code sequences without PLT
@ 2016-06-08 19:36 sergiodj+buildbot
  2016-06-08 19:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-08 19:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6eaa7fb59b32beaca017abf139a67bbe87592d9b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6eaa7fb59b32beaca017abf139a67bbe87592d9b

Support i386 TLS code sequences without PLT

We can generate i386 TLS code sequences for general and local dynamic
models without PLT, which uses indirect call via GOT:

call *___tls_get_addr@GOT(%reg)

where EBX register isn't required as GOT base, instead of direct call:

call ___tls_get_addr[@PLT]

which requires EBX register as GOT base.

Since direct call is 4-byte long and indirect call, is 5-byte long, the
extra one byte must be handled properly.

For general dynamic model, 7-byte lea instruction before call instruction
is replaced by 6-byte one to make room for indirect call.  For local
dynamic model, we simply use 5-byte indirect call.

TLS linker optimization is updated to recognize new instruction patterns.
For local dynamic model to local exec model transition, we generate
a 6-byte lea instruction as nop, instead of a 1-byte nop plus a 4-byte
lea instruction.  Since linker may convert

call ___tls_get_addr[@PLT]

to

addr32 call ____tls_get_addr

when producing static executable, both patterns are recognized.

bfd/

	* elf64-i386.c (elf_i386_link_hash_entry): Add tls_get_addr.
	(elf_i386_link_hash_newfunc): Initialize tls_get_addr to 2.
	(elf_i386_check_tls_transition): Check indirect call and direct
	call with the addr32 prefix for general and local dynamic models.
	Set the tls_get_addr feild.
	(elf_i386_convert_load_reloc): Always use addr32 prefix for
	indirect ___tls_get_addr call via GOT.
	(elf_i386_relocate_section): Handle GD->LE, GD->IE and LD->LE
	transitions with indirect call and direct call with the addr32
	prefix.

ld/

	* testsuite/ld-i386/i386.exp: Run libtlspic2.so, tlsbin2,
	tlsgd3, tlsld2, tlsgd4, tlspie3a, tlspie3b and tlspie3c.
	* testsuite/ld-i386/pass.out: New file.
	* testsuite/ld-i386/tls-def1.c: Likewise.
	* testsuite/ld-i386/tls-gd1.S: Likewise.
	* testsuite/ld-i386/tls-ld1.S: Likewise.
	* testsuite/ld-i386/tls-main1.c: Likewise.
	* testsuite/ld-i386/tls.exp: Likewise.
	* testsuite/ld-i386/tlsbin2-nacl.rd: Likewise.
	* testsuite/ld-i386/tlsbin2.dd: Likewise.
	* testsuite/ld-i386/tlsbin2.rd: Likewise.
	* testsuite/ld-i386/tlsbin2.sd: Likewise.
	* testsuite/ld-i386/tlsbin2.td: Likewise.
	* testsuite/ld-i386/tlsbinpic2.s: Likewise.
	* testsuite/ld-i386/tlsgd3.dd: Likewise.
	* testsuite/ld-i386/tlsgd3.s: Likewise.
	* testsuite/ld-i386/tlsgd4.d: Likewise.
	* testsuite/ld-i386/tlsgd4.s: Likewise.
	* testsuite/ld-i386/tlsld2.s: Likewise.
	* testsuite/ld-i386/tlspic2-nacl.rd: Likewise.
	* testsuite/ld-i386/tlspic2.dd: Likewise.
	* testsuite/ld-i386/tlspic2.rd: Likewise.
	* testsuite/ld-i386/tlspic2.sd: Likewise.
	* testsuite/ld-i386/tlspic2.td: Likewise.
	* testsuite/ld-i386/tlspic3.s: Likewise.
	* testsuite/ld-i386/tlspie3.s: Likewise.
	* testsuite/ld-i386/tlspie3a.d: Likewise.
	* testsuite/ld-i386/tlspie3b.d: Likewise.
	* testsuite/ld-i386/tlspie3c.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Print symbol names in comments for LDS/STS disassembly.
@ 2016-06-09 16:17 sergiodj+buildbot
  2016-06-09 16:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-09 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1857fe72aff6f254217956d141bff4b9ca454bc5 ***

Author: Denis Chertykov <chertykov@gmail.com>
Branch: master
Commit: 1857fe72aff6f254217956d141bff4b9ca454bc5

Print symbol names in comments for LDS/STS disassembly.

This patch adds default data address space origin (0x800000) to the symbol addresses.
when disassemble lds/sts instructions. So that symbol names shall be printed in comments
for lds/sts instructions disassemble.

ld/
	* testsuite/ld-avr/lds-mega.d: New test.
	* testsuite/ld-avr/lds-mega.s: New test source.
	* testsuite/ld-avr/lds-tiny.d: New test.
	* testsuite/ld-avr/lds-tiny.s: New test source.

opcodes/
	* avr-dis.c (avr_operand): Add default data address space origin (0x800000) to the
	address and set as symbol address for LDS/ STS immediate operands.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add myself as a write-after-approval GDB maintainer
@ 2016-06-10  5:39 sergiodj+buildbot
  2016-06-10  5:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-10  5:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c040f3fb55315f06ceb9e6de6ac167a95a445ace ***

Author: Toshihito Kikuchi <k.toshihito@yahoo.de>
Branch: master
Commit: c040f3fb55315f06ceb9e6de6ac167a95a445ace

Add myself as a write-after-approval GDB maintainer

gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add Toshihito Kikuchi.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add negative repeat count to 'x' command
@ 2016-06-10  6:19 sergiodj+buildbot
  2016-06-10  6:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-10  6:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb556f1facb86cdd1591d490f2d2d670bdd5a1ee ***

Author: Toshihito Kikuchi <k.toshihito@yahoo.de>
Branch: master
Commit: bb556f1facb86cdd1591d490f2d2d670bdd5a1ee

Add negative repeat count to 'x' command

This change adds support for specifying a negative repeat count to
all the formats of the 'x' command to examine memory backward.
A new testcase 'examine-backward' is added to cover this new feature.

Here's the example output from the new feature:

<format 'i'>
(gdb) bt
#0  Func1 (n=42, p=0x40432e "hogehoge") at main.cpp:5
#1  0x00000000004041fa in main (argc=1, argv=0x7fffffffdff8) at main.cpp:19
(gdb) x/-4i 0x4041fa
  0x4041e5 <main(int, char**)+11>: mov   %rsi,-0x10(%rbp)
  0x4041e9 <main(int, char**)+15>: lea   0x13e(%rip),%rsi
  0x4041f0 <main(int, char**)+22>: mov   $0x2a,%edi
  0x4041f5 <main(int, char**)+27>: callq 0x404147

<format 'x'>
(gdb) x/-4xw 0x404200
0x4041f0 <main(int, char**)+22>: 0x00002abf 0xff4de800 0x76e8ffff 0xb8ffffff
(gdb) x/-4
0x4041e0 <main(int, char**)+6>:  0x7d8910ec 0x758948fc 0x358d48f0 0x0000013e

gdb/ChangeLog:

	* NEWS: Mention that GDB now supports a negative repeat count in
	the 'x' command.
	* printcmd.c (decode_format): Allow '-' in the parameter
	"string_ptr" to accept a negative repeat count.
	(find_instruction_backward): New function.
	(read_memory_backward): New function.
	(integer_is_zero): New function.
	(find_string_backward): New function.
	(do_examine): Use new functions to examine memory backward.
	(_initialize_printcmd): Mention that 'x' command supports a negative
	repeat count.

gdb/doc/ChangeLog:

	* gdb.texinfo (Examining Memory): Document negative repeat
	count in the 'x' command.

gdb/testsuite/ChangeLog:

	* gdb.base/examine-backward.c: New file.
	* gdb.base/examine-backward.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fortran: Testsuite, non-local references in nested functions.
@ 2016-06-10  9:37 sergiodj+buildbot
  2016-06-10  9:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-10  9:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e13cf25436bf72d851d81f132fcd49b0c636607 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 5e13cf25436bf72d851d81f132fcd49b0c636607

Fortran: Testsuite, non-local references in nested functions.

Non-local references in nested functions are usually implemented
by using DWARF static link. This feature was added
with commit 63e43d3aedb8b1112899c2d0ad74cbbee687e5d6
(DWARF: handle non-local references in nested functions) but
a testcase was missing in Fortran.

2016-06-10  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Testsuite/Changelog:
	* gdb.fortran/nested-funcs.exp: New.
	* gdb.fortran/nested-funcs.f90:	New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix rust-exp handling in makefile
@ 2016-06-10 16:12 sergiodj+buildbot
  2016-06-10 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-10 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edef7b8cf3d811ce8630591dbed1257ba16164ff ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: edef7b8cf3d811ce8630591dbed1257ba16164ff

Fix rust-exp handling in makefile

I noticed that the rust-exp handling in the Makefile differed from
that of other .y files.  I believe I noticed this by seeing a stray
"rm" in the build log.

This patch changes the Makefile to bring the rust-exp handling in line
with that of other .y files.

2016-06-10  Tom Tromey  <tom@tromey.com>

	* Makefile.in (COMMON_OBS): Remove rust-exp.o.
	(YYFILES): Add rust-exp.c.
	(YYOBJ): Add rust-exp.o.
	(local-maintainer-clean): Remove rust-exp.c.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR rust/20110
@ 2016-06-10 16:15 sergiodj+buildbot
  2016-06-10 17:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-10 16:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 347dc1025db1c0acf616ab6520c3f36448f25e8b ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 347dc1025db1c0acf616ab6520c3f36448f25e8b

Fix PR rust/20110

PR rust/20110 concerns the type of an integer constant that is too
large for "i32", the default integer type.  This patch changes the
type of such a constant to i64.  This is important because such values
are often addresses, so truncating them by default is unfriendly.

Built and regtested on x86-64 Fedora 23.

2016-06-10  Tom Tromey  <tom@tromey.com>

	PR rust/20110:
	* rust-exp.y (lex_number): Don't truncate large numbers to i32.

2016-06-10  Tom Tromey  <tom@tromey.com>

	PR rust/20110:
	* gdb.rust/expr.exp: Add test for integer constant larger than
	i32.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Constify arch_type and friends
@ 2016-06-10 16:24 sergiodj+buildbot
  2016-06-10 18:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-10 16:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 695bfa52ccf22058e371828c3636a3d74424ec5b ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 695bfa52ccf22058e371828c3636a3d74424ec5b

Constify arch_type and friends

While working on the Rust support, I happened to notice that arch_type
and related functions take "char *" arguments, where "const char *"
would be more correct.  This patch fixes this oversight.  Tested by
rebuilding.

2016-06-10  Tom Tromey  <tom@tromey.com>

	* gdbtypes.c (arch_type, arch_integer_type, arch_character_type)
	(arch_boolean_type, arch_float_type, arch_complex_type)
	(arch_flags_type, append_flags_type_field)
	(append_flags_type_flag, arch_composite_type)
	(append_composite_type_field_raw)
	(append_composite_type_field_aligned)
	(append_composite_type_field): Make "name" parameter const.
	* gdbtypes.h (arch_type, arch_integer_type, arch_character_type)
	(arch_boolean_type, arch_float_type, arch_complex_type)
	(append_composite_type_field, append_composite_type_field_aligned)
	(append_composite_type_field_raw, arch_flags_type)
	(append_flags_type_field, append_flags_type_flag): Constify.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use size_t rather than bfd_size_type
@ 2016-06-11  8:19 sergiodj+buildbot
  2016-06-11  8:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-11  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef53be89160126f2fa5dec8f1ec3bd6d99fb0681 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ef53be89160126f2fa5dec8f1ec3bd6d99fb0681

Use size_t rather than bfd_size_type

I noticed when writing _bfd_elf_strtab_save/restore that size_t would
be better than bfd_size_type for a number of things in elf-strtab.c.
Using a 64-bit bfd_size_type on a 32-bit host doesn't make much sense
for array sizes and indices.

	* elf-strtab.c (struct strtab_save): Use size_t for "size".
	(struct elf_strtab_hash): Likewise for "size" and "alloced".
	(_bfd_elf_strtab_init): Formatting.
	(_bfd_elf_strtab_add): Return size_t rather than bfd_size_type.
	(_bfd_elf_strtab_addref): Take size_t idx param.
	(_bfd_elf_strtab_delref, _bfd_elf_strtab_refcount): Likewise.
	(_bfd_elf_strtab_offset): Likewise.
	(_bfd_elf_strtab_clear_all_refs): Use size_t idx.
	(_bfd_elf_strtab_save): Use size_t "idx" and "size" vars.
	(_bfd_elf_strtab_restore, _bfd_elf_strtab_emit): Similarly.
	(_bfd_elf_strtab_finalize): Similarly.
	* elf-bfd.h (_bfd_elf_strtab_add): Update prototypes.
	(_bfd_elf_strtab_addref, _bfd_elf_strtab_delref): Likewise.
	(_bfd_elf_strtab_refcount, _bfd_elf_strtab_offset): Likewise.
	* elf.c (bfd_elf_get_elf_syms): Calculate symbol buffer size
	using bfd_size_type.
	(bfd_section_from_shdr): Delete amt.
	(_bfd_elf_init_reloc_shdr): Likewise.
	(_bfd_elf_link_assign_sym_version): Likewise.
	(assign_section_numbers): Use size_t reloc_count.
	* elflink.c (struct elf_symbuf_head): Use size_t "count".
	(bfd_elf_link_record_dynamic_symbol): Use size_t for some vars.
	(elf_link_is_defined_archive_symbol): Likewise.
	(elf_add_dt_needed_tag): Likewise.
	(elf_finalize_dynstr): Likewise.
	(elf_link_add_object_symbols): Likewise.
	(bfd_elf_size_dynamic_sections): Likewise.
	(elf_create_symbuf): Similarly.
	(bfd_elf_match_symbols_in_sections): Likewise.
	(elf_link_swap_symbols_out): Likewise.
	(elf_link_check_versioned_symbol): Likewise.
	(bfd_elf_gc_record_vtinherit): Likewise.
	(bfd_elf_gc_common_finalize_got_offsets): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sparc-coff writing uninitialized memory
@ 2016-06-11  9:15 sergiodj+buildbot
  2016-06-11  9:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-11  9:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0eaf2e1b589472d635e85d2ce708faa35a23a90a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0eaf2e1b589472d635e85d2ce708faa35a23a90a

sparc-coff writing uninitialized memory

sparc-coff has a 20 byte symbol entry with an extra field, but neglects
to initialize the field.  Fix that.

	* coff/sparc.h (COFF_ADJUST_SYM_OUT_POST): Define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Subtract GOT base only with a base register
@ 2016-06-12  4:48 sergiodj+buildbot
  2016-06-12  4:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-12  4:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74d7f0aa5b1e27da215349fb32337e1d83aca7d7 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 74d7f0aa5b1e27da215349fb32337e1d83aca7d7

Subtract GOT base only with a base register

When relocating R_386_GOT32 in "op $0, bar@GOT", we shouldn't subtract
GOT base without a base register and we should disallow it without a
base register for PIC.

bfd/

	PR ld/20244
	* elf32-i386.c (elf_i386_relocate_section): When relocating
	R_386_GOT32, return error without a base register for PIC and
	subtract the .got.plt section address only with a base register.

ld/

	PR ld/20244
	* testsuite/ld-i386/i386.exp: Run pr20244-1a and pr20244-1b.
	* testsuite/ld-i386/pr20244-1.s: New file.
	* testsuite/ld-i386/pr20244-1a.d: Likewise.
	* testsuite/ld-i386/pr20244-1b.d: Likewise.
	* testsuite/ld-i386/pr20244-1c.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Generate DT_RELACOUNT.
@ 2016-06-13 14:52 sergiodj+buildbot
  2016-06-13 14:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f7f3789ca97ecaf0c4169c6d82e205f69fa0580 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 0f7f3789ca97ecaf0c4169c6d82e205f69fa0580

[ARC] Generate DT_RELACOUNT.

bfd/
2016-06-13  Cupertino Miranda  <cmiranda@synospsy.com>

	* elf32-arc.c (elf32_arc_reloc_type_class): Defined function to
	enable support for "-z combreloc" and DT_RELACOUNT.
	(elf_backend_reloc_type_class): Likewise


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] General bug fixes
@ 2016-06-13 15:47 sergiodj+buildbot
  2016-06-13 16:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 15:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ab2f40d58e6ad530667b018e42dd71519556f1b ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 2ab2f40d58e6ad530667b018e42dd71519556f1b

[ARC] General bug fixes

Fail safe for trying to reloc GOT and PLT on non dynamic linker.  Fix
issue with dynamic relocs not being generated with -pie.  Removed some
structures that were not being used.  Fixed typo changing RELENT to
RELAENT.  Fix for all SECTOFF relocations.

bfd/
2016-06-13  Cupertino Miranda  <cmiranda@synospsy.com>

	* elf32-arc.c (arc_local_data, arc_local_data): Removed.
	(SECTSTART): Changed.
	(elf_arc_relocate_section): Fixed mistake in PIE related
	condition.
	(elf_arc_size_dynamic_sections): Changed DT_RELENT to DT_RELAENT.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Use UNSUPPORTED not XFAIL for unsupported target features
@ 2016-06-13 16:49 sergiodj+buildbot
  2016-06-13 17:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cad8e26d2a2c7cee04954624fbaf91f03eec50ec ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: cad8e26d2a2c7cee04954624fbaf91f03eec50ec

gdb: Use UNSUPPORTED not XFAIL for unsupported target features

If a target does not support making function calls from GDB then in a
number of test files, we currently report an XFAIL and skip some, or all
of the tests.  This commit changes the XFAIL to an UNSUPPORTED as this
seems more appropriate in these cases.

Some of the tests used bug ID 2416 to be reported in the XFAIL.  In the
current GDB bugzilla bug 2416 has nothing to do with calling target
functions from GDB.

gdb/testsuite/ChangeLog:

	* gdb.base/call-ar-st.exp: Report unsupported rather than xfail
	for unsupported target features.
	* gdb.base/call-rt-st.exp: Likewise.
	* gdb.base/call-sc.exp: Likewise.
	* gdb.base/call-signal-resume.exp: Likewise.
	* gdb.base/call-strs.exp: Likewise.
	* gdb.base/callexit.exp: Likewise.
	* gdb.base/callfuncs.exp: Likewise.
	* gdb.base/nodebug.exp: Likewise.
	* gdb.base/printcmds.exp: Likewise.
	* gdb.base/ptype.exp: Likewise.
	* gdb.base/structs.exp: Likewise.
	* gdb.base/unwindonsignal.exp: Likewise.
	* gdb.cp/gdb2495.exp: Likewise.
	* gdb.cp/templates.exp: Likewise.
	* gdb.cp/virtfunc.exp: Likewise.
	* gdb.threads/hand-call-in-threads.exp: Likewise.
	* gdb.threads/interrupted-hand-call.exp: Likewise.
	* gdb.threads/thread-unwindonsignal.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Fix condition.
@ 2016-06-13 17:17 sergiodj+buildbot
  2016-06-13 18:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 815dc1bcdc1de926bfbb63fb15e0725c9bbc7671 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 815dc1bcdc1de926bfbb63fb15e0725c9bbc7671

[ARC] Fix condition.

bfd/
2016-06-13  Cupertino Miranda  <cmiranda@synospsy.com>

	* elf32-arc.c (elf_arc_relocate_section): Fixed condition.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add 2 i386 tests to call IFUNC functions via GOT
@ 2016-06-13 19:01 sergiodj+buildbot
  2016-06-13 21:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 19:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca8c86efe7765262e25ebb08004012ba2fdadf52 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: ca8c86efe7765262e25ebb08004012ba2fdadf52

Add 2 i386 tests to call IFUNC functions via GOT

bfd/

	* elf32-i386.c (elf_i386_relocate_section): Simplify IFUNC
	GOT32 adjustment for static executables.

ld/

2016-06-13  H.J. Lu  <hongjiu.lu@intel.com>

	* testsuite/ld-i386/i386.exp: Run ifunc-1a and ifunc-1b.
	* testsuite/ld-i386/ifunc-1a.c: New file.
	* testsuite/ld-i386/ifunc-1b.S: Likewise.
	* testsuite/ld-i386/ifunc-1c.S: Likewise.
	* testsuite/ld-i386/ifunc-1d.S: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add the GOT base for GOT32 relocs against IFUNC
@ 2016-06-13 19:23 sergiodj+buildbot
  2016-06-13 22:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 19:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 712ec27916b5604d29d928dec060fd1ba0fd9edb ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 712ec27916b5604d29d928dec060fd1ba0fd9edb

Add the GOT base for GOT32 relocs against IFUNC

Add the GOT base for R_386_GOT32/R_386_GOT32X relocations against IFUNC
symbols if there is no base register and disallow them for PIC.

bfd/

	PR ld/20244
	* elf32-i386.c (elf_i386_relocate_section): Add the .got.plt
	section address for R_386_GOT32/R_386_GOT32X relocations against
	IFUNC symbols if there is no base register and return error for
	PIC.

ld/

	PR ld/20244
	* testsuite/ld-i386/i386.exp: Run pr20244-2a, pr20244-2b,
	pr20244-2c and pr20244-2d.
	* testsuite/ld-i386/no-plt.exp: Run pr20244-3a and pr20244-3b.
	* testsuite/ld-i386/pr20244-2.s: New file.
	* testsuite/ld-i386/pr20244-2a.d: Likewise.
	* testsuite/ld-i386/pr20244-2b.d: Likewise.
	* testsuite/ld-i386/pr20244-2c.d: Likewise.
	* testsuite/ld-i386/pr20244-2d.d: Likewise.
	* testsuite/ld-i386/pr20244-3a.c: Likewise.
	* testsuite/ld-i386/pr20244-3b.S: Likewise.
	* testsuite/ld-i386/pr20244-3c.S: Likewise.
	* testsuite/ld-i386/pr20244-3d.S: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Update outdated comment about o32 R_MIPS_PC32 reloc support
@ 2016-06-13 20:20 sergiodj+buildbot
  2016-06-13 20:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-13 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c9663cbd41c27a8e20ca88a53ba3deae374f1d8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0c9663cbd41c27a8e20ca88a53ba3deae374f1d8

MIPS/BFD: Update outdated comment about o32 R_MIPS_PC32 reloc support

Complement:

commit b47468a6dbd1b54c44c2edc0f7db64a073d894ea
Author: Catherine Moore <clm@redhat.com>
Date:   Mon May 6 15:25:45 2013 +0000

and the return of support for R_MIPS_PC32 there.

	bfd/
	* elf32-mips.c (elf_mips_gnu_pcrel32): Update comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set my_archive for thin archives
@ 2016-06-14  6:01 sergiodj+buildbot
  2016-06-14  5:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14  6:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0cffb47671ffbaac559c1f17a9f248256ea6c42 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: b0cffb47671ffbaac559c1f17a9f248256ea6c42

Set my_archive for thin archives

LTO plugin support in plugin_maybe_claim wants to close the IR bfd
after replacing it with the recompiled object, but can't do so for
archive elements due to various pointers that access the archive bfd.
Thin archives have the same problem.  They too cannot have their
element bfds closed.

	PR ld/20241
bfd/
	* archive.c (open_nested_file): Set my_archive.
	* bfd.c (_bfd_default_error_handler <%B>): Exclude archive file name
	for thin archives.
	* bfdio.c (bfd_tell): Don't adjust origin for thin archives.
	(bfd_seek): Likewise.
	* bfdwin.c (bfd_get_file_window): Likewise.
	* cache.c (cache_bmmap): Likewise.
	(bfd_cache_lookup_worker): Don't look in my_archive for thin archives.
	* mach-o.c (bfd_mach_o_follow_dsym): Don't open my_archive for
	thin archives.
	* plugin.c (try_claim): Likewise.
	* xcofflink.c (xcoff_link_add_dynamic_symbols): Use import path of
	file within thin archive, not the archive.
binutils/
	* bucomm.c (bfd_get_archive_filename): Return file name within thin
	archive.
ld/
	* ldmain.c (add_archive_element): Just print file name of file within
	thin archives.
	* ldmisc.c (vfinfo): Likewise.
	* plugin.c (plugin_object_p): Open file within thin archives.
	(plugin_maybe_claim): Expand comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Delete bfd_my_archive macro
@ 2016-06-14  6:41 sergiodj+buildbot
  2016-06-14  7:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14  6:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3860d2b4b72feeef4cf045c6c9907a0476f46f3d ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3860d2b4b72feeef4cf045c6c9907a0476f46f3d

Delete bfd_my_archive macro

Many more places use abfd->my_archive rather than bfd_my_archive (abfd),
so let's make the code consistently use the first idiom.

bfd/
	* bfd-in.h (bfd_my_archive): Delete.
	* bfd-in2.h: Regenerate.
binutils/
	* ar.c: Expand uses of bfd_my_archive.
	* size.c: Likewise.
ld/
	* ldlang.c: Expand uses of bfd_my_archive.
	* ldmain.c: Likewise.
	* ldmisc.c: Likewise.
	* plugin.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Add arithmetic and logic instructions for nps
@ 2016-06-14 15:50 sergiodj+buildbot
  2016-06-14 15:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14053c1903cc0e4f0130570f61aee2825661cd7d ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 14053c1903cc0e4f0130570f61aee2825661cd7d

[ARC] Add arithmetic and logic instructions for nps

This commit completes the implementation of arithmetic and logic
instructions for the NPS-400. These instructions are:

- calcbsd / calcbxd
- calckey / calcxkey
- mxb / imxb
- addl, subl, orl, andl, xorl
- andab / orab
- lbdsize
- bdlen
- csms, csma, cbba
- zncv
- hofs


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Add deep packet inspection instructions for nps
@ 2016-06-14 16:46 sergiodj+buildbot
  2016-06-14 16:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ba75c884776383174cd894948bd8b3cbca62897 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 9ba75c884776383174cd894948bd8b3cbca62897

[ARC] Add deep packet inspection instructions for nps

With the exception of ldbit, this commit adds implementations of
all DPI instructions for the NPS-400. These instructions are:

- hash / hash.p[0-3]
- tr
- utf8
- e4by
- addf


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Add ldbit for nps
@ 2016-06-14 17:03 sergiodj+buildbot
  2016-06-14 17:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28215275a6bbb7c4b4c2d683a1d94fead7dacc35 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 28215275a6bbb7c4b4c2d683a1d94fead7dacc35

[ARC] Add ldbit for nps

This commit adds the ldbit instruction for the NPS-400. The ldbit
instruction uses the same encoding as the ld instruction, but sets
the ZZ field to 11 (which is a reserved setting), and sets the AA
field to 1 or 2 for the x2 and x4 flags respectively.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix elf_x86_64_reloc_type_class
@ 2016-06-14 17:58 sergiodj+buildbot
  2016-06-14 19:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 897463b12ba936df7d2070755eaac94f87fcedfb ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 897463b12ba936df7d2070755eaac94f87fcedfb

Fix elf_x86_64_reloc_type_class


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Pass a NULL pointer as the last argument to find_pc_partial_function.
@ 2016-06-14 20:17 sergiodj+buildbot
  2016-06-14 23:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 20:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 683cd65eb4787e3e2921076699e0ca9b00762df3 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 683cd65eb4787e3e2921076699e0ca9b00762df3

Pass a NULL pointer as the last argument to find_pc_partial_function.

gdb/ChangeLog:

	* tui/tui-stack.c (tui_show_frame_info): Fix type mismatch.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change the size field of MSP430_Opcode_Decoded to a plain integer.
@ 2016-06-14 21:49 sergiodj+buildbot
  2016-06-14 21:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 21:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99a54ef6f705eedb20f8f4baf3fdd47cc5ca8a92 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 99a54ef6f705eedb20f8f4baf3fdd47cc5ca8a92

Change the size field of MSP430_Opcode_Decoded to a plain integer.

The size field was defined as an instance of an enum, but existing code
treats the size field as a plain integer containing a bit count.

include/ChangeLog:

	* opcode/msp430-decode.h (MSP430_Size): Remove.
	(Msp430_Opcode_Decoded): Change type of size to int.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove unneeded checks on type lengths.
@ 2016-06-15  0:47 sergiodj+buildbot
  2016-06-15  0:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-15  0:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bf5402d913e9a5d17d9ffb8701dbd054e1d158c ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 4bf5402d913e9a5d17d9ffb8701dbd054e1d158c

Remove unneeded checks on type lengths.

Type lengths are unsigned, so they are always greater than or equal to
zero.  A check against the length of 'tgt_type' is retained to prevent
dividing by zero.

gdb/ChangeLog:

	* v850-tdep.c (v850_use_struct_convention): Trim type length checks.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR ld/20254
@ 2016-06-15  8:13 sergiodj+buildbot
  2016-06-15  7:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-15  8:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31eef93e717c59975b3e6f37619ab956302ca37a ***

Author: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com>
Branch: master
Commit: 31eef93e717c59975b3e6f37619ab956302ca37a

Fix PR ld/20254

This patch fixes another edge case related to alignment property
records - reloc offsets adjacent to property record offsets were not
getting adjusted during relaxation.

bfd/

	PR ld/20254
	* elf32-avr.c (elf32_avr_relax_delete_bytes): Adjust reloc
	offsets until reloc_toaddr.

ld/

	PR ld/20254
	* testsuite/ld-avr/avr-prop-6.d: New test.
	* testsuite/ld-avr/avr-prop-6.s: New test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes/arc: Fix extract for some add_s instructions
@ 2016-06-15  8:34 sergiodj+buildbot
  2016-06-15  8:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-15  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02f3be19f6fca3a46794f8f32350cc090ac38d0e ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: 02f3be19f6fca3a46794f8f32350cc090ac38d0e

opcodes/arc: Fix extract for some add_s instructions

The extract function used for some arc_s instructions was not
implemented, and instead always returned 0.  Fixed in this commit.

opcodes/ChangeLog:

	* arc-opc.c (extract_rhv1): Extract value from insn.

gas/ChangeLog:

	* testsuite/gas/arc/add_s.d: New file.
	* testsuite/gas/arc/add_s.s: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix simple gas testsuite failures.
@ 2016-06-15 15:51 sergiodj+buildbot
  2016-06-15 15:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-15 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ee6e4fbec4a4e0451f20efce50acb720e921a9f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 3ee6e4fbec4a4e0451f20efce50acb720e921a9f

Fix simple gas testsuite failures.

binutils* readelf.c (is_24bit_abs_reloc): Add support for R_FT32_20
	reloc.

gas	* config/tc-ft32.c (md_assemble): Call dwarf2_emit_insn with the
	instruction size.
	* config/tc-mcore.c (md_assemble): Likewise.
	* config/tc-mn10200.c (md_assemble): Likewise.
	* config/tc-moxie.c (md_assemble): Likewise.
	* config/tc-pj.c (md_apply_fix): Handle BFD_RELOC_PJ_CODE_REL32.
	* testsuite/gas/all/gas.exp (diff1 test): Alpha sort list of
	exception targets.  Add alpha, hppa, microblaze and rl78 to list
	of exceptions.
	(forward): Add microblaze to list of exceptions.
	(fwdexp): Add alpha to list of exceptions.
	(redef2): Add arm-epoc-pe and rl78 to list of exceptions.
	(redef3): Add rl78 and x86_64 cygwin to list of exceptions.
	(do_930509a): Alpha sort list of exception targets.  Add h8300 and
	mn10200 to list of exceptions.
	(align2): Expect to fail for nds32.
	(cond): Add alpha and rl78 to list of exceptions.
	* testsuite/gas/all/none.d: Skip for ft32 and hppa.
	* testsuite/gas/all/string.d: Skip for tic4x.
	* testsuite/gas/alpha/alpha.exp: Note that the alpha-linuxecoff
	target does not support ELF.
	* testsuite/gas/arm/blx-bl-convert.dL Skip for the nto target.
	* testsuite/gas/cfi/cfi-alpha-2.d: All extended format names.
	* testsuite/gas/cfi/cfi.exp: Alpha sort list of targets.  Skip SH
	tests for sh-pe and sh-rtemscoff targets.
	* testsuite/gas/elf/elf.exp (redef): Add rl78, xgate and vax to
	list of exceptions.
	(type): Run the noifunc version for alpha-freebsd and visium.
	* testsuite/gas/elf/warn-2.s: Do not expect to fail on the mcore,
	mn10200 or moxie targets.
	* testsuite/gas/ft32/insn.d: Update expected disassembly.
	* testsuite/gas/i386/i386.exp (x86-64-pcrel): Skip for cygwin
	targets.
	* testsuite/gas/lns/lns.exp (lns-common-1): No longer skip for
	mcore and rx targets.
	* testsuite/gas/macros/macros.exp (dot): Add exceptions for ns32k,
	rl78 and vax.
	(purge): Expect to fail on the ns32k and vax.
	* testsuite/gas/nds32/alu-2.d: Update expected disassembly.
	* testsuite/gas/nds32/ls.d: Likewise.
	* testsuite/gas/nds32/sys-reg.d: Likewise.
	* testsuite/gas/nds32/usr-spe-reg.d: Likewise.
	* testsuite/gas/pe/aligncomm-d.d: Skip for the sh.
	* testsuite/gas/pe/section-align-3.d: Likewise.
	* testsuite/gas/pe/section-exclude.d: Likewise.
	* testsuite/gas/ppc/test2xcoff32.d: Pass once all the required
	data has been seen.
	* testsuite/gas/ppc/textalign-xcoff-001.d: Fix up regexp to allow
	for variations in whitespace.
	* testsuite/gas/tilepro/t_constants.d: Pass once all the required
	data has been seen.
	* testsuite/gas/tilepro/t_constants.s (.safe_word): New macro.
	Installs a 32-bit value without generating warnings on 64-bit
	hosts.
	Use the new macro to replace the .word directives.

opcodes	* nds32-dis.c (nds32_parse_audio_ext): Change printing of integer
	constants to match expected behaviour.
	(nds32_parse_opcode): Likewise.  Also for whitespace.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Check SEC_ALLOC before allocating dynamic relocation
@ 2016-06-16  2:00 sergiodj+buildbot
  2016-06-16  2:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-16  2:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c23f2ffa8fbd467bca51956130a1f30cfe34371 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 4c23f2ffa8fbd467bca51956130a1f30cfe34371

Check SEC_ALLOC before allocating dynamic relocation

	* elf32-i386.c (elf_i386_check_relocs): Check SEC_ALLOC before
	allocating dynamic relocation.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip relocations in non-loaded, non-alloced sections
@ 2016-06-16 13:19 sergiodj+buildbot
  2016-06-16 13:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-16 13:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 081b1afe5a8cfa02bf3b3cdefb80c266705c17d1 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 081b1afe5a8cfa02bf3b3cdefb80c266705c17d1

Skip relocations in non-loaded, non-alloced sections

Don't do anything special with non-loaded, non-alloced sections.
In particular, any relocs in such sections should not affect GOT
and PLT reference counting (ie. we don't allow them to create GOT
or PLT entries), there's no possibility or desire to optimize TLS
relocs, and there's not much point in propagating relocs to shared
libs that the dynamic linker won't relocate.

	* elf32-i386.c (elf_i386_check_relocs): Skip relocations in
	non-loaded, non-alloced sections.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't check undefined symbol for IFUNC reloc
@ 2016-06-16 18:57 sergiodj+buildbot
  2016-06-16 19:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-16 18:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf52d7c72035679e6b3ab601133c56a4388f4dc9 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: bf52d7c72035679e6b3ab601133c56a4388f4dc9

Don't check undefined symbol for IFUNC reloc

Since x86 elf_*_check_relocs is called after all symbols have been
resolved, there is no need to check undefined symbols for relocations
against IFUNC symbols.

bfd/

	* elf32-i386.c (elf_i386_check_relocs): Don't check undefined
	symbols for relocations against IFUNC symbols.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.

ld/

	* testsuite/ld-i386/i386.exp: Run pr19636-2e-nacl.
	* testsuite/ld-i386/pr19636-2e.d: Skip for NaCl targets.
	Remove .rel.plt section.
	* testsuite/ld-i386/pr19636-2e-nacl.d: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd, opcodes: sparc: new opcode v9{c, d, e, v, m} architectures and bfd machine numbers.
@ 2016-06-17  9:36 sergiodj+buildbot
  2016-06-17 10:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17  9:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f26fb3a1b1369a044ac642d1e82bf6fc6dfa9d9 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 4f26fb3a1b1369a044ac642d1e82bf6fc6dfa9d9

bfd,opcodes: sparc: new opcode v9{c,d,e,v,m} architectures and bfd machine numbers.

This patch adds support for the opcode architectures
SPARC_OPCODE_ARCH_V9{C,D,E,V,M} and its associated BFD machine numbers
bfd_mach_sparc_v9{c,d,e,v,m} and bfd_mach_sparc_v8plus{c,d,e,v,m}.

Note that for arches up to v9b (UltraSPARC III), the detection of the
BFD machine type was based on the bits in the e_machine field of the ELF
header.  However, there are no more available bits in that field, so
this patch takes the approach of using the hardware capabilities stored
in the object attributes HWCAPS/HWCAPS2 in order to characterize the
machine the object was built for.

bfd/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* archures.c (bfd_mach_sparc_v8plusc): Define.
	(bfd_mach_sparc_v9c): Likewise.
	(bfd_mach_sparc_v8plusd): Likewise.
	(bfd_mach_sparc_v9d): Likewise.
	(bfd_mach_sparc_v8pluse): Likewise.
	(bfd_mach_sparc_v9e): Likewise.
	(bfd_mach_sparc_v8plusv): Likewise
	(bfd_mach_sparc_v9v): Likewise.
	(bfd_mach_sparc_v8plusm): Likewise.
	(bfd_mach_sparc_v9m): Likewise.
	(bfd_mach_sparc_v9_p): Adapt to v8plusm and v9m.
	(bfd_mach_sparc_64bit_p): Likewise.
	* bfd-in2.h: Regenerate.
	* cpu-sparc.c (arch_info_struct): Add entries for
	bfd_mach_sparc_v8plus{c,d,e,v,m} and bfd_mach_sparc_v9{c,d,e,v,m}.
	* aoutx.h (machine_type): Handle bfd_mach_sparc_v8plus{c,d,e,v,m}
	and bfd_mach_sparc_v9{c,d,e,v,m}.
	* elf32-sparc.c (elf32_sparc_final_write_processing): Likewise.
	* elfxx-sparc.c (_bfd_sparc_elf_object_p): Likewise.

include/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* opcode/sparc.h (enum sparc_opcode_arch_val): Add
	SPARC_OPCODE_ARCH_V9C, SPARC_OPCODE_ARCH_V9D,
	SPARC_OPCODE_ARCH_V9E, SPARC_OPCODE_ARCH_V9V and
	SPARC_OPCODE_ARCH_V9M.

opcodes/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-dis.c (MASK_V9): Add SPARC_OPCODE_ARCH_V9{C,D,E,V,M}.
	(compute_arch_mask): Handle bfd_mach_sparc_v8plus{c,d,e,v,m} and
	bfd_mach_sparc_v9{c,d,e,v,m}.
	* sparc-opc.c (MASK_V9C): Define.
	(MASK_V9D): Likewise.
	(MASK_V9E): Likewise.
	(MASK_V9V): Likewise.
	(MASK_V9M): Likewise.
	(v6): Add MASK_V9{C,D,E,V,M}.
	(v6notlet): Likewise.
	(v7): Likewise.
	(v8): Likewise.
	(v9): Likewise.
	(v9andleon): Likewise.
	(v9a): Likewise.
	(v9b): Likewise.
	(v9c): Define.
	(v9d): Likewise.
	(v9e): Likewise.
	(v9v): Likewise.
	(v9m): Likewise.
	(sparc_opcode_archs): Add entry for v9{c,d,e,v,m}.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes, gas: adjust sparc insns and make GAS aware of it
@ 2016-06-17 10:05 sergiodj+buildbot
  2016-06-17 11:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 10:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a10c22feb4dfb7e56855033d579338a6258722d ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 7a10c22feb4dfb7e56855033d579338a6258722d

opcodes,gas: adjust sparc insns and make GAS aware of it

This patch marks the SPARC instructions in the opcodes table with their
proper opcode architectures, and makes the assembler aware of them.
This allows the assembler to properly realize when a new instruction
needs a higher architecture (after v9b) and to react accordingly
emitting an error message or bumping the architecture.

It also expands architecture mismatch tests to cover architectures
higher than v9b, and fixes a couple of minor bugs in the GAS testsuite.

opcodes/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-opc.c (sparc_opcodes): Adjust instructions opcode
	architecture according to the hardware capabilities they require.
	(sparc_priv_regs): New table.
	(sparc_hpriv_regs): Likewise.
	(sparc_asr_regs): Likewise.
	(v9anotv9m): Define.

gas/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* config/tc-sparc.c (sparc_arch_table): adjust the GAS
	architectures to use the right opcode architecture.
	(sparc_md_end): Handle v9{c,d,e,v,m}.
	(sparc_ip): Fix some comments.
	* testsuite/gas/sparc/ldx_efsr.d: Fix the architecture of this
	instruction, which is v9d.
	* testsuite/gas/sparc/mwait.s: Remove the `rd %mwait,%g1'
	instruction from the test, as %mwait is not readable.
	* testsuite/gas/sparc/mwait.d: Likewise.
	* testsuite/gas/sparc/mism-1.s: Expand to check v9b and v9e
	mismatch architecture errors.
	* testsuite/gas/sparc/mism-2.s: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes, gas: sparc: fix rdasr, wrasr, rdpr, wrpr, rdhpr, wrhpr insns.
@ 2016-06-17 11:24 sergiodj+buildbot
  2016-06-17 12:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 11:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96074adc6a780c7984645e3e42434be368974737 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 96074adc6a780c7984645e3e42434be368974737

opcodes,gas: sparc: fix rdasr,wrasr,rdpr,wrpr,rdhpr,wrhpr insns.

This patch fixes and expands the definition of the read/write
instructions for ancillary-state, privileged and hyperprivileged
registers in opcodes.

It also adds support for three new v9m hyperprivileged registers:
%hmcdper, %hmcddfr and %hva_mask_nz.

Finally, the patch expands existing tests (and adds several new ones) in
order to cover all the read/write instructions in all its variants.

opcodes/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-opc.c (rdasr): New macro.
	(wrasr): Likewise.
	(rdpr): Likewise.
	(wrpr): Likewise.
	(rdhpr): Likewise.
	(wrhpr): Likewise.
	(sparc_opcodes): Use the macros above to fix and expand the
	definition of read/write instructions from/to
	asr/privileged/hyperprivileged instructions.
	* sparc-dis.c (v9_hpriv_reg_names): Add %hmcdper, %hmcddfr and
	%hva_mask_nz.  Prefer softint_set and softint_clear over
	set_softint and clear_softint.
	(print_insn_sparc): Support %ver in Rd.

gas/ChangeLog:

2016-06-17  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* config/tc-sparc.c (hpriv_reg_table): Add registers %hmcdper,
	%hmcddfr and %hva_mask_nz.
	(sparc_ip): New handling of asr/privileged/hyperprivileged
	registers, adapted to the new form of the sparc opcodes table.
	* testsuite/gas/sparc/rdasr.s: New file.
	* testsuite/gas/sparc/rdasr.d: Likewise.
	* testsuite/gas/sparc/wrasr.s: Likewise.
	* testsuite/gas/sparc/wrasr.d: Likewise.
	* testsuite/gas/sparc/sparc.exp (sparc_elf_setup): Add rdasr and
	wrasr tests.
	* testsuite/gas/sparc/rdpr.d: Use -Av9m, as some privileged
	registers require it.
	* testsuite/gas/sparc/wrpr.s: Complete to cover all privileged
	registers and write instruction modalities.
	* testsuite/gas/sparc/wrpr.d: Likewise.
	* testsuite/gas/sparc/rdhpr.s: Likewise for hyperprivileged
	registers.
	* testsuite/gas/sparc/rdhpr.d: Likewise.
	* testsuite/gas/sparc/wrhpr.s: Likewise.
	* testsuite/gas/sparc/wrhpr.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: new AndesTech NDS32 port
@ 2016-06-17 11:35 sergiodj+buildbot
  2016-06-17 13:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a28d8e5037333291991f7b0036b273e8ca1ffc34 ***

Author: Yan-Ting Lin <currygt52@gmail.com>
Branch: master
Commit: a28d8e5037333291991f7b0036b273e8ca1ffc34

gdb: new AndesTech NDS32 port

gdb/ChangeLog:

	* Makefile.in (ALL_TARGET_OBS): Add nds32-tdep.o.
	(HFILES_NO_SRCDIR): Add nds32-tdep.h.
	(ALLDEPFILES): Add nds32-tdep.c.
	* NEWS: Mention new NDS32 port.
	* configure.tgt: Add NDS32.
	* nds32-tdep.c: New file.
	* nds32-tdep.h: New file.
	* features/Makefile (XMLTOC): Add nds32.xml.
	* features/nds32-core.xml: New file.
	* features/nds32-fpu.xml: New file.
	* features/nds32-system.xml: New file.
	* features/nds32.c: New file (generated).
	* features/nds32.xml: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Standard Target Features): Document NDS32 features.
	(NDS32 Features): New Section.

gdb/testsuite/ChangeLog:

	* gdb.base/float.exp: Add target check for nds32*-*-*.
	* gdb.xml/tdesc-regs.exp: Set core-regs for nds32*-*-*.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] More assert checks on reinsert breakpoint
@ 2016-06-17 12:52 sergiodj+buildbot
  2016-06-17 15:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 12:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8376a3cbf73ca8b623db1daa8f9c49fb83ac54bd ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8376a3cbf73ca8b623db1daa8f9c49fb83ac54bd

More assert checks on reinsert breakpoint

This patch adds more asserts, so the incorrect or sub-optimal
reinsert breakpoints manipulations (from the tests in the following
patches) can trigger them.

gdb/gdbserver:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_resume_one_lwp_throw): Assert
	has_reinsert_breakpoints returns false.
	* mem-break.c (delete_disabled_breakpoints): Assert
	bp type isn't reinsert_breakpoint.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Switch to current thread in finish_step_over
@ 2016-06-17 13:31 sergiodj+buildbot
  2016-06-17 14:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 13:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f79b145de30d6eaafc1f3f5b2aa913519fcd311f ***

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

Switch to current thread in finish_step_over

This patch adds some sanity check that reinsert breakpoints must be
there when doing step-over on software single step target.  The check
triggers an assert when running forking-threads-plus-breakpoint.exp
on arm-linux target,

 gdb/gdbserver/linux-low.c:4714: A problem internal to GDBserver has been detected.^M
 int finish_step_over(lwp_info*): Assertion `has_reinsert_breakpoints ()' failed.

the error happens when GDBserver has already resumed a thread of
process A for step-over (and wait for it hitting reinsert breakpoint),
but receives detach request for process B from GDB, which is shown in
the backtrace below,

 (gdb) bt
 #2  0x000228aa in finish_step_over (lwp=0x12bbd98) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4703
 #3  0x00025a50 in finish_step_over (lwp=0x12bbd98) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4749
 #4  complete_ongoing_step_over () at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4760
 #5  linux_detach (pid=25228) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:1503
 #6  0x00012bae in process_serial_event () at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/server.c:3974
 #7  handle_serial_event (err=<optimized out>, client_data=<optimized out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/server.c:4347
 #8  0x00016d68 in handle_file_event (event_file_desc=<optimized out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/event-loop.c:429
 #9  0x000173ea in process_event () at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/event-loop.c:184
 #10 start_event_loop () at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/event-loop.c:547
 #11 0x0000aa2c in captured_main (argv=<optimized out>, argc=<optimized out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/server.c:3719
 #12 main (argc=<optimized out>, argv=<optimized out>) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/server.c:3804

the sanity check tries to find the reinsert breakpoint from process B,
but nothing is found.  It is wrong, we need to search in process A,
since we started step-over of a thread of process A.

 (gdb) p lwp->thread->entry.id
 $3 = {pid = 25120, lwp = 25131, tid = 0}
 (gdb) p current_thread->entry.id
 $4 = {pid = 25228, lwp = 25228, tid = 0}

This patch switched current_thread to the thread we are doing step-over
in finish_step_over.

gdb/gdbserver:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (maybe_hw_step): New function.
	(linux_resume_one_lwp_throw): Call maybe_hw_step.
	(finish_step_over): Switch current_thread to lwp temporarily,
	and assert has_reinsert_breakpoints returns true.
	(proceed_one_lwp): Call maybe_hw_step.
	* mem-break.c (has_reinsert_breakpoints): New function.
	* mem-break.h (has_reinsert_breakpoints): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Step over exit with reinsert breakpoints
@ 2016-06-17 13:51 sergiodj+buildbot
  2016-06-17 16:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 13:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f50bf8e5153e3cdddd1ad5d3f7d16f2b4e5adb3c ***

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

Step over exit with reinsert breakpoints

This patch fixes a GDBserver crash when one thread is stepping over
a syscall instruction which is exit.  Step-over isn't finished due
to the exit, but GDBserver doesn't clean up the state of step-over,
so in the wait next time, GDBserver will wait on step_over_bkpt,
which is already exited, and GDBserver crashes because
'requested_child' is NULL.  See gdbserver logs below,

Need step over [LWP 14858]? yes, found breakpoint at 0x2aaaaad91307^M
proceed_all_lwps: found thread 14858 needing a step-over^M
Starting step-over on LWP 14858.  Stopping all threads^M
>>>> entering void stop_all_lwps(int, lwp_info*)
....
<<<< exiting void stop_all_lwps(int, lwp_info*)^M
Done stopping all threads for step-over.^M
pc is 0x2aaaaad91307^M
Writing 0f to 0x2aaaaad91307 in process 14858^M
Could not find fast tracepoint jump at 0x2aaaaad91307 in list (uninserting).^M
  pending reinsert at 0x2aaaaad91307^M
  step from pc 0x2aaaaad91307^M
Resuming lwp 14858 (step, signal 0, stop not expected)^M

 # Start step-over for LWP 14858

>>>> entering ptid_t linux_wait_1(ptid_t, target_waitstatus*, int)
....
LLFE: 14858 exited.
...
<<<< exiting ptid_t linux_wait_1(ptid_t, target_waitstatus*, int)

  # LWP 14858 exited
.....
>>>> entering ptid_t linux_wait_1(ptid_t, target_waitstatus*, int)^M
linux_wait_1: [<all threads>]^M
step_over_bkpt set [LWP 14858.14858], doing a blocking wait

  # but step_over_bkpt is still LWP 14858, which is wrong

The fix is to finish step-over if it is ongoing, and unsuspend other
threads.  Without the fix in linux-low.c, GDBserver will crash in
with running gdb.base/step-over-exit.exp.

gdb/gdbserver:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (unsuspend_all_lwps): Declare.
	(linux_low_filter_event): If thread exited, call finish_step_over.
	If step-over is finished, unsuspend other threads.

gdb/testsuite:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/step-over-exit.c: New.
	* gdb.base/step-over-exit.exp: New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Delete reinsert breakpoints from forked child
@ 2016-06-17 14:33 sergiodj+buildbot
  2016-06-17 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 14:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a81c5d7a7cc3ec4d60032d2a911d2f6c3eb8328 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8a81c5d7a7cc3ec4d60032d2a911d2f6c3eb8328

Delete reinsert breakpoints from forked child

When a thread is stepping over a syscall instruction with software
single step, GDBserver inserts reinsert breakpoints at the next pcs.
If the syscall call is fork, the forked child has reinsert breakpoint
in its space, and GDBserver clones parent's breakpoint list to child's.
When GDBserver resumes the child, its bp_reinsert is zero, but has
reinsert breakpoints, so the following assert is triggered if I apply
the patch extending step-over-syscall.exp.

gdb/gdbserver/linux-low.c:4292: A problem internal to GDBserver has been detected.^M
void linux_resume_one_lwp_throw(lwp_info*, int, int, siginfo_t*): Assertion `!has_reinsert_breakpoints (proc)' failed.

gdb/gdbserver:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (handle_extended_wait): If the parent is doing
	step-over, remove the reinsert breakpoints from the forked child.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Extend step-over-syscall.exp with different detach-on-fork and follow-fork modes
@ 2016-06-17 15:07 sergiodj+buildbot
  2016-06-17 19:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 15:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21a770913c24ab085fe66a5274ebe7cf9e031982 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 21a770913c24ab085fe66a5274ebe7cf9e031982

Extend step-over-syscall.exp with different detach-on-fork and follow-fork modes

This patch extends step-over-syscall.exp by setting different values to
detach-on-fork and follow-fork.

gdb/testsuite:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/step-over-syscall.exp (break_cond_on_syscall): New
	parameters follow_fork and detach_on_fork.  Set follow-fork-mode
	and detach-on-fork.  Adjust tests.
	(top level): Invoke break_cond_on_syscall with combinations of
	syscall, follow-fork-mode and detach-on-fork.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Handle reinsert breakpoints for vforked child
@ 2016-06-17 18:03 sergiodj+buildbot
  2016-06-17 18:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e7b624b851c34f6bc2ab75fcbc94db75f72eb3a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2e7b624b851c34f6bc2ab75fcbc94db75f72eb3a

Handle reinsert breakpoints for vforked child

When a thread is doing step-over with reinsert breakpoint, and the
instruction executed is a syscall doing vfork, both parent and child
share the memory, so the reinsert breakpoint in the space is visible
to both of them.  Also, removing the reinsert breakpoints from the
child will effectively remove them from the parent.  We should
carefully manipulate reinsert breakpoints for both processes.

What we are doing here is that

 - uninsert reinsert breakpoints from the parent before cloning the
   breakpoint list.  We use "uninsert" instead of "remove", because
   we need to "reinsert" them back after vfork is done.  In fact,
   "uninsert" removes them from both child and parent process space.
 - reinsert breakpoints in parent process are still copied to child's
   breakpoint list,
 - remove them from child's breakpoint list as what we did for fork,
   at this point, reinsert breakpoints are removed from the child and
   the parent, but they are still tracked by the parent's breakpoint
   list,
 - once vfork is done, "reinsert" them back to the parent,

gdb/gdbserver:

2016-06-17  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (handle_extended_wait): Call
	uninsert_reinsert_breakpoints for the parent process.  Remove
	reinsert breakpoints from the child process.  Reinsert them to
	the parent process when vfork is done.
	* mem-break.c (uninsert_reinsert_breakpoints): New function.
	(reinsert_reinsert_breakpoints): New function.
	* mem-break.h (uninsert_reinsert_breakpoints): Declare
	(reinsert_reinsert_breakpoints): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for Thumb-2 long branch veneers
@ 2016-06-17 18:13 sergiodj+buildbot
  2016-06-17 20:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-17 18:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80c135e55489435f47bbeeb3715b42289c51e30e ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 80c135e55489435f47bbeeb3715b42289c51e30e

Add support for Thumb-2 long branch veneers

2016-06-17  Thomas Preud'homme  <thomas.preudhomme@arm.com>
	    Tony Wang  <tony.wang@arm.com>

bfd/
	* elf32-arm.c (elf32_arm_stub_long_branch_thumb2_only): Define stub
	sequence.
	(stub_long_branch_thumb2_only): Define stub.
	(arm_stub_is_thumb): Add case for arm_stub_long_branch_thumb2_only.
	(arm_stub_long_branch_thumb2_only): Likewise.
	(arm_type_of_stub): Use arm_stub_long_branch_thumb2_only for Thumb-2
	capable targets.

ld/
	* testsuite/ld-arm/arm-elf.exp (Thumb-Thumb farcall M profile):
	Assemble for ARMv6-M.
	(Thumb2-Thumb2 farcall M profile): New testcase.
	* testsuite/ld-arm/farcall-thumb2-thumb2-m.d: New file.
	* testsuite/ld-arm/jump-reloc-veneers-cond-long-backward.d: Update to
	reflect the use of Thumb-2 veneers for Thumb-2 capable targets.
	* testsuite/ld-arm/jump-reloc-veneers-cond-long.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't generate PLT for IFUNC GOT/pointer reference
@ 2016-06-18 16:43 sergiodj+buildbot
  2016-06-18 16:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-18 16:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 233cc9c13af8e8182d0ce5b306526b59f5b11f37 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 233cc9c13af8e8182d0ce5b306526b59f5b11f37

Don't generate PLT for IFUNC GOT/pointer reference

If a backend supports it, PLT entry isn't needed when all references
to a STT_GNU_IFUNC symbols are done via GOT or static function pointers.
For GOT entries, We generate dynamic R_*_GLOB_DAT relocations for
preemptable symbols and R_*_IRELATIVE relocations for non-preemptable
symbols to update them with real function address.  For static pointer
pointers, we generate dynamic pointer relocations and store them in:

1. .rel[a].ifunc section in PIC object.
2. .rel[a].got section in dynamic executable.
3. .rel[a].iplt section in static executable.

We don't allocate GOT entry if it isn't used.

bfd/

	PR ld/20253
	* elf-bfd.h (_bfd_elf_allocate_ifunc_dyn_relocs): Add an
	bfd_boolean argument.
	* elf-ifunc.c (_bfd_elf_create_ifunc_sections): Replace
	"shared object" with "PIC object" in comments.
	(_bfd_elf_allocate_ifunc_dyn_relocs): Updated.  Replace
	"shared object" with "PIC object" in comments.  Avoid PLT if
	requested.  Generate dynamic relocations for non-GOT references.
	Make room for the special first entry in PLT and allocate PLT
	entry only for PLT and PC-relative references.  Store dynamic
	GOT relocations in .rel[a].iplt section for static executables.
	If PLT isn't used, always use GOT for symbol value.  Don't
	allocate GOT entry if it isn't used.
	* elf32-i386.c (elf_i386_check_relocs): Increment PLT reference
	count only in the code section.  Allocate dynamic pointer
	relocation against STT_GNU_IFUNC symbol in the non-code section.
	(elf_i386_adjust_dynamic_symbol): Increment PLT reference count
	only for PC-relative references.
	(elf_i386_allocate_dynrelocs): Pass TRUE to
	_bfd_elf_allocate_ifunc_dyn_relocs.
	(elf_i386_relocate_section): Allow R_386_GOT32/R_386_GOT32X
	relocations against STT_GNU_IFUNC symbols without PLT.  Generate
	dynamic pointer relocation against STT_GNU_IFUNC symbol in
	the non-code section and store it in the proper REL section.
	Don't allow non-pointer relocation against STT_GNU_IFUNC symbol
	without PLT.
	(elf_i386_finish_dynamic_symbol): Generate dynamic
	R_386_IRELATIVE and R_386_GLOB_DAT GOT relocations against
	STT_GNU_IFUNC symbols without PLT.
	(elf_i386_finish_dynamic_sections): Don't handle local
	STT_GNU_IFUNC symbols here.
	(elf_i386_output_arch_local_syms): Handle local STT_GNU_IFUNC
	symbols here.
	(elf_backend_output_arch_local_syms): New.
	* elf32-x86-64.c (elf_i386_check_relocs): Increment PLT reference
	count only in the code section.  Allocate dynamic pointer
	relocation against STT_GNU_IFUNC symbol in the non-code section.
	(elf_x86_64_adjust_dynamic_symbol): Increment PLT reference
	count only for PC-relative references.
	(elf_x86_64_allocate_dynrelocs): Pass TRUE to
	_bfd_elf_allocate_ifunc_dyn_relocs.
	(elf_x86_64_relocate_section): Allow R_X86_64_GOTPCREL,
	R_X86_64_GOTPCRELX, R_X86_64_REX_GOTPCRELX and
	R_X86_64_GOTPCREL64 relocations against STT_GNU_IFUNC symbols
	without PLT.  Generate dynamic pointer relocation against
	STT_GNU_IFUNC symbol in the non-code section and store it in
	the proper RELA section.  Don't allow non-pointer relocation
	against STT_GNU_IFUNC symbol without PLT.
	(elf_x86_64_finish_dynamic_symbol): Generate dynamic
	R_X86_64_IRELATIVE and R_X86_64_GLOB_DAT GOT relocations against
	STT_GNU_IFUNC symbols without PLT.
	(elf_x86_64_finish_dynamic_sections): Don't handle local
	STT_GNU_IFUNC symbols here.
	(elf_x86_64_output_arch_local_syms): Handle local STT_GNU_IFUNC
	symbols here.
	(elf_backend_output_arch_local_syms): New.
	* elfnn-aarch64.c (elfNN_aarch64_allocate_ifunc_dynrelocs):
	Pass FALSE to _bfd_elf_allocate_ifunc_dyn_relocs.

ld/

	PR ld/20253
	* testsuite/ld-i386/i386.exp: Run PR ld/20253 tests.
	* testsuite/ld-i386/no-plt.exp: Likewise.
	* testsuite/ld-x86-64/no-plt.exp: Likewise.
	* testsuite/ld-i386/pr13302.d: Remove .rel.plt section.
	* testsuite/ld-ifunc/ifunc-13-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-13-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-15-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-15-x86-64.d: Likewise.
	* testsuite/ld-x86-64/pr13082-5a.d: Likewise.
	* testsuite/ld-x86-64/pr13082-5b.d: Likewise.
	* testsuite/ld-x86-64/pr13082-6a.d: Likewise.
	* testsuite/ld-x86-64/pr13082-6b.d: Likewise.
	* testsuite/ld-i386/pr20244-2a.d: Remove .plt section.
	* testsuite/ld-ifunc/ifunc-21-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-21-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-22-x86-64.d: Likewise.
	* testsuite/ld-i386/pr20244-2b.d: Updated.
	* testsuite/ld-i386/pr20244-2c.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-x86-64.d: Likewise.
	* testsuite/ld-i386/pr20253-1a.c: New file.
	* testsuite/ld-i386/pr20253-1b.S: Likewise.
	* testsuite/ld-i386/pr20253-1c.S: Likewise.
	* testsuite/ld-i386/pr20253-1d.S: Likewise.
	* testsuite/ld-i386/pr20253-2a.c: Likewise.
	* testsuite/ld-i386/pr20253-2b.S: Likewise.
	* testsuite/ld-i386/pr20253-2c.S: Likewise.
	* testsuite/ld-i386/pr20253-2d.S: Likewise.
	* testsuite/ld-i386/pr20253-3.d: Likewise.
	* testsuite/ld-i386/pr20253-3.s: Likewise.
	* testsuite/ld-i386/pr20253-4.s: Likewise.
	* testsuite/ld-i386/pr20253-4a.d: Likewise.
	* testsuite/ld-i386/pr20253-4b.d: Likewise.
	* testsuite/ld-i386/pr20253-4c.d: Likewise.
	* testsuite/ld-i386/pr20253-5.d: Likewise.
	* testsuite/ld-i386/pr20253-5.s: Likewise.
	* testsuite/ld-ifunc/ifunc-23-x86.s: Likewise.
	* testsuite/ld-ifunc/ifunc-23a-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-23b-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-23c-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-24-x86.s: Likewise.
	* testsuite/ld-ifunc/ifunc-24a-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-24b-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-24c-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-25-x86.s: Likewise.
	* testsuite/ld-ifunc/ifunc-25a-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-25b-x86.d: Likewise.
	* testsuite/ld-ifunc/ifunc-25c-x86.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1.s: Likewise.
	* testsuite/ld-x86-64/pr20253-1a.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1b.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1c.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1d.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1e.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1f.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1g.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1h.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1i.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1j.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1k.d: Likewise.
	* testsuite/ld-x86-64/pr20253-1l.d: Likewise.
	* testsuite/ld-x86-64/pr20253-2a.c: Likewise.
	* testsuite/ld-x86-64/pr20253-2b.S: Likewise.
	* testsuite/ld-x86-64/pr20253-2c.S: Likewise.
	* testsuite/ld-x86-64/pr20253-2d.S: Likewise.
	* testsuite/ld-x86-64/pr20253-3.d: Likewise.
	* testsuite/ld-x86-64/pr20253-3.s: Likewise.
	* testsuite/ld-x86-64/pr20253-4.s: Likewise.
	* testsuite/ld-x86-64/pr20253-4a.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4b.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4c.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4d.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4e.d: Likewise.
	* testsuite/ld-x86-64/pr20253-4f.d: Likewise.
	* testsuite/ld-x86-64/pr20253-5.s: Likewise.
	* testsuite/ld-x86-64/pr20253-5a.d: Likewise.
	* testsuite/ld-x86-64/pr20253-5b.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a-i386.d: Remove extra IRELATIVE
	relocation.
	* testsuite/ld-ifunc/ifunc-18a-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-i386.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18b-x86-64.d: Likewise.
	* testsuite/ld-ifunc/ifunc-18a.s: Fix a typo.
	* testsuite/ld-x86-64/x86-64.exp: Run pr20253-1 tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Rename bfd_plugin_uknown to bfd_plugin_unknown
@ 2016-06-18 21:39 sergiodj+buildbot
  2016-06-18 21:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-18 21:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49f30d83f659591d7d2b14a18dc8308b3fdb8dd5 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 49f30d83f659591d7d2b14a18dc8308b3fdb8dd5

Rename bfd_plugin_uknown to bfd_plugin_unknown

bfd/

	* bfd.c (bfd_plugin_format): Rename bfd_plugin_uknown to
	bfd_plugin_unknown.
	* bfd-in2.h: Regenerated.
	* plugin.c (bfd_plugin_object_p): Replace bfd_plugin_uknown
	with bfd_plugin_unknown.

ld/

	* plugin.c (plugin_object_p): Replace bfd_plugin_uknown
	with bfd_plugin_unknown.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR ld/20276: Set non_ir_ref on common symbol
@ 2016-06-20  2:13 sergiodj+buildbot
  2016-06-20  2:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-20  2:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0616a2803812f5c13f8936d281bd71c3d9c09655 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 0616a2803812f5c13f8936d281bd71c3d9c09655

PR ld/20276: Set non_ir_ref on common symbol

Also, don't check alignment on symbol from plugin dummy input.

bfd/
	PR ld/20276
	* elflink.c (elf_link_add_object_symbols): Don't check alignment
	on symbol from plugin dummy input.
ld/
	PR ld/20276
	* plugin.c (plugin_notice): Set non_ir_ref on common symbols.
	* testsuite/ld-plugin/lto.exp (lto_link_tests): Add test for
	PR ld/20276.
	(lto_run_tests): Likewise.
	* testsuite/ld-plugin/pass.out: New file.
	* testsuite/ld-plugin/pr20276a.c: Likewise.
	* testsuite/ld-plugin/pr20276b.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [Ada catchpoints] Fix "warning: failed to get exception name: No definition of \"e.full_name\" in current context"
@ 2016-06-21  1:41 sergiodj+buildbot
  2016-06-21  1:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  1:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45db7c09c37c9aceb3a7e149a6577388fc566432 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 45db7c09c37c9aceb3a7e149a6577388fc566432

[Ada catchpoints] Fix "warning: failed to get exception name: No definition of \"e.full_name\" in current context"

Looking at testsuite results, I noticed this warning in an MI test:

 ~"\nCatchpoint "
 ~"2, "
 &"warning: failed to get exception name: No definition of \"e.full_name\" in current context.\n"
 ~"exception at 0x000000000040192d in foo () at /home/pedro/brno/pedro/gdb/mygit/src/gdb/testsuite/gdb.ada/mi_catch_ex/foo.adb:20\n"
 ~"20\t      raise Constraint_Error;  -- SPOT1\n"
 *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",exception-name="CONSTRAINT_ERROR",frame={addr="0x000000000040192d",func="foo",args=[],file="/home/pedro/brno/pedro/gdb/mygit/src/gdb/testsuite/gdb.ada/mi_catch_ex/foo.adb",fullname="/home/pedro/brno/pedro/gdb/mygit/src/gdb/testsuite/gdb.ada/mi_catch_ex/foo.adb",line="20"},thread-id="1",stopped-threads="all",core="5"
 (gdb)
 PASS: gdb.ada/mi_catch_ex.exp: continue until CE caught by all-exceptions catchpoint

The problem is that:

  - MI prints the breakpoint hit twice: once on the MI stream;
    another time on the console stream.

  - After printing the Ada catchpoint hit, gdb selects a non-current
    frame, from within the catchpoint's print_it routine.

So the second time the breakpoint is printed, the selected frame is no
longer the current frame, and then evaluating e.full_name in
ada_exception_name_addr fails.

This commit fixes the problem and enhances the gdb.ada/mi_catch_ex.exp
test to make sure the catchpoint hit is printed correctly on the
console stream too.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_exception_name_addr_1): Add comment.
	(print_it_exception): Select the current frame.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.ada/mi_catch_ex.exp (continue_to_exception): New procedure.
	(top level): Use it instead of mi_execute_to.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce "struct ui"
@ 2016-06-21  1:57 sergiodj+buildbot
  2016-06-21  2:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a74e1786ac24d4ef1ce8a92a1ab06c727a462881 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a74e1786ac24d4ef1ce8a92a1ab06c727a462881

Introduce "struct ui"

This is a step towards supporting multiple consoles/MIs, each on its
own stdio streams / terminal.

See intro comment in top.h.

(I've had trouble picking a name for this object.  I've started out
with "struct console" originally.  But then this is about MI as well,
and there's "interpreter-exec console", which is specifically about
the CLI...

So I changed to "struct terminal", but, then we have a terminal object
that works when the input is not a terminal as well ...

Then I sort of gave up and renamed it to "struct top_level".  But it
then gets horribly confusing when we talk about the "top level
interpreter that's running on the current top level".

In the end, I realized we're already sort of calling this "ui", in
struct ui_out, struct ui_file, and a few coments here and there.)

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c: Update readline-related comments.
	(input_handler, call_readline): Delete globals.
	(gdb_rl_callback_handler): Call the current UI's input_handler
	method.
	(change_line_handler): Adjust to set current UI's properties
	instead of globals.
	(current_ui_, current_ui): New globals.
	(get_command_line_buffer): Rewrite to refer to the current UI.
	(stdin_event_handler): Adjust to call the call_readline method of
	the current UI.
	(gdb_readline_no_editing_callback): Adjust to call the current UI's
	input_handler method.
	(gdb_setup_readline): Adjust to set current UI's properties
	instead of globals.
	* event-top.h (call_readline, input_handler): Delete declarations.
	* mi/mi-interp.c (mi_interpreter_resume): Adjust to set current
	UI's properties instead of globals.
	* top.c (gdb_readline_wrapper_cleanup): Adjust to set current UI's
	properties instead of globals.
	(gdb_readline_wrapper): Adjust to call and set current UI's
	methods instead of globals.
	* top.h: Include buffer.h and event-loop.h.
	(struct ui): New struct.
	(current_ui): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb_stdout&co be per UI
@ 2016-06-21  2:22 sergiodj+buildbot
  2016-06-21  3:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  2:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79aa2fe86f105fae162f780f760d655f212eaeb6 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 79aa2fe86f105fae162f780f760d655f212eaeb6

Make gdb_stdout&co be per UI

We need to have these send output to the proper UI.

However, this patch still make them look like globals.  Kind of like
__thread variables, if you will.  Changing everything throughout to
write something like current_ui->gdb_stdout instead would be massive
overkill, IMNSHO.

This leaves gdb_stdtargin/stdtarg/stdtargerr global, but maybe that was a
mistake, I'm not sure -- IIRC, MI formats target I/O differently, so
if we have a separate MI channel, then I guess target output should go
there instead of to gdb's stdout.  OTOH, maybe GDB should send that
instead to "set inferior-tty", instead of multiplexing it over MI.  We
can always fix those later when it gets clearer where they should go.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* main.c (gdb_stdout, gdb_stderr, gdb_stdlog, gdb_stdin): Delete
	globals.
	(gen_ret_current_ui_field_ptr): New macro.  Use it to generate
	wrappers for gdb_stdout, gdb_stderr, gdb_stdlog and gdb_stdin.
	* top.h (struct ui) <m_gdb_stdout, m_gdb_stdin, m_gdb_stderr,
	m_gdb_stdlog>: New fields.
	(current_ui_gdb_stdout_ptr, current_ui_gdb_stdin_ptr)
	(current_ui_gdb_stderr_ptr, current_ui_gdb_stdlog_ptr): Declare.
	(gdb_stdout, gdb_stdin, gdb_stderr, gdb_stdlog): Reimplement as
	macros.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make the interpreters be per UI
@ 2016-06-21  3:09 sergiodj+buildbot
  2016-06-21  4:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  3:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb814510676f7f6c08b329af2f57006fa598b619 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: cb814510676f7f6c08b329af2f57006fa598b619

Make the interpreters be per UI

Make each UI have its own interpreter list, top level interpreter,
current interpreter, etc.  The "interpreter_async" global is not
really specific to an struct interp (it crosses interpreter-exec ...),
so I moved it to "struct ui" directly, while the other globals were
left hidden in interps.c, opaque to the rest of GDB.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (bpstat_do_actions_1): Access the current UI's
	async field instead of the interpreter_async global.
	* cli/cli-script.c (execute_user_command, while_command)
	(if_command, script_from_file): Likewise.
	* compile/compile.c: Include top.h instead of interps.h.
	(compile_file_command, compile_code_command)
	(compile_print_command): Access the current UI's async field
	instead of the interpreter_async global.
	* guile/guile.c: Include top.h instead of interps.h.
	(guile_repl_command, guile_command, gdbscm_execute_gdb_command):
	Access the current UI's async field instead of the
	interpreter_async global.
	* guile/scm-ports.c: Include top.h instead of interps.h.
	(ioscm_with_output_to_port_worker): Access the current UI's async
	field instead of the interpreter_async global.
	* inf-loop.c (inferior_event_handler): Likewise.
	* infcall.c (run_inferior_call): Likewise.
	* infrun.c (reinstall_readline_callback_handler_cleanup)
	(fetch_inferior_event): Likewise.
	* interps.c (interpreter_async): Delete.
	(struct ui_interp_info): New.
	(get_current_interp_info): New function.
	(interp_list, current_interpreter, top_level_interpreter_ptr):
	Delete.
	(interp_add, interp_set, interp_lookup, interp_ui_out)
	(current_interp_set_logging, interp_set_temp)
	(current_interp_named_p): Adjust to per-UI interpreters.
	(command_interpreter): Delete.
	(command_interp, current_interp_command_loop, interp_quiet_p)
	(interp_exec, interpreter_exec_cmd, interpreter_completer)
	(top_level_interpreter, top_level_interpreter_data): Adjust to
	per-UI interpreters.
	* interps.h (interpreter_async): Delete.
	* main.c (captured_command_loop): Access the current UI's async
	field instead of the interpreter_async global.
	* python/python.c (python_interactive_command, python_command)
	(execute_gdb_command): Likewise.
	* top.c (maybe_wait_sync_command_done, execute_command_to_string):
	Access the current UI's async field instead of the
	interpreter_async global.
	* top.h (struct tl_interp_info): Forward declare.
	(struct ui) <interp_info, async>: New fields.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make the intepreters output to all UIs
@ 2016-06-21  4:34 sergiodj+buildbot
  2016-06-21  6:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  4:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73ab01a07dfef77a9d845be2ef87754435eeffa1 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 73ab01a07dfef77a9d845be2ef87754435eeffa1

Make the intepreters output to all UIs

When we have multiple consoles, MI channels, etc., then we need to
broadcast breakpoint hits, etc. to all UIs.  In the past, I've
adjusted most of the run control to communicate events to the
interpreters through observer notifications, so events would be
properly sent to console and MI streams, in sync and async modes.

This patch does the next logical step -- have each interpreter's
observers output interpreter-specific info to _all_ UIs.

Note that when we have multiple instances of active cli/tui
interpreters, then the cli_interp and tui_interp globals no longer
work.  This is addressed by this patch.

Also, the interpreters currently register some observers when resumed
and remove them when suspended.  If we have multiple instances of the
interpreters, and they can be suspended/resumed at different,
independent times, that no longer works.  What we instead do is always
install the observers, and then have the observers themselves know
when to do nothing.

An earlier prototype of this series did the looping over struct UIs in
common code, and then dispatched events to the interpreters through a
matching interp_on_foo method for each observer.  That turned out a
lot more complicated than the present solution, as we'd end up with
having to create a new interp method every time some interpreter
wanted to listen to some observer notification, resulting in a lot of
duplicated make-work and more coupling than desirable.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c (cli_interp): Delete.
	(as_cli_interp): New function.
	(cli_on_normal_stop, cli_on_signal_received)
	(cli_on_end_stepping_range, cli_on_signal_exited, cli_on_exited)
	(cli_on_no_history): Send output to all CLI UIs.
	(cli_on_sync_execution_done, cli_on_command_error): Skip output if
	the top level interpreter is not a CLI.
	(cli_interpreter_init): Don't set cli_interp or install observers
	here.
	(_initialize_cli_interp): Install observers here.
	* event-top.c (main_ui_, ui_list): New globals.
	(current_ui): Point to main_ui_.
	(restore_ui_cleanup, switch_thru_all_uis_init)
	(switch_thru_all_uis_cond, switch_thru_all_uis_next): New
	functions.
	* mi/mi-interp.c (as_mi_interp): New function.
	(mi_interpreter_init): Don't install observers here.
	(mi_on_sync_execution_done): Skip output if the top level
	interpreter is not a MI.
	(mi_new_thread, mi_thread_exit, mi_record_changed)
	(mi_inferior_added, mi_inferior_appeared, mi_inferior_exit)
	(mi_inferior_removed): Send output to all MI UIs.
	(find_mi_interpreter, mi_interp_data): Delete.
	(find_mi_interp): New function.
	(mi_on_signal_received, mi_on_end_stepping_range)
	(mi_on_signal_exited, mi_on_exited, mi_on_no_history): Send output
	to all MI UIs.
	(mi_on_normal_stop): Rename to ...
	(mi_on_normal_stop_1): ... this.
	(mi_on_normal_stop): Reimplement, sending output to all MI UIs.
	(mi_traceframe_changed, mi_tsv_created, mi_tsv_deleted)
	(mi_tsv_modified, mi_breakpoint_created, mi_breakpoint_deleted)
	(mi_breakpoint_modified, mi_output_running_pid): Send output to
	all MI UIs.
	(mi_on_resume): Rename to ...
	(mi_on_resume_1): ... this.  Don't handle infcalls here.
	(mi_on_resume): Reimplement, sending output to all MI UIs.
	(mi_solib_loaded, mi_solib_unloaded, mi_command_param_changed)
	(mi_memory_changed): Send output to all MI UIs.
	(report_initial_inferior): Install observers here.
	* top.h (struct ui) <next>: New field.
	(ui_list): Declare.
	(struct switch_thru_all_uis): New.
	(switch_thru_all_uis_init, switch_thru_all_uis_cond)
	(switch_thru_all_uis_next): Declare.
	(SWITCH_THRU_ALL_UIS): New macro.
	* tui/tui-interp.c (tui_interp): Delete global.
	(as_tui_interp): New function.
	(tui_on_normal_stop, tui_on_signal_received)
	(tui_on_end_stepping_range, tui_on_signal_exited, tui_on_exited)
	(tui_on_no_history): Send output to all TUI UIs.
	(tui_on_sync_execution_done, tui_on_command_error): Skip output if
	the top level interpreter is not a TUI.
	(tui_init): Don't set tui_interp or install observers here.
	(_initialize_tui_interp): Install observers here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Always run async signal handlers in the main UI
@ 2016-06-21  5:16 sergiodj+buildbot
  2016-06-21  7:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  5:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c36c34e4c5c9438f17373a72773d741a17dc7b3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7c36c34e4c5c9438f17373a72773d741a17dc7b3

Always run async signal handlers in the main UI

Async signal handlers have no connection to whichever was the current
UI, and thus always run on the main one.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-loop.c: Include top.h.
	(invoke_async_signal_handlers): Switch to the main UI.
	* event-top.c (main_ui_): Update comment.
	(main_ui): New global.
	* top.h (main_ui): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce interpreter factories
@ 2016-06-21  5:39 sergiodj+buildbot
  2016-06-21  5:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  5:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8322445e0584be846f5873b9aab257dc9fbda05d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 8322445e0584be846f5873b9aab257dc9fbda05d

Introduce interpreter factories

If every UI instance has its own set of interpreters, then the current
scheme of creating the interpreters at GDB initialization time no
longer works.  We need to create them whenever a new UI instance is
created.

The scheme implemented here has each interpreter register a factory
callback that when called creates a new instance of a specific
interpreter type.  Then, when some code in gdb looks up an interpreter
(always by name), if there's none yet, the factory method is called to
construct one.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c (cli_uiout): Delete, moved into ...
	(struct cli_interp): ... this new structure.
	(cli_on_normal_stop, cli_on_signal_received)
	(cli_on_end_stepping_range, cli_on_signal_exited, cli_on_exited)
	(cli_on_no_history): Use interp_ui_out.
	(cli_interpreter_init): If top level, set the cli_interp global.
	(cli_interpreter_init): Return the interp's data instead of NULL.
	(cli_interpreter_resume, cli_interpreter_exec, cli_ui_out): Adjust
	to cli_uiout being in the interpreter's data.
	(cli_interp_procs): New, factored out from _initialize_cli_interp.
	(cli_interp_factory): New function.
	(_initialize_cli_interp): Call interp_factory_register.
	* interps.c (get_interp_info): New, factored out from ...
	(get_current_interp_info): ... this.
	(interp_new): Add parameter 'data'.  Store it.
	(struct interp_factory): New function.
	(interp_factory_p): New typedef.  Define a VEC_P.
	(interpreter_factories): New global.
	(interp_factory_register): New function.
	(interp_add): Add 'ui' parameter.  Use get_interp_info and
	interp_lookup_existing.
	(interp_lookup): Rename to ...
	(interp_lookup_existing): ... this.  Add 'ui' parameter.  Don't
	check for NULL or empty name here.
	(interp_lookup): Add 'ui' parameter and reimplement.
	(interp_set_temp, interpreter_exec_cmd): Adjust.
	(interpreter_completer): Complete on registered interpreter
	factories instead of interpreters.
	* interps.h (interp_factory_func): New typedef.
	(interp_factory_register): Declare.
	(interp_new, interp_add): Adjust.
	(interp_lookup): Declare.
	* main.c (captured_main): Adjust.
	* mi/mi-interp.c (mi_cmd_interpreter_exec): Adjust.
	(mi_interp_procs): New, factored out from
	_initialize_mi_interp.
	(mi_interp_factory): New function.
	* python/python.c (execute_gdb_command): Adjust.
	* tui/tui-interp.c (tui_init): If top level, set the tui_interp
	global.
	(tui_interp_procs): New.
	(tui_interp_factory): New function.
	(_initialize_tui_interp): Call interp_factory_register.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make instream be per UI
@ 2016-06-21  5:42 sergiodj+buildbot
  2016-06-21  8:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  5:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f38d3ad186f1820596743a04b7394b0749942501 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f38d3ad186f1820596743a04b7394b0749942501

Make instream be per UI

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-script.c (execute_user_command, read_next_line)
	(read_next_line): Adjust to per-UI instream.
	* event-top.c (stdin_event_handler, command_handler)
	(handle_line_of_input, command_line_handler)
	(gdb_readline_no_editing_callback, async_sigterm_handler)
	(gdb_setup_readline): Likewise.
	* inflow.c: Include top.h.
	(gdb_has_a_terminal, child_terminal_init_with_pgrp)
	(gdb_save_tty_state, child_terminal_inferior)
	(child_terminal_ours_1, copy_terminal_info): Use the main UI.
	(initialize_stdin_serial): Adjust to per-UI instream.
	* main.c (captured_command_loop, captured_main): Adjust to per-UI
	instream.
	* mi/mi-interp.c (mi_execute_command_wrapper): Likewise.
	* python/python.c (python_interactive_command): Likewise.
	* terminal.h (struct ui): Forward declare.
	(initialize_stdin_serial): Add struct ui parameter.
	* top.c (instream): Delete.
	(do_restore_instream_cleanup, read_command_file, dont_repeat)
	(gdb_readline_no_editing, command_line_input)
	(input_from_terminal_p, gdb_init): Adjust to per-UI instream.
	* top.h (struct ui) <instream>: New field.
	(instream): Delete declaration.
	(quit): Adjust to per-UI instream.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.gdb/selftest.exp (do_steps_and_nexts): Add new regexp.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make input_fd be per UI
@ 2016-06-21  6:37 sergiodj+buildbot
  2016-06-21  9:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41fd2b0f5d958fe3056da5c7af4032b1b99d726f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 41fd2b0f5d958fe3056da5c7af4032b1b99d726f

Make input_fd be per UI

And with that, we can switch the current UI to the UI whose input
descriptor woke up the event loop.  IOW, if the user types in UI 2,
the event loop wakes up, switches to UI 2, and processes the input.
Next the user types in UI 3, the event loop wakes up and switches to
UI 3, etc.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (input_fd): Delete.
	(stdin_event_handler): Switch to the UI whose input descriptor got
	the event.  Adjust to per-UI input_fd.
	(gdb_setup_readline): Don't set the input_fd global.  Adjust to
	per-UI input_fd.
	(gdb_disable_readline): Adjust to per-UI input_fd.
	* event-top.h (input_fd): Delete declaration.
	* linux-nat.c (linux_nat_terminal_inferior): Don't remove input_fd
	from the event-loop here.
	(linux_nat_terminal_ours): Don't register input_fd in the
	event-loop here.
	* main.c (captured_main): Adjust to per-UI input_fd.
	* remote.c (remote_terminal_inferior): Don't remove input_fd from
	the event-loop here.
	(remote_terminal_ours): Don't register input_fd in the event-loop
	here.
	* target.c: Include top.h and event-top.h.
	(target_terminal_inferior): Remove input_fd from the event-loop
	here.
	(target_terminal_ours): Register input_fd in the event-loop.
	* top.h (struct ui) <input_fd>: New field.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Delete def_uiout
@ 2016-06-21  7:51 sergiodj+buildbot
  2016-06-21 11:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  7:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23ff98d2fed4a1eaeb815e18cd4169e5aa7aaa60 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 23ff98d2fed4a1eaeb815e18cd4169e5aa7aaa60

Delete def_uiout

Currently, current_uiout starts out pointing to def_uiout, a dummy
ui_out implementation.

Since we create a replacement uiout early on as soon as we create the
interpreter, we never actually use def_uiout.  So this patch removes
it.

The proof that it works is that starting with current_uiout set to
NULL does not crash.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* ui-out.c (default_ui_out_impl): Delete.
	(def_uiout): Delete.
	(current_uiout): Set to NULL.
	(default_table_begin, default_table_body, default_table_end)
	(default_table_header, default_begin, default_end)
	(default_field_int, default_field_skip, default_field_string)
	(default_field_fmt, default_spaces, default_text, default_message)
	(default_wrap_hint, default_flush, default_data_destroy): Delete.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make command line editing (use of readline) be per UI
@ 2016-06-21  9:06 sergiodj+buildbot
  2016-06-21 13:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  9:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c216924d6ae534ea6c2f6bdcc4b42238af52ab1 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3c216924d6ae534ea6c2f6bdcc4b42238af52ab1

Make command line editing (use of readline) be per UI

Due to the way that readline's API works (based on globals), we can
only have one instance of readline in a process.  So the goal of this
patch is to only allow editing in the main UI, and make sure that only
one UI calls into readline.  Some MI paths touch readline variables
currently, which is bad as that is changing variables that matter for
the main console UI.  This patch fixes those.

This actually fixes a nasty bug -- starting gdb in MI mode ("gdb
-i=mi"), and then doing "set editing on" crashes GDB, because MI is
not prepared to use readline:

 set editing on
 &"set editing on\n"
 =cmd-param-changed,param="editing",value="on"
 ^done
 (gdb)
 p 1
 readline: readline_callback_read_char() called with no handler!
 Aborted (core dumped)

The fix for that was to add an interp_proc method to query the
interpreter whether it actually supports editing.  New test included.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	PR mi/20034
	* cli/cli-interp.c: Include cli-interp.h and event-top.h.
	(cli_interpreter_resume): Pass 1 to gdb_setup_readline.  Set the
	UI's input_handler here.
	(cli_interpreter_supports_command_editing): New function.
	(cli_interp_procs): Install it.
	* cli/cli-interp.h: New file.
	* event-top.c (async_command_editing_p): Rename to ...
	(set_editing_cmd_var): ... this.
	(change_line_handler): Add parameter 'editing', and use it.  Bail
	early if the interpreter doesn't support editing.  Don't touch
	readline state if editing is off.
	(gdb_rl_callback_handler_remove, gdb_rl_callback_handler_install)
	(gdb_rl_callback_handler_reinstall): Assert the current UI is the
	main UI.
	(display_gdb_prompt): Don't call gdb_rl_callback_handler_remove if
	not using readline.  Check whether the current UI is using command
	editing instead of checking the async_command_editing_p global.
	(set_async_editing_command): Delete.
	(gdb_setup_readline): Add 'editing' parameter.  Only allow editing
	on the main UI.  Don't touch readline state if editing is off.
	(gdb_disable_readline): Don't touch readline state if editing is
	off.
	* event-top.h (gdb_setup_readline): Add 'int' parameter.
	(set_async_editing_command): Delete declaration.
	(change_line_handler, command_line_handler): Declare.
	(async_command_editing_p): Rename to ...
	(set_editing_cmd_var): ... this.
	* infrun.c (reinstall_readline_callback_handler_cleanup): Check
	whether the current UI has editing enabled rather than checking
	the async_command_editing_p global.
	* interps.c (interp_supports_command_editing): New function.
	* interps.h (interp_supports_command_editing_ftype): New typedef.
	(struct interp_procs) <supports_command_editing_proc>: New field.
	(interp_supports_command_editing): Declare.
	* mi/mi-interp.c (mi_interpreter_resume): Pass 0 to
	gdb_setup_readline.  Don't clear the async_command_editing_p
	global.  Update comments.
	* top.c (gdb_readline_wrapper_line, gdb_readline_wrapper): Check
	whether the current UI has editing enabled rather than checking
	the async_command_editing_p global.  Don't touch readline state if
	editing is off.
	(undo_terminal_modifications_before_exit): Switch to the main UI.
	Unconditionally call gdb_disable_readline.
	(set_editing): New function.
	(show_async_command_editing_p): Rename to ...
	(show_editing): ... this.  Show the state of the current UI.
	(_initialize_top): Adjust.
	* top.h (struct ui) <command_editing>: New field.
	* tui/tui-interp.c: Include cli/cli-interp.h.
	(tui_resume): Pass 1 to gdb_setup_readline.  Set the UI's
	input_handler.
	(tui_interp_procs): Install
	cli_interpreter_supports_command_editing.
	* tui/tui-io.c (tui_getc): Check whether the current UI has
	editing enabled rather than checking the async_command_editing_p
	global.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	PR mi/20034
	* gdb.mi/mi-editing.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Always process target events in the main UI
@ 2016-06-21  9:34 sergiodj+buildbot
  2016-06-21 14:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21  9:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c61db772bf5dc21bf8e0db9acfa8796804f945ab ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c61db772bf5dc21bf8e0db9acfa8796804f945ab

Always process target events in the main UI

This makes target events always be always processed with the main UI
as current UI.  This way, warnings, debug output, etc. are always
consistently sent to the main console.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (restore_ui_cleanup): Make extern.
	* infrun.c (fetch_inferior_event): Always switch to the main UI.
	* top.h (restore_ui_cleanup): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make out and error streams be per UI
@ 2016-06-21 10:04 sergiodj+buildbot
  2016-06-21 10:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 10:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 694ec099d2fca9e7d47848e8a7fc40ea3aa47a32 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 694ec099d2fca9e7d47848e8a7fc40ea3aa47a32

Make out and error streams be per UI

stderr_fileopen () references stderr directly, which doesn't work when
we have a separate UI with its own stderr-like stream.  So this also
adds a "errstream" to "struct ui", and plumbs stderr_fileopen to take
a stream parameter.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (gdb_setup_readline): Pass the UI's outstream and
	errstream to stdout_fileopen and stderr_fileopen.
	* exceptions.c: Include top.h.
	(print_flush): Open the current UI's outstream file descriptor,
	instead of hardcoding file descriptor 1.
	* main.c (captured_main): Save the main UI's out and error
	streams.  Adjust stderr_fileopen call.
	* top.h (struct ui) <outstream, errstream>: New fields.
	* ui-file.c (stderr_fileopen): Add stream parameter.  Use it
	instead of stderr.
	* ui-file.h (stderr_fileopen): Add stream parameter and update
	comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make raw_stdout be per MI instance
@ 2016-06-21 11:28 sergiodj+buildbot
  2016-06-21 16:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9204d6922cb80f34dd799e57f7f0c74bc86e7027 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9204d6922cb80f34dd799e57f7f0c74bc86e7027

Make raw_stdout be per MI instance

Each MI instance should obviously have its own raw output channel,
along with save_raw_stdout.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* interps.c (current_interpreter): New function.
	* interps.h (current_interpreter): New declaration.
	* mi/mi-cmds.h (raw_stdout): Delete declaration.
	* mi/mi-common.h (struct mi_interp) <raw_stdout,
	saved_raw_stdout>: New field.
	* mi/mi-interp.c (display_mi_prompt): New parameter 'mi'.  Adjust
	to per-UI raw_stdout.
	(mi_interpreter_init): Adjust to per-UI raw_stdout.
	(mi_on_sync_execution_done, mi_execute_command_input_handler)
	(mi_command_loop): Pass MI instance to display_mi_prompt.
	(mi_on_normal_stop_1, mi_output_running_pid, mi_on_resume_1)
	(mi_on_resume): Adjust to per-UI raw_stdout.
	(saved_raw_stdout): Delete.
	(mi_set_logging): Adjust to per-UI raw_stdout and
	saved_raw_stdout.
	* mi/mi-main.c (raw_stdout): Delete.
	(mi_cmd_gdb_exit, captured_mi_execute_command)
	(mi_print_exception, mi_load_progress): Adjust to per-UI
	raw_stdout.
	(print_diff_now, mi_print_timing_maybe): New ui_file parameter.
	Pass it along.
	(print_diff): New ui_file parameter.  Send output there instead of
	raw_stdout.
	* mi/mi-main.h (struct ui_file): Forward declare.
	(mi_print_timing_maybe): Add ui_file parameter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make current_ui_out be per UI
@ 2016-06-21 11:56 sergiodj+buildbot
  2016-06-21 11:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6dcde571e1a230d12fc483ba6d38a1253ab097e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b6dcde571e1a230d12fc483ba6d38a1253ab097e

Make current_ui_out be per UI

Similarly to gdb_stdout&co.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* top.c: Call gen_ret_current_ui_field_ptr for current_uiout.
	* top.h (struct ui) <m_current_uiout>: New field.
	* ui-out.c (current_uiout): Delete.
	* ui-out.h (current_uiout): Delete.
	(current_ui_current_uiout_ptr): New declaration.
	(current_uiout): Reimplement as wrapper around
	current_ui_current_uiout_ptr.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb_in_secondary_prompt_p() be per UI
@ 2016-06-21 12:26 sergiodj+buildbot
  2016-06-21 18:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dbf30ca3f5fec91671b37592f1a6644a2c36f67a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: dbf30ca3f5fec91671b37592f1a6644a2c36f67a

Make gdb_in_secondary_prompt_p() be per UI

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* top.c (gdb_secondary_prompt_depth): Delete.
	(gdb_in_secondary_prompt_p): Add ui parameter.  Use it.
	(gdb_readline_wrapper_cleanup, gdb_readline_wrapper): Adjust to
	per-UI gdb_secondary_prompt_depth.
	* top.h (struct ui) <secondary_prompt_depth>: New field.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Replace the sync_execution global with a new enum prompt_state tristate
@ 2016-06-21 13:19 sergiodj+buildbot
  2016-06-21 19:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 13:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b12939dfc2399200f243851fd55d0e392b64165 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3b12939dfc2399200f243851fd55d0e392b64165

Replace the sync_execution global with a new enum prompt_state tristate

When sync_execution (a boolean) is true, it means we're running a
foreground command -- we hide the prompt stop listening to input, give
the inferior the terminal, then go to the event loop waiting for the
target to stop.

With multiple independent UIs, we need to track whether each UI is
synchronously blocked waiting for the target.  IOW, if you do
"continue" in one console, that console stops accepting commands, but
you should still be free to type other commands in the others
consoles.

Just simply making sync_execution be per-UI alone not sufficient,
because of this in fetch_inferior_event:

  /* If the inferior was in sync execution mode, and now isn't,
     restore the prompt (a synchronous execution command has finished,
     and we're ready for input).  */
  if (current_ui->async && was_sync && !sync_execution)
    observer_notify_sync_execution_done ();

We'd have to record at entry the "was_sync" state for each UI, not
just of the current UI.

This patch instead replaces the sync_execution flag by a per-UI
tristate flag indicating the command line prompt state:

 enum prompt_state
 {
   /* The command line is blocked simulating synchronous execution.
      This is used to implement the foreground execution commands
      ('run', 'continue', etc.).  We won't display the prompt and
      accept further commands until the execution is actually over.  */
   PROMPT_BLOCKED,

   /* The command finished; display the prompt before returning back to
      the top level.  */
   PROMPT_NEEDED,

   /* We've displayed the prompt already, ready for input.  */
   PROMPTED,
 ;

I think the end result is _much_ clearer than the current code, and,
it addresses the original motivation too.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* annotate.c: Include top.h.
	(async_background_execution_p): Delete.
	(print_value_flags): Check the UI's prompt state rather then
	async_background_execution_p.
	* event-loop.c (start_event_loop): Set the prompt state to
	PROMPT_NEEDED.
	* event-top.c (display_gdb_prompt, async_enable_stdin)
	(async_disable_stdin): Check the current UI's prompt state instead
	of the sync_execution global.
	(command_line_handler): Set the prompt state to PROMPT_NEEDED
	before running a command, and display the prompt if still needed
	afterwards.
	* infcall.c (struct call_thread_fsm) <waiting_ui>: New field.
	(new_call_thread_fsm): New parameter 'waiting_ui'.  Store it.
	(call_thread_fsm_should_stop): Set the prompt state to
	PROMPT_NEEDED.
	(run_inferior_call): Adjust to temporarily set the prompt state to
	PROMPT_BLOCKED instead of using the sync_execution global.
	(call_function_by_hand_dummy): Pass the current UI to
	new_call_thread_fsm.
	* infcmd.c: Include top.h.
	(continue_1): Check the current UI's prompt state instead of the
	sync_execution global.
	(continue_command): Validate global execution state before calling
	prepare_execution_command.
	(step_1): Call all_uis_check_sync_execution_done.
	(attach_post_wait): Don't call async_enable_stdin here.  Remove
	reference to sync_execution.
	* infrun.c (sync_execution): Delete global.
	(follow_fork_inferior)
	(reinstall_readline_callback_handler_cleanup): Check the current
	UI's prompt state instead of the sync_execution global.
	(check_curr_ui_sync_execution_done)
	(all_uis_check_sync_execution_done): New functions.
	(fetch_inferior_event): Call all_uis_check_sync_execution_done
	instead of trying to determine whether the global sync execution
	changed.
	(handle_no_resumed): Check the prompt state of all UIs.
	(normal_stop): Emit the no unwait-for even to all PROMPT_BLOCKED
	UIs.  Emit the "Switching to" notification to all UIs.  Enable
	stdin in all UIs.
	* infrun.h (sync_execution): Delete.
	(all_uis_check_sync_execution_done): Declare.
	* main.c (captured_command_loop): Don't call
	interp_pre_command_loop if the prompt is blocked.
	(catch_command_errors, catch_command_errors_const): Adjust.
	(captured_main): Set the initial prompt state to PROMPT_NEEDED.
	* mi/mi-interp.c (display_mi_prompt): Set the prompt state to
	PROMPTED.
	(mi_interpreter_resume): Don't clear sync_execution.  Remove hack
	comment.
	(mi_execute_command_input_handler): Set the prompt state to
	PROMPT_NEEDED before executing the command, and only display the
	prompt if the prompt state is PROMPT_NEEDED afterwards.
	(mi_on_resume_1): Adjust to check the prompt state.
	* target.c (target_terminal_inferior): Adjust to check the prompt
	state.
	* top.c (wait_sync_command_done, maybe_wait_sync_command_done)
	(execute_command): Check the current UI's prompt state instead of
	sync_execution.
	* top.h (enum prompt_state): New.
	(struct ui) <prompt_state>: New field.
	(ALL_UIS): New macro.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix for spurious prompts in secondary UIs
@ 2016-06-21 14:06 sergiodj+buildbot
  2016-06-21 20:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8836c9358a11055a08d11ecacc5d7c8f6d5e7a8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a8836c9358a11055a08d11ecacc5d7c8f6d5e7a8

Fix for spurious prompts in secondary UIs

Running mi-break.exp with MI on a secondary UI reveals that MI emits
spurious prompts compared MI running as primary UI:

   -exec-continue
   ^running
   *running,thread-id="all"
   (gdb)
   =breakpoint-modified,bkpt={number="9",type="breakpoint",disp="keep",enabled="y",func="callee2",line="39",script={"set $i=0","while $i<10","print $i","set $i=$i+1","end","continue"}}
   ~"\n"
   ~"Breakpoint 9, callee2 (intarg=2, strarg=0x400730 \"A string argument.\") at ...src/gdb/testsuite/gdb.mi/basics.c:39\n"
   ~"39\t  callee3 (strarg);\n"
   *stopped,reason="breakpoint-hit",disp="keep",bkptno="9",frame={addr="0x00000000004005dd",func="callee2",...
   *running,thread-id="all"
>> (gdb)
   =breakpoint-modified,bkpt={number="9",...
   ~"\n"
   ~"Breakpoint 9, callee2 (intarg=2, strarg=0x400730 \"A string argument.\") at ...src/gdb/testsuite/gdb.mi/basics.c:39\n"
   ~"39\t  callee3 (strarg);\n"
   *stopped,reason="breakpoint-hit",disp="keep",bkptno="9",...
   *running,thread-id="all"
   ~"[Inferior 1 (process 12639) exited normally]\n"
   =thread-exited,id="1",group-id="i1"
   =thread-group-exited,id="i1",exit-code="0"
   *stopped,reason="exited-normally"
   FAIL: gdb.mi/mi-break.exp: intermediate stop and continue
   FAIL: gdb.mi/mi-break.exp: test hitting breakpoint with commands (timeout)

Note the line marked >> above.

The test sets a breakpoint that runs "continue", a foreground command.
When we get to run the "continue", we've already emitted the *stopped
event on the MI UI, and set its prompt state to PROMPT_NEEDED (this is
done from within normal_stop).  Since inferior events are always
handled with the main UI as current UI, breakpoint commands always run
with the main UI as current UI too.  This means that the "continue"
ends up always disabling the prompt on the main UI, instead of the UI
that had just been done with synchronous execution.

I think we'll want to extend this with a concept of "set of
threads/inferiors a UI/interpreter is blocked waiting on", but I'm
leaving that for a separate series.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* infcmd.c (prepare_execution_command): Use
	all_uis_on_sync_execution_starting.
	* infrun.c (all_uis_on_sync_execution_starting): New function.
	* infrun.h (all_uis_on_sync_execution_starting): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] New function should_print_stop_to_console
@ 2016-06-21 14:53 sergiodj+buildbot
  2016-06-21 21:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 14:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26cde2cc30c25ba4d5666ea502db51ee6cb5b069 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 26cde2cc30c25ba4d5666ea502db51ee6cb5b069

New function should_print_stop_to_console

There's code in the MI interpreter that decides whether a stop should
be sent to MI's console stream.  Move this check to the CLI
interpreter code, so that we can reuse it in both the CLI and TUI
interpreters.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c: Include gdbthread.h and thread-fsm.h.
	(should_print_stop_to_console): New function, factored out from
	mi_on_normal_stop_1.
	* cli/cli-interp.h (should_print_stop_to_console): Declare.
	* mi/mi-interp.c (mi_on_normal_stop_1): Use
	should_print_stop_to_console.  Pass it the current UI's console
	interpreter.
	* mi/mi-main.c (captured_mi_execute_command): Use the
	INTERP_CONSOLE symbol rather than explicit "console".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce display_mi_prompt
@ 2016-06-21 16:17 sergiodj+buildbot
  2016-06-21 15:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 16:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 05beb2750cd51a0ae1e8bb429aacda567acceba4 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 05beb2750cd51a0ae1e8bb429aacda567acceba4

Introduce display_mi_prompt

Just a refactor.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* mi/mi-interp.c (display_mi_prompt): New function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Only send sync execution command output to the UI that ran the command
@ 2016-06-21 16:21 sergiodj+buildbot
  2016-06-21 23:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 16:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eaae60fd9421cd055c88584bf783942888b8c68e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: eaae60fd9421cd055c88584bf783942888b8c68e

Only send sync execution command output to the UI that ran the command

Currently when a "step", "next", etc. finishes, the current source
line is printed on all console UIs.

This patch makes the CLI and TUI interpreters reuse MI's logic to only
emit console output related to a synchronous command on the
console-like interpreter that started the command in the first place.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c (cli_on_normal_stop): Bail out early if there's
	nothing to print.  Use should_print_stop_to_console.
	* tui/tui-interp.c (tui_on_normal_stop): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make main_ui be heap allocated
@ 2016-06-21 16:33 sergiodj+buildbot
  2016-06-22  1:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 16:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98d9f24ed15c5ca33bff06647d87b85e22e586d2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 98d9f24ed15c5ca33bff06647d87b85e22e586d2

Make main_ui be heap allocated

This is preparation for being able to create more than one UI object.

The change to gdb_main to stop using catch_errors is necessary because
catch_errors references current_uiout, which expands to
current_ui->m_current_ui, which would crash because current_ui is not
initialized yet at that point.  It didn't trigger earlier in the
series because before this patch, main_ui/current_ui always start out
non-NULL.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (main_ui_): Delete.
	(main_ui, current_ui, ui_list): No longer initialize here.
	* main.c (captured_main): UI initialization code factored out to
	new new_ui function.
	(gdb_main): Wrap captured_main with TRY/CATCH instead of
	catch_errors.
	* top.c (highest_ui_num): New global.
	(new_ui): New function.
	* top.h (struct ui) <num>: New field.
	(new_ui): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Handle UI's terminal closing
@ 2016-06-21 17:20 sergiodj+buildbot
  2016-06-22  3:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07169ff772077f566c6540f623d7d609babc4c81 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 07169ff772077f566c6540f623d7d609babc4c81

Handle UI's terminal closing

Without this, GDB exits if a secondary UIs terminal/input stream is
closed:

 $ ./gdb -ex "new-ui mi /dev/pts/6"
 New UI allocated
	 <<< close /dev/pts/6
 (gdb) Error detected on fd 9
 $

We want that for the main UI, but not secondary UIs.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* event-top.c (stdin_event_handler): Don't quit gdb if it was a
	secondary UI's input stream that closed.  Instead, just delete the
	UI.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make stdin be per UI
@ 2016-06-21 18:04 sergiodj+buildbot
  2016-06-22  6:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 268a799a454ce862f516ff2215290fae08eca7fa ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 268a799a454ce862f516ff2215290fae08eca7fa

Make stdin be per UI

This commit makes each UI have its own "stdin" stream pointer.  This
is used to determine whether the "from_tty" argument to
execute_command, etc. should be true.

Related, this commit makes input_from_terminal_p take an UI parameter,
and then avoids the gdb_has_a_terminal in it.  gdb_has_a_terminal only
returns info on gdb's own main/primary terminal (the real stdin).
However, the places that call input_from_terminal_p really want to
know is whether the command came from an interactive tty.  This patch
thus renames input_from_terminal_p to input_interactive_p for clarity,
and then makes input_interactive_p check for "set interactive" itself,
along with ISATTY, instead of calling gdb_has_a_terminal.  Actually,
quit_force wants to call input_interactive_p _after_ stdin is closed,
we can't call ISATTY that late.  So instead we save the result of
ISATTY in a field of the UI.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* cli/cli-script.c (read_next_line): Adjust to per-UI stdin.
	(read_command_lines): Use input_interactive_p instead of
	input_from_terminal_p.
	* defs.h (struct ui): Forward declare.
	(input_from_terminal_p): Rename to ...
	(input_interactive_p): ... this.
	* event-top.c (stdin_event_handler): Pass 0 as from_tty argument
	to quit_command.
	(command_handler): Adjust to per-UI stdin.
	(handle_line_of_input): Adjust to per-UI stdin and use
	input_interactive_p instead of ISATTY and input_from_terminal_p.
	(gdb_readline_no_editing_callback): Adjust to per-UI stdin.
	(command_line_handler): Always pass true as "from_tty" parameter
	of handle_line_of_input and execute_command.
	(async_sigterm_handler): Pass 0 as from_tty argument to
	quit_command.
	* inflow.c (interactive_mode, show_interactive_mode): Moved to ...
	(gdb_has_a_terminal): Don't check interactive_mode here.
	(_initialize_inflow): Don't install "set interactive-mode" here.
	* main.c (captured_command_loop): Adjust to per-UI stdin.
	* mi/mi-interp.c (mi_execute_command_wrapper): Adjust to per-UI
	stdin.
	* top.c (new_ui): Save the stdin stream and whether it's a tty.
	(dont_repeat): Adjust to per-UI stdin.
	(command_line_input): Adjust to per-UI stdin and to use
	input_interactive_p.
	(quit_force): Write history if any UI supports interactive input.
	(interactive_mode, show_interactive_mode): Move here, from
	inflow.c.
	(input_from_terminal_p): Rename to ...
	(input_interactive_p): ... this, and check the "interactive_mode"
	global instead of calling gdb_has_a_terminal.
	(_initialize_top): Install "set interactive-mode" here.
	* top.h (struct ui) <stdin_stream, input_interactive_p>: New
	fields.
	* utils.c (quit): Pass 0 as from_tty argument to quit_force.
	(defaulted_query): Adjust to per-UI stdin and to use
	input_interactive_p.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add new command to create extra console/mi UIs
@ 2016-06-21 18:51 sergiodj+buildbot
  2016-06-22  9:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 18:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60eb5395fa7a7b8e3cd1841e38b6d1a0c16be0d0 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 60eb5395fa7a7b8e3cd1841e38b6d1a0c16be0d0

Add new command to create extra console/mi UIs

With all the previous plumbing in place, it's now easy to add a
command that actually creates a new console/mi UI.

The intended use case is to make it possible and easy for MI frontends
to provide a fully featured GDB console to users, with readline
support, command line editing, history, etc., just like if gdb was
started on the command line.  Currently MI frontends have to try to
implement all of that theirselves and make use of "-interpreter-exec
console ...", which is far from perfect.  If you ever tried Eclipse's
gdb console window, you'll know what I mean...

Instead of trying to multiplex console through MI, this command let's
just leverage all the built in readline/editing support already inside
gdb.

The plan is for the MI frontend to start GDB in regular console mode,
running inside a terminal emulator widget embedded in Eclipse (which
already exists, for supporting the shell widget; other frontends have
similar widgets), and then tell GDB to run a full MI interpreter on an
specified input/output device, independent of the console.

My original prototype planned to do things the other way around --
start GDB in MI mode, and then start an extra CLI console on separate
tty.  I handed over that prototype to Marc Khouzam @ Eclipse CDT, and
after experimentation and discussion, we ended up concluding that
starting GDB in CLI mode instead was both easier and actually also
supported an interesting use case -- connect an Eclipse frontend to a
GDB that is already running outside Eclipse.

The current usage is "new-ui <interpreter> <tty>".

E.g., on a terminal run this scriplet:

 $ cat gdb-client
 #!/bin/bash

 reset
 tty
 tail -f /dev/null

 $ gdb-client
 /dev/pts/15

Now run gdb on another terminal, and tell it to start a MI interpreter
on the tty of the other terminal:

 ...
 (gdb) new-ui mi /dev/pts/15
 New UI allocated

Now back to the the gdb-client terminal, we'll get an MI prompt, ready
for MI input:

 /dev/pts/15
 =thread-group-added,id="i1"
 (gdb)

You can also start a new UI running a CLI, with:

 (gdb) new-ui console /dev/pts/15

Though note that this console won't support readline command editing.
It works as if "set editing off" was entered.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* interps.c (set_top_level_interpreter): New function, factored
	out from captured_main.
	(interpreter_completer): Make extern.
	* interps.h (set_top_level_interpreter, interpreter_completer):
	New declarations.
	(captured_main): Use set_top_level_interpreter.
	* top.c [!O_NOCTTY] (O_NOCTTY): Define as 0.
	(open_terminal_stream, new_ui_command): New functions.
	(init_main): Install the "new-ui" command.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [DOC] Document support for running interpreters on separate UIs
@ 2016-06-21 19:51 sergiodj+buildbot
  2016-06-22 12:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86f78169c82095eced3a4d1b30f8e002ec841d79 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 86f78169c82095eced3a4d1b30f8e002ec841d79

[DOC] Document support for running interpreters on separate UIs

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention support for running interpreters on separate
	UIs and the new new-ui command.

gdb/doc/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Interpreters): Update intepreter-exec section,
	document new-ui and explain use case.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add testing infrastruture bits for running with MI on a separate UI
@ 2016-06-21 21:17 sergiodj+buildbot
  2016-06-22 13:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 21:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51f77c3704a6e5c28fdcdd6d6e0aeb97ebdb343f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 51f77c3704a6e5c28fdcdd6d6e0aeb97ebdb343f

Add testing infrastruture bits for running with MI on a separate UI

With this, a specific test may can start GDB with MI on a separate UI
by using:

  mi_gdb_start separate-mi-tty

In addition, it's also possible to run the whole testsuite with MI on
a separate tty, with:

 make check RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1"

gdb_main_spawn_id and mi_spawn_id are added so that tests may expect
output from either channel.

While at it, inferior_spawn_id was not being cleared when gdb exits,
unlike the other spawn ids, thus a test that starts gdb more than once
would end up using a stale spawn id.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* README (Testsuite Parameters): Document FORCE_SEPARATE_MI_TTY.
	* lib/gdb.exp (default_gdb_exit): Clear inferior_spawn_id.
	* lib/mi-support.exp (mi_uncatched_gdb_exit): Unset
	gdb_main_spawn_id, mi_spawn_id, unset inferior_spawn_id.
	(gdb_main_spawn_id, mi_spawn_id): Declare and
	comment.
	(mi_create_inferior_pty): New procedure,
	factored out from default_mi_gdb_start.
	(switch_gdb_spawn_id, mi_gdb_start_separate_mi_tty): New
	procedures.
	(default_mi_gdb_start): Call mi_gdb_start_separate_mi_tty if the
	separate-mi-tty option is specified, or SEPARATE_MI_TTY is set.
	Use mi_create_inferior_pty.
	(mi_gdb_start): Use eval to pass down args list.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make mi-break.exp always expect breakpoint commands output on the main UI
@ 2016-06-21 21:40 sergiodj+buildbot
  2016-06-22 18:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef274d26b57336b3baa5bb0ae93b49178bc45631 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ef274d26b57336b3baa5bb0ae93b49178bc45631

Make mi-break.exp always expect breakpoint commands output on the main UI

mi-break.exp regresses when tested with MI running on a secondary UI,
with RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1".

The problem is simply that the test sets a breakpoint, and attaches
"print" commands to the breakpoint.  Since breakpoint commands always
run with the main UI as current UI, the breakpoint command's output
goes to the main UI.  So we need to tweak the test to expect it there.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-break.exp (test_breakpoint_commands): Always expect
	breakpoint command's output on the main UI.
	(test_break): New procedure, factored out from calls in the top
	level.
	(top level): Use foreach_with_prefix to test MI as main UI and as
	separate UI.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Always switch fork child to the main UI
@ 2016-06-21 22:18 sergiodj+buildbot
  2016-06-22 21:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 22:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49940788ab38b9d58c663cf38855f29c0ebb1b55 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 49940788ab38b9d58c663cf38855f29c0ebb1b55

Always switch fork child to the main UI

The following scenario:

 - gdb started in normal CLI mode.

 - separate MI channel created with new-ui

 - inferior output redirected with the "set inferior-tty" command.

 - use -exec-run in the MI channel to run the inferior

is presently mishandled.

When we create the inferior, in fork-child.c, right after vfork, we'll
close all the file descriptors in the vfork child, and then dup the
tty to file descriptors 0/1/2, create a session, etc.  Note that when
we close all descriptors, we close the file descriptors behind
gdb_stdin/gdb_stdout/gdb_stderr of all secondary UIs...  So if
anything goes wrong in the child and it calls warning/error, it'll end
up writting to the current UI's stdout/stderr streams, which are
backed by file descriptors that have since been closed.  Because this
happens in a vfork region, the corresponding stdin/stdout/stderr in
the parent/gdb end up corrupted.

The fix is to switch to the main UI right after the vfork, so that
gdb_stdin/gdb_stdout/gdb_stderr are correctly mapped to
stdin/stdout/stderr (and thus to file descriptors 0/1/2), so this code
works as it has always worked.

(Technically, we're doing a lot of stuff we shouldn't be doing after a
vfork, while we should only be calling async-signal-safe functions.)

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* fork-child.c (fork_inferior): Switch the child to the main UI
	right after vfork.  Save/restore the current UI in the parent.
	Flush outputs of the main UI instead of the current UI.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-exec-run.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add "new-ui console" tests
@ 2016-06-21 23:24 sergiodj+buildbot
  2016-06-22 22:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac69f7863a6b5dbd1792356275de437371b8c879 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ac69f7863a6b5dbd1792356275de437371b8c879

Add "new-ui console" tests

This adds a test that uses new-ui to create a secondary console, and
then runs some basic smoke tests.  It ensures that:

 - synchronous commands send output to the UI that initiated it

 - asynchronous events like breakpoint hits are reported on all
   consoles.

 - "new-ui" without arguments doesn't crash.

 - The "new-ui" command doesn't repeat.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.base/new-ui.exp: New file.
	* lib/mi-support.exp (switch_gdb_spawn_id): Move to ...
	* lib/gdb.exp (switch_gdb_spawn_id): ... here.
	(with_spawn_id): New procedure.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S390: Fix typo "s930" -> "s390"
@ 2016-06-22  1:37 sergiodj+buildbot
  2016-06-22 23:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22  1:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34a60ddbad3b76d8f327250527cf4915839943d7 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 34a60ddbad3b76d8f327250527cf4915839943d7

S390: Fix typo "s930" -> "s390"

This fixes a typo in the name of the "last-break" regset.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_iterate_over_regset_sections): Fix typo
	in name of last-break regset.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Arc assembler: Convert nps400 from a machine type to an extension.
@ 2016-06-22  3:18 sergiodj+buildbot
  2016-06-23  3:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22  3:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdd582dbf14f12998a0003b5aa772d7868bc3dc7 ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: bdd582dbf14f12998a0003b5aa772d7868bc3dc7

Arc assembler: Convert nps400 from a machine type to an extension.

gas	* config/tc-arc.c (check_cpu_feature, md_parse_option):
	Add nps400 option and feature. Add check for nps400
	feature. Refactor existing checks to check subclass before
	feature enablement.
	(md_show_usage): Document flags for NPS-400 and add some other
	undocumented flags.
	(cpu_type): Remove nps400 CPU type entry
	(check_zol): Remove bfd_mach_arc_nps400 case.
	(md_show_usage): Add help on -mcpu=nps400.
	(cpu_types): Add entry for nps400 as arc700 plus nps400 extension
	set.
	* doc/c-arc.texi: Document the -mnps400, -mspfp, -mdpfp, and
	-fpuda flags.  Document -mcpu=nps400.
	* testsuite/gas/arc/nps-400-0.d: Use -mcpu=arc700 -mnps400. Change
	expected flags to match ARC700 instead of NPS400.
	* testsuite/gas/arc/nps-400-1.d: Use -mcpu=arc700 -mnps400.
	* testsuite/gas/arc/nps-400-2.d: Likewise.
	* testsuite/gas/arc/nps-400-3.d: Likewise.
	* testsuite/gas/arc/nps-400-4.d: Likewise.
	* testsuite/gas/arc/nps-400-5.d: Likewise.
	* testsuite/gas/arc/nps-400-6.d: Likewise.
	* testsuite/gas/arc/nps-400-7.d: Likewise.
	* testsuite/gas/arc/textinsn2op01.s: Change opcode of myinsn to
	avoid clash with cbba instruction.
	* testsuite/gas/arc/textinsn2op01.d: Likewise.
	* testsuite/gas/arc/textinsn3op.d: Likewise.
	* testsuite/gas/arc/textinsn3op.s: Likewise.
	* testsuite/gas/arc/nps-400-0.d: Test using NPS-400 using
	-mcpu=nps400 as an alternative to -mcpu=arc700 -mnps400 flags.

binutils* readelf.c (decode_ARC_machine_flags): Remove E_ARC_MACH_NPS400
	case.

ld	* testsuite/ld-arc/nps-1a.d: Use -mcpu=arc700 -mnps400.
	* testsuite/ld-arc/nps-1b.d: Likewise.

include	* opcode/arc.h: Add nps400 extension and instruction
	subclass.
	Remove ARC_OPCODE_NPS400
	* elf/arc.h: Remove E_ARC_MACH_NPS400

opcodes	* arc-dis.c (arc_insn_length): Add comment on instruction length.
	Use same method for determining	instruction length on ARC700 and
	NPS-400.
	(arc_insn_length, print_insn_arc): Remove bfd_mach_arc_nps400.
	* arc-nps400-tbl.h: Make all nps400 instructions ARC700 instructions
	with the NPS400 subclass.
	* arc-opc.c: Likewise.

bfd	* archures.c: Remove bfd_mach_arc_nps400.
	* bfd-in2.h: Likewise.
	* cpu-arc.c (arch_info_struct): Likewise.
	* elf32-arc.c (arc_elf_object_p, arc_elf_final_write_processing):
	Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tilegx: move TILEGX_NUM_PIPELINE_ENCODINGS to tilegx_pipeline enum
@ 2016-06-22  9:22 sergiodj+buildbot
  2016-06-23  9:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22  9:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6edaf4d75b45ff08d7296095506904663b8f0576 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 6edaf4d75b45ff08d7296095506904663b8f0576

tilegx: move TILEGX_NUM_PIPELINE_ENCODINGS to tilegx_pipeline enum

Its closely related to what the encodings are, more than a set of random
constants, so it seems to make sense to put it here.

include/ChangeLog:

2016-06-22  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/tilegx.h: Move TILEGX_NUM_PIPELINE_ENCODINGS into
	tilegx_pipeline.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Send deleted watchpoint-scope output to all UIs
@ 2016-06-22 11:03 sergiodj+buildbot
  2016-06-22 17:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 468afe6c5fc9c80b8c175f3f13702ffaa6308400 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 468afe6c5fc9c80b8c175f3f13702ffaa6308400

Send deleted watchpoint-scope output to all UIs

Testing with:

  make check RUNTESTFLAGS="SEPARATE_MI_TTY=1"

shows this, in gdb.mi/mi-watch.exp:

 -*stopped,reason="watchpoint-scope",wpnum="2",frame={addr="0x00000000004005cb",
 +*stopped,frame={addr="0x00000000004005cb",
 (...)
 -PASS: gdb.mi/mi-watch.exp: hw: watchpoint trigger
 +FAIL: gdb.mi/mi-watch.exp: hw: watchpoint trigger (unknown output after running)

That is, we lose the "watchpoint-scope" output on the MI UI.

This commit fixes it, and makes the test run with MI running as both
main UI and separate UI.

gdb/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (watchpoint_check): Send watchpoint-deleted output
	to all UIs.

gdb/testsuite/ChangeLog:
2016-06-21  Pedro Alves  <palves@redhat.com>

	* gdb.mi/mi-watch.exp (test_watchpoint_creation_and_listing)
	(test_awatch_creation_and_listing)
	(test_rwatch_creation_and_listing, test_watchpoint_triggering):
	Remove 'type' parameter.
	(test_watchpoint_all): New parameter mi_mode.  Remove
	with_test_prefix.
	(top level): Use foreach_with_prefix, and add main/separate UI MI
	testing axis.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S390 gdbserver: Mark local funcs/vars as static
@ 2016-06-22 16:52 sergiodj+buildbot
  2016-06-23  1:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 782c112285467b906296b020f8fce3fb76cc5bb5 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 782c112285467b906296b020f8fce3fb76cc5bb5

S390 gdbserver: Mark local funcs/vars as static

Compiling with '-Wmissing-declarations' yields warnings in
linux-s390-low.c.  To fix this, mark appropriate functions as static.

gdb/gdbserver/ChangeLog:

	* linux-s390-low.c (s390_emit_eq_goto): Mark function static.
	(s390_emit_ne_goto): Likewise.
	(s390_emit_lt_goto): Likewise.
	(s390_emit_le_goto): Likewise.
	(s390_emit_gt_goto): Likewise.
	(s390_emit_ge_goto): Likewise.
	(s390x_emit_eq_goto): Likewise.
	(s390x_emit_ne_goto): Likewise.
	(s390x_emit_lt_goto): Likewise.
	(s390x_emit_le_goto): Likewise.
	(s390x_emit_gt_goto): Likewise.
	(s390x_emit_ge_goto): Likewise.
	(s390_emit_ops_impl): Mark variable static.
	(s390x_emit_ops): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] addmore extern C
@ 2016-06-22 17:38 sergiodj+buildbot
  2016-06-23 12:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 17:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b4778968b298715ba78208bf047d72243961d49 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 6b4778968b298715ba78208bf047d72243961d49

addmore extern C

opcodes/ChangeLog:

2016-06-22  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* arc-ext.h: Wrap in extern C.

include/ChangeLog:

2016-06-22  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf/dlx.h: Wrap in extern C.
	* elf/xtensa.h: Likewise.
	* opcode/arc.h: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Improve user experience in printing Fortran derived types.
@ 2016-06-22 19:19 sergiodj+buildbot
  2016-06-23  5:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 19:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04d59df6f311bcc20d74ada64a5e15a4bbb40026 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 04d59df6f311bcc20d74ada64a5e15a4bbb40026

Improve user experience in printing Fortran derived types.

Output for Fortran derived classes is like:

  "( 9, 'abc')"

with this changes the output is changed to:

  "( lucky_number = 9, letters = 'abc')"

2016-06-21  Walfred Tedeschi  <walfred.tedeschi@intel.com>

	* f-valprint.c (f_val_print): Add field names for printing
	derived types fields.


gdb/testsuite:

	* gdb.fortran/derived-type.exp (print q): Add fields to the output.
	* gdb.fortran/vla-type.exp (print twov): Fix vla tests with
	structs.
	* gdb.fortran/derived-type-function.exp: New file.
	* gdb.fortran/derived-type-function.f90: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for yet some more new ISA 3.0 instructions.
@ 2016-06-22 23:12 sergiodj+buildbot
  2016-06-23 13:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-22 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6fd3a02da5548c71ff469f978444ef6c3af18783 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: 6fd3a02da5548c71ff469f978444ef6c3af18783

Add support for yet some more new ISA 3.0 instructions.

opcodes/
	* ppc-opc.c (RM, DRM, VXASH, VXASH_MASK, XMMF, XMMF_MASK): New defines.
	(powerpc_opcodes) <brd, brh, brw, mffsce, mffscdrn, mffscdrni,
	mffscrn, mffscrni, mffsl, nandxor, rldixor, setbool,
	xor3>: New mnemonics.
	<setb>: Change to a VX form instruction.
	(insert_sh6): Add support for rldixor.
	(extract_sh6): Likewise.

gas/
	* testsuite/gas/ppc/power9.d <brd, brh, brw, mffs, mffs., mffsce,
	mffscdrn, mffscdrni, mffscrn, mffscrni, mffsl, nandxor, rldixor,
	setbool, xor3>: New tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Misc minor edits/fixes
@ 2016-06-23  9:16 sergiodj+buildbot
  2016-06-23 14:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-23  9:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce440d638d271d76cc491bd22dc34f6a5760140e ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: ce440d638d271d76cc491bd22dc34f6a5760140e

[ARC] Misc minor edits/fixes

The code supporting -mspfp, -mdpfp, and -mfpuda options are in
sections of code that are commented as being for backward
compatibility only, and having no effect. However, they do have an
effect, enabling the SPX, DPX, and DPA instruction subclasses
respectively. This commit moves the code supporting these options
away from the comments indicating that they are dummy options, and
also fixes a small issue where -mnps400 had the additional effect
of enabling SPX instructions.

A couple of other minor edits (that make no functional change) are
also included.

gas/ChangeLog:

        * config/tc-arc.c (options, md_longopts, md_parse_option):
        Move -mspfp, -mdpfp and -mfpuda out of the sections for
        dummy options. Correct erroneous enabling of SPFP
        instructions when using -mnps400.

include/ChangeLog:

        * opcode/arc.h: Make insn_class_t alphabetical again.

opcodes/ChangeLog:

        * arc-opc.c: Correct description of availability of NPS400
        features.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR gdb/16483 - simplify "info frame-filters" output
@ 2016-06-23 14:21 sergiodj+buildbot
  2016-06-23 15:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-23 14:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17621150cc18737f0a80314cfd2f884b0c2e44b5 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 17621150cc18737f0a80314cfd2f884b0c2e44b5

PR gdb/16483 - simplify "info frame-filters" output

PR gdb/16483 notes that the output of "info frame-filters" is quite
voluminous.  In particular it prints an entry for each objfile, even if
only to say that the objfile does not have any associated frame filters.

I think it's better to only print output when there is a frame filter.
There's nothing worth doing with the no-frame-filter information, and
limiting the output makes it much more readable.

Built and regtested on x86-64 Fedora 23.

2016-06-23  Tom Tromey  <tom@tromey.com>

	PR gdb/16483:
	* python/lib/gdb/command/frame_filters.py
	(InfoFrameFilter.list_frame_filters): Rename to print_list.  Print
	nothing if no filters found.  Return value indicating whether
	filters were printed.
	(InfoFrameFilter.print_list): Remove.
	(InfoFrameFilter.invoke): Print message if no frame filters
	found.

2016-06-23  Tom Tromey  <tom@tromey.com>

	PR gdb/16483:
	* gdb.python/py-framefilter.exp: Add "info frame-filter" test
	before any filters are loaded.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdbpy_parameter static
@ 2016-06-24  3:10 sergiodj+buildbot
  2016-06-24  3:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24  3:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c72ed4ca21e7a9f78f19179584f3886bf463689 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0c72ed4ca21e7a9f78f19179584f3886bf463689

Make gdbpy_parameter static

While working on the next patch in this series, I noticed that
gdbpy_parameter did not need to be exported.  This makes it "static".

2016-06-23  Tom Tromey  <tom@tromey.com>

	* python/python.c (gdbpy_parameter): Now static.
	* python/python-internal.h (gdbpy_parameter): Don't declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use VEC for filename_language_table
@ 2016-06-24  3:40 sergiodj+buildbot
  2016-06-24  4:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24  3:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fcf0b0d5a8cf04da4b4210121e7276ca1f20101 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 3fcf0b0d5a8cf04da4b4210121e7276ca1f20101

Use VEC for filename_language_table

This patch changes filename_language_table to be a VEC.  This seemed
like a reasonable cleanup over the old code.

2016-06-23  Tom Tromey  <tom@tromey.com>

	* symfile.c (filename_language_table): Now a VEC.
	(fl_table_size, fl_table_next): Remove.
	(add_filename_language): Use VEC_safe_push.
	(set_ext_lang_command, info_ext_lang_command)
	(deduce_language_from_filename): Use VEC_iterate.
	(init_filename_language_table): Use VEC_empty.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Move filename extensions into language_defn
@ 2016-06-24  4:36 sergiodj+buildbot
  2016-06-24  4:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24  4:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56618e20bc50e55b49ed224df2a2a7e0840056fe ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 56618e20bc50e55b49ed224df2a2a7e0840056fe

Move filename extensions into language_defn

This moves filename extensions from a function in symfile.c out to
each language_defn.  I think this is an improvement because it means
less digging around when writing a new language port.

2016-06-23  Tom Tromey  <tom@tromey.com>

	* ada-lang.c (ada_extensions): New array.
	(ada_language_defn): Use it.
	* c-lang.c (c_extensions): New array.
	(c_language_defn): Use it.
	(cplus_extensions): New array.
	(cplus_language_defn): Use it.
	(asm_extensions): New array.
	(asm_language_defn): Use it.
	(minimal_language_defn): Update.
	* d-lang.c (d_extensions): New array.
	(d_language_defn): Use it.
	* f-lang.c (f_extensions): New array.
	(f_language_defn): Use it.
	* go-lang.c (go_language_defn): Update.
	* jv-lang.c (java_extensions): New array.
	(java_language_defn): Use it.
	* language.c (add_language): Call add_filename_language.
	(unknown_language_defn, auto_language_defn, local_language_defn):
	Update.
	* language.h (struct language_defn) <la_filename_extensions>: New
	field.
	* m2-lang.c (m2_language_defn): Update.
	* objc-lang.c (objc_extensions): New array.
	(objc_language_defn): Use it.
	* opencl-lang.c (opencl_language_defn): Update.
	* p-lang.c (p_extensions): New array.
	(pascal_language_defn): Use it.
	* rust-lang.c (rust_extensions): New array.
	(rust_language_defn): Use it.
	* symfile.c (add_filename_language): No longer static.  Make "ext"
	const.
	(init_filename_language_table): Remove.
	(_initialize_symfile): Update.
	* symfile.h (add_filename_language): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS objcopy --rename-section fix
@ 2016-06-24 14:28 sergiodj+buildbot
  2016-06-24 15:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 14:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9cc0123fea25379a1d57b700c078c7a9d0992f61 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9cc0123fea25379a1d57b700c078c7a9d0992f61

MIPS objcopy --rename-section fix

Some MIPS targets use a named section symbol rather than a symbol with
no name as is used with most ELF targets.  When renaming sections, the
named section symbol needs to be renamed too.

Rather than fix this bug, I'd originally intended to just correct the
xfail added recently for update-1.o vs update4.o in update-section.exp,
using the same set of targets for the localize-hidden-1 mips xfail.
I'd extracted that target test into a new function, is_bad_symtab.  It
turns out to be useful in readelf.exp too.

bfd/
	* config.bfd: Delete mips vxworks patterns matched earlier.
	Combine mips*-*-none with mips*-*-elf*.
binutils/
	* objcopy.c (find_section_rename): Forward declare.  Remove
	ibfd and sec_ptr param.  Add old_name param.  Allow for NULL
	returned_flags.  Move read of section name and flags to..
	(setup_section): ..here.  Update find_section_rename call.
	(filter_symbols): Rename section symbols for renamed sections.
	(copy_object): Call filter_symbols when renamed sections.
	* testsuite/lib/binutils-common.exp (is_bad_symtab): New.
	* testsuite/binutils-all/update-section.exp: Revert 96037eb0
	mips xfail.
	* testsuite/binutils-all/objcopy.exp (copy_executable): Use
	is_bad_symtab.
	(localize-hidden-1): xfail if is_bad_symtab.
	* testsuite/binutils-all/readelf.exp: Use is_bad_symtab to select
	between mips/tmips.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] fix undefined reference to bfd_link_plugin_object_p during link
@ 2016-06-24 17:34 sergiodj+buildbot
  2016-06-24 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08ce1d723ea3360a8ae52a4a4bd395ec984563eb ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 08ce1d723ea3360a8ae52a4a4bd395ec984563eb

fix undefined reference to bfd_link_plugin_object_p during link

When configured with the default options, GDB currently fails to link,
due to an undefined reference to bfd_link_plugin_object_p, coming from
elflink.c:

    #ifdef BFD_SUPPORTS_PLUGINS
           || (abfd->plugin_format == bfd_plugin_unknown
              && bfd_link_plugin_object_p (abfd))
    #endif

This is because BFD_SUPPORTS_PLUGINS is always defined. It is its value
that determines whether plugin support is enabled or not.

bfd/ChangeLog:

        * elflink.c: Check the value of BFD_SUPPORTS_PLUGINS rather
        than its existance.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add constants for FreeBSD-specific auxiliary vector entry types.
@ 2016-06-24 18:28 sergiodj+buildbot
  2016-06-24 18:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 18:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b00f86d0720d2cf44f3edb6101682074da1abe5d ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: b00f86d0720d2cf44f3edb6101682074da1abe5d

Add constants for FreeBSD-specific auxiliary vector entry types.

include/ChangeLog:

	* elf/common.h (AT_FREEBSD_EXECPATH, AT_FREEBSD_CANARY)
	(AT_FREEBSD_CANARYLEN, AT_FREEBSD_OSRELDATE, AT_FREEBSD_NCPUS)
	(AT_FREEBSD_PAGESIZES, AT_FREEBSD_PAGESIZESLEN)
	(AT_FREEBSD_TIMEKEEP, AT_FREEBSD_STACKPROT): Define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes.
@ 2016-06-24 18:39 sergiodj+buildbot
  2016-06-24 19:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa1ed4a93a2eb0fb90d274c15288f3aad1791f60 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: aa1ed4a93a2eb0fb90d274c15288f3aad1791f60

Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes.

Move parsing of FreeBSD-specific ELF core notes out of elfcore_grok_note
into a new elfcore_grok_freebsd_note function.  Add core note grok routines
for FreeBSD's psinfo and prstatus notes while here rather than depending
on the native handling in elfcore_grok_note.

bfd/ChangeLog:

	* elf.c (elfcore_grok_note): Remove handling of NT_X86_XSTATE for
	FreeBSD.  Remove case for NT_FREEBSD_THRMISC.
	(elfcore_grok_freebsd_psinfo): New function.
	(elfcore_grok_freebsd_prstatus): New function.
	(elfcore_grok_freebsd_note): New function.
	(elf_parse_notes): Use "elfcore_grok_freebsd_note" for "FreeBSD"
	notes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fetch the ELF auxiliary vector from live processes on FreeBSD.
@ 2016-06-24 19:32 sergiodj+buildbot
  2016-06-24 20:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 19:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7697fc9ec3a970f05abb836107653c46ada466ad ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 7697fc9ec3a970f05abb836107653c46ada466ad

Fetch the ELF auxiliary vector from live processes on FreeBSD.

Use the kern.proc.auxv.<pid> sysctl to fetch the ELF auxiliary vector for
a live process.

gdb/ChangeLog:

	* fbsd-nat.c [KERN_PROC_AUXV] New variable super_xfer_partial.
	(fbsd_xfer_partial): New function.
	(fbsd_nat_add_target) [KERN_PROC_AUXV] Set "to_xfer_partial" to
	"fbsd_xfer_partial".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Create a pseudo section for the ELF AUXV core dump note on FreeBSD.
@ 2016-06-24 20:19 sergiodj+buildbot
  2016-06-24 21:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3350c5f5de3d2e62dd9de2a76cf2d5d8728d2600 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 3350c5f5de3d2e62dd9de2a76cf2d5d8728d2600

Create a pseudo section for the ELF AUXV core dump note on FreeBSD.

The procstat AUXV core dump note in FreeBSD consists of 32-bit integer
followed by an array of auxiliary vector entries.

bfd/ChangeLog:

	* elf.c (elfcore_grok_freebsd_note): Handle NT_FREEBSD_PROCSTAT_AUXV
	notes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add a new gdbarch method to print a single AUXV entry.
@ 2016-06-24 20:57 sergiodj+buildbot
  2016-06-24 22:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2faa34476d9e6120eaf389b7f91b7227183fa2ce ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 2faa34476d9e6120eaf389b7f91b7227183fa2ce

Add a new gdbarch method to print a single AUXV entry.

Different platforms have different meanings for auxiliary vector
entries.  The 'print_auxv_entry' gdbarch method allows an architecture
to output a suitable description for platform-specific entries.

A fprint_auxv_entry function is split out of fprint_target_auxv.
This function outputs the description of a single auxiliary vector
entry to the specified file using caller-supplied formatting and
strings to describe the vector type.

The existing switch on auxiliary vector types is moved out of
fprint_target_auxv into a new default_print_auxv_entry function.
default_print_auxv_entry chooses an appropriate format and description
and calls fprint_single_auxv to describe a single vector entry.
This function is used as the default 'print_auxv_entry' gdbarch method.

fprint_target_auxv now invokes the gdbarch 'print_auxv_entry' method
on each vector entry.

gdb/ChangeLog:

	* auxv.c (fprint_auxv_entry): New function.
	(default_print_auxv_entry): New function.
	(fprint_target_auxv): Use gdbarch_print_auxv_entry.
	* auxv.h (enum auxv_format): New enum.
	(fprint_auxv_entry): Declare.
	(default_print_auxv_entry): Declare.
	* gdbarch.sh (print_auxv_entry): New.
	* gdbarch.c, gdbarch.h: Re-generated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for catching system calls to native FreeBSD targets.
@ 2016-06-24 22:12 sergiodj+buildbot
  2016-06-25  0:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 22:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6cdd38e8f0fead14cd3c528e9a4b666e1871752 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: e6cdd38e8f0fead14cd3c528e9a4b666e1871752

Add support for catching system calls to native FreeBSD targets.

All platforms on FreeBSD use a shared system call table, so use a
single XML file to describe the system calls available on each FreeBSD
platform.

Recent versions of FreeBSD include the identifier of the current
system call when reporting a system call entry or exit event in the
ptrace_lwpinfo structure obtained via PT_LWPINFO in fbsd_wait.  As
such, FreeBSD native targets do not use the gdbarch method to fetch
the system call code.  In addition, FreeBSD register sets fetched via
ptrace do not include an equivalent of 'orig_rax' (on amd64 for
example), so the system call code cannot be extracted from the
available registers during a system call exit.  However, GDB assumes
that system call catch points are not supported if the gdbarch method
is not present.  As a workaround, FreeBSD ABIs install a dummy gdbarch
method that throws an internal_error if it is ever invoked.

gdb/ChangeLog:

	* configure.ac: Check for support for system call LWP fields on
	FreeBSD.
	* config.in, configure: Rebuild.
	* data-directory/Makefile.in (SYSCALLS_FILES): Add freebsd.xml.
	* fbsd-nat.c (fbsd_wait) [HAVE_STRUCT_PTRACE_LWPINFO_PL_SYSCALL_CODE]:
	Report system call events.
	[HAVE_STRUCT_PTRACE_LWPINFO_PL_SYSCALL_CODE]
	(fbsd_set_syscall_catchpoint): New function.
	(fbsd_nat_add_target) [HAVE_STRUCT_PTRACE_LWPINFO_PL_SYSCALL_CODE]:
	Set "to_set_syscall_catchpoint" to "fbsd_set_syscall_catchpoint".
	* fbsd-tdep.c: Include xml-syscall.h
	(fbsd_get_syscall_number): New function.
	(fbsd_init_abi): Set XML system call file name.
	Add "get_syscall_number" gdbarch method.
	* syscalls/freebsd.xml: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add myself as a Write After Approval maintainer.
@ 2016-06-24 22:59 sergiodj+buildbot
  2016-06-25  1:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 22:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2907f41490b2b5602f47c5acdf9ad7ae94eaeff9 ***

Author: David Taylor <david.taylor@emc.com>
Branch: master
Commit: 2907f41490b2b5602f47c5acdf9ad7ae94eaeff9

Add myself as a Write After Approval maintainer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add a gdbarch 'print_auxv_entry' method for FreeBSD ABIs.
@ 2016-06-24 22:59 sergiodj+buildbot
  2016-06-24 23:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-24 22:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82372b2f2747d347e24bb10ddc7bc7e828222a42 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 82372b2f2747d347e24bb10ddc7bc7e828222a42

Add a gdbarch 'print_auxv_entry' method for FreeBSD ABIs.

Add a 'print_auxv_entry' method for FreeBSD ABIs that parses
FreeBSD-specific auxiliary vector entries and outputs a suitable
description using fprint_auxv_entry.

gdb/ChangeLog:

	* fbsd-tdep.c: Include "auxv.h".
	(fbsd_print_auxv_entry): New function.
	(fbsd_init_abi): Install gdbarch "print_auxv_entry" method.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support structure offsets that are 512K or larger.
@ 2016-06-25  1:36 sergiodj+buildbot
  2016-06-25  1:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-25  1:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b8505468e64c2be8d0eea1f2b8db86fa3897600 ***

Author: David Taylor <dtaylor@emc.com>
Branch: master
Commit: 6b8505468e64c2be8d0eea1f2b8db86fa3897600

Support structure offsets that are 512K or larger.

GDB computes structure byte offsets using a 32 bit integer.  And,
first it computes the offset in bits and then converts to bytes.  The
result is that any offset that if 512K bytes or larger overflows.
This patch changes GDB to use LONGEST for such calculations.

	PR gdb/17520 Structure offset wrong when 1/4 GB or greater.
	* c-lang.h: Change all parameters, variables, and struct or union
	members used as struct or union fie3ld offsets from int to
	LONGEST.
	* c-valprint.c: Likewise.
	* cp-abi.c: Likewise.
	* cp-abi.h: Likewise.
	* cp-valprint.c: Likewise.
	* d-valprint.c: Likewise.
	* dwarf2loc.c: Likewise.
	* eval.c: Likewise.
	* extension-priv.h: Likewise.
	* extension.c: Likewise.
	* extension.h: Likewise.
	* findvar.c: Likewise.
	* gdbtypes.h: Likewise.
	* gnu-v2-abi.c: Likewise.
	* gnu-v3-abi.c: Likewise.
	* go-valprint.c: Likewise.
	* guile/guile-internal.h: Likewise.
	* guile/scm-pretty-print.c: Likewise.
	* jv-valprint.c Likewise.
	* opencl-lang.c: Likewise.
	* p-lang.h: Likewise.
	* python/py-prettyprint.c: Likewise.
	* python/python-internal.h: Likewise.
	* spu-tdep.c: Likewise.
	* typeprint.c: Likewise.
	* valarith.c: Likewise.
	* valops.c: Likewise.
	* valprint.c: Likewise.
	* valprint.h: Likewise.
	* value.c: Likewise.
	* value.h: Likewise.
	* p-valprint.c: Likewise.
	* c-typeprint.c (c_type_print_base): When printing offset, use
	plongest, not %d.
	* gdbtypes.c (recursive_dump_type): Ditto.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make evaluation and type-printing of all NonZero optimized enums work
@ 2016-06-25  6:25 sergiodj+buildbot
  2016-06-25  6:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-25  6:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5a4b3c5e711be9096423f9765623eda449d8f4d ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: b5a4b3c5e711be9096423f9765623eda449d8f4d

Make evaluation and type-printing of all NonZero optimized enums work

gdb/ChangeLog:
2016-06-25  Manish Goregaokar  <manish@mozilla.com>

    PR gdb/20239
    * rust-lang.c (rust_get_disr_info): Correctly interpret
    NonZero-optimized enums of arbitrary depth.
    (rust_print_type): Correctly print NonZero-optimized
    enums.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add tests for printing of NonZero-optimized enums in Rust
@ 2016-06-25  7:24 sergiodj+buildbot
  2016-06-25  7:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-25  7:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fccb08f8cd2035b50a2b0a5e09983180b7411685 ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: fccb08f8cd2035b50a2b0a5e09983180b7411685

Add tests for printing of NonZero-optimized enums in Rust

gdb/testsuite/ChangeLog:
2016-06-25  Manish Goregaokar  <manish@mozilla.com>

    PR gdb/20239
    * gdb.rust/simple.rs: Add more tests for printing NonZero enums.
    * gdb.rust/simple.exp: Add test expectations for new NonZero tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix formatting in rust-lang.c
@ 2016-06-25 15:10 sergiodj+buildbot
  2016-06-25 15:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-25 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e8a8ea8feadb0d3cd6443a1bc773b1dc835767e ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9e8a8ea8feadb0d3cd6443a1bc773b1dc835767e

Fix formatting in rust-lang.c

This fixes up a few formatting nits in rust-lang.c.
Built and regtested on x86-64 Fedora 23.

2016-06-25  Tom Tromey  <tom@tromey.com>

	* rust-lang.c (rust_get_disr_info, rust_print_type): Fix
	formatting.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] xtensa: prototype xtensa_make_property_section in elf/xtensa.h
@ 2016-06-25 16:01 sergiodj+buildbot
  2016-06-25 16:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-25 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c2c4aa12f4931fb79f94d787ef60e88960bb2a7 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 7c2c4aa12f4931fb79f94d787ef60e88960bb2a7

xtensa: prototype xtensa_make_property_section in elf/xtensa.h

There's no reason to have multiple prototypes for the same function.

include/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf/xtensa.h (xtensa_make_property_section): New prototype.

gas/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-xtensa.c (xtensa_make_property_section): Remove prototype.

bfd/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-xtensa.c (xtensa_make_property_section): Remove prototype.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] remove a few sentinals
@ 2016-06-25 16:48 sergiodj+buildbot
  2016-06-25 17:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-25 16:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5703197e0421f490c3dc25ecd9ea04ca59750b64 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 5703197e0421f490c3dc25ecd9ea04ca59750b64

remove a few sentinals

gas/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-bfin.c (bfin_cpus): Remove sentinal.
	(md_parse_option): Adjust.
	* config/tc-aarch64.c (aarch64_parse_abi): Replace use of a sentinal
	with iteration from 0 to ARRAY_SIZE.
	* config/tc-mcore.c (md_begin): Likewise.
	* config/tc-visium.c (visium_parse_arch): Likewise.

opcodes/ChangeLog:

2016-06-25  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* mcore-opc.h: Remove sentinal.
	* mcore-dis.c (print_insn_mcore): Adjust.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] dlx: move prototype of dlx_set_skip_hi16 to elf/dlx.h
@ 2016-06-27 10:18 sergiodj+buildbot
  2016-06-27 10:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-27 10:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 48afb19489cf39cb7f48e24fe7c567a9cd438b95 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 48afb19489cf39cb7f48e24fe7c567a9cd438b95

dlx: move prototype of dlx_set_skip_hi16 to elf/dlx.h

bfd/ChangeLog:

2016-06-27  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* elf32-dlx.h: New file.
	* elf32-dlx.c: Adjust.

gas/ChangeLog:

2016-06-27  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* config/tc-dlx.c: Include bfd/elf32-dlx.h.
	* config/tc-dlx.h: Remove prototype of dlx_set_skip_hi16.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix use of a dangling pointer for Python breakpoint objects
@ 2016-06-27 10:42 sergiodj+buildbot
  2016-06-27 11:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-27 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4952523968703caa027a5922263eb97b88bedc3 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: f4952523968703caa027a5922263eb97b88bedc3

Fix use of a dangling pointer for Python breakpoint objects

When a Python script tries to create a breakpoint but fails to do so,
gdb.Breakpoint.__init__ raises an exception and the breakpoint does not
exist anymore in the Python interpreter. However, GDB still keeps a
reference to the Python object to be used for a later hook, which is
wrong.

This commit adds the necessary cleanup code so that there is no stale
reference to this Python object. It also adds a new testcase to
reproduce the bug and check the fix.

2016-06-25  Pierre-Marie de Rodat  <derodat@adacore.com>

gdb/
	* python/py-breakpoint.c (bppy_init): Clear bppy_pending_object
	when there is an error during the breakpoint creation.

gdb/testsuite

	* gdb.python/py-breakpoint-create-fail.c,
	gdb.python/py-breakpoint-create-fail.exp,
	gdb.python/py-breakpoint-create-fail.py: New testcase.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Print void types correctly in Rust
@ 2016-06-27 17:03 sergiodj+buildbot
  2016-06-27 17:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-27 17:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 921d8f549f9e35d3f83c7b1a381146a7dc1246f4 ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: 921d8f549f9e35d3f83c7b1a381146a7dc1246f4

Print void types correctly in Rust

Rust prefers to not specify the return type of a function when it is unit
(`()`). The type is also referred to as "void" in debuginfo but not in actual
usage, so we should never be printing "void" when the language is Rust.

2016-06-27  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_print_type): Print unit types as "()"
    * rust-lang.c (rust_print_type): Omit return type for functions
    returning unit

gdb/testsuite/ChangeLog:
    * gdb.rust/simple.rs: Add test for returning unit in a function
    * gdb.rust/simple.exp: Add expectation for functions returning unit


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16: Add R_MIPS16_PC16_S1 branch relocation support
@ 2016-06-28  0:55 sergiodj+buildbot
  2016-06-28  1:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28  0:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9775dde32773c57d4eb5dfb4265eda9cb8adbe8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: c9775dde32773c57d4eb5dfb4265eda9cb8adbe8

MIPS16: Add R_MIPS16_PC16_S1 branch relocation support

For R_MIPS16_PC16_S1 the calculation is `(sign_extend(A) + S - P) >> 1'
and the usual MIPS16 bit shuffling applies to relocated field handling,
as per the encoding of the branch target in the extended form of the
MIPS16 B, BEQZ, BNEZ, BTEQZ and BTNEZ instructions.

	include/
	* elf/mips.h (R_MIPS16_PC16_S1): New relocation.

	bfd/
	* elf32-mips.c (elf_mips16_howto_table_rel): Add
	R_MIPS16_PC16_S1.
	(mips16_reloc_map): Likewise.
	* elf64-mips.c (mips16_elf64_howto_table_rel): Likewise.
	(mips16_elf64_howto_table_rela): Likewise.
	(mips16_reloc_map): Likewise.
	* elfn32-mips.c (elf_mips16_howto_table_rel): Likewise.
	(elf_mips16_howto_table_rela): Likewise.
	(mips16_reloc_map): Likewise.
	* elfxx-mips.c (mips16_branch_reloc_p): New function.
	(mips16_reloc_p): Handle R_MIPS16_PC16_S1.
	(b_reloc_p): Likewise.
	(mips_elf_calculate_relocation): Likewise.
	(_bfd_mips_elf_check_relocs): Likewise.
	* reloc.c (BFD_RELOC_MIPS16_16_PCREL_S1): New relocation.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.

	gas/
	* config/tc-mips.c (mips16_reloc_p): Handle
	BFD_RELOC_MIPS16_16_PCREL_S1.
	(b_reloc_p): Likewise.
	(limited_pcrel_reloc_p): Likewise.
	(md_pcrel_from): Likewise.
	(md_apply_fix): Likewise.
	(tc_gen_reloc): Likewise.
	(md_convert_frag): Likewise.
	(mips_fix_adjustable): Update comment.
	* testsuite/gas/mips/mips16-branch-reloc-2.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-reloc-3.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-addend-2.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-addend-3.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-absolute.d: Remove error
	output, add dump patterns.
	* testsuite/gas/mips/mips16-branch-reloc-2.l: Remove file.
	* testsuite/gas/mips/mips16-branch-reloc-3.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-2.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-3.l: Remove file.
	* testsuite/gas/mips/mips16-branch-absolute.l: Remove file.
	* testsuite/gas/mips/mips16-branch-addend-2.s: Add padding.
	* testsuite/gas/mips/branch-weak.s: Adjust alignment, avoid
	implicit instruction padding, avoid MIPS16 JR->JRC conversion.
	* testsuite/gas/mips/branch-weak-6.d: New test.
	* testsuite/gas/mips/branch-weak-7.d: New test.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/mips16-branch-2.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-3.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-addend-2.d: New test.
	* testsuite/ld-mips-elf/mips16-branch-addend-3.d: New test.
	* testsuite/ld-mips-elf/mips16-branch.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Make register indices be full 64-bit values
@ 2016-06-28  8:38 sergiodj+buildbot
  2016-06-28  8:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28  8:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dab26bf4e7c8b48e0c5ffbef1c5400807b78072c ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: dab26bf4e7c8b48e0c5ffbef1c5400807b78072c

[AArch64] Make register indices be full 64-bit values

aarch64_opnd_info used bitfields to hold vector element indices,
but values were stored into those bitfields before their ranges had
been checked.  This meant large invalid indices could be silently
truncated to smaller valid indices.

The two obvious fixes were to do the range checking earlier or use
a full 64-bit field for the index.  I went for the latter for two
reasons:

      - Doing the range checking in operand_general_constraint_met_p
        seems structurally cleaner than doing it while parsing.

      - The bitfields didn't really buy us anything.  The imm field
        of the union is already 128 bits, so we can use a full int64_t
        index without growing the structure.

The patch also adds missing range checks for the elements in a register
list index.

include/
	* opcode/aarch64.h (aarch64_opnd_info): Change index fields to int64_t.

opcodes/
	* aarch64-opc.c (operand_general_constraint_met_p): Check the
	range of ldst_elemlist operands.
	(print_register_list): Use PRIi64 to print the index.
	(aarch64_print_operand): Likewise.

gas/
	* testsuite/gas/aarch64/diagnostic.s,
	testsuite/gas/aarch64/diagnostic.l: Add tests for out-of-range indices.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't convert R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64.
@ 2016-06-28 11:18 sergiodj+buildbot
  2016-06-28 11:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 11:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7160c10d6530b79ea45d435933b07765f610f54d ***

Author: James Clarke <jrtc27@jrtc27.com>
Branch: master
Commit: 7160c10d6530b79ea45d435933b07765f610f54d

Don't convert R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64.

bfd	* elfxx-sparc.c (_bfd_sparc_elf_relocate_section): Don't convert
	R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64.

gold	* sparc.cc (Target_sparc::Scan::local): Don't convert R_SPARC_32
	to R_SPARC_RELATIVE if class is ELFCLASS64.
	(Target_sparc::Scan::global): Likewise.

ld	* testsuite/ld-elf/symbolic-func.r: Allow non-zero offsets from
	.text.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove parameter sysret from linux_target_ops.get_syscall_trapinfo
@ 2016-06-28 13:01 sergiodj+buildbot
  2016-06-28 13:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 13:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4cc32bec04aadc5c070d0f4aee656313a4854c11 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4cc32bec04aadc5c070d0f4aee656313a4854c11

Remove parameter sysret from linux_target_ops.get_syscall_trapinfo

When I implement linux_target_ops.get_syscall_trapinfo for aarch64 and arm,
I find the second parameter sysret isn't used at all.  In RSP, we don't
need syscall return value either, because GDB can figure out the return
value from registers content got by 'g' packet.

This patch is to remove them.

gdb/gdbserver:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (get_syscall_trapinfo): Remove parameter sysret.
	Callers updated.
	* linux-low.h (struct linux_target_ops) <get_syscall_trapinfo>:
	Remove parameter sysno.
	* linux-x86-low.c (x86_get_syscall_trapinfo): Remove parameter
	sysret.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Implement get_syscall_trapinfo for arm-linux
@ 2016-06-28 14:32 sergiodj+buildbot
  2016-06-28 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 14:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79e7fd4f78e0c33e77dd0b69d7de8167a60af06a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 79e7fd4f78e0c33e77dd0b69d7de8167a60af06a

Implement get_syscall_trapinfo for arm-linux

gdb/gdbserver:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (arm_get_syscall_trapinfo): New function.
	(the_low_target): Install arm_get_syscall_trapinfo.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Mark ARM mapping symbols in object files are precious, so that strip will not remove them.
@ 2016-06-28 15:00 sergiodj+buildbot
  2016-06-28 17:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fca2a38fdb391f810e309a12d5279047d4edac34 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: fca2a38fdb391f810e309a12d5279047d4edac34

Mark ARM mapping symbols in object files are precious, so that strip will not remove them.

	* elf32-arm.c (elf32_arm_backend_symbol_processing): New
	function.  Marks mapping symbols in object files as precious, so
	that strip will not remove them.
	(elf_backend_symbol_processing): Define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix typo in previous commit
@ 2016-06-28 16:19 sergiodj+buildbot
  2016-06-28 18:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb95c51a232dffb46067c402ac62f1f3303b6bbd ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: bb95c51a232dffb46067c402ac62f1f3303b6bbd

Fix typo in previous commit


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Use int64_t for address offset
@ 2016-06-28 17:17 sergiodj+buildbot
  2016-06-28 20:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac09a5bbbff78d363ede2f038c31a9b1cb0887b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2ac09a5bbbff78d363ede2f038c31a9b1cb0887b

[AArch64] Use int64_t for address offset

In AArch64 displaced stepping and fast tracepoint, GDB/GDBserver needs
to check whether the offset can fit in the range.  We are using int32_t
for offset, it is sufficient to get an offset from an instruction, but
it is not enough to get an offset from two addresses.  For example,
we have a BL in shared lib which is at 0x0000002000040774, and the
scratch pad for displaced stepping is at 0x400698.  The offset can't
fit in 28 bit imm.  However, since we are using int32_t for offset, GDB
thinks the offset can fit it, and generate the B instruction with wrong
offset.

It fixes the following fail,

-FAIL: gdb.base/dso2dso.exp: next over call to sub2

gdb:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_displaced_step_b): Use int64_t for
	variable new_offset.

gdb/gdbserver:

2016-06-28  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_ftrace_insn_reloc_b): Use int64_t
	for variable new_offset.
	(aarch64_ftrace_insn_reloc_b_cond): Likewise.
	(aarch64_ftrace_insn_reloc_cb): Likewise.
	(aarch64_ftrace_insn_reloc_tb): Likewise.
	(aarch64_install_fast_tracepoint_jump_pad): Likewise.  Use
	PRIx64 instead of PRIx32.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Preserve all mapping symbols in ARM and AArch64 object files.
@ 2016-06-29 10:35 sergiodj+buildbot
  2016-06-29 11:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d691934d08a4132506a19ac8d7565f1a0461a80a ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: d691934d08a4132506a19ac8d7565f1a0461a80a

Preserve all mapping symbols in ARM and AArch64 object files.

bfd	* elfnn-aarch64.c (is_aarch64_mapping_symbol): New function.
	Returns TRUE for AArch64 mapping symbols.
	(elfNN_aarch64_backend_symbol_processing): New function.  Marks
	mapping symbols as precious in object files so that they will not
	be stripped.
	(elf_backend_symbol_processing): Define.

	* elf32-arm.c (is_arm_mapping_symbol): New function.  Returns TRUE
	for ARM mapping symbols.
	(elf32_arm_backend_symbol_processing): Make use of the new function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use strtok_r instead of strsep in rust_get_disr_info
@ 2016-06-29 11:32 sergiodj+buildbot
  2016-06-29 12:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a405c2281ad29b5c7f9f2a4d58b7cfef2b74ba99 ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: a405c2281ad29b5c7f9f2a4d58b7cfef2b74ba99

Use strtok_r instead of strsep in rust_get_disr_info

strsep doesn't exist on Windows.

2016-06-29  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_get_disr_info): Use strtok_r instead of strsep.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sparc: make SPARC_OPCODE_ARCH_MAX part of its enum
@ 2016-06-29 12:11 sergiodj+buildbot
  2016-06-29 12:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 042c94de565ae62640c064f1cb33d28484aeb9d3 ***

Author: Trevor Saunders <tbsaunde+binutils@tbsaunde.org>
Branch: master
Commit: 042c94de565ae62640c064f1cb33d28484aeb9d3

sparc: make SPARC_OPCODE_ARCH_MAX part of its enum

include/ChangeLog:

2016-06-29  Trevor Saunders  <tbsaunde+binutils@tbsaunde.org>

	* opcode/sparc.h (enum sparc_opcode_arch_val): Move
	SPARC_OPCODE_ARCH_MAX into the enum.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set unknown_syscall differently on arm linux
@ 2016-06-29 14:20 sergiodj+buildbot
  2016-06-29 14:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28244707d9e4f35cab1f9069cee1d44b38be095f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 28244707d9e4f35cab1f9069cee1d44b38be095f

Set unknown_syscall differently on arm linux

Currently, we use 123456789 as unknown or illegal syscall number, and
expect program return ENOSYS.  Although 123456789 is an illegal syscall
number on arm linux, kernel sends SIGILL rather than returns -ENOSYS.
However, arm linux kernel returns -ENOSYS if syscall number is within
0xf0001..0xf07ff, so we can use 0xf07ff for unknown_syscall in test.

gdb/testsuite:

2016-06-29  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/catch-syscall.c [__arm__]: Set unknown_syscall to
	0x0f07ff.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Initialize strtok_r's saveptr to NULL
@ 2016-06-29 14:59 sergiodj+buildbot
  2016-06-29 15:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9bf74fb27dc6e2a9679403d66fe919215e3c2a45 ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: 9bf74fb27dc6e2a9679403d66fe919215e3c2a45

Initialize strtok_r's saveptr to NULL

Building gdb with --enable-build-with-cxx=no trips on a warning:

 ../../binutils-gdb/gdb/rust-lang.c:173:15: error: saveptr may be used
 uninitialized in this function [-Werror=maybe-uninitialized]
     ret.name = concat (TYPE_NAME (type), "::", token, (char *) NULL);

The problem is that gcc doesn't understand that "tail" can never be
NULL in the call to strtok_r:

      name = xstrdup (TYPE_FIELD_NAME (type, 0));
      cleanup = make_cleanup (xfree, name);
      tail = name + strlen (RUST_ENUM_PREFIX);
...
      for (token = strtok_r (tail, "$", &saveptr);

Fix this by always initializing saveptr.

2016-06-29  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_get_disr_info): Initialize saveptr to NULL.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR gdb/17210 - fix possible memory leak in read_memory_robust
@ 2016-06-29 16:36 sergiodj+buildbot
  2016-06-29 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d78f827e0da9ab6fda2d6ef2d59cebb805b411f ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9d78f827e0da9ab6fda2d6ef2d59cebb805b411f

PR gdb/17210 - fix possible memory leak in read_memory_robust

PR gdb/17210 concerns a possible memory leak in read_memory_robust.
The bug can happen because read_memory_robust allocates memory, does
not install any cleanups, and invokes QUIT.  Similarly, target_read
calls QUIT, so it too can potentially throw.

The fix is to install cleanups to guard the allocated memory.

Built and regtested on x86-64 Fedora 23.  I couldn't think of a way to
test this, so no new test; and of course this means it should have
more careful review.

2016-06-29  Tom Tromey  <tom@tromey.com>

	PR gdb/17210:
	* target.c (free_memory_read_result_vector): Take a pointer to the
	VEC as an argument.
	(read_memory_robust): Install a cleanup for "result".
	* mi/mi-main.c (mi_cmd_data_read_memory_bytes): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR python/20129 - use of non-existing variable
@ 2016-06-29 16:58 sergiodj+buildbot
  2016-06-29 17:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 803b47e5d4dc86b953aba0bc44865de287726dbe ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 803b47e5d4dc86b953aba0bc44865de287726dbe

Fix PR python/20129 - use of non-existing variable

PR python/20129 concerns the error message one gets from a command
like "disable frame-filter global NoSuchFilter".  Currently this
throws a second, unexpected, exception due to the use of a
non-existing variable named "name".

This patch adds regression tests and fixes a couple of spots to use
the correct variable name.

Built and regtested on x86-64 Fedora 23.

2016-06-29  Tom Tromey  <tom@tromey.com>

	PR python/20129:
	* python/lib/gdb/command/frame_filters.py (_do_enable_frame_filter)
	(SetFrameFilterPriority._set_filter_priority): Use "frame_filter",
	not "name".

2016-06-29  Tom Tromey  <tom@tromey.com>

	PR python/20129:
	* gdb.python/py-framefilter.exp: Add tests for setting priority
	and disabling of non-existent frame filter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add copyright header in gdb.base/return.c
@ 2016-06-29 18:30 sergiodj+buildbot
  2016-06-29 18:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-29 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e56534680d0df0e2ca313086b1758480c9374615 ***

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

Add copyright header in gdb.base/return.c

gdb/testsuite:

2016-06-29  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/return.c: Add copyright header.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for simulating big-endian AArch64 binaries.
@ 2016-06-30  8:28 sergiodj+buildbot
  2016-06-30  8:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-30  8:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7be441465094e5ffce2f4205ea887676965d0be ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: c7be441465094e5ffce2f4205ea887676965d0be

Add support for simulating big-endian AArch64 binaries.

	* cpustate.h: Include config.h.
	(union GRegisterValue): Add WORDS_BIGENDIAN check.  For big endian code
	use anonymous structs to align members.
	* simulator.c (aarch64_step): Use sim_core_read_buffer and
	endian_le2h_4 to read instruction from pc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM][GAS] ARMv8.2 should enable ARMv8.1 NEON instructions.
@ 2016-06-30 10:07 sergiodj+buildbot
  2016-06-30 10:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 10:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 534dbe460e692a9befd9aca0eb0812db47459a30 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 534dbe460e692a9befd9aca0eb0812db47459a30

[ARM][GAS] ARMv8.2 should enable ARMv8.1 NEON instructions.

GAS fails to recognize march=armv8.2-a as a superset of march=armv8.1-a
when assembling NEON instructions. The patch corrects this, making
-march=armv8.2-a -mfpu=neon-fp-armv8 enable the NEON intructions
introduced with ARMv8.1-A.

include/
2016-06-30  Matthew Wahab  <matthew.wahab@arm.com>

	* opcode/arm.h (ARM_ARCH_V8_2a): Add FPU_NEON_EXT_RDMA to the set
	of enabled FPU features.

gas/
2016-06-30  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/arm/armv8_2+rdma.d: New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix gdbserver/MI testing regression
@ 2016-06-30 11:43 sergiodj+buildbot
  2016-06-30 12:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 038d48680941f014349256aeb7bab14b3f01d58e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 038d48680941f014349256aeb7bab14b3f01d58e

Fix gdbserver/MI testing regression

Commit 51f77c3704a6 ("Add testing infrastruture bits for running with
MI on a separate UI") broke MI testing with native-gdbserver:

 $ make check RUNTESTFLAGS="--target_board=native-gdbserver mi-var-child.exp"
	 ...
 Running .../src/binutils-gdb/gdb/testsuite/gdb.mi/mi-var-child.exp ...
 can't unset "inferior_spawn_id": no such variable
     while executing
 "unset inferior_spawn_id"
     (procedure "close_gdbserver" line 20)
     invoked from within
 "close_gdbserver"
 ...

When testing with gdbserver, gdb_exit is overridden with a special
version that calls close_gdbserver, which clears inferior_spawn_id.
The problem is that the commit mentioned above made
gdb_exit/mi_gdb_exit clear inferior_spawn_id too, and clearing a
non-existing variable is a tcl error.

Since gdb_exit/mi_gdb_exit always clears inferior_spawn_id now, the
fix is simply to stop clearing it in close_gdbserver.

gdb/testsuite/
2016-06-30  Pedro Alves  <palves@redhat.com>

	* lib/gdbserver-support.exp (close_gdbserver, gdb_exit): Don't
	unset inferior_spawn_id.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x86/Intel: fix operand checking for MOVSD
@ 2016-07-01  7:09 sergiodj+buildbot
  2016-07-01  7:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  7:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8325cc6398187c12e0fe04a68a21e4eb5f44fa20 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 8325cc6398187c12e0fe04a68a21e4eb5f44fa20

x86/Intel: fix operand checking for MOVSD

The dual purpose mnemonic (string move vs scalar double move) breaks
the assumption that the isstring flag would be set on both the first
and last entry in the current set of templates, which results in bogus
or missing diagnostics for the string move variant of the mnemonic.
Short of mostly rewriting i386_index_check() and its interaction with
the rest of the code, simply shrink the template set to just string
instructions when encountering the second memory operand, and run
i386_index_check() a second time for the first memory operand after
that reduction.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x86: remove stray instruction attributes
@ 2016-07-01  7:49 sergiodj+buildbot
  2016-07-01  8:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9243100aef7486524f1a7f87bbd2cce1fe980b75 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 9243100aef7486524f1a7f87bbd2cce1fe980b75

x86: remove stray instruction attributes

- with Cpu64 Disp16 makes no sense for memory operands
- with CpuNo64 Disp32S makes no sense
- non-64-bit lgdt doesn't allow 10-byte operands


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x86: allow suffix-less movzw and 64-bit movzb
@ 2016-07-01  8:42 sergiodj+buildbot
  2016-07-01  9:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c07315e0c610e0e3317b4c02266f81793df253d2 ***

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

x86: allow suffix-less movzw and 64-bit movzb

... just like is already the case for 16- and 32-bit movzb: I can't see
why omitting suffixes on this (and movs{b,w,l}) is not allowed, when it
is allowed for all other instructions where the suffix is redundant
with (one of) the operands.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Factor out "Detaching from program" message printing
@ 2016-07-01 10:53 sergiodj+buildbot
  2016-07-01 11:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 10:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f48b757071509040d800ff9f7c8726e5828bd1a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0f48b757071509040d800ff9f7c8726e5828bd1a

Factor out "Detaching from program" message printing

Several targets have a copy of the same code that prints

 "Detaching from program ..."

in their target_detach implementation.  Factor that out to a common
function.

(For now, I left the couple targets that print this a bit differently
alone.  Maybe this could be further pulled out into infcmd.c.  If we
did that, and those targets want to continue printing differently,
this new function could be converted to a target method.)

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* darwin-nat.c (darwin_detach): Use target_announce_detach.
	* inf-ptrace.c (inf_ptrace_detach): Likewise.
	* nto-procfs.c (procfs_detach): Likewise.
	* remote.c (remote_detach_1): Likewise.
	* target.c (target_announce_detach): New function.
	* target.h (target_announce_detach): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Forget watchpoint locations when inferior exits or is killed/detached
@ 2016-07-01 11:56 sergiodj+buildbot
  2016-07-01 11:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 630008884535a5b26828325e48e729034c110536 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 630008884535a5b26828325e48e729034c110536

Forget watchpoint locations when inferior exits or is killed/detached

If you have two inferiors (or more), set watchpoints in one of the
inferiors, and then that inferior exits, until you manually delete the
watchpoint (or something forces a breakpoint re-set), you can't resume
the other inferior.

This is exercised by the test added by this commit.  Without the GDB
fix, this test fails like this:

 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: continue to marker in inferior 1
 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=detach: continue to marker in inferior 1
 FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=exit: continue to marker in inferior 1

and gdb.log shows (in all three cases):

 (gdb) continue
 Continuing.
 Warning:
 Could not insert hardware watchpoint 2.
 Could not insert hardware breakpoints:
 You may have requested too many hardware breakpoints/watchpoints.

 Command aborted.
 (gdb) FAIL: gdb.multi/watchpoint-multi-exit.exp: dispose=kill: continue to marker in inferior 1

The problem is that GDB doesn't forget about the locations of
watchpoints set in the inferior that is now dead.  When we try to
continue the inferior that is still alive, we reach
insert_breakpoint_locations, which has the the loop that triggers the
error:

  /* If we failed to insert all locations of a watchpoint, remove
     them, as half-inserted watchpoint is of limited use.  */

That loop finds locations that are not marked inserted, but which
according to should_be_inserted should have been inserted, and so
errors out.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (breakpoint_init_inferior): Discard watchpoint
	locations.
	* infcmd.c (detach_command): Call breakpoint_init_inferior.

gdb/testsuite/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* gdb.multi/watchpoint-multi-exit.c: New file.
	* gdb.multi/watchpoint-multi-exit.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix failure to detach if process exits while detaching on Linux
@ 2016-07-01 12:41 sergiodj+buildbot
  2016-07-01 13:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ced2dffbf17bc661e959da1e39411d706ade9f77 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ced2dffbf17bc661e959da1e39411d706ade9f77

Fix failure to detach if process exits while detaching on Linux

This commit fixes detaching on Linux when some thread exits the whole
thread group (process) just while we're detaching.

On Linux, a ptracer must detach from each LWP individually, with
PTRACE_DETACH.  Since PTRACE_DETACH sets the thread running free, if
one of the already-detached threads causes the whole thread group to
exit (e.g., simply calls exit), the kernel force-kills the other
threads in the group, making them zombie, just as we're still
detaching them.  Since PTRACE_DETACH against a zombie thread fails
with ESRCH, and gdb/gdbserver are not expecting this, the detach fails
with an error like: "Can't detach process: No such process.".

This patch detects this detach failure as normal, and instead of
erroring out, reaps the now-dead thread.

New test included, that exercises several different scenarios that
cause GDB/GDBserver to error out when it should not.

Tested on x86-64 GNU/Linux with {unix, native-gdbserver,
native-extended-gdbserver}

Note: without the previous fix, the "single-process + continue"
variant of the new test would fail with:

 (gdb) PASS: gdb.threads/process-dies-while-detaching.exp: single-process: continue: watchpoint: switch to parent
 continue
 Continuing.
 Warning:
 Could not insert hardware watchpoint 3.
 Could not insert hardware breakpoints:
 You may have requested too many hardware breakpoints/watchpoints.

 Command aborted.
 (gdb) FAIL: gdb.threads/process-dies-while-detaching.exp: single-process: continue: watchpoint: continue

gdb/gdbserver/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Antoine Tremblay  <antoine.tremblay@ericsson.com>

	* linux-low.c: Change interface to take the target lwp_info
	pointer directly and return void.  Handle detaching from a zombie
	thread.
	(linux_detach_lwp_callback): New function.
	(linux_detach): Detach from the leader thread after detaching from
	the clone threads.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Antoine Tremblay  <antoine.tremblay@ericsson.com>

	* inf-ptrace.c (inf_ptrace_detach_success): New function, factored
	out from ...
	(inf_ptrace_detach): ... here.
	* inf-ptrace.h (inf_ptrace_detach_success): New declaration.
	* linux-nat.c (get_pending_status): Rename to ...
	(get_detach_signal): ... this, and return a host signal instead of
	filling in a wait status.
	(detach_one_lwp): New function, factored out from detach_callback
	and adjusted to handle detaching from a zombie thread.
	(detach_callback): Skip the leader thread.
	(linux_nat_detach): No longer defer to inf_ptrace_detach to detach
	the leader thread, nor build a signal string to pass down.
	Instead, use target_announce_detach, detach_one_lwp and
	inf_ptrace_detach_success.

gdb/testsuite/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Antoine Tremblay  <antoine.tremblay@ericsson.com>

	* gdb.threads/process-dies-while-detaching.c: New file.
	* gdb.threads/process-dies-while-detaching.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Extend JIT-reader test and fix GDB problems that exposes
@ 2016-07-01 12:59 sergiodj+buildbot
  2016-07-01 14:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 12:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20aa2c606ef682889722b03b1d874befa84fbf53 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 20aa2c606ef682889722b03b1d874befa84fbf53

Extend JIT-reader test and fix GDB problems that exposes

The jit-reader.exp test isn't really exercising the jit-reader's
unwinder API at all.  This commit address that, and then fixes GDB
problems exposed.

- The custom JIT reader provided for the jit-reader.exp testcase
  always rejects the jitted function's frame...

  This is because the custom JIT reader in the testcase never ever
  sets state->code_begin/end, so the bounds check in
  gdb.base/jitreader.c:unwind_frame:

   if (this_ip >= state->code_end || this_ip < state->code_begin)
     return GDB_FAIL;

  tends to fail, unless you're "lucky" (because it references
  uninitialized data).

  The result is that GDB is always actually using a built-in unwinder
  for the jitted function.

- The provided unwinder doesn't do anything that GDB's built-in
  unwinder can't do.

  IOW, we can't really tell whether the JIT reader's unwinder is
  working or not.

  I fixed that by making the jitted function mangle its own stack
  pointer with a xor, and then teaching the jit unwinder to demangle
  it back (another xor).  So now "backtrace" with GDB's built-in
  unwinder fails while with the jit unwinder, it succeeds.

- GDB crashes after unloading the JIT reader, and flushing frames...

  I made the testcase use the "flushregs" command after unloading the
  JIT reader, to force the JIT frames to be flushed.  However, that
  crashes GDB...

  When reinit_frame_cache tears down a frame's cache, it calls its
  unwinder's dealloc_cache method, which for JIT frames ends up in
  jit.c:jit_dealloc_cache.  This function calls each of the frame's
  gdb_reg_value's "free" pointer:

   for (i = 0; i < gdbarch_num_regs (frame_arch); i++)
     if (priv_data->registers[i] && priv_data->registers[i]->free)
       priv_data->registers[i]->free (priv_data->registers[i]);

  and the problem is these gdb_reg_value instances have been returned
  by the JIT reader that has been already unloaded, and their "free"
  function pointers likely point to functions in the DSO that has
  already been unloaded...

  A fix for that could be to call reinit_frame_cache in
  jit_reader_unload_command _before_ unloading the jit reader DSO so
  that the jit reader is given a chance to clean up the gdb_reg_values
  before it is unloaded.  However, the fix for the point below makes
  this unnecessary, because it stops jit.c from keeping around
  gdb_reg_values in the first place.

- However, it still makes sense to clear the frame cache when loading
  or unloading a JIT unwinder.

  This makes testing a JIT unwinder a bit simpler.

- Not only the frame cache actually -- gdb is not unloading the
  jit-registered objfiles when the JIT reader is unloaded, and not
  loading the already-registered descriptors when a JIT reader is
  loaded.

  The new test exercises unloading the jit reader, loading it back
  again, and then making sure the JIT reader's unwinder works again.
  Without the unload/re-load of already-read descriptors, the newly
  loaded JIT would have no idea where the new function is, because
  it's stored at symbol read time.

- I added a couple "info frame" calls to the test, and that
  crashes GDB...

  The problem is that jit_frame_prev_register assumes it'll only be
  called for raw registers, so when it gets a pseudo register number,
  the "priv->registers[reg]" access is really an out-of-bounds access.

  To fix that, I made jit_frame_prev_register use
  gdbarch_pseudo_register_read_value for reading the pseudo-registers.
  However, that works with a regcache and we don't have one.  To fix
  that, I made the JIT unwinder store a regcache in its cache instead
  of an array of gdb_reg_value pointers.

gdb/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>
	    Tom Tromey  <tom@tromey.com>

	* jit.c (jit_reader_load_command): Call reinit_frame_cache and
	jit_inferior_created_hook.
	(jit_reader_unload_command): Call reinit_frame_cache and
	jit_inferior_exit_hook.
	* jit.c (struct jit_unwind_private) <registers>: Delete field.
	<regcache>: New field.
	(jit_unwind_reg_set_impl): Set the register's value in the
	regcache.  Free the passed-in gdb_reg_value.
	(jit_dealloc_cache): Adjust to free the regcache.
	(jit_frame_sniffer): Allocate a regcache instead of an array of
	gdb_reg_value pointers.
	(jit_frame_this_id): Adjust.
	(jit_frame_prev_register): Read raw registers off of the regcache
	instead of from the gdb_reg_value pointer array.  Use
	gdbarch_pseudo_register_read_value to read pseudo registers.
	* regcache.c (regcache_raw_set_cached_value): New function,
	factored out from ...
	(regcache_raw_write): ... here.
	* regcache.h (regcache_raw_set_cached_value): Declare.

gdb/testsuite/ChangeLog:
2016-07-01  Pedro Alves  <palves@redhat.com>

	* gdb.base/jit-reader.exp (info_registers_current_frame): New
	procedure.
	(jit_reader_test): Test the jit reader's unwinder.
	* gdb.base/jithost.c (jit_function_00_code): New global.
	(main): Use memcpy to fill in the mmapped code, instead of poking
	bytes manually here.
	* gdb.base/jitreader.c (enum register_mapping) <AMD64_RBP>: New
	value.
	(read_debug_info): Save the function's range.
	(read_sp): New function.
	(unwind_frame): Use it.  Also unwind RBP.
	(get_frame_id): Use read_sp.
	(gdb_init_reader): Use calloc instead of malloc.
	* lib/gdb.exp (get_hexadecimal_valueof): Add optional 'test'
	parameter.  Use gdb_test_multiple.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Consolidate x86 debug register code for BSD native targets.
@ 2016-07-01 14:59 sergiodj+buildbot
  2016-07-01 15:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3405d124e1388b613a35af49f19f0cc1b8d959d ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: a3405d124e1388b613a35af49f19f0cc1b8d959d

Consolidate x86 debug register code for BSD native targets.

Move the debug register support code from amd64bsd-nat.c and
i386bsd-nat.c into a shared x86bsd-nat.c.

Instead of setting up x86_dr_low in amd64fbsd-nat.c and
i386fbsd-nat.c, add a x86bsd_target function that creates a new target
that inherits from inf_ptrace and sets up x86 debug registers if
supported.  In addition to initializing x86_dr_low, the x86bsd target
installs a custom mourn_inferior target operation to clean up the
x86 debug register state.  Previously this was only done on amd64.
Now it will be done for both i386 and amd64.  The i386bsd_target and
amd64bsd_target functions create targets that inherit from x86bsd
rather than inf_ptrace.

gdb/ChangeLog:

	* Makefile.in [HFILES_NO_SRCDIR]: Replace 'amd64bsd-nat.h' with
	'x86bsd-nat.h'.
	* amd64bsd-nat.c: Include 'x86bsd-nat.h' instead of
	'amd64bsd-nat.h'.
	(amd64bsd_xsave_len): Rename and move to x86bsd-nat.c.
	(amd64bsd_fetch_inferior_registers): Replace 'amd64bsd_xsave_len'
	with 'x86bsd_xsave_len'.
	(amd64bsd_store_inferior_registers): Likewise.
	(amd64bsd_target): Inherit from x86bsd_target.
	(amd64bsd_dr_get): Rename and move to x86bsd-nat.c.
	(amd64bsd_dr_set): Likewise.
	(amd64bsd_dr_set_control): Likewise.
	(amd64bsd_dr_set_addr): Likewise.
	(amd64bsd_dr_get_addr): Likewise.
	(amd64bsd_dr_get_status): Likewise.
	(amd64bsd_dr_get_control): Likewise.
	* amd64fbsd-nat.c: Include 'x86bsd-nat.h' instead of
	'amd64bsd-nat.h'.
	(super_mourn_inferior): Move to x86bsd-nat.c.
	(amd64fbsd_mourn_inferior): Rename and move to x86bsd-nat.c.
	(amd64fbsd_read_description): Replace 'amd64bsd_xsave_len' with
	'x86bsd_xsave_len'.
	(_initialize_amd64fbsd_nat): Remove x86 watchpoint setup and
	mourn_inferior' target op.
	* config/i386/fbsd.mh (NATDEPFILES): Add x86bsd-nat.o.
	* config/i386/fbsd64.mh: Likewise.
	* config/i386/nbsd64.mh: Likewise.
	* config/i386/nbsdelf.mh: Likewise.
	* config/i386/obsd.mh: Likewise.
	* config/i386/obsd64.mh: Likewise.
	* i386bsd-nat.c: Include 'x86bsd-nat.h'.
	(i386bsd_xsave_len): Rename and move to x86bsd-nat.c.
	(i386bsd_fetch_inferior_registers): Replace 'i386bsd_xsave_len'
	with 'x86bsd_xsave_len'.
	(i386bsd_store_inferior_registers): Likewise.
	(i386bsd_target): Inherit from x86bsd_target.
	(i386bsd_dr_get): Rename and move to x86bsd-nat.c.
	(i386bsd_dr_set): Likewise.
	(i386bsd_dr_set_control): Likewise.
	(i386bsd_dr_set_addr): Likewise.
	(i386bsd_dr_get_addr): Likewise.
	(i386bsd_dr_get_status): Likewise.
	(i386bsd_dr_get_control): Likewise.
	* i386bsd-nat.h (i386bsd_xsave_len): Remove.
	(i386bsd_dr_set_control): Remove.
	(i386bsd_dr_set_addr): Remove.
	(i386bsd_dr_get_addr): Remove.
	(i386bsd_dr_get_status): Remove.
	(i386bsd_dr_get_control): Remove.
	* i386fbsd-nat.c: Include 'x86bsd-nat.h'.
	(i386fbsd_read_description): Replace 'i386bsd_xsave_len' with
	'x86bsd_xsave_len'.
	(_initialize_i386fbsd_nat): Remove x86 watchpoint setup and
	mourn_inferior' target op.
	* x86bsd-nat.c: New file.
	* x86bsd-nat.h: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set debug registers on all threads belonging to the current inferior.
@ 2016-07-01 15:50 sergiodj+buildbot
  2016-07-01 16:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5077bfff905136e9d9a8fdf0886f6217887622ad ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 5077bfff905136e9d9a8fdf0886f6217887622ad

Set debug registers on all threads belonging to the current inferior.

gdb/ChangeLog:

	* x86bsd-nat.c: Include 'gdbthread.h'.
	(x86bsd_dr_set): Set debug registers on all threads belonging to
	the current inferior.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix Thumb-2 BL detection
@ 2016-07-01 16:41 sergiodj+buildbot
  2016-07-01 16:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e866f5aeeaf7514f5ca4f9eaba41594eac22e5b ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 5e866f5aeeaf7514f5ca4f9eaba41594eac22e5b

Fix Thumb-2 BL detection

2016-07-01  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (using_thumb2_bl): New function.
	(arm_type_of_stub): Declare thumb2 variable together and change type
	to bfd_boolean.  Use using_thumb2_bl () to determine whether
	THM_MAX_FWD_BRANCH_OFFSET or THM2_MAX_FWD_BRANCH_OFFSET should be
	checked for BL range.
	(elf32_arm_final_link_relocate): Use using_thumb2_bl () to determine
	the bit size of BL offset.

ld/
	* testsuite/ld-arm/arm-elf.exp (Thumb-2 BL): Assemble for ARMv7.
	(Thumb-2 BL on ARMv6-M): New testcase.
	* testsuite/ld-arm/thumb2-bl.d: Do not try to match testcase filename.
	* testsuite/ld-arm/thumb2-bl.s: Do not select architecture.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Honor detach-on-fork on FreeBSD.
@ 2016-07-01 17:17 sergiodj+buildbot
  2016-07-01 17:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb2a62e694953c099c41d49f59947d3d91cc7c27 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: bb2a62e694953c099c41d49f59947d3d91cc7c27

Honor detach-on-fork on FreeBSD.

Only detach from the new child process in the follow fork callback
if detach_fork is true.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_follow_fork): Only detach child if
	"detach_fork" is true.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fake VFORK_DONE events when following only the parent after a vfork.
@ 2016-07-01 18:48 sergiodj+buildbot
  2016-07-01 19:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c5c2a3321706c28cbf1b85a970a2e32912eb0c8 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 2c5c2a3321706c28cbf1b85a970a2e32912eb0c8

Fake VFORK_DONE events when following only the parent after a vfork.

FreeBSD does not currently report a ptrace event for a parent process
after it resumes due to the child exiting the shared memory region after
a vfork.  Take the same approach used in linux-nat.c in this case of
sleeping for a while and then reporting a fake VFORK_DONE event.

gdb/ChangeLog:

	* fbsd-nat.c (struct fbsd_fork_child_info): Rename to ...
	(struct fbsd_fork_info): ... this.
	(struct fbsd_fork_info) <child>: Rename to ...
	(struct fbsd_fork_info) <ptid>: ... this.
	(fbsd_pending_children): Update type.
	(fbsd_remember_child): Update type and field name.
	(fbsd_is_child_pending): Likewise.
	(fbsd_pending_vfork_done): New variable.
	(fbsd_is_vfork_done_pending): New function.
	(fbsd_next_vfork_done): New function.
	(fbsd_resume): Don't resume processes with a pending vfork done
	event.
	(fbsd_wait): Report pending vfork done events.
	(fbsd_follow_fork): Delay and record a pending vfork done event
	for a vfork parent when detaching the child.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Fix +nofp16 handling
@ 2016-07-01 19:44 sergiodj+buildbot
  2016-07-01 20:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 19:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93d8990cba700abdf9d2be06a5022e588d097fc8 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 93d8990cba700abdf9d2be06a5022e588d097fc8

[AArch64] Fix +nofp16 handling

Feature flag handling was not perfect, +nofp16 disabled fp
instructions too.

New feature flag macros were added to check features with multiple
bits set (matters for FP_F16 and SIMD_F16 opcode feature tests).
The unused AARCH64_OPCODE_HAS_FEATURE was removed, all checks should
use one of the AARCH64_CPU_HAS_* macros.  AARCH64_CPU_HAS_FEATURE
now checks all feature bits.

The aarch64_features table now contains the dependencies as
a separate field (so when the feature is enabled all dependencies
are enabled and when it is disabled everything that depends on it
is disabled).

Note that armv8-a+foo+nofoo is not equivalent to armv8-a if
+foo turns on dependent features that nofoo does not turn off.

gas/
	* config/tc-aarch64.c (struct aarch64_option_cpu_value_table): Add
	require field.
	(aarch64_features): Initialize require fields.
	(aarch64_parse_features): Handle dependencies.
	(aarch64_feature_enable_set, aarch64_feature_disable_set): New.
	(md_assemble): Use AARCH64_CPU_HAS_ALL_FEATURES.
	* testsuite/gas/aarch64/illegal-nofp16.s: New.
	* testsuite/gas/aarch64/illegal-nofp16.l: New.
	* testsuite/gas/aarch64/illegal-nofp16.d: New.

include/
	* opcode/aarch64.h (AARCH64_CPU_HAS_ALL_FEATURES): New.
	(AARCH64_CPU_HAS_ANY_FEATURES): New.
	(AARCH64_CPU_HAS_FEATURE): Define as AARCH64_CPU_HAS_ALL_FEATURES.
	(AARCH64_OPCODE_HAS_FEATURE): Remove.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Optimize memory_xfer_partial for remote
@ 2016-07-01 19:49 sergiodj+buildbot
  2016-07-01 21:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-01 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09c98b448f3d89cb9576e4e73991c2312939e0af ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 09c98b448f3d89cb9576e4e73991c2312939e0af

Optimize memory_xfer_partial for remote

Some analysis we did here showed that increasing the cap on the
transfer size in target.c:memory_xfer_partial could give 20% or more
improvement in remote load across JTAG.  Transfer sizes were capped
to 4K bytes because of performance problems encountered with the
restore command, documented here:

https://sourceware.org/ml/gdb-patches/2013-07/msg00611.html

and in commit 67c059c29e1f ("Improve performance of large restore
commands").

The 4K cap was introduced because in a case where the restore command
requested a 100MB transfer, memory_xfer_partial would repeatedy
allocate and copy an entire 100MB buffer in order to properly handle
breakpoint shadow instructions, even though memory_xfer_partial would
actually only write a small portion of the buffer contents.

A couple of alternative solutions were suggested:
* change the algorithm for handling the breakpoint shadow instructions
* throttle the transfer size up or down based on the previous actual
  transfer size

I tried implementing the throttling approach, and my implementation
reduced the performance in some cases.

This patch implements a new target function that returns that target's
limit on memory transfer size.  It defaults to ULONGEST_MAX bytes,
because for native targets there is no marshaling and thus no limit is
needed.  For remote targets it uses get_memory_write_packet_size.

gdb/ChangeLog:

	* remote.c (remote_get_memory_xfer_limit): New function.
	* target-delegates.c: Regenerate.
	* target.c (memory_xfer_partial): Call
	target_ops.to_get_memory_xfer_limit.
	* target.h (struct target_ops)
	<to_get_memory_xfer_limit>: New member.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] babeltrace compilation regression
@ 2016-07-05  9:02 sergiodj+buildbot
  2016-07-05  9:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-05  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13cdc2afb7873547ec2910ba647fb4a68602252f ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 13cdc2afb7873547ec2910ba647fb4a68602252f

babeltrace compilation regression

Since:
	commit 2d681be471cf8aff8f296cb7713c39e9aa4fc2bb
	Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
	Date:   Wed Apr 27 15:52:16 2016 +0200
	    Avoid non-C++-enabled babeltrace versions
tested with:
	libbabeltrace-devel-1.2.4-4.fc24.x86_64
	libbabeltrace-devel-1.4.0-2.fc25.x86_64
it can no longer build due to:
	configure:16435: gcc -o conftest -m64 -g3 -pipe -Wall -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -fno-diagno
stics-show-caret  -Werror  -static-libstdc++ -static-libgcc  conftest.c -ldl -ldl -lncurses -lm -ldl  -lbabeltrace -lbabeltrace-ctf >&5
	conftest.c: In function 'main':
	conftest.c:208:7: error: 'pos' is a pointer; did you mean to use '->'?

gdb/ChangeLog
2016-07-05  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* configure: Regenerate.
	* configure.ac (HAVE_LIBBABELTRACE): Fix pos variable dereference.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] Purecode compatible long branch veneer for M-profile targets with MOVW.
@ 2016-07-05 11:42 sergiodj+buildbot
  2016-07-05 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-05 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5a67c02901c0abe946546f2b3b1a3b67a876136 ***

Author: Andre Vieria <andre.simoesdiasvieira@arm.com>
Branch: master
Commit: d5a67c02901c0abe946546f2b3b1a3b67a876136

[ARM] Purecode compatible long branch veneer for M-profile targets with MOVW.

2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

	* elf32-arm.c (THUMB32_MOVT): New veneer macro.
	(THUMB32_MOVW): Likewise.
	(elf32_arm_stub_long_branch_thumb2_only_pure): New.
	(DEF_STUBS): Define long_branch_thumb2_only_pure.
	(arm_stub_is_thumb): Add new veneer stub.
	(arm_type_of_stub): Use new veneer.
	(arm_stub_required_alignment): Add new veneer.

2016-07-05  Andre Vieria  <andre.simoesdiasvieira@arm.com>

	* testsuite/ld-arm/farcall-thumb2-purecode.d: New test result.
	* testsuite/ld-arm/farcall-thumb2-purecode.s: New test.
	* testsuite/ld-arm/arm-elf.exp: Run it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix fail in gdb.mi/mi-reverse.exp
@ 2016-07-05 14:06 sergiodj+buildbot
  2016-07-05 14:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-05 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 647c264cb2c60c90ee2d09edb6bd001ff357306d ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 647c264cb2c60c90ee2d09edb6bd001ff357306d

Fix fail in gdb.mi/mi-reverse.exp

Commit 38b022b4452f996fb5a8598f80d850b594621bcf adds "method" and
"format" fields in =record-started, but doesn't update test case
gdb.mi/mi-reverse.exp, so it causes the fail like this,

PASS: gdb.mi/mi-reverse.exp: mi runto main
Expecting: ^(-interpreter-exec console record[^M
]+)?(=record-started,thread-group="i1"^M
\^done[^M
]+[(]gdb[)] ^M
[ ]*)
-interpreter-exec console record^M
=record-started,thread-group="i1",method="full"^M
^done^M
(gdb) ^M
FAIL: gdb.mi/mi-reverse.exp: Turn on process record

and regression was found by buildbot too
https://sourceware.org/ml/gdb-testers/2016-q2/msg04492.html

gdb/testsuite:

2016-07-05  Yao Qi  <yao.qi@linaro.org>

	* gdb.mi/mi-reverse.exp: Match =record-started output.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow subscripting raw pointers
@ 2016-07-06  5:38 sergiodj+buildbot
  2016-07-06  5:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42d940118a6372d6e85f71a54fed75fdf5c606bd ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: 42d940118a6372d6e85f71a54fed75fdf5c606bd

Allow subscripting raw pointers

This will be useful for dealing with vectors; regardless of our final solution
for the Index trait.

2016-07-06  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_subscript): Allow subscripting pointers

gdb/testsuite/ChangeLog:
    * simple.rs: Add test for raw pointer subscripting
    * simple.exp: Add test expectations


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] Fix endless recursion on calculating CPRC candidate
@ 2016-07-06  7:38 sergiodj+buildbot
  2016-07-06  7:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06  7:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1040b979bc46474530fa4fee397b8acc460c01e9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1040b979bc46474530fa4fee397b8acc460c01e9

[ARM] Fix endless recursion on calculating CPRC candidate

When GDB determines whether type T can be part of candidate for
passing and returning in VFP registers, it calls
arm_vfp_cprc_sub_candidate recursively.  However, if type T has
self-reference field, like,

class C
{
  static C s;
};

arm_vfp_cprc_sub_candidate won't return.  This fix is to skip calling
arm_vfp_cprc_sub_candidate if the field is static.

gdb:

2016-07-06  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_vfp_cprc_sub_candidate): Don't call
	arm_vfp_cprc_sub_candidate for static field.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove check for negative size.
@ 2016-07-06 13:45 sergiodj+buildbot
  2016-07-06 14:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d66ff635bec25bf940cc6d173a92f7796f18b310 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: d66ff635bec25bf940cc6d173a92f7796f18b310

Remove check for negative size.

Since CORE_ADDR is unsigned, this value can never be negative.

gdb/ChangeLog:

	* score-tdep.c (score7_malloc_and_get_memblock): Remove check for
	negative size.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set uses_fp for frames with a valid FP register explicitly.
@ 2016-07-06 14:25 sergiodj+buildbot
  2016-07-06 15:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 14:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ca107148e888a7f7aaf3582569708684bd04690 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 9ca107148e888a7f7aaf3582569708684bd04690

Set uses_fp for frames with a valid FP register explicitly.

Since CORE_ADDR is unsigned, the saved FP register is always greater than
or equal to zero.  Replace the comparison by explicitly setting uses_fp to
1 for frames with a valid FP register.

gdb/ChangeLog:

	* sh64-tdep.c (sh64_analyze_prologue): Set "uses_fp" when setting
	the MEDIA_FP_REGNUM register.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use unsigned integer constant with left shifts.
@ 2016-07-06 15:28 sergiodj+buildbot
  2016-07-06 16:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db297a6501dc44c10bff096eddcc358b48810aad ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: db297a6501dc44c10bff096eddcc358b48810aad

Use unsigned integer constant with left shifts.

This avoids undefined behavior.

gdb/ChangeLog:

	* ada-lang.c (ada_unpack_from_contents): Use unsigned constants with
	left shifts.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove extraneous parentheses.
@ 2016-07-06 15:43 sergiodj+buildbot
  2016-07-06 17:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb36c6bf0a019e7b989e61710f17b5ce4ec27686 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: fb36c6bf0a019e7b989e61710f17b5ce4ec27686

Remove extraneous parentheses.

gdb/ChangeLog:

	* h8300-tdep.c (h8300_print_register): Remove extraneous parentheses.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove extra output directory level for Ada tests
@ 2016-07-06 16:12 sergiodj+buildbot
  2016-07-06 18:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0464b231f046b836e2ed721d764fa309f18eb39 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: f0464b231f046b836e2ed721d764fa309f18eb39

Remove extra output directory level for Ada tests

The output of Ada tests create a layout where the test name
("formatted_ref" in this example) appears twice:

outputs
 gdb.ada
     formatted_ref
         formatted_ref
             b~formatted_ref.adb
             b~formatted_ref.ads
             b~formatted_ref.ali
             b~formatted_ref.o
             defs.ali
             defs.o
             formatted_ref
             formatted_ref.ali
             formatted_ref.o

This causes a problem when testing with the native-gdbserver board, when
the binary has the same name as the test.  When gdb_remote_download is
called to upload the compiled binary, the implementation for
native-gdbserver copies it in the standard output directory (in
outputs/gdb.ada/formatted_ref).  However, there is already a directory
named formatted_ref in there, so the copy fails and gdbserver isn't able
to load the binary.

This patch bypasses the problem by removing the extra directory level.
The compiled binary will already be in its final location in the
standard output directory, so the copy will effectively be a no-op.

gdb/testsuite/ChangeLog:

	* lib/ada.exp: Remove extra directory level in build directory.
	* gdb.ada/cond_lang.exp: Likewise.
	* gdb.ada/exec_changed.exp: Likewise.
	* gdb.ada/lang_switch.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb.ada/arraydim.exp: Fix directory layout
@ 2016-07-06 17:08 sergiodj+buildbot
  2016-07-06 19:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 986cf455bfb25d8696232695fbcc93649c10a523 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 986cf455bfb25d8696232695fbcc93649c10a523

gdb.ada/arraydim.exp: Fix directory layout

I forgot to fix this one in the previous commit.

gdb/testsuite/ChangeLog:

	* gdb.ada/arraydim.exp: Remove extra directory level in build
	directory.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix of default lookup for "this" symbol.
@ 2016-07-07 15:52 sergiodj+buildbot
  2016-07-07 16:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-07 15:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 4f19a0e6b45c63c0b4afe27a19d144cca412d4ae

Fix of default lookup for "this" symbol.

Using the default lookup for the symbol "this" might lead to segmentation
fault in GDB.
Some languages, e.g. Fortran, use as default lookup routine the C++
routines.
For those languages "this" can be the instance of a class or even the
definition of a class.
When an instance of a class having the name "this" is evaluated
in GDB a segmentation fault was observed.

As example of the issue take into consideration the Fortran code:
  type foo
    real :: a
    type(bar) :: x
    character*7 :: b
  end type foo
  type(foo) :: this

Issue appears when evaluating the variable "this" in GDB.

Within the language definition structure there is a field that represents
the name of the special symbol used for the C++ "this" for the language
being described.
The fix presented here takes into account the aforementioned field. In the
case the aforementioned field is NULL "this" is not represented in the
language described and the lookup should return a null_block_symbol.

Tests: Performed tests with gfortran and ifort.

Reviewed:
https://sourceware.org/ml/gdb-patches/2016-04/msg00068.html

After the commited patch:
https://sourceware.org/ml/gdb-patches/2016-06/msg00364.html
Patch can be applied.

2016-06-16  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* cp-namespace.c (cp_lookup_bare_symbol): Use language passed as
	parameter to look for the symbol "this".

gdb/testsuite/ChangeLog:

	* gdb.fortran/derived-types.exp (result_line, result_line_2):
	New variables.
	(print this%a, print this%b, print this): New tests.
	* gdb.fortran/derived-types.f90 (this): New object and
	initialization.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [obv] Fix broken build on Fedora 23.
@ 2016-07-07 17:47 sergiodj+buildbot
  2016-07-07 17:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-07 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41c977aa5c81c04a9fea61bfe0b88e428a4b1839 ***

Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 41c977aa5c81c04a9fea61bfe0b88e428a4b1839

[obv] Fix broken build on Fedora 23.

Compiler complains about possible utilization of "symbol" which is member
of lang_def.
Initialization was added.

2016-07-07  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* cp-namespace.c (cp_lookup_bare_symbol): Initialize
	lang_this.symbol.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] FT32: adjust disassembly opcode match fields
@ 2016-07-08 19:25 sergiodj+buildbot
  2016-07-08 19:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-08 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f831b9a2bfbd0c2f6083d41b6dc9d9fc6b61e5a ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 2f831b9a2bfbd0c2f6083d41b6dc9d9fc6b61e5a

FT32: adjust disassembly opcode match fields

Tighten up the opcode match fields for conditional jump and call
instructions so more general opcodes don't match them in disassembly.

opcodes/ChangeLog:

	* opcodes/ft32-opc.c (ft32_opc_info): Correct mask for "callc"
	and "jmpc".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fixes done to TLS.
@ 2016-07-11 14:19 sergiodj+buildbot
  2016-07-11 14:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-11 14:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08759e0fc8b0de1c56ad388212a104f3a6d61c25 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 08759e0fc8b0de1c56ad388212a104f3a6d61c25

Fixes done to TLS.

TLS relocations did not support multiple TLS modes for the same
symbol in a single object file.
Refactored how GOT and TLS is implemented. Removed code duplications between
local and global symbols conditioning.

bfd/ChangeLog:

2016-06-14  Cupertino Miranda  <cmiranda@synopsys.com>
  * arc-got.h: Moved got related structures from elf32-arc.c to
    this file. More precisely, tls_type_e, tls_got_entries, got_entry.
  * (arc_get_local_got_ents,
     got_entry_for_type,
     new_got_entry_to_list,
     tls_type_for_reloc,
     symbol_has_entry_of_type,
     get_got_entry_list_for_symbol,
     arc_got_entry_type_for_reloc,
     ADD_SYMBOL_REF_SEC_AND_RELOC,
     arc_fill_got_info_for_reloc,
     relocate_fix_got_relocs_for_got_info,
     create_got_dynrelocs_for_single_entry,
     create_got_dynrelocs_for_got_info): Added to file.
  * elf32-arc.c: Removed GOT & TLS related structs and functions to
                     arc-got.h.

Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable relocation overflow messages by default.
@ 2016-07-11 14:57 sergiodj+buildbot
  2016-07-11 15:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-11 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b9316f59852ff821cf621aca1e6ab8e7674a5615 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: b9316f59852ff821cf621aca1e6ab8e7674a5615

Enable relocation overflow messages by default.

bfd/ChangeLog:

2016-06-23  Cupertino Miranda  <cmiranda@synopsys.com>
        elf32-arc.c: made PR_DEBUG always defined.

Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix grammar in error message.
@ 2016-07-12 10:20 sergiodj+buildbot
  2016-07-12 10:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f231881ea65232b3f67379326a5b605c465dffc4 ***

Author: Douglas B Rupp <rupp@adacore.com>
Branch: master
Commit: f231881ea65232b3f67379326a5b605c465dffc4

Fix grammar in error message.

	* binary.c (binary_set_section_contents): Fix grammar in warning
	message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add type casts to allow C++ compile.
@ 2016-07-12 13:25 sergiodj+buildbot
  2016-07-12 13:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 13:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1c51e367880f5065707a2a902b99c6508d19ef8 ***

Author: Chung-Lin Tang <cltang@codesourcery.com>
Branch: master
Commit: b1c51e367880f5065707a2a902b99c6508d19ef8

Add type casts to allow C++ compile.

	gdb/gdbserver/
	* linux-nios2-low.c (nios2_fill_gregset): Add type cast
	to buf parameter.
	(nios2_store_gregset): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Second fix for grammar in error message.
@ 2016-07-12 15:23 sergiodj+buildbot
  2016-07-12 16:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 15:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf143069f39b4feeeca175f88b6d1a5c1cb0fee4 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: cf143069f39b4feeeca175f88b6d1a5c1cb0fee4

Second fix for grammar in error message.

	* binary.c (binary_set_section_contents): Second grammar fix.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR python/19293 - invalidate frame cache when unwinders change
@ 2016-07-12 20:41 sergiodj+buildbot
  2016-07-12 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 20:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0f3fd7c44cebec7d787893b9c800e7de509cb32 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: e0f3fd7c44cebec7d787893b9c800e7de509cb32

PR python/19293 - invalidate frame cache when unwinders change

PR python/19293 notes that when a Python unwinder is disabled, the
frame cache is not invalidated.  This means that disabling an unwinder
doesn't have any immediate effect -- but in my experience it's often
the case that I want to enable or disable an unwinder in order to see
what happens.

This patch adds a new gdb.invalidate_cached_frames function and
arranges for the relevant bits of library code to call it.  I've only
partially documented this function, considering a warning sufficient
without going into all the reasons ordinary code should not call it.
The name of the new function was taken from a comment in frame.h next
to reinit_frame_cache.

No new test as I think the updates to the existing test are sufficient
to show that the code is working as intended.

Built and regtested on x86-64 Fedora 23.

2016-07-12  Tom Tromey  <tom@tromey.com>

	PR python/19293:
	* python/lib/gdb/command/unwinders.py (do_enable_unwinder): Call
	gdb.invalidate_cached_frames.
	* python/lib/gdb/unwinder.py (register_unwinder): Call
	gdb.invalidate_cached_frames.
	* python/python.c (gdbpy_invalidate_cached_frames): New function.
	(python_GdbMethods): Add entry for invalidate_cached_frames.

2016-07-12  Tom Tromey  <tom@tromey.com>

	PR python/19293:
	* python.texi (Frames In Python): Document
	gdb.invalidate_cached_frames.

2016-07-12  Tom Tromey  <tom@tromey.com>

	PR python/19293:
	* gdb.python/py-unwind-maint.exp: Update tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Align x86-64 .got/.got.plt sections to 8 bytes
@ 2016-07-12 23:02 sergiodj+buildbot
  2016-07-12 23:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 23:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37567a2cdd8823c5700ec83b757179083446bf07 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 37567a2cdd8823c5700ec83b757179083446bf07

Align x86-64 .got/.got.plt sections to 8 bytes

Align x86-64 .got and .got.plt sections to their entry size.

	* elf64-x86-64.c (elf_x86_64_create_dynamic_sections): Align
	.got/.got.plt sections to 8 bytes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes, gas: support for the ldtxa SPARC instructions.
@ 2016-07-13 14:28 sergiodj+buildbot
  2016-07-13 14:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 14:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e7ced37e756420742d51abb044c24d0f1929143 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 6e7ced37e756420742d51abb044c24d0f1929143

opcodes,gas: support for the ldtxa SPARC instructions.

This patch adds support for the LDTXA instructions, along with the
corresponding ASIs.  Tests for GAS are included.

opcodes/ChangeLog:

2016-07-12  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-opc.c (ldtxa): New macro.
	(sparc_opcodes): Use the macro defined above to add entries for
	the LDTXA instructions.
	(asi_table): Add the ASI_TWINX_* asis used in the LDTXA
	instruction.

gas/ChangeLog:

2016-07-12  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* testsuite/gas/sparc/ldtxa.s: New file.
	* testsuite/gas/sparc/ldtxa.d: Likewise.
	* testsuite/gas/sparc/sparc.exp: Execute the ldtxa test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/opcodes: Address issues with NAL disassembly
@ 2016-07-13 17:04 sergiodj+buildbot
  2016-07-13 17:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92281a5b06dd83a2a7d96ab8d83ae40b4e519acd ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 92281a5b06dd83a2a7d96ab8d83ae40b4e519acd

MIPS/opcodes: Address issues with NAL disassembly

Address issues with the disassembly of the NAL assembly idiom and R6
instruction introduced with commit 7361da2c952e ("Add support for MIPS
R6.") and then further tweaked with commit b9121b573e2e ("Add in a JALRC
alias and fix the NAL instruction.").  As from R6 this instruction has
replaced the encoding of `bltzal $0, . + 4' as the solely supported form
of the former BLTZAL instruction for the regular MIPS ISA.

The instruction is marked as an alias only in our regular MIPS opcode
table, making it fail to disassemble in R6 code if the `no-aliases'
machine option has been passed to `objdump':

$ cat test.s
	.text
foo:
	nal
$ as -mips64r6 -o test.o test.s
$ objdump -dr --prefix-addresses --show-raw-insn -M no-aliases test.o

nal.o:     file format elf32-tradbigmips

Disassembly of section .text:
00000000 <foo> 04100000 	0x4100000
	...
$

This is because the `bltzal' entry has been marked as pre-R6 only in the
opcode table and there is no other opcode pattern to match.

Additionally the changes referred made NAL replace the equivalent
`bltzal $0, . + 4' instruction in disassembly, unless the `no-aliases'
machine option has been used, in legacy code.  Seeing NAL, especially in
its updated form lacking the branch target argument, in the disassembly
of such code may be confusing to people.  This is because unlike with
EHB only used in R2 and newer code -- the machine encoding of which we
anyway always disassemble to its corresponding current architecture's
mnemonic rather than its legacy meaning of `sll $0, $0, 3' -- BLTZAL has
been indeed used in legacy code.  Even though `bltzal $0, . + 8' and its
machine code encoding (0x04100001) -- which is not equivalent to NAL and
still disassembles as BLTZAL -- has been the predominant form as opposed
to NAL's `bltzal $0, . + 4' (0x04100000), it makes sense to always keep
the old form in disassembly, while still accepting `nal' in assembly.

Remove the alias marking then from the the `nal' instruction pattern,
making it always match for R6 code, even with the `no-aliases' option.
And move the entry beyond the `bltzal' entry, making the latter one take
precedence for legacy binary code, while letting the former still match
any `nal' mnemonic in source code assembled for a legacy target.

Add a suitable test case to the GAS test suite.  While the change
affects the disassembler more than the assembler, so placing the test
case in the binutils test suite might be more appropriate, the intent is
also to verify that `nal' is still accepted by GAS for legacy targets,
plus we have test infrastructure available in the GAS test suite for
automatic multiple ISA level testing, which we lack from the binutils
framework.

	opcodes/
	* mips-opc.c (mips_builtin_opcodes): Remove the INSN2_ALIAS
	annotation from the "nal" entry and reorder it beyond "bltzal".

	gas/
	* testsuite/gas/mips/nal-1.d: New test.
	* testsuite/gas/mips/mipsr6@nal-1.d: New test.
	* testsuite/gas/mips/nal-2.d: New test.
	* testsuite/gas/mips/mipsr6@nal-2.d: New test.
	* testsuite/gas/mips/nal.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR cli/18053
@ 2016-07-13 19:38 sergiodj+buildbot
  2016-07-13 19:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 19:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6571a3815623d907b7a3f560e909edd8c76a9e1c ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6571a3815623d907b7a3f560e909edd8c76a9e1c

Fix PR cli/18053

PR cli/18053 concerns a couple of minor bugs in the JIT debuginfo
support.  First, jit-reader-load should use filename completion and
support tilde expansion.  Second, the help for jit-reader-unload is
incorrect.  While working on this I also realized that
jit-reader-unload should use the no-op completer, so I've included
that as well.

Built and regtested on x86-64 Fedora 23.  A completer test for
jit-reader-load is included, but not a tilde-expansion test, as I
couldn't think of a reliable way to test that.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR cli/18053:
	* jit.c (jit_reader_load_command): Use tilde_expand.
	(_initialize_jit): Fix help for jit-reader-unload.  Set completer
	for new commands.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR cli/18053:
	* gdb.base/jit-so.exp (one_jit_test): Add jit-reader-load
	completion test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] use user_breakpoint_p in python code
@ 2016-07-13 20:39 sergiodj+buildbot
  2016-07-13 20:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 20:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43684a7b844bce64735940b55b667f7086fa3d44 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 43684a7b844bce64735940b55b667f7086fa3d44

use user_breakpoint_p in python code

I noticed that bppy_get_visibility and gdbpy_breakpoint_created
implemented their own visibility checks, but subtly different from
user_breakpoint_p.  I think the latter is more correct, and so changed
the Python code to use it.

I suspect there isn't a decent way to test this, so no new test.

Built and regtested on x86-64 Fedora 23.

2016-07-13  Tom Tromey  <tom@tromey.com>

	* python/py-breakpoint.c (bppy_get_visibility)
	(gdbpy_breakpoint_created): Use user_breakpoint_p.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR python/17698 - add Breakpoint.pending
@ 2016-07-13 20:53 sergiodj+buildbot
  2016-07-13 22:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 20:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93daf339a4d9496ecde15d3b1e852fbdb38c07d0 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 93daf339a4d9496ecde15d3b1e852fbdb38c07d0

PR python/17698 - add Breakpoint.pending

This patch adds a "pending" attribute to gdb.Breakpoint.

Built and regtested on x86-64 Fedora 23.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR python/17698:
	* NEWS: Update.
	* python/py-breakpoint.c (bppy_get_pending): New function.
	(breakpoint_object_getset): Add entry for "pending".
	* breakpoint.h (pending_breakpoint_p): Declare.
	* breakpoint.c (pending_breakpoint_p): New function.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR python/17698:
	* python.texi (Breakpoints In Python): Document
	Breakpoint.pending.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR python/17698:
	* gdb.python/py-breakpoint.exp (test_bkpt_basic): Add "pending"
	test.
	(test_watchpoints): Likewise.
	(test_bkpt_pending): New proc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Small improvements to the ARM simulator to cope with illegal binaries.
@ 2016-07-14  9:52 sergiodj+buildbot
  2016-07-14 10:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-14  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7df94786e4723ba93d8982e55fc5e652b4b80142 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 7df94786e4723ba93d8982e55fc5e652b4b80142

Small improvements to the ARM simulator to cope with illegal binaries.

	* armemu.c (Multiply64): Only issue error messages about invalid
	arguments if debugging is enabled.
	* armos.c (ARMul_OSHandleSWI): Ignore invalid flags.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add one use of ATTRIBUTE_UNUSED
@ 2016-07-14 17:26 sergiodj+buildbot
  2016-07-14 18:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 821fc4aeef26bc7e5d5943c2f5d009a23e16883c ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 821fc4aeef26bc7e5d5943c2f5d009a23e16883c

Add one use of ATTRIBUTE_UNUSED

One spot needed ATTRIBUTE_UNUSED to cope with the new warnings.

The case in inflow.c is just a mass of ifdefs; and while the only use
of "result" is guarded by "#if 0", I thought it simplest to leave it
all in place.

2016-07-14  Tom Tromey  <tom@tromey.com>

	* inflow.c (child_terminal_ours_1): Use ATTRIBUTE_UNUSED.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change reopen_exec_file to check result of stat
@ 2016-07-14 17:32 sergiodj+buildbot
  2016-07-14 17:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 17:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 537d9b851957475a8122949939023c81b1df1673 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 537d9b851957475a8122949939023c81b1df1673

Change reopen_exec_file to check result of stat

This seems to be a real bug found by -Wunused-but-set-variable.  If
"stat" fails for some reason, gdb would use the uninitialized "st".

2016-07-14  Tom Tromey  <tom@tromey.com>

	* corefile.c (reopen_exec_file): Only examine st.st_mtime if stat
	succeeded.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add missing newline to py-breakpoint.c
@ 2016-07-14 20:44 sergiodj+buildbot
  2016-07-14 23:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 20:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f131b39970944cb53b407715880d333c5248cac ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 7f131b39970944cb53b407715880d333c5248cac

Add missing newline to py-breakpoint.c

In https://sourceware.org/ml/gdb-patches/2016-07/msg00152.html,
Yao noted that a patch of mine was missing a newline.

I thought I had fixed this but when looking today I realized it was
not fixed.  This patch adds it.

I'm checking this in as obvious.

2016-07-14  Tom Tromey  <tom@tromey.com>

	* python/py-breakpoint.c (gdbpy_breakpoint_deleted): Add missing
	newline.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove some variables but call functions for side effects
@ 2016-07-14 21:08 sergiodj+buildbot
  2016-07-14 21:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 21:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac29888840f025448225e600d4cf99e126386878 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: ac29888840f025448225e600d4cf99e126386878

Remove some variables but call functions for side effects

This patch consolidates the (possibly-questionable) spots where we
remove a declaration but continue to call some function for side
effects.  In a couple of cases it wasn't entirely clear to me that
this mattered; and in some other cases it might be more aesthetically
pleasing to use ATTRIBUTE_UNUSED.  So, I broke this out into a
separate patch for simpler review.

2016-07-14  Tom Tromey  <tom@tromey.com>

	* arch-utils.c (default_skip_permanent_breakpoint): Remove
	"bp_insn".
	* disasm.c (do_assembly_only): Remove "num_displayed".
	* dwarf2read.c (read_abbrev_offset): Remove "length".
	(dwarf_decode_macro_bytes) <DW_MACINFO_vendor_ext>: Remove
	"constant".
	* m32c-tdep.c (make_regs): Remove "r2hl", "r3hl", and "intbhl".
	* microblaze-tdep.c (microblaze_frame_cache): Remove "func".
	* tracefile.c (trace_save): Remove "status".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] BFD: Let targets handle relocations against absolute symbols
@ 2016-07-14 21:44 sergiodj+buildbot
  2016-07-15  0:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c117286270e8166022900f4e5fef89719ccd2dc ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 0c117286270e8166022900f4e5fef89719ccd2dc

BFD: Let targets handle relocations against absolute symbols

Fix a generic BFD issue with relocations against absolute symbols, which
are installed without using any individual relocation handler provided
by the backend.  This causes any absolute section's addend to be lost on
REL targets such as o32 MIPS, and also relocation-specific calculation
adjustments are not made.

As an example assembling this program:

$ cat test.s
	.text
foo:
	b	bar
	b	baz

	.set	bar, 0x1234
$ as -EB -32 -o test-o32.o test.s
$ as -EB -n32 -o test-n32.o test.s

produces this binary code:

$ objdump -dr test-o32.o test-n32.o

test-o32.o:     file format elf32-tradbigmips

Disassembly of section .text:

00000000 <foo>:
   0:	10000000 	b	4 <foo+0x4>
			0: R_MIPS_PC16	*ABS*
   4:	00000000 	nop
   8:	1000ffff 	b	8 <foo+0x8>
			8: R_MIPS_PC16	baz
   c:	00000000 	nop

test-n32.o:     file format elf32-ntradbigmips

Disassembly of section .text:

00000000 <foo>:
   0:	10000000 	b	4 <foo+0x4>
			0: R_MIPS_PC16	*ABS*+0x1230
   4:	00000000 	nop
   8:	10000000 	b	c <foo+0xc>
			8: R_MIPS_PC16	baz-0x4
   c:	00000000 	nop
$

where it is clearly visible in `test-o32.o', which uses REL relocations,
that the absolute section's addend equivalent to the value of `bar' -- a
reference to which cannot be fully resolved at the assembly time,
because the reference is PC-relative -- has been lost, as has been the
relocation-specific adjustment of -4, required to take into account the
PC+4-relative calculation made by hardware with branches and seen in the
external symbol reference to `baz' as the `ffff' addend encoded in the
instruction word.  In `test-n32.o', which uses RELA relocations, the
absolute section's addend has been correctly retained.

Give precedence then in `bfd_perform_relocation' and
`bfd_install_relocation' to any individual relocation handler the
backend selected may have provided, while still resorting to the generic
calculation otherwise.  This retains the semantics which we've had since
forever or before the beginning of our repository history, and is at the
very least compatible with `bfd_elf_generic_reloc' being used as the
handler.

Retain the `bfd_is_und_section' check unchanged at the beginning of
`bfd_perform_relocation' since this does not affect the semantics of the
function.  The check returns the same `bfd_reloc_undefined' code the
check for a null `howto' does, so swapping the two does not matter.
Also the check is is mutually exclusive with the `bfd_is_abs_section'
check, since a section cannot be absolute and undefined both at once, so
swapping the two does not matter either.

With this change applied the program quoted above now has the in-place
addend correctly calculated and installed in the field being relocated:

$ objdump -dr fixed-o32.o

fixed-o32.o:     file format elf32-tradbigmips

Disassembly of section .text:

00000000 <foo>:
   0:	1000048c 	b	1234 <bar>
			0: R_MIPS_PC16	*ABS*
   4:	00000000 	nop
   8:	1000ffff 	b	8 <foo+0x8>
			8: R_MIPS_PC16	baz
   c:	00000000 	nop
$

Add a set of MIPS tests to cover the relevant cases, including absolute
symbols with addends, and verifying that PC-relative relocations against
symbols concerned resolve to the same value in the final link regardless
of whether the REL or the RELA relocation form is used.  Exclude linker
tests though which would overflow the in-place addend on REL targets and
use them as dump patterns for RELA targets only.

	bfd/
	* reloc.c (bfd_perform_relocation): Try the `howto' handler
	first with relocations against absolute symbols.
	(bfd_install_relocation): Likewise.

	gas/
	* testsuite/gas/mips/mips16-branch-absolute.d: Update patterns.
	* testsuite/gas/mips/branch-absolute.d: New test.
	* testsuite/gas/mips/branch-absolute-n32.d: New test.
	* testsuite/gas/mips/branch-absolute-n64.d: New test.
	* testsuite/gas/mips/branch-absolute-addend-n32.d: New test.
	* testsuite/gas/mips/branch-absolute-addend-n64.d: New test.
	* testsuite/gas/mips/mips16-branch-absolute-n32.d: New test.
	* testsuite/gas/mips/mips16-branch-absolute-n64.d: New test.
	* testsuite/gas/mips/mips16-branch-absolute-addend-n32.d: New
	test.
	* testsuite/gas/mips/mips16-branch-absolute-addend-n64.d: New
	test.
	* testsuite/gas/mips/micromips-branch-absolute.d: New test.
	* testsuite/gas/mips/micromips-branch-absolute-n32.d: New test.
	* testsuite/gas/mips/micromips-branch-absolute-n64.d: New test.
	* testsuite/gas/mips/micromips-branch-absolute-addend-n32.d: New
	test.
	* testsuite/gas/mips/micromips-branch-absolute-addend-n64.d: New
	test.
	* testsuite/gas/mips/branch-absolute.s: New test source.
	* testsuite/gas/mips/branch-absolute-addend.s: New test source.
	* testsuite/gas/mips/mips16-branch-absolute-addend.s: New test
	source.
	* testsuite/gas/mips/micromips-branch-absolute.s: New test
	source.
	* testsuite/gas/mips/micromips-branch-absolute-addend.s: New
	test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/branch-absolute.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-n32.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-n64.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-addend.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-addend-n32.d: New test.
	* testsuite/ld-mips-elf/branch-absolute-addend-n64.d: New test.
	* testsuite/ld-mips-elf/micromips-branch-absolute.d: New test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-n32.d: New
	test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-n64.d: New
	test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-addend.d: New
	test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-addend-n32.d:
	New test.
	* testsuite/ld-mips-elf/micromips-branch-absolute-addend-n64.d:
	New test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests, except
	from `branch-absolute-addend' and
	`micromips-branch-absolute-addend', referred indirectly only.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] COFF buffer overflow in mark_relocs
@ 2016-07-15 10:05 sergiodj+buildbot
  2016-07-15 10:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 10:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06ab6faf83ce47ca64198819eee02e4e56dc5a74 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 06ab6faf83ce47ca64198819eee02e4e56dc5a74

COFF buffer overflow in mark_relocs

	* cofflink.c (mark_relocs): Exclude relocs with -1 r_symndx
	from marking sym_indices.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Tidy up debugging in the ARC port of the BFD library.
@ 2016-07-15 11:25 sergiodj+buildbot
  2016-07-15 11:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7e8b360fe6dd93aae7cb4af554dc66364da4fe0 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: f7e8b360fe6dd93aae7cb4af554dc66364da4fe0

Tidy up debugging in the ARC port of the BFD library.

bfd	* elf32-arc.c (PR_DEBUG): Delete.
	Fix printing of debug information.  Fix formatting of debug
	statements.
	(debug_arc_reloc): Handle symbols that are not from an input file.
	(arc_do_relocation): Remove excessive exclamation points.
	(elf_arc_relocate_section): Print an informative message if the
	relocation fails, even if debugging is not enabled.
	* arc-got.h: Fix formatting.  Fix printing of debug information.
	(new_got_entry_to_list): Use xmalloc.
	* config.bfd: use the big-endian arc vector as the default vector
	for big-endian arc targets.

ld	* testsuite/ld-arc/arc.exp: Always run the sda-relocs test in
	little endian mode.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Pass SIGLIBRT directly to child processes.
@ 2016-07-15 14:01 sergiodj+buildbot
  2016-07-15 14:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 14:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc7b765ab71f967eb2a9c3da111d7529eec46fbe ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: bc7b765ab71f967eb2a9c3da111d7529eec46fbe

Pass SIGLIBRT directly to child processes.

FreeBSD's librt uses SIGLIBRT as an internal signal to implement
SIGEV_THREAD sigevent notifications.  Similar to SIGLWP or SIGCANCEL
this signal should be passed through to child processes by default.

include/ChangeLog:

	* signals.def: Add GDB_SIGNAL_LIBRT.

gdb/ChangeLog:

	* common/signals.c (gdb_signal_from_host): Handle SIGLIBRT.
	(do_gdb_signal_to_host): Likewise.
	* infrun.c (_initialize_infrun): Pass GDB_SIGNAL_LIBRT through to
	programs.
	* proc-events.c (signal_table): Add entry for SIGLIBRT.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] GDB testsuite: Escape paths used in regular expressions
@ 2016-07-15 18:48 sergiodj+buildbot
  2016-07-15 18:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37539ebee2ea9fc0daceaae1074a79de88d563fb ***

Author: Don Breazeal <donb@codesourcery.com>
Branch: master
Commit: 37539ebee2ea9fc0daceaae1074a79de88d563fb

GDB testsuite: Escape paths used in regular expressions

This patch fixes problems with a few GDB testsuites when executing in a
path that contains special characters (e.g. "++").  When such paths are
used as a regular expression, the regular expression parser will choke
and cause the tests to fail.  This patch uses string_to_regexp to
escape strings that will be used as regular expressions, in order to
sanitize path names used in expect scripts.

2016-07-15  Zachary Welch  <zwelch@codesourcery.com>
	    Don Breazeal <donb@codesourcery.com>

	gdb/testsuite/ChangeLog:
	* gdb.base/maint.exp: Escape paths used in regular expressions.
	* gdb.stabs/weird.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't include libbfd.h outside of bfd, part 2
@ 2016-07-16 14:06 sergiodj+buildbot
  2016-07-16 14:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-16 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00dad9a491b3bb0069b5a1471b8f32052e071965 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 00dad9a491b3bb0069b5a1471b8f32052e071965

Don't include libbfd.h outside of bfd, part 2

Make bfd_default_set_arch_mach available to a bunch of gas backend
files.

bfd/
	* archures.c (bfd_default_set_arch_mach): Make available in bfd.h.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Regenerate.
gas/
	* config/tc-epiphany.c: Don't include libbfd.h.
	* config/tc-frv.c: Likewise.
	* config/tc-ip2k.c: Likewise.
	* config/tc-iq2000.c: Likewise.
	* config/tc-m32c.c: Likewise.
	* config/tc-mep.c: Likewise.
	* config/tc-mt.c: Likewise.
	* config/tc-nios2.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't include libbfd.h outside of bfd, part 6
@ 2016-07-16 15:07 sergiodj+buildbot
  2016-07-16 16:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-16 15:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d0b9ebc1e0079271a7c7737b53bc026525eab64 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7d0b9ebc1e0079271a7c7737b53bc026525eab64

Don't include libbfd.h outside of bfd, part 6

Some messing with plugin code in order to not need arelt_size in
ld code.  File descriptor handling in ld/plugin.c is tidied too,
simply duping the open fd rather than opening the file again.

bfd/
	* elflink.c: Include plugin-api.h.
	* plugin.c (bfd_plugin_open_input): New function, extracted from..
	(try_claim): ..here.
	* plugin.h: Don't include bfd.h.
	(bfd_plugin_open_input): Declare.
binutils/
	* ar.c: Include plugin-api.h.
	* nm.c: Likewise.
ld/
	* plugin.c: Don't include libbfd.h.  Include plugin-api.h
	before bfd/plugin.h.
	(plugin_object_p): Use bfd_plugin_open_input.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update PC when simulate break instruction.
@ 2016-07-19  8:17 sergiodj+buildbot
  2016-07-19  8:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-19  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59f48f5a45d2300da401f1fccab31ba436217469 ***

Author: Denis Chertykov <chertykov@gmail.com>
Branch: master
Commit: 59f48f5a45d2300da401f1fccab31ba436217469

Update PC when simulate break instruction.

	PR target/ 19401
	* avr/interp.c (step_once): Pass break instruction address to
	sim_engine_halt function which writes that to PC. Remove code that
	follows that function call as it is unreachable.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use do_self_tests in selftest.exp
@ 2016-07-19 10:01 sergiodj+buildbot
  2016-07-19 10:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-19 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f25827c194fe9894f2c65f7e1101854022be4328 ***

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

Use do_self_tests in selftest.exp

This patch uses do_self_tests to simplify selftest.exp.  It doesn't
change the tests except the order,

-PASS: gdb.gdb/selftest.exp: Disassemble main
 PASS: gdb.gdb/selftest.exp: breakpoint in captured_main
+PASS: gdb.gdb/selftest.exp: run until breakpoint at captured_main
+PASS: gdb.gdb/selftest.exp: Disassemble main
 PASS: gdb.gdb/selftest.exp: set interrupt character in test_with_self
 PASS: gdb.gdb/selftest.exp: set listsize to 1
-PASS: gdb.gdb/selftest.exp: run until breakpoint at captured_main

gdb/testsuite:

2016-07-19  Yao Qi  <yao.qi@linaro.org>

	* gdb.gdb/selftest.exp: Remove checks on is_remote and isnative.
	(test_with_self): Remove some code.  Remove argument executable.
	(top-level): Use do_self_tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS: Verify the ISA mode and alignment of branch and jump targets
@ 2016-07-19 14:34 sergiodj+buildbot
  2016-07-19 15:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-19 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d862524f6ae9703fe8e264dd4785756d358570a ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 9d862524f6ae9703fe8e264dd4785756d358570a

MIPS: Verify the ISA mode and alignment of branch and jump targets

Verify that the ISA mode of branch targets is the same as the referring
relocation, so that an attempt to produce a branch between instructions
encoded in different ISA modes each causes an error rather than silently
producing non-functional code.  Make sure that no symbol or addend bits
are silently truncated: terminate with an error if the relocation value
calculated cannot be encoded in the relocatable field of a branch; for
REL targets also applying to any intermediate addend.

Also make jump target's alignment verification consistent with that for
branches.

This change will require an update to some obscure handcoded assembly
sources which make branches to labels placed at data objects, however
for microMIPS code only.  These labels will have to be updated with the
`.insn' directive for containing code to assemble and link successfully.
Such code is broken as any such labels have always been required by the
microMIPS architecture specification[1][2] to be annotated this way for
correct interpretation, and with our old code missing `.insn' directives
caused labels to present different semantics depending on whether they
were referred with branch (ISA bit ignored) or other relocations (ISA
bit respected).

Enforcing these checks however will ensure errors in building software,
like mixed regular MIPS and microMIPS code links with branches between,
will be diagnosed at the build time rather than causing odd run-time
errors such as intermittent crashes.  It will also let cross-mode BAL
instructions be converted to JALX instructions, with a separate change.

References:

[1] "MIPS Architecture for Programmers, Volume II-B: The microMIPS32
    Instruction Set", MIPS Technologies, Inc., Document Number: MD00582,
    Revision 5.04, January 15, 2014, Section 7.1 "Assembly-Level
    Compatibility", p. 533

[2] "MIPS Architecture for Programmers, Volume II-B: The microMIPS64
    Instruction Set", MIPS Technologies, Inc., Document Number: MD00594,
    Revision 5.04, January 15, 2014, Section 8.1 "Assembly-Level
    Compatibility", p. 623

	bfd/
	* elfxx-mips.c (b_reloc_p): Add R_MICROMIPS_PC16_S1,
	R_MICROMIPS_PC10_S1 and R_MICROMIPS_PC7_S1.
	(branch_reloc_p): New function.
	(mips_elf_calculate_relocation): Handle ISA mode determination
	for relocations against section symbols, against absolute
	symbols and absolute relocations.  Also set `*cross_mode_jump_p'
	for branches.
	<R_MIPS16_26, R_MIPS_26, R_MICROMIPS_26_S1>: Suppress alignment
	checks for weak undefined symbols.  Also check target alignment
	within the same ISA mode.
	<R_MIPS_PC16, R_MIPS_GNU_REL16_S2>: Handle cross-mode branches
	in the alignment check.
	<R_MICROMIPS_PC7_S1>: Add an alignment check.
	<R_MICROMIPS_PC10_S1>: Likewise.
	<R_MICROMIPS_PC16_S1>: Likewise.
	(mips_elf_perform_relocation): Report a failure for unsupported
	same-mode JALX instructions and cross-mode branches.
	(_bfd_mips_elf_relocate_section) <bfd_reloc_outofrange>: Add
	error messages for jumps to misaligned addresses.

	gas/
	* config/tc-mips.c (mips_force_relocation): Also retain branch
	relocations against MIPS16 and microMIPS symbols.
	(fix_bad_cross_mode_jump_p): New function.
	(fix_bad_same_mode_jalx_p): Likewise.
	(fix_bad_misaligned_jump_p): Likewise.
	(fix_bad_cross_mode_branch_p): Likewise.
	(fix_bad_misaligned_branch_p): Likewise.
	(fix_validate_branch): Likewise.
	(md_apply_fix) <BFD_RELOC_MIPS_JMP, BFD_RELOC_MIPS16_JMP>
	<BFD_RELOC_MICROMIPS_JMP>: Separate from BFD_RELOC_MIPS_SHIFT5,
	etc.  Verify the ISA mode and alignment of the jump target.
	<BFD_RELOC_MIPS_21_PCREL_S2>: Replace the inline alignment check
	with a call to `fix_validate_branch'.
	<BFD_RELOC_MIPS_26_PCREL_S2>: Likewise.
	<BFD_RELOC_16_PCREL_S2>: Likewise.
	<BFD_RELOC_MICROMIPS_7_PCREL_S1, BFD_RELOC_MICROMIPS_10_PCREL_S1>
	<BFD_RELOC_MICROMIPS_16_PCREL_S1>: Retain the original addend.
	Verify the ISA mode and alignment of the branch target.
	(md_convert_frag): Verify the ISA mode and alignment of resolved
	MIPS16 branch targets.
	* testsuite/gas/mips/branch-misc-1.s: Annotate non-instruction
	branch targets with `.insn'.
	* testsuite/gas/mips/branch-misc-5.s: Likewise.
	* testsuite/gas/mips/micromips@branch-misc-5-64.d: Update
	accordingly.
	* testsuite/gas/mips/micromips@branch-misc-5pic-64.d: Likewise.
	* testsuite/gas/mips/micromips-branch-relax.s: Annotate
	non-instruction branch target with `.insn'.
	* testsuite/gas/mips/micromips.s: Replace microMIPS JALX targets
	with external symbols.
	* testsuite/gas/mips/micromips-insn32.d: Update accordingly.
	* testsuite/gas/mips/micromips-noinsn32.d: Likewise.
	* testsuite/gas/mips/micromips-trap.d: Likewise.
	* testsuite/gas/mips/micromips.d: Likewise.
	* testsuite/gas/mips/mips16.s: Annotate non-instruction branch
	targets with `.insn'.
	* testsuite/gas/mips/mips16.d: Update accordingly.
	* testsuite/gas/mips/mips16-64.d: Likewise.
	* testsuite/gas/mips/mips16-dwarf2.s: Annotate non-instruction
	branch target with `.insn'.
	* testsuite/gas/mips/relax-swap3.s: Likewise.
	* testsuite/gas/mips/branch-local-2.l: New list test.
	* testsuite/gas/mips/branch-local-3.l: New list test.
	* testsuite/gas/mips/branch-local-n32-2.l: New list test.
	* testsuite/gas/mips/branch-local-n32-3.l: New list test.
	* testsuite/gas/mips/branch-local-n64-2.l: New list test.
	* testsuite/gas/mips/branch-local-n64-3.l: New list test.
	* testsuite/gas/mips/unaligned-jump-1.l: New list test.
	* testsuite/gas/mips/unaligned-jump-2.l: New list test.
	* testsuite/gas/mips/unaligned-jump-3.d: New test.
	* testsuite/gas/mips/unaligned-jump-mips16-1.l: New list test.
	* testsuite/gas/mips/unaligned-jump-mips16-2.l: New list test.
	* testsuite/gas/mips/unaligned-jump-mips16-3.d: New test.
	* testsuite/gas/mips/unaligned-jump-micromips-1.l: New list
	test.
	* testsuite/gas/mips/unaligned-jump-micromips-2.l: New list
	test.
	* testsuite/gas/mips/unaligned-jump-micromips-3.d: New test.
	* testsuite/gas/mips/unaligned-branch-1.l: New list test.
	* testsuite/gas/mips/unaligned-branch-2.l: New list test.
	* testsuite/gas/mips/unaligned-branch-3.d: New test.
	* testsuite/gas/mips/unaligned-branch-r6-1.l: New list test.
	* testsuite/gas/mips/unaligned-branch-r6-2.l: New list test.
	* testsuite/gas/mips/unaligned-branch-r6-3.l: New list test.
	* testsuite/gas/mips/unaligned-branch-r6-4.l: New list test.
	* testsuite/gas/mips/unaligned-branch-r6-5.d: New test.
	* testsuite/gas/mips/unaligned-branch-r6-6.d: New test.
	* testsuite/gas/mips/unaligned-branch-mips16-1.l: New list test.
	* testsuite/gas/mips/unaligned-branch-mips16-2.l: New list test.
	* testsuite/gas/mips/unaligned-branch-mips16-3.d: New test.
	* testsuite/gas/mips/unaligned-branch-micromips-1.l: New list
	test.
	* testsuite/gas/mips/unaligned-branch-micromips-2.l: New list
	test.
	* testsuite/gas/mips/unaligned-branch-micromips-3.d: New test.
	* testsuite/gas/mips/branch-local-2.s: New test source.
	* testsuite/gas/mips/branch-local-3.s: New test source.
	* testsuite/gas/mips/branch-local-n32-2.s: New test source.
	* testsuite/gas/mips/branch-local-n32-3.s: New test source.
	* testsuite/gas/mips/branch-local-n64-2.s: New test source.
	* testsuite/gas/mips/branch-local-n64-3.s: New test source.
	* testsuite/gas/mips/unaligned-jump-1.s: New test source.
	* testsuite/gas/mips/unaligned-jump-2.s: New test source.
	* testsuite/gas/mips/unaligned-jump-mips16-1.s: New test source.
	* testsuite/gas/mips/unaligned-jump-mips16-2.s: New test source.
	* testsuite/gas/mips/unaligned-jump-micromips-1.s: New test
	source.
	* testsuite/gas/mips/unaligned-jump-micromips-2.s: New test
	source.
	* testsuite/gas/mips/unaligned-branch-1.s: New test source.
	* testsuite/gas/mips/unaligned-branch-2.s: New test source.
	* testsuite/gas/mips/unaligned-branch-r6-1.s: New test source.
	* testsuite/gas/mips/unaligned-branch-r6-2.s: New test source.
	* testsuite/gas/mips/unaligned-branch-r6-3.s: New test source.
	* testsuite/gas/mips/unaligned-branch-r6-4.s: New test source.
	* testsuite/gas/mips/unaligned-branch-mips16-1.s: New test
	source.
	* testsuite/gas/mips/unaligned-branch-mips16-2.s: New test
	source.
	* testsuite/gas/mips/unaligned-branch-micromips-1.s: New test
	source.
	* testsuite/gas/mips/unaligned-branch-micromips-2.s: New test
	source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/unaligned-jalx-1.d: Update error message
	expected.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-mips16-1.d:
	Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-micromips-1.d:
	Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-mips16-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-jalx-micromips-1.d: Likewise.
	* testsuite/ld-mips-elf/undefweak-overflow.s: Add jumps,
	microMIPS BAL and MIPS16 instructions.
	* testsuite/ld-mips-elf/undefweak-overflow.d: Update
	accordingly.
	* testsuite/ld-mips-elf/unaligned-branch-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-branch-r6-1.d: New test.
	* testsuite/ld-mips-elf/unaligned-branch-r6-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-branch-mips16.d: New test.
	* testsuite/ld-mips-elf/unaligned-branch-micromips.d: New test.
	* testsuite/ld-mips-elf/unaligned-jump-mips16.d: New test.
	* testsuite/ld-mips-elf/unaligned-jump-micromips.d: New test.
	* testsuite/ld-mips-elf/unaligned-jump.d: New test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS: Convert cross-mode BAL to JALX
@ 2016-07-19 16:20 sergiodj+buildbot
  2016-07-19 16:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-19 16:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6ebf6169a1bd14724b9ac49990089542396f576 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: a6ebf6169a1bd14724b9ac49990089542396f576

MIPS: Convert cross-mode BAL to JALX

Convert cross-mode regular MIPS and microMIPS BAL instructions to JALX,
similarly to how JAL instructions are converted.

	bfd/
	* elfxx-mips.c (mips_elf_perform_relocation): Convert cross-mode
	BAL to JALX.
	(_bfd_mips_elf_relocate_section) <bfd_reloc_outofrange>: Add a
	corresponding error message.

	gas/
	* config/tc-mips.c (mips_force_relocation, mips_fix_adjustable):
	Adjust comments for BAL to JALX linker conversion.
	(fix_bad_cross_mode_branch_p): Accept cross-mode BAL.
	* testsuite/gas/mips/unaligned-branch-1.l: Update error messages
	expected.
	* testsuite/gas/mips/unaligned-branch-micromips-1.l: Likewise.
	* testsuite/gas/mips/branch-local-4.d: New test.
	* testsuite/gas/mips/branch-local-n32-4.d: New test.
	* testsuite/gas/mips/branch-local-n64-4.d: New test.
	* testsuite/gas/mips/branch-addend.d: New test.
	* testsuite/gas/mips/branch-addend-n32.d: New test.
	* testsuite/gas/mips/branch-addend-n64.d: New test.
	* testsuite/gas/mips/branch-local-4.s: New test source.
	* testsuite/gas/mips/branch-addend.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

	ld/
	* testsuite/ld-mips-elf/unaligned-branch-2.d: Update error
	messages expected.
	* testsuite/ld-mips-elf/unaligned-branch-r6-1.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-branch-mips16.d: Likewise.
	* testsuite/ld-mips-elf/unaligned-branch-micromips.d: Likewise.
	* testsuite/ld-mips-elf/bal-jalx-addend.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-local.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-pic.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-addend-n32.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-local-n32.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-pic-n32.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-addend-n64.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-local-n64.d: New test.
	* testsuite/ld-mips-elf/bal-jalx-pic-n64.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-3.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-2.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-3.d: New test.
	* testsuite/ld-mips-elf/unaligned-jalx-2.s: New test source.
	* testsuite/ld-mips-elf/unaligned-jalx-3.s: New test source.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-2.s: New test
	source.
	* testsuite/ld-mips-elf/unaligned-jalx-addend-3.s: New test
	source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Build gdb.opt/inline-*.exp tests at -O0, rely on __attribute__((always_inline))
@ 2016-07-19 18:00 sergiodj+buildbot
  2016-07-19 18:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-19 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f960ced9a3e4aa0823dcc234d9de49aebaee055 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1f960ced9a3e4aa0823dcc234d9de49aebaee055

Build gdb.opt/inline-*.exp tests at -O0, rely on __attribute__((always_inline))

A test recently added to gdb.opt/inline-cmds.exp fails for
arm-none-eabi targets because -O2 leads to instructions to be
reordered widely.

I guess it might have made sense years ago to enable optimization in
these tests, but I fail to see the need for that nowadays.

Using -O0 while relying on __attribute__((always_inline)), which is
already used in the tests [1] [2], avoids this sort of trouble, while
still exercising the inlining-related use cases that are the focus of
these tests.

I think that nowadays we can safely assume that all compilers we care
about support __attribute__((always_inline)) or similar.

[1] - Except one spot that missed it.

[2] - Note that the .exp files make sure the frames that should have
      been inlined are indeed inlined, with "info frame".

gdb/testsuite/ChangeLog:
2016-07-19  Pedro Alves  <palves@redhat.com>

	* gdb.opt/inline-break.exp: Remove optimize=-O2.
	* gdb.opt/inline-bt.exp: Likewise.
	* gdb.opt/inline-cmds.exp: Remove optimize=-O2 and add
	additional_flags=-Winline.
	* gdb.opt/inline-locals.exp: Likewise.
	* gdb.opt/inline-markers.c (ATTR): Define.
	(inlined_fn): Use it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Mark some more powerpc relocs as not handled by generic linker
@ 2016-07-20  4:10 sergiodj+buildbot
  2016-07-20  4:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20  4:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ce512885ba76da53fae84cd1a555bc721fdd25e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3ce512885ba76da53fae84cd1a555bc721fdd25e

Mark some more powerpc relocs as not handled by generic linker

	* elf64-ppc.c (ppc64_elf_howto_raw <R_PPC64_PLTREL32>): Put
	ppc64_elf_unhandled_reloc for special_function.
	* elf32-ppc.c (ppc_elf_howto_raw): Similarly for lots of relocs.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite patch: Skip py-unwind.exp on x86_64 -m32
@ 2016-07-20 15:41 sergiodj+buildbot
  2016-07-20 15:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72b5d09937fa2dac8ca7c801b9ddefe1b0176b6f ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 72b5d09937fa2dac8ca7c801b9ddefe1b0176b6f

testsuite patch: Skip py-unwind.exp on x86_64 -m32

(gdb) source /home/jkratoch/redhat/gdb-clean/gdb/testsuite/outputs/gdb.python/py-unwind/py-unwind.py^M
Python script imported^M
Python Exception <type 'exceptions.ValueError'> Bad register: ^M
(gdb) FAIL: gdb.python/py-unwind.exp: import python scripts

class TestUnwinder(Unwinder):
    AMD64_RBP = 6
    AMD64_RSP = 7
    AMD64_RIP = 16

On Tue, 19 Jul 2016 12:06:09 +0200, Yao Qi wrote:
py-unwind.exp does nothing on arch specific thing, so py-unwind.exp shouldn't
be aware of the arch difference, but py-unwind.py should.

On Tue, 19 Jul 2016 20:04:33 +0200, Pedro Alves wrote:
How about we handle this in the .exp file for now and leave something
more complicated for when the test is first ported to some other
arch.  WDYT?

gdb/testsuite/ChangeLog
2016-07-20  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.python/py-unwind.exp: Test also ![is_lp64_target].


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
@ 2016-07-20 16:06 sergiodj+buildbot
  2016-07-20 17:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 16:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7674d381b47f9f2411c0ca1da0c152940dc0d7bd ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 7674d381b47f9f2411c0ca1da0c152940dc0d7bd

testsuite: Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32

$ runtest 'CC_FOR_TARGET=gcc -m32' gdb.btrace/tailcall-only.exp
Running ./gdb.btrace/tailcall-only.exp ...
gdb compile failed, tailcall-only.c: Assembler messages:
tailcall-only.c:142: Error: cannot represent relocation type BFD_RELOC_64
[...]
tailcall-only.c:425: Error: cannot represent relocation type BFD_RELOC_64

It works for the other x86 arch combinations:

On Mon, 11 Apr 2016 08:44:23 +0200, Metzger, Markus T wrote:
I'm setting the target triplet to "i686-unknown-linux" in my m32 configuration.
Like this:

set target_triplet "i686-unknown-linux"
set_board_info cflags "-m32"
set_board_info cppflags "-m32"

On Wed, 20 Jul 2016 16:02:20 +0200, Pedro Alves wrote:
There's no reason you should _not_ set it.

But, multilib-style testing with --target_board=unix\{-m64,-m32\} etc.
should work _too_, IMO.

gdb/testsuite/ChangeLog
2016-07-20  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.btrace/tailcall-only.exp: Use is_lp64_target check.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix gdb.gdb/selftest.exp for C++-O2-g-built GDB
@ 2016-07-20 17:08 sergiodj+buildbot
  2016-07-20 17:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027d97f8b0193a8113ee60bafc686d45d0af59ee ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 027d97f8b0193a8113ee60bafc686d45d0af59ee

testsuite: Fix gdb.gdb/selftest.exp for C++-O2-g-built GDB

tested on Fedora 24 x86_64 after:
        ./configure; make
That is: CFLAGS='-g -O2' CXXFLAGS='-g -O2'

FAIL: gdb.gdb/selftest.exp: unknown source line
FAIL: gdb.gdb/selftest.exp: step into xmalloc call

gdb/testsuite/ChangeLog
2016-07-20  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.gdb/selftest.exp (do_steps_and_nexts): Add "next over TRY" and
	"step into captured_main (args)".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Check p_paddr for program header space
@ 2016-07-20 18:26 sergiodj+buildbot
  2016-07-20 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 18:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ab8247228844bb6608d6b2c99b6d8732bab08c1 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 9ab8247228844bb6608d6b2c99b6d8732bab08c1

Check p_paddr for program header space

Issue an error if p_paddr becomes invalid when allocating space for
program headers.

	PR ld/20376
	* elf.c (assign_file_positions_for_load_sections): Also check
	p_paddr for program header space.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Consolidate code to enable optional FreeBSD native target event reporting.
@ 2016-07-20 20:07 sergiodj+buildbot
  2016-07-20 22:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 20:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da95a26cc381c0f092f515ffe108075985c16d7f ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: da95a26cc381c0f092f515ffe108075985c16d7f

Consolidate code to enable optional FreeBSD native target event reporting.

Add a new function to enable optional event reporting for FreeBSD native
targets.  Specifically, use this to enable fork and LWP events.
The bodies of fbsd_enable_follow_fork and fbsd_enable_lwp_events have been
subsumed into the new function.  In addition, use the PT_GET_EVENT_MASK
and PT_EVENT_SET_MASK requests added in FreeBSD 12 when present to enable
these events.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_enable_lwp_events): Remove function.
	(fbsd_enable_proc_events): New function.
	(fbsd_enable_follow_fork): Remove function.
	(fbsd_post_startup_inferior): Use "fbsd_enable_proc_events".
	(fbsd_post_attach): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable ptrace events on new child processes.
@ 2016-07-20 20:22 sergiodj+buildbot
  2016-07-20 23:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 20:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fa14c6b9789bad6f91dd21889f7b1a0eb75c6d0 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 5fa14c6b9789bad6f91dd21889f7b1a0eb75c6d0

Enable ptrace events on new child processes.

New child processes on FreeBSD do not inherit optional ptrace events
such as fork and LWP events from the parent process.  Instead,
explicitly enable events on new children when reporting a fork
event.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_wait): Use "fbsd_enable_proc_events" on
	new child processes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use a real vfork done event on FreeBSD when available.
@ 2016-07-20 21:44 sergiodj+buildbot
  2016-07-21  0:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dbaed3853474e7bd824a25bc454a8f2fdd71d2b3 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: dbaed3853474e7bd824a25bc454a8f2fdd71d2b3

Use a real vfork done event on FreeBSD when available.

FreeBSD 12 recently added a new ptrace event to indicate when the vfork
parent resumes after the child process stops sharing the address space.
Use this event to report a proper TARGET_WAITKIND_VFORK_DONE rather than
faking a vfork done event after a delay.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_enable_proc_events): Enable "PTRACE_VFORK"
	events.
	(fbsd_pending_vfork_done): Only define if "PTRACE_VFORK" is not
	defined.
	(fbsd_add_vfork_done): Likewise.
	(fbsd_is_vfork_done_pending): Likewise.
	(fbsd_next_vfork_done): Likewise.
	(fbsd_resume): Only ignore pending vfork done events if
	"PTRACE_VFORK" is not defined.
	(fbsd_wait): Only look for pending vfork done events if
	"PTRACE_VFORK" is not defined.
	[PTRACE_VFORK]: Handle "PL_FLAG_VFORKED" and "PL_FLAG_VFORK_DONE"
	events.
	(fbsd_follow_fork): Only fake a vfork done event if "PTRACE_VFORK"
	is not defined.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix implib test failures
@ 2016-07-21  4:17 sergiodj+buildbot
  2016-07-21  6:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21  4:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5df1bc570fcc5ef5257b7a044acdaeb6b95b9822 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 5df1bc570fcc5ef5257b7a044acdaeb6b95b9822

Fix implib test failures

bfd/
	* elf.c (_bfd_elf_filter_global_symbols): Skip local symbols.
	(swap_out_syms): Return an error when not finding ELF output
	section rather than asserting.
	* elflink.c (elf_output_implib): Call bfd_set_error on no symbols.
ld/
	* testsuite/lib/ld-lib.exp (run_ld_link_tests): Add optional
	parameter to pass list of xfails.
	* testsuite/ld-elf/elf.exp: Add xfails for implib tests.  Tidy
	implib test formatting.  Don't set .data start address.
	* testsuite/ld-elf/implib.s: Remove first .bss directive and
	replace second one with equivalent .section directive.
	* testsuite/ld-elf/empty-implib.out: Add expected final error.
	* testsuite/ld-elf/implib.rd: Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use fsqrt() to calculate float (rather than double) square root.
@ 2016-07-21 10:51 sergiodj+buildbot
  2016-07-21 11:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 10:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f118bc7a620f3e3ceff6f2fadca7b8d287a553b ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 0f118bc7a620f3e3ceff6f2fadca7b8d287a553b

Use fsqrt() to calculate float (rather than double) square root.

	* simulator.c (fsqrts): Use fsqrt rather than sqrt.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip gdb.server/ tests if lack of XML support
@ 2016-07-21 11:10 sergiodj+buildbot
  2016-07-21 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 11:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bae62ee2087bb54fd06746c99de9b734cc58a721 ***

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

Skip gdb.server/ tests if lack of XML support

I recently see some gdb.server/*.exp fails in my native gdb testing,
in which libexpat isn't available, so GDB isn't able to parse xml file.
It causes gdb.server/ tests fails because GDB can't get registers
correctly from GDBserver.

(gdb) PASS: gdb.server/connect-without-multi-process.exp: multiprocess=off: break main
target remote localhost:2352^M
Remote debugging using localhost:2352^M
warning: Can not parse XML target description; XML support was disabled at compile time^M
Reading /lib/ld-linux-armhf.so.3 from remote target...^M
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.^M
Reading /lib/ld-linux-armhf.so.3 from remote target...^M
Reading symbols from target:/lib/ld-linux-armhf.so.3...Reading /lib/ld-2.17.so.debug from remote target...^M
Reading /lib/.debug/ld-2.17.so.debug from remote target...^M
(no debugging symbols found)...done.^M
Remote 'g' packet reply is too long: 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000efffbe00000000808d0f4d100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000^
0x4d0f8d80 in _start () from target:/lib/ld-linux-armhf.so.3^M

Without XML support in GDB, it can't parse xml sent by GDBserver, and has
to fall back to the oldest arch.  However, GDBserver doesn't know this
(IMO, this is a defect in RSP), and still choose the right target
description to create regcache and 'g' packet.  If the port only has
one target description or coincidentally two sides choose the same
target description, there is no such issue.  Otherwise, GDB is broken
on read registers.

This patch is to skip gdbserver tests if XML is not support and the
target has multiple target descriptions.

gdb/testsuite:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* lib/gdbserver-support.exp (skip_gdbserver_tests): Return 1
	if gdb_skip_xml_test is true on some targets.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Create sub classes of 'struct breakpoint'
@ 2016-07-21 12:41 sergiodj+buildbot
  2016-07-21 14:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9aa76cd0a7b2cfdcc9da31e7763a695fac89f569 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9aa76cd0a7b2cfdcc9da31e7763a695fac89f569

Create sub classes of 'struct breakpoint'

Nowadays, there are three types of breakpoint in GDBserver,

 - gdb breakpoints,
 - reinsert breakpoints, used for software single step,
 - other breakpoints, used for tracepoint,

but we only have one 'struct breakpoint' for all of them.  Some fields
are only useful to one type of breakpoint.  For example, cond_list
and command_list are only used by gdb breakpoints, while handler is
only used by other breakpoints.

This patch changes 'struct breakpoint' to a base class, which has fields
needed by all breakpoint types, also add three sub-classes to
'struct breakpoint' to these three types of breakpoints.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (struct breakpoint) <cond_list>: Remove.
	<command_list, handler>: Remove.
	(struct gdb_breakpoint): New.
	(struct other_breakpoint): New.
	(struct reinsert_breakpoint): New.
	(is_gdb_breakpoint): New function.
	(any_persistent_commands): Update command_list if
	is_gdb_breakpoint returns true.
	(set_breakpoint): Create breakpoints according to their types.
	(find_gdb_breakpoint): Return 'struct gdb_breakpoint *'.
	(set_gdb_breakpoint_1): Likewise.
	(set_gdb_breakpoint): Likewise.
	(clear_breakpoint_conditions): Change parameter type to
	'struct gdb_breakpoint *'.
	(clear_breakpoint_commands): Likewise.
	(clear_breakpoint_conditions_and_commands): Likewise.
	(add_condition_to_breakpoint): Likewise.
	(add_breakpoint_condition): Likewise.
	(add_commands_to_breakpoint): Likewise.
	(check_breakpoints): Check other_breakpoint.
	(clone_one_breakpoint): Clone breakpopint according to its type.
	* mem-break.h (struct gdb_breakpoint): Declare.
	(set_gdb_breakpoint): Update declaration.
	(clear_breakpoint_conditions_and_commands): Likewise.
	(add_breakpoint_condition): Likewise.
	(add_breakpoint_commands): Likewise.
	* server.c (process_point_options): Change parameter type to
	'struct gdb_breakpoint *'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Refactor clone_all_breakpoints
@ 2016-07-21 13:37 sergiodj+buildbot
  2016-07-21 15:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63c40ec727109e2bb2956ab95968350df00c1aa1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 63c40ec727109e2bb2956ab95968350df00c1aa1

Refactor clone_all_breakpoints

This patch is to change the interface of clone_all_breakpoints, from
lists of breakpoints and raw_breakpoints to child thread and parent
thread.  I choose child thread to pass because we need the ptid of
the child thread in the following patch.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* inferiors.c (get_thread_process): Make parameter const.
	* inferiors.h (get_thread_process): Update declaration.
	* mem-break.c (clone_all_breakpoints): Remove all parameters.
	Add new parameters child_thread and parent_thread.  Callers
	updated.
	* mem-break.h (clone_all_breakpoints): Update declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make reinsert_breakpoint thread specific
@ 2016-07-21 14:36 sergiodj+buildbot
  2016-07-21 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bec903c96bc5119e357b4ad2cab99bbee7de628e ***

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

Make reinsert_breakpoint thread specific

This patch makes reinsert_breakpoint thread specific, which means we
insert and remove reinsert_breakpoint breakpoints for a specific
thread.  This motivation of this change is that I'll use
reinsert_breakpoint for vCont;s on software single step target, so that
GDBserver may insert one reinsert_breakpoint for one thread doing
step-over, and insert one reinsert_breakpoint for another thread doing
vCont;s.  After the operation of one thread is finished, GDBserver must
remove reinsert_breakpoint for that thread only.

On the other hand, reinsert_breakpoint is used for step-over nowadays.
GDBserver inserts reinsert_breakpoint, and wait only from the thread
doing step-over.  After the step-over is done, GDBserver removes the
reinsert_breakpoint.  If there is still any threads need step-over, do
the same again until all threads are finished step-over.  In other words,
reinsert_breakpoint is globally thread specific, but in an implicit way.
It is natural to make it explicitly thread specific.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (struct reinsert_breakpoint) <ptid>: New field.
	(set_reinsert_breakpoint): New parameter ptid.  Callers updated.
	(clone_one_breakpoint): Likewise.
	(delete_reinsert_breakpoints): Change parameter to thread.
	Callers updated.
	(has_reinsert_breakpoints): Likewise.
	(uninsert_reinsert_breakpoints): Likewise.
	(reinsert_reinsert_breakpoints): Likewise.
	* mem-break.h (set_reinsert_breakpoint): Update declaration.
	(delete_reinsert_breakpoints): Likewise.
	(reinsert_reinsert_breakpoints): Likewise.
	(uninsert_reinsert_breakpoints): Likewise.
	(has_reinsert_breakpoints): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Switch current_thread to lwp's thread in install_software_single_step_breakpoints
@ 2016-07-21 14:58 sergiodj+buildbot
  2016-07-21 17:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 14:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 984a2c042e82f2306183d9d165c5cb99e4341503 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 984a2c042e82f2306183d9d165c5cb99e4341503

Switch current_thread to lwp's thread in install_software_single_step_breakpoints

install_software_single_step_breakpoints has parameter lwp, but still
need to switch to current_thread.  In order to simplify its caller,
we do the current_thread save/restore inside install_software_single_step_breakpoints.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* gdbthread.h (make_cleanup_restore_current_thread): Declare.
	* inferiors.c (do_restore_current_thread_cleanup): New function.
	(make_cleanup_restore_current_thread): Likewise.
	* linux-low.c (install_software_single_step_breakpoints): Call
	make_cleanup_restore_current_thread.  Switch current_thread to
	thread.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use enqueue_pending_signal in linux_resume_one_thread
@ 2016-07-21 15:20 sergiodj+buildbot
  2016-07-21 18:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4281b351bfa3b646ab531cf73c56e49366fef108 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 4281b351bfa3b646ab531cf73c56e49366fef108

Use enqueue_pending_signal in linux_resume_one_thread

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_resume_one_thread): Call
	enqueue_pending_signal.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enqueue signal even when resuming threads
@ 2016-07-21 15:58 sergiodj+buildbot
  2016-07-21 19:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e9a339ec8ffab80fdbe97adaf888fe03b73fe22 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0e9a339ec8ffab80fdbe97adaf888fe03b73fe22

Enqueue signal even when resuming threads

Nowadays, we only enqueue signal when we leave thread pending in
linux_resume_one_thread.  If lwp->resume->sig isn't zero (GDB wants
to resume with signal), we pass lwp->resume->sig to
linux_resume_one_lwp.

In order to reduce the difference between resuming thread with signal
and proceeding thread with signal, when we resume thread, we can
enqueue signal too, and proceed thread.  The signal will be consumed in
linux_resume_one_lwp_throw from lwp->pending_signals.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (proceed_one_lwp): Declare.
	(linux_resume_one_thread): Remove local variable 'step'.
	Lift code enqueue signal.  Call proceed_one_lwp instead of
	linux_resume_one_lwp.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use reinsert_breakpoint for vCont;s
@ 2016-07-21 17:08 sergiodj+buildbot
  2016-07-21 21:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8901d1936e4e691f0b3b976f5626ac5a8f27aa7f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8901d1936e4e691f0b3b976f5626ac5a8f27aa7f

Use reinsert_breakpoint for vCont;s

This patch is to teach GDBserver using software single step to handle
vCont;s.  Simply speaking, if the thread's resume request is resume_step,
install reinsert breakpoint at the next pcs when GDBserver is about to
resume threads.  These reinsert breakpoints of a thread are removed,
when GDBserver gets an event from that thread and reports it back to
GDB.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (resume_stopped_resumed_lwps): If resume request
	is resume_step, call maybe_hw_step.
	(linux_wait_1): Stop all threads, remove reinsert breakpoints,
	and unstop them.
	(linux_resume_one_lwp_throw): Don't assert the thread has reinsert
	breakpoints or not.
	(proceed_one_lwp): If resume request is resume_step, install
	reinsert breakpoints and call maybe_hw_step.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support vCont s and S actions with software single step
@ 2016-07-21 17:54 sergiodj+buildbot
  2016-07-21 22:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 17:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21536b367ce73eed103e1389b5f45010f0c96bbb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 21536b367ce73eed103e1389b5f45010f0c96bbb

Support vCont s and S actions with software single step

GDBserver with software single step should be able to claim supporting
vCont s and S actions, so that GDB knows the remote target can do
single step.  It doesn't matter to GDB that the single step in the
remote target is done via hardware or software.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* server.c (handle_v_requests): Support s and S actions
	if target_supports_software_single_step return true.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix cast to 'gdb_breakpoint *'
@ 2016-07-21 18:25 sergiodj+buildbot
  2016-07-21 23:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2583da7cd64e680e43cf92c8022eadee84357b3b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2583da7cd64e680e43cf92c8022eadee84357b3b

Fix cast to 'gdb_breakpoint *'

c-mode buildbot catches a build problem,

gcc -g -O2    -I. -I../../../binutils-gdb/gdb/gdbserver -I../../../binutils-gdb/gdb/gdbserver/../common -I../../../binutils-gdb/gdb/gdbserver/../regformats -I../../../binutils-gdb/gdb/gdbserver/.. -I../../../binutils-gdb/gdb/gdbserver/../../include -I../../../binutils-gdb/gdb/gdbserver/../gnulib/import -Ibuild-gnulib-gdbserver/import  -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wpointer-sign -Wmissing-prototypes -Wdeclaration-after-statement -Wmissing-parameter-type -Wold-style-declaration -Wold-style-definition -Wformat-nonliteral -Wno-missing-prototypes -Werror -DGDBSERVER -c -o hostio.o -MT hostio.o -MMD -MP -MF .deps/hostio.Tpo ../../../binutils-gdb/gdb/gdbserver/hostio.c
../../../binutils-gdb/gdb/gdbserver/mem-break.c: In function find_gdb_breakpoint:
../../../binutils-gdb/gdb/gdbserver/mem-break.c:996:15: error: gdb_breakpoint undeclared (first use in this function)
       return (gdb_breakpoint *) bp;

we should use 'struct gdb_breakpoint' rather than 'gdb_breakpoint'.
Patch below fixes this.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (find_gdb_breakpoint): Cast bp to
	'struct gdb_breakpoint *' rather than 'gdb_breakpoint *'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove unused variable in windows-nat.c
@ 2016-07-21 19:45 sergiodj+buildbot
  2016-07-22  1:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 19:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c25b7ccef4d6d96ed4af1d27c79d78767dba7161 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c25b7ccef4d6d96ed4af1d27c79d78767dba7161

Remove unused variable in windows-nat.c

Leave the call for side effects.

gdb/ChangeLog:
2016-07-21  Pedro Alves  <palves@redhat.com>

	* windows-nat.c (handle_exception): Remove "th".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix djgpp gdb build
@ 2016-07-21 20:40 sergiodj+buildbot
  2016-07-22  2:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f515a1d643b599ebb8a23d3d95e9f0dfc8261a11 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f515a1d643b599ebb8a23d3d95e9f0dfc8261a11

Fix djgpp gdb build

 - A few missing casts required by C++, resulting in:

   ../../src/gdb/ser-go32.c:795:21: error: invalid conversion from 'const void*' to 'const char*' [-fpermissive]

   etc.

 - dos_noop has an incompatible prototype with struct serial_ops's
   setparity, resulting in:

    ../../src/gdb/ser-go32.c:874:1: error: invalid conversion from 'int (*)(serial*)' to 'int (*)(serial*, int)' [-fpermissive]

   (I thought of calling the ser-base.c default methods, but djgpp
   doesn't include ser-base.c in the build.)

gdb/ChangeLog:
2016-07-21  Pedro Alves  <palves@redhat.com>

	* go32-nat.c (go32_create_inferior): Add cast.
	* ser-go32.c (dos_noop): Delete.
	(dos_flush_output, dos_setparity, dos_drain_output): New
	functions.
	(dos_write): Add cast.
	(dos_ops): Use dos_flush_output, dos_setparity and
	dos_drain_output.
	* top.c (do_chdir_cleanup): Add cast.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set BFD_VERSION to 2.27.51
@ 2016-07-22  0:11 sergiodj+buildbot
  2016-07-22  5:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-22  0:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fecd57f9f1f58f043861d5929a650f35a88a6caa ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: fecd57f9f1f58f043861d5929a650f35a88a6caa

Set BFD_VERSION to 2.27.51

bfd/

	* version.m4 (BFD_VERSION): Set to 2.27.51.
	* configure: Regenerated.

binutils/

	* configure: Regenerated.

gas/

	* configure: Regenerated.

gprof/

	* configure: Regenerated.

ld/

	* configure: Regenerated.

opcodes/

	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow empty struct expressions in Rust
@ 2016-07-22  3:02 sergiodj+buildbot
  2016-07-22  4:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-22  3:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12df5c002dcbfc5ac54983e1e7040a182f71a753 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 12df5c002dcbfc5ac54983e1e7040a182f71a753

Allow empty struct expressions in Rust

I learned recently that empty struct expressions, like "X{}", have been
promoted from experimental to stable in Rust.  This patch changes the
Rust expression parser to allow this case.

New test case included.
Built and regtested on x86-64 Fedora 23, using Rust 1.11 beta.

2016-07-21  Tom Tromey  <tom@tromey.com>

	* rust-lang.c (rust_tuple_struct_type_p): Return false for empty
	structs.
	* rust-exp.y (struct_expr_list): Allow empty elements.

2016-07-21  Tom Tromey  <tom@tromey.com>

	* gdb.rust/simple.rs (main): Use empty struct expression.
	* gdb.rust/simple.exp: Add tests for empty struct expression.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix segfault in ARC linker when generating got entries for local symbols.
@ 2016-07-22 16:29 sergiodj+buildbot
  2016-07-22 16:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-22 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c02d11a585398734a2178d65a17411cd3050b9d2 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: c02d11a585398734a2178d65a17411cd3050b9d2

Fix segfault in ARC linker when generating got entries for local symbols.

bfd	* arc-got.h (relocate_fix_got_relocs_for_got_info): Handle the case
	where there's no elf_link_hash_entry while processing GOT_NORMAL got
	entries.

ld	* testsuite/ld-arc/got-01.d: New file.
	* testsuite/ld-arc/got-01.s: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Get "num" as unsigned in ctf
@ 2016-07-22 17:58 sergiodj+buildbot
  2016-07-22 18:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-22 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eed2386e45968fa4fee8d093895f4789044fb077 ***

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

Get "num" as unsigned in ctf

I see the following fail due to the warning,

-trace-frame-collected^M
[warning] Extracting signed value from an unsigned int (num)^M
....
FAIL: gdb.trace/mi-trace-frame-collected.exp: ctf: -trace-frame-collected

In ctf metadata, "num" in "tsv" is defined as unint32_t,

  ctf_save_write_metadata (&writer->tcs,
			   "event {\n\tname = \"tsv\";\n\tid = %u;\n"
			   "\tfields := struct { \n"
			   "\t\tuint64_t val;\n"
			   "\t\tuint32_t num;\n"
			   "\t};\n"
			   "};\n", CTF_EVENT_ID_TSV);

so we should read it as unsigned.  The patch below fixes the fail by
changing to bt_ctf_get_uint64.

gdb:

2016-07-22  Yao Qi  <yao.qi@linaro.org>

	* ctf.c (ctf_traceframe_info): Call bt_ctf_get_uint64 rather than
	bt_ctf_get_int64.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix ARMv8.1/v8.2 for hw watchpoint and breakpoint
@ 2016-07-23 19:48 sergiodj+buildbot
  2016-07-23 22:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-07-23 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49ecef2a7da2ee9df4ae675f99b70518fbf1bb23 ***

Author: Andrew Pinski <apinski@cavium.com>
Branch: master
Commit: 49ecef2a7da2ee9df4ae675f99b70518fbf1bb23

Fix ARMv8.1/v8.2 for hw watchpoint and breakpoint

The problem here is ARMv8.1 (and ARMv8.2) define a
different debug version than ARMv8 (7 and 8 respectively).
This fixes hw watchpoints and breakpoints by checking
for those debug versions too.

Committed as obvious after a test on aarch64-linux-gnu
(on a ThunderX machine which has ARMv8.1 support enabled).

ChangeLog:
	* nat/aarch64-linux-hw-point.c
	(aarch64_linux_get_debug_reg_capacity): Handle
	ARMv8.1 and ARMv8.2 debug versions.
	* nat/aarch64-linux-hw-point.h
	(AARCH64_DEBUG_ARCH_V8_1): New define.
	(AARCH64_DEBUG_ARCH_V8_2): New define.

Signed-off-by: Andrew Pinski <apinski@cavium.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
[parent not found: <e34879080d8935792ef3942efa5f25b4c3169b5a@gdb-build>]
[parent not found: <c0272db5854a799a9f3bb3803c3d03d1a62b9ac2@gdb-build>]
[parent not found: <3a1518e4f3c467cfee2786b0af3388529f14d23b@gdb-build>]
[parent not found: <0e1a6a5169023ee0c19de2c9160b469e43634b21@gdb-build>]
[parent not found: <e0461dbb653dbb3c46ea7a15054fd2c98f879f31@gdb-build>]
[parent not found: <9cf12d57c58a82cfe3e6fee26d1ea55dfe49f9c4@gdb-build>]
[parent not found: <40c31709c6a51926fcb409611caa52b2da6515c0@gdb-build>]
[parent not found: <54806ffa85643c3a1ee721d5c3f5586d32f86ee1@gdb-build>]
[parent not found: <6598661d14c90cabac1daa5e683d1e17883b2e41@gdb-build>]
[parent not found: <293acfae4e3c9aad417e262edc9847c79bbbbb11@gdb-build>]
[parent not found: <147d994bcdd36a177e49e7b6ac8d9c1f7b4cdcf5@gdb-build>]
[parent not found: <db18dbabad8e7b63e98d47813ef20acac7072350@gdb-build>]
[parent not found: <7bd374a44d1db21b54a9a52ecde1d064cdaa8cd1@gdb-build>]
* [binutils-gdb] Tweak gdb.cp tests for aarch32
@ 2016-08-01  9:52 sergiodj+buildbot
  2016-08-01 10:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-01  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3465b24a22bd1f783313e680aa76bac83c8aaf5 ***

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

Tweak gdb.cp tests for aarch32

There are some gdb.cp/ tests fails if the program is compiled for arm
32-bit but GDB/GDBserver is aarch64 64-bit program, because target triplet
doesn't match "arm*-*-*".  Instead, we can use is_aarch32_target.

gdb/testsuite:

2016-08-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.cp/anon-struct.exp: Check is_aarch32_target.
	* gdb.cp/cpexprs.exp: Likewise.
	* gdb.cp/m-static.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update Swedish translation in bfd directory.
@ 2016-08-01 10:35 sergiodj+buildbot
  2016-08-01 10:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 781bf64d2414f70c51938e15ebce5c88e7172e55 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 781bf64d2414f70c51938e15ebce5c88e7172e55

Update Swedish translation in bfd directory.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Bump version to 7.12.50.DATE-git.
@ 2016-08-01 17:20 sergiodj+buildbot
  2016-08-01 18:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2bd7787d3e5f87f66761f555d89b8ce5d631a62 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: b2bd7787d3e5f87f66761f555d89b8ce5d631a62

Bump version to 7.12.50.DATE-git.

Now that the GDB 7.12 branch has been created, we can
bump the version number.

gdb/ChangeLog:

	GDB 7.12 branch created (41bfcd638a4e0e48b96ce4de2845372dea481322):
	* version.in: Bump version to 7.12.50.DATE-git.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update NEWS post GDB 7.12 branch creation.
@ 2016-08-01 18:17 sergiodj+buildbot
  2016-08-01 19:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 18:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 751b375e01e7e85aeccdd965578cb2040836593d ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 751b375e01e7e85aeccdd965578cb2040836593d

Update NEWS post GDB 7.12 branch creation.

gdb/ChangeLog:

	* NEWS: Create a new section for the next release branch.
	Rename the section of the current branch, now that it has
	been cut.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix some PowerPC VLE BFD issues and add some PowerPC VLE instructions.
@ 2016-08-01 21:12 sergiodj+buildbot
  2016-08-02  2:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfdaec14b0db059497b47b515d753b6383772b6b ***

Author: Andrew Jenner <andrew@codesourcery.com>
Branch: master
Commit: dfdaec14b0db059497b47b515d753b6383772b6b

Fix some PowerPC VLE BFD issues and add some PowerPC VLE instructions.

        bfd/
        * elf32-ppc.c (is_branch_reloc): Recognise VLE branch relocations.
        (ppc_elf_howto_raw): Fix dst_mask of R_PPC_VLE_REL15.
        (ppc_elf_vle_split16): Clear field before inserting.

        opcodes/
        * ppc-opc.c (vle_opcodes): Alias 'e_cmpwi' to 'e_cmpi' and
        'e_cmplwi' to 'e_cmpli' instead.
        (OPVUPRT, OPVUPRT_MASK): Define.
        (powerpc_opcodes): Add E200Z4 insns.
        (vle_opcodes): Add context save/restore insns.

        include/
        * opcode/ppc.h (PPC_OPCODE_E200Z4): New define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix SH GOT allocation in the presence of linker garbage collection.
@ 2016-08-02 12:23 sergiodj+buildbot
  2016-08-02 12:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-02 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a94d834c9d0108f0bb50ddc311554d1bed320f54 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a94d834c9d0108f0bb50ddc311554d1bed320f54

Fix SH GOT allocation in the presence of linker garbage collection.

	PR ld/17739
ld	* emulparams/shelf.sh (CHECK_RELOCS_AFTER_OPEN_INPUT): Define with
	valye 'yes'.
	* emulparams/shelf32.sh: Likewise.
	* emulparams/shelf32.sh: Likewise.
	* emulparams/shelf_nto.sh: Likewise.
	* emulparams/shelf_nto.sh: Likewise.
	* emulparams/shelf_vxworks.sh: Likewise.
	* emulparams/shelf_vxworks.sh: Likewise.
	* emulparams/shlelf32_linux.sh: Likewise.
	* emulparams/shlelf32_linux.sh: Likewise.
	* emulparams/shlelf_linux.sh: Likewise.
	* emulparams/shlelf_linux.sh: Likewise.
	* emulparams/shlelf_nto.sh: Likewise.
	* emulparams/shlelf_nto.sh: Likewise.

bfd	* elf32-sh.c (sh_elf_gc_sweep_hook): Delete.
	(elf_backend_sweep_hook): Delete.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Synchronize libiberty sources with FSF GCC mainline version.
@ 2016-08-02 14:43 sergiodj+buildbot
  2016-08-02 14:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-02 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa3fcee7b8c73070306ec358e730d1dfcac246bf ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: fa3fcee7b8c73070306ec358e730d1dfcac246bf

Synchronize libiberty sources with FSF GCC mainline version.

include	* libiberty.h (MAX_ALLOCA_SIZE): New macro.

libiberty * make-relative-prefix.c (make_relative_prefix_1): Fall back to
	malloc if alloca argument is greater than MAX_ALLOCA_SIZE.

	* cp-demangle.c (cplus_demangle_operators): Add f[lrLR].
	(d_expression_1): Handle them.
	(d_maybe_print_fold_expression): New.
	(d_print_comp_inner): Use it.
	(d_index_template_argument): Handle negative index.

	* cp-demangle.c (cplus_demangle_operators): Add sP and sZ.
	(d_print_comp_inner): Handle them.
	(d_template_args_1): Split out from d_template_args.
	(d_args_length): New.

	PR c++/70926
	* cplus-dem.c: Handle large values and overflow when demangling
	length variables.
	(demangle_template_value_parm): Read only until end of mangled string.
	(do_hpacc_template_literal): Likewise.
	(do_type): Handle overflow when demangling array indices.

	* cp-demangle.c (cplus_demangle_print_callback): Avoid zero-length
	  VLAs.

	PR c++/70498
	* cp-demangle.c (d_expression_1): Formatting fix.

	* cplus-dem.c (enum type_kind_t): Add tk_rvalue_reference
	constant.
	(demangle_template_value_parm): Handle tk_rvalue_reference
	type kind.
	(do_type): Support 'O' type id (rvalue references).

	* testsuite/demangle-expected: Add tests.

	PR c++/70498
	* cp-demangle.c: Parse numbers as integer instead of long to avoid
	overflow after sanity checks. Include <limits.h> if available.
	(INT_MAX): Define if necessary.
	(d_make_template_param): Takes integer argument instead of long.
	(d_make_function_param): Likewise.
	(d_append_num): Likewise.
	(d_identifier): Likewise.
	(d_number): Parse as and return integer.
	(d_compact_number): Handle overflow.
	(d_source_name): Change variable type to integer for parsed number.
	(d_java_resource): Likewise.
	(d_special_name): Likewise.
	(d_discriminator): Likewise.
	(d_unnamed_type): Likewise.
	* testsuite/demangle-expected: Add regression test cases.

	* configure: Remove SH5 support.

	PR c++/69687
	* cplus-dem.c: Include <limits.h> if available.
	(INT_MAX): Define if necessary.
	(remember_type, remember_Ktype, register_Btype, string_need):
	Abort if we detect cases where we the size of the allocation would
	overflow.

	PR c++/70492
	* cplus-dem.c (gnu_special): Handle case where consume_count returns
	-1.

	PR c++/67394
	PR c++/70481
	* cplus-dem.c (squangle_mop_up): Zero bsize/ksize after freeing
	btypevec/ktypevec.
	* testsuite/demangle-expected: Add coverage tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg
@ 2016-08-02 16:45 sergiodj+buildbot
  2016-08-02 19:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-02 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 979659d08478172311764b468bfce4960b38760b ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 979659d08478172311764b468bfce4960b38760b

[GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg

As a result of this commit,

  9b4c5f878ff39e04127a1ad95f6b3832afe6d278
  (Remove support for thread events without PTRACE_EVENT_CLONE in GDBServer.)

the last usage of td_ta_event_addr td_ta_set_event and
td_ta_event_getmsg were removed.  They are no longer used.  This patch
is to remove them.

gdb/gdbserver:

2016-08-02  Yao Qi  <yao.qi@linaro.org>

	* thread-db.c (struct thread_db) <td_ta_event_getmsg_p>: Remove.
	<td_ta_set_event_p, td_ta_event_addr_p>: Remove.
	(thread_db_load_search): Update.
	(try_thread_db_load_1): Don't look for td_ta_event_addr,
	td_ta_set_event and td_ta_event_getmsg.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add myself as Rust maintainer
@ 2016-08-03 16:11 sergiodj+buildbot
  2016-08-03 16:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-03 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33541b2e56a653b9260fb1dc2cd7dd73b0c49169 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 33541b2e56a653b9260fb1dc2cd7dd73b0c49169

Add myself as Rust maintainer

A while ago, Pedro announced that I would be the Rust maintainer for
gdb.  However, I neglected to update the MAINTAINERS file until now.

2016-08-02  Tom Tromey  <tom@tromey.com>

	* MAINTAINERS (Core): Add self as Rust maintainer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update NEWS to mention Python breakpoint events
@ 2016-08-03 17:44 sergiodj+buildbot
  2016-08-03 18:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-03 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d2a0a14e53945eb260c08752654bd03a240ecf7 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 8d2a0a14e53945eb260c08752654bd03a240ecf7

Update NEWS to mention Python breakpoint events

An earlier patch added three new breakpoint-related events to the
Python API.  However, at that time, I forgot to update NEWS.  This
patch supplies the missing entry.

2016-08-03  Tom Tromey  <tom@tromey.com>

	* NEWS: Mention new Python breakpoint events.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Quiet ptrace error ESRCH in regsets_fetch_inferior_registers
@ 2016-08-04 10:44 sergiodj+buildbot
  2016-08-04 10:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 10:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fcd4a73d7dc3505662b4d58489f4c1b8b003b8f3 ***

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

Quiet ptrace error ESRCH in regsets_fetch_inferior_registers

When I run process-dies-while-detaching.exp with GDBserver, I see many
warnings printed by GDBserver,

ptrace(regsets_fetch_inferior_registers) PID=26183: No such process
ptrace(regsets_fetch_inferior_registers) PID=26183: No such process
ptrace(regsets_fetch_inferior_registers) PID=26184: No such process
ptrace(regsets_fetch_inferior_registers) PID=26184: No such process

regsets_fetch_inferior_registers is called when GDBserver resumes each
lwp.

 #2  0x0000000000428260 in regsets_fetch_inferior_registers (regsets_info=0x4690d0 <aarch64_regsets_info>, regcache=0x31832020)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:5412
 #3  0x00000000004070e8 in get_thread_regcache (thread=0x31832940, fetch=fetch@entry=1) at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/regcache.c:58
 #4  0x0000000000429c40 in linux_resume_one_lwp_throw (info=<optimized out>, signal=0, step=0, lwp=0x31832830)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4463
 #5  linux_resume_one_lwp (lwp=0x31832830, step=<optimized out>, signal=<optimized out>, info=<optimized out>)
    at /home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:4573

The is the case that threads are disappeared when GDB/GDBserver resumes
them.  We check errno for ESRCH, and don't print error messages, like
what we are doing in regsets_store_inferior_registers.

gdb/gdbserver:

2016-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (regsets_fetch_inferior_registers): Check
	errno is ESRCH or not.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Determine target description for native aarch64
@ 2016-08-04 11:45 sergiodj+buildbot
  2016-08-04 12:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f67973b4280cfd045e632a3340becd16e43b4b1 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 6f67973b4280cfd045e632a3340becd16e43b4b1

Determine target description for native aarch64

I find the following test fail when I test native aarch64 gdb with
arm program,

(gdb) PASS: gdb.base/attach-pie-noexec.exp: attach
set architecture arm^M
warning: Selected architecture arm is not compatible with reported target architecture aarch64^M
Architecture `arm' not recognized.^M
The target architecture is set automatically (currently aarch64)^M
(gdb) FAIL: gdb.base/attach-pie-noexec.exp: set architecture arm

GDB thinks the target is aarch64, but it isn't.  Nowadays, we are
using some entries AT_PHENT and AT_HWCAP in auxv to determine whether
the process is a 32-bit arm one or 64-bit aarch64 one, and get the
right gdbarch.  However, in the process of parsing auxv (in
inf_ptrace_auxv_parse), the size of int and data pointer of
target_gdbarch is used.  If debug program exists (in most of cases),
target_gdbarch is already set according to the debug program, which
is arm in my case.  Then, GDB can parse auxv successfully.  However,
in gdb.base/attach-pie-noexec.exp, the debug program is removed,
target_gdbarch is aarch64 when GDB parse auxv, so GDB can't parse
it successfully.

Instead of using auxv, we check the return value of ptrace NT_ARM_VFP.
If the program is an arm process, NT_ARM_VFP is OK, otherwise, error
is returned.

Additionally, we only return tdesc_arm_with_neon for arm process,
because neon is mandatory on ARMv8.

gdb:

2016-08-04  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-nat.c (tdesc_arm_with_vfpv3): Remove the
	declaration.
	(aarch64_linux_read_description): Remove code on getting
	auxv and select target description on it.  Select target
	description by the result of NT_ARM_VFP ptrace request.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] 2016-08-04 Thomas Preud'homme <thomas.preudhomme@arm.com>
@ 2016-08-04 16:49 sergiodj+buildbot
  2016-08-04 19:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 54ddd295b505efe4b07cc1e939d4e150032603d8 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 54ddd295b505efe4b07cc1e939d4e150032603d8

2016-08-04  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* bfd-in.h (bfd_elf32_arm_set_target_relocs): Add one parameter.
	* bfd-in2.h: Regenerate.
	* elf32-arm.c (struct elf32_arm_link_hash_table): Declare new
	cmse_implib field.
	(bfd_elf32_arm_set_target_relocs): Add new parameter to initialize
	cmse_implib field in struct elf32_arm_link_hash_table.
	(elf32_arm_filter_cmse_symbols): New function.
	(elf32_arm_filter_implib_symbols): Likewise.
	(elf_backend_filter_implib_symbols): Define to
	elf32_arm_filter_implib_symbols.

ld/
	* emultempl/armelf.em (cmse_implib): Declare and define this new
	static variable.
	(arm_elf_create_output_section_statements): Add new cmse_implib
	parameter.
	(OPTION_CMSE_IMPLIB): Define macro.
	(PARSE_AND_LIST_LONGOPTS): Add entry for new --cmse-implib switch.
	(PARSE_AND_LIST_OPTIONS): Likewise.
	(PARSE_AND_LIST_ARGS_CASES): Handle OPTION_CMSE_IMPLIB case.
	* ld.texinfo (--cmse-implib): Document new option.
	* testsuite/ld-arm/arm-elf.exp
	(Secure gateway import library generation): New test.
	(Secure gateway import library generation: errors): Likewise.
	* testsuite/ld-arm/cmse-implib.s: New file.
	* testsuite/ld-arm/cmse-implib-errors.out: Likewise.
	* testsuite/ld-arm/cmse-implib.rd: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/configure --help: suggest --disable-build-with-cxx instead of --enable...
@ 2016-08-05 17:17 sergiodj+buildbot
  2016-08-05 17:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 17:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1baf514936892a01d8ea49c2c1ccfd7ecd3b7dcd ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1baf514936892a01d8ea49c2c1ccfd7ecd3b7dcd

gdb/configure --help: suggest --disable-build-with-cxx instead of --enable...

We build by default with a C++ compiler, but "configure --help" still
says "--enable-build-with-cxx", which hints that it is by default
disabled.  Update the --help text.

gdb/ChangeLog:
2016-08-05  Pedro Alves  <palves@redhat.com>

	* build-with-cxx.m4: Change help string to be in terms of
	--disable-build-with-cxx.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:
2016-08-05  Pedro Alves  <palves@redhat.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/NEWS: Mention that C++ is now the default
@ 2016-08-05 18:21 sergiodj+buildbot
  2016-08-05 19:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69ffd7f270c8a3f1b577848d2536b93ed01287de ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 69ffd7f270c8a3f1b577848d2536b93ed01287de

gdb/NEWS: Mention that C++ is now the default

gdb/ChangeLog:
2016-08-05  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that GDB and GDBserver build with a C++ compiler
	by default.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove unused cli_command_loop declaration
@ 2016-08-05 22:57 sergiodj+buildbot
  2016-08-06  2:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c632e428c2fd707b83a2c61e0b25b473e3d7d18e ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: c632e428c2fd707b83a2c61e0b25b473e3d7d18e

Remove unused cli_command_loop declaration

This declaration is not used anymore.

gdb/ChangeLog:

	* event-top.h (cli_command_loop): Remove.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix memory leaks in chew program.
@ 2016-08-08 16:36 sergiodj+buildbot
  2016-08-08 17:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-08 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a286b63457628b0a55d395f14005f254512e27d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 8a286b63457628b0a55d395f14005f254512e27d

Fix memory leaks in chew program.

	* doc/chew.c (delete_string): Only free the string buffer if it is
	there.  Mark the buffer as NULL after freeing.
	(drop): Free the dropped string.
	(free_words): New function: Frees the memory allocated to the
	dictionary.
	(add_instrinsic): Duplicate the name string, so that it can be
	freed later on.
	(compile): Free unused words.
	(main): Free the dictionary and top level string buffers at the
	end.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Regenerate some target description files
@ 2016-08-09  7:29 sergiodj+buildbot
  2016-08-09  7:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-09  7:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a17ca318b7bc453831049f1d8bbc7f336f5ac5a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6a17ca318b7bc453831049f1d8bbc7f336f5ac5a

Regenerate some target description files

I regenerated all target description .c files from scratch, and got
this spurious diff.

It's a simple mid-air collision - these files were clearly generated
before commit 73b4f516a037 ("maint_print_c_tdesc_cmd: Use type for
TYPE_CODE_FLAGS instead of field_type."), which did the global
s/field_type/type/, and pushed to master afterwards.

gdb/features/ChangeLog:
2016-08-08  Pedro Alves  <palves@redhat.com>

	* features/i386/amd64-avx-mpx-linux.c: Regenerate.
	* features/i386/amd64-avx-mpx.c: Regenerate.
	* features/i386/i386-avx-mpx-linux.c: Regenerate.
	* features/i386/i386-avx-mpx.c: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] linux-procfs: Introduce enum proc_state
@ 2016-08-09 13:06 sergiodj+buildbot
  2016-07-26  3:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 13:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d617208bb06bd461b52ce041d89f7127e3044762 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d617208bb06bd461b52ce041d89f7127e3044762

linux-procfs: Introduce enum proc_state

Parse the process's /proc/PID/status state into an enum instead of the
current scheme of passing state strings around.

gdb/ChangeLog:
2016-07-25  Pedro Alves  <palves@redhat.com>

	* nat/linux-procfs.c (enum proc_state): New enum.
	(parse_proc_status_state): New function.
	(linux_proc_pid_get_state): Replace output string buffer parameter
	with an output proc_state parameter.  Use parse_proc_status_state.
	(linux_proc_pid_is_gone): Adjust to use proc_state values.
	(linux_proc_pid_has_state): Change type of 'state' parameter; now
	an enum proc_state.  Adjust to linux_proc_pid_get_state interface
	change.
	(linux_proc_pid_is_stopped)
	(linux_proc_pid_is_trace_stopped_nowarn)
	(linux_proc_pid_is_zombie_maybe_warn): Adjust to
	linux_proc_pid_get_state interface change.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Handle correctly passing a bad interpreter name to new-ui
@ 2016-08-09 13:28 sergiodj+buildbot
  2016-07-26 12:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8194e927cc66e8cceb9890240ad75363b3ca6d53 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8194e927cc66e8cceb9890240ad75363b3ca6d53

Handle correctly passing a bad interpreter name to new-ui

When a bad interpreter name is passed to new-ui, such as:

  (gdb)  new-ui bloop /dev/pts/10

A partially created UI is left in the UI list, with interp set to NULL.
Trying to do anything that will print on this UI (such as "start") will
cause a segmentation fault.

Changes in v2:

  - Use with_test_prefix to namespace test procedures
  - Give an explicit stable test name
  - Add a "bad terminal path" test
  - Remove useless runto_main
  - Add missing intro comments

I did not factor out the pty spawn, as there is some magic involved I
don't quite understand.  But it wouldn't bring that much anyway.

gdb/ChangeLog:

	* top.h (make_delete_ui_cleanup): New declaration.
	* top.c (delete_ui_cleanup): New function.
	(make_delete_ui_cleanup): New function.
	(new_ui_command): Create restore_ui cleanup earlier, create a
	delete_ui cleanup and discard it on success.

gdb/testsuite/ChangeLog:

	* gdb.base/new-ui.exp (do_test_invalid_args): New
	procedure.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR gdb/20295: GDB segfaults printing bitfield member of optimized out value
@ 2016-08-09 13:36 sergiodj+buildbot
  2016-08-09 13:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 13:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5ca03b41d2c94919d5cb59d8d7adad98c29d156 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e5ca03b41d2c94919d5cb59d8d7adad98c29d156

Fix PR gdb/20295: GDB segfaults printing bitfield member of optimized out value

With something like:

  struct A { int bitfield:4; } var;

If 'var' ends up wholly-optimized out, printing 'var.bitfield' crashes
gdb here:

 (top-gdb) bt
 #0  0x000000000058b89f in extract_unsigned_integer (addr=0x2 <error: Cannot access memory at address 0x2>, len=2, byte_order=BFD_ENDIAN_LITTLE)
     at /home/pedro/gdb/mygit/src/gdb/findvar.c:109
 #1  0x00000000005a187a in unpack_bits_as_long (field_type=0x16cff70, valaddr=0x0, bitpos=16, bitsize=12) at /home/pedro/gdb/mygit/src/gdb/value.c:3347
 #2  0x00000000005a1b9d in unpack_value_bitfield (dest_val=0x1b5d9d0, bitpos=16, bitsize=12, valaddr=0x0, embedded_offset=0, val=0x1b5d8d0)
     at /home/pedro/gdb/mygit/src/gdb/value.c:3441
 #3  0x00000000005a2a5f in value_fetch_lazy (val=0x1b5d9d0) at /home/pedro/gdb/mygit/src/gdb/value.c:3958
 #4  0x00000000005a10a7 in value_primitive_field (arg1=0x1b5d8d0, offset=0, fieldno=0, arg_type=0x16d04c0) at /home/pedro/gdb/mygit/src/gdb/value.c:3161
 #5  0x00000000005b01e5 in do_search_struct_field (name=0x1727c60 "bitfield", arg1=0x1b5d8d0, offset=0, type=0x16d04c0, looking_for_baseclass=0, result_ptr=0x7fffffffcaf8,
 [...]

unpack_value_bitfield is already optimized-out/unavailable -aware:

   (...) VALADDR points to the contents of VAL.  If the VAL's contents
   required to extract the bitfield from are unavailable/optimized
   out, DEST_VAL is correspondingly marked unavailable/optimized out.

however, it is not considering the case of the value having no
contents buffer at all, as can happen through
allocate_optimized_out_value.

gdb/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	* value.c (unpack_value_bitfield): Skip unpacking if the parent
	has no contents buffer to begin with.

gdb/testsuite/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	* gdb.dwarf2/bitfield-parent-optimized-out.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR python/20190 - compute TLS symbol without a frame
@ 2016-08-09 13:48 sergiodj+buildbot
  2016-07-27  1:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b31a4bcec2efec9bc8ca40deb61123c52690a2e ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0b31a4bcec2efec9bc8ca40deb61123c52690a2e

PR python/20190 - compute TLS symbol without a frame

PR python/20190 arose from an exception I noticed when trying to use
the Python unwinder for Spider Monkey in Firefox.

The problem is that the unwinder wants to examine the value of a
thread-local variable.  However, sympy_value rejects this because
symbol_read_needs_frame returns true for a TLS variable.

This problem arose once before, though in a different context:

https://sourceware.org/bugzilla/show_bug.cgi?id=11803

At the time Pedro and Daniel pointed out a simpler way to fix that bug
(see links in 20190 if you are interested); but for this new bug I
couldn't think of a similar fix and ended up implementing Daniel's
other suggestion:

https://sourceware.org/ml/gdb-patches/2010-07/msg00393.html

That is, this patch makes it possible to detect whether a symbol needs
a specific frame, or whether it just needs the inferior to have
registers.

Built and regtested on x86-64 Fedora 24.

2016-07-26  Tom Tromey  <tom@tromey.com>

	* symtab.c (register_symbol_computed_impl): Update.
	PR python/20190:
	* value.h (symbol_read_needs): Declare.
	(symbol_read_needs_frame): Add comment.
	* symtab.h (struct symbol_computed_ops) <read_variable>: Update
	comment.
	<get_symbol_read_needs>: Rename.  Change return type.
	* findvar.c (symbol_read_needs): New function.
	(symbol_read_needs_frame): Rewrite.
	(default_read_var_value): Use symbol_read_needs.
	* dwarf2loc.c (struct symbol_needs_baton): Rename.
	<needs>: Renamed from needs_frame.  Changed type.
	(needs_frame_read_addr_from_reg, symbol_needs_get_reg_value)
	(symbol_needs_read_mem, symbol_needs_frame_base)
	(symbol_needs_frame_cfa, symbol_needs_tls_address)
	(symbol_needs_dwarf_call): Rename.
	(needs_dwarf_reg_entry_value): Update.
	(symbol_needs_ctx_funcs, dwarf2_loc_desc_get_symbol_read_needs):
	Rename and update.
	(locexpr_get_symbol_read_needs, loclist_symbol_needs): Likewise.
	(dwarf2_locexpr_funcs, dwarf2_loclist_funcs): Update.
	* defs.h (enum symbol_needs_kind): New.

2016-07-26  Tom Tromey  <tom@tromey.com>

	PR python/20190:
	* gdb.threads/tls.exp (check_thread_local): Add python symbol
	test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions
@ 2016-08-09 22:30 sergiodj+buildbot
  2016-08-09 22:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 22:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f348d89aeccaf3eb613e2f31a823baa64300bf88 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f348d89aeccaf3eb613e2f31a823baa64300bf88

Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions

gdb's (or gdbserver's) own signal handling should not interfere with
the signal dispositions their spawned children inherit.  However, it
currently does.  For example, some paths in gdb cause SIGPIPE to be
set to SIG_IGN, and as consequence, the child starts with SIGPIPE to
set to SIG_IGN too, even though gdb was started with SIGPIPE set to
SIG_DFL.

This is because the exec family of functions does not reset the signal
disposition of signals that are set to SIG_IGN:

  http://pubs.opengroup.org/onlinepubs/7908799/xsh/execve.html

  Signals set to the default action (SIG_DFL) in the calling process
  image are set to the default action in the new process
  image. Signals set to be ignored (SIG_IGN) by the calling process
  image are set to be ignored by the new process image. Signals set to
  be caught by the calling process image are set to the default action
  in the new process image (see <signal.h>).

And neither does it reset signal masks or flags.

In order to be transparent, when spawning new child processes to debug
(with "run", etc.), reset signal actions and mask back to what was
originally inherited from gdb/gdbserver's parent, just before execing
the target program to debug.

gdb/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	PR gdb/18653
	* Makefile.in (SFILES): Add
	common/signals-state-save-restore.c.
	(HFILES_NO_SRCDIR): Add common/signals-state-save-restore.h.
	(COMMON_OBS): Add signals-state-save-restore.o.
	(signals-state-save-restore.o): New rule.
	* configure: Regenerate.
	* fork-child.c: Include "signals-state-save-restore.h".
	(fork_inferior): Call restore_original_signals_state.
	* main.c: Include "signals-state-save-restore.h".
	(captured_main): Call save_original_signals_state.
	* common/common.m4: Add sigaction to AC_CHECK_FUNCS checks.
	* common/signals-state-save-restore.c: New file.
	* common/signals-state-save-restore.h: New file.

gdb/gdbserver/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	PR gdb/18653
	* Makefile.in (OBS): Add signals-state-save-restore.o.
	(signals-state-save-restore.o): New rule.
	* config.in: Regenerate.
	* configure: Regenerate.
	* linux-low.c: Include "signals-state-save-restore.h".
	(linux_create_inferior): Call
	restore_original_signals_state.
	* server.c: Include "dispositions-save-restore.h".
	(captured_main): Call save_original_signals_state.

gdb/testsuite/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	PR gdb/18653
	* gdb.base/signals-state-child.c: New file.
	* gdb.base/signals-state-child.exp: New file.
	* gdb.gdb/selftest.exp (do_steps_and_nexts): Add new pattern.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors
@ 2016-08-10  0:26 sergiodj+buildbot
  2016-08-10  0:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-10  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80614914274f7166baea2ec656aec6a949869324 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 80614914274f7166baea2ec656aec6a949869324

Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors

gdb 7.11 introduced an MI regression: a failing MI sync execution
command misses printing the MI prompt, and then all subsequent command
miss it too:

 $ gdb-7.11.1 -i=mi
 [...]
 p 1
 &"p 1\n"
 ~"$1 = 1"
 ~"\n"
 ^done
 (gdb)                                        <<< prompted ok
 -exec-continue
 ^error,msg="The program is not being run."   <<< missing prompt after this
 print 1
 &"print 1\n"
 ~"$2 = 1"
 ~"\n"
 ^done                                        <<< missing prompt after this


gdb 7.10.1 behaved correctly, even with "set mi-async on":

 -exec-continue
 ^error,msg="The program is not being run."
 (gdb)                                        <<< prompted ok

etc.

Bisecting points at:

  commit 0b333c5e7d6c
  Author: Pedro Alves <palves@redhat.com>
  Date:   Wed Sep 9 18:23:23 2015 +0100

      Merge async and sync code paths some more
  [...]

The problem is that when an exception is thrown, we leave the prompt
state set to PROMPT_BLOCKED, and then mi_execute_command_input_handler
doesn't print the prompt.  It used to work because before that patch,
we happened to skip disabling stdin if the current target didn't do
async (which it never does before execution).

I was surprised to find that this bug isn't caught by the testsuite,
so I made a thorough test that tests all combinations of pairs of:

 - a failing synchronous execution command
 - a failing non-execution command
 - a non-failing command

gdb/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	PR mi/20431
	* mi/mi-main.c (mi_execute_command): Enable input and set prompt
	state to PROMPT_NEEDED.

gdb/testsuite/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	PR mi/20431
	* gdb.mi/mi-cmd-error.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR gdb/20418 - Problems with synchronous commands and new-ui
@ 2016-08-10  1:19 sergiodj+buildbot
  2016-08-10  1:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-10  1:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3eb7562a983bab4c768983bcd85708852d171121 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3eb7562a983bab4c768983bcd85708852d171121

Fix PR gdb/20418 - Problems with synchronous commands and new-ui

When executing commands on a secondary UI running the MI interpreter,
some commands that should be synchronous are not.  MI incorrectly
continues processing input right after the synchronous command is
sent, before the target stops.

The problem happens when we emit MI async events (=library-loaded,
etc.), and we go about restoring the previous terminal state, we end
up calling target_terminal_ours, which incorrectly always installs the
current UI's input_fd in the event loop...  That is, code like this:

   old_chain = make_cleanup_restore_target_terminal ();
   target_terminal_ours_for_output ();

   fprintf_unfiltered (mi->event_channel, "library-loaded");

...

   do_cleanups (old_chain);

The fix is to move the add_file_handler/delete_file_handler calls out
of target_terminal_$foo, making these completely no-ops unless called
with the main UI as current UI.

gdb/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>

	PR gdb/20418
	* event-top.c (ui_register_input_event_handler)
	(ui_unregister_input_event_handler): New functions.
	(async_enable_stdin): Register input in the event loop.
	(async_disable_stdin): Unregister input from the event loop.
	(gdb_setup_readline): Register input in the event loop.
	* infrun.c (check_curr_ui_sync_execution_done): Register input in
	the event loop.
	* target.c (target_terminal_inferior): Don't unregister input from
	the event loop.
	(target_terminal_ours): Don't register input in the event loop.
	* target.h (target_terminal_inferior)
	(target_terminal_ours_for_output, target_terminal_ours): Update
	comments.
	* top.h (ui_register_input_event_handler)
	(ui_unregister_input_event_handler): New declarations.
	* utils.c (ui_unregister_input_event_handler_cleanup)
	(prepare_to_handle_input): New functions.
	(defaulted_query, prompt_for_continue): Use
	prepare_to_handle_input.

gdb/testsuite/ChangeLog:
2016-08-09  Pedro Alves  <palves@redhat.com>
	    Simon Marchi  <simon.marchi@ericsson.com>

	PR gdb/20418
	* gdb.mi/new-ui-mi-sync.c, gdb.mi/new-ui-mi-sync.exp: New files.
	* lib/mi-support.exp (mi_expect_interrupt): Remove anchors.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Quiet ARI gettext checks
@ 2016-08-10 21:20 sergiodj+buildbot
  2016-08-10 22:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-10 21:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 669f9429c7b5a9e827497c5ad70efb6a570c8c7d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 669f9429c7b5a9e827497c5ad70efb6a570c8c7d

Quiet ARI gettext checks

The ARI complains about this new file:

 common/signals-state-save-restore.c:46: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:59: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:87: warning: gettext: All messages should be marked up with _.
 common/signals-state-save-restore.c:92: warning: gettext: All messages should be marked up with _.

Since these are untranslatable strings, use () instead of _().

gdb/ChangeLog:
2016-08-10  Pedro Alves  <palves@redhat.com>

	* common/signals-state-save-restore.c
	(save_original_signals_state, restore_original_signals_state):
	Wrap perror_with_name arguments with '()'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support setting thread names (MS-Windows)
@ 2016-08-11  0:35 sergiodj+buildbot
  2016-08-11  0:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24cdb46e9f0a694b4fbc11085e094857f08c0419 ***

Author:   <lrn1986@gmail.com>
Branch: master
Commit: 24cdb46e9f0a694b4fbc11085e094857f08c0419

Support setting thread names (MS-Windows)

This is done by catching an exception number 0x406d1388 (it has no
documented name, though MSDN dubs it "MS_VC_EXCEPTION" in one code
example), which is thrown by the program.  The exception record
contains an ID of a thread and a name to give it.

This requires rolling back some changes in handle_exception(), which
now again returns more than two distinct values.  The new
HANDLE_EXCEPTION_IGNORED value means that gdb should just continue,
without returning the thread ID up the stack (which would result in
further handling of the exception, which is not what we want).

gdb/ChangeLog:
2016-08-10     <lrn1986@gmail.com>
	    Pedro Alves  <palves@redhat.com>

	* windows-nat.c (MS_VC_EXCEPTION): New define.
	(handle_exception_result): New enum.
	(windows_delete_thread): Free the thread's name.
	(handle_exception): Handle MS_VC_EXCEPTION.
	(get_windows_debug_event): Handle HANDLE_EXCEPTION_IGNORED.
	(windows_thread_name): New function.
	(windows_target): Install it as to_thread_name method.
	* NEWS: Mention the thread naming support on MS-Windows.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Set the ISA bit in microMIPS LA25 stub references
@ 2016-08-11  0:52 sergiodj+buildbot
  2016-08-11  1:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  0:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7318def0cbfc6f0e1bab5fb54306efaf9ed3a5c ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: c7318def0cbfc6f0e1bab5fb54306efaf9ed3a5c

MIPS/BFD: Set the ISA bit in microMIPS LA25 stub references

Fix a linker regression introduced with commit 9d862524f6ae ("MIPS:
Verify the ISA mode and alignment of branch and jump targets") causing a
build failure in microMIPS glibc where the `zdump' tool fails to link:

.../timezone/zdump.o: In function `yeartot':
.../timezone/zdump.c:758:(.text+0x62): Jump to a non-instruction-aligned address
.../timezone/zdump.c:758:(.text+0x76): Jump to a non-instruction-aligned address
.../timezone/zdump.c:768:(.text+0x112): Jump to a non-instruction-aligned address
.../timezone/zdump.c:774:(.text+0x1b8): Jump to a non-instruction-aligned address
.../timezone/zdump.c:774:(.text+0x1cc): Jump to a non-instruction-aligned address
collect2: error: ld returned 1 exit status
make[2]: *** [.../timezone/zdump] Error 1

The cause of the failure is the stricter check introduced with the said
change for jump and branch targets tripping on the address of microMIPS
LA25 stubs.  Despite being microMIPS code these stubs do not have the
ISA bit set throughout the relocation calculation process, because they
have their address set to the memory offset into the stub section they
are placed in.

The `mips_elf_la25_stub' structure does not carry ISA mode information,
but there is no need to extend it, because the ISA mode can be inferred
from the original symbol, which will have STO_MICROMIPS annotation, so
use that instead to set the ISA bit appropriately.  Also only LA25 stubs
associated with microMIPS symbols need to have the ISA bit set, because
other LA25 stubs are made with regular MIPS code, even if associated
with a MIPS16 symbol (in which case they are needed by a call thunk only
rather than the MIPS16 function proper).

	bfd/
	* elfxx-mips.c (mips_elf_calculate_relocation): Set the ISA bit
	in microMIPS LA25 stub references.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Add microMIPS annotation to LA25 stub symbols
@ 2016-08-11  1:15 sergiodj+buildbot
  2016-08-11  1:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  1:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a848a2271b9bd45400e875a2518ebedf1efba2fa ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: a848a2271b9bd45400e875a2518ebedf1efba2fa

MIPS/BFD: Add microMIPS annotation to LA25 stub symbols

Fix a problem with missing microMIPS symbol annotation with microMIPS
LA25 stub symbols.  The consequence of the issue is these symbols appear
in the symbol table as regular MIPS symbols with the ISA bit set, as
shown with the example below:

$ cat la25a.s
	.abicalls

	.global	f1
	.ent	f1
f1:
	.set	noreorder
	.cpload	$25
	.set	reorder
	.option	pic0
	jal	f2
	.option	pic2
	jr	$31
	.end	f1

	.global	f2
	.ent	f2
f2:
	jr	$31
	.end	f2
$ cat la25b.s
	.abicalls
	.option	pic0

	.global	__start
	.ent	__start
__start:
	jal	f1
	jal	f2
	.end	__start
$ as -mmicromips -32 -EB -o la25a.o la25a.s
$ as -mmicromips -32 -EB -o la25b.o la25b.s
$ ld -melf32btsmip -o la25 la25a.o la25b.o
$ readelf -s la25

Symbol table '.symtab' contains 18 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00400098     0 SECTION LOCAL  DEFAULT    1
     2: 004000b0     0 SECTION LOCAL  DEFAULT    2
     3: 004000d0     0 SECTION LOCAL  DEFAULT    3
     4: 00000000     0 SECTION LOCAL  DEFAULT    4
     5: 00000000     0 SECTION LOCAL  DEFAULT    5
     6: 00418110     0 NOTYPE  LOCAL  DEFAULT    3 _gp
     7: 004000e1    16 FUNC    LOCAL  DEFAULT    3 .pic.f1
     8: 004000d1    16 FUNC    LOCAL  DEFAULT    3 .pic.f2
     9: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _fdata
    10: 00400110    16 FUNC    GLOBAL DEFAULT [MICROMIPS]     3 __start
    11: 00400106     2 FUNC    GLOBAL DEFAULT [MICROMIPS]     3 f2
    12: 004000d0     0 NOTYPE  GLOBAL DEFAULT    3 _ftext
    13: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 __bss_start
    14: 004000f0    22 FUNC    GLOBAL DEFAULT [MICROMIPS]     3 f1
    15: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _edata
    16: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _end
    17: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _fbss
$

where microMIPS annotation is missing for `.pic.f1' and `.pic.f2' even
though these stubs are associated with microMIPS functions `f1' and `f2'
respectively.

Add the missing annotation then, by copying it from the function symbol
an LA25 stub is associated with, correcting the example above:

$ readelf -s la25

Symbol table '.symtab' contains 18 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00400098     0 SECTION LOCAL  DEFAULT    1
     2: 004000b0     0 SECTION LOCAL  DEFAULT    2
     3: 004000d0     0 SECTION LOCAL  DEFAULT    3
     4: 00000000     0 SECTION LOCAL  DEFAULT    4
     5: 00000000     0 SECTION LOCAL  DEFAULT    5
     6: 00418110     0 NOTYPE  LOCAL  DEFAULT    3 _gp
     7: 004000e0    16 FUNC    LOCAL  DEFAULT [MICROMIPS]     3 .pic.f1
     8: 004000d0    16 FUNC    LOCAL  DEFAULT [MICROMIPS]     3 .pic.f2
     9: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _fdata
    10: 00400110    16 FUNC    GLOBAL DEFAULT [MICROMIPS]     3 __start
    11: 00400106     2 FUNC    GLOBAL DEFAULT [MICROMIPS]     3 f2
    12: 004000d0     0 NOTYPE  GLOBAL DEFAULT    3 _ftext
    13: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 __bss_start
    14: 004000f0    22 FUNC    GLOBAL DEFAULT [MICROMIPS]     3 f1
    15: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _edata
    16: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _end
    17: 00410120     0 NOTYPE  GLOBAL DEFAULT    3 _fbss
$

This problem has been there since the beginning of microMIPS support:

commit df58fc944dbc6d5efd8d3826241b64b6af22f447
Author: Richard Sandiford <rdsandiford@googlemail.com>
Date:   Sun Jul 24 14:20:15 2011 +0000

<https://sourceware.org/ml/binutils/2011-07/msg00198.html>, ("MIPS:
microMIPS ASE support").

	bfd/
	* elfxx-mips.c (mips_elf_create_stub_symbol): For a microMIPS
	stub also add STO_MICROMIPS annotation.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Simplify remove_breakpoint interface
@ 2016-08-11  5:30 sergiodj+buildbot
  2016-08-11 16:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  5:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 834c0d033bdade640aab149d0d4bd7b41dcb16af ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 834c0d033bdade640aab149d0d4bd7b41dcb16af

Simplify remove_breakpoint interface

All callers pass mark_uninserted, so there's no need for the 'is'
parameter.

gdb/ChangeLog:
2016-08-10  Pedro Alves  <palves@redhat.com>

	PR gdb/19187
	* breakpoint.c (remove_breakpoint): Remove 'is' parameter and
	always pass mark_uninserted to remove_breakpoint_1.
	(insert_breakpoint_locations, remove_breakpoints)
	(remove_breakpoints_pid, update_global_location_list): Update
	callers.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR gdb/19187 (process record over a fork causes internal error)
@ 2016-08-11  7:55 sergiodj+buildbot
  2016-08-12  0:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  7:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01d3dedf60912cee478c242d575f4683adada1d2 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 01d3dedf60912cee478c242d575f4683adada1d2

Fix PR gdb/19187 (process record over a fork causes internal error)

Right after a fork is detected, we detach breakpoints from the child
(detach_breakpoints), which calls into target_remove_breakpoint with
inferior_ptid pointing at the child process, but leaves the breakpoint
marked inserted (in the parent).

The problem is that record-full.c always deletes all knowledge of the
breakpoint.  Then when we later really delete the breakpoint from the
parent, we fail the assertion, since the breakpoint is unexpectedly
not found in the record-full.c breakpoint table.

The fix is simply to not forget about the breakpoint if we're
detaching it from a fork child.

gdb/ChangeLog:
2016-08-10  Pedro Alves  <palves@redhat.com>

	PR gdb/19187
	* record-full.c (record_full_remove_breakpoint): Don't remove the
	breakpoint from the record_full_breakpoints VEC if we're detaching
	the breakpoint from a fork child.

gdb/testsuite/ChangeLog:
2016-08-10  Pedro Alves  <palves@redhat.com>

	PR gdb/19187
	* gdb.reverse/waitpid-reverse.exp: Add comment and remove
	setup_kfails.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce 'enum remove_bp_reason'
@ 2016-08-11  8:00 sergiodj+buildbot
  2016-08-11 22:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  8:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2b6a7dab91de9a616e1d76c869d127c5752b9e6 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b2b6a7dab91de9a616e1d76c869d127c5752b9e6

Introduce 'enum remove_bp_reason'

Makes the code more obvious.

gdb/ChangeLog:
2016-08-10  Pedro Alves  <palves@redhat.com>

	PR gdb/19187
	* breakpoint.c (insertion_state_t): Delete.
	(enum remove_bp_reason): New.
	(detach_breakpoints, remove_breakpoint_1, remove_breakpoint):
	Adjust to use enum remove_bp_reason instead of insertion_state_t.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PowerPC64 ELFv1 undefined weak functions
@ 2016-08-11 10:04 sergiodj+buildbot
  2016-08-12  1:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-11 10:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d93d1c80b351a424c1737436b5e7dfb44ddc9d46 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: d93d1c80b351a424c1737436b5e7dfb44ddc9d46

PowerPC64 ELFv1 undefined weak functions

Undefined weak functions, like __gmon_start__, were not being made
dynamic or emitting plt call code.  While the behaviour of undefined
weak symbols is not defined in the ELF standard, the intention on
powerpc64 was to make it possible to link without a definition of such
symbols and at run time behave the same as if a definition was found
at link time in a shared library.

	* elf64-ppc.c (ppc64_elf_adjust_dynamic_symbol): Don't exit with
	non_got_ref true in any case where we could have generated dynbss
	copies but decide not to do so.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER)
@ 2016-08-12 10:33 sergiodj+buildbot
  2016-08-12 11:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-12 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39b22471578843019026c50fcdbe0483a6045970 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 39b22471578843019026c50fcdbe0483a6045970

Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER)

Fixes, on NIOS GNU/Linux:

  In file included from
  /scratch/mbilal/nois-lite/src/gdb-trunk/gdb/gdbserver/../nat/linux-ptrace.c:26:0:
  /scratch/mbilal/nois-lite/src/gdb-trunk/gdb/gdbserver/../gregset.h:27:23:
  error: unknown type name 'gregset_t'
   #define GDB_GREGSET_T gregset_t
			 ^

Fix this by including sys/procfs.h directly.  We shouldn't really be
including a gdb-only header in a gdb/nat/ file, anyway.  Whoops.

gdb/ChangeLog:
2016-08-11  Pedro Alves  <palves@redhat.com>

	PR gdb/20413
	* nat/linux-ptrace.c: Include <sys/procfs.h> instead of
	"gregset.h".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Export the single step function from the AArch64 simulator.
@ 2016-08-12 11:02 sergiodj+buildbot
  2016-08-12 12:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-12 11:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a2775793d17c8a73956977c75111b33ec10ec37 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6a2775793d17c8a73956977c75111b33ec10ec37

Export the single step function from the AArch64 simulator.

	* interp.c (sim_create_inferior): Allow for being called with a
	NULL abfd parameter.  If a bfd is provided, initialise the sim
	with that start address.
	* simulator.c (HALT_NYI): Just print out the numeric value of the
	instruction when not tracing.
	(aarch64_step): Change from static to global.
	* simulator.h: Add a prototype for aarch64_step().


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix warning in gdb.base/signals-state-child.c
@ 2016-08-12 13:46 sergiodj+buildbot
  2016-08-12 14:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-12 13:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b17065f843252c27e8b9c093f78382079fe4d7f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7b17065f843252c27e8b9c093f78382079fe4d7f

Fix warning in gdb.base/signals-state-child.c

I see the following warning when running signals-state-child.exp.

gdb/testsuite/gdb.base/signals-state-child.c:77:4: warning: too many arguments for format [-Wformat-extra-args]
    fprintf (out, "sigaction={sa_handler=", i);
    ^

this patch is to remove the argument from fprintf.

gdb/testsuite:

2016-08-12  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/signals-state-child.c (main): Remove "i" from fprintf's
	argument list.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Undo the previous change to the aarch64 sim - exporting aarch64_step() - and instead make aarch64_run correctly process sim events.
@ 2016-08-12 18:13 sergiodj+buildbot
  2016-08-13 20:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-12 18:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b14bdb3bab20db9d200d669dfb5e2eadde7b14cc ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: b14bdb3bab20db9d200d669dfb5e2eadde7b14cc

Undo the previous change to the aarch64 sim - exporting aarch64_step() - and instead make aarch64_run correctly process sim events.

	* simulator.c (aarch64_step): Revert pervious delta.
	(aarch64_run): Call sim_events_tick after each
	instruction is simulated, and if necessary call
	sim_events_process.
	* simulator.h: Revert previous delta.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Correct .dynsym sh_info
@ 2016-08-13 21:55 sergiodj+buildbot
  2016-08-13 21:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-13 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90ac242072dc68ad454aaaa228868b0f1c8e10f9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 90ac242072dc68ad454aaaa228868b0f1c8e10f9

Correct .dynsym sh_info

bfd/
	* elf-bfd.h (struct elf_link_hash_table): Add local_dynsymcount.
	* elflink.c (_bfd_elf_link_renumber_dynsyms): Set local_dynsymcount.
	(bfd_elf_final_link): Set .dynsym sh_info from local_dynsymcount.
ld/
	* testsuite/ld-tic6x/shlib-1.rd: Correct expected .dynsym sh_info.
	* testsuite/ld-tic6x/shlib-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/shlib-app-1rb.rd: Likewise.
	* testsuite/ld-tic6x/shlib-noindex.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1b.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1r.rd: Likewise.
	* testsuite/ld-tic6x/static-app-1rb.rd: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sim: bfin: split out common mach/model defines into arch.h [PR sim/20438]
@ 2016-08-14  1:05 sergiodj+buildbot
  2016-08-14  6:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-14  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 474a2d9f5f8a080e30812525729c3a8b7baa61d6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 474a2d9f5f8a080e30812525729c3a8b7baa61d6

sim: bfin: split out common mach/model defines into arch.h [PR sim/20438]

The current machs.h mixes common enums with Blackfin-specific defines.
This causes us troubles with header inclusion order such that we can't
drop the old SIM_CPU typedef (which is duplicated in common code).  By
splitting the two up, we can unwind this dependency chain, and drop the
old typedef.  It also fixes building with older gcc versions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sim: cgen: drop unused argv/envp definitions
@ 2016-08-14  7:01 sergiodj+buildbot
  2016-08-14 11:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-14  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b97945424f3714d2f9f6866079fd2bc658f4285 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 6b97945424f3714d2f9f6866079fd2bc658f4285

sim: cgen: drop unused argv/envp definitions

The common argv/envp are used now by all ports, so drop this old
cgen fragment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sim: cgen: constify mode_names
@ 2016-08-15 12:16 sergiodj+buildbot
  2016-08-15 12:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 12:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c171e25a8c83fc26b78430fa632fa9e64f61050 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 4c171e25a8c83fc26b78430fa632fa9e64f61050

sim: cgen: constify mode_names


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix heap-buffer-overflow in explicit_location_lex_one
@ 2016-08-15 14:48 sergiodj+buildbot
  2016-08-15 14:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31f9478185764487b1dcfb2803ed9c399c40ed1 ***

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

Fix heap-buffer-overflow in explicit_location_lex_one

I build GDB with -fsanitize=address, and see the error in tests,

(gdb) PASS: gdb.linespec/ls-errs.exp: lang=C++: break 3 foo
break -line 3 foo^M
=================================================================^M
==4401==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000047487 at pc 0x819d8e bp 0x7fff4e4e6bb0 sp 0x7fff4e4e6ba8^M
READ of size 1 at 0x603000047487 thread T0^[[1m^[[0m^M
    #0 0x819d8d in explicit_location_lex_one /home/yao/SourceCode/gnu/gdb/git/gdb/location.c:502^M
    #1 0x81a185 in string_to_explicit_location(char const**, language_defn const*, int) /home/yao/SourceCode/gnu/gdb/git/gdb/location.c:556^M
    #2 0x81ac10 in string_to_event_location(char**, language_defn const*) /home/yao/SourceCode/gnu/gdb/git/gdb/location.c:687^

the code in question is:

>         /* Special case: C++ operator,.  */
>         if (language->la_language == language_cplus
>             && strncmp (*inp, "operator", 8)  <--- [1]
>             && (*inp)[9] == ',')
>           (*inp) += 9;
>         ++(*inp);

The error is caused by the access to (*inp)[9] if 9 is out of its bounds.
However [1] looks odd to me, because if strncmp returns true (non-zero),
the following check "(*inp)[9] == ','" makes no sense any more.  I
suspect it was a typo in the code we meant to "strncmp () == 0".  Another
problem in the code above is that if *inp is "operator,", we first
increment *inp by 9, and then increment it by one again, which is wrong
to me.  We should only increment *inp by 8 to skip "operator", and go
back to the loop header to decide where we stop.

gdb:

2016-08-15  Yao Qi  <yao.qi@linaro.org>

	* location.c (explicit_location_lex_one): Compare the return
	value of strncmp with zero.  Don't check (*inp)[9].  Increment
	*inp by 8.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sim: m68hc11: use standard STATIC_INLINE helper
@ 2016-08-17 21:25 sergiodj+buildbot
  2016-08-17 21:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-17 21:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa0843f50204bfd46b444c0ded6a1df1051c876e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: fa0843f50204bfd46b444c0ded6a1df1051c876e

sim: m68hc11: use standard STATIC_INLINE helper

Rather than redefine inline locally, use the common STATIC_INLINE.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add remove-inferiors test
@ 2016-08-18 14:37 sergiodj+buildbot
  2016-08-18 14:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-18 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63c61e04bb7168f0819fc590ac44e7583b225f7b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 63c61e04bb7168f0819fc590ac44e7583b225f7b

Add remove-inferiors test

I noticed that the remove-inferiors command was not tested, and as I am
doing some changes related to the user selection, I want to make sure I
don't break it.  For example, I want to make sure it's not possible to
remove the current inferior.

gdb/testsuite/ChangeLog:

	* gdb.multi/remove-inferiors.exp: New file.
	* gdb.multi/remove-inferiors.c: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix remove-inferior error message
@ 2016-08-18 15:13 sergiodj+buildbot
  2016-08-18 17:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-18 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb2332d78d4ef40a2696aa0f6c833ea26a739efc ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: eb2332d78d4ef40a2696aa0f6c833ea26a739efc

Fix remove-inferior error message

This error message should not contain the word symbol:

  (gdb) remove-inferiors 1
  Warning: Can not remove current symbol inferior 1.

gdb/ChangeLog:

	* inferior.c (remove_inferior_command): Fix error message.

gdb/testsuite/ChangeLog:

	* gdb.multi/remove-inferiors.exp (test_remove_inferiors): Fix
	expected error message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ppc: Fix record of HTM instructions
@ 2016-08-18 21:19 sergiodj+buildbot
  2016-08-18 21:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-18 21:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d44c67f38178c5ad0c083ebff6429d6e477ea42e ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: d44c67f38178c5ad0c083ebff6429d6e477ea42e

ppc: Fix record of HTM instructions

The patch fixes the record support of Hardware Transactional Memory
instructions on Power. It also solves a large number of unexpected failures
from gdb.reverse testcases sigall-precsave.exp and sigall-reverse.exp that
occur on distros which glibc uses HTM instructions.

gdb/ChangeLog
2016-08-18  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (ppc_process_record_op31): Handle HTM instructions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add myself as write-after-approval GDB maintainer.
@ 2016-08-19  5:31 sergiodj+buildbot
  2016-08-19  8:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19  5:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e859fd22942c6b8077416e01e50355da6cbc052 ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: 6e859fd22942c6b8077416e01e50355da6cbc052

Add myself as write-after-approval GDB maintainer.

gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add "Carl Love".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR 20472, PowerPC64 ifunc confusion
@ 2016-08-19 12:02 sergiodj+buildbot
  2016-08-19 12:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a2058b5e3318a337a6fecd61b91349d1131758e ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8a2058b5e3318a337a6fecd61b91349d1131758e

PR 20472, PowerPC64 ifunc confusion

This patch fixes quite a lot of confusion in allocate_dynrelocs over
ifuncs.  Function descriptors make ELFv1 quite different to ELFv2.

	PR 20472
	* elf64-ppc.c (ppc64_elf_before_check_relocs): Tweak abiversion test.
	(readonly_dynrelocs): Comment fix.
	(global_entry_stub): New function.
	(ppc64_elf_adjust_dynamic_symbol): Tweak abiversion test.  Match
	ELFv2 code deciding on dynamic relocs vs. global entry stubs to
	that in size_global_entry_stubs, handling ifunc too.  Delete dead
	weak sym code.
	(allocate_dynrelocs): Ensure dyn_relocs field is cleared when no
	dyn_relocs are needed.  Correct handling of ifunc dyn_relocs.
	Tidy ELIMINATE_COPY_RELOCS code, only setting dynindx for
	undefweak syms.  Expand and correct comments.
	(size_global_entry_stubs): Ensure symbol is defined.
	(ppc64_elf_relocate_section): Match condition under which
	dyn_relocs are emitted to that in allocate_dynrelocs.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PowerPC64, Don't copy weak symbol dyn_relocs to weakdef.
@ 2016-08-19 12:40 sergiodj+buildbot
  2016-08-19 13:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 12:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d311bc8bf85f8358df21301fe8a357aa1212f80c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: d311bc8bf85f8358df21301fe8a357aa1212f80c

PowerPC64, Don't copy weak symbol dyn_relocs to weakdef.

At the cost of an extra field in the symbol table hash entries, this
simplification to the relocate_section dynamic reloc test should help
maintainability.

	* elf64-ppc.c (struct ppc_link_hash_entry): Add weakref.
	(ppc64_elf_copy_indirect_symbol): Set weakref.  Don't merge
	dyn_relocs for weakdefs.
	(alias_readonly_dynrelocs): New function.
	(ppc64_elf_adjust_dynamic_symbol): Use alias_readonly_dynrelocs.
	(ppc64_elf_relocate_section): Simplify condition under which
	dyn_relocs are emitted.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Place .shstrtab section after .symtab and .strtab, thus restoring monotonically increasing section offsets.
@ 2016-08-19 14:59 sergiodj+buildbot
  2016-08-19 15:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd90581873482f67922a4ace92dafdfdfed09f3c ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: dd90581873482f67922a4ace92dafdfdfed09f3c

Place .shstrtab section after .symtab and .strtab, thus restoring monotonically increasing section offsets.

bfd
  * elf.c (assign_section_numbers): Assign number for the .shstrtab
  section after the symbol table and string table sections.

binutils
  * testsuite/binutils-all/readelf.s: Adjust expected ordering of
  sections.
  * testsuite/binutils-all/readelf.s-64: Likewise.

gas
  * testsuite/gas/i386/ilp32/x86-64-unwind.d: Adjust expected ordering
  of sections.
  * testsuite/gas/i386/x86-64-unwind.d: Likewise.
  * testsuite/gas/ia64/alias-ilp32.d: Likewise.
  * testsuite/gas/ia64/alias.d: Likewise.
  * testsuite/gas/ia64/group-1.d: Likewise.
  * testsuite/gas/ia64/group-2.d: Likewise.
  * testsuite/gas/ia64/secname-ilp32.d: Likewise.
  * testsuite/gas/ia64/secname.d: Likewise.
  * testsuite/gas/ia64/unwind-ilp32.d: Likewise.
  * testsuite/gas/ia64/unwind.d: Likewise.
  * testsuite/gas/ia64/xdata-ilp32.d: Likewise.
  * testsuite/gas/ia64/xdata.d: Likewise.
  * testsuite/gas/mmix/bspec-1.d: Likewise.
  * testsuite/gas/mmix/bspec-2.d: Likewise.
  * testsuite/gas/mmix/byte-1.d: Likewise.
  * testsuite/gas/mmix/loc-1.d: Likewise.
  * testsuite/gas/mmix/loc-2.d: Likewise.
  * testsuite/gas/mmix/loc-3.d: Likewise.
  * testsuite/gas/mmix/loc-4.d: Likewise.
  * testsuite/gas/mmix/loc-5.d: Likewise.
  * testsuite/gas/tic6x/scomm-directive-4.d: Likewise.

ld
  * testsuite/ld-alpha/tlsbin.rd: Adjust expected ordering of sections.
  * testsuite/ld-alpha/tlsbinr.rd: Likewise.
  * testsuite/ld-alpha/tlspic.rd: Likewise.
  * testsuite/ld-cris/libdso-2.d: Likewise.
  * testsuite/ld-i386/nogot1.d: Likewise.
  * testsuite/ld-i386/pr12718.d: Likewise.
  * testsuite/ld-i386/pr12921.d: Likewise.
  * testsuite/ld-i386/tlsbin-nacl.rd: Likewise.
  * testsuite/ld-i386/tlsbin.rd: Likewise.
  * testsuite/ld-i386/tlsbin2-nacl.rd: Likewise.
  * testsuite/ld-i386/tlsbin2.rd: Likewise.
  * testsuite/ld-i386/tlsbindesc-nacl.rd: Likewise.
  * testsuite/ld-i386/tlsbindesc.rd: Likewise.
  * testsuite/ld-i386/tlsdesc-nacl.rd: Likewise.
  * testsuite/ld-i386/tlsdesc.rd: Likewise.
  * testsuite/ld-i386/tlsgdesc-nacl.rd: Likewise.
  * testsuite/ld-i386/tlsgdesc.rd: Likewise.
  * testsuite/ld-i386/tlsnopic-nacl.rd: Likewise.
  * testsuite/ld-i386/tlsnopic.rd: Likewise.
  * testsuite/ld-i386/tlspic-nacl.rd: Likewise.
  * testsuite/ld-i386/tlspic.rd: Likewise.
  * testsuite/ld-i386/tlspic2-nacl.rd: Likewise.
  * testsuite/ld-i386/tlspic2.rd: Likewise.
  * testsuite/ld-ia64/tlsbin.rd: Likewise.
  * testsuite/ld-ia64/tlspic.rd: Likewise.
  * testsuite/ld-mips-elf/attr-gnu-4-10.d: Likewise.
  * testsuite/ld-mips-elf/attr-gnu-4-50.d: Likewise.
  * testsuite/ld-mips-elf/attr-gnu-4-60.d: Likewise.
  * testsuite/ld-mips-elf/attr-gnu-4-70.d: Likewise.
  * testsuite/ld-mmix/bspec1.d: Likewise.
  * testsuite/ld-mmix/bspec2.d: Likewise.
  * testsuite/ld-mmix/local1.d: Likewise.
  * testsuite/ld-mmix/local3.d: Likewise.
  * testsuite/ld-mmix/local5.d: Likewise.
  * testsuite/ld-mmix/local7.d: Likewise.
  * testsuite/ld-mmix/undef-3.d: Likewise.
  * testsuite/ld-powerpc/tlsexe.r: Likewise.
  * testsuite/ld-powerpc/tlsexe32.r: Likewise.
  * testsuite/ld-powerpc/tlsexetoc.r: Likewise.
  * testsuite/ld-powerpc/tlsso.r: Likewise.
  * testsuite/ld-powerpc/tlsso32.r: Likewise.
  * testsuite/ld-powerpc/tlstocso.r: Likewise.
  * testsuite/ld-s390/tlsbin.rd: Likewise.
  * testsuite/ld-s390/tlsbin_64.rd: Likewise.
  * testsuite/ld-s390/tlspic.rd: Likewise.
  * testsuite/ld-s390/tlspic_64.rd: Likewise.
  * testsuite/ld-sh/sh64/crange1.rd: Likewise.
  * testsuite/ld-sh/sh64/crange2.rd: Likewise.
  * testsuite/ld-sh/sh64/crange3-cmpct.rd: Likewise.
  * testsuite/ld-sh/sh64/crange3-media.rd: Likewise.
  * testsuite/ld-sh/sh64/crange3.rd: Likewise.
  * testsuite/ld-sh/sh64/crangerel1.rd: Likewise.
  * testsuite/ld-sh/sh64/crangerel2.rd: Likewise.
  * testsuite/ld-sh/tlsbin-2.d: Likewise.
  * testsuite/ld-sh/tlspic-2.d: Likewise.
  * testsuite/ld-sparc/gotop32.rd: Likewise.
  * testsuite/ld-sparc/gotop64.rd: Likewise.
  * testsuite/ld-sparc/tlssunbin32.rd: Likewise.
  * testsuite/ld-sparc/tlssunbin64.rd: Likewise.
  * testsuite/ld-sparc/tlssunnopic32.rd: Likewise.
  * testsuite/ld-sparc/tlssunnopic64.rd: Likewise.
  * testsuite/ld-sparc/tlssunpic32.rd: Likewise.
  * testsuite/ld-sparc/tlssunpic64.rd: Likewise.
  * testsuite/ld-tic6x/common.d: Likewise.
  * testsuite/ld-tic6x/shlib-1.rd: Likewise.
  * testsuite/ld-tic6x/shlib-1b.rd: Likewise.
  * testsuite/ld-tic6x/shlib-1r.rd: Likewise.
  * testsuite/ld-tic6x/shlib-1rb.rd: Likewise.
  * testsuite/ld-tic6x/shlib-app-1.rd: Likewise.
  * testsuite/ld-tic6x/shlib-app-1b.rd: Likewise.
  * testsuite/ld-tic6x/shlib-app-1r.rd: Likewise.
  * testsuite/ld-tic6x/shlib-app-1rb.rd: Likewise.
  * testsuite/ld-tic6x/shlib-noindex.rd: Likewise.
  * testsuite/ld-tic6x/static-app-1.rd: Likewise.
  * testsuite/ld-tic6x/static-app-1b.rd: Likewise.
  * testsuite/ld-tic6x/static-app-1r.rd: Likewise.
  * testsuite/ld-tic6x/static-app-1rb.rd: Likewise.
  * testsuite/ld-x86-64/ilp32-4-nacl.d: Likewise.
  * testsuite/ld-x86-64/ilp32-4.d: Likewise.
  * testsuite/ld-x86-64/nogot1.d: Likewise.
  * testsuite/ld-x86-64/pr12718.d: Likewise.
  * testsuite/ld-x86-64/pr12921.d: Likewise.
  * testsuite/ld-x86-64/split-by-file-nacl.rd: Likewise.
  * testsuite/ld-x86-64/split-by-file.rd: Likewise.
  * testsuite/ld-x86-64/tlsbin-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlsbin.rd: Likewise.
  * testsuite/ld-x86-64/tlsbin2-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlsbin2.rd: Likewise.
  * testsuite/ld-x86-64/tlsbindesc-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlsbindesc.rd: Likewise.
  * testsuite/ld-x86-64/tlsdesc-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlsdesc.rd: Likewise.
  * testsuite/ld-x86-64/tlsgdesc-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlsgdesc.rd: Likewise.
  * testsuite/ld-x86-64/tlspic-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlspic.rd: Likewise.
  * testsuite/ld-x86-64/tlspic2-nacl.rd: Likewise.
  * testsuite/ld-x86-64/tlspic2.rd: Likewise.
  * testsuite/ld-xtensa/tlsbin.rd: Likewise.
  * testsuite/ld-xtensa/tlspic.rd: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x32 Fast tracepoints: IPA target descriptions
@ 2016-08-19 16:06 sergiodj+buildbot
  2016-08-19 16:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 16:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 201506dadd117df72d0528f735e44ce2e68cc66f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 201506dadd117df72d0528f735e44ce2e68cc66f

x32 Fast tracepoints: IPA target descriptions

Building GDB for x32 fails building the IPA, with:

   .../src/gdb/gdbserver/linux-amd64-ipa.c: In function const target_desc* get_ipa_tdesc(int):
   .../src/gdb/gdbserver/linux-amd64-ipa.c:182:14: error: tdesc_amd64_avx_linux was not declared in this scope
	  return tdesc_amd64_avx_linux;
		 ^
   .../src/gdb/gdbserver/linux-amd64-ipa.c:184:14: error: tdesc_amd64_mpx_linux was not declared in this scope
	  return tdesc_amd64_mpx_linux;
		 ^
   .../src/gdb/gdbserver/linux-amd64-ipa.c:186:14: error: tdesc_amd64_avx_mpx_linux was not declared in this scope
	  return tdesc_amd64_avx_mpx_linux;
		 ^
  [...]

The problem is that the IPA is trying to use the 64-bit descriptions,
when it should be using the x32 ones.

gdb/gdbserver/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

	PR gdb/20415
	* Makefile.in (x32-linux-ipa.o, x32-avx-linux-ipa.o)
	(x32-avx512-linux-ipa.o): New rules.
	* configure.ac (x86_64-*-linux*): New x32 check.
	* configure.srv (ipa_x32_linux_regobj): New.
	(x86_64-*-linux*): Use $ipa_x32_linux_regobj if building for x32.
	* linux-amd64-ipa.c (get_ipa_tdesc) [__ILP32__]: Return x32
	descriptions.
	(initialize_low_tracepoint) [__ILP32__]: Initialize x32
	descriptions.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x32 Fast tracepoints: Customize jump pad address
@ 2016-08-19 16:23 sergiodj+buildbot
  2016-08-19 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c235a72a112c5656f17499c0c0d3ad73609833d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9c235a72a112c5656f17499c0c0d3ad73609833d

x32 Fast tracepoints: Customize jump pad address

MAP_32BIT is ignored on x32, meaning the jump pad can end up somewhere
between 2GB and 4GB, too far away from the executable for 5-byte
relative jumps (JMP rel32).  So on x32, try explicitly placing the
jump pad near the middle of the available address space.

gdb/gdbserver/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

	* linux-amd64-ipa.c (alloc_jump_pad_buffer) [__ILP32__]: Try
	allocating around 0x80000000.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x32: gdbserver's agent bytecode JIT: fix "call" emission
@ 2016-08-19 16:52 sergiodj+buildbot
  2016-08-19 17:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed036b4052193ba6790ba7ee94a33a364ace3b55 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ed036b4052193ba6790ba7ee94a33a364ace3b55

x32: gdbserver's agent bytecode JIT: fix "call" emission

Running fast tracepoint tests on x32 exposes a latent bug in the agent
bytecode jitting.  There's a code path that forgets to emit the call
opcode...  Whoops.  Fixes a bunch of gdb.trace/trace-condition.exp
FAILs, like:

  (gdb)
  continue
  Continuing.

  Thread 1 "trace-condition" received signal SIGSEGV, Segmentation fault.
  0x7ffec016 in ?? ()
  (gdb) FAIL: gdb.trace/trace-condition.exp: ftrace: $rip == *set_point: advance through tracing

gdb/gdbserver/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

	* linux-x86-low.c (amd64_emit_call): Emit missing call opcode.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x32: Avoid unsigned long when installing fast tracepoint jump pads
@ 2016-08-19 17:02 sergiodj+buildbot
  2016-08-19 17:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8ef42eed100c2439e600e846caa7437da93ac17 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c8ef42eed100c2439e600e846caa7437da93ac17

x32: Avoid unsigned long when installing fast tracepoint jump pads

We're casting through unsigned long to write a 64-bit immediate
operand of movabs (the comment said movl, but that was incorrect).
The problem is that unsigned long is 32-bit on x32, so we were writing
fewer bytes than necessary.

Fix this by using an 8 byte memcpy like in other similar places in the
function.

gdb/gdbserver/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

	* linux-x86-low.c (amd64_install_fast_tracepoint_jump_pad): Fix
	comment.  Use memcpy instead of casting through unsigned long.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] x32: gdb: Fix 'call' insn relocation with qRelocInsn
@ 2016-08-19 18:19 sergiodj+buildbot
  2016-08-19 19:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f077e978deccac00fea013c4f120122bf6726834 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f077e978deccac00fea013c4f120122bf6726834

x32: gdb: Fix 'call' insn relocation with qRelocInsn

Running the fast tracepoints tests against x32 gdbserver exposes a
latent bug.  E.g.,:

 (gdb)
 continue
 Continuing.
 Reading /media/sf_host-pedro/gdb/mygit/build-ubuntu-x32/gdb/testsuite/outputs/gdb.trace/change-loc/change-loc-2.sl from remote target...

 Thread 1 "change-loc" received signal SIGSEGV, Segmentation fault.
 func4 () at /home/pedro/gdb/src/gdb/testsuite/gdb.trace/change-loc.h:24
 24      }
 (gdb) FAIL: gdb.trace/change-loc.exp: 1 ftrace: continue to marker 2

The test sets a fast tracepoint on a shared library.  On x32, shared
libraries end up loaded somewhere in the upper 2GB of the 4GB address
space x32 has access to.  When gdbserver needs to copy an instruction
to execute it in the jump pad, it asks gdb to relocate/adjust it, with
the qRelocInsn packet.  gdb converts "call" instructions into a "push
$<2GB-4GB addr> + jmp" sequence, however, the "pushq" instruction sign
extends its operand, so later when the called function returns, it
returns to an incorrectly sign-extended address.  E.g.,
0xfffffffffabc0000 instead of 0xfabc0000, resulting in the
segmentation fault.

Fix this by converting calls at such addresses to "sub + mov + jmp"
sequences instead.

gdb/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

	* amd64-tdep.c (amd64_relocate_instruction) <callq>: Handle return
	addresses over 0x7fffffff.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Match instruction "STP with base register" in prologue
@ 2016-08-19 19:59 sergiodj+buildbot
  2016-08-20  8:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-19 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03bcd7394eefb9399f5ab97919a0463dea274c02 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 03bcd7394eefb9399f5ab97919a0463dea274c02

[AArch64] Match instruction "STP with base register" in prologue

Nowadays, we only match pre-indexed STP in prologue.  Due to the change
in gcc, https://gcc.gnu.org/ml/gcc-patches/2016-07/msg01933.html, it
may generate "STP with base register" in prologue, which GDB doesn't
handle.  That is to say, previously GCC generates prologue like this,

 sub sp, sp, #490
 stp x29, x30, [sp, #-96]!
 mov x29, sp

with the gcc patch above, GCC generates prologue like like this,

 sub sp, sp, #4f0
 stp x29, x30, [sp]
 mov x29, sp

This patch is to teach GDB to recognize this instruction in prologue
analysis.

gdb:

2016-08-19  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (aarch64_analyze_prologue): Handle register
	based STP instruction.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Error on unsupported PowerPC ifuncs
@ 2016-08-22 20:15 sergiodj+buildbot
  2016-08-22 20:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-22 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 888a7fc3665a67e20da1bce2f865b0ff9ef15842 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 888a7fc3665a67e20da1bce2f865b0ff9ef15842

Error on unsupported PowerPC ifuncs

The pr19784 tests fail on ppc32 due to a gcc bug.  The failure should
be noticed when building both libpr19784a.so and libpr19784b.so,
rather than ld building a buggy libpr19784a.so that fails at run time.
This patch fixes that by moving the @local ifunc check out of
check_relocs, where a call destination may not yet be known to be
ifunc.  The patch also adds a related error for -mbss-plt code.

	* elf32-ppc.c (ppc_elf_check_relocs): Move error for @local ifunc..
	(ppc_elf_relocate_section): ..to here.  Comment.  Error on
	detecting -mbss-plt -fPIC local ifuncs too.
	(ppc_elf_size_dynamic_sections): Comment on unnecessary glink
	branch table entries.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Free the string buffer used by the chew program to hold each file it parses.
@ 2016-08-22 21:15 sergiodj+buildbot
  2016-08-22 23:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-22 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fbe0d878a691b9be42bb2bdebd027ac3dfd38c2 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 5fbe0d878a691b9be42bb2bdebd027ac3dfd38c2

Free the string buffer used by the chew program to hold each file it parses.

	* doc/chew.c (main): Free the string buffer used to files as they
	are parsed.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR gdb/20505 - Make vDSO detection work with core files
@ 2016-08-23  4:03 sergiodj+buildbot
  2016-08-23  4:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6bb90213cb7b8e2f3be20f2e46f11f57f0c9ce55 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6bb90213cb7b8e2f3be20f2e46f11f57f0c9ce55

Fix PR gdb/20505 - Make vDSO detection work with core files

Loading a core dump that was either generated on a system running
pristine glibc master, or on a Fedora/RHEL system with LD_DEBUG=unused
set in the environment, solib-svr4.c:svr4_current_sos fails to filter
out the vDSO, resulting in:

  (gdb) core-file corefile.core^M
  [New LWP 2362]^M
  warning: Could not load shared library symbols for linux-vdso.so.1.^M
  Do you need "set solib-search-path" or "set sysroot"?^M
  Core was generated by `build-gdb/gdb/testsuite/outputs/gdb.base/corefile/'.^M
  ...

The problem is that gdbarch_vsyscall_range does not support core
inferiors at all.

When live debugging, we're finding the vDSO's start address with
auxv/AT_SYSINFO_EHDR, and then we find the vDSO's size by look for the
corresponding mapping, by parsing /proc/PID/maps.  When debugging a
core dump, we can also determine the starting address from
auxv/AT_SYSINFO_EHDR.  However, we obviously can't read the core
mappings out of the host's /proc.  But we can instead look for a
corresponding load segment in the core's bfd.

gdb/ChangeLog:
2016-08-22  Pedro Alves  <palves@redhat.com>

	PR gdb/20505
	* linux-tdep.c (linux_vsyscall_range_raw): For core inferiors,
	find the vDSO's start address with AT_SYSINFO_EHDR too, and
	determine the vDSO's size by finding the PT_LOAD segment that
	matches AT_SYSINFO_EHDR.

gdb/testsuite/ChangeLog:
2016-08-22  Pedro Alves  <palves@redhat.com>

	PR gdb/20505
	* gdb.base/vdso-warning.exp: Test core dumps too.  Use
	with_test_prefix.  Factor out bits to ...
	(test_no_vdso): ... this new procedure.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] R_OR1K_GOTOFF_* relocations
@ 2016-08-23 13:28 sergiodj+buildbot
  2016-08-23 13:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eacfca90f1ff457d3a7be9d593040218b6208d2b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: eacfca90f1ff457d3a7be9d593040218b6208d2b

R_OR1K_GOTOFF_* relocations

	PR 20475
	* elf32-or1k.c (or1k_elf_relocate_section): Offset from
	_GLOBAL_OFFSET_TABLE_, not start of .got section.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Add OP parameter to aarch64-tbl.h macros
@ 2016-08-23 14:15 sergiodj+buildbot
  2016-08-23 14:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 14:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d30b0bdab56a563a29984705778168ae93f71ae ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 9d30b0bdab56a563a29984705778168ae93f71ae

[AArch64] Add OP parameter to aarch64-tbl.h macros

Nick recently wrapped most of aarch64-tbl.h entries in macros
like CORE_INSN.  These new macros assumed that the aarch64_op
"op" field of aarch64_opcode is 0 and that the new "verifier"
field is NULL.

However, there are a lot of CORE, SIMD and FP insns whose table
entries need a nonzero aarch64_op field, so these entries
continued to use a braced list instead of a macro.  This makes
the table entries less consistent and means that there are still
quite a few braced entries that need to be updated when making
further changes to the aarch64_opcode structure.

I think the number of entries that need a nonzero aarch64_op
field is high enough to justify having an explicit aarch64_op
entry for all CORE, SIMD and FP entries.  This patch adds
one and updates all existing uses of the macros.  A following
patch makes more use of the macros.

I've followed existing practice by using 0 instead of OP_NIL
for empty aarch64_op fields.  Empty fields are still the norm
and you need to know what the fields are when reading the table
anyway, so it was hard to justify an additional patch to replace
all 0 op fields with OP_NIL.

opcodes/
	* aarch64-tbl.h (CORE_INSN, __FP_INSN, SIMD_INSN): Add OP parameter.
	(aarch64_opcode_table): Update uses accordingly.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Make more use of CORE/FP/SIMD_INSN
@ 2016-08-23 14:27 sergiodj+buildbot
  2016-08-23 15:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ce912d8016857990f894d10e15516c17cf7d653 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 5ce912d8016857990f894d10e15516c17cf7d653

[AArch64] Make more use of CORE/FP/SIMD_INSN

After the previous patch, this one makes all CORE, FP
and SIMD table entries with null "verify" fields use
the associated macros.

opcodes/
	* aarch64-tbl.h (aarch64_opcode_table): Make more use of
	CORE_INSN, __FP_INSN and SIMD_INSN.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix seg-fault in ARM linker when trying to parse a binary file.
@ 2016-08-23 15:22 sergiodj+buildbot
  2016-08-23 16:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6342be709e8749d0a44c02e1876ddca360bfd52f ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6342be709e8749d0a44c02e1876ddca360bfd52f

Fix seg-fault in ARM linker when trying to parse a binary file.

	* elf32-arm.c (elf32_arm_count_additional_relocs): Return zero if
	there is no arm data associated with the section.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix signals-state-child.exp in remote testing
@ 2016-08-23 16:22 sergiodj+buildbot
  2016-08-23 17:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 16:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3589529e3cec4a5a72cd161959055d1e48dcf129 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3589529e3cec4a5a72cd161959055d1e48dcf129

Fix signals-state-child.exp in remote testing

Remote testing isn't considered in signals-state-child.exp, so the it
fails like

shell diff -s /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.base/signals-state-child/standalone.txt /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.base/signals-state-child/gdb.txt^M
diff: /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.base/signals-state-child/standalone.txt: No such file or directory^M
(gdb) FAIL: gdb.base/signals-state-child.exp: signals states are identical

This patch is to fix it.

gdb/testsuite:

2016-08-23  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/signals-state-child.exp: Set variables gdb_txt and
	standalone_txt.  Delete gdb_txt and standalone_txt on host
	and target.  Spawn the binary on target.  Copy files from
	target to host.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbserver_spawn "" rather than gdbserver_spawn ${binfile}
@ 2016-08-23 17:39 sergiodj+buildbot
  2016-08-23 22:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9d9abd7470ea500eb4e82567fff68e87a30efb9 ***

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

gdbserver_spawn "" rather than gdbserver_spawn ${binfile}

Hi,
I happen to see gdbserver is spawned like this in gdb.log,

spawn /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../../gdb/gdbserver/gdbserver --once :2346 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.s
erver/connect-stopped-target/connect-stopped-target /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.server/connect-stopped-target/connect-stopped-t
arget

spawn /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../../gdb/gdbserver/gdbserver --once :2347 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.s
erver/connect-stopped-target/connect-stopped-target /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.server/connect-stopped-target/connect-stopped-t
arget

as we can see, there are two instances of connect-stopped-target or
connect-stopped-target in the command line spawning gdbserver, but
none of these gets parameters from command line.  In these two
tests, gdbserver is spawned via "gdbserver_spawn ${binfile}".  However,
the argument of gdbserver_spawn is the argument passed the child
inferior, not the program itself.

 # Start a gdbserver process running SERVER_EXEC, and connect GDB
 # to it.  CHILD_ARGS are passed to the inferior.
 #
 # Returns the target protocol and socket to connect to.

proc gdbserver_spawn { child_args } {
    set target_exec [gdbserver_download_current_prog]

GDBserver gets the program via last_loaded_file, which is set by
gdb_file_cmd.  In each test, we don't need to pass ${binfile}.

gdb/testsuite:

2016-08-23  Yao Qi  <yao.qi@linaro.org>

	* gdb.server/connect-stopped-target.exp (do_test): Pass "" to
	gdbserver_spawn.
	* gdb.server/connect-without-multi-process.exp (do_test):
	Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Parse NOTE section in core dump files
@ 2016-08-24 18:02 sergiodj+buildbot
  2016-08-24 18:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 18:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47f7f636bc8abc3c41848a412a68ca6aa36dbd21 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: 47f7f636bc8abc3c41848a412a68ca6aa36dbd21

[ARC] Parse NOTE section in core dump files

This patch adds function elf32_arc_grok_parse to parse NOTE section of core
dump files. GDB requires this to work properly with core dumps.

bfd/
2016-08-24  Anton Kolesov  <Anton.Kolesov@synopsys.com>

	* elf32-arc.c (elf32_arc_grok_prstatus): New function.

Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix for gdb.base/pc-fp.exp.
@ 2016-08-24 18:43 sergiodj+buildbot
  2016-08-24 18:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 18:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdd78711b4c1ae26dbc8c2a64f28abec3486ae6c ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: bdd78711b4c1ae26dbc8c2a64f28abec3486ae6c

Fix for gdb.base/pc-fp.exp.

It is my understanding that GDB used to require each architecture to
define a Frame Pointer (fp).  However, this functionality was deprecated
some time ago so the call to setup the fp_reg was changed to deprecated
(set_gdbarch_deprecated_fp_regnum).  It should have been removed from the
Power code.

That said, the code "set_gdbarch_deprecated_fp_regnum
(gdbarch, PPC_R0_REGNUM + 1);" sets up register r1 as the frame pointer.
Register r1 is no longer used to hold the frame pointer on Power.  By
removing the fp definition for Power in GDB, it causes GDB to fall back
to the call get_frame_base_address (frame) which returns the correct value
depending on the specific senario but most of the time is the DWARF
canonical frame address.

gdb/ChangeLog

2016-08-24  Carl Love  <cel@us.ibm.com>

	* rs6000-tdep.c (rs6000_gdbarch_init): Remove call
        set_gdbarch_deprecated_fp_regnum() from initialization function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Allow resetting an empty inferior-tty
@ 2016-08-24 20:24 sergiodj+buildbot
  2016-08-24 21:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-24 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a1ddfa6b67201bb06f51fb47b56096e81bec5c0 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 0a1ddfa6b67201bb06f51fb47b56096e81bec5c0

Allow resetting an empty inferior-tty

This patch allows the user to set the inferior-tty to "empty", in order
to come back to the default behaviour of using the same tty as gdb is
using.

This is already supported in MI (and tested in gdb.mi/mi-basics.exp).

I added a new test, set-inferior-tty.exp, where I test only the setting
and unsetting of the parameter.  It would be nice to actually test that
the inferior output properly goes to the separate tty, but that will be
for another day.

gdb/ChangeLog:

	* infcmd.c (set_inferior_io_terminal): Set inferior terminal to
	NULL if terminal_name is an empty string.
	(_initialize_infcmd): Make the argument of "set inferior-tty"
	optional, mention it in the help doc.

gdb/doc/ChangeLog:

	* gdb.texinfo (Input/Output): Mention possibility to unset
	inferior-tty.

gdb/testsuite/ChangeLog:

	* gdb.base/set-inferior-tty.exp: New file.
	* gdb.base/set-inferior-tty.c: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Test case to detect recursive unwinding in Python-based unwinders.
@ 2016-08-25  7:58 sergiodj+buildbot
  2016-08-25  7:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-25  7:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb1fe4acb8927fc4d451402f3f5fc245144c987e ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: bb1fe4acb8927fc4d451402f3f5fc245144c987e

Test case to detect recursive unwinding in Python-based unwinders.

This test case verifies that GDB will not attempt to invoke a python
unwinder recursively.

At the moment, the behavior exhibited by GDB looks like this:

    (gdb) source py-recurse-unwind.py
    Python script imported
    (gdb) b ccc
    Breakpoint 1 at 0x4004bd: file py-recurse-unwind.c, line 23.
    (gdb) run
    Starting program: py-recurse-unwind
    TestUnwinder: Recursion detected - returning early.
    TestUnwinder: Recursion detected - returning early.
    TestUnwinder: Recursion detected - returning early.
    TestUnwinder: Recursion detected - returning early.

    Breakpoint 1, ccc (arg=<unavailable>) at py-recurse-unwind.c:23
    23      }
    (gdb) bt
    #-1 ccc (arg=<unavailable>) at py-recurse-unwind.c:23
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)

[I've shortened pathnames for easier reading.]

The desired / expected behavior looks like this:

    (gdb) source py-recurse-unwind.py
    Python script imported
    (gdb) b ccc
    Breakpoint 1 at 0x4004bd: file py-recurse-unwind.c, line 23.
    (gdb) run
    Starting program: py-recurse-unwind

    Breakpoint 1, ccc (arg=789) at py-recurse-unwind.c:23
    23      }
    (gdb) bt
    #0  ccc (arg=789) at py-recurse-unwind.c:23
    #1  0x00000000004004d5 in bbb (arg=456) at py-recurse-unwind.c:28
    #2  0x00000000004004ed in aaa (arg=123) at py-recurse-unwind.c:34
    #3  0x00000000004004fe in main () at py-recurse-unwind.c:40

Note that GDB's problems go well beyond the fact that it invokes the
unwinder recursively.  In the process it messes up some internal state
(the frame stash) leading to display of (only) the sentinel frame in
the backtrace.

gdb/testsuite/ChangeLog:

	* gdb.python/py-recurse-unwind.c: New file.
	* gdb.python/py-recurse-unwind.py: New file.
	* gdb.python/py-recurse-unwind.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] X86: Add ptwrite instruction
@ 2016-08-25  8:11 sergiodj+buildbot
  2016-08-25  8:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-25  8:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b40c462310066612636ec7434645ec7b46ff135 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 6b40c462310066612636ec7434645ec7b46ff135

X86: Add ptwrite instruction

Implement ptwrite instruction defined in Intel64 and IA-32 Architectures
Software Developers Manual, June 2016.

gas/

	* config/tc-i386.c (cpu_arch): Add .ptwrite.
	* doc/c-i386.texi: Document ptwrite and .ptwrite.
	* testsuite/gas/i386/i386.exp: Run ptwrite, ptwrite-intel,
	x86-64-ptwrite and x86-64-ptwrite-intel.
	* testsuite/gas/i386/ptwrite-intel.d: New file.
	* testsuite/gas/i386/ptwrite.d: Likewise.
	* testsuite/gas/i386/ptwrite.s: Likewise.
	* testsuite/gas/i386/x86-64-ptwrite-intel.d: Likewise.
	* testsuite/gas/i386/x86-64-ptwrite.d: Likewise.
	* testsuite/gas/i386/x86-64-ptwrite.s: Likewise.

opcodes/

	* i386-dis.c (PREFIX_MOD_0_0FAE_REG_4): New.
	(PREFIX_MOD_3_0FAE_REG_4): Likewise.
	(prefix_table): Add PREFIX_MOD_0_0FAE_REG_4 and
	PREFIX_MOD_3_0FAE_REG_4.
	(mod_table): Use PREFIX_MOD_0_0FAE_REG_4 and
	PREFIX_MOD_3_0FAE_REG_4.
	* i386-gen.c (cpu_flag_init): Add CPU_PTWRITE_FLAGS.
	(cpu_flags): Add CpuPTWRITE.
	* i386-opc.h (CpuPTWRITE): New.
	(i386_cpu_flags): Add cpuptwrite.
	* i386-opc.tbl: Add ptwrite instruction.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Sync proc_service definition with GLIBC
@ 2016-08-25 10:27 sergiodj+buildbot
  2016-08-25 12:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-25 10:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 754653a7c0a43a668a38aa30c4063b9e292a19f9 ***

Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Branch: master
Commit: 754653a7c0a43a668a38aa30c4063b9e292a19f9

Sync proc_service definition with GLIBC

GLIBC BZ#20311 [1] proc_service.h install patch also remove 'const'
attributes from ps_get_thread_area and comment #15 discuss why to remove
the const attribute (basically since it a callback with the struct
ps_prochandle owned by the client it should be able to modify it if
it the case).

On default build this is not the issue and current g++ does not trigger
any issue with this mismatch declaration.  However, on some bootstrap
build configuration where gdbserver is build with gcc instead this
triggers:

error: conflicting types for 'ps_get_thread_area'

This patch fixes it by syncing the declaration with GLIBC.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=20311

gdb/ChangeLog:

2016-08-25  Adhemerval Zanella  <adhemerval.zanella@linaro.org>

	* aarch64-linux-nat.c (ps_get_thread_area): Remove const from
	struct ps_prochandle.
	* amd64-linux-nat.c (ps_get_thread_area): Likewise.
	* arm-linux-nat.c (ps_get_thread_area): Likewise.
	* gdb_proc_service.h (ps_get_thread_area): Likewise.
	* i386-linux-nat.c (ps_get_thread_area): Likewise.
	* m68klinux-nat.c (ps_get_thread_area): Likewise.
	* mips-linux-nat.c (ps_get_thread_area): Likewise.
	* nat/aarch64-linux.c (aarch64_ps_get_thread_area): Likewise.
	* nat/aarch64-linux.h (aarch64_ps_get_thread_area): Likewise.
	* xtensa-linux-nat.c (ps_get_thread_area): Likewise.

gdb/gdbserver/ChangeLog:

2016-08-25  Adhemerval Zanella  <adhemerval.zanella@linaro.org>

	PR server/20491
	* gdb_proc_service.h (ps_get_thread_area): Remove const from struct
	ps_prochandle.
	* linux-aarch64-low.c (ps_get_thread_area): Likewise.
	* linux-arm-low.c (ps_get_thread_area): Likewise.
	* linux-crisv32-low.c (ps_get_thread_area): Likewise.
	* linux-m68k-low.c (ps_get_thread_area): Likewise.
	* linux-mips-low.c (ps_get_thread_area): Likewise.
	* linux-nios2-low.c (ps_get_thread_area): Likewise.
	* linux-tic6x-low.c (ps_get_thread_area): Likewise.
	* linux-x86-low.c (ps_get_thread_area): Likewise.
	* linux-xtensa-low.c (ps_get_thread_area): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] xtensa: Avoid designated inits, for C++ compliance
@ 2016-08-26 10:59 sergiodj+buildbot
  2016-08-26 11:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 10:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae68ff9f280902d9cead28b90979e75dc046492e ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: ae68ff9f280902d9cead28b90979e75dc046492e

xtensa: Avoid designated inits, for C++ compliance

C++ does not officially support designators in initializer lists.  Thus
some compilers may issue errors when encountering them.  Modern versions
of GCC seem to allow them by default, as a GCC extension, even though
the GCC documentation explicitly states otherwise: "[...] This extension
is not implemented in GNU C++."  But some older GCC versions (like
4.4.7) did indeed emit an error instead, like this:

  .../gdb/xtensa-config.c:219: error: expected primary-expression before
			       . token

This patch removes the only such instance I've seen when building with
'--enable-targets=all'.

gdb/ChangeLog:

	* xtensa-tdep.h (XTENSA_GDBARCH_TDEP_INSTANTIATE): Replace
	designated initializer list by plain initializer list, for C++
	compliance.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S390: Indentation fixes in elf32/64-s390.c
@ 2016-08-26 11:41 sergiodj+buildbot
  2016-08-26 12:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ceada89664de30158de12d3d8f7bd7880ff6af29 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: ceada89664de30158de12d3d8f7bd7880ff6af29

S390: Indentation fixes in elf32/64-s390.c

Some indentation fixes in elf32-s390.c and elf64-s390.c.  Whitespace
changes only.

bfd/ChangeLog:

	* elf32-s390.c (allocate_dynrelocs): Fix indentation.
	(elf_s390_finish_ifunc_symbol): Likewise.
	(elf_s390_finish_dynamic_symbol): Likewise.
	(elf_s390_finish_dynamic_sections): Likewise.
	(elf_s390_grok_prstatus): Likewise.
	* elf64-s390.c (elf_s390_hash_table): Fix indentation.
	(elf_s390_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for stable secure gateway veneers addresses
@ 2016-08-26 15:04 sergiodj+buildbot
  2016-08-26 14:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0955507f6e7144c9c5e420bbcf617593b13de38b ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 0955507f6e7144c9c5e420bbcf617593b13de38b

Add support for stable secure gateway veneers addresses

2016-08-26  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* bfd-in.h (bfd_elf32_arm_set_target_relocs): Add a new parameter for
	the input import library bfd.
	* bfd-in2.h: Regenerate.
	* elf32-arm.c (struct elf32_arm_link_hash_table): New in_implib_bfd
	and new_cmse_stub_offset fields.
	(stub_hash_newfunc): Initialize stub_offset and stub_template_size to
	-1.
	(elf32_arm_add_stub): Likewise for stub_offset.
	(arm_new_stubs_start_offset_ptr): New function.
	(arm_build_one_stub): Only allocate a stub_offset if it is -1.  Allow
	empty SG veneers to have zero relocations.
	(arm_size_one_stub): Only initialize stub size and template
	information for non empty veneers.  Do not update veneer section size
	if veneer already has an offset.
	(elf32_arm_create_stub): Return the stub entry pointer or NULL instead
	of a boolean indicating success or failure.
	(cmse_scan): Change stub_changed parameter into an integer pointer
	parameter cmse_stub_created to count the number of stub created and
	adapt to change of return value in elf32_arm_create_stub.
	(cmse_entry_fct_p): New function.
	(arm_list_new_cmse_stub): Likewise.
	(set_cmse_veneer_addr_from_implib): Likewise.
	(elf32_arm_size_stubs): Define cmse_stub_created, pass its address to
	cmse_scan instead of that of cmse_stub_changed to compute the number
	of stub created and use it to initialize stub_changed.  Call
	set_cmse_veneer_addr_from_implib after all cmse_scan.  Adapt to change
	of return value in elf32_arm_create_stub.  Use
	arm_stub_section_start_offset () if not NULL to initialize size of
	secure gateway veneers section.  Initialize stub_offset of Cortex-A8
	erratum fix to -1.  Use ret to hold return value.
	(elf32_arm_build_stubs): Use arm_stub_section_start_offset () if not
	NULL to initialize size of secure gateway veneers section.  Adapt
	comment to stress the importance of zeroing veneer section content.
	(bfd_elf32_arm_set_target_relocs): Add new in_implib_bfd parameter to
	initialize eponymous field in struct elf32_arm_link_hash_table.

ld/
	* emultempl/armelf.em (in_implib_filename): Declare and initialize new
	variable.
	(arm_elf_create_output_section_statements): Open import input library
	file for writing and pass resulting in_implib_bfd to
	bfd_elf32_arm_set_target_relocs.
	(PARSE_AND_LIST_PROLOGUE): Define OPTION_IN_IMPLIB option.
	(PARSE_AND_LIST_LONGOPTS): Define --in-implib option.
	(PARSE_AND_LIST_OPTIONS): Add help message for --in-implib option.
	(PARSE_AND_LIST_ARGS_CASES): Handle new OPTION_IN_IMPLIB case.
	* ld.texinfo (--cmse-implib): Update to mention --in-implib.
	(--in-implib): Document new option.
	* NEWS: Likewise.
	* testsuite/ld-arm/arm-elf.exp
	(Secure gateway import library generation): add --defsym VER=1 to gas
	CLI.
	(Secure gateway import library generation: errors): Likewise.
	(Input secure gateway import library): New test.
	(Input secure gateway import library: no output import library):
	Likewise.
	(Input secure gateway import library: not an SG input import library):
	Likewise.
	(Input secure gateway import library: earlier stub section base):
	Likewise.
	(Input secure gateway import library: later stub section base):
	Likewise.
	(Input secure gateway import library: veneer comeback): Likewise.
	(Input secure gateway import library: entry function change):
	Likewise.
	* testsuite/ld-arm/cmse-implib.s: Add input import library testing.
	* testsuite/ld-arm/cmse-implib.rd: Update accordingly.
	* testsuite/ld-arm/cmse-new-implib.out: New file.
	* testsuite/ld-arm/cmse-new-implib.rd: Likewise.
	* testsuite/ld-arm/cmse-new-implib-no-output.out: Likewise.
	* testsuite/ld-arm/cmse-new-implib-not-sg-in-implib.out: Likewise.
	* testsuite/ld-arm/cmse-new-earlier-later-implib.out: Likewise.
	* testsuite/ld-arm/cmse-new-comeback-implib.rd: Likewise.
	* testsuite/ld-arm/cmse-new-wrong-implib.out: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fixes to legacy ARC relocations.
@ 2016-08-26 15:37 sergiodj+buildbot
  2016-08-26 15:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a87aa054a67e23faeead400bdf902a1eddb242a4 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: a87aa054a67e23faeead400bdf902a1eddb242a4

Fixes to legacy ARC relocations.

Added support for ARC_SDA_12 reloc.
Fixed ARC_N32_ME.
Added ME (middle-endian) to ARC_SDA_12 reloc.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>
	* reloc.c: Fixed type in ARC_SECTOFF relocations. Added ARC_SDA_12
	relocation.
	* bfd-in2.h: Regenerated from the previous changes.
	* libbfd.h: Regenerated from the previous changes.

include/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>
	* elf/arc-reloc.def: Fixed relocation formula for N*, SDA, SDA_12,
	SDA_16_LD*, S13_PCREL, N32_ME, SECTOFF_* relocations.
	* opcode/arc-func.h (replace_disp12s): Added. Used for SDA_12 relocation.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Several fixes related to ARC PIE support.
@ 2016-08-26 15:56 sergiodj+buildbot
  2016-08-26 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 15:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a36df4dcfa3cb89779e1a3eaca8067426e9cad6 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 8a36df4dcfa3cb89779e1a3eaca8067426e9cad6

Several fixes related to ARC PIE support.

Fixed conditions related to dynamic relocs relative offset patching.
Added arc_link_hash_table to be able to always generate and track
.rela.bss section.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* elf-bfd.h: Added ARC_ELF_DATA to enum elf_target_id.
	* elf32-arc.c (struct elf_arc_link_hash_entry): Added.
	(struct elf_arc_link_hash_table): Likewise.
	(elf_arc_link_hash_newfunc): Likewise.
	(elf_arc_link_hash_table_free): Likewise.
	(arc_elf_link_hash_table_create): Likewise.
	(elf_arc_relocate_section): Fixed conditions related to dynamic
	(elf_arc_check_relocs): Likewise.
	(arc_elf_create_dynamic_sections): Added
	(elf_arc_adjust_dynamic_symbol): Changed access to .rela.bss to be done
	through the hash table.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Content for TLS_IE_GOT not written to .got.
@ 2016-08-26 16:13 sergiodj+buildbot
  2016-08-26 16:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dd72ffdfe254fec30fd5eab0c5fd4445df73529 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 4dd72ffdfe254fec30fd5eab0c5fd4445df73529

Content for TLS_IE_GOT not written to .got.

When no dynamic relocation was generated the .got content would not be
updated for the TLS_IE_GOT relocation addresses.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* arc-got.h (relocate_fix_got_relocs_for_got_info): Fixed addresses in
	debug comments. Fixed address in .got related to TLS_IE_GOT dynamic
	relocation.

ld/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* testsuite/ld-arc/tls_ie-01.s: Added to verify associated fix.
	* testsuite/ld-arc/tls_ie-01.d: Likewise


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fixed -init, -fini linker options.
@ 2016-08-26 16:28 sergiodj+buildbot
  2016-08-26 18:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65b94e90977efe3235381708f5a3e0d541026d88 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 65b94e90977efe3235381708f5a3e0d541026d88

Fixed -init, -fini linker options.

ARC was overloading this options by forcing DT_INIT AND DT_FINI
to always point to _init and _fini, respectively.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synospsys.com>

	* elf32-arc.c (elf_arc_finish_dynamic_sections): Changed.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Dynamic TLS GOT entries would not be relocated.
@ 2016-08-26 17:24 sergiodj+buildbot
  2016-08-26 19:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 980aa3e6dfeb0f018915f65be4b2987667f31fe9 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 980aa3e6dfeb0f018915f65be4b2987667f31fe9

Dynamic TLS GOT entries would not be relocated.

Forgot to set should_relocate to TRUE in case of GOT and TLS relocations of
undefined symbols for shared libraries.
In dynamic libraries if symbol is not known the instruction relocation would
not be resolved to point to the respective .got entry.
A test was created to detect similar future mistakes.

bfd/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_relocate_section): Changed. Set should_relocate
	to TRUE for GOT and TLS relocs.

ld/ChangeLog:

Cupertino Miranda  <cmiranda@synopsys.com>

	* ld/testsuite/ld-arc/tls_gd-01.s: Added a testcase for this patch.
	* ld/testsuite/ld-arc/tls_gd-01.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add missing ARMv8-M special registers
@ 2016-08-26 17:28 sergiodj+buildbot
  2016-08-26 22:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a336194b70b712074a3f5479a01cc221003a152 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 1a336194b70b712074a3f5479a01cc221003a152

Add missing ARMv8-M special registers

2016-08-26  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
	* config/tc-arm.c (v7m_psrs): Add MSPLIM, PSPLIM, MSPLIM_NS,
	PSPLIM_NS, PRIMASK_NS, BASEPRI_NS, FAULTMASK_NS, CONTROL_NS, SP_NS and
	their lowecase counterpart special registers.  Write register
	identifier in hex.
	* testsuite/gas/arm/archv8m-cmse-msr.s: Reorganize tests per
	operation, special register and then case.  Use different register for
	each operation.  Add tests for new special registers.
	* testsuite/gas/arm/archv8m-cmse-msr-base.d: Adapt expected result
	accordingly.
	* testsuite/gas/arm/archv8m-cmse-msr-main.d: Likewise.
	* testsuite/gas/arm/archv8m-main-dsp-4.d: Likewise.

opcodes/
	* arm-dis.c (psr_name): Use hex as case labels.  Add detection for
	MSPLIM, PSPLIM, MSPLIM_NS, PSPLIM_NS, PRIMASK_NS, BASEPRI_NS,
	FAULTMASK_NS, CONTROL_NS and SP_NS special registers.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Reduce parameter list in bfd_elf32_arm_target_relocs
@ 2016-08-26 20:45 sergiodj+buildbot
  2016-08-27  5:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68c398921742291719d97f803891b5113874a22b ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 68c398921742291719d97f803891b5113874a22b

Reduce parameter list in bfd_elf32_arm_target_relocs

2016-08-26  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* bfd-in.h (struct elf32_arm_params): Define.
	(bfd_elf32_arm_set_target_relocs): Rename into ...
	(bfd_elf32_arm_set_target_params): This.  Use a struct
	elf32_arm_params to pass all parameters but the bfd and bfd_link_info.
	* bfd-in2.h: Regenerate.
	* elf32-arm.c (bfd_elf32_arm_set_target_relocs): Rename into ...
	(bfd_elf32_arm_set_target_params): This.  Pass all values via a struct
	elf32_arm_params rather than as individual parameters.

ld/
	* emultempl/armelf.em (params): New static variable.
	(thumb_entry_symbol, byteswap_code, target1_is_rel, target2_type,
	fix_v4bx, use_blx, vfp11_denorm_fix, stm32l4xx_fix, fix_cortex_a8,
	no_enum_size_warning, no_wchar_size_warning, pic_veneer,
	merge_exidx_entries, fix_arm1176, cmse_implib): move as part of the
	above new structure.
	(arm_elf_before_allocation): Access static variable from the params
	structure.
	(gld${EMULATION_NAME}_finish): Likewise.
	(arm_elf_create_output_section_statements): Likewise and pass the
	address of that structure to bfd_elf32_arm_set_target_relocs instead
	of the static variables.
	(PARSE_AND_LIST_ARGS_CASES): Access static variable from the params
	structure.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes, gas: fix mnemonic of sparc camellia_fl
@ 2016-08-27  0:57 sergiodj+buildbot
  2016-08-27  6:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-27  0:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b8b65328f8825444a7370a7817f2802b0e1a7c9 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 1b8b65328f8825444a7370a7817f2802b0e1a7c9

opcodes, gas: fix mnemonic of sparc camellia_fl

This patch fixes a typo in the mnemonic of the camellia_fl
instruction, which was implemented before as camellia_fi.

gas/ChangeLog:

2016-08-26  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* testsuite/gas/sparc/crypto.d: Rename invalid opcode camellia_fi
	to camellia_fl.
	* testsuite/gas/sparc/crypto.s: Likewise.

opcodes/ChangeLog:

2016-08-26  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* sparc-opc.c (sparc_opcodes): Fix typo in opcode, camellia_fi ->
	camellia_fl.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] 2016-08-26 Thomas Preud'homme <thomas.preudhomme@arm.com>
@ 2016-08-27  2:17 sergiodj+buildbot
  2016-08-27  2:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-27  2:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2abbbebcccf6c9403f8d6327e3fe3655acffbc1 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: c2abbbebcccf6c9403f8d6327e3fe3655acffbc1

2016-08-26  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (elf32_arm_get_stub_entry): Assert that we don't access
	passed the end of htab->stub_group array.
	(elf32_arm_create_or_find_stub_sec): Likewise.
	(elf32_arm_create_stub): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix commit 980aa3e6
@ 2016-08-27 12:09 sergiodj+buildbot
  2016-08-27 12:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-27 12:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a9e8e72fe88095043d16f8a56b5a1e150ee288b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8a9e8e72fe88095043d16f8a56b5a1e150ee288b

Fix commit 980aa3e6

Commit 980aa3e6 was supposed to cure dyn_reloc counting problems, but
did the opposite.  For PIC we count two types of dyn_reloc, those on
pc-relative relocs, and the total.  If a sym needs pc-relative dyn
relocs then all the relocs are dynamic.  If not, then only those that
are must_be_dyn_reloc are dynamic.

	PR 20519
	* elf64-ppc.c (pc_dynrelocs): New function.
	(ppc64_elf_relocate_section): Use it and must_be_dyn_reloc to
	handle pic dynamic relocs.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Lack of SHF_GROUP sections result in ld segfault
@ 2016-08-27 13:37 sergiodj+buildbot
  2016-08-29 13:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-27 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53720c495c7c25f9b0f4bfce3269c6c8a7696522 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 53720c495c7c25f9b0f4bfce3269c6c8a7696522

Lack of SHF_GROUP sections result in ld segfault

	PR 20520
	* elf.c (_bfd_elf_setup_sections): Check that SHT_GROUP sections
	have corresponding SHF_GROUP sections.
	(bfd_elf_set_group_contents): Comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb.base/default.exp regression
@ 2016-08-30  6:44 sergiodj+buildbot
  2016-08-30 11:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-30  6:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fac69100a7c1fb52b2e044294a858272bad4e46 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 7fac69100a7c1fb52b2e044294a858272bad4e46

gdb.base/default.exp regression

tty^M
(gdb) FAIL: gdb.base/default.exp: tty

gdb/testsuite/ChangeLog
2016-08-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.base/default.exp (tty): Remove.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] i386: Issue an error on non-PIC call to IFUNC in PIC object
@ 2016-08-30 16:56 sergiodj+buildbot
  2016-08-30 17:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-30 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74437ea28fb611d4c88077b486fd7c0a8b4c2a25 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 74437ea28fb611d4c88077b486fd7c0a8b4c2a25

i386: Issue an error on non-PIC call to IFUNC in PIC object

On i386, IFUNC function must be called via PLT.  Since PLT in PIC
object uses EBX register, R_386_PLT32 relocation must be used to
call IFUNC function even when IFUNC function is defined locally.
Linker should issue an error when R_386_PC32 relocation is used
to call IFUNC function.

Since PR ld/19784 tests doesn't use PLT relocation to local IFUNC
function, they are moved to the x86-64 test directory.

bfd/

	PR ld/14961
	PR ld/20515
	* elf32-i386.c (elf_i386_check_relocs): Issue an error when
	R_386_PC32 relocation is used to call IFUNC function in PIC
	object.

ld/

	PR ld/14961
	PR ld/20515
	* testsuite/ld-i386/i386.exp: Run pr20515.
	* testsuite/ld-i386/pr20515.d: New file.
	* testsuite/ld-i386/pr20515.s: Likewise.
	* testsuite/ld-ifunc/ifunc-14a.s: Use R_386_PLT32 to call IFUNC
	function.
	* testsuite/ld-ifunc/ifunc-14c.s: Likewise.
	* testsuite/ld-ifunc/ifunc-2-i386.s: Likewise.
	* testsuite/ld-ifunc/ifunc-2-local-i386.s: Likewise.
	* testsuite/ld-ifunc/ifunc.exp: Move PR ld/19784 tests to ...
	* testsuite/ld-x86-64/x86-64.exp: Here.
	* testsuite/ld-ifunc/pr19784a.c: Moved to ...
	* testsuite/ld-x86-64/pr19784a.c: Here.
	* testsuite/ld-ifunc/pr19784b.c: Moved to ...
	* testsuite/ld-x86-64/pr19784b.c: Here.
	* testsuite/ld-ifunc/pr19784c.c: Moved to ...
	* testsuite/ld-x86-64/pr19784c.c: Here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ppc apuinfo for spe parsed incorrectly
@ 2016-08-30 18:41 sergiodj+buildbot
  2016-08-30 18:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-30 18:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8941017bc0226b60ce306d5271df15820ce66a53 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8941017bc0226b60ce306d5271df15820ce66a53

ppc apuinfo for spe parsed incorrectly

apuinfo saying SPE resulted in mach = bfd_mach_ppc_vle due to a
missing break.

	PR 20531
	* elf32-ppc.c (_bfd_elf_ppc_set_arch): Add missing "break".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix order of inferiors in "thread apply all"
@ 2016-08-31  4:17 sergiodj+buildbot
  2016-08-31  4:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-31  4:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5af962df4dda65216b83d0a954ea355296517f4b ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 5af962df4dda65216b83d0a954ea355296517f4b

Fix order of inferiors in "thread apply all"

This inserts missing parentheses in the calculation of the comparison
result between two different inferior numbers.  The problem was found by
Philipp Rudo.

gdb/ChangeLog:

	* thread.c (tp_array_compar): Insert missing parentheses.

gdb/testsuite/ChangeLog:

	* gdb.multi/tids.exp: Test "thread apply all".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fixed issue with NULL pointer access on header var.
@ 2016-08-31  5:42 sergiodj+buildbot
  2016-08-31  7:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-31  5:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7763838e991e4d17a24c4214db5144eefd515543 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 7763838e991e4d17a24c4214db5144eefd515543

Fixed issue with NULL pointer access on header var.

Variable "header" in function is set conditionally, but was accessed without
verifying if pointer was NULL.

opcodes/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
	* opcodes/arc-dis.c (print_insn_arc): Changed.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PowerPC VLE sh_flags and p_flags
@ 2016-08-31 18:21 sergiodj+buildbot
  2016-08-31 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-31 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7d69005fb97f0d90c9eb414944a5035bfd67b36 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: f7d69005fb97f0d90c9eb414944a5035bfd67b36

PowerPC VLE sh_flags and p_flags

ELF section sh_flags SHF_PPC_VLE was being set based on arch/mach,
which meant all code sections in an object file has the flag or all
lacked it.  We can do better than that.  Only those code sections
where VLE is enabled ought to have the flag, allowing an object file
to contain both VLE and non-VLE code.

Also, ELF header p_flags PF_PPC_VLE wasn't being set, and segments
were being split unnecessarily.

bfd/
	* elf32-ppc.c (ppc_elf_section_processing): Delete.
	(elf_backend_section_processing): Don't define.
	(ppc_elf_modify_segment_map): Set p_flags and mark valid.  Don't
	split on non-exec sections differing in SHF_PPC_VLE.  When
	splitting segments, mark size invalid.
gas/
	* config/tc-ppc.c (md_assemble): Set sh_flags for VLE.  Test
	ppc_cpu rather than calling ppc_mach to determine VLE mode.
	(ppc_frag_check, ppc_handle_align): Likewise use ppc_cpu.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix a typo in comment
@ 2016-08-31 20:01 sergiodj+buildbot
  2016-08-31 20:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-08-31 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f99bd5f2c1e6b545a0a6cfb3b13f79deea84098e ***

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

Fix a typo in comment

This patch replaces "keep things single" with "keep things simple".

gdb:

2016-08-31  Yao Qi  <yao.qi@linaro.org>

	* record-full.c (record_full_insert_breakpoint): Fix typo.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix lwp_suspend/unsuspend imbalance in linux_wait_1
@ 2016-09-01  7:16 sergiodj+buildbot
  2016-09-01  7:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-01  7:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3aa5cfa0d1cdbbd839884302535da28ca8c8b00d ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 3aa5cfa0d1cdbbd839884302535da28ca8c8b00d

Fix lwp_suspend/unsuspend imbalance in linux_wait_1

This patch fixes imbalanced lwp_suspend/unsuspend calls caused by the
premature choosing of another event for fairness.

select_event_lwp would switch the event before a call to
unsuspend_all_lwps, thus it would be called with the wrong event.

This caused an assertion failure: unsuspend LWP xx, suspended=-1 when
testing  gdb.threads/non-stop-fair-events.exp with ARM range stepping in
GDBServer.

This patch moves the switch of event after the unsuspend/unstop calls.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-native.

gdb/gdbserver/ChangeLog:

	* linux-low.c (linux_wait_1): Move event switch after unsuspend_lwps.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't treat .opd section specially when ELFv2
@ 2016-09-01 20:40 sergiodj+buildbot
  2016-09-01 20:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-01 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd285db582fb1bd59db01e3dc29511d08999d05b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: cd285db582fb1bd59db01e3dc29511d08999d05b

Don't treat .opd section specially when ELFv2

Fixes a gdb segfault if a section named .opd is found in ELFv2 binaries.

	* elf64-ppc.c (synthetic_opd): New static var.
	(compare_symbols): Don't treat symbols in .opd specially for ELFv2.
	(ppc64_elf_get_synthetic_symtab): Likewise.  Comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] 2016-09-01 Thomas Preud'homme <thomas.preudhomme@arm.com>
@ 2016-09-01 21:43 sergiodj+buildbot
  2016-09-01 23:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-01 21:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 424844864aa6f49c616b3bb74a0a5ba9bcb92e72 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 424844864aa6f49c616b3bb74a0a5ba9bcb92e72

2016-09-01  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (cmse_entry_fct_p): Store instruction encoding in an
	array of bytes and use bfd_get_16 to interpret its encoding according
	to endianness of target.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume
@ 2016-09-02  9:02 sergiodj+buildbot
  2016-09-02  9:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-02  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 049a857091cff98371b5688140832a3cf767153c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 049a857091cff98371b5688140832a3cf767153c

Use target_continue{,_no_signal} instead of target_resume

This commit implements a new function, target_continue, on top of the
target_resume function.  Then, it replaces all calls to target_resume
by calls to target_continue or to the already existing
target_continue_no_signal.

This is one of the (many) necessary steps needed to consolidate the
target interface between GDB and gdbserver.  In particular, I am
interested in the impact this change will have on the unification of
the fork_inferior function (which I have been working on).

Tested on the BuildBot, no regressions introduced.

gdb/gdbserver/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (start_inferior): New variable 'ptid'.  Replace calls
	to the_target->resume by target_continue{,_no_signal}, depending
	on the case.
	* target.c (target_stop_and_wait): Call target_continue_no_signal
	instead of the_target->resume.
	(target_continue): New function.

gdb/ChangeLog:
2016-09-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* fork-child.c (startup_inferior): Replace calls to target_resume
	by target_continue{,_no_signal}, depending on the case.
	* linux-nat.c (cleanup_target_stop): Call
	target_continue_no_signal instead of target_resume.
	* procfs.c (procfs_wait): Likewise.
	* target.c (target_continue): New function.
	* target/target.h (target_continue): New prototype.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Share target_wait prototype between GDB and gdbserver
@ 2016-09-02 14:53 sergiodj+buildbot
  2016-09-02 16:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-02 14:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2b9e3dfd4bc3c5149496fdbeaa5f0907220685f ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: f2b9e3dfd4bc3c5149496fdbeaa5f0907220685f

Share target_wait prototype between GDB and gdbserver

This commit moves the target_wait prototype from the GDB-specific
target.h header to the common target/target.h header.  Then, it
creates a compatible implementation of target_wait on gdbserver using
the_target->wait, and adjusts the (only) caller (mywait function).

Pretty straightforward, no regressions introduced.

gdb/gdbserver/ChangeLog:
2016-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* target.c (mywait): Call target_wait instead of
	the_target->wait.
	(target_wait): New function.

gdb/ChangeLog:
2016-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* target.c (target_wait): Mention that the function's prototype
	can be found at target/target.h.
	* target.h (target_wait): Move prototype from here...
	* target/target.h (target_wait): ... to here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Detect broken ptrace in gdb_skip_float_test
@ 2016-09-02 17:12 sergiodj+buildbot
  2016-09-02 18:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-02 17:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27aba0477a4818fd760accd5b29a210d0ade2f42 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 27aba0477a4818fd760accd5b29a210d0ade2f42

Detect broken ptrace in gdb_skip_float_test

We recently found a ARM kernel ptrace bug
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-May/431962.html
Details can be found in the comment in gdb_skip_float_test.  We can
skip floating point tests if the kernel bug is detected.

This patch adds more code in gdb_skip_float_test to detect the broken
ptrace on arm-linux.  Such detection should be done at the beginning
of the test, because it starts a fresh GDB, so change the test cases
to invoke gdb_skip_float_test at the beginning of test, and use its
return value afterwards.

Since gdb_skip_float_test becomes a gdb_caching_proc, so it can't
have an argument, this patch also removes argument "msg", which isn't
useful.

gdb/testsuite:

2016-09-02  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/arm-neon.exp: Skip it if gdb_skip_float_test returns
	true.
	* gdb.base/call-ar-st.exp: Invoke gdb_skip_float_test.
	* gdb.base/call-rt-st.exp: Likewise.
	* gdb.base/call-sc.exp: Invoke gdb_skip_float_test and use its
	return value instead of gdb,skip_float_test.
	* gdb.base/callfuncs.exp: Invoke gdb_skip_float_test.
	(do_function_calls): Use its return value instead of
	gdb,skip_float_test.
	* gdb.base/finish.exp: Likewise.
	* gdb.base/funcargs.exp: Likewise.
	* gdb.base/return.exp: Likewise.
	* gdb.base/return2.exp: Likewise.
	* gdb.base/varargs.exp: Likewise.
	* lib/gdb.exp (gdb_skip_float_test): Change it to
	gdb_caching_proc.  Detect the broken ptrace on arm-linux.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip floating point tests in return-nodebug.exp if gdb_skip_float_test is true
@ 2016-09-02 19:40 sergiodj+buildbot
  2016-09-02 19:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-02 19:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae9cf263fdd47c30b997fcf4627609df77ca64c1 ***

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

Skip floating point tests in return-nodebug.exp if gdb_skip_float_test is true

return-nodebug.exp does the test for various types, but we shouldn't
test with floating point type if gdb_skip_float_test returns true.

gdb/testsuite:

2016-09-02  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/return-nodebug.exp: Skip the test if	skip_float_test
	is true and $type is "float" or "double".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [GDBserver] Replace "reinsert_breakpoint" with "single_step_breakpoint"
@ 2016-09-02 22:03 sergiodj+buildbot
  2016-09-03 11:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-02 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b9a79ef767f0e7f8c5fecd7eea920f20084d3d4 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3b9a79ef767f0e7f8c5fecd7eea920f20084d3d4

[GDBserver] Replace "reinsert_breakpoint" with "single_step_breakpoint"

reinsert_breakpoint is used for software single step, so it is more
clear to rename it to single_step_breakpoint.  This was pointed out in
the review https://sourceware.org/ml/gdb-patches/2016-05/msg00429.html
I don't rename "other_breakpoint" in this patch.

gdb/gdbserver:

2016-09-02  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c: Replace "reinsert_breakpoints" with
	"single_step_breakpoints".  Replace "reinsert breakpoints"
	with "single-step breakpoints".
	* mem-break.c: Likewise.
	* mem-break.h: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Handle DW_OP_form_tls_address
@ 2016-09-03 12:46 sergiodj+buildbot
  2016-09-03 19:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-03 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4aa4e28bdcf5f0d733def62b542fea11d5f219d5 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4aa4e28bdcf5f0d733def62b542fea11d5f219d5

Handle DW_OP_form_tls_address

Currently gdb supports DW_OP_GNU_push_tls_address, but not
DW_OP_form_tls_address.  I think it would be better if the toolchain
as a whole moved to using the standard opcode, and the prerequisite to
this is getting gdb to recognize it.

GCC can sometimes emit DW_OP_form_tls_address for emultls targets.  As
far as I know, nobody has ever tried this with gdb (since it wouldn't
work at all).

I don't think there's a major drawback to using a single opcode for
all targets, because computing the location of a thread-local is
already target specific.

This is PR gdb/11616.

I don't know how to write a test case for this; though it's worth
noting that there aren't explicit tests for DW_OP_GNU_push_tls_address
either -- and if I change GCC, these paths will be tested to the same
extent they are now.

2016-09-02  Tom Tromey  <tom@tromey.com>

	PR gdb/11616:
	* dwarf2read.c (decode_locdesc): Handle DW_OP_form_tls_address.
	* dwarf2loc.c (dwarf2_compile_expr_to_ax): Handle
	DW_OP_form_tls_address.
	(locexpr_describe_location_piece): Likewise.
	* dwarf2expr.h (struct dwarf_expr_context_funcs): Update comment.
	* dwarf2expr.c (execute_stack_op): Handle DW_OP_form_tls_address.
	(ctx_no_get_tls_address): Mention DW_OP_form_tls_address.
	* compile/compile-loc2c.c (struct insn_info): Update comment.
	(compute_stack_depth_worker): Handle DW_OP_form_tls_address.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Removed redundant line remote-utils.c
@ 2016-09-05 19:41 sergiodj+buildbot
  2016-09-05 20:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-05 19:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1da6748f560ec19173d5d7766e0d497e8a0f1e4 ***

Author: Akash Trehan <akash.trehan123@gmail.com>
Branch: master
Commit: c1da6748f560ec19173d5d7766e0d497e8a0f1e4

Removed redundant line remote-utils.c

2016-09-02  Akash Trehan  <akash.trehan123@gmail.com>

gdb/gdbserver/ChangeLog:
    PR gdb/19495
    * remote-utils.c (relocate_instruction): Remove redundant strcpy()
    call writing data to own_buf.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR19927: Avoid unwinder recursion if sniffer uses calls parse_and_eval
@ 2016-09-06  8:12 sergiodj+buildbot
  2016-09-06  8:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06  8:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f245535cf583ae4ca13b10d47b3c7d3334593ece ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f245535cf583ae4ca13b10d47b3c7d3334593ece

Fix PR19927: Avoid unwinder recursion if sniffer uses calls parse_and_eval

This fixes the problem exercised by Kevin's test at:

 https://sourceware.org/ml/gdb-patches/2016-08/msg00216.html

This was originally exposed by the OpenJDK Python-based unwinder.

If an unwinder attempts to call parse_and_eval from within its
sniffing method, GDB's unwinding machinery enters infinite recursion.
However, parse_and_eval is a pretty reasonable thing to call, because
Python/Scheme-based unwinders will often need to read globals out of
inferior memory.  The recursion happens because:

- get_current_frame() is called soon after the target stops.

- current_frame is NULL, and so we unwind it from the sentinel frame
  (which is special and has level == -1).

- We reach get_prev_frame_if_no_cycle, which does cycle detection
  based on frame id, and thus tries to compute the frame id of the new
  frame.

- Frame id computation requires an unwinder, so we go through all
  unwinder sniffers trying to see if one accepts the new frame (the
  current frame).

- the unwinder's sniffer calls parse_and_eval().

- parse_and_eval depends on the selected frame/block, and if not set
  yet, the selected frame is set to the current frame.

- get_current_frame () is called again.  current_frame is still NULL,
  so ...

- recurse forever.


In Kevin's test at:

 https://sourceware.org/ml/gdb-patches/2016-08/msg00216.html

gdb doesn't recurse forever simply because the Python unwinder
contains code to detect and stop the recursion itself.  However, GDB
goes downhill from here, e.g., by showing the sentinel frame as
current frame (note the -1):

    Breakpoint 1, ccc (arg=<unavailable>) at py-recurse-unwind.c:23
    23      }
    (gdb) bt
    #-1 ccc (arg=<unavailable>) at py-recurse-unwind.c:23
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)

That "-1" frame level comes from this:

      if (catch_exceptions (current_uiout, unwind_to_current_frame,
			    sentinel_frame, RETURN_MASK_ERROR) != 0)
	{
	  /* Oops! Fake a current frame?  Is this useful?  It has a PC
             of zero, for instance.  */
	  current_frame = sentinel_frame;
	}

which is bogus.  It's never correct to set the current frame to the
sentinel frame.  The only reason this has survived so long is that
getting here normally indicates something wrong has already happened
before and we fix that.  And this case is no exception -- it doesn't
really matter how precisely we managed to get to that bogus code (it
has to do with the the stash), because anything after recursion
happens is going to be invalid.

So the fix is to avoid the recursion in the first place.

Observations:

 #1 - The recursion happens because we try to do cycle detection from
      within get_prev_frame_if_no_cycle.  That requires computing the
      frame id of the frame being unwound, and that itself requires
      calling into the unwinders.

 #2 - But, the first time we're unwinding from the sentinel frame,
      when we reach get_prev_frame_if_no_cycle, there's no frame chain
      at all yet:

      - current_frame is NULL.
      - the frame stash is empty.

Thus, there's really no need to do cycle detection the first time we
reach get_prev_frame_if_no_cycle, when building the current frame.

So we can break the recursion by making get_current_frame call a
simplified version of get_prev_frame_if_no_cycle that results in
setting the current_frame global _before_ computing the current
frame's id.

But, we can go a little bit further.  As there's really no reason
anymore to compute the current frame's frame id immediately, we can
defer computing it to when some caller of get_current_frame might need
it.  This was actually how the frame id was computed for all frames
before the stash-based cycle detection was added.  So in a way, this
patch reintroduces the lazy frame id computation, but unlike before,
only for the case of the current frame, which turns out to be special.

This lazyness, however, requires adjusting
gdb.python/py-unwind-maint.exp, because that assumes unwinders are
immediately called as side effect of some commands.  I didn't see a
need to preserve the behavior expected by that test (all it would take
is call get_frame_id inside get_current_frame), so I adjusted the
test.

gdb/ChangeLog:
2016-09-05  Pedro Alves  <palves@redhat.com>

	PR backtrace/19927
	* frame.c (get_frame_id): Compute the frame id if not computed
	yet.
	(unwind_to_current_frame): Delete.
	(get_current_frame): Use get_prev_frame_always_1 to get the
	current frame and assert that that always succeeds.
	(get_prev_frame_if_no_cycle): Skip cycle detection if returning
	the current frame.

gdb/testsuite/ChangeLog:
2016-09-05  Pedro Alves  <palves@redhat.com>

	PR backtrace/19927
	* gdb.python/py-unwind-maint.exp: Adjust tests to not expect that
	unwinders are immediately called as side effect of "source" or
	"disable unwinder" commands.
	* gdb.python/py-recurse-unwind.exp: Remove setup_kfail calls.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/: Require a C++ compiler
@ 2016-09-06 16:28 sergiodj+buildbot
  2016-09-06 17:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf6de44d75082116865a85cbf94db2632b679361 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: cf6de44d75082116865a85cbf94db2632b679361

gdb/: Require a C++ compiler

This removes all support for building gdb & gdbserver with a C
compiler from gdb & gdbserver's build machinery.

gdb/ChangeLog:
2016-09-05  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that a C++ compiler is now required.
	* Makefile.in (COMPILER, COMPILER_CFLAGS): Remove.
	(COMPILE.pre, CC_LD): Use CXX directly.
	(INTERNAL_CFLAGS_BASE): Use CXXFLAGS directly.
	* acinclude.m4: Don't include build-with-cxx.m4.
	* build-with-cxx.m4: Delete file.
	* configure.ac: Remove GDB_AC_BUILD_WITH_CXX call.
	* warning.m4: Assume $enable_build_with_cxx is yes.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:
2016-09-05  Pedro Alves  <palves@redhat.com>

	* Makefile.in (COMPILER, COMPILER_CFLAGS): Remove.
	(COMPILE.pre, CC_LD): Use CXX directly.
	(INTERNAL_CFLAGS_BASE): Use CXXFLAGS directly.
	* acinclude.m4: Don't include build-with-cxx.m4.
	* configure.ac: Remove GDB_AC_BUILD_WITH_CXX call.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix typo in ada_language_arch_info
@ 2016-09-06 18:54 sergiodj+buildbot
  2016-09-06 19:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 18:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f3bceb68dd211be977eb61d5f1ea68e7de51b7a ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 5f3bceb68dd211be977eb61d5f1ea68e7de51b7a

Fix typo in ada_language_arch_info

This fixes a bug introduced by a wrong replacement here:
https://sourceware.org/ml/gdb-patches/2007-06/msg00196.html

The Ada "long_long_float" type is supposed to correspond to the
platform ABI long double type, not double.

gdb/ChangeLog:

	* ada-lang.c (ada_language_arch_info): Use gdbarch_long_double_bit
	instead of gdbarch_double_bit for "long_long_float".

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix TYPE_SPECIFIC_FIELD for types created via arch_type
@ 2016-09-06 19:59 sergiodj+buildbot
  2016-09-06 20:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae438bc5c06b770c00f37e4ed244707ce3ab9ff4 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: ae438bc5c06b770c00f37e4ed244707ce3ab9ff4

Fix TYPE_SPECIFIC_FIELD for types created via arch_type

A type's TYPE_SPECIFIC_FIELD is supposed to be initialized as appropriate
for the type code.  This does happen if the type is created via init_type,
but not if it created via arch_type.

Fixed by extracting the initialization logic into a new set_type_code
routine, which is then called from both places.

gdb/ChangeLog:

	* gdbtypes.c (set_type_code): New function.
	(init_type, arch_type): Use it.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add some missing arch_..._type helpers
@ 2016-09-06 20:46 sergiodj+buildbot
  2016-09-06 22:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88dfca6c43c11dea69db24cfb87e6821e63e29b2 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 88dfca6c43c11dea69db24cfb87e6821e63e29b2

Add some missing arch_..._type helpers

gdbtypes provides a number of helper routines that can be called instead of
using arch_type directly to create a type of a particular kind.  This patch
adds two additional such routines that have been missing so far, to allow
creation of TYPE_CODE_DECFLOAT and TYPE_CODE_POINTER types.

The patch also changes a number of places to use the new helper routines
instead of calling arch_type directly.  No functional change intended.

gdb/ChangeLog:

	* gdbtypes.h (arch_decfloat_type): New prototype.
	(arch_pointer_type): Likewise.
	* gdbtypes.c (arch_decfloat_type): New function.
	(arch_pointer_type): Likewise.
	(gdbtypes_post_init): Use arch_decfloat_type.
	* avr-tdep.c (avr_gdbarch_init): Use arch_pointer_type.
	* ft32-tdep.c (ft32_gdbarch_init): Likewise.
	* m32c-tdep.c (make_types): Likewise.
	* rl78-tdep.c (rl78_gdbarch_init): Likewise.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove obsolete TYPE_FLAG_... values
@ 2016-09-06 22:01 sergiodj+buildbot
  2016-09-07  0:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9ff5f12cff6cd06f74ecf387ac5468984c94c6f ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: a9ff5f12cff6cd06f74ecf387ac5468984c94c6f

Remove obsolete TYPE_FLAG_... values

Now that init_type no longer takes a FLAGS argument, there is no user of
the TYPE_FLAGS_... enum values left.  This commit removes them (and all
references to them in comments as well).

This is mostly a no-op, except for a change to the Python type printer,
which attempted to use them before.  (As best as I can tell, this wasn't
really needed anyway, since it was only used to pretty-print type
*instance* flags, which only use the instance flags.)

gdb/ChangeLog:

	* gdbtypes.h (enum type_flag_value): Remove.
	Remove references to TYPE_FLAG_... in comments throughout.
	* gdbtypes.c (recursive_dump_type): Do not print TYPE_FLAG_...
	flags, print the corresponding TYPE_... access macro names.
	Remove references to TYPE_FLAG_... in comments throughout.
	* infcall.c: Remove references to TYPE_FLAG_... in comments.
	* valprint.c: Likewise.
	* gdb-gdb.py (class TypeFlag): No longer consider TYPE_FLAG_...
	values, only TYPE_INSTANCE_FLAG_... values.
	(class TypeFlagsPrinter): Likewise.

gdb/testsuite/ChangeLog:

	* gdb.cp/hang.exp: Remove reference to TYPE_FLAG_STUB in comment.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove TYPE_NOSIGN "char" hack
@ 2016-09-06 23:33 sergiodj+buildbot
  2016-09-07  1:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 23:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c413c44801e449f1f0b9828b81770e752b8219af ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: c413c44801e449f1f0b9828b81770e752b8219af

Remove TYPE_NOSIGN "char" hack

init_type (and arch_integer_type) currently use a special hack to set the
TYPE_NOSIGN flag if the type name is exactly "char".  This commit moves the
hack up to the callers of those routines.

The special case currently can hit only for types created from dwarf2read,
but read_base_type actually implements the "char" check itself, so it is
redundant to do it in init_type as well.  (Note that stabsread.c and the
other type readers always pass NULL as name to init_type, so the special
case can never hit for those.)

A few other cases create pre-definded types with a hard-coded name of "char";
the commit simply moves setting the TYPE_NOSIGN flag to those places.

No functional change intended.

gdb/ChangeLog:

	* gdbtypes.c (init_type): Remove "char" special case.
	(arch_integer_type): Likewise.
	(gdbtypes_post_init): Set TYPE_NOSIGN for "char" type.
	(objfile_type): Likewise.
	* mdebugread.c (basic_type): Likewise.
	* stabsread.c (rs6000_builtin_type): Likewise.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add missing format for built-in floating-point types
@ 2016-09-06 23:37 sergiodj+buildbot
  2016-09-07  6:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6

Add missing format for built-in floating-point types

Many callers of init_float_type and arch_float_type still pass a NULL
floatformat.  This commit changes those callers where the floatformat
that is supposed to be use is obvious.  There are two categories where
this is the case:

- A number of built-in types are intended to match the platform ABI
  floating-point types (i.e. types that use gdbarch_float_bit etc.).
  Those places should use the platform ABI floating-point formats
  defined via gdbarch_float_format etc.

- A number of language built-in types should simply use IEEE floating-
  point formats, since the language actually defines that this is the
  format that must be used to implement floating-point types for this
  language.  (This affects Java, Go, and Rust.)  The same applies for
  to the predefined "RS/6000" stabs floating-point built-in types.

gdb/ChangeLog:

	* ada-lang.c (ada_language_arch_info): Use gdbarch-provided
	platform ABI floating-point formats for built-in types.
	* d-lang.c (build_d_types): Likewise.
	* f-lang.c (build_fortran_types): Likewise.
	* m2-lang.c (build_m2_types): Likewise.
	* mdebugread.c (basic_type): Likewise.

	* go-lang.c (build_go_types): Use IEEE floating-point formats
	for language built-in types as mandanted by the language.
	* jv-lang.c (build_java_types): Likewise.
	* rust-lang.c (rust_language_arch_info): Likewise.
	* stabsread.c (rs6000_builtin_type): Likewise.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support 128-bit IEEE floating-point types on Intel and Power
@ 2016-09-07  0:39 sergiodj+buildbot
  2016-09-07 10:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00d5215ecec4fa0a78dcc37fec9425593753eb66 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 00d5215ecec4fa0a78dcc37fec9425593753eb66

Support 128-bit IEEE floating-point types on Intel and Power

Now that all the prerequisites are in place, this commit finally adds support
for handling the __float128 type on Intel and Power, by providing appropriate
platform-specific versions of the floatformat_for_type callback.

Since at this point we do not yet have any indication in the debug info to
distinguish different floating-point formats of the same length, we simply
use the type name as hint.  Types named "__float128" get the IEEE format.
In addition to handling "__float128" itself, we also recognize "_Float128"
and (on Power) "_Float64x", as well as the complex versions of those.
(As pointed out by Joseph Myers, starting with GCC 7, __float128 is just
a typedef for _Float128 -- but it's good to handle this anyway.)

A new test case does some simple verification that the format is decoded
correctly, using both __float128 and "long double" to make sure using both
in the same file still works.  Another new test verifies handling of the
_FloatN and _FloatNx types supported by GCC 7, as well as the complex
versions of those types.

Note that this still only supports basic format decoding and encoding.
We do not yet support the GNU extension 'g' suffix for __float128 constants.
In addition, since all *arithmetic* on floating-point values is still
performed in native host "long double" arithmetic, if that format is not
able to encode all target __float128 values, we may get incorrect results.
(To fix this would require implementing fully synthetic target floating-
point arithmetic along the lines of GCC's real.c, presumably using MPFR.)

gdb/ChangeLog:

	* i386-tdep.c (i386_floatformat_for_type): New function.
	(i386_gdbarch_init): Install it.
	* ppc-linux-tdep.c (ppc_floatformat_for_type): New function.
	(ppc_linux_init_abi): Install it.

gdb/testsuite/ChangeLog:

	* gdb.base/float128.c: New file.
	* gdb.base/float128.exp: Likewise.
	* gdb.base/floatn.c: Likewise.
	* gdb.base/floatn.exp: Likewise.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Resolve size relocation with copy relocation
@ 2016-09-07  1:30 sergiodj+buildbot
  2016-09-07 13:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  1:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8457a04b71cbd642a00352dce0539fe1fe22dd4 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: d8457a04b71cbd642a00352dce0539fe1fe22dd4

Resolve size relocation with copy relocation

We can resolve size relocation against symbol which needs copy relocation
when building executable.

bfd/

	PR ld/20550
	* elf64-x86-64.c (elf_x86_64_relocate_section): Resolve size
	relocation with copy relocation when building executable.

ld/

	PR ld/20550
	* testsuite/ld-x86-64/pr20550a.s: New file.
	* testsuite/ld-x86-64/pr20550b.s: Likewise.
	* testsuite/ld-x86-64/x86-64.exp (x86_64tests): Add tests for
	PR ld/20550.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce make_cleanup_restore_current_ui
@ 2016-09-07  5:56 sergiodj+buildbot
  2016-09-07 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  5:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a025b477cc466112af0b120c5f2bf5d62a62017e ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: a025b477cc466112af0b120c5f2bf5d62a62017e

Introduce make_cleanup_restore_current_ui

Just a tidy, no functional changes.

gdb/ChangeLog:
2016-09-06  Pedro Alves  <palves@redhat.com>

	* event-top.c (restore_ui_cleanup): Now static.
	(make_cleanup_restore_current_ui): New function.
	(switch_thru_all_uis_init): Use it.
	* infcall.c (call_thread_fsm_should_stop): Use it.
	* infrun.c (fetch_inferior_event): Use it.
	* top.c (new_ui_command): Use it.
	* top.h (restore_ui_cleanup): Delete declaration.
	(make_cleanup_restore_current_ui): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] new-ui command: gdb internal errors if input is already pending
@ 2016-09-07  7:09 sergiodj+buildbot
  2016-09-07 18:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  7:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4295e285efa8193504ee08b9f633d9f8680bf181 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4295e285efa8193504ee08b9f633d9f8680bf181

new-ui command: gdb internal errors if input is already pending

I noticed that if input is already pending on the new-ui TTY, gdb
internal-errors.

E.g., create /dev/pts/2, and type anything there (even just <return>
is sufficient).

Now start GDB creating a new UI on that TTY, while at the same time,
running a synchronous execution command.  Something like:

$ gdb program -ex "new-ui console /dev/pts/2" -ex "start"

Back on /dev/pts/2, we get:

  (gdb) .../src/gdb/event-top.c:360: internal-error: double prompt
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

While the main UI was waiting for "start" to finish, gdb kepts pumping
events, including the input fd of the extra console.  The problem is
that stdin_event_handler doesn't restore the current UI back to what
it was, assuming that it's only ever called from the top level event
loop.  However, in this case, it's being called from the nested event
loop from within maybe_wait_sync_command_done.

When finally the "start" command is done, we reach the code that
prints the prompt in the main UI, just before starting the main event
loop.  Since now the current UI is pointing at the extra console (by
mistake), we find ourselves printing a double prompt on the extra
console.  This is caught by the assertion that fails, as shown above.

Since other event handlers also don't restore the UI (e.g., signal
event handlers), I think it's better if whatever is pumping events to
take care to restore the UI, if it cares.  That's what this patch
does.  New test included.

gdb/ChangeLog:
2016-09-06  Pedro Alves  <palves@redhat.com>

	* top.c (wait_sync_command_done): Don't assume current_ui doesn't
	change across events.  Restore the current UI before returning.
	(gdb_readline_wrapper): Restore the current UI before returning.

gdb/testsuite/ChangeLog:
2016-09-06  Pedro Alves  <palves@redhat.com>

	* gdb.base/new-ui-pending-input.c: New file.
	* gdb.base/new-ui-pending-input.exp: New file.
	* gdb.exp (clear_gdb_spawn_id): New procedure.
	(with_spawn_id): Check whether gdb_spawn_id exists before
	referencing it.  If gdb_spawn_id didn't exist on entry, clear it
	on exit.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [arm] Automatically enable CRC instructions on supported ARMv8-A CPUs.
@ 2016-09-07 21:00 sergiodj+buildbot
  2016-09-07 20:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-07 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27e5a270962fb92c07e7d476966ba380fa3bb68e ***

Author: Richard Earnshaw <Richard.Earnshaw@arm.com>
Branch: master
Commit: 27e5a270962fb92c07e7d476966ba380fa3bb68e

[arm] Automatically enable CRC instructions on supported ARMv8-A CPUs.

2016-09-07  Richard Earnshaw  <rearnsha@arm.com>

	* opcode/arm.h (ARM_ARCH_V8A_CRC): New architecture.

2016-09-07  Richard Earnshaw  <rearnsha@arm.com>

	* config/tc-arm.c ((arm_cpus): Use ARM_ARCH_V8A_CRC for all
	ARMv8-A CPUs except xgene1.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove some unneeded casts from remote.c
@ 2016-09-10 20:57 sergiodj+buildbot
  2016-09-10 20:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-10 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5c4fcd9712f516e2b5cfb8ad2464f0d5dfcc61b ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: f5c4fcd9712f516e2b5cfb8ad2464f0d5dfcc61b

Remove some unneeded casts from remote.c

I happened to notice a few unneeded casts in remote.c.  In some cases
these are no-ops, and in others these cast away const, but in a context
where this is not needed.

I'm checking this in under the obvious rule.
Tested by rebuilding on x86-64 Fedora 24.

2016-09-08  Tom Tromey  <tom@tromey.com>

	* remote.c (remote_notif_stop_ack, remote_wait_as)
	(show_remote_cmd): Remove unneeded casts.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Pass HWCAP to ifunc resolver
@ 2016-09-10 23:25 sergiodj+buildbot
  2016-09-12  5:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-10 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e1b2624a08fae1f669d879946d5041945b4dc248 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: e1b2624a08fae1f669d879946d5041945b4dc248

Pass HWCAP to ifunc resolver

On various GNU Elf architectures, including AArch64, ARM, s390/s390x,
ppc32/64, and sparc32/64, the dynamic loader passes HWCAP as a parameter
to each ifunc resolver.  Currently there is an open glibc Bugzilla that
requests this to be generalized to all architectures:

  https://sourceware.org/bugzilla/show_bug.cgi?id=19766

And various ifunc resolvers already rely on receiving HWCAP.  Currently
GDB always calls an ifunc resolver without any arguments; thus the
resolver may receive garbage, and based on that, the resolver may decide
to return a function that is not suited for the given platform.

This patch always passes HWCAP to ifunc resolvers, even on systems where
the dynamic loader currently behaves otherwise.  The rationale is
that (1) the dynamic loader may get adjusted on those systems as well in
the future; (2) passing an unused argument should not cause a problem
with existing resolvers; and (3) the logic is much simpler without such
a distinction.

gdb/ChangeLog:

	* elfread.c (auxv.h): New include.
	(elf_gnu_ifunc_resolve_addr): Pass HWCAP to ifunc resolver.

gdb/testsuite/ChangeLog:

	* gdb.base/gnu-ifunc-lib.c (resolver_hwcap): New external
	variable declaration.
	(gnu_ifunc): Add parameter hwcap.  Store it in resolver_hwcap.
	* gdb.base/gnu-ifunc.c (resolver_hwcap): New global variable.
	* gdb.base/gnu-ifunc.exp: Add test to verify that the resolver
	received HWCAP as its argument.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use target_sim_options for sim target.
@ 2016-09-12 15:28 sergiodj+buildbot
  2016-09-12 15:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-12 15:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc3c284619d0482506f532cc8c1b00018fe14136 ***

Author: Jon Beniston <jon@beniston.com>
Branch: master
Commit: cc3c284619d0482506f532cc8c1b00018fe14136

Use target_sim_options for sim target.

2016-09-10  Jon Beniston  <jon@beniston.com>

	* lib/mi-support.exp (mi_gdb_target_load): Use target_sim_options
	for sim target.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix false FAIL on gdb.base/stap-probe.exp, due to ICF optimization
@ 2016-09-12 17:26 sergiodj+buildbot
  2016-09-12 17:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-12 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c29df25b7c2ff006b45afd80ee6dd734ebbd47c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 2c29df25b7c2ff006b45afd80ee6dd734ebbd47c

Fix false FAIL on gdb.base/stap-probe.exp, due to ICF optimization

GCC 6's ICF optimization pass is making the declaration of 'm1' and
'm2', on gdb.base/stap-probe.c, to be unified.  However, this leads to
only one instance of the probe 'two' being created, which causes a
failure on the testsuite (which expects a multi-location breakpoint to
be inserted on the probe).

This patch fixes this failure by declaring a dummy variable on 'm1',
and using it as an argument to m1's version of probe 'two'.  Since we
do not care about the contents of the functions nor about the
arguments of each probe 'two', this is OK.

gdb/testsuite/ChangeLog:
2016-09-11  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.base/stap-probe.c (m1): New variable 'dummy', necessary to
	make m1's definition to be different from m2's.  Use 'dummy' as an
	argument for probe 'two'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S/390: Fix kmctr instruction type.
@ 2016-09-13 17:42 sergiodj+buildbot
  2016-09-13 17:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-13 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b71537b6be5d66d6b6cf1273f7acab0621adfc5 ***

Author: Patrick Steuer <steuer@linux.vnet.ibm.com>
Branch: master
Commit: 8b71537b6be5d66d6b6cf1273f7acab0621adfc5

S/390: Fix kmctr instruction type.

opcodes/ChangeLog:

2016-09-12  Patrick Steuer  <steuer@linux.vnet.ibm.com>

	* s390-opc.txt: Fix kmctr instruction type.

gas/ChangeLog:

2016-09-12  Patrick Steuer  <steuer@linux.vnet.ibm.com>

	* testsuite/gas/s390/zarch-z196.d: Adjust testcase.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S/390: Add alternate processor names.
@ 2016-09-13 18:36 sergiodj+buildbot
  2016-09-13 20:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-13 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 952c3f51ac994f5e98aa829076609124cf9e5243 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 952c3f51ac994f5e98aa829076609124cf9e5243

S/390: Add alternate processor names.

This patch adds alternate CPU names which adhere to the number of the
architecture document.  So instead of having z196, zEC12, and z13 you
can use arch9, arch10, and arch11.  The old cpu names stay valid and
should primarily be used.

The alternate names are supposed to improve compatibility with the IBM
XL compiler toolchain which uses the arch numbering.

opcodes/ChangeLog:

2016-09-12  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-mkopc.c (main): Support alternate arch strings.

gas/ChangeLog:

2016-09-12  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* config/tc-s390.c (s390_parse_cpu): Support alternate arch
	strings.
	* doc/as.texinfo: Document new arch strings.
	* doc/c-s390.texi: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix for gdb.server/non-existing-program.exp test case
@ 2016-09-14 12:25 sergiodj+buildbot
  2016-09-14 12:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-14 12:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7313bced5b695b71a707c82b6817763046e21bb1 ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: 7313bced5b695b71a707c82b6817763046e21bb1

Fix for gdb.server/non-existing-program.exp test case

The test checks to make sure GDB exits cleanly if there is
no valid target binary.  Currently, ppc and S390 fail on this
test.  The function target_post_create_inferior () calls
linux_post_create_inferior () which calls the architecture
specific functions s390_arch_setup () and ppc_arch_setup ()
which make ptrace calls	to access the architecture specific
registers.  These ptrace calls fail because the	process	does
not exist causing GDB to exit on error.

This patch checks to see if the initial ptrace (PTRACE_TRACEME, ...)
call returned a status of TARGET_WAITKIND_EXITED indicating the
target has already exited.  If the target has exited, then the
target_post_create_inferior () is not called since there is no
inferior to be setup.  The test	to see if the initial ptrace
call succeeded is done after the ptrace (PTRACE_TRACEME, ...)
call and the wait for the inferior process to stop, assuming
it exists, has occurred.

The patch has been tested on X86 64-bit, ppc64 and s390.  If
fixes the test failures	on ppc64 and s390.  The	test does not
fail on	X86 64-bit.  The patch does not	introduce any additional
regression failures on any of these three platforms.

gdbserver/ChangeLog

2016-09-06  Carl Love  <cel@us.ibm.com>

	* server.c (start_inferior):  Do not call
	function target_post_create_inferior () if the
	inferior process has already exited.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix for gdb.server/non-existing-program.exp test case
@ 2016-09-14 13:01 sergiodj+buildbot
  2016-09-14 14:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-14 13:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d8cb77dff14d44b1e3b670442438da496f99c6e ***

Author: Carl E. Love <carll@oc4738070240.ibm.com>
Branch: master
Commit: 1d8cb77dff14d44b1e3b670442438da496f99c6e

Fix for gdb.server/non-existing-program.exp test case

The last commit was supposed to have the reference to ptrace () removed.
The patch didn't get updated correctly before the commit.  This commit
fixes the comment as requested

gdbserver/ChangeLog

	2016-09-06  Carl Love  <cel@us.ibm.com>

	* server.c (start_inferior):  Fixed comment, requested comment change
	didn't get updated correctly.  Removed reference to ptrace () call as
 	it is only true on Linux systems.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Stop the ARC disassembler from seg-faulting if initialised without a BFD present.
@ 2016-09-14 16:07 sergiodj+buildbot
  2016-09-14 16:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-14 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dce084426d75b45ef728425a880d642a604c36a7 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: dce084426d75b45ef728425a880d642a604c36a7

Stop the ARC disassembler from seg-faulting if initialised without a BFD present.

	* arc-dis.c (arc_get_disassembler): Accept a null bfd gracefully.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Prevent segfault in GDB when searching for architecture matches.
@ 2016-09-14 17:34 sergiodj+buildbot
  2016-09-14 17:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-14 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d9bbb73c1df68741048c3d0f837b50c289ea608 ***

Author: Bhushan Attarde <bhushan.attarde@imgtec.com>
Branch: master
Commit: 5d9bbb73c1df68741048c3d0f837b50c289ea608

Prevent segfault in GDB when searching for architecture matches.

	* format.c (struct bfd_preserve): New "build_id" field.
	(bfd_preserve_save): Save "build_id".
	(bfd_preserve_restore): Restore "build_id".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix ld --gc-section segfault with ARMv8-M entry function in absolute section
@ 2016-09-15  4:45 sergiodj+buildbot
  2016-09-15 12:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-15  4:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f90d84b2f2995829d6af475077598d45ef1d127 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 4f90d84b2f2995829d6af475077598d45ef1d127

Fix ld --gc-section segfault with ARMv8-M entry function in absolute section

bfd/
2016-09-14  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* elf32-arm.c (elf32_arm_gc_mark_extra_sections): Only mark section
	not already marked.

ld/
2016-09-14  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* testsuite/ld-arm/cmse-veneers.s: Add a test for ARMv8-M Security
	Extensions entry functions in absolute section.
	* testsuite/ld-arm/cmse-veneers.rd: Adapt expected output accordingly.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Modify POWER9 support to match final ISA 3.0 documentation.
@ 2016-09-15 21:47 sergiodj+buildbot
  2016-09-15 22:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-15 21:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd486b633e87f8ab2977592d56a6d98168814e2e ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: fd486b633e87f8ab2977592d56a6d98168814e2e

Modify POWER9 support to match final ISA 3.0 documentation.

opcodes/
	* ppc-opc.c (powerpc_opcodes) <slbiag>: New mnemonic.
	<addex., brd, brh, brw, lwzmx, nandxor, rldixor, setbool,
	xor3>: Delete mnemonics.
	<cp_abort>: Rename mnemonic from ...
	<cpabort>: ...to this.
	<setb>: Change to a X form instruction.
	<sync>: Change to 1 operand form.
	<copy>: Delete mnemonic.
	<copy_first>: Rename mnemonic from ...
	<copy>: ...to this.
	<paste, paste.>: Delete mnemonics.
	<paste_last>: Rename mnemonic from ...
	<paste.>: ...to this.

gas/
	* testsuite/gas/ppc/power9.d <slbiag, cpabort> New tests.
	<addex., brd, brh, brw, lwzmx, nandxor, rldixor, setbool,
	xor3, cp_abort, copy_first, paste, paste_last, sync>: Remove tests.
	<copy, paste.>: Update tests.
	* testsuite/gas/ppc/power9.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Disable ccache
@ 2016-09-15 23:31 sergiodj+buildbot
  2016-09-15 23:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-15 23:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49b4de64242d4ae035e0e2197837278e33c187fc ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 49b4de64242d4ae035e0e2197837278e33c187fc

testsuite: Disable ccache

There were always various problems with compatibility with ccache:
	https://bugzilla.redhat.com/show_bug.cgi?id=488863
	https://bugzilla.redhat.com/show_bug.cgi?id=759592
	https://sourceware.org/ml/gdb-patches/2009-02/msg00397.html

IMO in a summary ccache finds more a benefit of faster compilation despite the
debug info is no longer exactly the same (as without ccache).

Although for example in this case ccache helped to find a real GDB bug:
	https://sourceware.org/ml/gdb-patches/2015-01/msg00497.html

For the GDB testcases ccache has (IMO) no real performance advantage and it
just brings heisenbugs - false FAILs - from time to time:

Breakpoint 1, main () at gdb/testsuite/gdb.base/vdso-warning.c:21^M
	21        return 0;^M
	(gdb) PASS: gdb.base/vdso-warning.exp: run: startup
	->
	Breakpoint 1, main () at gdb/testsuite/gdb.base/hbreak-unmapped.c:21^M
	21        return 0;^M
	(gdb) FAIL: gdb.base/vdso-warning.exp: run: startup

So I find most safe and easy to just disable ccache for all testsuites.

gdb/testsuite/ChangeLog
2016-09-15  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* lib/future.exp: Set CCACHE_DISABLE, clear CCACHE_NODISABLE.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix C++11 compilation failure for gdb.cp/m-static.exp
@ 2016-09-16 18:19 sergiodj+buildbot
  2016-09-16 18:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dfe7003423d41394d2475680e55af796566b8e ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: d2dfe7003423d41394d2475680e55af796566b8e

testsuite: Fix C++11 compilation failure for gdb.cp/m-static.exp

gcc-6.2.1-1.fc26.x86_64

g++ -std=c++03:
no warnings

g++:
In file included from /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.cc:79:0:
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.h:9:34: error: constexpr needed for in-class initialization of static
data member const float gnu_obj_4::somewhere of non-integral type [-fpermissive]
   static const float somewhere = 3.14159;
                                  ^~~~~~~

clang++:
In file included from /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.cc:79:
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.h:9:22: warning: in-class initializer for static data member of type 'const
float' is a GNU extension [-Wgnu-static-float-init]
  static const float somewhere = 3.14159;
                     ^           ~~~~~~~
1 warning generated.

clang++ -std=c++11:
In file included from /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.cc:79:
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.h:9:22: error: in-class initializer for static data member of type 'const
float' requires 'constexpr' specifier [-Wstatic-float-init]
  static const float somewhere = 3.14159;
                     ^           ~~~~~~~
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.h:9:3: note: add 'constexpr'
  static const float somewhere = 3.14159;
  ^
  constexpr
1 error generated.

OK for check-in?

After the fix out of the 4 combinations above only this one remains non-empty:

clang++:
In file included from /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.cc:79:
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.h:9:22: warning: in-class initializer for static data member of type 'const
float' is a GNU extension [-Wgnu-static-float-init]
  static const float somewhere = 3.14159;
                     ^           ~~~~~~~
1 warning generated.

On Thu, 15 Sep 2016 15:10:50 +0200, Pedro Alves wrote:

Hmm, OK, now that I read the test, I think you were right in trying to
keep it safe, actually.  The .exp file has:

if { $non_dwarf } { setup_xfail *-*-* }
gdb_test "print test4.everywhere" "\\$\[0-9\].* = 317" "static const int initialized in class definition"
if { $non_dwarf } { setup_xfail *-*-* }
gdb_test "print test4.somewhere" "\\$\[0-9\].* = 3.14\[0-9\]*" "static const float initialized in class definition"
                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Added by this:

 https://sourceware.org/bugzilla/show_bug.cgi?id=11702
 https://sourceware.org/ml/gdb-patches/2010-06/msg00677.html
 https://sourceware.org/ml/gdb-patches/2010-06/txt00011.txt

So the new patch would make that highlighted tested above not
test what its test message says it is testing.

So I now think your original patch is better.  Please push
that one instead.

gdb/testsuite/ChangeLog
2016-09-15  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.cp/m-static.h (gnu_obj_4::somewhere): Use constexpr for C++11.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] Disassemble correctly extension instructions.
@ 2016-09-16 19:43 sergiodj+buildbot
  2016-09-16 19:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 19:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f807f43d7eba5bba3042554f9b3e884d71a68309 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: f807f43d7eba5bba3042554f9b3e884d71a68309

[ARC] Disassemble correctly extension instructions.

For each MAJOR-MINOR opcode tuple, we can have either a 3-operand, or
2-operand, or a single operand instruction format, depending on the
values present in i-field, and a-field.

The disassembler is reading the section containing the extension
instruction format and stores them in a table.  Each table element
represents a linked list with encodings for a particular MAJOR-MINOR
tuple.

The current implementation checks only against the first element of
the list, hence, the issue.

This patch is walking the linked list until empty or finds an opcode
match.  It also adds a test outlining the found problem.

opcodes/
2016-09-15  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-dis.c (find_format): Walk the linked list pointed by einsn.

gas/
2016-09-15  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/gas/arc/textinsnxop.d: New file.
	* testsuite/gas/arc/textinsnxop.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix false FAIL in gdb.cp/casts.exp
@ 2016-09-16 20:49 sergiodj+buildbot
  2016-09-16 21:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 20:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d41a5c096ec613f7df33d5d5ea4c0e512ac1e87a ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: d41a5c096ec613f7df33d5d5ea4c0e512ac1e87a

testsuite: Fix false FAIL in gdb.cp/casts.exp

gcc-6.2.1-1.fc26.x86_64

gdb compile failed, /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:40:10: error: expected primary-expression before 'int'
 decltype(int x)
          ^~~
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:40:10: error: expected ')' before 'int'
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:40:1: error: expected unqualified-id before 'decltype'
 decltype(int x)
 ^~~~~~~~
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc: In function 'int main(int, char**)':
/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/casts.cc:59:14: error: expected primary-expression before 'decltype'
   double y = decltype(2);
              ^~~~~~~~

'decltype' is a registered keyword since C++11 which is now a default for GCC.

On Thu, 15 Sep 2016 14:06:56 +0200, Pedro Alves wrote:

Seems to be exercising the FLAG_SHADOW bits:

...
    {"__typeof__", TYPEOF, OP_TYPEOF, 0 },
    {"__typeof", TYPEOF, OP_TYPEOF, 0 },
    {"typeof", TYPEOF, OP_TYPEOF, FLAG_SHADOW },
    {"__decltype", DECLTYPE, OP_DECLTYPE, FLAG_CXX },
    {"decltype", DECLTYPE, OP_DECLTYPE, FLAG_CXX | FLAG_SHADOW },
...

/* This is used to associate some attributes with a token.  */

enum token_flag
{
...
  /* If this bit is set, the token is conditional: if there is a
     symbol of the same name, then the token is a symbol; otherwise,
     the token is a keyword.  */

  FLAG_SHADOW = 2
};

So perhaps a better fix is to move that particular test to a
separate testcase that force-compiles with -std=c++03.

gdb/testsuite/ChangeLog
2016-09-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.cp/casts.cc (decltype): Move it ...
	(main): ... with its call to ...
	* gdb.cp/casts03.cc: ... a new file.
	* gdb.cp/casts.exp: Add new file casts03.cc, move decltype test to it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S390: Migrate watch areas from list to VEC type
@ 2016-09-16 22:36 sergiodj+buildbot
  2016-09-17  0:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 22:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17c84ccaf042dfb7dd81e4670b74768fe5a96017 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 17c84ccaf042dfb7dd81e4670b74768fe5a96017

S390: Migrate watch areas from list to VEC type

For S390, the list of active watchpoints is maintained in a list based
at "watch_base".  This refactors the list to a vector "watch_areas".

gdb/ChangeLog:

	* s390-linux-nat.c (s390_watch_area): New typedef.  Define a VEC.
	(watch_base): Remove variable.
	(watch_areas): New variable.
	(s390_stopped_by_watchpoint): Transform operations on the
	watch_base list to equivalent operations on the watch_areas VEC.
	(s390_prepare_to_resume): Likewise.
	(s390_insert_watchpoint): Likewise.
	(s390_remove_watchpoint): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S390: Multi-inferior watchpoint support
@ 2016-09-16 23:12 sergiodj+buildbot
  2016-09-17  1:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 373c3dad74da78c46bc1fe4280a26d07e5b54cdd ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 373c3dad74da78c46bc1fe4280a26d07e5b54cdd

S390: Multi-inferior watchpoint support

Support different sets of watchpoints in multiple inferiors.

gdb/ChangeLog:

	* s390-linux-nat.c (watch_areas): Remove variable.  Replace by a
	member of...
	(struct s390_debug_reg_state): ...this.  New struct.
	(struct s390_process_info): New struct.
	(s390_process_list): New variable.
	(s390_find_process_pid, s390_add_process, s390_process_info_get)
	(s390_get_debug_reg_state): New functions.
	(s390_stopped_by_watchpoint): Now access the watch_areas VEC via
	s390_get_debug_reg_state.
	(s390_prepare_to_resume): Likewise.
	(s390_insert_watchpoint): Likewise.
	(s390_remove_watchpoint): Likewise.
	(s390_forget_process, s390_linux_new_fork): New linux_nat target
	methods.
	(_initialize_s390_nat): Register them.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] linux-nat: Add function lwp_is_stepping
@ 2016-09-17  0:28 sergiodj+buildbot
  2016-09-17  8:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-17  0:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e00e962c57138f0dd8c261cbd6918782deec3c4 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 0e00e962c57138f0dd8c261cbd6918782deec3c4

linux-nat: Add function lwp_is_stepping

Add the function lwp_is_stepping which indicates whether the given LWP
is currently single-stepping.  This is a common interface, usable from
native GDB as well as from gdbserver.

gdb/gdbserver/ChangeLog:

	* linux-low.c (lwp_is_stepping): New function.

gdb/ChangeLog:

	* nat/linux-nat.h (lwp_is_stepping): New declaration.
	* linux-nat.c (lwp_is_stepping): New function.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] S390: Hardware breakpoint support
@ 2016-09-17  1:02 sergiodj+buildbot
  2016-09-17 10:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-17  1:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8193adea2f86e37423a5d0acffb69b80bde05d52 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 8193adea2f86e37423a5d0acffb69b80bde05d52

S390: Hardware breakpoint support

Add hardware breakpoint support for S390 targets.

gdb/ChangeLog:

	* s390-linux-nat.c (PER_BIT, PER_EVENT_BRANCH, PER_EVENT_IFETCH)
	(PER_EVENT_STORE, PER_EVENT_NULLIFICATION)
	(PER_CONTROL_BRANCH_ADDRESS, PER_CONTROL_SUSPENSION)
	(PER_CONTROL_ALTERATION): New macros.
	(struct s390_debug_reg_state) <break_areas>: New member.
	(s390_forget_process): Free break_areas as well.
	(s390_linux_new_fork): Copy break_areas as well.
	(s390_prepare_to_resume): Install hardware breakpoints.
	(s390_can_use_hw_breakpoint): Indicate support for hardware
	breakpoints.
	(s390_insert_hw_breakpoint, s390_remove_hw_breakpoint): New
	linux_nat target methods.
	(_initialize_s390_nat): Register them.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp: No longer skip hardware breakpoint tests on s390.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Fix std::{min, max}-related build breakage on 32-bit hosts
@ 2016-09-19  6:16 sergiodj+buildbot
  2016-09-19 13:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-19  6:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 768adc05c44c7e8b5c0f9ca5ad3ca96657715293 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 768adc05c44c7e8b5c0f9ca5ad3ca96657715293

gdb: Fix std::{min, max}-related build breakage on 32-bit hosts

Building on a 32-bit host fails currently with errors like:

  .../src/gdb/exec.c: In function target_xfer_status section_table_read_available_memory(gdb_byte*, ULONGEST, ULONGEST, ULONGEST*):
  .../src/gdb/exec.c:801:54: error: no matching function for call to min(ULONGEST, long unsigned int)
      end = std::min (offset + len, r->start + r->length);
							^
  In file included from /usr/include/c++/5.3.1/algorithm:61:0,
		   from .../src/gdb/exec.c:46:
  /usr/include/c++/5.3.1/bits/stl_algobase.h:195:5: note: candidate: template<class _Tp> const _Tp& std::min(const _Tp&, const _Tp&)
       min(const _Tp& __a, const _Tp& __b)
       ^
  /usr/include/c++/5.3.1/bits/stl_algobase.h:195:5: note:   template argument deduction/substitution failed:
  .../src/gdb/exec.c:801:54: note:   deduced conflicting types for parameter const _Tp (long long unsigned int and long unsigned int)
      end = std::min (offset + len, r->start + r->length);
							^
  In file included from /usr/include/c++/5.3.1/algorithm:61:0,
		   from .../src/gdb/exec.c:46:
  /usr/include/c++/5.3.1/bits/stl_algobase.h:243:5: note: candidate: template<class _Tp, class _Compare> const _Tp& std::min(const _Tp&, const _Tp&, _Compare)
       min(const _Tp& __a, const _Tp& __b, _Compare __comp)
       ^

The problem is that the std::min/std::max function templates use the
same type for both parameters.  When the argument types are different,
the compiler can't automatically deduce which template specialization
to pick from the arguments' types.

Fix that by specifying the specialization we want explicitly.

gdb/ChangeLog:
2016-09-18  Pedro Alves  <palves@redhat.com>

	* breakpoint.c (hardware_watchpoint_inserted_in_range): Explicitly
	specify the std:min/std::max specialization.
	* exec.c (section_table_read_available_memory): Likewise.
	* remote.c (remote_read_qxfer): Likewise.
	* target.c (simple_verify_memory): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/s390: Fix build breakage due to std::min/std::max usage without header
@ 2016-09-19 12:42 sergiodj+buildbot
  2016-09-19 15:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-19 12:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93689493b376c4e5616c1679733619f96202c369 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 93689493b376c4e5616c1679733619f96202c369

gdb/s390: Fix build breakage due to std::min/std::max usage without header

  [...]
  .../gdb/s390-linux-nat.c: In function 'void s390_prepare_to_resume(lwp_info*)':
  .../gdb/s390-linux-nat.c:703:20: error: 'min' is not a member of 'std'
      watch_lo_addr = std::min (watch_lo_addr, area->lo_addr);
  [...]

gdb/ChangeLog:
2016-09-18  Pedro Alves  <palves@redhat.com>

	* s390-linux-nat.c: Include <algorithm>.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver
@ 2016-09-19 16:45 sergiodj+buildbot
  2016-09-19 17:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-19 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc1e6c81d5b77d78282c47f6fd7f697e564a6eb6 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: bc1e6c81d5b77d78282c47f6fd7f697e564a6eb6

Consolidate target_mourn_inferior between GDB and gdbserver

This patch consolidates the API of target_mourn_inferior between GDB
and gdbserver, in my continuing efforts to make sharing the
fork_inferior function possible between both.

GDB's version of the function did not care about the inferior's ptid
being mourned, but gdbserver's needed to know this information.  Since
it actually makes sense to pass the ptid as an argument, instead of
depending on a global value directly (which GDB's version did), I
decided to make the generic API to accept it.  I then went on and
extended all calls being made on GDB to include a ptid argument (which
ended up being inferior_ptid most of the times, anyway), and now we
have a more sane interface.

On GDB's side, after talking to Pedro a bit about it, we decided that
just an assertion to make sure that the ptid being passed is equal to
inferior_ptid would be enough for now, on the GDB side.  We can remove
the assertion and perform more operations later if we ever pass
anything different than inferior_ptid.

Regression tested on our BuildBot, everything OK.

I'd appreciate a special look at gdb/windows-nat.c's modification
because I wasn't really sure what to do there.  It seemed to me that
maybe I should build a ptid out of the process information there, but
then I am almost sure the assertion on GDB's side would trigger.

gdb/ChangeLog:
2016-09-19  Sergio Durigan Junior  <sergiodj@redhat.com>

	* darwin-nat.c (darwin_kill_inferior): Adjusting call to
	target_mourn_inferior to include ptid_t argument.
	* fork-child.c (startup_inferior): Likewise.
	* gnu-nat.c (gnu_kill_inferior): Likewise.
	* inf-ptrace.c (inf_ptrace_kill): Likewise.
	* infrun.c (handle_inferior_event_1): Likewise.
	* linux-nat.c (linux_nat_attach): Likewise.
	(linux_nat_kill): Likewise.
	* nto-procfs.c (interrupt_query): Likewise.
	(procfs_interrupt): Likewise.
	(procfs_kill_inferior): Likewise.
	* procfs.c (procfs_kill_inferior): Likewise.
	* record.c (record_mourn_inferior): Likewise.
	* remote-sim.c (gdbsim_kill): Likewise.
	* remote.c (remote_detach_1): Likewise.
	(remote_kill): Likewise.
	* target.c (target_mourn_inferior): Change declaration to accept
	new ptid_t argument; use gdb_assert on it.
	* target.h (target_mourn_inferior): Move function prototype from
	here...
	* target/target.h (target_mourn_inferior): ... to here.  Adjust it
	to accept new ptid_t argument.
	* windows-nat.c (get_windows_debug_event): Adjusting call to
	target_mourn_inferior to include ptid_t argument.

gdb/gdbserver/ChangeLog:
2016-09-19  Sergio Durigan Junior  <sergiodj@redhat.com>

	* server.c (start_inferior): Call target_mourn_inferior instead of
	mourn_inferior; pass ptid_t argument to it.
	(resume): Likewise.
	(handle_target_event): Likewise.
	* target.c (target_mourn_inferior): New function.
	* target.h (mourn_inferior): Delete macro.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Fix build breakage with GCC 4.1 and --disable-nls
@ 2016-09-20  9:06 sergiodj+buildbot
  2016-09-20  8:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-20  9:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6679754127e51d9c3bd0e387fabbe4e71038c8ce ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6679754127e51d9c3bd0e387fabbe4e71038c8ce

gdb: Fix build breakage with GCC 4.1 and --disable-nls

Ref: https://sourceware.org/ml/gdb-patches/2016-09/msg00203.html

The std::{min,max} patch caused build failures when configuring GDB
with with --disable-nls and using GCC 4.1.

The reason is this bit in common/gdb_locale.h:

 #ifdef ENABLE_NLS
 ...
 #else
 # define gettext(Msgid) (Msgid)
 ...
 #endif

This causes problems if the <libintl.h> header is first included at
any point after "gdb_locale.h".

Specifically, the gettext&co declarations in libintl.h:

 extern char *gettext (__const char *__msgid)
      __THROW __attribute_format_arg__ (1);

end up broken after preprocessing:

 extern char *(__const char *__msgid)
      throw () __attribute__ ((__format_arg__ (1)));

After the std::min/std::max change to include <algorithm>, this now
happens with at least the GCC 4.1 copy of <algorithm>, which includes
<libintl.h> via <bits/stl_algobase.h>, <iosfwd>, and
<bits/c++locale.h>.

The fix is to simply remove the troublesome *gettext and *textdomain
macros, leaving only the _ and N_ ones.

gdb/ChangeLog:
2016-09-19  Pedro Alves  <palves@redhat.com>

	* common/gdb_locale.h [!ENABLE_NLS] (gettext, dgettext, dcgettext,
	textdomain, bindtextdomain): Delete macros.
	* main.c (captured_main) [!ENABLE_NLS]: Skip bintextdomain and
	textdomain calls.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use 'event_ptid' instead of 'resume_ptid' on startup_inferior (fix for regression on my last commit)
@ 2016-09-20 17:47 sergiodj+buildbot
  2016-09-20 17:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-20 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d5adfe3118050243e85469ad891c7813e4db68a ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 7d5adfe3118050243e85469ad891c7813e4db68a

Use 'event_ptid' instead of 'resume_ptid' on startup_inferior (fix for regression on my last commit)

Pedro pointed out a regression happening on gdb.mi/mi-exec-run.exp,
and as it turned out, this was a thinko when dealing with some events
on startup_inferior.  Basically, one needs to pass 'event_ptid' to
target_mourn_inferior, but I mistakenly passed 'resume_ptid'.

This commit fixes it.

Built and regtested on BuildBot, now with fixed e-mail notifications!

gdb/ChangeLog:
2016-09-20  Sergio Durigan Junior  <sergiodj@redhat.com>

	* fork-inferior.c (startup_inferior): Pass 'event_ptid' instead of
	'resume_ptid' to 'target_mourn_inferior'.  Fix regression
	introduced by my last commit.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ppc: Fix record support of Store String Word instructions
@ 2016-09-20 20:52 sergiodj+buildbot
  2016-09-20 20:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-20 20:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f7efd5bf76aa5065298d13aefb109ecfd7a825a ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: 9f7efd5bf76aa5065298d13aefb109ecfd7a825a

ppc: Fix record support of Store String Word instructions

gdb/ChangeLog
2016-09-20  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (ppc_process_record_op31): Fix record of Store String
	Word instructions.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Keep reserved bits in CPSR on write
@ 2016-09-21 15:44 sergiodj+buildbot
  2016-09-21 15:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 15:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc6cda2ee85d2c2719db3b5ae3a1ae963f28416b ***

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

Keep reserved bits in CPSR on write

In patch https://sourceware.org/ml/gdb-patches/2016-04/msg00529.html
I cleared reserved bits when reading CPSR.  It makes a problem that
these bits (zero) are written back to kernel through ptrace, and it
changes the state of the processor on some recent kernel, which is
unexpected.

In this patch, I keep these reserved bits when write CPSR back to
hardware.

gdb:

2016-09-21  Yao Qi  <yao.qi@linaro.org>

	* aarch32-linux-nat.c (aarch32_gp_regcache_collect): Keep
	bits 20 to 23.

gdb/gdbserver:

2016-09-21  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.c (arm_fill_gregset): Keep bits 20 to
	23.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/testsuite: mips16-thunks: Use `standard_output_file'
@ 2016-09-21 17:21 sergiodj+buildbot
  2016-09-21 18:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d0ec882241884d0cabb27f8fee1262dbc7cf9e7 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 3d0ec882241884d0cabb27f8fee1262dbc7cf9e7

MIPS/testsuite: mips16-thunks: Use `standard_output_file'

Correct a commit 2151ccc56c74 ("Always organize test artifacts in a
directory hierarchy") regression causing:

Running .../gdb/testsuite/gdb.arch/mips16-thunks.exp ...
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.arch/mips16-thunks-inmain.o: No such file or directory
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.arch/mips16-thunks-main.o: No such file or directory
gdb compile failed, mips-mti-linux-gnu-gcc: error: .../gdb/testsuite/gdb.arch/mips16-thunks-inmain.o: No such file or directory
mips-mti-linux-gnu-gcc: error: .../gdb/testsuite/gdb.arch/mips16-thunks-main.o: No such file or directory
UNSUPPORTED: gdb.arch/mips16-thunks.exp: No MIPS16 support in the toolchain.

by using `standard_output_file' to construct output file names
throughout.

	gdb/testsuite/
	* gdb.arch/mips16-thunks.exp: Use `standard_output_file'
	throughout.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 02/32] Avoid hard-coded limit in indented_print
@ 2016-09-21 19:48 sergiodj+buildbot
  2016-09-21 20:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd11d5d83775e6d05c8e49f2233fb1cf883ff5b4 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: bd11d5d83775e6d05c8e49f2233fb1cf883ff5b4

[AArch64][SVE 02/32] Avoid hard-coded limit in indented_print

The maximum indentation needed by aarch64-gen.c grows as more
instructions are added to aarch64-tbl.h.  Rather than having to
increase the indentation limit to a higher value, it seemed better
to replace it with "%*s".

opcodes/
	* aarch64-gen.c (indented_print): Avoid hard-coded indentation limit.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 13/32] Add an F_STRICT flag
@ 2016-09-21 20:22 sergiodj+buildbot
  2016-09-21 21:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 20:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4989adac848eb8f2fee8b98d9615d2fded22623b ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 4989adac848eb8f2fee8b98d9615d2fded22623b

[AArch64][SVE 13/32] Add an F_STRICT flag

SVE predicate operands can appear in three forms:

1. unsuffixed: "Pn"
2. with a predication type: "Pn/[ZM]"
3. with a size suffix: "Pn.[BHSD]"

No variation is allowed: unsuffixed operands cannot have a (redundant)
suffix, and the suffixes can never be dropped.  Unsuffixed Pn are used
in LDR and STR, but they are also used for Pg operands in cases where
the result is scalar and where there is therefore no choice to be made
between "merging" and "zeroing".  This means that some Pg operands have
suffixes and others don't.

It would be possible to use context-sensitive parsing to handle
this difference.  The tc-aarch64.c code would then raise an error
if the wrong kind of suffix is used for a particular instruction.

However, we get much more user-friendly error messages if we parse
all three forms for all SVE instructions and record the suffix as a
qualifier.  The normal qualifier matching code can then report cases
where the wrong kind of suffix is used.  This is a slight extension
of existing usage, which really only checks for the wrong choice of
suffix within a particular kind of suffix.

The only catch is a that a "NIL" entry in the qualifier list
specifically means "no suffix should be present" (case 1 above).
NIL isn't a wildcard here.  It also means that an instruction that
requires all-NIL qualifiers can fail to match (because a suffix was
supplied when it shouldn't have been); this requires a slight change
to find_best_match.

This patch adds an F_STRICT flag to select this behaviour.
The flag will be set for all SVE instructions.  The behaviour
for other instructions doesn't change.

include/
	* opcode/aarch64.h (F_STRICT): New flag.

opcodes/
	* aarch64-opc.c (match_operands_qualifier): Handle F_STRICT.

gas/
	* config/tc-aarch64.c (find_best_match): Simplify, allowing an
	instruction with all-NIL qualifiers to fail to match.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 14/32] Make aarch64_logical_immediate_p take an element size
@ 2016-09-21 21:23 sergiodj+buildbot
  2016-09-21 23:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 21:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42408347b86745fdbd4bec9ee3a6a3fee31c4dee ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 42408347b86745fdbd4bec9ee3a6a3fee31c4dee

[AArch64][SVE 14/32] Make aarch64_logical_immediate_p take an element size

SVE supports logical immediate operations on 8-bit, 16-bit and 32-bit
elements, treating them as aliases of operations on 64-bit elements in
which the immediate is replicated.  This patch therefore replaces the
"32-bit/64-bit" input to aarch64_logical_immediate_p with a more
general "number of bytes" input.

opcodes/
	* aarch64-opc.c (aarch64_logical_immediate_p): Replace is32
	with an esize parameter.
	(operand_general_constraint_met_p): Update accordingly.
	Fix misindented code.
	* aarch64-asm.c (aarch64_ins_limm): Update call to
	aarch64_logical_immediate_p.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 15/32] Add {insert, extract}_all_fields helpers
@ 2016-09-21 21:52 sergiodj+buildbot
  2016-09-22  0:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 21:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5464a6825e40e6d8ab2dd86c7ff5d65bedd64d4 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: b5464a6825e40e6d8ab2dd86c7ff5d65bedd64d4

[AArch64][SVE 15/32] Add {insert,extract}_all_fields helpers

Several of the SVE operands use the aarch64_operand fields array
to store the fields that make up the operand, rather than hard-coding
the names in the C code.  This patch adds helpers for inserting and
extracting those fields.

opcodes/
	* aarch64-asm.c: Include libiberty.h.
	(insert_fields): New function.
	(aarch64_ins_imm): Use it.
	* aarch64-dis.c (extract_fields): New function.
	(aarch64_ext_imm): Use it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 17/32] Add a prefix parameter to print_register_list
@ 2016-09-21 23:40 sergiodj+buildbot
  2016-09-22  3:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 23:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a7f0c1b5ae35d041886855ac7ca9b9533e8788a ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 8a7f0c1b5ae35d041886855ac7ca9b9533e8788a

[AArch64][SVE 17/32] Add a prefix parameter to print_register_list

This patch generalises the interface to print_register_list so
that it can print register lists involving SVE z registers as
well as AdvSIMD v ones.

opcodes/
	* aarch64-opc.c (print_register_list): Add a prefix parameter.
	(aarch64_print_operand): Update accordingly.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 18/32] Tidy definition of aarch64-opc.c:int_reg
@ 2016-09-22  0:34 sergiodj+buildbot
  2016-09-22  5:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72e9f31937f063ed6f5991a2b8c00068fa2dc8fc ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 72e9f31937f063ed6f5991a2b8c00068fa2dc8fc

[AArch64][SVE 18/32] Tidy definition of aarch64-opc.c:int_reg

Use a macro to define 31 regular registers followed by a supplied
value for 0b11111.  The SVE code will also use this for vector base
and offset registers.

opcodes/
	* aarch64-opc.c (BANK): New macro.
	(R32, R64): Take a register number as argument
	(int_reg): Use BANK.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 19/32] Refactor address-printing code
@ 2016-09-22  1:25 sergiodj+buildbot
  2016-09-22  6:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  1:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01dbfe4c0e2b832c6b1076e8d373b162e2faa376 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 01dbfe4c0e2b832c6b1076e8d373b162e2faa376

[AArch64][SVE 19/32] Refactor address-printing code

SVE adds addresses in which the base or offset are vector registers.
The addresses otherwise have the same kind of form as normal AArch64
addresses, including things like SXTW with or without a shift, UXTW
with or without a shift, and LSL.

This patch therefore refactors the address-printing code so that it
can cope with both scalar and vector registers.

opcodes/
	* aarch64-opc.c (get_offset_int_reg_name): New function.
	(print_immediate_offset_address): Likewise.
	(print_register_offset_address): Take the base and offset
	registers as parameters.
	(aarch64_print_operand): Update caller accordingly.  Use
	print_immediate_offset_address.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 20/32] Add support for tied operands
@ 2016-09-22  2:10 sergiodj+buildbot
  2016-09-22  8:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  2:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c608d6b62f9164203685ab125b4b3ad113eb26e ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 0c608d6b62f9164203685ab125b4b3ad113eb26e

[AArch64][SVE 20/32] Add support for tied operands

SVE has some instructions in which the same register appears twice
in the assembly string, once as an input and once as an output.
This patch adds a general mechanism for that.

The patch needs to add new information to the instruction entries.
One option would have been to extend the flags field of the opcode
to 64 bits (since we already rely on 64-bit integers being available
on the host).  However, the *_INSN macros mean that it's easy to add
new information as top-level fields without affecting the existing
table entries too much.  Going for that option seemed to give slightly
neater code.

include/
	* opcode/aarch64.h (aarch64_opcode): Add a tied_operand field.
	(AARCH64_OPDE_UNTIED_OPERAND): New aarch64_operand_error_kind.

opcodes/
	* aarch64-tbl.h (CORE_INSN, __FP_INSN, SIMD_INSN, CRYP_INSN)
	(_CRC_INSN, _LSE_INSN, _LOR_INSN, RDMA_INSN, FP16_INSN, SF16_INSN)
	(V8_2_INSN, aarch64_opcode_table): Initialize tied_operand field.
	* aarch64-opc.c (aarch64_match_operands_constraint): Check for
	tied operands.

gas/
	* config/tc-aarch64.c (output_operand_error_record): Handle
	AARCH64_OPDE_UNTIED_OPERAND.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 21/32] Add Zn and Pn registers
@ 2016-09-22  2:34 sergiodj+buildbot
  2016-09-22 10:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  2:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f11ad6bc0fc44b94c6970115bb6984b497b967e7 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: f11ad6bc0fc44b94c6970115bb6984b497b967e7

[AArch64][SVE 21/32] Add Zn and Pn registers

This patch adds the Zn and Pn registers, and associated fields and
operands.

include/
	* opcode/aarch64.h (AARCH64_OPND_CLASS_SVE_REG): New
	aarch64_operand_class.
	(AARCH64_OPND_CLASS_PRED_REG): Likewise.
	(AARCH64_OPND_SVE_Pd, AARCH64_OPND_SVE_Pg3, AARCH64_OPND_SVE_Pg4_5)
	(AARCH64_OPND_SVE_Pg4_10, AARCH64_OPND_SVE_Pg4_16)
	(AARCH64_OPND_SVE_Pm, AARCH64_OPND_SVE_Pn, AARCH64_OPND_SVE_Pt)
	(AARCH64_OPND_SVE_Za_5, AARCH64_OPND_SVE_Za_16, AARCH64_OPND_SVE_Zd)
	(AARCH64_OPND_SVE_Zm_5, AARCH64_OPND_SVE_Zm_16, AARCH64_OPND_SVE_Zn)
	(AARCH64_OPND_SVE_Zn_INDEX, AARCH64_OPND_SVE_ZnxN)
	(AARCH64_OPND_SVE_Zt, AARCH64_OPND_SVE_ZtxN): New aarch64_opnds.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for new SVE operands.
	* aarch64-opc.h (FLD_SVE_Pd, FLD_SVE_Pg3, FLD_SVE_Pg4_5)
	(FLD_SVE_Pg4_10, FLD_SVE_Pg4_16, FLD_SVE_Pm, FLD_SVE_Pn, FLD_SVE_Pt)
	(FLD_SVE_Za_5, FLD_SVE_Za_16, FLD_SVE_Zd, FLD_SVE_Zm_5, FLD_SVE_Zm_16)
	(FLD_SVE_Zn, FLD_SVE_Zt, FLD_SVE_tzsh): New aarch64_field_kinds.
	* aarch64-opc.c (fields): Add corresponding entries here.
	(operand_general_constraint_met_p): Check that SVE register lists
	have the correct length.  Check the ranges of SVE index registers.
	Check for cases where p8-p15 are used in 3-bit predicate fields.
	(aarch64_print_operand): Handle the new SVE operands.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_index, ins_sve_reglist): New inserters.
	* aarch64-asm.c (aarch64_ins_sve_index): New function.
	(aarch64_ins_sve_reglist): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_index, ext_sve_reglist): New extractors.
	* aarch64-dis.c (aarch64_ext_sve_index): New function.
	(aarch64_ext_sve_reglist): Likewise.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (NTA_HASVARWIDTH): New macro.
	(AARCH64_REG_TYPES): Add ZN and PN.
	(get_reg_expected_msg): Handle them.
	(parse_vector_type_for_operand): Add a reg_type parameter.
	Skip the width for Zn and Pn registers.
	(parse_typed_reg): Extend vector handling to Zn and Pn.  Update the
	call to parse_vector_type_for_operand.  Set HASVARTYPE for Zn and Pn,
	expecting the width to be 0.
	(parse_vector_reg_list): Restrict error about [BHSD]nn operands to
	REG_TYPE_VN.
	(vectype_to_qualifier): Use S_[BHSD] qualifiers for NTA_HASVARWIDTH.
	(parse_operands): Handle the new Zn and Pn operands.
	(REGSET16): New macro, split out from...
	(REGSET31): ...here.
	(reg_names): Add Zn and Pn entries.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 22/32] Add qualifiers for merging and zeroing predication
@ 2016-09-22  4:21 sergiodj+buildbot
  2016-09-22 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  4:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d50c751e00b5336b4604b92271ab84615fdb0d27 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: d50c751e00b5336b4604b92271ab84615fdb0d27

[AArch64][SVE 22/32] Add qualifiers for merging and zeroing predication

This patch adds qualifiers to represent /z and /m suffixes on
predicate registers.

include/
	* opcode/aarch64.h (AARCH64_OPND_QLF_P_Z): New aarch64_opnd_qualifier.
	(AARCH64_OPND_QLF_P_M): Likewise.

opcodes/
	* aarch64-opc.c (aarch64_opnd_qualifiers): Add entries for
	AARCH64_OPND_QLF_P_[ZM].
	(aarch64_print_operand): Print /z and /m where appropriate.

gas/
	* config/tc-aarch64.c (vector_el_type): Add NT_zero and NT_merge.
	(parse_vector_type_for_operand): Assert that the skipped character
	is a '.'.
	(parse_predication_for_operand): New function.
	(parse_typed_reg): Parse /z and /m suffixes for predicate registers.
	(vectype_to_qualifier): Handle NT_zero and NT_merge.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 23/32] Add SVE pattern and prfop operands
@ 2016-09-22  4:41 sergiodj+buildbot
  2016-09-22 13:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 245d2e3fe8d9ff35c65ed1329609fb7e59034877 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 245d2e3fe8d9ff35c65ed1329609fb7e59034877

[AArch64][SVE 23/32] Add SVE pattern and prfop operands

The SVE instructions have two enumerated operands: one to select a
vector pattern and another to select a prefetch operation.  The latter
is a cut-down version of the base AArch64 prefetch operation.

Both types of operand can also be specified as raw enum values such as #31.
Reserved values can only be specified this way.

If it hadn't been for the pattern operand, I would have been tempted
to use the existing parsing for prefetch operations and add extra
checks for SVE.  However, since the patterns needed new enum parsing
code anyway, it seeemed cleaner to reuse it for the prefetches too.

Because of the small number of enum values, I don't think we'd gain
anything by using hash tables.

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_PATTERN): New aarch64_opnd.
	(AARCH64_OPND_SVE_PRFOP): Likewise.
	(aarch64_sve_pattern_array): Declare.
	(aarch64_sve_prfop_array): Likewise.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for
	AARCH64_OPND_SVE_PATTERN and AARCH64_OPND_SVE_PRFOP.
	* aarch64-opc.h (FLD_SVE_pattern): New aarch64_field_kind.
	(FLD_SVE_prfop): Likewise.
	* aarch64-opc.c: Include libiberty.h.
	(aarch64_sve_pattern_array): New variable.
	(aarch64_sve_prfop_array): Likewise.
	(fields): Add entries for FLD_SVE_pattern and FLD_SVE_prfop.
	(aarch64_print_operand): Handle AARCH64_OPND_SVE_PATTERN and
	AARCH64_OPND_SVE_PRFOP.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Likewise.
	* aarch64-opc-2.c: Likewise.

gas/
	* config/tc-aarch64.c (parse_enum_string): New function.
	(po_enum_or_fail): New macro.
	(parse_operands): Handle AARCH64_OPND_SVE_PATTERN and
	AARCH64_OPND_SVE_PRFOP.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 24/32] Add AARCH64_OPND_SVE_PATTERN_SCALED
@ 2016-09-22  5:23 sergiodj+buildbot
  2016-09-22 15:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  5:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2442d8466e221ba6cf4ec4bd2a819fdcb1e5ea7e ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 2442d8466e221ba6cf4ec4bd2a819fdcb1e5ea7e

[AArch64][SVE 24/32] Add AARCH64_OPND_SVE_PATTERN_SCALED

Some SVE instructions count the number of elements in a given vector
pattern and allow a scale factor of [1, 16] to be applied to the result.
This scale factor is written ", MUL #n", where "MUL" is a new operator.
E.g.:

	UQINCD	X0, POW2, MUL #2

This patch adds support for this kind of operand.

All existing operators were shifts of some kind, so there was a natural
range of [0, 63] regardless of context.  This was then narrowered further
by later checks (e.g. to [0, 31] when used for 32-bit values).

In contrast, MUL doesn't really have a natural context-independent range.
Rather than pick one arbitrarily, it seemed better to make the "shift"
amount a full 64-bit value and leave the range test to the usual
operand-checking code.  I've rearranged the fields of aarch64_opnd_info
so that this doesn't increase the size of the structure (although I don't
think its size is critical anyway).

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_PATTERN_SCALED): New
	aarch64_opnd.
	(AARCH64_MOD_MUL): New aarch64_modifier_kind.
	(aarch64_opnd_info): Make shifter.amount an int64_t and
	rearrange the fields.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add an entry for
	AARCH64_OPND_SVE_PATTERN_SCALED.
	* aarch64-opc.h (FLD_SVE_imm4): New aarch64_field_kind.
	* aarch64-opc.c (fields): Add a corresponding entry.
	(set_multiplier_out_of_range_error): New function.
	(aarch64_operand_modifiers): Add entry for AARCH64_MOD_MUL.
	(operand_general_constraint_met_p): Handle
	AARCH64_OPND_SVE_PATTERN_SCALED.
	(print_register_offset_address): Use PRIi64 to print the
	shift amount.
	(aarch64_print_operand): Likewise.  Handle
	AARCH64_OPND_SVE_PATTERN_SCALED.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_scale): New inserter.
	* aarch64-asm.c (aarch64_ins_sve_scale): New function.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_scale): New inserter.
	* aarch64-dis.c (aarch64_ext_sve_scale): New function.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (SHIFTED_MUL): New parse_shift_mode.
	(parse_shift): Handle it.  Reject AARCH64_MOD_MUL for all other
	shift modes.  Skip range tests for AARCH64_MOD_MUL.
	(process_omitted_operand): Handle AARCH64_OPND_SVE_PATTERN_SCALED.
	(parse_operands): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 26/32] Add SVE MUL VL addressing modes
@ 2016-09-22  7:02 sergiodj+buildbot
  2016-09-22 19:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  7:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98907a704908c5877d929c57b2ddb2e5f899d9a9 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 98907a704908c5877d929c57b2ddb2e5f899d9a9

[AArch64][SVE 26/32] Add SVE MUL VL addressing modes

This patch adds support for addresses of the form:

       [<base>, #<offset>, MUL VL]

This involves adding a new AARCH64_MOD_MUL_VL modifier, which is
why I split it out from the other addressing modes.

For LD2, LD3 and LD4, the offset must be a multiple of the structure
size, so for LD3 the possible values are 0, 3, 6, ....  The patch
therefore extends value_aligned_p to handle non-power-of-2 alignments.

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_ADDR_RI_S4xVL): New aarch64_opnd.
	(AARCH64_OPND_SVE_ADDR_RI_S4x2xVL, AARCH64_OPND_SVE_ADDR_RI_S4x3xVL)
	(AARCH64_OPND_SVE_ADDR_RI_S4x4xVL, AARCH64_OPND_SVE_ADDR_RI_S6xVL)
	(AARCH64_OPND_SVE_ADDR_RI_S9xVL): Likewise.
	(AARCH64_MOD_MUL_VL): New aarch64_modifier_kind.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for new MUL VL
	operands.
	* aarch64-opc.c (aarch64_operand_modifiers): Initialize
	the AARCH64_MOD_MUL_VL entry.
	(value_aligned_p): Cope with non-power-of-two alignments.
	(operand_general_constraint_met_p): Handle the new MUL VL addresses.
	(print_immediate_offset_address): Likewise.
	(aarch64_print_operand): Likewise.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_addr_ri_s4xvl, ins_sve_addr_ri_s6xvl)
	(ins_sve_addr_ri_s9xvl): New inserters.
	* aarch64-asm.c (aarch64_ins_sve_addr_ri_s4xvl): New function.
	(aarch64_ins_sve_addr_ri_s6xvl): Likewise.
	(aarch64_ins_sve_addr_ri_s9xvl): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_addr_ri_s4xvl, ext_sve_addr_ri_s6xvl)
	(ext_sve_addr_ri_s9xvl): New extractors.
	* aarch64-dis.c (aarch64_ext_sve_addr_reg_mul_vl): New function.
	(aarch64_ext_sve_addr_ri_s4xvl): Likewise.
	(aarch64_ext_sve_addr_ri_s6xvl): Likewise.
	(aarch64_ext_sve_addr_ri_s9xvl): Likewise.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (SHIFTED_NONE, SHIFTED_MUL_VL): New
	parse_shift_modes.
	(parse_shift): Handle SHIFTED_MUL_VL.
	(parse_address_main): Add an imm_shift_mode parameter.
	(parse_address, parse_sve_address): Update accordingly.
	(parse_operands): Handle MUL VL addressing modes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 27/32] Add SVE integer immediate operands
@ 2016-09-22  8:06 sergiodj+buildbot
  2016-09-22 19:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  8:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e950b3453948830c5ce9c2f70d114d0b38a4b4ac ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: e950b3453948830c5ce9c2f70d114d0b38a4b4ac

[AArch64][SVE 27/32] Add SVE integer immediate operands

This patch adds the new SVE integer immediate operands.  There are
three kinds:

- simple signed and unsigned ranges, but with new widths and positions.

- 13-bit logical immediates.  These have the same form as in base AArch64,
  but at a different bit position.

  In the case of the "MOV Zn.<T>, #<limm>" alias of DUPM, the logical
  immediate <limm> is not allowed to be a valid DUP immediate, since DUP
  is preferred over DUPM for constants that both instructions can handle.

- a new 9-bit arithmetic immediate, of the form "<imm8>{, LSL #8}".
  In some contexts the operand is signed and in others it's unsigned.
  As an extension, we allow shifted immediates to be written as a single
  integer, e.g. "#256" is equivalent to "#1, LSL #8".  We also use the
  shiftless form as the preferred disassembly, except for the special
  case of "#0, LSL #8" (a redundant encoding of 0).

include/
	* opcode/aarch64.h (AARCH64_OPND_SIMM5): New aarch64_opnd.
	(AARCH64_OPND_SVE_AIMM, AARCH64_OPND_SVE_ASIMM)
	(AARCH64_OPND_SVE_INV_LIMM, AARCH64_OPND_SVE_LIMM)
	(AARCH64_OPND_SVE_LIMM_MOV, AARCH64_OPND_SVE_SHLIMM_PRED)
	(AARCH64_OPND_SVE_SHLIMM_UNPRED, AARCH64_OPND_SVE_SHRIMM_PRED)
	(AARCH64_OPND_SVE_SHRIMM_UNPRED, AARCH64_OPND_SVE_SIMM5)
	(AARCH64_OPND_SVE_SIMM5B, AARCH64_OPND_SVE_SIMM6)
	(AARCH64_OPND_SVE_SIMM8, AARCH64_OPND_SVE_UIMM3)
	(AARCH64_OPND_SVE_UIMM7, AARCH64_OPND_SVE_UIMM8)
	(AARCH64_OPND_SVE_UIMM8_53): Likewise.
	(aarch64_sve_dupm_mov_immediate_p): Declare.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for the new SVE
	integer immediate operands.
	* aarch64-opc.h (FLD_SVE_immN, FLD_SVE_imm3, FLD_SVE_imm5)
	(FLD_SVE_imm5b, FLD_SVE_imm7, FLD_SVE_imm8, FLD_SVE_imm9)
	(FLD_SVE_immr, FLD_SVE_imms, FLD_SVE_tszh): New aarch64_field_kinds.
	* aarch64-opc.c (fields): Add corresponding entries.
	(operand_general_constraint_met_p): Handle the new SVE integer
	immediate operands.
	(aarch64_print_operand): Likewise.
	(aarch64_sve_dupm_mov_immediate_p): New function.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_inv_limm, ins_sve_aimm, ins_sve_asimm)
	(ins_sve_limm_mov, ins_sve_shlimm, ins_sve_shrimm): New inserters.
	* aarch64-asm.c (aarch64_ins_limm_1): New function, split out from...
	(aarch64_ins_limm): ...here.
	(aarch64_ins_inv_limm): New function.
	(aarch64_ins_sve_aimm): Likewise.
	(aarch64_ins_sve_asimm): Likewise.
	(aarch64_ins_sve_limm_mov): Likewise.
	(aarch64_ins_sve_shlimm): Likewise.
	(aarch64_ins_sve_shrimm): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_inv_limm, ext_sve_aimm, ext_sve_asimm)
	(ext_sve_limm_mov, ext_sve_shlimm, ext_sve_shrimm): New extractors.
	* aarch64-dis.c (decode_limm): New function, split out from...
	(aarch64_ext_limm): ...here.
	(aarch64_ext_inv_limm): New function.
	(decode_sve_aimm): Likewise.
	(aarch64_ext_sve_aimm): Likewise.
	(aarch64_ext_sve_asimm): Likewise.
	(aarch64_ext_sve_limm_mov): Likewise.
	(aarch64_top_bit): Likewise.
	(aarch64_ext_sve_shlimm): Likewise.
	(aarch64_ext_sve_shrimm): Likewise.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (parse_operands): Handle the new SVE integer
	immediate operands.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 28/32] Add SVE FP immediate operands
@ 2016-09-22  8:08 sergiodj+buildbot
  2016-09-22 22:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  8:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 165d4950855493dd904a7996e7fcf58880d54219 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 165d4950855493dd904a7996e7fcf58880d54219

[AArch64][SVE 28/32] Add SVE FP immediate operands

This patch adds support for the new SVE floating-point immediate
operands.  One operand uses the same 8-bit encoding as base AArch64,
but in a different position.  The others use a single bit to select
between two values.

One of the single-bit operands is a choice between 0 and 1, where 0
is not a valid 8-bit encoding.  I think the cleanest way of handling
these single-bit immediates is therefore to use the IEEE float encoding
itself as the immediate value and select between the two possible values
when encoding and decoding.

As described in the covering note for the patch that added F_STRICT,
we get better error messages by accepting unsuffixed vector registers
and leaving the qualifier matching code to report an error.  This means
that we carry on parsing the other operands, and so can try to parse FP
immediates for invalid instructions like:

	fcpy	z0, #2.5

In this case there is no suffix to tell us whether the immediate should
be treated as single or double precision.  Again, we get better error
messages by picking one (arbitrary) immediate size and reporting an error
for the missing suffix later.

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_FPIMM8): New aarch64_opnd.
	(AARCH64_OPND_SVE_I1_HALF_ONE, AARCH64_OPND_SVE_I1_HALF_TWO)
	(AARCH64_OPND_SVE_I1_ZERO_ONE): Likewise.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for the new SVE FP
	immediate operands.
	* aarch64-opc.h (FLD_SVE_i1): New aarch64_field_kind.
	* aarch64-opc.c (fields): Add corresponding entry.
	(operand_general_constraint_met_p): Handle the new SVE FP immediate
	operands.
	(aarch64_print_operand): Likewise.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_float_half_one, ins_sve_float_half_two)
	(ins_sve_float_zero_one): New inserters.
	* aarch64-asm.c (aarch64_ins_sve_float_half_one): New function.
	(aarch64_ins_sve_float_half_two): Likewise.
	(aarch64_ins_sve_float_zero_one): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_float_half_one, ext_sve_float_half_two)
	(ext_sve_float_zero_one): New extractors.
	* aarch64-dis.c (aarch64_ext_sve_float_half_one): New function.
	(aarch64_ext_sve_float_half_two): Likewise.
	(aarch64_ext_sve_float_zero_one): Likewise.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (double_precision_operand_p): New function.
	(parse_operands): Use it to calculate the dp_p input to
	parse_aarch64_imm_float.  Handle the new SVE FP immediate operands.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64][SVE 30/32] Add SVE instruction classes
@ 2016-09-22  9:31 sergiodj+buildbot
  2016-09-23  3:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  9:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 116b60193779ac65a29fb3688b753527980cb3e7 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 116b60193779ac65a29fb3688b753527980cb3e7

[AArch64][SVE 30/32] Add SVE instruction classes

The main purpose of the SVE aarch64_insn_classes is to describe how
an index into an aarch64_opnd_qualifier_seq_t is represented in the
instruction encoding.  Other instructions usually use flags for this
information, but (a) we're running out of those and (b) the iclass
would otherwise be unused for SVE.

include/
	* opcode/aarch64.h (sve_cpy, sve_index, sve_limm, sve_misc)
	(sve_movprfx, sve_pred_zm, sve_shift_pred, sve_shift_unpred)
	(sve_size_bhs, sve_size_bhsd, sve_size_hsd, sve_size_sd): New
	aarch64_insn_classes.

opcodes/
	* aarch64-opc.h (FLD_SVE_M_4, FLD_SVE_M_14, FLD_SVE_M_16)
	(FLD_SVE_sz, FLD_SVE_tsz, FLD_SVE_tszl_8, FLD_SVE_tszl_19): New
	aarch64_field_kinds.
	* aarch64-opc.c (fields): Add corresponding entries.
	* aarch64-asm.c (aarch64_get_variant): New function.
	(aarch64_encode_variant_using_iclass): Likewise.
	(aarch64_opcode_encode): Call it.
	* aarch64-dis.c (aarch64_decode_variant_using_iclass): New function.
	(aarch64_opcode_decode): Call it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Add SVE condition codes
@ 2016-09-22 11:51 sergiodj+buildbot
  2016-09-23  7:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb7eff5206e4795ac79c177a80fe9f4630aaf730 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: bb7eff5206e4795ac79c177a80fe9f4630aaf730

[AArch64] Add SVE condition codes

SVE defines new names for existing NZCV conditions, to reflect the
result of instructions like PTEST.  This patch adds support for these
names.

The patch also adds comments to the disassembly output to show the
alternative names of a condition code.  For example:

	cinv	x0, x1, cc

becomes:

     	cinv	x0, x1, cc  // cc = lo, ul, last

and:

	b.cc	f0 <...>

becomes:

     	b.cc	f0 <...>  // b.lo, b.ul, b.last

Doing this for the SVE names follows the practice recommended by the
SVE specification and is definitely useful when reading SVE code.
If the feeling is that it's too distracting elsewhere, we could add
an option to turn it off.

include/
	* opcode/aarch64.h (aarch64_cond): Bump array size to 4.

opcodes/
	* aarch64-dis.c (remove_dot_suffix): New function, split out from...
	(print_mnemonic_name): ...here.
	(print_comment): New function.
	(print_aarch64_insn): Call it.
	* aarch64-opc.c (aarch64_conds): Add SVE names.
	(aarch64_print_operand): Print alternative condition names in
	a comment.

gas/
	* config/tc-aarch64.c (opcode_lookup): Search for the end of
	a condition name, rather than assuming that it will have exactly
	2 characters.
	(parse_operands): Likewise.
	* testsuite/gas/aarch64/alias.d: Add new condition-code comments
	to the expected output.
	* testsuite/gas/aarch64/beq_1.d: Likewise.
	* testsuite/gas/aarch64/float-fp16.d: Likewise.
	* testsuite/gas/aarch64/int-insns.d: Likewise.
	* testsuite/gas/aarch64/no-aliases.d: Likewise.
	* testsuite/gas/aarch64/programmer-friendly.d: Likewise.
	* testsuite/gas/aarch64/reloc-insn.d: Likewise.
	* testsuite/gas/aarch64/b_c_1.d, testsuite/gas/aarch64/b_c_1.s:
	New test.

ld/
	* testsuite/ld-aarch64/emit-relocs-280.d: Match branch comments.
	* testsuite/ld-aarch64/weak-undefined.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Use "must" rather than "should" in error messages
@ 2016-09-22 12:08 sergiodj+buildbot
  2016-09-23  7:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 12:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab3b8fcfdb06695d27eaec4eedb019ada4a5713e ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: ab3b8fcfdb06695d27eaec4eedb019ada4a5713e

[AArch64] Use "must" rather than "should" in error messages

One of the review comments from the SVE series was that it would
be better to use "must" rather than "should" in error messages.
I think this patch fixes all cases in the AArch64 code.
It also uses "must be" instead of "expected to be".

opcodes/
	* aarch64-opc.c (operand_general_constraint_met_p): Use "must be"
	rather than "should be" or "expected to be" in error messages.

gas/
	* config/tc-aarch64.c (output_operand_error_record): Use "must be"
	rather than "should be" or "expected to be" in error messages.
	(parse_operands): Likewise.
	* testsuite/gas/aarch64/diagnostic.l: Likewise.
	* testsuite/gas/aarch64/legacy_reg_names.l: Likewise.
	* testsuite/gas/aarch64/sve-invalid.l: Likewise.
	* testsuite/gas/aarch64/sve-reg-diagnostic.l: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Print spaces after commas in addresses
@ 2016-09-22 12:46 sergiodj+buildbot
  2016-09-23  8:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad43e107eb233dcef8e76da6328aa4e4d74afd84 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: ad43e107eb233dcef8e76da6328aa4e4d74afd84

[AArch64] Print spaces after commas in addresses

I got an off-list request to make the AArch64 disassembler print
spaces after commas in addresses.  This patch does that.

The same code is used to print operands in "did you mean" errors,
so to keep things consistent, the patch also prints spaces between
operands in those messages.

opcodes/
	* aarch64-opc.c (print_immediate_offset_address): Print spaces
	after commas in addresses.
	(aarch64_print_operand): Likewise.

gas/
	* config/tc-aarch64.c (print_operands): Print spaces between
	operands.
	* testsuite/gas/aarch64/ilp32-basic.d: Expect spaces after ","
	in addresses.
	* testsuite/gas/aarch64/ldst-reg-imm-post-ind.d: Likewise.
	* testsuite/gas/aarch64/ldst-reg-imm-pre-ind.d: Likewise.
	* testsuite/gas/aarch64/ldst-reg-pair.d: Likewise.
	* testsuite/gas/aarch64/ldst-reg-reg-offset.d: Likewise.
	* testsuite/gas/aarch64/ldst-reg-uns-imm.d: Likewise.
	* testsuite/gas/aarch64/ldst-reg-unscaled-imm.d: Likewise.
	* testsuite/gas/aarch64/reloc-insn.d: Likewise.
	* testsuite/gas/aarch64/sve.d: Likewise.
	* testsuite/gas/aarch64/symbol.d: Likewise.
	* testsuite/gas/aarch64/system.d: Likewise.
	* testsuite/gas/aarch64/tls-desc.d: Likewise.
	* testsuite/gas/aarch64/sve-invalid.l: Expect spaces after ","
	in suggested alternatives.
	* testsuite/gas/aarch64/verbose-error.l: Likewise.

ld/
	* testsuite/ld-aarch64/emit-relocs-28.d: Expect spaces after ","
	in addresses.
	* testsuite/ld-aarch64/emit-relocs-301-be.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-301.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-302-be.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-302.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-310-be.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-310.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-313.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-515-be.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-515.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-516-be.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-516.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-531.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-532.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-533.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-534.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-535.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-536.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-537.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-538.d: Likewise.
	* testsuite/ld-aarch64/erratum835769.d: Likewise.
	* testsuite/ld-aarch64/erratum843419.d: Likewise.
	* testsuite/ld-aarch64/farcall-b-plt.d: Likewise.
	* testsuite/ld-aarch64/farcall-bl-plt.d: Likewise.
	* testsuite/ld-aarch64/gc-plt-relocs.d: Likewise.
	* testsuite/ld-aarch64/ifunc-21.d: Likewise.
	* testsuite/ld-aarch64/ifunc-7c.d: Likewise.
	* testsuite/ld-aarch64/tls-desc-ie.d: Likewise.
	* testsuite/ld-aarch64/tls-large-desc-be.d: Likewise.
	* testsuite/ld-aarch64/tls-large-desc.d: Likewise.
	* testsuite/ld-aarch64/tls-large-ie-be.d: Likewise.
	* testsuite/ld-aarch64/tls-large-ie.d: Likewise.
	* testsuite/ld-aarch64/tls-relax-all.d: Likewise.
	* testsuite/ld-aarch64/tls-relax-gd-ie.d: Likewise.
	* testsuite/ld-aarch64/tls-relax-gdesc-ie-2.d: Likewise.
	* testsuite/ld-aarch64/tls-relax-gdesc-ie.d: Likewise.
	* testsuite/ld-aarch64/tls-relax-large-desc-ie-be.d: Likewise.
	* testsuite/ld-aarch64/tls-relax-large-desc-ie.d: Likewise.
	* testsuite/ld-aarch64/tls-tiny-desc.d: Likewise.
	* testsuite/ld-aarch64/tls-tiny-gd.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix build breakage from commit 6ec2b2
@ 2016-09-22 23:04 sergiodj+buildbot
  2016-09-23 15:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 23:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de6784544abc97d5e396cb1e83eda1ae09f63d40 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: de6784544abc97d5e396cb1e83eda1ae09f63d40

Fix build breakage from commit 6ec2b2

I was notified by buildbot that my patch (commit 6ec2b2) has broken the build
on x86_64:

../../binutils-gdb/gdb/rs6000-tdep.c: In function int ppc_process_record_op31(gdbarch*, regcache*, CORE_ADDR, uint32_t):
../../binutils-gdb/gdb/rs6000-tdep.c:4705:50: error: cannot convert CORE_ADDR* {aka long unsigned int*} to ULONGEST* {aka long long unsigned int*} for argument 3 to register_status regcache_raw_read_unsigned(regcache*, int, ULONGEST*)
         tdep->ppc_gp0_regnum + PPC_RA (insn), &ea);
                                                  ^
../../binutils-gdb/gdb/rs6000-tdep.c:4718:50: error: cannot convert CORE_ADDR* {aka long unsigned int*} to ULONGEST* {aka long long unsigned int*} for argument 3 to register_status regcache_raw_read_unsigned(regcache*, int, ULONGEST*)
         tdep->ppc_gp0_regnum + PPC_RA (insn), &ea);
                                                  ^
The patch below should fix it.

gdb/ChangeLog:
2016-09-22  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (ppc_process_record_op31): Fix
	regcache_raw_read_unsigned call using the correct parameter type.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Close gdbserver in mi_gdb_exit
@ 2016-09-23  0:46 sergiodj+buildbot
  2016-09-23 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-23  0:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f73842fc847e297fd44542de9601a84b4d6b28d8 ***

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

Close gdbserver in mi_gdb_exit

In commit 6423214f (testsuite: Don't use expect_background to reap
gdbserver), we override gdb_exit in lib/gdbserver-support.exp, so
that we can close gdbserver first.  However, we don't close gdbserver
in mi_gdb_exit.  This makes a problem in my aarch64 mulit-arch testing,
in which I run some mi tests, mi-watch.exp for example, in different
variations (aarch64 and arm),

Schedule of variations:
    junor0-2
    junor0-2-arm/-marm
    junor0-2-arm/-mthumb

When the test is done in the first variation (aarch64), test case is
recompiled for arm, but GDBserver with aarch64 program is still
running.  When the second variation is started, GDB loads arm program,
but GDBserver still loads aarch64 program because the old GDBserver
process is using it.  We'll get,

47-target-select remote junor0-2:2350^M
&"warning: Selected architecture arm is not compatible with reported target architecture aarch64\n"^M
&"warning: Architecture rejected target-supplied description\n"

This patch fixes this problem by closing GDBserver in mi_gdb_exit.

gdb/testsuite:

2016-09-22  Yao Qi  <yao.qi@linaro.org>

	* lib/gdbserver-support.exp: Rename mi_gdb_exit.
	(gdb_exit): Rename it to ...
	(gdbserver_gdb_exit): ...  Close GDBserver.
	(gdb_exit): New proc, call gdbserver_gdb_exit.
	(mi_gdb_exit): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Delete relocations associatesd with deleted exidx entries.
@ 2016-09-23 19:06 sergiodj+buildbot
  2016-09-23 20:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-23 19:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5025eb7c0d87b01507116353b5d63b163d7add3d ***

Author: Akihiko Odaki <akihiko.odaki.4i@stu.hosei.ac.jp>
Branch: master
Commit: 5025eb7c0d87b01507116353b5d63b163d7add3d

Delete relocations associatesd with deleted exidx entries.

	PR ld/20595
ld	* testsuite/ld-arm/unwind-4.d: Add -q option to linker command
	line and -r option to objdump command line.  Match emitted relocs
	to make sure that superflous relocs are not generated.

bfd	* elf-bfd.h (struct elf_backend_data): Add
	elf_backend_count_output_relocs callback to count relocations in
	the final output.
	* elf-arm.c (elf32_arm_add_relocation): Deleted.
	(elf32_arm_write_section): Move additional relocation to emit_relocs.
	(elf32_arm_count_output_relocs): New function.
	(emit_relocs): New function.
	(elf32_arm_emit_relocs): New function.
	(elf32_arm_vxworks_emit_relocs): New function.
	(elf_backend_emit_relocs): Updated to use the new functions.
	(elf_backend_count_output_relocs): New define.
	* bfd/elflink.c (bfd_elf_final_link): Do not add additional_reloc_count
	to the relocation count.
	(_bfd_elf_link_size_reloc_section): Use callback to count the
	relocations which will be in output.
	(_bfd_elf_default_count_output_relocs): New function.
	* bfd/elfxx-target.h (elf_backend_count_output_relocs): New define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Replace operator new / operator new[]
@ 2016-09-23 20:08 sergiodj+buildbot
  2016-09-23 21:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-23 20:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 503b1c39dc801389f7ae510fb1f7ee1e533b67ac ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 503b1c39dc801389f7ae510fb1f7ee1e533b67ac

gdb: Replace operator new / operator new[]

If xmalloc fails allocating memory, usually because something tried a
huge allocation, like xmalloc(-1) or some such, GDB asks the user what
to do:

  .../src/gdb/utils.c:1079: internal-error: virtual memory exhausted.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)

If the user says "n", that throws a QUIT exception, which is caught by
one of the multiple CATCH(RETURN_MASK_ALL) blocks somewhere up the
stack.

The default implementations of operator new / operator new[] call
malloc directly, and on memory allocation failure throw
std::bad_alloc.  Currently, if that happens, since nothing catches it,
the exception escapes out of main, and GDB aborts from unhandled
exception.

This patch replaces the default operator new variants with versions
that, just like xmalloc:

 #1 - Raise an internal-error on memory allocation failure.

 #2 - Throw a QUIT gdb_exception, so that the exact same CATCH blocks
      continue handling memory allocation problems.

A minor complication of #2 is that operator new can _only_ throw
std::bad_alloc, or something that extends it:

  void* operator new (std::size_t size) throw (std::bad_alloc);

That means that if we let a gdb QUIT exception escape from within
operator new, the C++ runtime aborts due to unexpected exception
thrown.

So to bridge the gap, this patch adds a new gdb_quit_bad_alloc
exception type that inherits both std::bad_alloc and gdb_exception,
and throws _that_.

If we decide that we should be catching memory allocation errors in
fewer places than all the places we currently catch them (everywhere
we use RETURN_MASK_ALL currently), then we could change operator new
to throw plain std::bad_alloc then.  But I'm considering such a change
as separate matter from this one -- it'd make sense to do the same to
xmalloc at the same time, for instance.

Meanwhile, this allows using new/new[] instead of xmalloc/XNEW/etc.
without losing the "virtual memory exhausted" internal-error
safeguard.

Tested on x86_64 Fedora 23.

gdb/ChangeLog:
2016-09-23  Pedro Alves  <palves@redhat.com>

	* Makefile.in (SFILES): Add common/new-op.c.
	(COMMON_OBS): Add common/new-op.o.
	(new-op.o): New rule.
	* common/common-exceptions.h: Include <new>.
	(struct gdb_quit_bad_alloc): New type.
	* common/new-op.c: New file.

gdb/gdbserver/ChangeLog:
2016-09-23  Pedro Alves  <palves@redhat.com>

	* Makefile.in (SFILES): Add common/new-op.c.
	(OBS): Add common/new-op.o.
	(new-op.o): New rule.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Replace sprintf with xsnprintf in nat/linux-osdata.c
@ 2016-09-23 21:43 sergiodj+buildbot
  2016-09-23 23:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-23 21:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97e64e5ab19dbf6a9babd711e8deec5545520954 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 97e64e5ab19dbf6a9babd711e8deec5545520954

Replace sprintf with xsnprintf in nat/linux-osdata.c

I see the following build warning when I build GDB with GCC trunk.

../../binutils-gdb/gdb/nat/linux-osdata.c: In function LONGEST linux_xfer_osdata_fds(gdb_byte*, ULONGEST, ULONGEST):
../../binutils-gdb/gdb/nat/linux-osdata.c:767:1: error: %s directive writing between 0 and 255 bytes into a region of size 11 [-Werror=format-length=]
 linux_xfer_osdata_fds (gdb_byte *readbuf,
 ^~~~~~~~~~~~~~~~~~~~~
../../binutils-gdb/gdb/nat/linux-osdata.c:800:51: note: format output between 7 and 262 bytes into a destination of size 17
        sprintf (procentry, "/proc/%s", dp->d_name);
                                                   ^
../../binutils-gdb/gdb/nat/linux-osdata.c: In function LONGEST linux_xfer_osdata_threads(gdb_byte*, ULONGEST, ULONGEST):
../../binutils-gdb/gdb/nat/linux-osdata.c:555:1: error: %s directive writing between 0 and 255 bytes into a region of size 11 [-Werror=format-length=]
 linux_xfer_osdata_threads (gdb_byte *readbuf,
 ^~~~~~~~~~~~~~~~~~~~~~~~~
../../binutils-gdb/gdb/nat/linux-osdata.c:588:51: note: format output between 7 and 262 bytes into a destination of size 17
        sprintf (procentry, "/proc/%s", dp->d_name);
                                                   ^
cc1plus: all warnings being treated as errors

The warning is a false positive, but we can workaround it by replacing
sprintf with xsnprintf.  On the other hand, it is always preferred to
use xsnprintf.

gdb:

2016-09-23  Yao Qi  <yao.qi@linaro.org>

	* nat/linux-osdata.c (linux_xfer_osdata_threads): Replace
	sprintf with xsnprintf.
	(linux_xfer_osdata_fds): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove some unnecessary code
@ 2016-09-23 22:27 sergiodj+buildbot
  2016-09-24  0:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-23 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e25a500a1ba05587389737e7c617e5ae6dd2bcf ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 3e25a500a1ba05587389737e7c617e5ae6dd2bcf

Remove some unnecessary code

This patch removes some unnecessary code.  In particular,
terminate_minimal_symbol_table is declared in minsyms.h, so it doesn't
need to be declared in objfiles.h as well.  And,
restore_ui_out_closure was rendered unnecessary by an earlier patch,
so the structure definition can be removed now.

I'm checking this in as obvious.

Tested by rebuilding on x86-64 Fedora 24 with --enable-targets=all;
which would notice any missing includes of minsyms.h.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* utils.c (struct restore_ui_out_closure): Remove.
	* objfiles.h (terminate_minimal_symbol_table): Don't declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string in break-catch-sig.c
@ 2016-09-23 23:51 sergiodj+buildbot
  2016-09-24  5:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-23 23:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5809899dad253e2fefcb6f7ae57a6f43cfa4e3c5 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 5809899dad253e2fefcb6f7ae57a6f43cfa4e3c5

Use std::string in break-catch-sig.c

This changes one spot in break-catch-sig.c to use std::string,
removing some cleanups.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* break-catch-sig.c: Include <string>.
	(signal_catchpoint_print_one): Use std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string in cp-namespace.c
@ 2016-09-24  0:14 sergiodj+buildbot
  2016-09-24  9:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-24  0:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 05d49c372d4689f8ca8baf4fdd32529ac40f297a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 05d49c372d4689f8ca8baf4fdd32529ac40f297a

Use std::string in cp-namespace.c

This changes a few spots in cp-namespace.c to use std::string,
removing some cleanups.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* cp-namespace.c: Include <string>.
	(cp_search_static_and_baseclasses)
	(cp_lookup_symbol_imports_or_template, find_symbol_in_baseclass):
	Use std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string, std::vector in rust-lang.c
@ 2016-09-24  2:55 sergiodj+buildbot
  2016-09-24 12:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-24  2:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab8b80a88546eacb6e75004e8dd571e6bdf9505f ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: ab8b80a88546eacb6e75004e8dd571e6bdf9505f

Use std::string, std::vector in rust-lang.c

This patch changes some spots in rust-lang.c to use std::string or
std::vector, removing some cleanups.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* rust-lang.c: Include <string> and <vector>.
	(rust_evaluate_funcall): Use std::vector, std::string.
	(rust_evaluate_subexp): Use std::string.
	(rust_lookup_symbol_nonlocal): Use std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::vector in objfiles.c
@ 2016-09-24  4:16 sergiodj+buildbot
  2016-09-24 14:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-24  4:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cfe826d45ea2e15f0df4c039dfa4b9ea605831da ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cfe826d45ea2e15f0df4c039dfa4b9ea605831da

Use std::vector in objfiles.c

This patch changes a spot in objfiles.c to use a std::vector, removing
a cleanup.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* objfiles.c: Include <vector>.
	(objfile_relocate): Use std::vector.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string rather than dyn-string
@ 2016-09-24  7:30 sergiodj+buildbot
  2016-09-24 15:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-24  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97e29d248d51bb688cff677def657eb0cf82cca ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: a97e29d248d51bb688cff677def657eb0cf82cca

Use std::string rather than dyn-string

This patch changes some code in cli-cmds.c to use std::string rather
than dyn-string, removing some cleanups.  Since this was the last use
of dyn-string in gdb, this patch also removes
make_cleanup_dyn_string_delete.

2016-09-23  Tom Tromey  <tom@tromey.com>

	* utils.h (make_cleanup_dyn_string_delete): Remove declaration.
	* utils.c: Don't include dyn-string.h.
	(do_dyn_string_delete, make_cleanup_dyn_string_delete): Remove.
	* cli/cli-cmds.c: Include <string>.  Don't include dyn-string.h.
	(argv_to_string): Rename.  Change return type to std::string.
	(alias_command): Use std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix a use of target_mourn_inferior in windows-nat.c
@ 2016-09-25  5:08 sergiodj+buildbot
  2016-09-25  5:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-25  5:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9eee20eb5400345cab1952cbfc0426035ddf1140 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 9eee20eb5400345cab1952cbfc0426035ddf1140

Fix a use of target_mourn_inferior in windows-nat.c

One use of target_mourn_interior seems to have been missed in bc1e6c81

gdb/ChangeLog:

2016-09-23  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (windows_delete_thread): Adjusting call to
	target_mourn_inferior to include ptid_t argument.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Call debug_exit in linux_wait_1
@ 2016-09-26 11:09 sergiodj+buildbot
  2016-09-26 15:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-26 11:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edeeb6024373d865284903f0b96b9811afde0441 ***

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

Call debug_exit in linux_wait_1

When I read the GDBserver debug message, I find the "entering" of
linux_wait_1 doesn't match the "existing" of linux_wait_1.  Looks
we don't call debug_exit somewhere in linux_wait_1 on return.

gdb/gdbserver:

2016-09-26  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_wait_1): Call debug_exit.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PowerPC .gnu.attributes
@ 2016-09-26 16:58 sergiodj+buildbot
  2016-09-26 17:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-26 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 005d79fd6101dae0aaf62a1b0cee399efcbd0e21 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 005d79fd6101dae0aaf62a1b0cee399efcbd0e21

PowerPC .gnu.attributes

This patch extends Tag_GNU_Power_ABI_FP to cover long double ABIs,
makes the assembler warn about undefined tag values, and removes
similar warnings from the linker.  I think it is better to not
warn in the linker about undefined tag values as future extensions to
the tags then won't result in likely bogus warnings.  This is
consistent with the fact that an older linker won't warn on an
entirely new tag.

include/
	* elf/ppc.h (Tag_GNU_Power_ABI_FP): Comment.
bfd/
	* elf-bfd.h (_bfd_elf_ppc_merge_fp_attributes): Declare.
	* elf32-ppc.c (_bfd_elf_ppc_merge_fp_attributes): New function.
	(ppc_elf_merge_obj_attributes): Use it.  Don't copy first file
	attributes, merge them.  Don't warn about undefined tag bits,
	or copy unknown values to output.
	* elf64-ppc.c (ppc64_elf_merge_private_bfd_data): Call
	_bfd_elf_ppc_merge_fp_attributes.
binutils/
	* readelf.c (display_power_gnu_attribute): Catch truncated section
	for all powerpc attributes.  Display long double ABI.  Don't
	capitalize words, except for names.  Show known bits of tag values
	when some unknown bits are present.  Whitespace fixes.
gas/
	* config/tc-ppc.c (ppc_elf_gnu_attribute): New function.
	(md_pseudo_table <ELF>): Handle "gnu_attribute".
ld/
	* testsuite/ld-powerpc/attr-gnu-4-4.s: Delete.
	* testsuite/ld-powerpc/attr-gnu-4-14.d: Delete.
	* testsuite/ld-powerpc/attr-gnu-4-24.d: Delete.
	* testsuite/ld-powerpc/attr-gnu-4-34.d: Delete.
	* testsuite/ld-powerpc/attr-gnu-4-41.d: Delete.
	* testsuite/ld-powerpc/attr-gnu-4-32.d: Adjust expected warning.
	* testsuite/ld-powerpc/attr-gnu-8-23.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-01.d: Adjust expected output.
	* testsuite/ld-powerpc/attr-gnu-4-02.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-03.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-10.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-11.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-20.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-22.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-33.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-8-11.d: Likewise.
	* testsuite/ld-powerpc/powerpc.exp: Don't run deleted tests.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARC] ISA alignment.
@ 2016-09-26 19:24 sergiodj+buildbot
  2016-09-26 20:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-26 19:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b848ebdbb2d1f856c7525ed4d6efaf6fe70de81 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 2b848ebdbb2d1f856c7525ed4d6efaf6fe70de81

[ARC] ISA alignment.

include/
2016-09-26  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (insn_class_t): Add two new classes.

opcodes/
2016-09-26  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-ext-tbl.h (EXTINSN2OPF): Define.
	(EXTINSN2OP): Use EXTINSN2OPF.
	(bspeekm, bspop, modapp): New extension instructions.
	* arc-opc.c (F_DNZ_ND): Define.
	(F_DNZ_D): Likewise.
	(F_SIZEB1): Changed.
	(C_DNZ_D): Define.
	(C_HARD): Changed.
	* arc-tbl.h (dbnz): New instruction.
	(prealloc): Allow it for ARC EM.
	(xbfu): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix the calculation of AMD64_PCRQUAD relocations.
@ 2016-09-26 22:57 sergiodj+buildbot
  2016-09-27  2:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-26 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 384f7503344b1d07561f801ced7493858cde6164 ***

Author: Awson <kyrab@mail.ru>
Branch: master
Commit: 384f7503344b1d07561f801ced7493858cde6164

Fix the calculation of AMD64_PCRQUAD relocations.

	PR ld/17955
	* coff-x86_64.c (coff_amd64_rtype_to_howto): Use an 8 byte offset
	for R_AMD64_PCRQUAD relocations.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Detect the magic address of EXC_RETURN in ARM coretx-m profile
@ 2016-09-27 11:34 sergiodj+buildbot
  2016-09-27 11:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-27 11:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca90e76046d302a730629ecf39b425a8aaa590c2 ***

Author: Fredrik Hederstierna <fredrik.hederstierna@verisure.com>
Branch: master
Commit: ca90e76046d302a730629ecf39b425a8aaa590c2

Detect the magic address of EXC_RETURN in ARM coretx-m profile

On ARMv6-M and ARMv7-M, the exception return address is sort of magic
address defined by the manual.  This patch is to let GDB well handle
these magic addresses.

2016-09-27  Fredrik Hederstierna  <fredrik.hederstierna@verisure.com>

	* arm-tdep.c (arm_m_addr_is_magic): New function.
	(arm_addr_bits_remove): Call arm_m_addr_is_magic.
	(arm_m_exception_unwind_sniffer): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Ensure that the timestamp in PE/COFF headers is always initialised.
@ 2016-09-28  0:56 sergiodj+buildbot
  2016-09-28  1:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-28  0:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c5f704fc035bc705dee887418f42cb8bca24b5d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 1c5f704fc035bc705dee887418f42cb8bca24b5d

Ensure that the timestamp in PE/COFF headers is always initialised.

	PR ld/20634
	* peXXigen.c (_bfd_XXi_only_swap_filehdr_out): Put 0 in the
	timestamp field if real time values are not being stored.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add archives and make stamps to the .gitignore file.
@ 2016-09-28 12:00 sergiodj+buildbot
  2016-09-28 12:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-28 12:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07619d52fef6fda58cbc327512a4d8ec60ad5637 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 07619d52fef6fda58cbc327512a4d8ec60ad5637

Add archives and make stamps to the .gitignore file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] PR ld/20608 Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry
@ 2016-09-28 22:44 sergiodj+buildbot
  2016-09-28 22:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-28 22:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2df2751d1927e1231bbe7d548139da98d6ca9b9a ***

Author: Christophe Lyon <christophe.lyon@linaro.org>
Branch: master
Commit: 2df2751d1927e1231bbe7d548139da98d6ca9b9a

[ARM] PR ld/20608 Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry

2016-09-28  Christophe Lyon  <christophe.lyon@linaro.org>

	PR ld/20608
	bfd/
	* elf32-arm.c (arm_type_of_stub): Handle the case when the pre-PLT
	Thumb-ARM stub is too far.

	ld
	* testsuite/ld-arm/arm-elf.exp: Handle new testcase.
	* testsuite/ld-arm/farcall-mixed-app2.d: New file.
	* testsuite/ld-arm/farcall-mixed-app2.r: Likewise.
	* testsuite/ld-arm/farcall-mixed-app2.s: Likewise.
	* testsuite/ld-arm/farcall-mixed-app2.sym: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix seg-fault in the linker introduced by the previous delta.
@ 2016-09-28 23:53 sergiodj+buildbot
  2016-09-29  0:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-28 23:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9eaff8613893f063400fdae95bc382ab33685e3b ***

Author: Akihiko Odaki <akihiko.odaki.4i@stu.hosei.ac.jp>
Branch: master
Commit: 9eaff8613893f063400fdae95bc382ab33685e3b

Fix seg-fault in the linker introduced by the previous delta.

	PR ld/20636
	* elf-bfd.h (struct elf_backend_data): Delete
	elf_backend_count_output_relocs callback and add
	elf_backend_update_relocs.
	* elf32-arm.c (elf32_arm_count_output_relocs): Deleted.
	(emit_relocs): Deleted.
	(elf32_arm_emit_relocs): Deleted.
	(elf_backend_emit_relocs): Updated not to use the old functions.
	(elf32_arm_update_relocs): New function.
	(elf_backend_update_relocs): New define.
	* elflink.c (bfd_elf_final_link): Add additional_reloc_count to the
	relocation count. Call elf_backend_emit_relocs.
	(_bfd_elf_size_reloc_section): Do not call
	elf_backend_count_output_relocs.
	* elfxx-target.h (elf_backend_count_output_relocs): Deleted.
	(elf_backend_update_relocs): New define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed
@ 2016-09-29  6:35 sergiodj+buildbot
  2016-09-29  6:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-29  6:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d61dee599fb314f0561c3bd0dd17ac0cfa05e35 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6d61dee599fb314f0561c3bd0dd17ac0cfa05e35

Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed

If you run an infcall from the command line, and immediately after run
some other command, GDB incorrectly processes the other command before
the infcall finishes.

The problem is that the fix for PR gdb/20418 (Problems with
synchronous commands and new-ui, git 3eb7562a983b) moved the
add_file_handler/delete_file_handler calls out of
target_terminal_$foo, and missed adjusting the infcall code.

gdb/ChangeLog:
2016-09-28  Pedro Alves  <palves@redhat.com>

	* infcall.c (run_inferior_call): Remove input from the event
	loop while running the infcall.

gdb/testsuite/ChangeLog:
2016-09-28  Pedro Alves  <palves@redhat.com>

	* gdb.base/infcall-input.c: New file.
	* gdb.base/infcall-input.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
@ 2016-09-29 21:17 sergiodj+buildbot
  2016-09-29 21:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-29 21:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb805577d2b212411fb7b0a2d01644567fac4e8d ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: bb805577d2b212411fb7b0a2d01644567fac4e8d

PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression

Regression: gdb --pid $(pidof qemu-system-x86_64) stopped working with gdb 7.11.1
https://sourceware.org/bugzilla/show_bug.cgi?id=20609

It was reported for qemu-system-x86_64 but it happens for any multithreaded
inferior with a JIT debugging hook.

136613ef0c6850427317e57be1b644080ff6decb is the first bad commit
Author: Pedro Alves <palves@redhat.com>
    Fix PR gdb/19828: gdb -p <process from a container>: internal error
Message-ID: <cbdf2e04-4fa8-872a-2a23-08c9c1b26e00@redhat.com>
https://sourceware.org/ml/gdb-patches/2016-05/msg00450.html

jit_breakpoint_re_set() is specific by trying to insert a breakpoint into the
main executable, not into a shared library.  During attachment GDB thinks it
needs to use 'breakpoint always-inserted' from
breakpoints_should_be_inserted_now() as a newly attached thread is
'thread_info->executing' due to 'lwp_info->must_set_ptrace_flags' enabled and
the task not yet stopped.  This did not happen before the 'bad commit' above
which adds tracking of such thread.

GDB then fails to insert the breakpoints to invalid address as PIE executable
gets properly relocated during later phase of attachment.  One can see in the
backtraces below:
 -> jit_breakpoint_re_set_internal()
later:
 -> svr4_exec_displacement()

One can suppress the initial breakpoint_re_set() call as there will be another
breakpoint_re_set() done from the final post_create_inferior() call in
setup_inferior().

BTW additionally 'threads_executing' cache bool is somehow stale (somewhere is
missing update_threads_executing()).  I was trying to deal with that in my
first/second attempt below but in my final third attempt (attached) I have
left it as it is.

First attempt trying not to falsely require 'breakpoint always-inserted':
  https://people.redhat.com/jkratoch/rhbz1375553-fix1.patch
Reduced first attempt:
  https://people.redhat.com/jkratoch/rhbz1375553-fix2.patch

The third attempt suppresses breakpoint insertion until PIE executable gets
relocated by svr4_exec_displacement().  Applied.

gdb/ChangeLog
2016-09-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
	* exec.c (exec_file_locate_attach): Add parameter defer_bp_reset.
	Use it.
	* gdbcore.h (exec_file_locate_attach): Add parameter defer_bp_reset.
	* infcmd.c (setup_inferior): Update caller.
	* remote.c (remote_add_inferior): Likewise.

gdb/testsuite/ChangeLog
2016-09-29  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression
	* gdb.base/jit-attach-pie.c: New file.
	* gdb.base/jit-attach-pie.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update tests to account for the L operand being compulsory.
@ 2016-09-30 10:59 sergiodj+buildbot
  2016-09-30 11:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-30 10:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4297203ea1a1e4664b6f2b05efecd60f6437f46 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: a4297203ea1a1e4664b6f2b05efecd60f6437f46

Update tests to account for the L operand being compulsory.

	* gdb.arch/powerpc-power.exp <cmprb>: Update tests to account for
	the compulsory L operand changes.
	* gdb.arch/powerpc-power.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove syntactic sugar
@ 2016-09-30 15:11 sergiodj+buildbot
  2016-09-30 16:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-30 15:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4eca02287cf48e60ee89338ddd35f8d0d8257a51 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4eca02287cf48e60ee89338ddd35f8d0d8257a51

Remove syntactic sugar

Now that _bfd_error_handler is not a function pointer.

	* aout-adobe.c: Replace (*_bfd_error_handler) (...) with
	_bfd_error_handler (...) throughout.
	* aout-cris.c, * aoutx.h, * archive.c, * bfd.c, * binary.c,
	* cache.c, * coff-alpha.c, * coff-arm.c, * coff-h8300.c,
	* coff-i860.c, * coff-mcore.c, * coff-ppc.c, * coff-rs6000.c,
	* coff-sh.c, * coff-tic4x.c, * coff-tic54x.c, * coff-tic80.c,
	* coff64-rs6000.c, * coffcode.h, * coffgen.c, * cofflink.c,
	* coffswap.h, * cpu-arm.c, * cpu-m68k.c, * cpu-sh.c, * dwarf2.c,
	* ecoff.c, * elf-eh-frame.c, * elf-m10300.c, * elf.c, * elf32-arc.c,
	* elf32-arm.c, * elf32-avr.c, * elf32-bfin.c, * elf32-cr16.c,
	* elf32-cris.c, * elf32-crx.c, * elf32-dlx.c, * elf32-frv.c,
	* elf32-hppa.c, * elf32-i370.c, * elf32-i386.c, * elf32-lm32.c,
	* elf32-m32c.c, * elf32-m32r.c, * elf32-m68hc1x.c, * elf32-m68k.c,
	* elf32-mcore.c, * elf32-mep.c, * elf32-metag.c, * elf32-microblaze.c,
	* elf32-mips.c, * elf32-nds32.c, * elf32-nios2.c, * elf32-or1k.c,
	* elf32-pj.c, * elf32-ppc.c, * elf32-rl78.c, * elf32-s390.c,
	* elf32-score.c, * elf32-score7.c, * elf32-sh.c, * elf32-sh64.c,
	* elf32-sparc.c, * elf32-spu.c, * elf32-tic6x.c, * elf32-tilepro.c,
	* elf32-v850.c, * elf32-vax.c, * elf32-xtensa.c, * elf64-alpha.c,
	* elf64-hppa.c, * elf64-ia64-vms.c, * elf64-mips.c, * elf64-mmix.c,
	* elf64-ppc.c, * elf64-s390.c, * elf64-sh64.c, * elf64-sparc.c,
	* elf64-x86-64.c, * elfcode.h, * elfcore.h, * elflink.c,
	* elfn32-mips.c, * elfnn-aarch64.c, * elfnn-ia64.c, * elfxx-mips.c,
	* elfxx-sparc.c, * elfxx-tilegx.c, * hpux-core.c, * i386linux.c,
	* ieee.c, * ihex.c, * libbfd.c, * linker.c, * m68klinux.c,
	* mach-o.c, * merge.c, * mmo.c, * oasys.c, * osf-core.c, * pdp11.c,
	* pe-mips.c, * peXXigen.c, * pef.c, * plugin.c, * reloc.c,
	* rs6000-core.c, * sco5-core.c, * som.c, * sparclinux.c, * srec.c,
	* stabs.c, * syms.c, * vms-alpha.c, * vms-lib.c, * vms-misc.c,
	* xcofflink.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add missing dependencies to BFD_H_FILES
@ 2016-09-30 19:17 sergiodj+buildbot
  2016-09-30 19:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-09-30 19:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92c6e4fe5d6f30a24fe15795a6a3b25afd0b24c9 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 92c6e4fe5d6f30a24fe15795a6a3b25afd0b24c9

Add missing dependencies to BFD_H_FILES

	* Makefile.am (BFD_H_FILES): Add linker.c and simple.c.  Sort
	as per comment at head of bfd-in2.h.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Emit inferior, thread and frame selection events to all UIs
@ 2016-10-03 21:15 sergiodj+buildbot
  2016-10-03 21:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-03 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4034d0ff52b0f346efedd2d335ccbc672466da45 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 4034d0ff52b0f346efedd2d335ccbc672466da45

Emit inferior, thread and frame selection events to all UIs

With this patch, when an inferior, thread or frame is explicitly
selected by the user, notifications will appear on all CLI and MI UIs.
When a GDB console is integrated in a front-end, this allows the
front-end to follow a selection made by the user ont he CLI, and it
informs the user about selection changes made behind the scenes by the
front-end.

This patch addresses PR gdb/20487.

In order to communicate frame changes to the front-end, this patch adds
a new field to the =thread-selected event for the selected frame.  The
idea is that since inferior/thread/frame can be seen as a composition,
it makes sense to send them together in the same event.  The vision
would be to eventually send the inferior information as well, if we find
that it's needed, although the "=thread-selected" event would be
ill-named for that job.

Front-ends need to handle this new field if they want to follow the
frame selection changes that originate from the console.  The format of
the frame attribute is the same as what is found in the *stopped events.

Here's a detailed example for each command and the events they generate:

thread
------

1. CLI command:

     thread 1.3

   MI event:

     =thread-selected,id="3",frame={...}

2. MI command:

     -thread-select 3

   CLI event:

     [Switching to thread 1.3 ...]

3. MI command (CLI-in-MI):

     thread 1.3

   MI event/reply:

     &"thread 1.3\n"
     ~"#0  child_sub_function () ...
     =thread-selected,id="3",frame={level="0",...}
     ^done

frame
-----

1. CLI command:

     frame 1

   MI event:

     =thread-selected,id="3",frame={level="1",...}

2. MI command:

     -stack-select-frame 1

   CLI event:

     #1  0x00000000004007f0 in child_function...

3. MI command (CLI-in-MI):

     frame 1

   MI event/reply:

     &"frame 1\n"
     ~"#1  0x00000000004007f9 in ..."
     =thread-selected,id="3",frame={level="1"...}
     ^done

inferior
--------

Inferior selection events only go from the console to MI, since there's
no way to select the inferior in pure MI.

1. CLI command:

     inferior 2

   MI event:

     =thread-selected,id="3"

Note that if the user selects an inferior that is not started or exited,
the MI doesn't receive a notification.  Since there is no threads to
select, the =thread-selected event does not apply...

2. MI command (CLI-in-MI):

     inferior 2

   MI event/reply:

     &"inferior 2\n"
     ~"[Switching to inferior 2 ...]"
     =thread-selected,id="4",frame={level="0"...}
     ^done

Internal implementation detail: this patch makes it possible to suppress
notifications caused by a CLI command, like what is done in mi-interp.c.
This means that it's now possible to use the
add_com_suppress_notification function to register a command with some
event suppressed.  It is used to implement the select-frame command in
this patch.

The function command_notifies_uscc_observer was added to extract
the rather complicated logical expression from the if statement.  It is
also now clearer what that logic does: if the command used by the user
already notifies the user_selected_context_changed observer, there is
not need to notify it again.  It therefore protects again emitting the
event twice.

No regressions, tested on ubuntu 14.04 x86 with target boards unix and
native-extended-gdbserver.

gdb/ChangeLog:

YYYY-MM-DD  Antoine Tremblay  <antoine.tremblay@ericsson.com>
YYYY-MM-DD  Simon Marchi  <simon.marchi@ericsson.com>

	PR gdb/20487
	* NEWS: Mention new frame field of =thread-selected event.
	* cli/cli-decode.c (add_cmd): Initialize c->suppress_notification.
	(add_com_suppress_notification): New function definition.
	(cmd_func): Set and restore the suppress_notification flag.
	* cli/cli-deicode.h (struct cmd_list_element)
	<suppress_notification>: New field.
	* cli/cli-interp.c (cli_suppress_notification): New global variable.
	(cli_on_user_selected_context_changed): New function.
	(_initialize_cli_interp): Attach to user_selected_context_changed
	observer.
	* command.h (struct cli_suppress_notification): New structure.
	(cli_suppress_notification): New global variable declaration.
	(add_com_suppress_notification): New function declaration.
	* defs.h (enum user_selected_what_flag): New enum.
	(user_selected_what): New enum flag type.
	* frame.h (print_stack_frame_to_uiout): New function declaration.
	* gdbthread.h (print_selected_thread_frame): New function declaration.
	* inferior.c (print_selected_inferior): New function definition.
	(inferior_command): Remove printing of inferior/thread/frame switch
	notifications, notify user_selected_context_changed observer.
	* inferior.h (print_selected_inferior): New function declaration.
	* mi/mi-cmds.c (struct mi_cmd): Add user_selected_context
	suppression to stack-select-frame and thread-select commands.
	* mi/mi-interp.c (struct mi_suppress_notification)
	<user_selected_context>: Initialize.
	(mi_user_selected_context_changed): New function definition.
	(_initialize_mi_interp): Attach to user_selected_context_changed.
	* mi/mi-main.c (mi_cmd_thread_select): Print thread selection reply.
	(mi_execute_command): Handle notification suppression.  Notify
	user_selected_context_changed observer on thread change instead of printing
	event directly.  Don't send it if command already sends the notification.
	(command_notifies_uscc_observer): New function.
	(mi_cmd_execute): Don't handle notification suppression.
	* mi/mi-main.h (struct mi_suppress_notification)
	<user_selected_context>: New field.
	* stack.c (print_stack_frame_to_uiout): New function definition.
	(select_frame_command): Notify user_selected_context_changed
	observer.
	(frame_command): Call print_selected_thread_frame if there's no frame
	change or notify user_selected_context_changed observer if there is.
	(up_command): Notify user_selected_context_changed observer.
	(down_command): Likewise.
	(_initialize_stack): Suppress user_selected_context notification for
	command select-frame.
	* thread.c (thread_command): Notify
	user_selected_context_changed if the thread has changed, print
	thread info directly if it hasn't.
	(do_captured_thread_select): Do not print thread switch event.
	(print_selected_thread_frame): New function definition.
	* tui/tui-interp.c (tui_on_user_selected_context_changed):
	New function definition.
	(_initialize_tui_interp): Attach to user_selected_context_changed
	observer.

gdb/doc/ChangeLog:

	PR gdb/20487
	* gdb.texinfo (Context management): Update mention of frame
	change notifications.
	(gdb/mi Async Records): Document frame field in
	=thread-select event.
	* observer.texi (GDB Observers): New user_selected_context_changed
	observer.

gdb/testsuite/ChangeLog:

	PR gdb/20487
	* gdb.mi/mi-pthreads.exp (check_mi_thread_command_set): Adapt
	=thread-select-event check.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add test for user context selection sync
@ 2016-10-03 22:01 sergiodj+buildbot
  2016-10-03 22:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-03 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c36d9544f0987cbd840a19552af3343252d28a0 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 9c36d9544f0987cbd840a19552af3343252d28a0

Add test for user context selection sync

This patch adds a test to verify that events are sent properly to all
UIs when the user selection context (inferior, thread, frame) changes.

The goal of the C test file is to provide two threads that are stopped with the
same predictable backtrace (so that we can test frame switching).  The barrier
helps us know when the child threads are started.  Then, scheduler-locking is
used to bring each thread one by one to the position we expect them to be
during the test.

gdb/testsuite/ChangeLog:

YYYY-MM-DD  Antoine Tremblay  <antoine.tremblay@ericsson.com>
YYYY-MM-DD  Simon Marchi  <simon.marchi@ericsson.com>

	PR gdb/20487
	* gdb.mi/user-selected-context-sync.exp: New file.
	* gdb.mi/user-selected-context-sync.c: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Clean up the XML files for ARM
@ 2016-10-05  8:44 sergiodj+buildbot
  2016-10-05  9:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05  8:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a69eedb6d7c1c90ec7888a857c4d7c0a1fd1b31 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0a69eedb6d7c1c90ec7888a857c4d7c0a1fd1b31

Clean up the XML files for ARM

This patch is move features/arm-*.xml to features/arm/, and it is based
on Terry's patch posted here
https://sourceware.org/ml/gdb-patches/2014-06/msg00794.html

One comment to Terry's patch is about losing "arm" prefix, and the new
patch fixes this problem.

gdb:

2016-10-05  Terry Guo  <terry.guo@arm.com>
	    Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c: Adjust includes.
	* features/Makefile (WHICH): Add "arm/" directory to arm
	target descriptions.
	(XMLTOC): Likewise.
	(arm/arm-with-iwmmxt.dat): Adjust the path for
	dependencies.
	* features/arm-core.xml: Moved to ...
	* features/arm/arm-core.xml: ... it.
	* features/arm-fpa.xml: Moved to ...
	* features/arm/arm-fpa.xml: ... it.
	* features/arm-m-profile.xml: Moved to ...
	* features/arm/arm-m-profile.xm: ... it.
	* features/arm-vfpv2.xml: Moved to ...
	* features/arm/arm-vfpv2.xm: ... it.
	* features/arm-vfpv3.xml: Moved to ...
	* features/arm/arm-vfpv3.xml: ... it.
	* features/arm-with-iwmmxt.c: Moved to ...
	* features/arm/arm-with-iwmmxt.c: ... it.
	* features/arm-with-iwmmxt.xml: Moved to ...
	* features/arm/arm-with-iwmmxt.xml: ... it.
	* features/arm-with-m-fpa-layout.c: Moved to ...
	* features/arm/arm-with-m-fpa-layout.c: ... it.
	* features/arm-with-m-fpa-layout.xml: Moved to ...
	* features/arm/arm-with-m-fpa-layout.xml: ... it.
	* features/arm-with-m-vfp-d16.c: Moved to ...
	* features/arm/arm-with-m-vfp-d16.c: ... it.
	* features/arm-with-m-vfp-d16.xml: Moved to ...
	* features/arm/arm-with-m-vfp-d16.xml: ... it.
	* features/arm-with-m.c: Moved to ...
	* features/arm/arm-with-m.c: ... it.
	* features/arm-with-m.xml: Moved to ...
	* features/arm/arm-with-m.xm: ... it.
	* features/arm-with-neon.c: Moved to ...
	* features/arm/arm-with-neon.c: ... it.
	* features/arm-with-neon.xml: Moved to ...
	* features/arm/arm-with-neon.xml: ... it.
	* features/arm-with-vfpv2.c: Moved to ...
	* features/arm/arm-with-vfpv2.c: ... it.
	* features/arm-with-vfpv2.xml: Moved to ...
	* features/arm/arm-with-vfpv2.xml: ... it.
	* features/arm-with-vfpv3.c: Moved to ...
	* features/arm/arm-with-vfpv3.c: ... it.
	* features/arm-with-vfpv3.xml: Moved to ...
	* features/arm/arm-with-vfpv3.xml: ... it.
	* features/xscale-iwmmxt.xml: Moved to ...
	* features/arm/xscale-iwmmxt.xml: ... it.

gdb/gdbserver:

2016-10-05  Terry Guo  <terry.guo@arm.com>
	    Yao Qi  <yao.qi@linaro.org>

	* Makefile.in: Adjust the path of rules.
	* configure.srv: Update the path of xml files.
	* regformats/arm-with-iwmmxt.dat: Regenerated.
	* regformats/arm-with-neon.dat: Likewise.
	* regformats/arm-with-vfpv2.dat: Likewise.
	* regformats/arm-with-vfpv3.dat Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Simplify i386, amd64 and x32 expedite registers
@ 2016-10-05  9:01 sergiodj+buildbot
  2016-10-05  9:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 414c838a722efedb0f787b64629db13d88c9ef7c ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 414c838a722efedb0f787b64629db13d88c9ef7c

Simplify i386, amd64 and x32 expedite registers

Nowadays, there are a lot of duplication about
i386/{i386, amd64, x32}*-expedite in features/Makefile.  However,
in features/Makefile, we have

 echo "expedite:$(if $($*-expedite),$($*-expedite),$($(firstword $(subst -, ,$(notdir $*)))-expedite))" \
	  >> $(outdir)/$*.tmp

which means for a given bar/foo-baz.xml, we'll look for either
bar/foo-baz-expedite or foo-expedite.  In x86 expedite registers, we
use the former now, but it will be much simpler if we use the latter.
This is what this patch does.  This patch removes them, and defines
three generic expedite.  Re-run 'make GDB=/path/build/gdb all' to
regenerate regformats/*.dat files, and they are not changed.

gdb:

2016-10-05  Yao Qi  <yao.qi@linaro.org>

	* features/Makefile: Remove i386/*-expedite. Add i386-expedite,
	amd64-expedite, and x32-expedite.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Regenerate some regformats/rs6000/*.dat files
@ 2016-10-05  9:34 sergiodj+buildbot
  2016-10-05 12:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05  9:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5878efd48016e091cb19dc09345cd7f73d791c6f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 5878efd48016e091cb19dc09345cd7f73d791c6f

Regenerate some regformats/rs6000/*.dat files

If I remove all regformats/*.dat files and run
make GDB=/scratch/yao/gdb/build-git/all-targets/gdb/gdb all, some
powerpc .dat files are not generated.

This patch fixes it by adding them to WHICH, so these .dat files can
be generated.

gdb:

2016-10-05  Yao Qi  <yao.qi@linaro.org>

	* features/Makefile (WHICH): Add
	rs6000/powerpc-isa205-32l, rs6000/powerpc-isa205-64l,
	rs6000/powerpc-isa205-altivec32l, rs6000/powerpc-isa205-altivec64l,
	rs6000/powerpc-isa205-vsx32l and rs6000/powerpc-isa205-vsx64l.
	* regformats/rs6000/powerpc-isa205-32l.dat: Regenerated.
	* regformats/rs6000/powerpc-isa205-64l.dat: Likewise.
	* regformats/rs6000/powerpc-isa205-altivec32l.dat: Likewise.
	* regformats/rs6000/powerpc-isa205-altivec64l.dat: Likewise.
	* regformats/rs6000/powerpc-isa205-vsx32l.dat: Likewise.
	* regformats/rs6000/powerpc-isa205-vsx64l.dat: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update the path arm-*.xml files for aarch64
@ 2016-10-05 11:11 sergiodj+buildbot
  2016-10-05 13:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 11:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1d0b70ae517512a77eed778c6dd7d8a941962fc ***

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

Update the path arm-*.xml files for aarch64

0a69eedb (Clean up the XML files for ARM) breaks the GDBserver build
on aarch64 because some arm-*.xml files can't be found.

This patch is to fix the build failure.

gdb/gdbserver:

2016-10-05  Yao Qi  <yao.qi@linaro.org>

	* configure.srv: Update the path of arm-*.xml files.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] arc: Remove annoying debug message
@ 2016-10-05 14:41 sergiodj+buildbot
  2016-10-05 14:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 14:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed2f09e183df513e9616c53cdace32cf8b824b98 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: ed2f09e183df513e9616c53cdace32cf8b824b98

arc: Remove annoying debug message

The logging message is called too often - once for each register when it's
value has to be evaluated. This floods the screen for commands like "info
register all", but doesn't give really any help at debugging GDB issues.
Between increasing the debug level of this message and removing it altogether I
think that removing it is preferable.

gdb/ChangeLog:

	arc-tdep.c (arc_frame_prev_register): Remove annoying log message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip complex types tests if gdb_skip_float_test
@ 2016-10-05 16:25 sergiodj+buildbot
  2016-10-05 16:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fdebf1a415f565fc4606f9139d10d1e9393999c0 ***

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

Skip complex types tests if gdb_skip_float_test

If the target doesn't support float, we don't run float complex types
tests.

gdb/testsuite:

2016-10-05  Yao Qi  <yao.qi@linaro.org>

	* lib/gdb.exp (support_complex_tests): Return zero if
	gdb_skip_float_test return true.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR symtab/20652 - fix psymbol_compare
@ 2016-10-05 17:49 sergiodj+buildbot
  2016-10-05 17:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e611445bf05fa20e0befa41afa42651d1983734 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 3e611445bf05fa20e0befa41afa42651d1983734

PR symtab/20652 - fix psymbol_compare

This fixes an oversight in psymbol_compare.

2016-10-05  Tom Tromey  <tom@tromey.com>

	PR symtab/20652:
	* psymtab.c (psymbol_compare): Correctly compare "ginfo.value"
	fields.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR remote/20655 - small fix in handle_tracepoint_bkpts
@ 2016-10-05 19:49 sergiodj+buildbot
  2016-10-05 19:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39b5a3b9b3aadac723de719f3c27f8462ed49af7 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 39b5a3b9b3aadac723de719f3c27f8462ed49af7

PR remote/20655 - small fix in handle_tracepoint_bkpts

handle_tracepoint_bkpts has two parallel "if"s.  This changes the
second one to check ipa_error_tracepoint, which seems to be what was
intended.

2016-10-05  Tom Tromey  <tom@tromey.com>

	PR remote/20655:
	* tracepoint.c (handle_tracepoint_bkpts): Check
	ipa_error_tracepoint, not ipa_stopping_tracepoint.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix recent GCC FAIL: gdb.arch/i386-signal.exp
@ 2016-10-05 20:50 sergiodj+buildbot
  2016-10-05 20:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 20:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f389f6fef76d7cf8e8beb7061edff2155c284898 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: f389f6fef76d7cf8e8beb7061edff2155c284898

testsuite: Fix recent GCC FAIL: gdb.arch/i386-signal.exp

gcc-6.2.1-2.fc24.x86_64

(gdb) backtrace 10^M
(gdb) FAIL: gdb.arch/i386-signal.exp: backtrace 10

(gdb) disas/s
Dump of assembler code for function main:
.../gdb/testsuite/gdb.arch/i386-signal.c:
30      {
   0x000000000040057f <+0>:     push   %rbp
   0x0000000000400580 <+1>:     mov    %rsp,%rbp
31        setup ();
   0x0000000000400583 <+4>:     callq  0x400590 <setup>
=> 0x0000000000400588 <+9>:     mov    $0x0,%eax
32      }
   0x000000000040058d <+14>:    pop    %rbp
   0x000000000040058e <+15>:    retq
End of assembler dump.

The .exp patch is an obvious typo fix I think.  The regex was written to
accept "ADDR in main" and I find it OK as checking .debug_line validity is not
the purpose of this testfile.

gcc-4.8.5-11.el7.x86_64 did not put the 'mov $0x0,%eax' instruction there at
all so there was no problem with .debug_line.

gdb/testsuite/ChangeLog
2016-10-05  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/i386-signal.exp (backtrace 10): Fix #2 typo.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't use boolean OR in arithmetic expressions
@ 2016-10-06  0:04 sergiodj+buildbot
  2016-10-06  0:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06  0:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 616ec3583b7b6ba0a4e581c426b700b0664a3027 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 616ec3583b7b6ba0a4e581c426b700b0664a3027

Don't use boolean OR in arithmetic expressions

bfd/
	* elf32-epiphany.c (epiphany_final_link_relocate): Use bitwise
	OR in arithmetic expression, not boolean OR.
opcodes/
	* cr16-dis.c (print_insn_cr16): Don't use boolean OR in arithmetic.
	* crx-dis.c (print_insn_crx): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] -Wimplicit-fallthrough error fixes
@ 2016-10-06  0:52 sergiodj+buildbot
  2016-10-06  1:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06  0:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b804145796e948fa4c025c07eb201e700281e6b ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 2b804145796e948fa4c025c07eb201e700281e6b

-Wimplicit-fallthrough error fixes

Well, not all are errors, but a little more substantive than just
fiddling with comments.

bfd/
	* coffcode.h (coff_slurp_symbol_table): Revert accidental commit
	made 2015-01-08.
	* elf32-nds32.c (nds32_elf_grok_psinfo): Add missing break.
	* reloc.c (bfd_default_reloc_type_lookup): Add missing breaks.
opcodes/
	* arc-ext.c (create_map): Add missing break.
	* msp430-decode.opc (encode_as): Likewise.
	* msp430-decode.c: Regenerate.
binutils/
	* coffdump.c (dump_coff_where): Add missing break.
	* stabs.c (stab_xcoff_builtin_type): Likewise.
gas/
	* config/tc-arc.c (find_opcode_match): Add missing break.
	* config/tc-i960.c (get_cdisp): Likewise.
	* config/tc-metag.c (parse_swap, md_apply_fix): Likewise.
	* config/tc-mt.c (md_parse_option): Likewise.
	* config/tc-nds32.c (nds32_apply_fix): Likewise.
	* config/tc-hppa.c (pa_ip): Assert rather than testing last
	condition of multiple if statements.
	* config/tc-s390.c (s390_exp_compare): Return 0 on error.
	* config/tc-tic4x.c (tic4x_operand_parse): Add as_bad and break
	out of case rather than falling into next case.  Formatting.
ld/
	* plugin.c (asymbol_from_plugin_symbol): Avoid compiler warning
	by adding return.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] -Wimplicit-fallthrough warning fixes
@ 2016-10-06  1:07 sergiodj+buildbot
  2016-10-06  3:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06  1:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a0670f37442b7ae904932b347353046126b990c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1a0670f37442b7ae904932b347353046126b990c

-Wimplicit-fallthrough warning fixes

Comment changes.

bfd/
	* coff-h8300.c: Spell fall through comments consistently.
	* coffgen.c: Likewise.
	* elf32-hppa.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-score.c: Likewise.
	* elf32-score7.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elfxx-aarch64.c: Likewise.
	* elfxx-mips.c: Likewise.
	* cpu-ns32k.c: Add missing fall through comments.
	* elf-m10300.c: Likewise.
	* elf32-arm.c: Likewise.
	* elf32-avr.c: Likewise.
	* elf32-bfin.c: Likewise.
	* elf32-frv.c: Likewise.
	* elf32-i386.c: Likewise.
	* elf32-microblaze.c: Likewise.
	* elf32-nds32.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-rl78.c: Likewise.
	* elf32-rx.c: Likewise.
	* elf32-s390.c: Likewise.
	* elf32-sh.c: Likewise.
	* elf32-tic6x.c: Likewise.
	* elf64-ia64-vms.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elf64-s390.c: Likewise.
	* elf64-x86-64.c: Likewise.
	* elflink.c: Likewise.
	* elfnn-aarch64.c: Likewise.
	* elfnn-ia64.c: Likewise.
	* ieee.c: Likewise.
	* oasys.c: Likewise.
	* pdp11.c: Likewise.
	* srec.c: Likewise.
	* versados.c: Likewise.
opcodes/
	* aarch64-opc.c: Spell fall through comments consistently.
	* i386-dis.c: Likewise.
	* aarch64-dis.c: Add missing fall through comments.
	* aarch64-opc.c: Likewise.
	* arc-dis.c: Likewise.
	* arm-dis.c: Likewise.
	* i386-dis.c: Likewise.
	* m68k-dis.c: Likewise.
	* mep-asm.c: Likewise.
	* ns32k-dis.c: Likewise.
	* sh-dis.c: Likewise.
	* tic4x-dis.c: Likewise.
	* tic6x-dis.c: Likewise.
	* vax-dis.c: Likewise.
binutils/
	* dlltool.c: Spell fall through comments consistently.
	* objcopy.c: Likewise.
	* readelf.c: Likewise.
	* dwarf.c: Add missing fall through comments.
	* elfcomm.c: Likewise.
	* sysinfo.y: Likewise.
	* readelf.c: Likewise.  Also remove extraneous comments.
gas/
	* app.c: Add missing fall through comments.
	* dw2gencfi.c: Likewise.
	* expr.c: Likewise.
	* config/tc-alpha.c: Likewise.
	* config/tc-arc.c: Likewise.
	* config/tc-arm.c: Likewise.
	* config/tc-cr16.c: Likewise.
	* config/tc-crx.c: Likewise.
	* config/tc-dlx.c: Likewise.
	* config/tc-h8300.c: Likewise.
	* config/tc-hppa.c: Likewise.
	* config/tc-i370.c: Likewise.
	* config/tc-i386.c: Likewise.
	* config/tc-i960.c: Likewise.
	* config/tc-ia64.c: Likewise.
	* config/tc-m68hc11.c: Likewise.
	* config/tc-m68k.c: Likewise.
	* config/tc-mep.c: Likewise.
	* config/tc-metag.c: Likewise.
	* config/tc-microblaze.c: Likewise.
	* config/tc-mips.c: Likewise.
	* config/tc-ns32k.c: Likewise.
	* config/tc-rx.c: Likewise.
	* config/tc-score.c: Likewise.
	* config/tc-score7.c: Likewise.
	* config/tc-sh.c: Likewise.
	* config/tc-tic4x.c: Likewise.
	* config/tc-vax.c: Likewise.
	* config/tc-xstormy16.c: Likewise.
	* config/tc-z80.c: Likewise.
	* config/tc-z8k.c: Likewise.
	* config/obj-elf.c: Likewise.
	* config/tc-i386.c: Likewise.
	* depend.c: Spell fall through comments consistently.
	* config/tc-arm.c: Likewise.
	* config/tc-d10v.c: Likewise.
	* config/tc-i960.c: Likewise.
	* config/tc-ia64.c: Likewise.
	* config/tc-m68k.c: Likewise.
	* config/tc-mcore.c: Likewise.
	* config/tc-mep.c: Likewise.
	* config/tc-ns32k.c: Likewise.
	* config/tc-visium.c: Likewise.
	* config/tc-xstormy16.c: Likewise.
	* config/tc-z8k.c: Likewise.
gprof/
	* gprof.c: Add missing fall through comments.
ld/
	* lexsup.c: Spell fall through comments consistently and add
	missing fall through comments.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make "end" field in feature specs required again.
@ 2016-10-06 11:32 sergiodj+buildbot
  2016-10-06 12:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee8da4b8396d9a74d27cb9bb0f3aa43d6d23b8ea ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: ee8da4b8396d9a74d27cb9bb0f3aa43d6d23b8ea

Make "end" field in feature specs required again.

Newer gdbservers may be talking to older gdbs,
and older gdbs will flag a missing "end" as an error.
So just make "end" required again, and for compatibility
change the default field type to "bool".

gdb/ChangeLog:
2016-10-06  Doug Evans  <dje@google.com>

	* features/aarch64-core.xml (cpsr_flags): Elide "type" and specify
	"end" in all fields.
	* features/aarch64.c: Regenerate.
	* features/i386/32bit-mpx.xml (_bndcfgu): Specify type of "preserved"
	and "enabled" fields. Correct size of "enabled" field.
	* features/i386/64bit-mpx.xml (_bndcfgu): Specify type of "preserved"
	and "enabled" fields.
	* features/i386/i386-avx-mpx-linux.c: Regenerate.
	* features/i386/i386-avx-mpx.c: Regenerate.
	* features/i386/i386-avx512-linux.c: Regenerate.
	* features/i386/i386-avx512.c: Regenerate.
	* features/i386/i386-mpx-linux.c: Regenerate.
	* features/i386/i386-mpx.c: Regenerate.
	* features/arc-arcompact.c: Regenerate.
	* features/arc-v2.c: Regenerate.
	* xml-tdesc.c (tdesc_start_field): Require "end" spec.  Single bit
	fields default to "bool" type.

	Revert 2016-03-15  Doug Evans  <dje@google.com>
	* features/i386/32bit-core.xml (i386_eflags): Remove "end" spec.
	* features/i386/32bit-sse.xml (i386_eflags): Ditto.
	* features/i386/64bit-core.xml (i386_eflags): Ditto.
	* features/i386/64bit-sse.xml (i386_eflags): Ditto.
	* features/i386/x32-core.xml (i386_eflags): Ditto.

gdb/doc/ChangeLog:
2016-10-06  Doug Evans  <dje@google.com>

	* gdb.texinfo (Target Description Format): Update docs on "end"
	field spec and field default type.

gdb/testsuite/ChangeLog:
2016-10-06  Doug Evans  <dje@google.com>

	* gdb.xml/extra-regs.xml: Update, end field now required, default type
	for single bitfields is bool.
	* gdb.xml/tdesc-regs.exp: Ditto.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix a few gdb.base/jit-simple.exp problems
@ 2016-10-06 12:17 sergiodj+buildbot
  2016-10-06 13:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 12:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a122fbc307f35093b8fe038a8e6caa51b4d0dae ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5a122fbc307f35093b8fe038a8e6caa51b4d0dae

Fix a few gdb.base/jit-simple.exp problems

I noticed that we sometimes get this:

  (gdb) print &__jit_debug_descriptor
  $1 = (struct jit_descriptor *) 0x601040 <__jit_debug_descriptor>
  (gdb) PASS: gdb.base/jit-simple.exp: blah 1
  [...]
  (gdb) run
  [...]
  Starting program: build/gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple
  Unsupported JIT protocol version 4 in descriptor (expected 1)

  Breakpoint 2, main () at src/gdb/testsuite/gdb.base/jit-simple.c:36
  36        return 0;
  (gdb) print &__jit_debug_descriptor
  $2 = (struct jit_descriptor *) 0x601040 <__jit_debug_descriptor>
  (gdb) PASS: gdb.base/jit-simple.exp: blah 1

All tests PASSed, but note the "Unsupported JIT protocol version 4"
message.

Also notice that "__jit_debug_descriptor" has the same address before
and after the rerun, while the test is built in a way that should make
that address change between runs.

The test doesn't catch any of this because it doesn't compare
before/after addresses.

And then notice the "blah 1" test messages.  "blah" is clearly a WIP
message, but it should be at least "blah 2" the second time.  :-)

The reason this sometimes happens is that the test recompiles the
program and expects gdb to reload it automaticallyt on "run".  However,
if the original program and the new recompilation happen to be in the
same second, then gdb does not realize that the binary needs to be
reloaded.  (This is an old problem out of scope of this series.)  If
that happens, then GDB ends up using the wrong symbols for the program
that it spawns, reads the JIT descriptor out of the wrong address,
finds garbage, and prints that "unsupported version" notice.

Fix that in the same way gdb.base/reread.exp handles it -- by sleeping
one second before recompiling.

gdb/testsuite/ChangeLog:
2016-10-06  Pedro Alves  <palves@redhat.com>

	* gdb.base/jit-simple.exp (top level) Delete get_compiler_info
	call.
	(jit_run): Delete.
	(jit_test_reread): Use with_test_prefix.  Reload the main binary
	explicitly.  Compare the before/after addresses of the JIT
	descriptor.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR11094: JIT breakpoint is not properly recreated on reruns
@ 2016-10-06 13:14 sergiodj+buildbot
  2016-10-06 14:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a556533cf0256613c412b9627fa8b8edfa7674a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4a556533cf0256613c412b9627fa8b8edfa7674a

Fix PR11094: JIT breakpoint is not properly recreated on reruns

Even though this was supposedly in the gdb 7.2 timeframe, the testcase
in PR11094 crashes current GDB with a segfault:

  Program received signal SIGSEGV, Segmentation fault.
  0x00000000005ee894 in event_location_to_string (location=0x0) at
  src/gdb/location.c:412
  412       if (EL_STRING (location) == NULL)
  (top-gdb) bt
  #0  0x00000000005ee894 in event_location_to_string (location=0x0) at
  src/gdb/location.c:412
  #1  0x000000000057411a in print_breakpoint_location (b=0x18288e0, loc=0x0) at
  src/gdb/breakpoint.c:6201
  #2  0x000000000057483f in print_one_breakpoint_location (b=0x18288e0,
  loc=0x182cf10, loc_number=0, last_loc=0x7fffffffd258, allflag=1)
      at src/gdb/breakpoint.c:6473
  #3  0x00000000005751e1 in print_one_breakpoint (b=0x18288e0,
  last_loc=0x7fffffffd258, allflag=1) at
  src/gdb/breakpoint.c:6707
  #4  0x000000000057589c in breakpoint_1 (args=0x0, allflag=1, filter=0x0) at
  src/gdb/breakpoint.c:6947
  #5  0x0000000000575aa8 in maintenance_info_breakpoints (args=0x0, from_tty=0)
  at src/gdb/breakpoint.c:7026
  [...]

This is GDB trying to print the location spec of the JIT event
breakpoint, but that's an internal breakpoint without one.

If I add a NULL check, then we see that the JIT breakpoint is now
pending (because its location has shlib_disabled set):

  (gdb) maint info breakpoints
  Num     Type           Disp Enb Address            What
  [...]
  -8      jit events     keep y   <PENDING>           inf 1
  [...]

But that's incorrect.  GDB should have managed to recreate the JIT
breakpoint's location for the second run.  So the problem is
elsewhere.

The problem is that if the JIT loads at the same address on the second
run, we never recreate the JIT breakpoint, because we hit this early
return:

  static int
  jit_breakpoint_re_set_internal (struct gdbarch *gdbarch,
				  struct jit_program_space_data *ps_data)
  {
    [...]
    if (ps_data->cached_code_address == addr)
      return 0;

    [...]
      delete_breakpoint (ps_data->jit_breakpoint);
    [...]
    ps_data->jit_breakpoint = create_jit_event_breakpoint (gdbarch, addr);

Fix this by deleting the breakpoint and discarding the cached code
address when the objfile where the previous JIT breakpoint was found
is deleted/unloaded in the first place.

The test that was originally added for PR11094 doesn't trip on this
because:

  #1 - It doesn't test the case of the JIT descriptor's address _not_
       changing between reruns.

  #2 - And then it doesn't do "maint info breakpoints", or really
       anything with the JIT at all.

  #3 - and even then, to trigger the problem the JIT descriptor needs
       to be in a separate library, while the current test puts it in
       the main program.

The patch extends the test to cover all combinations of these
scenarios.

gdb/ChangeLog:
2016-10-06  Pedro Alves  <palves@redhat.com>

	* jit.c (free_objfile_data): Delete the JIT breakpoint and clear
	the cached code address.

gdb/testsuite/ChangeLog:
2016-10-06  Pedro Alves  <palves@redhat.com>

	* gdb.base/jit-simple-dl.c: New file.
	* gdb.base/jit-simple-jit.c: New file, factored out from ...
	* gdb.base/jit-simple.c: ... this.
	* gdb.base/jit-simple.exp (jit_run): Delete.
	(build_jit): New proc.
	(jit_test_reread): Recompile either the main program or the shared
	library, depending on what is being tested.  Skip changing address
	if caller wants to.  Compare before/after addresses.  If testing
	standalone, explicitly load the binary.  Test "maint info
	breakpoints".
	(top level): Add "standalone vs shared lib" and "change address"
	vs "same address" axes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression
@ 2016-10-06 15:03 sergiodj+buildbot
  2016-10-06 17:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 15:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c620c3e48d01e70c435c146905cab1a50382ce89 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: c620c3e48d01e70c435c146905cab1a50382ce89

stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression

Commit a038fa3e14a4 stack: check frame_unwind_caller_id adds a frame_id check to
frame_info and treats a missing frame_id as NOT_AVAILABLE_ERROR.  This causes a
regression in gdb.dwarf2/dw2-undefined-ret-addr.exp.

Treat a missing frame_id as OPTIMIZED_OUT_ERROR instead.

See also https://sourceware.org/ml/gdb-patches/2016-07/msg00273.html.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: solib-disc: Use `standard_output_file'
@ 2016-10-06 16:49 sergiodj+buildbot
  2016-10-06 19:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7470adbb872d5363580eb5e0a8dbb231c286ee4c ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 7470adbb872d5363580eb5e0a8dbb231c286ee4c

testsuite: solib-disc: Use `standard_output_file'

Correct a commit 2151ccc56c74 ("Always organize test artifacts in a
directory hierarchy") regression causing:

Running .../gdb/testsuite/gdb.base/solib-disc.exp ...
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.base/so-disc-shr.c.o: No such file or directory

by using `standard_output_file' to construct output file names
throughout.

	gdb/testsuite/
	* gdb.base/solib-disc.exp: Use `standard_output_file'
	throughout.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] mips-tdep: Rearrange comments in `mips_pseudo_register_type'
@ 2016-10-06 17:15 sergiodj+buildbot
  2016-10-06 20:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 17:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6912260f813b1493efefd27cbcb6a73d933accc ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: a6912260f813b1493efefd27cbcb6a73d933accc

mips-tdep: Rearrange comments in `mips_pseudo_register_type'

Rearrange comments throughout `mips_pseudo_register_type', placing them
ahead the condtionals they apply to consistently.

	gdb/
	* mips-tdep.c (mips_pseudo_register_type): Rearrange comments
	throughout.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] mips-tdep: Make FCRs always 32-bit
@ 2016-10-06 17:57 sergiodj+buildbot
  2016-10-06 21:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 17:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 78b86327b5301231005b08a7c589b2b58e6b4322 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 78b86327b5301231005b08a7c589b2b58e6b4322

mips-tdep: Make FCRs always 32-bit

Fix a regression from commit f8b73d13b7ca ("Target-described register
support for MIPS"),
<https://sourceware.org/ml/gdb-patches/2007-05/msg00340.html>,
<https://sourceware.org/ml/gdb-patches/2007-06/msg00256.html>, which
caused Floating Point Control Registers (FCRs) to be shown as 64-bit
with 64-bit targets.

This came from the legacy register format where all raw registers
matched the width of the architecture regardless of their actual size.
The correct size was then set in `mips_register_type' for cooked
registers presented to the user, which in the case of FCRs meant the
cooked size was always forced to 32 bits, reflecting their actual
hardware size, even though the raw format carried them in 64-bit
quantities on 64-bit targets.  The upper 32 bits carried in the raw FCR
format have always been don't-cares, not actually retrieved from
hardware and never written back.

With the introduction of XML register descriptions the layout of
previously defined raw registers has been preserved, so as to keep
existing register handling code unchanged and make it easier for GDB and
`gdbserver' to interact with each other whether neither, either or both
parties talking over RSP support XML register descriptions.  For the
XML-described case however `mips_register_type' is not used in raw to
cooked register conversion, so any special cases coded there are not
taken into account.

Instead a new function, `mips_pseudo_register_type', has been introduced
to handle size conversion, however lacking the special case for FCRs for
the Linux and the now defunct IRIX target.  The correct size has been
maintained for embedded targets however, due to the bundling of FCRs
with the embedded registers under the `rawnum >= MIPS_EMBED_FP0_REGNUM +
32' condition.

Add the missing case to `mips_pseudo_register_type' then, referring to
the FCR indices explicitly, and observing that between
`MIPS_EMBED_FP0_REGNUM + 32' and `MIPS_FIRST_EMBED_REGNUM' there is an
unused register slot whose contents are ignored so with the removal of
embedded FCRs from under that condition we don't have to care about it
and we can refer to the embedded registers starting from
MIPS_FIRST_EMBED_REGNUM instead.

Add a test case too so that we have means to check automatically that
the correct user-visible size of FCRs is maintained.

	gdb/
	* mips-tdep.c (mips_pseudo_register_type): Make FCRs always
	32-bit.

	gdb/testsuite/
	* gdb.arch/mips-fcr.exp: New test.
	* gdb.arch/mips-fcr.c: Source for the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] frame.h: Forward-declare struct ui_out
@ 2016-10-06 22:11 sergiodj+buildbot
  2016-10-07  4:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 22:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d73f9c4bab1a0ec82007f9d36b8a7bf5d34f7bf6 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: d73f9c4bab1a0ec82007f9d36b8a7bf5d34f7bf6

frame.h: Forward-declare struct ui_out

Fixes this failure when building in C mode.  I think it's relevant for master
as well, since it's a good practice to include (or forward-declare) what you
use.

In file included from ../../binutils-gdb/gdb/gdbarch.h:38:0,
                 from ../../binutils-gdb/gdb/defs.h:653,
                 from ../../binutils-gdb/gdb/dictionary.c:23:
../../binutils-gdb/gdb/frame.h:710:48: warning: struct ui_out declared inside parameter list will not be visible outside of this definition or declaration
 extern void print_stack_frame_to_uiout (struct ui_out *uiout,

gdb/ChangeLog:

	* frame.h: Forward-declare struct ui_out.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Remove some C compiler support leftovers
@ 2016-10-06 23:29 sergiodj+buildbot
  2016-10-07  7:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 23:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddb6d633875b76f9d772af901118233fc498253a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: ddb6d633875b76f9d772af901118233fc498253a

gdb: Remove some C compiler support leftovers

Remove some __cplusplus checks, inline EXPORTED_CONST, and update some comments.

gdb/ChangeLog:
2016-10-06  Pedro Alves  <palves@redhat.com>

	* cp-valprint.c (vtbl_ptr_name): Write "extern const" instead of
	EXPORTED_CONST.
	* stub-termcap.c: Remove __cplusplus checks.
	* common/common-defs.h [!__cplusplus] (EXTERN_C, EXTERN_C_PUSH,
	EXTERN_C_POP): Delete.
	* common/common-exceptions.h (GDB_XCPT_SJMP): Update comments.
	(GDB_XCPT) [!__cplusplus]: Delete.
	(throw_exception, throw_exception_sjlj): Update comments.
	* guile/guile-internal.h (as_a_scm_t_subr) [!__cplusplus]: Delete.
	* guile/guile.c (extension_language_guile): Write "extern const"
	instead of EXPORTED_CONST.
	* features/feature_to_c.sh: Don't emit !__cplusplus code.  Write
	"extern const" instead of EXPORTED_CONST.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Consolidate API of target_supports_multi_process
@ 2016-10-06 23:56 sergiodj+buildbot
  2016-10-07  8:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 23:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1fb77080fd74d11c0dbccf812ed98ffa0b3edc4e ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 1fb77080fd74d11c0dbccf812ed98ffa0b3edc4e

Consolidate API of target_supports_multi_process

This simple commit consolidates the API of
target_supports_multi_process.  Since both GDB and gdbserver use the
same function prototype, all that was needed was to move create this
prototype on gdb/target/target.h and turn the macros declared on
gdb/{,gdbserver/}target.h into actual functions.

Regtested (clean pass) on the BuildBot.

gdb/ChangeLog:
2016-10-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* target.c (target_supports_multi_process): New function, moved
	from...
	* target.h (target_supports_multi_process): ... here.  Remove
	macro.
	* target/target.h (target_supports_multi_process): New prototype.

gdb/gdbserver/ChangeLog:
2016-10-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* target.c (target_supports_multi_process): New function, moved
	from...
	* target.h (target_supports_multi_process): ... here.  Remove
	macro.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Pass link_info to _bfd_merge_private_bfd_data
@ 2016-10-07  2:07 sergiodj+buildbot
  2016-10-07 10:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  2:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50e03d47b77d5730f96f6b6bb66187654e66c797 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 50e03d47b77d5730f96f6b6bb66187654e66c797

Pass link_info to _bfd_merge_private_bfd_data

Most BFD linker functions take a bfd_link_info param, which reinforces
the fact that they are linker functions and allow access to linker
callbacks, eg. einfo for printing errors.  I was going to use einfo
for --fatal-warnings support before I decided a better way was the
patch commit 4519d071.

bfd/
	* targets.c (bfd_target <_bfd_merge_private_bfd_data>): Replace
	obfd param with struct bfd_link_info param.  Update all callers.
	* linker.c (bfd_merge_private_bfd_data): Likewise.
	(_bfd_generic_verify_endian_match): Likewise.
	* aoutf1.h (sunos_merge_private_bfd_data): Likewise.
	* coff-arm.c (coff_arm_merge_private_bfd_data): Likewise.
	* elf-attrs.c (_bfd_elf_merge_object_attributes): Likewise.
	* elf-bfd.h (_bfd_elf_ppc_merge_fp_attributes): Likewise.
	(_bfd_elf_merge_object_attributes): Likewise.
	* elf-m10300.c (_bfd_mn10300_elf_merge_private_bfd_data): Likewise.
	* elf-s390-common.c (elf_s390_merge_obj_attributes): Likewise.
	* elf32-arc.c (arc_elf_merge_private_bfd_data): Likewise.
	* elf32-arm.c (elf32_arm_merge_eabi_attributes): Likewise.
	(elf32_arm_merge_private_bfd_data): Likewise.
	* elf32-bfin.c (elf32_bfin_merge_private_bfd_data): Likewise.
	* elf32-cr16.c (_bfd_cr16_elf_merge_private_bfd_data): Likewise.
	* elf32-cris.c (cris_elf_merge_private_bfd_data): Likewise.
	* elf32-frv.c (frv_elf_merge_private_bfd_data): Likewise.
	* elf32-h8300.c (elf32_h8_merge_private_bfd_data): Likewise.
	* elf32-i370.c (i370_elf_merge_private_bfd_data): Likewise.
	* elf32-iq2000.c (iq2000_elf_merge_private_bfd_data): Likewise.
	* elf32-m32c.c (m32c_elf_merge_private_bfd_data): Likewise.
	* elf32-m32r.c (m32r_elf_merge_private_bfd_data): Likewise.
	* elf32-m68hc1x.c (_bfd_m68hc11_elf_merge_private_bfd_data): Likewise.
	* elf32-m68hc1x.h (_bfd_m68hc11_elf_merge_private_bfd_data): Likewise.
	* elf32-m68k.c (elf32_m68k_merge_private_bfd_data): Likewise.
	* elf32-mcore.c (mcore_elf_merge_private_bfd_data): Likewise.
	* elf32-mep.c (mep_elf_merge_private_bfd_data): Likewise.
	* elf32-msp430.c (elf32_msp430_merge_mspabi_attributes): Likewise.
	(elf32_msp430_merge_private_bfd_data): Likewise.
	* elf32-mt.c (mt_elf_merge_private_bfd_data): Likewise.
	* elf32-nds32.c (nds32_elf_merge_private_bfd_data): Likewise.
	* elf32-nios2.c (nios2_elf32_merge_private_bfd_data): Likewise.
	* elf32-or1k.c (elf32_or1k_merge_private_bfd_data): Likewise.
	* elf32-ppc.c (_bfd_elf_ppc_merge_fp_attributes): Likewise.
	(ppc_elf_merge_obj_attributes): Likewise.
	(ppc_elf_merge_private_bfd_data): Likewise.
	* elf32-rl78.c (rl78_elf_merge_private_bfd_data): Likewise.
	* elf32-rx.c (rx_elf_merge_private_bfd_data): Likewise.
	* elf32-s390.c (elf32_s390_merge_private_bfd_data): Likewise.
	* elf32-score.c (s3_elf32_score_merge_private_bfd_data): Likewise.
	(elf32_score_merge_private_bfd_data): Likewise.
	* elf32-score.h (s7_elf32_score_merge_private_bfd_data): Likewise.
	* elf32-score7.c (s7_elf32_score_merge_private_bfd_data): Likewise.
	* elf32-sh.c (sh_merge_bfd_arch, sh_elf_merge_private_data): Likewise.
	* elf32-sh64.c (sh64_elf_merge_private_data): Likewise.
	* elf32-sparc.c (elf32_sparc_merge_private_bfd_data): Likewise.
	* elf32-tic6x.c (elf32_tic6x_merge_attributes): Likewise.
	(elf32_tic6x_merge_private_bfd_data): Likewise.
	* elf32-v850.c (v850_elf_merge_private_bfd_data): Likewise.
	* elf32-vax.c (elf32_vax_merge_private_bfd_data): Likewise.
	* elf32-visium.c (visium_elf_merge_private_bfd_data): Likewise.
	* elf32-xtensa.c (elf_xtensa_merge_private_bfd_data): Likewise.
	* elf64-ia64-vms.c (elf64_ia64_merge_private_bfd_data): Likewise.
	* elf64-ppc.c (ppc64_elf_merge_private_bfd_data): Likewise.
	* elf64-s390.c (elf64_s390_merge_private_bfd_data): Likewise.
	* elf64-sh64.c (sh_elf64_merge_private_data): Likewise.
	* elf64-sparc.c (elf64_sparc_merge_private_bfd_data): Likewise.
	* elfnn-aarch64.c (elfNN_aarch64_merge_private_bfd_data): Likewise.
	* elfnn-ia64.c (elfNN_ia64_merge_private_bfd_data): Likewise.
	* elfxx-mips.c (mips_elf_merge_obj_e_flags): Likewise.
	(mips_elf_merge_obj_attributes): Likewise.
	(_bfd_mips_elf_merge_private_bfd_data): Likewise.
	* elfxx-mips.h (_bfd_mips_elf_merge_private_bfd_data): Likewise.
	* elfxx-sparc.c (_bfd_sparc_elf_merge_private_bfd_data): Likewise.
	* elfxx-sparc.h (_bfd_sparc_elf_merge_private_bfd_data): Likewise.
	* elfxx-target.h (bfd_elfNN_bfd_merge_private_bfd_data): Likewise.
	* elfxx-tilegx.c (_bfd_tilegx_elf_merge_private_bfd_data): Likewise.
	* elfxx-tilegx.h (_bfd_tilegx_elf_merge_private_bfd_data): Likewise.
	* libbfd-in.h (_bfd_generic_bfd_merge_private_bfd_data): Likewise.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
ld/
	* ldlang.c (lang_check): Update bfd_merge_private_bfd_data call.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix gdb.Value->python conversion for large unsigned ints.
@ 2016-10-07  4:51 sergiodj+buildbot
  2016-10-07  6:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  4:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33fa2c6e1b1e63599156f7d79de8c0a6ea69c8af ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 33fa2c6e1b1e63599156f7d79de8c0a6ea69c8af

Fix gdb.Value->python conversion for large unsigned ints.

gdb/ChangeLog:

	* python/py-value.c (valpy_long): Handle unsigned values.

gdb/testsuite/ChangeLog:

	* gdb.python/py-value.exp (test_value_creation): Add test for large
	unsigned 64-bit value.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd_merge_private_bfd_data tidy
@ 2016-10-07  7:33 sergiodj+buildbot
  2016-10-07  9:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  7:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1047201fd0f402428bb3331638a198413f97f476 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 1047201fd0f402428bb3331638a198413f97f476

bfd_merge_private_bfd_data tidy

bfd_merge_private_bfd_data and _bfd_generic_verify_endian_match are
linker functions, so move them to linker.c.

bfd/
	* Makefile.am (LIBBFD_H_FILES): Update.
	* doc/Makefile.am (LIBBFD_H_DEP): Likewise.
	* cpu-sh.c (sh_merge_bfd_arch): Move to..
	* elf32-sh.c: ..here, and make static.
	* elf32-arc.c (arc_elf_merge_private_bfd_data): Delete extraneous
	error.
	* elf32-cris.c (cris_elf_merge_private_bfd_data): Don't call
	_bfd_generic_verify_endian_match.
	* elf32-microblaze.c (microblaze_elf_merge_private_bfd_data): Delete.
	(bfd_elf32_bfd_merge_private_bfd_data): Define as
	_bfd_generic_verify_endian_match.
	* elf32-mt.c (mt_elf_merge_private_bfd_data): Don't test
	boolean == FALSE.
	* elf32-xgate.c (_bfd_xgate_elf_merge_private_bfd_data): Delete.
	(bfd_elf32_bfd_merge_private_bfd_data): Don't define.
	* elf32-xgate.h (_bfd_xgate_elf_merge_private_bfd_data): Delete.
	* libbfd-in.h (_bfd_generic_verify_endian_match): Delete.
	* libbfd.c (_bfd_generic_verify_endian_match): Move to..
	* linker.c: ..here, and make internal.
	* bfd.c (bfd_merge_private_bfd_data): Move to..
	* linker.c: ..here.
	* Makefile.in: Regenerate.
	* doc/Makefile.in: Regenerate.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
opcodes/
	* sh-opc.h (sh_merge_bfd_arch): Delete prototype.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ui-out.c: Remove unused parameter to push_level
@ 2016-10-09  0:26 sergiodj+buildbot
  2016-10-09  0:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-09  0:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49d06418ada11004ca1cdc0ec5847358e83fc67a ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 49d06418ada11004ca1cdc0ec5847358e83fc67a

ui-out.c: Remove unused parameter to push_level

The parameter "id" is unused.

gdb/ChangeLog:

	* ui-out.c (push_level): Remove "id" parameter.
	(ui_out_begin): Update call.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove v850_dbtrap_breakpoint_from_pc
@ 2016-10-10  9:44 sergiodj+buildbot
  2016-10-10  9:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-10  9:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff12a6593a1675aa9ba5340aa2984af19cf8966c ***

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

Remove v850_dbtrap_breakpoint_from_pc

v850 has two functions to install to gdbarch_breakpoint_from_pc,
and it selects one according to info.bfd_arch_info->mach.  However,
we can select the kind/length of breakpoint instruction inside
v850_breakpoint_from_pc by gdbarch_bfd_arch_info (gdbarch)->mach.
This patch is to do that, and remove v850_dbtrap_breakpoint_from_pc.

gdb:

2016-08-30  Yao Qi  <yao.qi@linaro.org>

	* v850-tdep.c (v850_breakpoint_from_pc): Use the right
	breakpoint instruction.
	(v850_dbtrap_breakpoint_from_pc): Remove.
	(v850_gdbarch_init): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Rename 'arch' by 'gdbarch' in m32c_gdbarch_init
@ 2016-10-10 10:37 sergiodj+buildbot
  2016-10-10 10:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-10 10:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97ce08cb8071bf9a8df6c99cdf8e9fbf1911f3f5 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 97ce08cb8071bf9a8df6c99cdf8e9fbf1911f3f5

Rename 'arch' by 'gdbarch' in m32c_gdbarch_init

This patch renames local 'arch' by 'gdbarch' in m32c_gdbarch_init, so
that I can use macros in the following patch.

gdb:

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

	* m32c-tdep.c (m32c_gdbarch_init): Rename local 'arch' by
	'gdbarch'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Share enum arm_breakpoint_kinds
@ 2016-10-10 11:41 sergiodj+buildbot
  2016-10-10 11:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-10 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1078bea751d48e8846b91542d91647f1e0aed8d ***

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

Share enum arm_breakpoint_kinds

This patch shares "enum arm_breakpoint_kinds", and use ARM_BP_KIND_THUMB2
in GDB.

gdb:

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

	* arch/arm.h (enum arm_breakpoint_kinds): New.
	* arm-tdep.c (arm_remote_breakpoint_from_pc): Use
	ARM_BP_KIND_THUMB2.

gdb/gdbserver:

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

	* linux-aarch32-low.c (enum arm_breakpoint_kinds): Remove.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo
@ 2016-10-11 10:42 sergiodj+buildbot
  2016-10-11 11:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93562a343c26f67d2bd0e93cceb18a0a793087c2 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 93562a343c26f67d2bd0e93cceb18a0a793087c2

[AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo

opcode/
	PR target/20666
	* aarch64-asm.c (convert_bfc_to_bfm): Fix dest index.

gas/
	* testsuite/gas/aarch64/alias-2.d: Update expected results.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Use standard_output_file
@ 2016-10-11 15:00 sergiodj+buildbot
  2016-10-11 15:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16c85b5d14a04c275d3cb39b2029f3dc0f708531 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 16c85b5d14a04c275d3cb39b2029f3dc0f708531

testsuite: Use standard_output_file

gdb/testsuite/ChangeLog
2016-10-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/powerpc-prologue.exp: Use standard_output_file.
	* gdb.arch/ppc64-symtab-cordic.exp: Likewise.
	* gdb.arch/vsx-regs.exp: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix gdb.arch/powerpc-prologue.c compilation
@ 2016-10-11 17:27 sergiodj+buildbot
  2016-10-11 17:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 17:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f1a8fc4df2244f548d55fbecce20b7cd6f90e16 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 8f1a8fc4df2244f548d55fbecce20b7cd6f90e16

testsuite: Fix gdb.arch/powerpc-prologue.c compilation

gcc-6.2.1

gdb compile failed, gdb/testsuite/gdb.arch/powerpc-prologue.c: In function 'main':
gdb/testsuite/gdb.arch/powerpc-prologue.c:32:3: warning: implicit declaration of function 'optimized_1' [-Wimplicit-function-declaration]
   optimized_1 ();
   ^~~~~~~~~~~

gdb/testsuite/ChangeLog
2016-10-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.arch/powerpc-prologue.c (optimized_1): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Track FP registers in prologue analyzer
@ 2016-10-12 11:51 sergiodj+buildbot
  2016-10-12 12:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 187f5d00acf0ffe5390f282fd4d6285bcd6fccb9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 187f5d00acf0ffe5390f282fd4d6285bcd6fccb9

[AArch64] Track FP registers in prologue analyzer

We don't track FP registers in aarch64 prologue analyzer, so this causes
an internal error when FP registers are saved by "stp" instruction in
prologue (stp	d8, d9, [sp,#128]),

 tbreak _Unwind_RaiseException^M
 aarch64-tdep.c:335: internal-error: CORE_ADDR aarch64_analyze_prologue(gdbarch*, CORE_ADDR, CORE_ADDR, aarch64_prologue_cache*): Assertion `inst.operands[0].type == AARCH64_OPND_Rt' failed.^M
 A problem internal to GDB has been detected,

This patch teaches GDB to track FP registers (D registers) in prologue
analyzer.

gdb:

2016-10-12  Yao Qi  <yao.qi@linaro.org>

	PR tdep/20682
	* aarch64-tdep.c: Replace 32 with AARCH64_D_REGISTER_COUNT.
	(aarch64_analyze_prologue): Extend array 'regs' for D registers.
	Assert that operand 0 and 1 can be X or D registers.  Update
	register number for D registers.  Update registers in frame
	cache.
	* aarch64-tdep.h (AARCH64_D_REGISTER_COUNT): New macro.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] arc: Add evaluation of long jump targets
@ 2016-10-12 13:32 sergiodj+buildbot
  2016-10-12 15:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaf43c4882f827d9f778b40dcdb93566f765f5f9 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: aaf43c4882f827d9f778b40dcdb93566f765f5f9

arc: Add evaluation of long jump targets

Standard get_longjmp_target implementation, similar to what is in arm-tdep.c.
Actual value of jb_pc should be set in init_osabi methods of particular OS/ABI
implementations.

gdb/ChangeLog:

	* arc-tdep.h (struct gdbarch_tdep) <jb_pc>: New field.
	* arc-tdep.c (arc_get_longjmp_target): New function.
	(arc_gdbarch_init): Set get_longjmp_target if jb_pc is non-negative.
	(arc_dump_tdep): Print jb_pc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fixup gdb.python/py-value.exp for bare-metal aarch64-elf
@ 2016-10-12 15:51 sergiodj+buildbot
  2016-10-12 17:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dac951e11030b43b17f52df8bdfa7432e4bf73c ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 4dac951e11030b43b17f52df8bdfa7432e4bf73c

Fixup gdb.python/py-value.exp for bare-metal aarch64-elf

I noticed that testing aarch64-elf gdb with a physical board
ran into issues with gdb.python/py-value.exp. Further investigation showed
that we were actually trying to dereference a NULL pointer (argv) when trying
to access argv[0].

Being bare-metal, argv is not guaranteed to be valid. So we need to make sure
argv is sane before accessing argv[0].

The following patch fixes up the test program to check for a NULL argv and also
improves the testcase a bit so it doesn't have to work with a hardcoded argc
value.

Regression-tested on x86-64 Ubuntu 16.04.

gdb/testsuite/ChangeLog:

2016-10-12  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.python/py-value.c (main): Check if argv is NULL before using it.
	* gdb.python/py-value.exp (test_value_in_inferior): Don't use hardcoded
	argc values.
	Add 1 to argc so we guarantee distinct initial/modified argc values.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] arc: Add support for Newlib
@ 2016-10-12 16:00 sergiodj+buildbot
  2016-10-12 16:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-12 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a2f4826907de97b089295000a67d2497aa94c99 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: 4a2f4826907de97b089295000a67d2497aa94c99

arc: Add support for Newlib

Add support for Newlib as an OS/ABI.  The only thing that is specific to it
relatively to "generic" baremetal target is location of PC register in jump
buffer for longjump support.

Sniffer uses .ivt section to decide if ELF file is for ARC Newlib or not.

gdb/ChangeLog:

	* arc-newlib-tdep.c: New file.
	* configure.tgt: Add newlib support for ARC.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Convert tid_range_parser and get_number_or_range to classes
@ 2016-10-13  1:21 sergiodj+buildbot
  2016-10-13  1:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  1:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfd282882d534cd4f48e2fc29d4ce0923c52352b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: bfd282882d534cd4f48e2fc29d4ce0923c52352b

Convert tid_range_parser and get_number_or_range to classes

This converts tid_range_parser and get_number_or_range to be classes.
The various tid_range_parser_* and get_number_or_range_* functions
become methods on the respective classes.  Then it updates the users
to follow.

The rationale for the change is that this provides better
encapsulation.  For example, this forced me to think of a better
interface between tid_range_parser and get_number_or_range, since the
former peeked into the latter's internals a bit too much.  That ended
up resulting mostly in these two not-just-straight-1-1 changes:

  void
 -tid_range_parser_skip (struct tid_range_parser *parser)
 +tid_range_parser::skip_range ()
  {
 ...

 -  tid_range_parser_init (parser, parser->range_parser.end_ptr,
 -			 parser->default_inferior);
 +  m_range_parser.skip_range ();
 +  init (m_range_parser.string (), m_default_inferior);
  }

 and:

    /* If we successfully parsed a thread number or finished parsing a
       thread range, switch back to assuming the next TID is
       inferior-qualified.  */
 -  if (parser->range_parser.end_ptr == NULL
 -      || parser->range_parser.string == parser->range_parser.end_ptr)
 +  if (!m_range_parser.in_range ())
      {

For the same reason (encapsulation), this moves the enum
tid_range_state definition to within the tid_parser class's scope,
since that is private implementation detail.

While at it, switch to use "bool" for booleans.

gdb/ChangeLog:
2016-10-13  Pedro Alves  <palves@redhat.com>
	    Tom Tromey  <tom@tromey.com>

	* tid-parse.h (tid_range_parser): New class.
	(enum tid_range_state): Move into tid_range_parser's scope.
	Remove TID_RANGE_ prefix from all values.
	(tid_range_parser_get_tid, tid_range_parser_get_tid_range)
	(tid_range_parser_star_range, tid_range_parser_finished)
	(tid_range_parser_skip, tid_range_parser_qualified): Don't
	declare.
	(tid_is_in_list): Update comment.
	* tid-parse.c (tid_range_parser::tid_range_parser): New.
	(init, finished, get_string, skip, tid_is_qualified)
	(get_tid_or_range, get_tid_range, get_tid, star_range): Rename;
	turn into methods.
	(tid_is_in_list): Adjust.
	* cli/cli-utils.h (number_or_range_parser): New class.
	(init_number_or_range, get_number_or_range)
	(number_range_setup_range): Don't declare.
	* cli/cli-utils.c
	(number_or_range_parser::number_or_range_parser): New.
	(init_number_or_range, get_number_or_range)
	(number_range_setup_range): Rename; turn into methods.
	(number_is_in_list): Adjust.
	* breakpoint.c (map_breakpoint_numbers): Adjust.  Use bool.
	(trace_pass_command, get_tracepoint_by_number): Adjust.
	* breakpoint.h (get_tracepoint_by_number): Adjust.
	* inferior.c (detach_inferior_command, kill_inferior_command)
	(remove_inferior_command): Adjust.
	* linespec.c (decode_line_2): Adjust.
	* memattr.c (mem_enable_command, mem_disable_command)
	(mem_delete_command): Adjust.
	* printcmd.c (map_display_numbers): Adjust.
	* reverse.c (delete_bookmark_command, bookmarks_info): Adjust.
	* thread.c (thread_apply_command): Adjust.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change selttest.c to use use std::vector
@ 2016-10-13  2:25 sergiodj+buildbot
  2016-10-13  2:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  2:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 816d7b53047bca81c226990bc9248d59d80d4b8b ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 816d7b53047bca81c226990bc9248d59d80d4b8b

Change selttest.c to use use std::vector

This patch changes selftest.c to use std::vector rather than VEC.
I think this is a small net plus.

2016-10-12  Tom Tromey  <tom@tromey.com>

	* selftest.c: Include <vector>, not "vec.h".
	(self_test_function_ptr): Remove.
	(tests): Now a std::vector.
	(register_self_test, run_self_tests): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Turn wchar iterator into a class
@ 2016-10-13  2:59 sergiodj+buildbot
  2016-10-13  3:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  2:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cda6c55bd399a8892d62178d4daeb074def909e0 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cda6c55bd399a8892d62178d4daeb074def909e0

Turn wchar iterator into a class

This changes wchar_iterator from charset.c into a real C++ class, then
updates the users to use the class.  This lets us remove some cleanups
in favor of the class' destructor.

2016-10-12  Tom Tromey  <tom@tromey.com>

	* valprint.c (generic_emit_char, count_next_character)
	(generic_printstr): Update.
	* charset.c (struct wchar_iterator): Move to charset.h.
	(wchar_iterator::wchar_iterator): Rename from
	make_wchar_iterator, turn into a constructor.
	(wchar_iterator::~wchar_iterator): Rename from
	do_cleanup_iterator, turn into a destructor.
	(make_cleanup_wchar_iterator): Remove.
	(wchar_iterator::iterate): Rename from wchar_iterate.  Remove
	"iter" argument.  Update.
	* charset.h: Include <vector>.
	(class wchar_iterator): New class, from old struct
	wchar_iterator.
	(make_wchar_iterator, make_cleanup_wchar_iterator): Don't
	declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove unnecessary null_cleanup
@ 2016-10-13  4:50 sergiodj+buildbot
  2016-10-13  4:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  4:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1a760cbb796b62f18ff6b81a189fd261809ef74 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d1a760cbb796b62f18ff6b81a189fd261809ef74

Remove unnecessary null_cleanup

This patch removes an unnecessary null_cleanup.

2016-10-12  Tom Tromey  <tom@tromey.com>

	* tracepoint.c (trace_dump_command): Remove unnecessary
	null_cleanup.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string in macho_symfile_read_all_oso
@ 2016-10-13  5:24 sergiodj+buildbot
  2016-10-13  5:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13  5:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af533a5f8b149bfa1394ab04c3947e97dd507a33 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: af533a5f8b149bfa1394ab04c3947e97dd507a33

Use std::string in macho_symfile_read_all_oso

This changes macho_symfile_read_all_oso to use std::string.  This
avoids a cleanup.

2016-10-12  Tom Tromey  <tom@tromey.com>

	* machoread.c (macho_symfile_read_all_oso): Use std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Skip testing structures with floating points
@ 2016-10-13 14:54 sergiodj+buildbot
  2016-10-13 15:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 14:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62df7e210ebf096dc09ad14d9316fcda0f6217f7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 62df7e210ebf096dc09ad14d9316fcda0f6217f7

Skip testing structures with floating points

This patch skips some tests related to floating point in structs.exp
if gdb_skip_float_test return false.

gdb/testsuite:

2016-10-13  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/structs.exp: Invoke gdb_skip_float_test, and do
	floating point tests if $skip_float_test is false.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ARI: Remove true/false checks
@ 2016-10-13 17:38 sergiodj+buildbot
  2016-10-13 18:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 17:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f2e9c5e3b0ef55cb0ab180dd0c82c7954a73e1a ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1f2e9c5e3b0ef55cb0ab180dd0c82c7954a73e1a

ARI: Remove true/false checks

These don't make sense with C++.

gdb/ChangeLog:
2016-10-13  Pedro Alves  <palves@redhat.com>

	* contrib/ari/gdb_ari.sh (boolean): Suggest bool instead.
	(false, true): Remove checks.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include strings.h where available
@ 2016-10-14  7:30 sergiodj+buildbot
  2016-10-14  7:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-14  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ffc1bb12a22e548835c9291871ad0eb68b7f6f0 ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 8ffc1bb12a22e548835c9291871ad0eb68b7f6f0

Include strings.h where available

gdb/ChangeLog

2016-10-14  Eli Zaretskii  <eliz@gnu.org>

	* common/common-defs.h [HAVE_STRINGS_H]: Include strings.h if
	available, to get prototypes of 'strcasecmp' and 'strncasecmp'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix set sysroot command on AIX
@ 2016-10-14 13:25 sergiodj+buildbot
  2016-10-14 13:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 13:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 754c39c2f32a796ad9983836deb7c4429c808e48 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 754c39c2f32a796ad9983836deb7c4429c808e48

Fix set sysroot command on AIX

set sysroot command on AIX has no effect if a program depends on shared
library archives (.a).  Fixed by using solib_find and solib_bfd_fopen
instead of gdb_bfd_open in solib_aix_bfd_open.

gdb/
2016-10-14  Sangamesh Mallayya  <sangamesh.swamy@in.ibm.com>
	    Ulrich Weigand  <uweigand@de.ibm.com>

	* solib-aix.c (solib_aix_bfd_open): Call solib_find so that sysroot
	path is set properly if program has a dependency on .a archive and
	sysroot is set via set sysroot command.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h
@ 2016-10-14 16:29 sergiodj+buildbot
  2016-10-14 16:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d118ee3761bcf0c861a75e454d0c2b741fccb956 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d118ee3761bcf0c861a75e454d0c2b741fccb956

Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h

So that GDB and other projects that share the top level can use them.

Bootstrapped with all default languages + jit on x86-64 Fedora 23.

gcc/ChangeLog:
2016-10-14  Pedro Alves  <palves@redhat.com>

	* coretypes.h (OVERRIDE, FINAL): Delete, moved to
	include/ansidecl.h.

include/ChangeLog:
2016-10-14  Pedro Alves  <palves@redhat.com>

	* ansidecl.h (GCC_FINAL): Delete.
	(OVERRIDE, FINAL): New, moved from gcc/coretypes.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] FINAL/OVERRIDE: Define to empty on g++ < 4.7
@ 2016-10-14 16:54 sergiodj+buildbot
  2016-10-14 17:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-14 16:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4f6af8ee2ea97b8c6f2bca1c2fd728683e68ef5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b4f6af8ee2ea97b8c6f2bca1c2fd728683e68ef5

FINAL/OVERRIDE: Define to empty on g++ < 4.7

final/override were only implemented in g++ 4.7.

include/ChangeLog
2016-10-14  Pedro Alves  <palves@redhat.com>

	* ansidecl.h [__cplusplus >= 201103 && GCC_VERSION < 4007] (FINAL,
	OVERRIDE): Define as empty.
	[__cplusplus < 201103 && GCC_VERSION < 4007] (FINAL): Define as
	__final.
	[__cplusplus < 201103 && GCC_VERSION >= 4007] (OVERRIDE): Define as
	empty.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Sync libiberty sources with gcc mainline.
@ 2016-10-17  9:46 sergiodj+buildbot
  2016-10-17  9:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-17  9:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41f225defe891ff71d3c8a149cdc1ed8f3a64c5c ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 41f225defe891ff71d3c8a149cdc1ed8f3a64c5c

Sync libiberty sources with gcc mainline.

2016-09-19  Andrew Stubbs  <ams@codesourcery.com>

	* pex-win32.c (argv_to_cmdline): Quote zero-length parameters.
	* testsuite/test-pexecute.c (main): Insert check for zero-length parameters.

2016-09-10  Mark Wielaard  <mjw@redhat.com>

	* cp-demangle.c (d_substitution): Change struct demangle_component
	variable name from c to dc.

2016-08-12  Marek Polacek  <polacek@redhat.com>

	PR c/7652
	* cp-demangle.c (d_print_mod): Add FALLTHRU.

2016-08-04  Marcel B?hme  <boehme.marcel@gmail.com>

	PR c++/71696
	* cplus-dem.c: Prevent infinite recursion when there is a cycle
	in the referencing of remembered mangled types.
	(work_stuff): New stack to keep track of the remembered mangled
	types that are currently being processed.
	(push_processed_type): New method to push currently processed
	remembered type onto the stack.
	(pop_processed_type): New method to pop currently processed
	remembered type from the stack.
	(work_stuff_copy_to_from): Copy values of new variables.
	(delete_non_B_K_work_stuff): Free stack memory.
	(demangle_args): Push/Pop currently processed remembered type.
	(do_type): Do not demangle a cyclic reference and push/pop
	referenced remembered type.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update list of ELF machine numbers.
@ 2016-10-17 11:03 sergiodj+buildbot
  2016-10-17 11:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d91379408b87b6d0c1cd4bc2880b530cc4ec721 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6d91379408b87b6d0c1cd4bc2880b530cc4ec721

Update list of ELF machine numbers.

include	* elf/common.h (DT_SYMTAB_SHNDX): Define.
	(EM_CLOUDSHIELD, EM_COREA_1ST, EM_COREA_2ND, EM_OPEN8): Define.
	(EM_VIDEOCORE5, EM_56800EX, EM_BA1, EM_BA2, EM_XCORE): Define.
	(EM_MCHP_PIC, EM_KM32, EM_KMX32, EM_KMX16, EM_KMX8): Define.
	(EM_KVARC, EM_CDP, EM_COGE, EM_COOL, EM_NORC): Define.
	(EM_CSR_KALIMBA, EM_Z80, EM_AMDGPU, EM_RISCV): Define.
	(ELFOSABI_OPENVOS): Define.
	(GRP_MASKOS, GRP_MASKPROC): Define.

binutils	* readelf.c (get_dynamic_type): Add DT_SYMTAB_SHNDX.
	(get_machine_type): Add EM_CLOUDSHIELD, EM_COREA_1ST,
	EM_COREA_2ND, EM_OPEN8, EM_VIDEOCORE5, EM_56800EX, EM_BA1, EM_BA2,
	EM_XCORE, EM_MCHP_PIC, EM_KM32, EM_KMX32, EM_KMX16, EM_KMX8,
	EM_KVARC, EM_CDP, EM_COGE, EM_COOL, EM_NORC, EM_CSR_KALIMBA,
	EM_Z80, EM_AMDGPU, EM_RISCV.
	(get_osabi_name): Add ELFOSABI_CLOUDABI and ELFOSABI_OPENVS.
	(get_group_flags): Update to handle flags in the
	GRP_MASKOS and GRP_MASKPROC ranges.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Removed pseudo invalid instructions opcodes.
@ 2016-10-17 13:56 sergiodj+buildbot
  2016-10-17 13:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT decf5bd1570be3de10aeab99869a9548d17b1354 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: decf5bd1570be3de10aeab99869a9548d17b1354

Removed pseudo invalid instructions opcodes.

The disassember was generating invXXX instructions for cases when in reality we
had llockd or scondd instrutions.

opcodes/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
	arc-tbl.h: Removed any "inv.+" instructions from the table.

gas/ChangeLog:

    Cupertino Miranda  <cmiranda@synopsys.com>
        testsuite/arc/dis-inv.s: Test to validate patch.
        testsuite/arc/dis-inv.d: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Fix phony iconv build
@ 2016-10-17 16:34 sergiodj+buildbot
  2016-10-17 17:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5562a44eb490b5777c9e786971907c0727d88495 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5562a44eb490b5777c9e786971907c0727d88495

gdb: Fix phony iconv build

Cross building gdb for mingw32 on Fedora 23 fails with:

  x86_64-w64-mingw32-g++ -g -O2  [...]  ../../src/gdb/charset.c
  In file included from ../../src/gdb/charset.c:21:0:
  ../../src/gdb/charset.h:134:3: error: 'iconv_t' does not name a type
     iconv_t m_desc;
     ^
  ../../src/gdb/charset.c: In constructor 'wchar_iterator::wchar_iterator(const gdb_byte*, size_t, const char*, size_t)':
  ../../src/gdb/charset.c:600:3: error: 'm_desc' was not declared in this scope
     m_desc = iconv_open (INTERMEDIATE_ENCODING, charset);
     ^
  ../../src/gdb/charset.c: In destructor 'wchar_iterator::~wchar_iterator()':
  ../../src/gdb/charset.c:607:7: error: 'm_desc' was not declared in this scope
     if (m_desc != (iconv_t) -1)
	 ^
  ../../src/gdb/charset.c: In member function 'int wchar_iterator::iterate(wchar_iterate_result*, gdb_wchar_t**, const gdb_byte**, size_t*)':
  ../../src/gdb/charset.c:633:25: error: 'm_desc' was not declared in this scope
	 size_t r = iconv (m_desc, &inptr, &m_bytes, &outptr, &out_avail);
			   ^

This is a regression caused by commit cda6c55bd399 (Turn wchar
iterator into a class).  The problem is that iconv_t is now exposed in
gdb/charset.h, while before it was only used in gdb/charset.c.

gdb/charset.c, under #ifdef PHONY_ICONV, does:

 #undef iconv_t
 #define iconv_t int

So it seems the simplest is to use 'int' in the header file too.

gdb/ChangeLog:
2016-10-17  Pedro Alves  <palves@redhat.com>

	* charset.h (class wchar_iterator) [PHONY_ICONV] <m_desc>: Use
	'int' as type.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix comment in mi-trace-save.exp
@ 2016-10-17 21:50 sergiodj+buildbot
  2016-10-17 23:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ccdb4324b0dc9fa46ee7cad9b370f8c7c370c3b ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 3ccdb4324b0dc9fa46ee7cad9b370f8c7c370c3b

Fix comment in mi-trace-save.exp

This fixes a comment I forgot to update in the previous patch.

gdb/testsuite/ChangeLog:

	* gdb.trace/mi-trace-save.exp (test_trace_save_wrong_num_args):
	Update comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix duplicate test message in mi-trace-save.exp
@ 2016-10-17 23:24 sergiodj+buildbot
  2016-10-18  0:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-17 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e42b25a0407fbbf3529815f69bd56a61b1821295 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: e42b25a0407fbbf3529815f69bd56a61b1821295

Fix duplicate test message in mi-trace-save.exp

gdb/testsuite/ChangeLog:

	* gdb.trace/mi-trace-save.exp (test_trace_save_wrong_num_args):
	Change test message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix gcc_compiled for gcc 6 & 7
@ 2016-10-24 18:51 sergiodj+buildbot
  2016-10-26  0:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-24 18:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f90fd8c2f17c7631915103ce5b760830a156ee93 ***

Author(s): Jan Kratochvil <jan.kratochvil@redhat.com>, Nick Clifton <nickc@redhat.com>, Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f90fd8c2f17c7631915103ce5b760830a156ee93

commit f90fd8c2f17c7631915103ce5b760830a156ee93
Author:     Jan Kratochvil <jan.kratochvil@redhat.com>
AuthorDate: Thu Oct 20 21:58:54 2016 +0200
Commit:     Jan Kratochvil <jan.kratochvil@redhat.com>
CommitDate: Thu Oct 20 21:58:54 2016 +0200

    testsuite: Fix gcc_compiled for gcc 6 & 7
    
    gdb/testsuite/ChangeLog
    2016-10-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
    
    	* lib/gdb.exp (get_compiler_info): Generalize gcc_compile regexp.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 5409537..c8709b7 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2016-10-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
+
+	* lib/gdb.exp (get_compiler_info): Generalize gcc_compile regexp.
+
 2016-10-19  Maciej W. Rozycki  <macro@imgtec.com>
 
     	* gdb.base/killed-outside.exp: Remove $options from a call to
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 378eea0..7d9b198 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -3290,12 +3290,8 @@ proc get_compiler_info {{arg ""}} {
     }
 
     # Set the legacy symbols.
-    set gcc_compiled     0
-    if { [regexp "^gcc-1-" "$compiler_info" ] } { set gcc_compiled 1 }
-    if { [regexp "^gcc-2-" "$compiler_info" ] } { set gcc_compiled 2 }
-    if { [regexp "^gcc-3-" "$compiler_info" ] } { set gcc_compiled 3 }
-    if { [regexp "^gcc-4-" "$compiler_info" ] } { set gcc_compiled 4 }
-    if { [regexp "^gcc-5-" "$compiler_info" ] } { set gcc_compiled 5 }
+    set gcc_compiled 0
+    regexp "^gcc-(\[0-9\]+)-" "$compiler_info" matchall gcc_compiled
 
     # Log what happened.
     verbose -log "get_compiler_info: $compiler_info"


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Check invalid mask registers
@ 2016-10-24 18:58 sergiodj+buildbot
  2016-10-26  1:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-24 18:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9889cbb14ebea4b281408afcfd94ad6646ab370a ***

Author(s): H.J. Lu <hjl.tools@gmail.com>, Jan Kratochvil <jan.kratochvil@redhat.com>, Nick Clifton <nickc@redhat.com>, Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9889cbb14ebea4b281408afcfd94ad6646ab370a

commit 9889cbb14ebea4b281408afcfd94ad6646ab370a
Author:     H.J. Lu <hjl.tools@gmail.com>
AuthorDate: Thu Oct 20 15:07:42 2016 -0700
Commit:     H.J. Lu <hjl.tools@gmail.com>
CommitDate: Thu Oct 20 15:26:23 2016 -0700

    Check invalid mask registers
    
    In 32-bit, the REX_B bit in the 3-byte VEX prefix is ignored and the
    the highest bit in VEX.vvvv is either 1 or ignored.  In 64-bit, we
    need to check invalid mask registers.
    
    gas/
    
    	PR binutis/20705
    	* testsuite/gas/i386/i386.exp: Run x86-64-opcode-bad.
    	* testsuite/gas/i386/x86-64-opcode-bad.d: New file.
    	* testsuite/gas/i386/x86-64-opcode-bad.s: Likewise.
    
    opcodes/
    
    	PR binutis/20705
    	* i386-dis.c (get_valid_dis386): Ignore the REX_B bit and
    	the highest bit in VEX.vvvv for the 3-byte VEX prefix in
    	32-bit mode.  Don't check vex.register_specifier in 32-bit
    	mode.
    	(OP_E_register): Check invalid mask registers.
    	(OP_G): Likewise.
    	(OP_VEX): Likewise.

diff --git a/gas/ChangeLog b/gas/ChangeLog
index 2e3adbe..50282ab 100644
--- a/gas/ChangeLog
+++ b/gas/ChangeLog
@@ -1,3 +1,10 @@
+2016-10-20  H.J. Lu  <hongjiu.lu@intel.com>
+
+	PR binutis/20705
+	* testsuite/gas/i386/i386.exp: Run x86-64-opcode-bad.
+	* testsuite/gas/i386/x86-64-opcode-bad.d: New file.
+	* testsuite/gas/i386/x86-64-opcode-bad.s: Likewise.
+
 2016-10-19  Renlin Li  <renlin.li@arm.com>
 
 	* config/tc-arm.c (encode_arm_shift): Generate unpredictable warning
diff --git a/gas/testsuite/gas/i386/i386.exp b/gas/testsuite/gas/i386/i386.exp
index c2cdf60..e2b874d 100644
--- a/gas/testsuite/gas/i386/i386.exp
+++ b/gas/testsuite/gas/i386/i386.exp
@@ -776,6 +776,7 @@ if [expr ([istarget "i*86-*-*"] || [istarget "x86_64-*-*"]) && [gas_64_check]] t
     run_dump_test "x86-64-pr20141"
     run_list_test "x86-64-avx512vl-1" "-al"
     run_list_test "x86-64-avx512vl-2" "-al"
+    run_dump_test "x86-64-opcode-bad"
 
     if { ![istarget "*-*-aix*"]
       && ![istarget "*-*-beos*"]
diff --git a/gas/testsuite/gas/i386/x86-64-opcode-bad.d b/gas/testsuite/gas/i386/x86-64-opcode-bad.d
new file mode 100644
index 0000000..24fb5eb
--- /dev/null
+++ b/gas/testsuite/gas/i386/x86-64-opcode-bad.d
@@ -0,0 +1,12 @@
+#as: --64
+#objdump: -dw
+#name: 64bit bad opcodes
+
+.*: +file format .*
+
+Disassembly of section .text:
+
+0+ <.text>:
+ +[a-f0-9]+:	c5 ac 46 f5          	kxnorw %k5,\(bad\),%k6
+ +[a-f0-9]+:	c5 2c 46 f5          	kxnorw %k5,\(bad\),\(bad\)
+#pass
diff --git a/gas/testsuite/gas/i386/x86-64-opcode-bad.s b/gas/testsuite/gas/i386/x86-64-opcode-bad.s
new file mode 100644
index 0000000..5acbcbb
--- /dev/null
+++ b/gas/testsuite/gas/i386/x86-64-opcode-bad.s
@@ -0,0 +1,10 @@
+	.text
+# All the followings are bad opcodes for x86-64.
+	.byte 0xc5
+	.byte 0xac
+	.byte 0x46
+	.byte 0xf5
+	.byte 0xc5
+	.byte 0x2c
+	.byte 0x46
+	.byte 0xf5
diff --git a/opcodes/ChangeLog b/opcodes/ChangeLog
index 36ed580..75c99ac 100644
--- a/opcodes/ChangeLog
+++ b/opcodes/ChangeLog
@@ -1,3 +1,12 @@
+2016-10-20  H.J. Lu  <hongjiu.lu@intel.com>
+
+	PR binutis/20705
+	* i386-dis.c (get_valid_dis386): Ignore the REX_B bit and
+	the highest bit in VEX.vvvv for the 3-byte VEX prefix in
+	32-bit mode.  Don't check vex.register_specifier in 32-bit
+	mode.
+	(OP_VEX): Check for invalid mask registers.
+
 2016-10-18  H.J. Lu  <hongjiu.lu@intel.com>
 
 	PR binutis/20699
diff --git a/opcodes/i386-dis.c b/opcodes/i386-dis.c
index 4624a6a..1518a1d 100644
--- a/opcodes/i386-dis.c
+++ b/opcodes/i386-dis.c
@@ -13022,17 +13022,20 @@ get_valid_dis386 (const struct dis386 *dp, disassemble_info *info)
 	}
       codep++;
       vex.w = *codep & 0x80;
-      if (vex.w && address_mode == mode_64bit)
-	rex |= REX_W;
-
-      vex.register_specifier = (~(*codep >> 3)) & 0xf;
-      if (address_mode != mode_64bit
-	  && vex.register_specifier > 0x7)
+      if (address_mode == mode_64bit)
 	{
-	  dp = &bad_opcode;
-	  return dp;
+	  if (vex.w)
+	    rex |= REX_W;
+	  vex.register_specifier = (~(*codep >> 3)) & 0xf;
+	}
+      else
+	{
+	  /* For the 3-byte VEX prefix in 32-bit mode, the REX_B bit
+	     is ignored, other REX bits are 0 and the highest bit in
+	     VEX.vvvv is also ignored.  */
+	  rex = 0;
+	  vex.register_specifier = (~(*codep >> 3)) & 0x7;
 	}
-
       vex.length = (*codep & 0x4) ? 256 : 128;
       switch ((*codep & 0x3))
 	{
@@ -13072,16 +13075,10 @@ get_valid_dis386 (const struct dis386 *dp, disassemble_info *info)
       rex_ignored = rex;
       rex = (*codep & 0x80) ? 0 : REX_R;
 
+      /* For the 2-byte VEX prefix in 32-bit mode, the highest bit in
+	 VEX.vvvv is 1.  */
       vex.register_specifier = (~(*codep >> 3)) & 0xf;
-      if (address_mode != mode_64bit
-	  && vex.register_specifier > 0x7)
-	{
-	  dp = &bad_opcode;
-	  return dp;
-	}
-
       vex.w = 0;
-
       vex.length = (*codep & 0x4) ? 256 : 128;
       switch ((*codep & 0x3))
 	{
@@ -15266,6 +15263,11 @@ OP_E_register (int bytemode, int sizeflag)
       break;
     case mask_bd_mode:
     case mask_mode:
+      if (reg > 0x7)
+	{
+	  oappend ("(bad)");
+	  return;
+	}
       names = names_mask;
       break;
     case 0:
@@ -15795,6 +15797,11 @@ OP_G (int bytemode, int sizeflag)
       break;
     case mask_bd_mode:
     case mask_mode:
+      if ((modrm.reg + add) > 0x7)
+	{
+	  oappend ("(bad)");
+	  return;
+	}
       oappend (names_mask[modrm.reg + add]);
       break;
     default:
@@ -17225,6 +17232,11 @@ OP_VEX (int bytemode, int sizeflag ATTRIBUTE_UNUSED)
 	  break;
 	case mask_bd_mode:
 	case mask_mode:
+	  if (reg > 0x7)
+	    {
+	      oappend ("(bad)");
+	      return;
+	    }
 	  names = names_mask;
 	  break;
 	default:
@@ -17245,6 +17257,11 @@ OP_VEX (int bytemode, int sizeflag ATTRIBUTE_UNUSED)
 	  break;
 	case mask_bd_mode:
 	case mask_mode:
+	  if (reg > 0x7)
+	    {
+	      oappend ("(bad)");
+	      return;
+	    }
 	  names = names_mask;
 	  break;
 	default:


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ARM/BFD: Correct an `index' global shadowing error
@ 2016-10-25  5:31 sergiodj+buildbot
  2016-10-25  8:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25  5:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c48182bfe408e06e3301ee887fd9a7b06bedff37 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: c48182bfe408e06e3301ee887fd9a7b06bedff37

ARM/BFD: Correct an `index' global shadowing error

Fix a commit 5025eb7c0d87 ("Delete relocations associatesd with deleted
exidx entries.") build regression:

cc1: warnings being treated as errors
.../bfd/elf32-arm.c: In function 'elf32_arm_update_relocs':
.../bfd/elf32-arm.c:14951: warning: declaration of 'index' shadows a global declaration
/usr/include/string.h:304: warning: shadowed declaration is here
make[3]: *** [elf32-arm.lo] Error 1

in a way following commit 91d6fa6a035c ("Add -Wshadow to the gcc command
line options used when compiling the binutils.").

	bfd/
	* elf32-arm.c (elf32_arm_update_relocs): Rename `index' local
	variable to `reloc_index'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tilegx-tdep: Correct aliasing errors in `tilegx_analyze_prologue'
@ 2016-10-25  8:56 sergiodj+buildbot
  2016-10-25 11:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25  8:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b348d11b70068e7eabba6d8f99d4ad371c3f6253 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: b348d11b70068e7eabba6d8f99d4ad371c3f6253

tilegx-tdep: Correct aliasing errors in `tilegx_analyze_prologue'

Fix a load of aliasing build errors:

cc1plus: warnings being treated as errors
.../gdb/tilegx-tdep.c: In function 'CORE_ADDR tilegx_analyze_prologue(gdbarch*, CORE_ADDR, CORE_ADDR, tilegx_frame_cache*, frame_info*)':
.../gdb/tilegx-tdep.c:609: error: dereferencing pointer 'operands' does break strict-aliasing rules
.../gdb/tilegx-tdep.c:592: error: dereferencing pointer 'operands' does break strict-aliasing rules
.../gdb/tilegx-tdep.c:571: error: dereferencing pointer 'operands' does break strict-aliasing rules
[...]
.../gdb/tilegx-tdep.c:601: error: dereferencing pointer '<anonymous>' does break strict-aliasing rules
.../gdb/tilegx-tdep.c:601: note: initialized from here
cc1plus: error: dereferencing pointer 'operands' does break strict-aliasing rules
cc1plus: error: dereferencing pointer 'operands' does break strict-aliasing rules
.../gdb/tilegx-tdep.c:452: note: initialized from here
cc1plus: error: dereferencing pointer 'pretmp.896' does break strict-aliasing rules
cc1plus: note: initialized from here
cc1plus: error: dereferencing pointer 'pretmp.896' does break strict-aliasing rules
cc1plus: note: initialized from here
make[1]: *** [tilegx-tdep.o] Error 1

from an attempt to cast a `long long' pointer to an `int64_t' pointer,
which may not necessarily be compatible types.  Use the `long long' type
for the auxiliary variable then as this is the type of the structure
member referred.

	gdb/
	* tilegx-tdep.c (tilegx_analyze_prologue): Use the `long long'
	type for `operands'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Updated Danish translation for the BFD library.
@ 2016-10-25  9:45 sergiodj+buildbot
  2016-10-25 13:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25  9:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b928b56ea67da30216b79abd6a87ffda99fc911d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: b928b56ea67da30216b79abd6a87ffda99fc911d

Updated Danish translation for the BFD library.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] i386-tdep: Verify architecture before proceeding with `set/show mpx'
@ 2016-10-25 11:26 sergiodj+buildbot
  2016-10-25 12:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 11:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae71e7b59836219c617193a263b17041d765a031 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: ae71e7b59836219c617193a263b17041d765a031

i386-tdep: Verify architecture before proceeding with `set/show mpx'

Make sure the architecture is `bfd_arch_i386' before handling the `set
mpx' and `show mpx' commands, avoiding the issue with `i386_mpx_enabled'
interpreting `gdbarch->tdep' according to the `struct gdbarch_tdep'
definition in i386-tdep.h while indeed in a multi-target configuration
it may have a different layout and cause GDB to crash or at least
misbehave.

	gdb/
	* i386-tdep.c (i386_mpx_info_bounds): Make sure the architecture
	is `bfd_arch_i386' before proceeding.
	(i386_mpx_set_bounds): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] common/common-defs.h: Define __STDC_FORMAT_MACROS as well
@ 2016-10-25 14:27 sergiodj+buildbot
  2016-10-27  7:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b30f354acb39f63bf3213673a0584119e63538b9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b30f354acb39f63bf3213673a0584119e63538b9

common/common-defs.h: Define __STDC_FORMAT_MACROS as well

Ref: https://sourceware.org/ml/gdb-patches/2016-10/msg00694.html

gdb/ChangeLog:
2016-10-25  Pedro Alves  <palves@redhat.com>

	* common/common-defs.h (__STDC_FORMAT_MACROS): Define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update gnulib to current upstream master
@ 2016-10-25 16:26 sergiodj+buildbot
  2016-10-25 17:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 16:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49e4877c5487dc34edf414bb0f1125ce1b71e08b ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 49e4877c5487dc34edf414bb0f1125ce1b71e08b

Update gnulib to current upstream master

I tried building gdb with G++ 4.7 and CXX="g++ -std=gnu+11", and that
tripped on a build error:

  In file included from build-gnulib/import/stdio.h:53:0,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/common/common-defs.h:31,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/defs.h:28,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/armobsd-tdep.c:20:
  build-gnulib/import/stddef.h:104:3: error: conflicting declaration typedef union max_align_t max_align_t
  In file included from build-gnulib/import/stddef.h:55:0,
		   from build-gnulib/import/stdio.h:53,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/common/common-defs.h:31,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/defs.h:28,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/armobsd-tdep.c:20:
  /opt/gcc-4.7/lib/gcc/x86_64-unknown-linux-gnu/4.7.4/include/stddef.h:426:3: error: max_align_t has a previous declaration as typedef struct max_align_t max_align_t

Updating gnulib to current master fixes it, since it brings in this
fix:

 http://lists.gnu.org/archive/html/bug-gnulib/2016-04/msg00000.html

Our last update was in August 2015.  This doesn't bring in much added
baggage, it's mostly bug fixes.  It pulled in the "limits-h" module as
automatic dependency, and given that looks potentially useful I added
it to the set of modules we require.

Tested on x86_64 Fedora 23, with g++ 4.7 and g++ 5.3, native and gdbserver.

gdb/ChangeLog:
2016-10-18  Pedro Alves  <palves@redhat.com>

	* gnulib/update-gnulib.sh (GNULIB_COMMIT_SHA1): Set to
	2692e23a48e21f6daa029e8af9f1a143b7532f47.
	* gnulib/configure, gnulib/config.in, gnulib/aclocal.m4:
	Regenerate.
	* gnulib/import/Makefile: Update.
	* gnulib/import/alloca: Update.
	* gnulib/import/basename-lgpl: Update.
	* gnulib/import/canonicalize-lgpl: Update.
	* gnulib/import/config: Update.
	* gnulib/import/dirent: Update.
	* gnulib/import/dirfd: Update.
	* gnulib/import/dirname-lgpl: Update.
	* gnulib/import/dirname.h: Update.
	* gnulib/import/dosname.h: Update.
	* gnulib/import/errno: Update.
	* gnulib/import/extra/snippet/arg-nonnull.h: Update.
	* gnulib/import/extra/snippet/c++defs.h: Update.
	* gnulib/import/extra/snippet/warn-on-use.h: Update.
	* gnulib/import/extra/update-copyright: Update.
	* gnulib/import/flexmember.h: Update.
	* gnulib/import/float+.h: Update.
	* gnulib/import/float: Update.
	* gnulib/import/float: Update.
	* gnulib/import/fnmatch: Update.
	* gnulib/import/fnmatch: Update.
	* gnulib/import/fnmatch_loop: Update.
	* gnulib/import/fpucw.h: Update.
	* gnulib/import/frexp: Update.
	* gnulib/import/frexpl: Update.
	* gnulib/import/gettimeofday: Update.
	* gnulib/import/hard-locale: Update.
	* gnulib/import/hard-locale.h: Update.
	* gnulib/import/inttypes: Update.
	* gnulib/import/isnan: Update.
	* gnulib/import/isnand-nolibm.h: Update.
	* gnulib/import/isnand: Update.
	* gnulib/import/isnanl-nolibm.h: Update.
	* gnulib/import/isnanl: Update.
	* gnulib/import/itold: Update.
	* gnulib/import/limits: Update.
	* gnulib/import/localcharset: Update.
	* gnulib/import/localcharset.h: Update.
	* gnulib/import/lstat: Update.
	* gnulib/import/m4/00gnulib: Update.
	* gnulib/import/m4/absolute-header: Update.
	* gnulib/import/m4/alloca: Update.
	* gnulib/import/m4/canonicalize: Update.
	* gnulib/import/m4/codeset: Update.
	* gnulib/import/m4/configmake: Update.
	* gnulib/import/m4/dirent_h: Update.
	* gnulib/import/m4/dirfd: Update.
	* gnulib/import/m4/dirname: Update.
	* gnulib/import/m4/double-slash-root: Update.
	* gnulib/import/m4/eealloc: Update.
	* gnulib/import/m4/errno_h: Update.
	* gnulib/import/m4/exponentd: Update.
	* gnulib/import/m4/exponentl: Update.
	* gnulib/import/m4/extensions: Update.
	* gnulib/import/m4/extern-inline: Update.
	* gnulib/import/m4/fcntl-o: Update.
	* gnulib/import/m4/flexmember: Update.
	* gnulib/import/m4/float_h: Update.
	* gnulib/import/m4/fnmatch: Update.
	* gnulib/import/m4/fpieee: Update.
	* gnulib/import/m4/frexp: Update.
	* gnulib/import/m4/frexpl: Update.
	* gnulib/import/m4/gettimeofday: Update.
	* gnulib/import/m4/glibc21: Update.
	* gnulib/import/m4/gnulib-cache: Update.
	* gnulib/import/m4/gnulib-common: Update.
	* gnulib/import/m4/gnulib-comp: Update.
	* gnulib/import/m4/gnulib-tool: Update.
	* gnulib/import/m4/hard-locale: Update.
	* gnulib/import/m4/include_next: Update.
	* gnulib/import/m4/inttypes-pri: Update.
	* gnulib/import/m4/inttypes: Update.
	* gnulib/import/m4/isnand: Update.
	* gnulib/import/m4/isnanl: Update.
	* gnulib/import/m4/largefile: Update.
	* gnulib/import/m4/limits-h: Update.
	* gnulib/import/m4/localcharset: Update.
	* gnulib/import/m4/locale-fr: Update.
	* gnulib/import/m4/locale-ja: Update.
	* gnulib/import/m4/locale-zh: Update.
	* gnulib/import/m4/longlong: Update.
	* gnulib/import/m4/lstat: Update.
	* gnulib/import/m4/malloc: Update.
	* gnulib/import/m4/malloca: Update.
	* gnulib/import/m4/math_h: Update.
	* gnulib/import/m4/mbrtowc: Update.
	* gnulib/import/m4/mbsinit: Update.
	* gnulib/import/m4/mbsrtowcs: Update.
	* gnulib/import/m4/mbstate_t: Update.
	* gnulib/import/m4/memchr: Update.
	* gnulib/import/m4/memmem: Update.
	* gnulib/import/m4/mmap-anon: Update.
	* gnulib/import/m4/multiarch: Update.
	* gnulib/import/m4/nocrash: Update.
	* gnulib/import/m4/off_t: Update.
	* gnulib/import/m4/pathmax: Update.
	* gnulib/import/m4/rawmemchr: Update.
	* gnulib/import/m4/readlink: Update.
	* gnulib/import/m4/rename: Update.
	* gnulib/import/m4/rmdir: Update.
	* gnulib/import/m4/signal_h: Update.
	* gnulib/import/m4/ssize_t: Update.
	* gnulib/import/m4/stat: Update.
	* gnulib/import/m4/stdbool: Update.
	* gnulib/import/m4/stddef_h: Update.
	* gnulib/import/m4/stdint: Update.
	* gnulib/import/m4/stdio_h: Update.
	* gnulib/import/m4/stdlib_h: Update.
	* gnulib/import/m4/strchrnul: Update.
	* gnulib/import/m4/string_h: Update.
	* gnulib/import/m4/strstr: Update.
	* gnulib/import/m4/strtok_r: Update.
	* gnulib/import/m4/sys_socket_h: Update.
	* gnulib/import/m4/sys_stat_h: Update.
	* gnulib/import/m4/sys_time_h: Update.
	* gnulib/import/m4/sys_types_h: Update.
	* gnulib/import/m4/time_h: Update.
	* gnulib/import/m4/unistd_h: Update.
	* gnulib/import/m4/warn-on-use: Update.
	* gnulib/import/m4/wchar_h: Update.
	* gnulib/import/m4/wchar_t: Update.
	* gnulib/import/m4/wctype_h: Update.
	* gnulib/import/m4/wint_t: Update.
	* gnulib/import/malloc: Update.
	* gnulib/import/malloca: Update.
	* gnulib/import/malloca.h: Update.
	* gnulib/import/math: Update.
	* gnulib/import/math: Update.
	* gnulib/import/mbrtowc: Update.
	* gnulib/import/mbsinit: Update.
	* gnulib/import/mbsrtowcs-impl.h: Update.
	* gnulib/import/mbsrtowcs-state: Update.
	* gnulib/import/mbsrtowcs: Update.
	* gnulib/import/memchr: Update.
	* gnulib/import/memmem: Update.
	* gnulib/import/pathmax.h: Update.
	* gnulib/import/rawmemchr: Update.
	* gnulib/import/readlink: Update.
	* gnulib/import/ref-add.sin: Update.
	* gnulib/import/ref-del.sin: Update.
	* gnulib/import/rename: Update.
	* gnulib/import/rmdir: Update.
	* gnulib/import/same-inode.h: Update.
	* gnulib/import/signal: Update.
	* gnulib/import/stat: Update.
	* gnulib/import/stdbool: Update.
	* gnulib/import/stddef: Update.
	* gnulib/import/stdint: Update.
	* gnulib/import/stdio: Update.
	* gnulib/import/stdlib: Update.
	* gnulib/import/str-two-way.h: Update.
	* gnulib/import/strchrnul: Update.
	* gnulib/import/streq.h: Update.
	* gnulib/import/string: Update.
	* gnulib/import/stripslash: Update.
	* gnulib/import/strnlen1: Update.
	* gnulib/import/strnlen1.h: Update.
	* gnulib/import/strstr: Update.
	* gnulib/import/strtok_r: Update.
	* gnulib/import/sys_stat: Update.
	* gnulib/import/sys_time: Update.
	* gnulib/import/sys_types: Update.
	* gnulib/import/time: Update.
	* gnulib/import/unistd: Update.
	* gnulib/import/unistd: Update.
	* gnulib/import/verify.h: Update.
	* gnulib/import/wchar: Update.
	* gnulib/import/wctype: Update.
	* gnulib/import/flexmember.h: New file.
	* gnulib/import/hard-locale.c: New file.
	* gnulib/import/hard-locale.h: New file.
	* gnulib/import/limits.in.h: New file.
	* gnulib/import/m4/flexmember.m4: New file.
	* gnulib/import/m4/hard-locale.m4: New file.
	* gnulib/import/m4/limits-h.m4: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: no longer define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS
@ 2016-10-25 17:13 sergiodj+buildbot
  2016-10-25 18:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 17:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f6abaf7a4088dc9a5d73ee2233246347af9181d5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f6abaf7a4088dc9a5d73ee2233246347af9181d5

gdb: no longer define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS

My gnulib fix at:
  https://lists.gnu.org/archive/html/bug-gnulib/2015-11/msg00010.html
was merged upstream meanwhile and our gnulib copy now includes it.

As a concidence, Kevin was telling me today that these macros are
causing a build problem on FreeBSD:

common/common-defs.h:47:0: error: "__STDC_CONSTANT_MACROS" redefined [-Werror]
  #define __STDC_CONSTANT_MACROS 1
  /usr/include/sys/cdefs.h:408:0: note: this is the location of the previous definition
  #define __STDC_CONSTANT_MACROS
(and a similar error for __STDC_LIMIT_MACROS)

The problem seems to be that we should be defining these input macros
before including any system header, but, we're not.

So let's just revert e063da67902e ([C++] Define __STDC_CONSTANT_MACROS
/ __STDC_LIMIT_MACROS for stdint.h).  If this causes a problem
somewhere, we can re-define the macros higher up in the file, before
system headers are included.

gdb/ChangeLog:
2016-10-18  Pedro Alves  <palves@redhat.com>

	* common/common-defs.h (__STDC_CONSTANT_MACROS)
	(__STDC_LIMIT_MACROS): Delete.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add c-format tags to translatable strings with more than one argument-using formatting token.
@ 2016-10-25 19:09 sergiodj+buildbot
  2016-10-25 20:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 19:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 695344c018c8e462280c47a644df02ea472b0a4e ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 695344c018c8e462280c47a644df02ea472b0a4e

Add c-format tags to translatable strings with more than one argument-using formatting token.

	* aout-adobe.c: Add missing c-format tags for translatable strings.
	* aout-cris.c: Likewise.
	* aoutx.h: Likewise.
	* bfd.c: Likewise.
	* binary.c: Likewise.
	* cache.c: Likewise.
	* coff-alpha.c: Likewise.
	* coff-arm.c: Likewise.
	* coff-i860.c: Likewise.
	* coff-mcore.c: Likewise.
	* coff-ppc.c: Likewise.
	* coff-rs6000.c: Likewise.
	* coff-sh.c: Likewise.
	* coff-tic4x.c: Likewise.
	* coff-tic54x.c: Likewise.
	* coff-tic80.c: Likewise.
	* coff64-rs6000.c: Likewise.
	* coffcode.h: Likewise.
	* coffgen.c: Likewise.
	* cofflink.c: Likewise.
	* coffswap.h: Likewise.
	* cpu-arm.c: Likewise.
	* dwarf2.c: Likewise.
	* ecoff.c: Likewise.
	* elf-attrs.c: Likewise.
	* elf-eh-frame.c: Likewise.
	* elf-ifunc.c: Likewise.
	* elf-m10300.c: Likewise.
	* elf-s390-common.c: Likewise.
	* elf.c: Likewise.
	* elf32-arc.c: Likewise.
	* elf32-arm.c: Likewise.
	* elf32-avr.c: Likewise.
	* elf32-bfin.c: Likewise.
	* elf32-cr16.c: Likewise.
	* elf32-cr16c.c: Likewise.
	* elf32-cris.c: Likewise.
	* elf32-crx.c: Likewise.
	* elf32-d10v.c: Likewise.
	* elf32-d30v.c: Likewise.
	* elf32-epiphany.c: Likewise.
	* elf32-fr30.c: Likewise.
	* elf32-frv.c: Likewise.
	* elf32-gen.c: Likewise.
	* elf32-hppa.c: Likewise.
	* elf32-i370.c: Likewise.
	* elf32-i386.c: Likewise.
	* elf32-i960.c: Likewise.
	* elf32-ip2k.c: Likewise.
	* elf32-iq2000.c: Likewise.
	* elf32-lm32.c: Likewise.
	* elf32-m32c.c: Likewise.
	* elf32-m32r.c: Likewise.
	* elf32-m68hc11.c: Likewise.
	* elf32-m68hc12.c: Likewise.
	* elf32-m68hc1x.c: Likewise.
	* elf32-m68k.c: Likewise.
	* elf32-mcore.c: Likewise.
	* elf32-mep.c: Likewise.
	* elf32-metag.c: Likewise.
	* elf32-microblaze.c: Likewise.
	* elf32-moxie.c: Likewise.
	* elf32-msp430.c: Likewise.
	* elf32-mt.c: Likewise.
	* elf32-nds32.c: Likewise.
	* elf32-nios2.c: Likewise.
	* elf32-or1k.c: Likewise.
	* elf32-pj.c: Likewise.
	* elf32-ppc.c: Likewise.
	* elf32-rl78.c: Likewise.
	* elf32-rx.c: Likewise.
	* elf32-s390.c: Likewise.
	* elf32-score.c: Likewise.
	* elf32-score7.c: Likewise.
	* elf32-sh-symbian.c: Likewise.
	* elf32-sh.c: Likewise.
	* elf32-sh64.c: Likewise.
	* elf32-spu.c: Likewise.
	* elf32-tic6x.c: Likewise.
	* elf32-tilepro.c: Likewise.
	* elf32-v850.c: Likewise.
	* elf32-vax.c: Likewise.
	* elf32-visium.c: Likewise.
	* elf32-xgate.c: Likewise.
	* elf32-xtensa.c: Likewise.
	* elf64-alpha.c: Likewise.
	* elf64-gen.c: Likewise.
	* elf64-hppa.c: Likewise.
	* elf64-ia64-vms.c: Likewise.
	* elf64-mmix.c: Likewise.
	* elf64-ppc.c: Likewise.
	* elf64-s390.c: Likewise.
	* elf64-sh64.c: Likewise.
	* elf64-sparc.c: Likewise.
	* elf64-x86-64.c: Likewise.
	* elfcode.h: Likewise.
	* elfcore.h: Likewise.
	* elflink.c: Likewise.
	* elfnn-aarch64.c: Likewise.
	* elfnn-ia64.c: Likewise.
	* elfxx-mips.c: Likewise.
	* elfxx-sparc.c: Likewise.
	* elfxx-tilegx.c: Likewise.
	* ieee.c: Likewise.
	* ihex.c: Likewise.
	* libbfd.c: Likewise.
	* linker.c: Likewise.
	* m68klinux.c: Likewise.
	* mach-o.c: Likewise.
	* merge.c: Likewise.
	* mmo.c: Likewise.
	* oasys.c: Likewise.
	* pdp11.c: Likewise.
	* pe-mips.c: Likewise.
	* peXXigen.c: Likewise.
	* pei-x86_64.c: Likewise.
	* peicode.h: Likewise.
	* ppcboot.c: Likewise.
	* reloc.c: Likewise.
	* sparclinux.c: Likewise.
	* srec.c: Likewise.
	* stabs.c: Likewise.
	* vms-alpha.c: Likewise.
	* vms-lib.c: Likewise.
	* xcofflink.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] testsuite: Fix gdb.base/killed-outside.exp using irrelevant stale options
@ 2016-10-25 20:01 sergiodj+buildbot
  2016-10-25 20:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d2476aac71fcafad6d1524733f0d88f2b53753b ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 2d2476aac71fcafad6d1524733f0d88f2b53753b

testsuite: Fix gdb.base/killed-outside.exp using irrelevant stale options

Fix a commit 4a556533cf02 ("Fix PR11094: JIT breakpoint is not properly
recreated on reruns") regression:

Running .../gdb/testsuite/gdb.base/killed-outside.exp ...
Executing on host: mips-mti-linux-gnu-gcc  -Wl,--no-as-needed  -c -g  -o .../gdb/testsuite/outputs/gdb.base/killed-outside/killed-outside0.o .../gdb/testsuite/gdb.base/killed-outside.c .../gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple-jit.so    (timeout = 300)
spawn mips-mti-linux-gnu-gcc -Wl,--no-as-needed -c -g -o .../gdb/testsuite/outputs/gdb.base/killed-outside/killed-outside0.o .../gdb/testsuite/gdb.base/killed-outside.c .../gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple-jit.so
mips-mti-linux-gnu-gcc: warning: .../gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple-jit.so: linker input file unused because linking not done
output is:
mips-mti-linux-gnu-gcc: warning: .../gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple-jit.so: linker input file unused because linking not done

gdb compile failed, mips-mti-linux-gnu-gcc: warning: .../gdb/testsuite/outputs/gdb.base/jit-simple/jit-simple-jit.so: linker input file unused because linking not done
UNTESTED: gdb.base/killed-outside.exp: failed to prepare

and adjust the call to `prepare_for_testing' by removing a reference to
`options', which is not set in this test case but a stale value is
carried over from `gdb.base/jit-simple.exp' previously executed in a
full test suite run.

	gdb/testsuite/
	* gdb.base/killed-outside.exp: Remove $options from a call to
	`prepare_for_testing'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Regenerate bfd.pot.
@ 2016-10-25 23:12 sergiodj+buildbot
  2016-10-25 22:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-25 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 789b4e00353f554c69ded290564276742ee290db ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 789b4e00353f554c69ded290564276742ee290db

Regenerate bfd.pot.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Delete target_so_ops->special_symbol_handling hook
@ 2016-10-26  0:57 sergiodj+buildbot
  2016-10-26  1:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  0:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4db41a0a1097860d1e0d3b8ecf6c01dbbb65ba5a ***

Author: Philipp Rudo <prudo@linux.vnet.ibm.com>
Branch: master
Commit: 4db41a0a1097860d1e0d3b8ecf6c01dbbb65ba5a

Delete target_so_ops->special_symbol_handling hook

No one(!) actually implements this hook. So simply delete it.

gdb/ChangeLog:

	* solist.h (struct target_so_ops): Delete special_symbol_handling
	hook.
	* solib.c (solib_add, reload_shared_libraries): Adjust.
	* solib-aix.c (solib_aix_special_symbol_handling): Delete
	(_initialize_solib_aix): Adjust
	* solib-darwin.c (darwin_special_symbol_handling): Delete
	(_initialize_darwin_solib): Adjust
	* solib-dsbt.c (dsbt_special_symbol_handling): Delete
	(_initialize_dsbt_solib): Adjust
	* solib-frv.c (frv_special_symbol_handling): Delete
	(_initialize_frv_solib): Adjust
	* solib-svr4.c (svr4_special_symbol_handling): Delete
	(_initialize_svr4_solib): Adjust
	* solib-target.c (solib_target_special_symbol_handling): Delete
	(_initialize_solib_target): Adjust


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use RAII to save and restore scalars
@ 2016-10-26  3:15 sergiodj+buildbot
  2016-10-26  4:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  3:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7b633e9b13fc5697af035f4504c9790c612a8c7 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: b7b633e9b13fc5697af035f4504c9790c612a8c7

Use RAII to save and restore scalars

This patch replaces many (but not all) uses of
make_cleanup_restore_integer with a simple RAII-based template class.
It also removes the similar restore_execution_direction cleanup in
favor of this new class.  Subsequent patches will replace other
similar cleanups with this class.

The class is typically instantiated using make_scoped_restore.  This
allows for template argument deduction.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* common/scoped_restore.h: New file.
	* utils.h: Include scoped_restore.h.
	* top.c (execute_command_to_string): Use scoped_restore.
	* python/python.c (python_interactive_command): Use
	scoped_restore.
	(python_command, execute_gdb_command): Likewise.
	* printcmd.c (do_one_display): Use scoped_restore.
	* mi/mi-main.c (exec_continue): Use scoped_restore.
	* mi/mi-cmd-var.c (mi_cmd_var_assign): Use scoped_restore.
	* linux-fork.c (checkpoint_command): Use scoped_restore.
	* infrun.c (restore_execution_direction): Remove.
	(fetch_inferior_event): Use scoped_restore.
	* compile/compile.c (compile_file_command): Use
	scoped_restore.
	(compile_code_command, compile_print_command): Likewise.
	* cli/cli-script.c (execute_user_command): Use
	scoped_restore.
	(while_command, if_command, script_from_file): Likewise.
	* arm-tdep.c (arm_insert_single_step_breakpoint): Use
	scoped_restore.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Record minimal symbols directly in reader.
@ 2016-10-26  4:10 sergiodj+buildbot
  2016-10-26  8:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  4:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8dddcb8f005e8470312bf33041bb6ddaa5084e32 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 8dddcb8f005e8470312bf33041bb6ddaa5084e32

Record minimal symbols directly in reader.

This patch changes minimal symbol creation in two ways.  First, it
removes global variables in favor of members of minimal_symbol_reader.
Second, it changes functions like prim_record_minimal_symbol to be
member functions of minimal_symbol_reader.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* xcoffread.c (record_minimal_symbol, scan_xcoff_symtab): Add
	"reader" argument.  Update.
	(xcoff_initial_scan): Update.
	* symfile.h (mdebug_build_psymtabs): Add "reader" argument.
	* mipsread.c (mipscoff_symfile_read): Update.
	(read_alphacoff_dynamic_symtab): Add "reader" argument.  Update.
	* minsyms.h (minimal_symbol_reader) <record, record_full>:
	Declare.
	<m_msym_bunch, m_msym_bunch_index, m_msym_count>: New members.
	<record_with_info>: New function, renamed from
	prim_record_minimal_symbol_and_info.
	* minsyms.c (msym_bunch, msym_bunch_index, msym_count): Remove
	globals.
	(minimal_symbol_reader): Initialize new members.
	(minimal_symbol_reader::record): Renamed from
	prim_record_minimal_symbol.
	(minimal_symbol_reader::record_full): Renamed from
	prim_record_minimal_symbol_full.
	(prim_record_minimal_symbol_and_info): Move to minsyms.h; rename.
	* mdebugread.c (mdebug_build_psymtabs, parse_partial_symbols)
	(record_minimal_symbol): Add "reader" argument.  Update.
	(elfmdebug_build_psymtabs): Update.
	* machoread.c (macho_symtab_add_minsym, macho_symtab_read): Add
	"reader" argument.  Update.
	(macho_symfile_read): Update.
	* elfread.c (record_minimal_symbol, elf_symtab_read)
	(elf_rel_plt_read): Add "reader" argument.  Update.
	(elf_read_minimal_symbols): Update.
	* dbxread.c (record_minimal_symbol, read_dbx_dynamic_symtab)
	(read_dbx_symtab): Add "reader" argument.  Update.
	(dbx_symfile_read): Update.
	* coffread.c (record_minimal_symbol, coff_symtab_read): Add
	"reader" argument.  Update.
	(coff_symfile_read): Update.
	* coff-pe-read.h (read_pe_exported_syms): Add "reader" argument.
	* coff-pe-read.c (add_pe_exported_sym, add_pe_forwarded_sym)
	(read_pe_exported_syms): Add "reader" argument.  Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use scoped_restore for current_ui
@ 2016-10-26  5:16 sergiodj+buildbot
  2016-10-26  5:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  5:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b6749b9a4680e79affdb9c02ea2f5ba39a54587 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4b6749b9a4680e79affdb9c02ea2f5ba39a54587

Use scoped_restore for current_ui

This changes most uses of make_cleanup_restore_current_ui to use
scoped_restore.  The use in switch_thru_all_uis_init still remains;
that is dealt with in a later patch by replacing this iterator with a
real class.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* top.c (new_ui_command, wait_sync_command_done)
	(gdb_readline_wrapper): Use scoped_restore.
	* infrun.c (fetch_inferior_event): Use scoped_restore.
	* infcall.c (call_thread_fsm_should_stop): Use scoped_restore.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change command stats reporting to use class
@ 2016-10-26  6:04 sergiodj+buildbot
  2016-10-26 12:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  6:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e3b796d58ac3c4396e1739f44a0a41de6335eef ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1e3b796d58ac3c4396e1739f44a0a41de6335eef

Change command stats reporting to use class

This removes make_command_stats_cleanup in favor of an RAII class.
The patch is reasonably straightforward, but keeping the same
semantics without excessive reindentation required splitting
captured_main in two.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* maint.h (scoped_command_stats): New class.
	(make_command_stats_cleanup): Don't declare.
	* maint.c (struct cmd_stats): Remove.
	(~scoped_command_stats): Rename from report_command_stats.  Now a
	destructor.
	(scoped_command_stats): Rename from make_command_stats_cleanup.
	Now a constructor.
	* main.c (captured_main_1): New function.  Use
	scoped_command_stats.
	(captured_main): Call captured_main_1.
	* event-top.c (command_handler): Use scoped_command_stats.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Replace two xmallocs with unique_ptr
@ 2016-10-26  7:29 sergiodj+buildbot
  2016-10-26 13:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  7:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd9da5b077c21f0984cfbdac060ced6f4945ce06 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cd9da5b077c21f0984cfbdac060ced6f4945ce06

Replace two xmallocs with unique_ptr

This replaces a couple of uses of xmalloc with gdb::unique_ptr, also
removing a couple of cleanups.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* cli/cli-dump.c (dump_memory_to_file): Use gdb::unique_ptr.
	(restore_binary_file): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove make_cleanup_restore_current_ui
@ 2016-10-26  8:46 sergiodj+buildbot
  2016-10-26  9:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  8:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e454242cc1527e49ad0ea795614ac94a083b68a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0e454242cc1527e49ad0ea795614ac94a083b68a

Remove make_cleanup_restore_current_ui

This removes make_cleanup_restore_current_ui by converting the last
use.  The last use was in a few functions used to iterate over all
UIs.  This patch replaces these functions with a class, and arranges
for the class destructor to do the needed cleanup.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* tui/tui-interp.c (tui_on_normal_stop, tui_on_signal_received)
	(tui_on_end_stepping_range, tui_on_signal_exited, tui_on_exited)
	(tui_on_no_history, tui_on_user_selected_context_changed):
	Update.
	* top.h (switch_thru_all_uis): New class.
	(SWITCH_THRU_ALL_UIS): Rewrite.
	(make_cleanup_restore_current_ui, switch_thru_all_uis_init)
	(switch_thru_all_uis_cond, switch_thru_all_uis_next): Don't
	declare.
	* mi/mi-interp.c (mi_new_thread, mi_thread_exit)
	(mi_record_changed, mi_inferior_added, mi_inferior_appeared)
	(mi_inferior_exit, mi_inferior_removed, mi_on_signal_received)
	(mi_on_end_stepping_range, mi_on_signal_exited, mi_on_exited)
	(mi_on_no_history, mi_on_normal_stop, mi_traceframe_changed)
	(mi_tsv_created, mi_tsv_deleted, mi_tsv_modified)
	(mi_breakpoint_created, mi_breakpoint_deleted)
	(mi_breakpoint_modified, mi_output_running_pid, mi_on_resume)
	(mi_solib_loaded, mi_solib_unloaded, mi_command_param_changed)
	(mi_memory_changed, mi_user_selected_context_changed): Update.
	* infrun.c (all_uis_check_sync_execution_done)
	(all_uis_on_sync_execution_starting, normal_stop): Update.
	* event-top.c (restore_ui_cleanup)
	(make_cleanup_restore_current_ui, switch_thru_all_uis_init)
	(switch_thru_all_uis_cond, switch_thru_all_uis_next): Remove.
	* cli/cli-interp.c (cli_on_normal_stop, cli_on_signal_received)
	(cli_on_end_stepping_range, cli_on_signal_exited, cli_on_exited)
	(cli_on_no_history, cli_on_user_selected_context_changed):
	Update.
	* breakpoint.c (watchpoint_check): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove some cleanups in MI
@ 2016-10-26  9:49 sergiodj+buildbot
  2016-10-26 10:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26  9:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6fc31fc73b577fce960730d87ead9a25df6c2653 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6fc31fc73b577fce960730d87ead9a25df6c2653

Remove some cleanups in MI

This patch removes a couple of cleanups from MI by using
gdb::unique_ptr.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* mi/mi-main.c (mi_cmd_data_read_memory): Use gdb::unique_ptr.
	Remove some cleanups.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdb::unique_ptr in elf_read_minimal_symbols
@ 2016-10-26 11:13 sergiodj+buildbot
  2016-10-26 13:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 11:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1e4a624699fd734b3b6e87fb79a4da71c182dfd ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d1e4a624699fd734b3b6e87fb79a4da71c182dfd

Use gdb::unique_ptr in elf_read_minimal_symbols

This changes elf_read_minimal_symbols to use gdb::unique_ptr rather
than an explicit allocation.  This removes a cleanup.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* elfread.c (elf_read_minimal_symbols): Use gdb::unique_ptr.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Convert dwarf_expr_context_funcs to methods
@ 2016-10-26 12:26 sergiodj+buildbot
  2016-10-26 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 192ca6d8eac4a5538036ef200b95d6ef3dbe9511 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 192ca6d8eac4a5538036ef200b95d6ef3dbe9511

Convert dwarf_expr_context_funcs to methods

This patch converts the function pointers in dwarf_expr_context_funcs
into methods on dwarf_expr_context, and then updates the various
implementations and callers to follow.

NB this patch uses "override" (which caught a couple of renaming bugs
during development) -- but this is C++11, so this patch at least has
to wait for Pedro's patch that adds the OVERRIDE macro.

After this patch it would be possible to do one more, that makes
various members of dwarf_expr_context "protected"; but I haven't done
this.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* dwarf2loc.c (struct dwarf_expr_context_funcs): Don't declare.
	(dwarf_expr_read_addr_from_reg, dwarf_expr_get_reg_value)
	(dwarf_expr_read_mem, dwarf_expr_frame_base): Rename; turn into
	methods.
	(get_frame_pc_for_per_cu_dwarf_call): New function.
	(dwarf_expr_frame_cfa, dwarf_expr_frame_pc)
	(dwarf_expr_tls_address): Rename; turn into methods.
	(per_cu_dwarf_call): Remove arguments.  Use
	get_frame_pc_for_per_cu_dwarf_call.
	(dwarf_evaluate_loc_desc): New class.
	(dwarf_expr_dwarf_call, dwarf_expr_context)
	(dwarf_expr_push_dwarf_reg_entry_value)
	(dwarf_expr_get_addr_index, dwarf_expr_get_obj_addr): Rename; turn
	into methods.
	(dwarf_expr_ctx_funcs): Remove.
	(dwarf2_evaluate_loc_desc_full): Update.
	(dwarf2_locexpr_baton_eval): Update.
	(symbol_needs_eval_context): New class.
	(symbol_needs_read_addr_from_reg, symbol_needs_get_reg_value)
	(symbol_needs_read_mem, symbol_needs_frame_base)
	(symbol_needs_frame_cfa, symbol_needs_tls_address)
	(symbol_needs_dwarf_call, needs_dwarf_reg_entry_value): Rename;
	turn into methods.
	(needs_get_addr_index, needs_get_obj_addr): Remove; turn into
	methods.
	(symbol_needs_ctx_funcs): Remove.
	(dwarf2_loc_desc_get_symbol_read_needs): Update.
	* dwarf2expr.h (struct dwarf_expr_context_funcs): Remove; turn
	contents into methods.
	(struct dwarf_expr_context) <baton, funcs>: Remove.
	<read_addr_from_reg, get_reg_value, read_mem, get_frame_base,
	get_frame_cfa, get_frame_pc, get_tls_address, dwarf_call,
	impl_get_base_type, push_dwarf_block_entry_value, get_addr_index,
	get_object_address>: Declare new methods.
	(ctx_no_get_frame_base, ctx_no_get_frame_cfa)
	(ctx_no_get_frame_pc, ctx_no_get_tls_address, ctx_no_dwarf_call)
	(ctx_no_get_base_type, ctx_no_push_dwarf_reg_entry_value)
	(ctx_no_get_addr_index): Don't declare.
	* dwarf2expr.c (get_base_type): Use impl_get_base_type.
	(execute_stack_op): Update.
	(ctx_no_get_frame_base, ctx_no_get_frame_cfa)
	(ctx_no_get_frame_pc, ctx_no_get_tls_address, ctx_no_dwarf_call)
	(ctx_no_get_base_type, ctx_no_push_dwarf_reg_entry_value)
	(ctx_no_get_addr_index): Remove; now methods on
	dwarf_expr_context.
	* dwarf2-frame.c (read_addr_from_reg): Take a frame_info, not a
	baton.
	(class dwarf_expr_executor): New class.
	(get_reg_value, read_mem): Rename, turn into methods.
	(execute_stack_op): Use dwarf_expr_executor.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Initial conversion of dwarf_expr_ctx
@ 2016-10-26 13:44 sergiodj+buildbot
  2016-10-26 16:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 718b962660007c529f4ff4c5e940119da21e05a7 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 718b962660007c529f4ff4c5e940119da21e05a7

Initial conversion of dwarf_expr_ctx

This is the first step in the conversion of dwarf_expr_ctx to a C++
class.  This conversion is done in steps to make the patches, and the
reviews, a bit simpler.  This patch changes dwarf_expr_ctx to be
stack-allocated and removes the associated cleanup.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* dwarf2loc.c (dwarf2_evaluate_loc_desc_full): Stack-allocate
	dwarf_expr_context.  Remove cleanups.
	(dwarf2_locexpr_baton_eval)
	(dwarf2_loc_desc_get_symbol_read_needs):  Likewise.
	* dwarf2expr.h (dwarf_expr_context, ~dwarf_expr_context): Add
	constructors and destructors.
	(new_dwarf_expr_context, free_dwarf_expr_context)
	(make_cleanup_free_dwarf_expr_context): Don't declare.
	* dwarf2-frame.c (execute_stack_op): Stack-allocate
	dwarf_expr_context.  Remove cleanups.
	(dwarf_expr_context): Rename from new_dwarf_expr_context.  Turn
	into constructor.
	(free_dwarf_expr_context, free_dwarf_expr_context_cleanup):
	Remove.
	(~dwarf_expr_context): Rename from
	make_cleanup_free_dwarf_expr_context.  Turn into destructor.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change minimal_symbol_reader::record_full to take a bool
@ 2016-10-26 14:01 sergiodj+buildbot
  2016-10-26 21:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 14:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce6c454e5acbaec4e0c22e9c8af0fe7686a53baa ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: ce6c454e5acbaec4e0c22e9c8af0fe7686a53baa

Change minimal_symbol_reader::record_full to take a bool

This changes an "int" to a "bool" in the signature for
minimal_symbol_reader::record_full, and then fixes the callers.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* minsyms.h (minimal_symbol_reader::record_full): "copy_name" now
	a bool.
	(record, record_with_info): Update.
	* minsyms.c (record): Fix indentation.
	(record_full): Fix indentation.  Update for type change.
	* elfread.c (record_minimal_symbol): "copy_name" now a bool.
	(elf_symtab_read): "copy_names" now a bool.
	(elf_rel_plt_read, elf_read_minimal_symbols): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make some dwarf_expr_context methods pure virtual
@ 2016-10-26 15:19 sergiodj+buildbot
  2016-10-26 22:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT befbff861e07212f4073e4ce72e4b45cca3e0f8d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: befbff861e07212f4073e4ce72e4b45cca3e0f8d

Make some dwarf_expr_context methods pure virtual

This patch changes some dwarf_expr_context to be pure virtual, as
mentioned during the discussion of an earlier patch in this series.

2016-10-21  Tom Tromey  <tom@tromey.com>

	* dwarf2expr.h (class dwarf_expr_context)
	<get_frame_base, get_frame_cfa, get_tls_address, dwarf_call,
	push_dwarf_block_entry_value, get_addr_index, get_object_address>:
	Now pure virtual.
	* dwarf2-frame.c (class dwarf_expr_executor)
	<get_frame_base, get_frame_cfa, get_tls_address, dwarf_call,
	push_dwarf_block_entry_value, get_addr_index, get_object_address>:
	New methods.
	<invalid>: New method.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbserver: Leave already-vCont-resumed threads as they were
@ 2016-10-26 18:48 sergiodj+buildbot
  2016-10-27 12:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a04c4cf5df6d13596e79e7b84520cbe245a5a4d ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 5a04c4cf5df6d13596e79e7b84520cbe245a5a4d

gdbserver: Leave already-vCont-resumed threads as they were

Currently GDB never sends more than one action per vCont packet, when
connected in non-stop mode.  A follow up patch will change that, and
it exposed a gdbserver problem with the vCont handling.

For example, this in non-stop mode:

  => vCont;s:p1.1;c
  <= OK

Should be equivalent to:

  => vCont;s:p1.1
  <= OK
  => vCont;c
  <= OK

But gdbserver currently doesn't handle this.  In the latter case,
"vCont;c" makes gdbserver clobber the previous step request.  This
patch fixes that.

Note the server side must ignore resume actions for the thread that
has a pending %Stopped notification (and any other threads with events
pending), until GDB acks the notification with vStopped.  Otherwise,
e.g., the following case is mishandled:

 #1 => g  (or any other packet)
 #2 <= [registers]
 #3 <= %Stopped T05 thread:p1.2
 #4 => vCont s:p1.1;c
 #5 <= OK

Above, the server must not resume thread p1.2 when it processes the
vCont.  GDB can't know that p1.2 stopped until it acks the %Stopped
notification.  (Otherwise it wouldn't send a default "c" action.)

(The vCont documentation already specifies this.)

Finally, special care must also be given to handling fork/vfork
events.  A (v)fork event actually tells us that two processes stopped
-- the parent and the child.  Until we follow the fork, we must not
resume the child.  Therefore, if we have a pending fork follow, we
must not send a global wildcard resume action (vCont;c).  We can still
send process-wide wildcards though.

(The comments above will be added as code comments to gdb in a follow
up patch.)

gdb/gdbserver/ChangeLog:
2016-10-26  Pedro Alves  <palves@redhat.com>

	* linux-low.c (handle_extended_wait): Link parent/child fork
	threads.
	(linux_wait_1): Unlink them.
	(linux_set_resume_request): Ignore resume requests for
	already-resumed and unhandled fork child threads.
	* linux-low.h (struct lwp_info) <fork_relative>: New field.
	* server.c (in_queued_stop_replies_ptid, in_queued_stop_replies):
	New functions.
	(handle_v_requests) <vCont>: Don't call require_running.
	* server.h (in_queued_stop_replies): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [GDBserver] Fix conversion warning
@ 2016-10-26 19:43 sergiodj+buildbot
  2016-10-26 23:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 19:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb93dc7f262978bafe36397a41a56e409a302042 ***

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

[GDBserver] Fix conversion warning

I got the following warning if I build GDBserver for aarch64_be-linux-gnu,

git/gdb/gdbserver/linux-aarch64-low.c:1539:39: error: invalid conversion from 'void*' to 'uint32_t* {aka unsigned int*}' [-fpermissive]
   uint32_t *le_buf = xmalloc (byte_len);
                                       ^
The patch is to fix the warning.

gdb/gdbserver:

2016-10-24  Yao Qi  <yao.qi@linaro.org>

	PR server/20733
	* linux-aarch64-low.c (append_insns): Cast the return value to
	'uint32_t *'.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix obvious gotcha in string comparison
@ 2016-10-26 21:08 sergiodj+buildbot
  2016-10-27  2:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 21:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 010ece9c47f1ac08c9436b133a74472713dd709b ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 010ece9c47f1ac08c9436b133a74472713dd709b

Fix obvious gotcha in string comparison

This patch fixes a gotcha when comparing exception's messages in
exception_print_same. It should've used the statically-allocated
string versions msg1 and msg2 instead.

As is, it could lead to crashes.

gdb/ChangeLog:
2016-10-24  Luis Machado  <lgustavo@codesourcery.com>

	* exec.c (exception_print_same): Fix string comparison to use
	statically-allocated ones.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix potential NULL pointer dereference
@ 2016-10-26 21:15 sergiodj+buildbot
  2016-10-27  3:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5e1db87897cabfd9beb8b1bd49f7d965c0f2607 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: b5e1db87897cabfd9beb8b1bd49f7d965c0f2607

Fix potential NULL pointer dereference

This patch addresses a potential NULL pointer dereference when we try to
duplicate a string. The input pointer can be NULL and that may lead to
crashes. We simply add a check for that case.

gdb/ChangeLog:
2016-10-24  Luis Machado  <lgustavo@codesourcery.com>

	* exec.c (exec_file_locate_attach): Prevent NULL pointer dereference
	when duplicating a string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make symfile_add_flags and objfile->flags strongly typed
@ 2016-10-26 21:33 sergiodj+buildbot
  2016-10-27 15:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-26 21:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b15cc25cbe7c13e450f77b4a309223b9b3da3936 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b15cc25cbe7c13e450f77b4a309223b9b3da3936

Make symfile_add_flags and objfile->flags strongly typed

This makes these flag types be "enum flag" types.  The benefit is
making use of C++'s stronger typing -- mixing the flags types by
mistake errors at compile time.

This caught one old bug in symbol_file_add_main_1 already, fixed by
this patch as well:

  @@ -1318,7 +1326,7 @@ symbol_file_add_main_1 (const char *args, int from_tty, int flags)
	what is frameless.  */
     reinit_frame_cache ();

  -  if ((flags & SYMFILE_NO_READ) == 0)
  +  if ((add_flags & SYMFILE_NO_READ) == 0)
       set_initial_language ();
   }

Above, "flags" are objfile flags, not symfile_add_flags.  So that was
actually checking for "flag & OBJF_PSYMTABS_READ", which has the same
value as SYMFILE_NO_READ...

I moved the flags definitions to separate files to break circular
dependencies.

Built with --enable-targets=all and tested on x86-64 Fedora 23.

gdb/ChangeLog:
2016-10-26  Pedro Alves  <palves@redhat.com>

	* coffread.c (coff_symfile_read): Use symfile_add_flags.
	* dbxread.c (dbx_symfile_read): Ditto.
	* elfread.c (elf_symfile_read): Ditto.
	* inferior.h: Include symfile-add-flags.h.
	(struct inferior) <symfile_flags>: Now symfile_add_flags.
	* machoread.c (macho_add_oso_symfile, macho_symfile_read_all_oso)
	(macho_symfile_read, mipscoff_symfile_read): Use
	symfile_add_flags.
	* objfile-flags.h: New file.
	* objfiles.c (allocate_objfile): Use objfile_flags.
	* objfiles.h: Include objfile-flags.h.
	(struct objfile) <flags>: Now an objfile_flags.
	(OBJF_REORDERED, OBJF_SHARED, OBJF_READNOW, OBJF_USERLOADED)
	(OBJF_PSYMTABS_READ, OBJF_MAINLINE, OBJF_NOT_FILENAME): Delete.
	Converted to an enum-flags in objfile-flags.h.
	(allocate_objfile): Use objfile_flags.
	* python/py-objfile.c (objfpy_add_separate_debug_file): Remove
	unnecessary local.
	* solib.c (solib_read_symbols, solib_add)
	(reload_shared_libraries_1): Use symfile_add_flags.
	* solib.h: Include "symfile-add-flags.h".
	(solib_read_symbols): Use symfile_add_flags.
	* symfile-add-flags.h: New file.
	* symfile-debug.c (debug_sym_read): Use symfile_add_flags.
	* symfile-mem.c (symbol_file_add_from_memory): Use
	symfile_add_flags.
	* symfile.c (read_symbols, syms_from_objfile_1)
	(syms_from_objfile, finish_new_objfile): Use symfile_add_flags.
	(symbol_file_add_with_addrs): Use symfile_add_flags and
	objfile_flags.
	(symbol_file_add_separate): Use symfile_add_flags.
	(symbol_file_add_from_bfd, symbol_file_add): Use symfile_add_flags
	and objfile_flags.
	(symbol_file_add_main_1): : Use objfile_flags.  Fix add_flags vs
	flags confusion.
	(symbol_file_command): Use objfile_flags.
	(add_symbol_file_command): Use symfile_add_flags and
	objfile_flags.
	(clear_symtab_users): Use symfile_add_flags.
	* symfile.h: Include "symfile-add-flags.h" and "objfile-flags.h".
	(struct sym_fns) <sym_read>: Use symfile_add_flags.
	(clear_symtab_users): Use symfile_add_flags.
	(enum symfile_add_flags): Delete, moved to symfile-add-flags.h and
	converted to enum-flags.
	(symbol_file_add, symbol_file_add_from_bfd)
	(symbol_file_add_separate): Use symfile_add_flags.
	* xcoffread.c (xcoff_initial_scan): Use symfile_add_flags.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make dwarf_expr_context's destructor virtual
@ 2016-10-27  1:11 sergiodj+buildbot
  2016-10-27 11:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27  1:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT beb18c865c42ab57176099eecb65bb52e71def85 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: beb18c865c42ab57176099eecb65bb52e71def85

Make dwarf_expr_context's destructor virtual

Ref: https://sourceware.org/ml/gdb-patches/2016-10/msg00662.html

 $ make WERROR_CFLAGS="-Wnon-virtual-dtor" dwarf2expr.o
 ...
 In file included from .../src/gdb/dwarf2expr.c:28:0:
 .../src/gdb/dwarf2expr.h:68:8: warning: struct dwarf_expr_context has virtual functions and accessible non-virtual destructor [-Wnon-virtual-dtor]
  struct dwarf_expr_context
	 ^~~~~~~~~~~~~~~~~~

Happens to not be a problem in practice currently because concrete
subclasses are allocated on the stack.  I.e., we don't ever delete
objects of types that derive from dwarf_expr_context through pointers
to dwarf_expr_context.

gdb/ChangeLog:
2016-10-25  Pedro Alves  <palves@redhat.com>

	* dwarf2expr.h (struct dwarf_expr_context) <~dwarf_expr_context>:
	Make virtual.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't override operator new if GDB is built with -fsanitize=address
@ 2016-10-27  2:24 sergiodj+buildbot
  2016-10-27  4:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27  2:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ef9d661f45abfaca5d0c0bb2ea9ab60470f1bb7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3ef9d661f45abfaca5d0c0bb2ea9ab60470f1bb7

Don't override operator new if GDB is built with -fsanitize=address

Nowadays, if we build GDB with -fsanitize=address, we can get the asan
error below,

(gdb) quit
=================================================================
==9723==ERROR: AddressSanitizer: alloc-dealloc-mismatch (malloc vs operator delete) on 0x60200003bf70
    #0 0x7f88f3837527 in operator delete(void*) (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x55527)
    #1 0xac8e13 in __gnu_cxx::new_allocator<void (*)()>::deallocate(void (**)(), unsigned long) /usr/include/c++/4.9/ext/new_allocator.h:110
    #2 0xac8cc2 in __gnu_cxx::__alloc_traits<std::allocator<void (*)()> >::deallocate(std::allocator<void (*)()>&, void (**)(), unsigned long) /usr/include/c++/4.9/ext/alloc_traits.h:185
....
0x60200003bf70 is located 0 bytes inside of 8-byte region [0x60200003bf70,0x60200003bf78)
allocated by thread T0 here:
    #0 0x7f88f38367ef in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x547ef)
    #1 0xbd2762 in operator new(unsigned long) /home/yao/SourceCode/gnu/gdb/git/gdb/common/new-op.c:42
    #2 0xac8edc in __gnu_cxx::new_allocator<void (*)()>::allocate(unsigned long, void const*) /usr/include/c++/4.9/ext/new_allocator.h:104
    #3 0xac8d81 in __gnu_cxx::__alloc_traits<std::allocator<void (*)()> >::allocate(std::allocator<void (*)()>&, unsigned long) /usr/include/c++/4.9/ext/alloc_traits.h:182

The reason for this is that we override operator new but don't override
operator delete.  This patch does the override if the code is NOT
compiled with asan.

gdb:

2016-10-25  Yao Qi  <yao.qi@linaro.org>

	PR gdb/20716
	* common/new-op.c (__has_feature): New macro.
	Don't override operator new if asan is used.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] new-op.c: Add comment about -fsanitize=address
@ 2016-10-27  4:28 sergiodj+buildbot
  2016-10-27  6:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27  4:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4426cb42f082b0dc1298a173014f18ff0ff7ea7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: e4426cb42f082b0dc1298a173014f18ff0ff7ea7

new-op.c: Add comment about -fsanitize=address

gdb/ChangeLog:
2016-10-25  Pedro Alves  <palves@redhat.com>

	* common/new-op.c: Add comment about -fsanitize=address.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS again.
@ 2016-10-27  4:45 sergiodj+buildbot
  2016-10-27  5:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27  4:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28fe4f87e0b815f4c0d9b80e0a9f3e6a53c649b3 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 28fe4f87e0b815f4c0d9b80e0a9f3e6a53c649b3

Define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS again.

Revert commit f6abaf7a4088 (gdb: no longer define
__STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS), with the tweak suggested
in that commit's log: the macros are now defined before any system
header is included.

This should fix AIX:
  https://sourceware.org/ml/gdb-patches/2016-10/msg00682.html

gdb/ChangeLog:
2016-10-25  Pedro Alves  <palves@redhat.com>

       * common/common-defs.h (__STDC_CONSTANT_MACROS)
       (__STDC_LIMIT_MACROS): Define.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gas/arc: Don't rely on bfd list of cpu type for cpu selection
@ 2016-10-27 12:23 sergiodj+buildbot
  2016-10-27 16:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb65a718b601ecfebd1ebe5be71728d5c359c31f ***

Author: Andrew Burgess <andrew.burgess@embecosm.com>
Branch: master
Commit: bb65a718b601ecfebd1ebe5be71728d5c359c31f

gas/arc: Don't rely on bfd list of cpu type for cpu selection

In the ARC assembler, when a cpu type is specified using the .cpu
directive, we rely on the bfd list of arc machine types in order to
validate the cpu name passed in.

This validation is only used in order to check that the cpu type passed
to the .cpu directive matches any machine type selected earlier on the
command line.  Once that initial check has passed a full check is
performed using the assemblers internal list of know cpu types.

The problem is that the assembler knows about more cpu types than bfd,
some cpu types known by the assembler are actually aliases for a base
cpu type plus a specific set of assembler extensions.  One such example
is NPS400, though more could be added later.

This commit removes the need for the assembler to use the bfd list of
machine types for validation.  Instead the error checking, to ensure
that any value passed to a '.cpu' directive matches any earlier command
line selection, is moved into the function arc_select_cpu.

I have taken the opportunity to bundle the 4 separate static globals
that describe the currently selected machine type into a single
structure (called selected_cpu).

gas/ChangeLog:

	* config/tc-arc.c (arc_target): Delete.
	(arc_target_name): Delete.
	(arc_features): Delete.
	(arc_mach_type): Delete.
	(mach_type_specified_p): Delete.
	(enum mach_selection_type): New enum.
	(mach_selection_mode): New static global.
	(selected_cpu): New static global.
	(arc_eflag): Rename to ...
	(arc_initial_eflag): ...this, and make const.
	(arc_select_cpu): Update comment, new parameter, check how
	previous machine type selection was made, and record this
	selection.  Use selected_cpu instead of old globals.
	(arc_option): Remove use of arc_get_mach, instead use
	arc_select_cpu to validate machine type selection.  Use
	selected_cpu over old globals.
	(allocate_tok): Use selected_cpu over old globals.
	(find_opcode_match): Likewise.
	(assemble_tokens): Likewise.
	(arc_cons_fix_new): Likewise.
	(arc_extinsn): Likewise.
	(arc_extcorereg): Likewise.
	(md_begin): Update default machine type selection, use
	selected_cpu over old globals.
	(md_parse_option): Update machine type selection option handling,
	use selected_cpu over old globals.
	* testsuite/gas/arc/nps400-0.s: Add .cpu directive.

bfd/ChangeLog:

	* cpu-arc.c (arc_get_mach): Delete.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Coalesce/aggregate (async) vCont packets/actions
@ 2016-10-27 13:09 sergiodj+buildbot
  2016-10-27 13:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27 13:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85ad3aaf403d2104c82010494d3d4a93a36e2e6f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 85ad3aaf403d2104c82010494d3d4a93a36e2e6f

gdb: Coalesce/aggregate (async) vCont packets/actions

Currently, with "maint set target-non-stop on", that is, when gdb
connects with the non-stop/asynchronous variant of the remote
protocol, even with "set non-stop off", GDB always sends one vCont
packet per thread resumed.  This patch makes GDB aggregate and
coalesce vCont packets, so we send vCont packets like "vCont;s:p1.1;c"
in non-stop mode too.

Basically, this is done by:

  - Adding a new target method target_commit_resume that is called
    after calling target_resume one or more times.  When resuming a
    batch of threads, we'll only call target_commit_resume once after
    calling target_resume for all threads.

  - Making the remote target defer sending the actual vCont packet to
    target_commit_resume.

Special care must be taken to avoid sending a vCont action with a
"wildcard" thread-id (all threads of process / all threads) when that
would resume threads/processes that should not be resumed.  See
remote_commit_resume comments for details.

Unlike all-stop's remote_resume implementation, this handles the case
of too many actions resulting in a too-big vCont packet, by flushing
the vCont packet and starting a new one.

E.g., imagining that the "c" action in:

  vCont;s:1;c

overflows the packet buffer, we split the actions like:

  vCont;s:1
  vCont;c

Tested on x86_64 Fedora 20, with and without "maint set
target-non-stop on".

Also tested with a hack that makes remote_commit_resume flush the vCont
packet after every action appended (which caught a few bugs).

gdb/ChangeLog:
2016-10-26  Pedro Alves  <palves@redhat.com>

	* inferior.h (ALL_NON_EXITED_INFERIORS): New macro.
	* infrun.c (do_target_resume): Call target_commit_resume.
	(proceed): Defer target_commit_resume while looping over threads,
	resuming them.  Call target_commit_resume at the end.
	* record-btrace.c (record_btrace_commit_resume): New function.
	(init_record_btrace_ops): Install it as to_commit_resume method.
	* record-full.c (record_full_commit_resume): New function.
	(record_full_wait_1): Call the beneath target's to_commit_resume
	method.
	(init_record_full_ops): Install record_full_commit_resume as
	to_commit_resume method.
	* remote.c (struct private_thread_info) <last_resume_step,
	last_resume_sig, vcont_resumed>: New fields.
	(remote_add_thread): Set the new thread's vcont_resumed flag.
	(demand_private_info): Delete.
	(get_private_info_thread, get_private_info_ptid): New functions.
	(remote_update_thread_list): Adjust.
	(process_initial_stop_replies): Clear the thread's vcont_resumed
	flag.
	(remote_resume): If connected in non-stop mode, record the resume
	request and return early.
	(struct private_inferior): New.
	(struct vcont_builder): New.
	(vcont_builder_restart, vcont_builder_flush)
	(vcont_builder_push_action): New functions.
	(MAX_ACTION_SIZE): New macro.
	(remote_commit_resume): New function.
	(thread_pending_fork_status, is_pending_fork_parent_thread): New
	functions.
	(check_pending_event_prevents_wildcard_vcont_callback)
	(check_pending_events_prevent_wildcard_vcont): New functions.
	(process_stop_reply): Adjust.  Clear the thread's vcont_resumed
	flag.
	(init_remote_ops): Install remote_commit_resume.
	* target-delegates.c: Regenerate.
	* target.c (defer_target_commit_resume): New global.
	(target_commit_resume, make_cleanup_defer_target_commit_resume):
	New functions.
	* target.h (struct target_ops) <to_commit_resume>: New field.
	(target_resume): Update comments.
	(target_commit_resume): New declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Get pending events in random
@ 2016-10-27 17:15 sergiodj+buildbot
  2016-10-27 19:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27 17:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 89342618773b64db3e67701c0cd9dd89cdbbc18a ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 89342618773b64db3e67701c0cd9dd89cdbbc18a

Get pending events in random

Nowadays, we select events to be reported to GDB in random, however
that is not enough when many GDBserver internal events (not reported
to GDB) are generated.

GDBserver pulls all events out of kernel via waitpid, and leave them
pending.  When goes through threads which have pending events,
GDBserver uses find_inferior to find the first thread which has
pending event, and consumes it.  Note that find_inferior always
iterate threads in a fixed order.  If multiple threads keep hitting
GDBserver breakpoints, range stepping with single-step breakpoint for
example, threads in the head of the thread list are more likely to be
processed and threads in the tail are starved.  This causes some timeout
fails in gdb.threads/non-stop-fair-events.exp when range stepping is
enabled on arm-linux.

This patch fixes this issue by randomly selecting pending events.  It
adds a new function find_inferior_in_random, which iterates threads
which have pending events randomly.

gdb/gdbserver:

2016-10-27  Yao Qi  <yao.qi@linaro.org>

	* inferiors.c (find_inferior_in_random): New function.
	* inferiors.h (find_inferior_in_random): Declare.
	* linux-low.c (linux_wait_for_event_filtered): Call
	find_inferior_in_random instead of find_inferior.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Enable range stepping if software single step is supported
@ 2016-10-27 17:39 sergiodj+buildbot
  2016-10-27 20:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-27 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c38058942ececeb32c381a838a10277ba43be94c ***

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

Enable range stepping if software single step is supported

If the target can do software single step, it can do range
stepping.

gdb/gdbserver:

2016-10-27  Yao Qi  <yao.qi@linaro.org>

	* linux-low.c (linux_supports_agent): Return true if
	can_software_single_step return true.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] btrace: fix gap indication
@ 2016-10-28  9:54 sergiodj+buildbot
  2016-10-28 10:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63ab433e29b2715f429551cdbec72dab0d752c20 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 63ab433e29b2715f429551cdbec72dab0d752c20

btrace: fix gap indication

Trace gaps due to overflows or non-contiguous trace are ignored in the 'info
record' command.  Fix that.

Also add a warning when decoding the trace and print the instruction number
preceding the trace gap in that warning message.  It looks like this:

    (gdb) info record
    Active record target: record-btrace
    Recording format: Intel Processor Trace.
    Buffer size: 16kB.
    warning: Decode error (-13) at instruction 101044 (offset = 0x29f0, pc = 0x7ffff728a642): no memory mapped at this address.
    Recorded 101044 instructions in 2093 functions (1 gaps) for thread 1 (process 5360).
    (gdb) record instruction-history 101044
    101044     0x00007ffff728a640:  pop    %r13
    [decode error (-13): no memory mapped at this address]

Remove the dead code that was supposed to print a gaps warning at the end of
trace decode.  This isn't really needed since we now print a warning for each
gap.

gdb/
	* btrace.c (ftrace_add_pt): Fix gap indication.  Add warning for non-
	contiguous trace and overflow.  Rephrase trace decode warning and print
	instruction number.  Remove dead gaps warning.
	(btrace_compute_ftrace_bts): Rephrase warnings and print instruction
	number.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] btrace: allow leading trace gaps
@ 2016-10-28 10:04 sergiodj+buildbot
  2016-10-28 11:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28 10:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b61ce85cc54bf4acc86714cacd10d6f9f7e89d1b ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: b61ce85cc54bf4acc86714cacd10d6f9f7e89d1b

btrace: allow leading trace gaps

GDB ignores trace gaps from decode errors or overflows at the beginning of the
trace.  There isn't really a gap in the trace; the trace just starts a bit
later than expected.

In cases where there is no trace at all or where the trace is smaller than
expected, this may hide the reason for the missing trace.

Allow leading trace gaps.  They will be shown as decode warnings and by the
record function-call-history command.

    (gdb) info record
    Active record target: record-btrace
    Recording format: Intel Processor Trace.
    Buffer size: 16kB.
    warning: Decode error (-6) at instruction 0 (offset = 0x58, pc = 0x0): unexpected packet context.
    warning: Decode error (-6) at instruction 0 (offset = 0xb0, pc = 0x0): unexpected packet context.
    warning: Decode error (-6) at instruction 0 (offset = 0x168, pc = 0x0): unexpected packet context.
    warning: Decode error (-6) at instruction 54205 (offset = 0xe08, pc = 0x0): unexpected packet context.
    warning: Decode error (-6) at instruction 54205 (offset = 0xe60, pc = 0x0): unexpected packet context.
    warning: Decode error (-6) at instruction 54205 (offset = 0xed8, pc = 0x0): unexpected packet context.
    Recorded 91582 instructions in 1111 functions (6 gaps) for thread 1 (process 15710).
    (gdb) record function-call-history /c 1
    1       [decode error (-6): unexpected packet context]
    2       [decode error (-6): unexpected packet context]
    3       [decode error (-6): unexpected packet context]
    4           _dl_addr
    5             ??
    6           _dl_addr
    7         ??
    8           ??
    9         ??
    10      ??

Leading trace gaps will not be shown by the record instruction-history command
without further changes.

gdb/
	* btrace.c (btrace_compute_ftrace_bts, ftrace_add_pt): Allow leading gaps.
	* record-btrace.c (record_btrace_single_step_forward)
	(record_btrace_single_step_backward): Jump back to last instruction if
	step ends at a gap.
	(record_btrace_goto_begin): Skip gaps.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] btrace: bridge gaps
@ 2016-10-28 12:51 sergiodj+buildbot
  2016-10-28 15:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28 12:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d87fdac3591d57c1a667b9d2dfeb05e3198b0b53 ***

Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: d87fdac3591d57c1a667b9d2dfeb05e3198b0b53

btrace: bridge gaps

Most of the time, the trace should be in one piece.  This case is handled fine
by GDB.  In some cases, however, there may be gaps in the trace.  They result
from trace decode errors or from overflows.

A gap in the trace means we lost an unknown amount of trace.  Gaps can be very
small, such as a few instructions in the same function, or they can be rather
big.  We may, for example, lose a few function calls or returns.  The trace may
continue in a different function and we likely don't know how we got there.

Even though we can't say how the program executed across a gap, higher levels
may not be impacted too much by it.  Let's assume we have functions a-e and a
trace that looks roughly like this:

  a
   \
    b                    b
     \                  /
      c   <gap>        c
                      /
                 d   d
                  \ /
                   e

Even though we can't say for sure, it is likely that b and c are the same
function instance before and after the gap.  This patch is trying to connect
the c and b function segments across the gap.

This will add a to the back trace of b on the right hand side.  The changes are
reflected in GDB's internal representation of the trace and will improve:

  - the output of "record function-call-history /c"
  - the output of "backtrace" in replay mode
  - source stepping in replay mode
    will be improved indirectly via the improved back trace

I don't have an automated test for this patch; decode errors will be fixed and
overflows occur sporadically and are quite rare.  I tested it by hacking GDB to
provoke a decode error and on the expected gap in the gdb.btrace/dlopen.exp
test.

The issue is that we can't predict where we will be able to re-sync in case of
errors.  For the expected decode error in gdb.btrace/dlopen.exp, for example, we
may be able to re-sync somewhere in dlclose, in test, in main, or not at all.

Here's one example run of gdb.btrace/dlopen.exp with and without this patch.

    (gdb) info record
    Active record target: record-btrace
    Recording format: Intel Processor Trace.
    Buffer size: 16kB.
    warning: Non-contiguous trace at instruction 66608 (offset = 0xa83, pc = 0xb7fdcc31).
    warning: Non-contiguous trace at instruction 66652 (offset = 0xa9b, pc = 0xb7fdcc31).
    warning: Non-contiguous trace at instruction 66770 (offset = 0xacb, pc = 0xb7fdcc31).
    warning: Non-contiguous trace at instruction 66966 (offset = 0xb60, pc = 0xb7ff5ee4).
    warning: Non-contiguous trace at instruction 66994 (offset = 0xb74, pc = 0xb7ff5f24).
    warning: Non-contiguous trace at instruction 67334 (offset = 0xbac, pc = 0xb7ff5e6d).
    warning: Non-contiguous trace at instruction 69022 (offset = 0xc04, pc = 0xb7ff60b3).
    warning: Non-contiguous trace at instruction 69116 (offset = 0xc1c, pc = 0xb7ff60b3).
    warning: Non-contiguous trace at instruction 69504 (offset = 0xc74, pc = 0xb7ff605d).
    warning: Non-contiguous trace at instruction 83648 (offset = 0xecc, pc = 0xb7ff6134).
    warning: Decode error (-13) at instruction 83876 (offset = 0xf48, pc = 0xb7fd6380): no memory mapped at this address.
    warning: Non-contiguous trace at instruction 83876 (offset = 0x11b7, pc = 0xb7ff1c70).
    Recorded 83948 instructions in 912 functions (12 gaps) for thread 1 (process 12996).
    (gdb) record instruction-history 83876, +2
    83876   => 0xb7fec46f <call_init.part.0+95>:    call   *%eax
    [decode error (-13): no memory mapped at this address]
    [disabled]
    83877      0xb7ff1c70 <_dl_close_worker.part.0+1584>:   nop

Without the patch, the trace is disconnected and the backtrace is short:

    (gdb) record goto 83876
    #0  0xb7fec46f in call_init.part () from /lib/ld-linux.so.2
    (gdb) backtrace
    #0  0xb7fec46f in call_init.part () from /lib/ld-linux.so.2
    #1  0xb7fec5d0 in _dl_init () from /lib/ld-linux.so.2
    #2  0xb7ff0fe3 in dl_open_worker () from /lib/ld-linux.so.2
    Backtrace stopped: not enough registers or memory available to unwind further
    (gdb) record goto 83877
    #0  0xb7ff1c70 in _dl_close_worker.part.0 () from /lib/ld-linux.so.2
    (gdb) backtrace
    #0  0xb7ff1c70 in _dl_close_worker.part.0 () from /lib/ld-linux.so.2
    #1  0xb7ff287a in _dl_close () from /lib/ld-linux.so.2
    #2  0xb7fc3d5d in dlclose_doit () from /lib/libdl.so.2
    #3  0xb7fec354 in _dl_catch_error () from /lib/ld-linux.so.2
    #4  0xb7fc43dd in _dlerror_run () from /lib/libdl.so.2
    #5  0xb7fc3d98 in dlclose () from /lib/libdl.so.2
    #6  0x0804860a in test ()
    #7  0x08048628 in main ()

With the patch, GDB is able to connect the trace pieces and we get a full
backtrace.

    (gdb) record goto 83876
    #0  0xb7fec46f in call_init.part () from /lib/ld-linux.so.2
    (gdb) backtrace
    #0  0xb7fec46f in call_init.part () from /lib/ld-linux.so.2
    #1  0xb7fec5d0 in _dl_init () from /lib/ld-linux.so.2
    #2  0xb7ff0fe3 in dl_open_worker () from /lib/ld-linux.so.2
    #3  0xb7fec354 in _dl_catch_error () from /lib/ld-linux.so.2
    #4  0xb7ff02e2 in _dl_open () from /lib/ld-linux.so.2
    #5  0xb7fc3c65 in dlopen_doit () from /lib/libdl.so.2
    #6  0xb7fec354 in _dl_catch_error () from /lib/ld-linux.so.2
    #7  0xb7fc43dd in _dlerror_run () from /lib/libdl.so.2
    #8  0xb7fc3d0e in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2
    #9  0xb7ff28ee in _dl_runtime_resolve () from /lib/ld-linux.so.2
    #10 0x0804841c in ?? ()
    #11 0x08048470 in dlopen@plt ()
    #12 0x080485a3 in test ()
    #13 0x08048628 in main ()
    (gdb) record goto 83877
    #0  0xb7ff1c70 in _dl_close_worker.part.0 () from /lib/ld-linux.so.2
    (gdb) backtrace
    #0  0xb7ff1c70 in _dl_close_worker.part.0 () from /lib/ld-linux.so.2
    #1  0xb7ff287a in _dl_close () from /lib/ld-linux.so.2
    #2  0xb7fc3d5d in dlclose_doit () from /lib/libdl.so.2
    #3  0xb7fec354 in _dl_catch_error () from /lib/ld-linux.so.2
    #4  0xb7fc43dd in _dlerror_run () from /lib/libdl.so.2
    #5  0xb7fc3d98 in dlclose () from /lib/libdl.so.2
    #6  0x0804860a in test ()
    #7  0x08048628 in main ()

It worked nicely in this case but it may, of course, also lead to weird
connections; it is a heuristic, after all.

It works best when the gap is small and the trace pieces are long.

gdb/
	* btrace.c (bfun_s): New typedef.
	(ftrace_update_caller): Print caller in debug dump.
	(ftrace_get_caller, ftrace_match_backtrace, ftrace_fixup_level)
	(ftrace_compute_global_level_offset, ftrace_connect_bfun)
	(ftrace_connect_backtrace, ftrace_bridge_gap, btrace_bridge_gaps): New.
	(btrace_compute_ftrace_bts): Pass vector of gaps.  Collect gaps.
	(btrace_compute_ftrace_pt): Likewise.
	(btrace_compute_ftrace): Split into this, ...
	(btrace_compute_ftrace_1): ... this, and ...
	(btrace_finalize_ftrace): ... this.  Call btrace_bridge_gaps.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix gdb.base/maint.exp regressions
@ 2016-10-28 14:01 sergiodj+buildbot
  2016-10-28 15:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28 14:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 44d83468ec8e5fccf904d66b752ac36e07d66c56 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 44d83468ec8e5fccf904d66b752ac36e07d66c56

Fix gdb.base/maint.exp regressions

This commit fixes these regressions:

 FAIL: gdb.base/maint.exp: mt set per on for expand-symtabs
 FAIL: gdb.base/maint.exp: maint set per-command on

caused by commit 1e3b796d58ac ("Change command stats reporting to use
class").

gdb.log shows that the command stats are now printing garbage:

 (gdb) mt set per on
 Command execution time: -6.-419590 (cpu), 1467139648.-7706296840 (wall)
 Space used: 9809920 (-33276528 for this command)
 (gdb) FAIL: gdb.base/maint.exp: mt set per on for expand-symtabs

while there should have been no output at all.

The stats printing is done from within the scoped_command_stats's
destructor, depending on whether some flags in the object are set.
The problem is simply that scoped_command_stats's ctor misses clearing
those flags on some paths.

Since scoped_command_stats objects are allocated on the stack, whether
you'll see the regression simply depends on whatever happens to
already be on the stack space the object occupies.

gdb/ChangeLog:
2016-10-28  Pedro Alves  <palves@redhat.com>

	* maint.c (scoped_command_stats::scoped_command_stats): Clear
	m_space_enabled, m_time_enabled and m_symtab_enabled.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb.base/foll-exec.exp test pattern more general
@ 2016-10-28 15:01 sergiodj+buildbot
  2016-10-28 16:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28 15:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b129b0cacd4c8e982605b7c8d99e96c74155882a ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: b129b0cacd4c8e982605b7c8d99e96c74155882a

Make gdb.base/foll-exec.exp test pattern more general

Testing a powerpc toolchain running gdbserver on the other end i noticed a
failure in gdb.base/foll-exec.exp.  Turns out gdb is outputting a slightly
different pattern due to the presence of debug information.

--
foll-exec is about to execlp(execd-prog)...^M
Continuing.^M
process 21222 is executing new program: gdb.d/outputs/gdb.base/foll-exec/execd-prog^M
^M
Catchpoint 2 (exec'd gdb.d/outputs/gdb.base/foll-exec/execd-prog), _start () at ../sysdeps/powerpc/powerpc32/dl-start.S:32^M
--

Notice the presence of source file information.

Now, on my local machine, i get this:

--
foll-exec is about to execlp(execd-prog)...^M
Continuing.^M
process 9285 is executing new program: gdb/testsuite/outputs/gdb.base/foll-exec/execd-prog^M
^M
Catchpoint 2 (exec'd gdb/testsuite/outputs/gdb.base/foll-exec/execd-prog), 0x00007ffff7dd7cc0 in ?? () from /lib64/ld-linux-x86-64.so.2^M
--

So the output differs slightly and the testcase is actually expecting only
the second form with the "in" anchor.

This patch removes the "in" pattern and lets the test match both kinds of
output.

gdb/testsuite/ChangeLog:

2016-10-28  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/foll-exec.exp (do_exec_tests): Make test pattern more
	general.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/testsuite: Avoid a buffer overrun in `gdb.base/maint.exp'
@ 2016-10-28 15:46 sergiodj+buildbot
  2016-10-28 17:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28 15:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f610ab6d3cbab5d8b8ef3f3a93dd81a800ec5725 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: f610ab6d3cbab5d8b8ef3f3a93dd81a800ec5725

gdb/testsuite: Avoid a buffer overrun in `gdb.base/maint.exp'

Fixes:

 PASS: gdb.base/maint.exp: maint w/o args
 ERROR: internal buffer is full.
 UNRESOLVED: gdb.base/maint.exp: maint info line-table w/o a file name

The problem is just many symtabs and long line tables, enough to
overflow the expect buffer.  Fix this by matching input incrementally.

gdb/testsuite/ChangeLog:
2016-10-28  Pedro Alves  <palves@redhat.com>

	* gdb.base/maint.exp <maint info line-table w/o a file name>: Use
	gdb_test_multiple, tighten regexps and match symtabs and line
	tables incrementally.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Require C++11
@ 2016-10-28 17:46 sergiodj+buildbot
  2016-10-28 22:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-28 17:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bcda68539948828795564b35a497dc69c27f768 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 0bcda68539948828795564b35a497dc69c27f768

gdb: Require C++11

Use AX_CXX_COMPILE_STDCXX to detect if the compiler supports C++11,
and if -std=xxx switches are necessary to enable C++11.

We need to tweak AX_CXX_COMPILE_STDCXX a bit though.  Pristine
upstream AX_CXX_COMPILE_STDCXX appends -std=gnu++11 to CXX directly.
That doesn't work for us, because the top level Makefile passes CXX
down to subdirs, and that overrides whatever gdb/Makefile may set CXX
to.  The result would be that a make invocation from the build/gdb/
directory would use "g++ -std=gnu++11" as expected, while a make
invocation at the top level would not.

So instead of having AX_CXX_COMPILE_STDCXX set CXX directly, tweak it
to AC_SUBST a separate variable -- CXX_DIALECT -- and use '$(CXX)
(CXX_DIALECT)' to compile/link.

Confirmed that this enables C++11 starting with gcc 4.8, the first gcc
release with full C++11 support.

Also confirmed that configure errors out gracefully with older GCC
releases:

  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features by default... no
  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features with -std=gnu++11... no
  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features with -std=gnu++0x... no
  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features with -std=c++11... no
  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features with -std=c++0x... no
  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features with +std=c++11... no
  checking whether /opt/gcc-4.7/bin/g++ supports C++11 features with -h std=c++11... no
  configure: error: *** A compiler with support for C++11 language features is required.
  Makefile:9451: recipe for target 'configure-gdb' failed
  make[1]: *** [configure-gdb] Error 1
  make[1]: Leaving directory '/home/pedro/brno/pedro/gdb/mygit/cxx-convertion/build-gcc-4.7'

If we need to revert back to making C++11 optional, all that's
necessary is to change the "mandatory" to "optional" in configure.ac
and regenerate configure (both gdb and gdbserver).

gdb/ChangeLog:
2016-10-28  Pedro Alves  <palves@redhat.com>

	* Makefile.in (CXX_DIALECT): Get from configure.
	(COMPILE.pre, CC_LD): Append $(CXX_DIALECT).
	(FLAGS_TO_PASS): Pass CXX_DIALECT.
	* acinclude.m4: Include ax_cxx_compile_stdcxx.m4.
	* ax_cxx_compile_stdcxx.m4: Add FSF copyright header.  Set and
	AC_SUBST CXX_DIALECT instead of changing CXX/CXXCPP.
	* configure.ac: Call AX_CXX_COMPILE_STDCXX.
	* config.in: Regenerate.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:
2016-10-28  Pedro Alves  <palves@redhat.com>

	* Makefile.in (CXX_DIALECT): Get from configure.
	(COMPILE.pre, CC_LD): Append $(CXX_DIALECT).
	* acinclude.m4: Include ../ax_cxx_compile_stdcxx.m4.
	* configure.ac: Call AX_CXX_COMPILE_STDCXX.
	* config.in: Regenerate.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Support command-line redirection in native MS-Windows debugging
@ 2016-10-29 16:13 sergiodj+buildbot
  2016-10-29 16:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-29 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ba42bc5da8015fd0bd9e7f021af9cb0ef252005 ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 8ba42bc5da8015fd0bd9e7f021af9cb0ef252005

Support command-line redirection in native MS-Windows debugging

gdb/ChangeLog
2016-10-29  Eli Zaretskii  <eliz@gnu.org>

	* NEWS: Mention support for redirection on MS-Windows.

	* windows-nat.c (redir_open, redir_set_redirection)
	(redirect_inferior_handles) [!__CYGWIN__]: New functions.
	(windows_create_inferior) [!__CYGWIN__]: Use
	'redirect_inferior_handles' to redirect standard handles of the
	debuggee if the command line requests that.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS: Remove remains of legacy remote target support
@ 2016-10-31 18:27 sergiodj+buildbot
  2016-10-31 18:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-31 18:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e3d947dd6ae45d71aa175b96fbd42a51e93b3f8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 7e3d947dd6ae45d71aa175b96fbd42a51e93b3f8

MIPS: Remove remains of legacy remote target support

Complement commit f7c382926d78 ("Remove support for "target m32rsdi" and
"target mips/pmon/ddb/rockhopper/lsi"") and remove dead MIPS target code
which used to support these legacy remote targets.

	gdb/
	* mips-tdep.c (mips_r3041_reg_names): Remove.
	(mips_breakpoint_from_pc): Remove IDT and PMON breakpoint
	encodings.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove IRIX 5 <sys/proc.h> _KMEMUSER workaround
@ 2016-10-31 19:02 sergiodj+buildbot
  2016-11-01 16:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-10-31 19:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c50730217d606814cda69a2bb6975730c0f1ee63 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: c50730217d606814cda69a2bb6975730c0f1ee63

Remove IRIX 5 <sys/proc.h> _KMEMUSER workaround

Complement commit 3831839c089c ("Delete IRIX support") and remove the
IRIX 5 <sys/proc.h> _KMEMUSER workaround from the `configure' script, as
IRIX is no longer a supported host configuration.

	gdb/
	* configure.ac <mips-sgi-irix5*>: Remove <sys/proc.h> _KMEMUSER
	workaround.
	* configure: Regenerate.
	* config.in: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix building binutils for all 32-bit targets by moving riscv32 target into 64-bit builds only.
@ 2016-11-04 14:52 sergiodj+buildbot
  2016-11-04 16:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-04 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b7a12f2d68f2f334fbe78cc2db76982ba6d4ef1 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 1b7a12f2d68f2f334fbe78cc2db76982ba6d4ef1

Fix building binutils for all 32-bit targets by moving riscv32 target into 64-bit builds only.

	* targets.c (bfd_target_vector): Only add riscv_elf32_vec target
	when supporting 64-bit BFD targets.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix a few typos
@ 2016-11-05  4:41 sergiodj+buildbot
  2016-11-05  5:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-05  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26c4b26f0cc51f04cdaba3c9e6ff09032bd10d8b ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 26c4b26f0cc51f04cdaba3c9e6ff09032bd10d8b

Fix a few typos

gdb/ChangeLog:

	* maint.c (scoped_command_stats::scoped_command_stats): Fix typo.
	* ppcnbsd-tdep.c (_initialize_ppcnbsd_tdep): Likewise.
	* ppcobsd-tdep.c (_initialize_ppcobsd_tdep): Likewise.
	* ui-out.c (ui_out_new): Likewise.
	* utils.c (init_page_info): Likewise.
	(reset_prompt_for_continue_wait_time): Likewise.
	* windows-nat.c (windows_init_thread_list): Likewise.
	* xtensa-tdep.c (call0_analyze_prologue): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix ext lang calls to value_struct_elt.
@ 2016-11-08  1:46 sergiodj+buildbot
  2016-11-08 10:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-08  1:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5996220cfa24ef6fddb782617720cd56913b1bb7 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 5996220cfa24ef6fddb782617720cd56913b1bb7

Fix ext lang calls to value_struct_elt.

gdb/ChangeLog:

	* guile/scm-value.c (gdbscm_value_field): Fix call to value_struct_elt.
	* python/py-value.c (valpy_getitem): Ditto.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step returns VEC (CORE_ADDR) *
@ 2016-11-08 17:10 sergiodj+buildbot
  2016-11-08 18:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 17:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93f9a11fbdb8f09428b17180d51a09a1bda39a52 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 93f9a11fbdb8f09428b17180d51a09a1bda39a52

gdbarch software_single_step returns VEC (CORE_ADDR) *

This patch changes gdbarch method software_single_step to return a
vector of addresses on which GDB should insert breakpoints, and don't
insert breakpoints.  Instead, the caller of
gdbarch_software_single_step inserts breakpoints if the returned
vector is not NULL.

gdb:

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

	* aarch64-tdep.c (aarch64_software_single_step): Return
	VEC (CORE_ADDR) *.  Return NULL instead of 0.  Don't call
	insert_single_step_breakpoint.
	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Likewise.
	(alpha_software_single_step): Likewise.
	* alpha-tdep.h (alpha_software_single_step): Update declaration.
	* arm-linux-tdep.c (arm_linux_software_single_step): Return
	VEC (CORE_ADDR) *.  Return NULL instead of 0.
	* arm-tdep.c (arm_software_single_step): Return NULL instead of	0.
	* arm-tdep.h (arm_software_single_step): Update declaration.
	* breakpoint.c (insert_single_step_breakpoints): New function.
	* breakpoint.h (insert_single_step_breakpoints): Declare.
	* cris-tdep.c (cris_software_single_step): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	* gdbarch.sh (software_single_step): Change it to return
	VEC (CORE_ADDR) *.
	* gdbarch.c, gdbarch.h: Regenerated.
	* infrun.c (maybe_software_singlestep): Adjust.
	* mips-tdep.c (mips_deal_with_atomic_sequence): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	(micromips_deal_with_atomic_sequence): Likewise.
	(deal_with_atomic_sequence): Likewise.
	(mips_software_single_step): Likewise.
	* mips-tdep.h (mips_software_single_step): Update declaration.
	* moxie-tdep.c (moxie_software_single_step): Likewise.
	* nios2-tdep.c (nios2_software_single_step): Likewise.
	* ppc-tdep.h (ppc_deal_with_atomic_sequence): Update
	declaration.
	* record-full.c (record_full_resume): Adjust.
	(record_full_wait_1): Likewise.
	* rs6000-aix-tdep.c (rs6000_software_single_step): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	* rs6000-tdep.c	(ppc_deal_with_atomic_sequence): Return
	VEC (CORE_ADDR) *.  Don't call insert_single_step_breakpoint.
	* s390-linux-tdep.c (s390_software_single_step): Likewise.
	* sparc-tdep.c (sparc_software_single_step): Likewise.
	* spu-tdep.c (spu_software_single_step): Likewise.
	* tic6x-tdep.c (tic6x_software_single_step): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string in dwarf2_compute_name
@ 2016-11-08 23:02 sergiodj+buildbot
  2016-11-09  5:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 23:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 322a851675234b3c16be6dd5035b07f5e3410ec7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 322a851675234b3c16be6dd5035b07f5e3410ec7

Use ui_file_as_string in dwarf2_compute_name

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* dwarf2read.c (dwarf2_compute_name): Use ui_file_as_string and
	std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/ui-out.c
@ 2016-11-09  2:14 sergiodj+buildbot
  2016-11-09  8:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  2:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56dbf31760f721893a44d3da26adfccf548995c7 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 56dbf31760f721893a44d3da26adfccf548995c7

Use ui_file_as_string in gdb/ui-out.c

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* ui-out.c (ui_out_field_stream): Use ui_file_as_string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/python/
@ 2016-11-09  8:07 sergiodj+buildbot
  2016-11-09 16:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  8:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c92aed165e8af79f51c5165f98f12389bb59a121 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: c92aed165e8af79f51c5165f98f12389bb59a121

Use ui_file_as_string in gdb/python/

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* python/py-arch.c (archpy_disassemble): Use ui_file_as_string and
	std::string.
	* python/py-breakpoint.c (bppy_get_commands): Use
	ui_file_as_string and std::string.
	* python/py-frame.c (frapy_str): Likewise.
	* python/py-type.c (typy_str): Likewise.
	* python/py-unwind.c (unwind_infopy_str): Likewise.
	* python/py-value.c (valpy_str): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/compile/
@ 2016-11-09 10:10 sergiodj+buildbot
  2016-11-09 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 10:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaee65aea29ac8f7317e866d5dbef9f96cfdb253 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: aaee65aea29ac8f7317e866d5dbef9f96cfdb253

Use ui_file_as_string in gdb/compile/

Using ui_file_as_string would imply changing a few prototypes to pass
around source and object file names as std::string.  Instead of that,
wrap those two in a new class.  This ends up eliminating a small
wrinkle: get_new_file_names and compile_object_load have swapped
parameters.  The former takes "source, objfile", while the latter
takes "objfile, source".

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* c-lang.h (c_compute_program): Now returns std::string.
	* compile/compile-internal.h (class compile_file_names): New
	class.
	* compile/compile-object-load.c (compile_object_load): Replace
	object_file and source_file parameters with a compile_file_names
	parameter.  Adjust.
	* compile-object-load.h: Include "compile-internal.h".
	(compile_object_load): Replace object_file and source_file
	parameters with a compile_file_names parameter.
	* compile/compile-c-support.c (c_compute_program): Now returns a
	std::string.  Use ui_file_as_string.
	* compile/compile.c (get_new_file_names): Remove parameters and
	return a compile_file_names instead.
	(compile_to_object): Now returns a compile_file_names.  Use
	ui_file_as_string.
	(eval_compile_command): Use compile_file_names.
	* language.h (struct language_defn) <la_compute_program>: Now
	returns std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/c-exp.y
@ 2016-11-09 10:46 sergiodj+buildbot
  2016-11-09 22:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 10:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 66bbce5bda870c49a68f2b77a29fb96eca72632f ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 66bbce5bda870c49a68f2b77a29fb96eca72632f

Use ui_file_as_string in gdb/c-exp.y

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* c-exp.y (OPERATOR NEW): Adjust to use ui_file_as_string and
	std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/language.c
@ 2016-11-09 15:45 sergiodj+buildbot
  2016-11-10  9:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2af8993a7cac29eaa5a4efd47c9117bbd175068 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: d2af8993a7cac29eaa5a4efd47c9117bbd175068

Use ui_file_as_string in gdb/language.c

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* language.c (add_language): Use ui_file_as_string and adjust to
	use std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] 'struct agent_expr *' -> unique_ptr<agent_expr>
@ 2016-11-09 17:48 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 833177a4a5c1a2a6cabe70bfe35ecf241b68d169 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 833177a4a5c1a2a6cabe70bfe35ecf241b68d169

'struct agent_expr *' -> unique_ptr<agent_expr>

This patch makes the gen_* functions return a unique_ptr instead of
raw pointer:

  typedef gdb::unique_ptr<agent_expr> agent_expr_up;

and then adjusts the codebase throughout to stop using
make_cleanup_free_agent_expr.

The cond_bytecode and cmd_bytecode fields of struct bp_location are
owning pointers, so they're changed to be unique_ptr's instead of raw
pointers.

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* ax-gdb.c (is_nontrivial_conversion): Use agent_expr_up.
	(gen_trace_for_var, gen_trace_for_expr, gen_eval_for_expr)
	(gen_trace_for_return_address, gen_printf): Use and return an
	agent_expr_up.  Don't use make_cleanup_free_agent_expr.
	(agent_eval_command_one, maint_agent_printf_command): Use
	agent_expr_up.  Don't use make_cleanup_free_agent_expr.
	* ax-gdb.h (gen_trace_for_expr, gen_trace_for_var)
	(gen_trace_for_return_address, gen_eval_for_expr, gen_printf): Use
	agent_expr_up.
	* ax-general.c (new_agent_expr): Rename to ...
	(agent_expr::agent_expr): ... this, and now a constructor.
	(free_agent_expr): Rename to ...
	(agent_expr::~agent_exp): ... this, and now a destructor.
	(do_free_agent_expr_cleanup, make_cleanup_free_agent_expr):
	Delete.
	* ax.h (struct agent_expr): Add ctor/dtor.
	(agent_expr_up): New typedef.
	(new_agent_expr, free_agent_expr, make_cleanup_free_agent_expr):
	Delete declarations.
	* breakpoint.c (parse_cond_to_aexpr): Use and return an
	agent_expr_up.  Don't use make_cleanup_free_agent_expr.
	(build_target_condition_list): Adjust to use agent_expr_up.
	(parse_cmd_to_aexpr): Use and return an agent_expr_up.  Don't use
	make_cleanup_free_agent_expr.
	(build_target_command_list): Adjust to use agent_expr_up.
	(force_breakpoint_reinsertion): Adjust to use agent_expr_up.
	(bp_location_dtor): Remove unnecessary free_agent_expr and xfree
	calls.
	* breakpoint.h (struct bp_target_info) <cond_bytecode,
	cmd_bytecode>: Now agent_expr_up's.
	* remote.c (remote_download_tracepoint): Adjust to use
	agent_expr_up and remove use of make_cleanup_free_agent_expr.
	* tracepoint.c (validate_actionline, collect_symbol): Adjust to
	use agent_expr_up and remove uses of make_cleanup_free_agent_expr.
	(collection_list::~collection_list): Call delete instead of
	free_agent_expr.
	(encode_actions_1): Adjust to use agent_expr_up and remove uses of
	make_cleanup_free_agent_expr.
	(add_aexpr): Change parameter type to agent_expr_up; Return a raw
	agent_expr pointer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use ui_file_as_string throughout more
@ 2016-11-09 18:35 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f408ecb929bd56613e94cf1e84ace4692c78257 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2f408ecb929bd56613e94cf1e84ace4692c78257

Use ui_file_as_string throughout more

This replaces most of the remaining ui_file_xstrdup calls with
ui_file_as_string calls.  Whenever a call was replaced, that led to a
cascade of other necessary adjustments throughout, to make the code
use std::string instead of raw pointers.  And then whenever I added a
std::string as member of a struct, I needed to adjust
allocation/destruction of said struct to use new/delete instead of
xmalloc/xfree.

The stopping point was once gdb built again.  These doesn't seem to be
a way to reasonably split this out further.

Maybe-not-obvious changes:

 - demangle_for_lookup returns a cleanup today.  To get rid of that,
   and avoid unnecessary string dupping/copying, this introduces a
   demangle_result_storage type that the caller instantiates and
   passes to demangle_for_lookup.

 - Many methods returned a "char *" to indicate that the caller owns
   the memory and must free it.  Those are switched to return a
   std::string instead.  Methods that return a "view" into some
   internal string return a "const char *" instead.  I.e., we only
   copy/allocate when necessary.

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_name_for_lookup, type_as_string): Use and return
	std::string.
	(type_as_string_and_cleanup): Delete.
	(ada_lookup_struct_elt_type): Use type_as_string.
	* ada-lang.h (ada_name_for_lookup): Now returns std::string.
	* ada-varobj.c (ada_varobj_scalar_image): Return a std::string.
	(ada_varobj_describe_child): Make 'child_name' and
	'child_path_expr' parameters std::string pointers.
	(ada_varobj_describe_struct_child, ada_varobj_describe_ptr_child):
	Likewise, and use string_printf.
	(ada_varobj_describe_simple_array_child)
	(ada_varobj_describe_child): Likewise.
	(ada_varobj_get_name_of_child, ada_varobj_get_path_expr_of_child)
	(ada_varobj_get_value_image)
	(ada_varobj_get_value_of_array_variable)
	(ada_varobj_get_value_of_variable, ada_name_of_variable)
	(ada_name_of_child, ada_path_expr_of_child)
	(ada_value_of_variable): Now returns std::string.  Use
	string_printf.
	(ada_value_of_child): Adjust.
	* break-catch-throw.c (check_status_exception_catchpoint): Adjust
	to use std::string.
	* breakpoint.c (watch_command_1): Adjust to use std::string.
	* c-lang.c (c_get_string): Adjust to use std::string.
	* c-typeprint.c (print_name_maybe_canonical): Use std::string.
	* c-varobj.c (varobj_is_anonymous_child): Use ==/!= std::string
	operators.
	(c_name_of_variable): Now returns a std::string.
	(c_describe_child): The 'cname' and 'cfull_expression' output
	parameters are now std::string pointers.  Adjust.
	(c_name_of_child, c_path_expr_of_child, c_value_of_variable)
	(cplus_number_of_children): Adjust to use std::string and
	string_printf.
	(cplus_name_of_variable): Now returns a std::string.
	(cplus_describe_child): The 'cname' and 'cfull_expression' output
	parameters are now std::string pointers.  Adjust.
	(cplus_name_of_child, cplus_path_expr_of_child)
	(cplus_value_of_variable): Now returns a std::string.
	* cp-abi.c (cplus_typename_from_type_info): Return std::string.
	* cp-abi.h (cplus_typename_from_type_info): Return std::string.
	(struct cp_abi_ops) <get_typename_from_type_info>: Return
	std::string.
	* cp-support.c (inspect_type): Use std::string.
	(cp_canonicalize_string_full, cp_canonicalize_string_no_typedefs)
	(cp_canonicalize_string): Return std::string and adjust.
	* cp-support.h (cp_canonicalize_string)
	(cp_canonicalize_string_no_typedefs, cp_canonicalize_string_full):
	Return std::string.
	* dbxread.c (read_dbx_symtab): Use std::string.
	* dwarf2read.c (dwarf2_canonicalize_name): Adjust to use std::string.
	* gdbcmd.h (lookup_struct_elt_type): Adjust to use std::string.
	* gnu-v3-abi.c (gnuv3_get_typeid): Use std::string.
	(gnuv3_get_typename_from_type_info): Return a std::string and
	adjust.
	(gnuv3_get_type_from_type_info): Adjust to use std::string.
	* guile/guile.c (gdbscm_execute_gdb_command): Adjust to use
	std::string.
	* infcmd.c (print_return_value_1): Adjust to use std::string.
	* linespec.c (find_linespec_symbols): Adjust to
	demangle_for_lookup API change.  Use std::string.
	* mi/mi-cmd-var.c (print_varobj, mi_cmd_var_set_format)
	(mi_cmd_var_info_type, mi_cmd_var_info_path_expression)
	(mi_cmd_var_info_expression, mi_cmd_var_evaluate_expression)
	(mi_cmd_var_assign, varobj_update_one): Adjust to use std::string.
	* minsyms.c (lookup_minimal_symbol): Use std::string.
	* python/py-varobj.c (py_varobj_iter_next): Use new instead of
	XNEW.  vitem->name is a std::string now, adjust.
	* rust-exp.y (convert_ast_to_type, convert_name): Adjust to use
	std::string.
	* stabsread.c (define_symbol): Adjust to use std::string.
	* symtab.c (demangle_for_lookup): Now returns 'const char *'.  Add
	a demangle_result_storage parameter.  Use it for storage.
	(lookup_symbol_in_language)
	(lookup_symbol_in_objfile_from_linkage_name): Adjust to new
	demangle_for_lookup API.
	* symtab.h (struct demangle_result_storage): New type.
	(demangle_for_lookup): Now returns 'const char *'.  Add a
	demangle_result_storage parameter.
	* typeprint.c (type_to_string): Return std::string and use
	ui_file_as_string.
	* value.h (type_to_string): Change return type to std::string.
	* varobj-iter.h (struct varobj_item) <name>: Now a std::string.
	(varobj_iter_delete): Use delete instead of xfree.
	* varobj.c (create_child): Return std::string instead of char * in
	output parameter.
	(name_of_variable, name_of_child, my_value_of_variable): Return
	std::string instead of char *.
	(varobj_create, varobj_get_handle): Constify 'objname' parameter.
	Adjust to std::string fields.
	(varobj_get_objname): Return a const char * instead of a char *.
	(varobj_get_expression): Return a std::string.
	(varobj_list_children): Adjust to use std::string.
	(varobj_get_type): Return a std::string.
	(varobj_get_path_expr): Return a const char * instead of a char *.
	Adjust to std::string fields.
	(varobj_get_formatted_value, varobj_get_value): Return a
	std::string.
	(varobj_set_value): Change type of 'expression' parameter to
	std::string.  Use std::string.
	(install_new_value): Use std::string.
	(delete_variable_1): Adjust to use std::string.
	(create_child): Change the 'name' parameter to a std::string
	reference.  Swap it into the new item's name.
	(create_child_with_value): Swap item's name into the new child's
	name.  Use string_printf.
	(new_variable): Use new instead of XNEW.
	(free_variable): Don't xfree fields that are now std::string.
	(name_of_variable, name_of_child): Now returns std::string.
	(value_of_root): Adjust to use std::string.
	(my_value_of_variable, varobj_value_get_print_value): Return
	and use std::string.
	(varobj_value_get_print_value): Adjust to use ui_file_as_string
	and std::string.
	* varobj.h (struct varobj) <name, path_expr, obj_name,
	print_value>: Now std::string's.
	<name_of_variable, name_of_child, path_expr_of_child,
	value_of_variable>: Return std::string.
	(varobj_create, varobj_get_handle): Constify 'objname' parameter.
	(varobj_get_objname): Return a const char * instead of a char *.
	(varobj_get_expression, varobj_get_type): Return a std::string.
	(varobj_get_path_expr): Return a const char * instead of a char *.
	(varobj_get_formatted_value, varobj_get_value): Return a
	std::string.
	(varobj_set_value): Constify 'expression' parameter.
	(varobj_value_get_print_value): Return a std::string.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info
@ 2016-11-09 18:42 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 18:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cde5c42d1c1ddcf8bbde5c47233c644370c959c ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3cde5c42d1c1ddcf8bbde5c47233c644370c959c

Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info

After the previous patch, we end up with these two types with quite
similar, and potentially confusing names:

  typedef gdb::unique_ptr<agent_expr> agent_expr_up;

  /* Pointer to an agent_expr structure.  */
  typedef struct agent_expr *agent_expr_p;

The latter is only necessary to put agent_expr pointers in VECs.  So
just eliminate it and use std::vector instead.

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* ax.h (agent_expr_p): Delete.
	(DEF_VEC_P (agent_expr_p)): Delete.
	* breakpoint.c (build_target_condition_list)
	(build_target_command_list): Adjust to use of std::vector.
	(bp_location_dtor): Remove now unnecessary VEC_free calls.
	* breakpoint.h: Include <vector>.
	(struct bp_target_info) <conditions, tcommands>: Now
	std::vector's.
	* remote.c (remote_add_target_side_condition): bp_tgt->conditions
	is now a std::vector; adjust.
	(remote_add_target_side_commands, remote_insert_breakpoint):
	bp_tgt->tcommands is now a std::vector; adjust.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use get_frame_register_value instead of deprecated_frame_register_read
@ 2016-11-09 19:49 sergiodj+buildbot
  2016-11-10 10:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc977dc7d53ef4546592a4f02a2e06a621beae6f ***

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

Use get_frame_register_value instead of deprecated_frame_register_read

This patch calls get_frame_register_value instead of
deprecated_frame_register_read, so that we can pass
value_contents_for_printing to val_print.  Both
get_frame_register_value and deprecated_frame_register_read call
frame_unwind_register_value indirectly, so no functionality is changed
by this patch.

gdb:

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

	* mt-tdep.c (mt_registers_info): Call
	get_frame_register_value instead of
	deprecated_frame_register_read.
	* sh64-tdep.c (sh64_do_register): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove parameter valaddr from la_val_print
@ 2016-11-09 20:30 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e8b24d9ff5b9419fc079f5fe975fac6f499f8bfb ***

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

Remove parameter valaddr from la_val_print

Nowadays, we pass both val and return value of
value_contents_for_printing (val) to la_val_print.  The latter is
unnecessary.  This patch removes the second parameter of la_val_print,
and get valaddr in each language's implementation by calling
value_contents_for_printing.  Since value_contents_for_printing calls
value_fetch_lazy, I also make VAL non-const.

Note that
 - I don't clean up the valaddr usages in each language's routines,
 - I don't remove valaddr from apply_ext_lang_val_pretty_printer, and
   extension language ops apply_val_pretty_printer.

They can be done in followup patches.

gdb:

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

	* ada-lang.h (ada_val_print): Remove second parameter.  Remove
	const from "struct value *".
	* ada-valprint.c (print_field_values): Remove const from
	"struct value *".
	(val_print_packed_array_elements): Likewise.
	(print_variant_part): Likewise.
	(ada_val_print_string): Likewise.
	(ada_val_print_gnat_array): Likewise.
	(ada_val_print_ptr): Likewise.
	(ada_val_print_num): Likewise.
	(ada_val_print_enum): Likewise.
	(ada_val_print_flt): Likewise.
	(ada_val_print_union): Likewise.
	(ada_val_print_struct_union): Likewise.
	(ada_val_print_ref): Likewise.
	(ada_val_print_1): Remove second parameter.  Remove const from
	"struct value *".
	(ada_val_print): Likewise.
	* c-lang.h (c_val_print): Likewise.
	* c-valprint.c (c_val_print_array): Remove const from
	"struct value *".
	(c_val_print_ptr): Likewise.
	(c_val_print_struct): Likewise.
	(c_val_print_union): Likewise.
	(c_val_print_int): Likewise.
	(c_val_print_memberptr): Likewise.
	(c_val_print): Remove second parameter.  Remove const from
	"struct value *".  All callers updated.
	* cp-valprint.c (cp_print_value): Remove const from
	"struct value *".
	(cp_print_value_fields): Likewise.
	(c_val_print_value): Likewise.
	* d-lang.h (d_val_print): Remove second parameter.  Remove const
	from "struct value *".
	* d-valprint.c (dynamic_array_type): Likewise.
	(d_val_print): Likewise.
	* f-lang.h (f_val_print): Likewise.
	* f-valprint.c (f_val_print): Likewise.
	* go-lang.h (go_val_print): Likewise.
	* go-valprint.c (print_go_string): Likewise.
	(go_val_print): Likewise.
	* language.c (unk_lang_val_print): Likewise.
	* language.h (struct language_defn) <la_val_print>: Likewise.
	Update comments.
	(LA_VAL_PRINT): Remove.
	* m2-lang.h (m2_val_print): Remove const from
	"struct value *".
	* m2-valprint.c (m2_print_array_contents): Likewise.
	(m2_val_print): Likewise.
	* p-lang.h (pascal_val_print): Remove second parameter.  Remove
	const from "struct value *".
	(pascal_object_print_value_fields): Likewise.
	* p-valprint.c (pascal_val_print): Likewise.
	(pascal_object_print_value_fields): Likewise.
	(pascal_object_print_value): Likewise.
	* rust-lang.c (rust_get_disr_info): Likewise.
	(val_print_struct): Likewise.
	(rust_val_print): Likewise.
	* valprint.c (generic_val_print_array): Likewise.
	(generic_val_print_ptr): Likewise.
	(generic_val_print_memberptr): Likewise.
	(generic_val_print_ref): Likewise.
	(generic_val_print_enum): Likewise.
	(generic_val_print_flags): Likewise.
	(generic_val_print_func): Likewise.
	(generic_val_print_bool): Likewise.
	(generic_val_print_int): Likewise.
	(generic_val_print_char): Likewise.
	(generic_val_print_float): Likewise.
	(generic_val_print_decfloat): Likewise.
	(generic_val_print_complex): Likewise.
	(generic_val_print): Likewise.
	(val_print): Likewise.
	(common_val_print): Likewise.
	(val_print_type_code_flags): Likewise.
	(val_print_scalar_formatted): Likewise.
	(val_print_array_elements): Likewise.
	* valprint.h (val_print_array_elements): Update declaration.
	(val_print_scalar_formatted): Likewise.
	(generic_val_print): Likewise.
	* value.h (val_print): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix some error-handling bugs in python frame filters
@ 2016-11-09 21:50 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a7bb833cbd848b1814f18b91dfdafba4e86839 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 30a7bb833cbd848b1814f18b91dfdafba4e86839

Fix some error-handling bugs in python frame filters

While writing a Python frame filter, I found a few bugs in the current
frame filter code.  In particular:

* One spot converts a Python long to a CORE_ADDR using PyLong_AsLong.
  However, this can fail on overflow.  I changed this to use
  get_addr_from_python.

* Another spot is doing the same but with PyLong_AsUnsignedLongLong; I
  changed this as well just for consistency.

* Converting line numbers can print "-1" if conversion from long
  fails.  This isn't fatal but just a bit ugly.

I've included a test case for the first issue.  The line number one
didn't seem important enough to bother with.

2016-11-08  Tom Tromey  <tom@tromey.com>

	* python/py-framefilter.c (py_print_frame): Use
	get_addr_from_python.  Check for errors when getting line number.

2016-11-08  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-framefilter.py (ElidingFrameDecorator.address):
	New method.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry
@ 2016-11-09 23:16 sergiodj+buildbot
  2016-11-10 10:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 23:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f334aeb2268db153f01143e9b0ac01448ecaa56 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 1f334aeb2268db153f01143e9b0ac01448ecaa56

X86: Remove the THREE_BYTE_0F7A entry

Remove the THREE_BYTE_0F7A entry which is leftover from SSE5.

	PR binutils/20701
	* i386-dis.c (THREE_BYTE_0F7A): Removed.
	(dis386_twobyte): Don't use THREE_BYTE_0F7A.
	(three_byte_table): Remove THREE_BYTE_0F7A.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix py-value.exp failure on Python 3
@ 2016-11-09 23:50 sergiodj+buildbot
  2016-11-10 10:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-09 23:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7353f2470c2eda19c31c9fa44c315c7c69dea7c4 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 7353f2470c2eda19c31c9fa44c315c7c69dea7c4

Fix py-value.exp failure on Python 3

I happened to notice that one test in py-value.exp did not work
properly with Python 3.  This patch fixes the problem.

2016-11-08  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-value.exp (test_value_creation): Make "long" test
	depend on Python 2.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] darwin-nat.c: handle Darwin 16 (aka Sierra).
@ 2016-11-10  1:21 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  1:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82b19a4d2f9c9e8d56fdffdd702f7db4af486386 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 82b19a4d2f9c9e8d56fdffdd702f7db4af486386

darwin-nat.c: handle Darwin 16 (aka Sierra).

Support message from new task and dead name notification on task of an
existing process.
With Sierra, exec(2) terminate the current task and creates a new one.
'set startup-with-shell off' must still be used on Darwin 16.

2016-11-09  Tristan Gingold  <gingold@adacore.com>

	* darwin-nat.c (find_inferior_task_it): Fix indentation.
	(find_inferior_notify_it): Remove.
	(find_inferior_pid_it): New function.
	(darwin_find_inferior_by_notify): Remove.
	(darwin_find_inferior_by_pid): New function.
	(darwin_find_new_inferior): New function.
	(darwin_check_message_ndr): New function from
	darwin_decode_exception_message.
	(darwin_decode_exception_message): Call darwin_check_message_ndr.
	Handle SIGTRAP addressed to an unknown task (when a task spawned).
	(darwin_decode_notify_message): New function.
	(darwin_decode_message): Handle unknown task.
	(darwin_deallocate_threads): New function from darwin_mourn_inferior.
	(darwin_mourn_inferior): Use darwin_deallocate_threads and
	darwin_deallocate_exception_ports.
	(darwin_deallocate_exception_ports): New function from
	darwin_mourn_inferior.
	(darwin_setup_exceptions): New function from darwin_attach_pid.
	(darwin_setup_request_notification): Likewise.
	(darwin_attach_pid): Call darwin_setup_request_notification and
	darwin_setup_request_notification.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tui-winsource: Allocate for actual lines only
@ 2016-11-10  3:59 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  3:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bc2c8b83ea82b4315c67e7658af815aed062e73 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 7bc2c8b83ea82b4315c67e7658af815aed062e73

tui-winsource: Allocate for actual lines only

The logic for allocating a TUI source window's content buffer allocates
two more lines than needed, because it does not reduce the window height
by the highlight box's overhead.  However, it does reduce the line width
accordingly.  This patch makes the height and width calculation
consistent and improves the comment.

gdb/ChangeLog:

	* tui/tui-winsource.c (tui_alloc_source_buffer): Subtract
	highlight box's overhead when calculating the content height.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tui-disasm: Fix line buffer size calculation
@ 2016-11-10  4:19 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5396833d35a257902409493a63f777dcd771868 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: f5396833d35a257902409493a63f777dcd771868

tui-disasm: Fix line buffer size calculation

The code that fills the TUI disassembly window content first calculates
the maximum full length of a displayed disassembly line.  This
calculation typically yields the wrong result.  The result is too large,
so the bug does not cause any run-time failures, but unnecessary
confusion for the reader.  This patch fixes the calculation.

gdb/ChangeLog:

	* tui/tui-disasm.c (tui_set_disassem_content): Fix calculation of
	the longest disassembly line's length.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: Use vector::emplace_back
@ 2016-11-10  5:47 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  5:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a63494a0df60cf71b9cf03c4eb8f24719d03e66 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 7a63494a0df60cf71b9cf03c4eb8f24719d03e66

gdb: Use vector::emplace_back

Now that we require C++11, we can use vector::emplace_back to
construct elements in place instead of constructing and then copying.

gdb/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* main.c (struct cmdarg): Add constructor.
	(captured_main_1): Use vector::emplace_back.
	* tracepoint.c (collection_list::add_memrange): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tui-winsource: Remove failed-allocation logic
@ 2016-11-10  6:36 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  6:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c84bffb45ac63b98fffc5c1a492c2eb7e4f27e2 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 8c84bffb45ac63b98fffc5c1a492c2eb7e4f27e2

tui-winsource: Remove failed-allocation logic

This removes dead code in tui_alloc_source_buffer for handling a NULL
return value from xmalloc.

gdb/ChangeLog:

	* tui/tui-winsource.c (tui_alloc_source_buffer): Remove
	failed-xmalloc handling.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c73cd95f96d37dbf6092a87c8ba0f35277223a5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 6c73cd95f96d37dbf6092a87c8ba0f35277223a5

agent_expr_up: gdb::unique_ptr -> std::unique_ptr

Now that we require C++11, use std::unique_ptr directly.  This allows
simplifying collection_list a bit by placing unique pointers in the
vector directly, making the vector own its elements.

gdb/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* ax-gdb.c (agent_eval_command_one): Use std::move instead of
	gdb::move.
	* ax.h (agent_expr_up): Use std::unique_ptr instead of
	gdb::unique_ptr.
	* breakpoint.c (parse_cond_to_aexpr): Use std::move instead of
	gdb::move.
	* tracepoint.c (collection_list::collect_symbol): Likewise.
	(collection_list::~collection_list): Delete.
	(encode_actions_1): Use std::move instead of gdb::move.
	(collection_list::add_aexpr): Use std::move instead of
	unique_ptr::release.
	* tracepoint.h (collection_list) <~collection_list>: Delete
	declaration.
	<m_aexprs>: Now a vector of agent_ptr_up.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/testsuite: Introduce "proc_with_prefix"
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64f367a201565d5c7d1e03da072db51123ac2174 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 64f367a201565d5c7d1e03da072db51123ac2174

gdb/testsuite: Introduce "proc_with_prefix"

While adding new tests to gdb.base/commands.exp, I noticed that the
file includes a bunch of individual testcases split into their own
procedures, and that none have ever been adjusted to use
with_test_prefix.  Instead, each gdb_test/gdb_test_multiple/etc
invocation takes care of including the procedure name in the test
message, in order to make sure test messages are unique.

Simon convinced me that using the procedure name as prefix is not that
bad of an idea:
  https://sourceware.org/ml/gdb-patches/2016-10/msg00020.html

This commit adds an IMO simpler alternative to
with_test_prefix_procname added by that patch -- a new
"proc_with_prefix" convenience proc that is meant to be used in place
of "proc", and then uses it in commands.exp.  Procedures defined with
this automatically run their bodies under with_test_prefix $proc_name.

Here's a sample of the resulting gdb.sum diff:

 [...]
 -PASS: gdb.base/commands.exp: break factorial #3
 -PASS: gdb.base/commands.exp: set value to 5 in test_command_prompt_position
 -PASS: gdb.base/commands.exp: if test in test_command_prompt_position
 -PASS: gdb.base/commands.exp: > OK in test_command_prompt_position
 +PASS: gdb.base/commands.exp: test_command_prompt_position: break factorial
 +PASS: gdb.base/commands.exp: test_command_prompt_position: set value to 5
 +PASS: gdb.base/commands.exp: test_command_prompt_position: if test
 +PASS: gdb.base/commands.exp: test_command_prompt_position: > OK
 [...]

gdb/testsuite/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* gdb.base/commands.exp (gdbvar_simple_if_test)
	(gdbvar_simple_while_test, gdbvar_complex_if_while_test)
	(progvar_simple_if_test, progvar_simple_while_test)
	(progvar_complex_if_while_test, if_while_breakpoint_command_test)
	(infrun_breakpoint_command_test, breakpoint_command_test)
	(user_defined_command_test, watchpoint_command_test)
	(test_command_prompt_position, deprecated_command_test)
	(bp_deleted_in_command, temporary_breakpoint_commands)
	(stray_arg0_test, source_file_with_indented_comment)
	(recursive_source_test, if_commands_test)
	(error_clears_commands_left, redefine_hook_test)
	(redefine_backtrace_test): Use proc_with_prefix.
	* lib/gdb.exp (proc_with_prefix): New proc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix
@ 2016-11-10  7:46 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8354c62cd144964fce17e11ce035c0c2c0635cbf ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 8354c62cd144964fce17e11ce035c0c2c0635cbf

Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix

Pedro's patch provides a cleaner way to prefix tests with the proc name,
so let's use that.

gdb/testsuite/ChangeLog:

	* gdb.mi/user-selected-context-sync.exp (with_test_prefix_procname):
	Remove.
	(test_setup): Define with proc_with_prefix.
	(test_cli_inferior): Likewise.
	(test_cli_thread): Likewise.
	(test_cli_frame): Likewise.
	(test_cli_select_frame): Likewise.
	(test_cli_up_down): Likewise.
	(test_mi_thread_select): Likewise.
	(test_mi_stack_select_frame): Likewise.
	(test_cli_in_mi_inferior): Likewise.
	(test_cli_in_mi_thread): Likewise.
	(test_cli_in_mi_frame): Likewise.
	(top level): Do not use with_test_prefix_procname.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] X86: Remove the .s suffix from EVEX vpextrw
@ 2016-11-10  7:47 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60227d64dd9228be1a07fc7122894fc2875b1a70 ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 60227d64dd9228be1a07fc7122894fc2875b1a70

X86: Remove the .s suffix from EVEX vpextrw

The .s suffix indicates that the instruction is encoded by swapping
2 register operands.  Since vpextrw takes an XMM register and an
integer register, the .s suffix should be ignored for EVEX vpextrw.

gas/

	PR binutils/20799
	* testsuite/gas/i386/opcode.s: Add a test for EVEX vpextrw.
	* testsuite/gas/i386/opcode-intel.d: Updated.
	* testsuite/gas/i386/opcode-suffix.d: Likewise.
	* testsuite/gas/i386/opcode.d: Likewise.
	* testsuite/gas/i386/x86-64-avx512bw-opts.s: Remove vpextrw
	tests.
	* testsuite/gas/i386/x86-64-avx512bw-opts-intel.d: Updated.
	* testsuite/gas/i386/x86-64-avx512bw-opts.d: Likewise.

opcodes/

	PR binutils/20799
	* i386-dis-evex.h (evex_table): Replace EdqwS with Edqw.
	* i386-dis.c (EdqwS): Removed.
	(dqw_swap_mode): Likewise.
	(intel_operand_size): Don't check dqw_swap_mode.
	(OP_E_register): Likewise.
	(OP_E_memory): Likewise.
	(OP_G): Likewise.
	(OP_EX): Likewise.
	* i386-opc.tbl: Remove "S" from EVEX vpextrw.
	* i386-tbl.h: Regerated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] X86: Merge AVX512F vmovq
@ 2016-11-10  7:47 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7efeed176a291c15c74e80aee5d7f906e28081cf ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: 7efeed176a291c15c74e80aee5d7f906e28081cf

X86: Merge AVX512F vmovq

AVX512F vmovq doesn't support masking.  We can't swap register operand
in AVX512F vmovq with Reg64 since Reg64 != RegXMM.  This patch merges
AVX512F vmovq.

	* i386-opc.tbl: Merge AVX512F vmovq.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Further cleanup/modernization of gdb.base/commands.exp
@ 2016-11-10  7:48 sergiodj+buildbot
  2016-11-10 10:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fad0c9fb7dd362bdb5a3e4f89fb7f6e6789f5beb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: fad0c9fb7dd362bdb5a3e4f89fb7f6e6789f5beb

Further cleanup/modernization of gdb.base/commands.exp

 - Use multi_line for matching multi-line GDB output.

 - Add a multi_line_input variant of multi_line to build GDB input and
   use it throughout.

   (The two changes above make the tests much more readable, IMO.)

 - Add a new valnum_re global to get rid of the multiple "\\\$\[0-9\]*".

 - Remove gdb_stop_suppressing_tests uses.

 - tighten a few regexps.

 - Replace send_gdb/gdb_expect with gdb_test_multiple and simplify,
   making pass/fail messages the same.

gdb/ChangeLog:
2016-11-09  Pedro Alves  <palves@redhat.com>

	* gdb.base/commands.exp (runto_or_return): New procedure.
	(gdbvar_simple_if_test, gdbvar_simple_while_test)
	(gdbvar_complex_if_while_test, progvar_simple_if_test)
	(progvar_simple_while_test, progvar_complex_if_while_test)
	(if_while_breakpoint_command_test)
	(infrun_breakpoint_command_test, breakpoint_command_test)
	(user_defined_command_test, watchpoint_command_test)
	(test_command_prompt_position, redefine_hook_test)
	(stray_arg0_test, error_clears_commands_left, redefine_hook_test)
	(redefine_backtrace_test): Use runto_or_return, $valnum_re,
	multi_line_input and multi_line.  Remove gdb_expect and
	gdb_stop_suppressing_tests uses.
	* lib/gdb.exp (valnum_re): New global.
	* lib/gdb.exp (valnum_re): New global.
	(multi_line_input): New procedure.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use unique_xmalloc_ptr in Python code
@ 2016-11-10  7:49 sergiodj+buildbot
  2016-11-10 10:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b9720149dfee4a9a961c29d0382fc5bdf9c975b ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9b9720149dfee4a9a961c29d0382fc5bdf9c975b

Use unique_xmalloc_ptr in Python code

This changes some utility functions in the Python code to return
unique_xmalloc_ptr, and then fixes up the callers.

I chose unique_xmalloc_ptr rather than std::string because at a few
call points the xmalloc'd string is released and ownership transferred
elsewhere.

This patch found a few existing memory leaks.  For example,
py-unwind.c called gdbpy_obj_to_string but never freed the result.

Built and regression tested on the buildbot.

2016-11-09  Tom Tromey  <tom@tromey.com>

	* varobj.h (varobj_get_display_hint): Change return type.
	* varobj.c (varobj_get_display_hint): Return unique_xmalloc_ptr.
	(varobj_value_get_print_value): Update.
	* python/python.c (gdbpy_before_prompt_hook, gdbpy_print_stack)
	(gdbpy_apply_type_printers): Update.
	* python/python-internal.h (unicode_to_target_string)
	(python_string_to_target_string, python_string_to_host_string)
	(gdbpy_obj_to_string, gdbpy_exception_to_string)
	(gdbpy_get_display_hint): Change return types.
	* python/py-varobj.c (py_varobj_iter_next): Update.
	* python/py-value.c (valpy_getitem, convert_value_from_python):
	Update.
	* python/py-utils.c (unicode_to_encoded_string)
	(unicode_to_target_string, python_string_to_target_string)
	(python_string_to_host_string, gdbpy_obj_to_string)
	(gdbpy_exception_to_string): Return unique_xmalloc_ptr.
	* python/py-unwind.c (pyuw_parse_register_id): Update.
	* python/py-type.c (typy_getitem): Update.
	* python/py-prettyprint.c (gdbpy_get_display_hint)
	(print_stack_unless_memory_error, print_children)
	(gdbpy_apply_val_pretty_printer): Update.
	* python/py-param.c (set_parameter_value): Update.
	(get_doc_string, call_doc_function): Return unique_xmalloc_ptr.
	(get_set_value, get_show_value, compute_enum_values, parmpy_init):
	Update.
	* python/py-infthread.c (thpy_set_name): Update.
	* python/py-function.c (fnpy_call, fnpy_init): Update.
	* python/py-framefilter.c (extract_sym): Change "name" to
	unique_xmalloc_ptr.
	(enumerate_args, enumerate_locals): Update.
	(py_print_frame): Use unique_xmalloc_ptr.
	* python/py-frame.c (frapy_read_var): Update.  Remove cleanup.
	* python/py-cmd.c (cmdpy_function, cmdpy_completer, cmdpy_init):
	Update.
	* python/py-breakpoint.c (bppy_set_condition): Use
	unique_xmalloc_ptr.
	(bppy_init): Likewise.  Remove cleanup.
	(local_setattro): Update.
	* mi/mi-cmd-var.c (print_varobj, mi_cmd_var_list_children)
	(varobj_update_one): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] tui-disasm: Fix window content buffer overrun
@ 2016-11-10  8:07 sergiodj+buildbot
  2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  8:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bb65f1e7c9eed7338ef2e4a2f5b42d010409c39 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 0bb65f1e7c9eed7338ef2e4a2f5b42d010409c39

tui-disasm: Fix window content buffer overrun

A user reported a GDB crash with TUI when trying to debug a function
with a long demangled C++ method name.  It turned out that the logic for
displaying the TUI disassembly window has a bug that can cause a buffer
overrun, possibly overwriting GDB-internal data structures.  In
particular, the logic performs an unguarded strcpy.

Another (harmless) bug in tui_alloc_source_buffer causes the buffer to
be two lines longer than needed.  This may have made the crash appear
less frequently.

gdb/ChangeLog:

	* tui/tui-disasm.c (tui_set_disassem_content): Fix line buffer
	overrun due to unchecked strcpy.

gdb/testsuite/ChangeLog:

	* gdb.base/tui-layout.c: New file.
	* gdb.base/tui-layout.exp: Use tui-layout.c, to ensure that the
	disassembly window contains very long lines.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Bind defined symbol locally in PIE
@ 2016-11-10  9:30 sergiodj+buildbot
  2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10  9:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac33b731d214d79738ca04d27f7464d4482f6a01 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: ac33b731d214d79738ca04d27f7464d4482f6a01

[AArch64] Bind defined symbol locally in PIE

bfd/
	PR target/20737
	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Bind defined
	symbol locally in PIE.

ld/
	* testsuite/ld-aarch64/pie-bind-locally-a.s: New test source.
	* testsuite/ld-aarch64/pie-bind-locally-b.s: Likewise.
	* testsuite/ld-aarch64/pie-bind-locally.d: New testcase.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Provide a more helpful error message when the BFD library is unable to load an extremely large section.
@ 2016-11-10 12:31 sergiodj+buildbot
  2016-11-10 12:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-10 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a18590c38657a982f8d544f2f54f39ba9abe9fca ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: a18590c38657a982f8d544f2f54f39ba9abe9fca

Provide a more helpful error message when the BFD library is unable to load an extremely large section.

	PR target/20737
	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Bind defined
	symbol locally in PIE.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] sim: mips: fix dv-tx3904cpu build error
@ 2016-11-11 10:09 sergiodj+buildbot
  2016-11-11 11:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91588b3af8e026ba11c7368476cc1f3fa8c2e2b1 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 91588b3af8e026ba11c7368476cc1f3fa8c2e2b1

sim: mips: fix dv-tx3904cpu build error

When building for mipstx39-rtems4.12 targets, some funcs use SD and CPU
implicitly.  Restore the defines for these to the local sd and cpu vars.

This was broken by the clean up in commit d47f5b30d8481272e9480118bdcb.

Reported-by: Joel Sherrill <joel.sherrill@oarcorp.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove parameter valaddr from c print functions
@ 2016-11-11 10:40 sergiodj+buildbot
  2016-11-11 12:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65408fa680538f997cdd4b6fb9d74f043a060801 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 65408fa680538f997cdd4b6fb9d74f043a060801

Remove parameter valaddr from c print functions

This patch removes parameter valaddr from some c print functions.

gdb:

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

	* c-lang.h (cp_print_value_fields): Update declaration.
	* cp-valprint.c (cp_print_value): Update declaration.
	(cp_print_value_fields): Remove parameter valaddr.  Callers
	updated.
	(cp_print_value): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr
@ 2016-11-11 12:02 sergiodj+buildbot
  2016-11-11 13:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 12:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 668e167446b2777869f413841ec05aed59473d9f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 668e167446b2777869f413841ec05aed59473d9f

Remove apply_val_pretty_printer parameter valaddr

This patch removes the parameter valaddr of
extension_language_ops::apply_val_pretty_printer and remove const from
"struct value *val".  valaddr can be got in each extension language's
implementation of apply_val_pretty_printer.

gdb:

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

	* cp-valprint.c (cp_print_value): Remove local base_valaddr.
	* extension-priv.h (struct extension_language_ops)
	<apply_val_pretty_printer>: Remove the second parameter.
	Remove const from "struct value *".  Callers updated.
	* extension.c (apply_ext_lang_val_pretty_printer): Update
	comments.  Remove parameter valaddr.  Remove const from
	"struct value *".
	* extension.h (apply_ext_lang_val_pretty_printer): Update
	declaration.
	* guile/guile-internal.h (gdbscm_apply_val_pretty_printer):
	Update declaration.
	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
	Remove parameter valaddr.  Remove const from "struct value *".
	* python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
	Likewise.
	* python/python-internal.h (gdbpy_apply_val_pretty_printer):
	Update declaration.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Accept hidden COFF symbols, but treat them as if they were debugging symbols.
@ 2016-11-11 12:40 sergiodj+buildbot
  2016-11-11 15:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 12:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7103ad7639b7ed80bec170404185a8e39079446b ***

Author: Luke Allardyce <lukeallardyce@gmail.com>
Branch: master
Commit: 7103ad7639b7ed80bec170404185a8e39079446b

Accept hidden COFF symbols, but treat them as if they were debugging symbols.

	PR ld/20722
	* coffcode.h (coff_slurp_symbol_table): Accept C_HIDDEN symbols,
	but treat them as debugging symbols.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Increase max_num_aliases in aarch64-gen
@ 2016-11-11 14:42 sergiodj+buildbot
  2016-11-11 17:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d731f6949e2b0099cfbe0cf608d60a52a66d354 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 3d731f6949e2b0099cfbe0cf608d60a52a66d354

[AArch64] Increase max_num_aliases in aarch64-gen

Some ARMv8.3 pointer authentication instructions are encoded as HINT aliases,
so to allow more instruction aliases in the generator, max_num_aliases is
increased from 16 to 32.

opcodes/
2016-11-11  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-gen.c (find_alias_opcode): Increase max_num_aliases to 32.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't handle unavailable/optimized-out in spu_software_single_step
@ 2016-11-11 21:18 sergiodj+buildbot
  2016-11-12  2:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 21:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d15592e06e4abccc97cb8c5670f564327f747e9 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7d15592e06e4abccc97cb8c5670f564327f747e9

Don't handle unavailable/optimized-out in spu_software_single_step

When we do software single step, frame is always the innermost one,
so it is impossible to get unavailable/optimized-out errors.

gdb:

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

	* spu-tdep.c (spu_software_single_step): Don't call
	get_frame_register_bytes, call get_frame_register_unsigned
	instead.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string in rust_get_disr_info
@ 2016-11-12 19:05 sergiodj+buildbot
  2016-11-12 19:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-12 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d93f4d96bb0fb307db9e2dade38ddb3c6bc469ca ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d93f4d96bb0fb307db9e2dade38ddb3c6bc469ca

Use std::string in rust_get_disr_info

This changes rust_get_disr_info to use std::string in one more spot,
avoiding a memory leak.

2016-11-12  Tom Tromey  <tom@tromey.com>

	* rust-lang.c (rust_get_disr_info): Use std::string in one more
	spot.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition
@ 2016-11-15 20:24 sergiodj+buildbot
  2016-11-15 21:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-15 20:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7f38fdae7c75e1d13abd455b3931950db28d22b ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: b7f38fdae7c75e1d13abd455b3931950db28d22b

bitfield-parent-optimized-out: Fix struct definition

The "struct S" type in bitfield-parent-optimized-out.exp is declared to
have a size of 4 bytes but to hold two 4-byte members: an int-based
bitfield and a 4-byte int.  Also, both members have the same
data_member_location 2, causing them to overlap and to reach 2 bytes
beyond the structure's boundary.

This is fixed by increasing the structure size to 8 and setting the
first and second member's data_member_location to 0 and 4, respectively.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/bitfield-parent-optimized-out.exp: Fix DWARF code for
	the definition of struct S.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb::{unique_ptr,move} -> std::{unique_ptr,move}
@ 2016-11-15 20:54 sergiodj+buildbot
  2016-11-15 23:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-15 20:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b22e99fdaf2efe58161c382bbd55f4572ba49eef ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: b22e99fdaf2efe58161c382bbd55f4572ba49eef

gdb::{unique_ptr,move} -> std::{unique_ptr,move}

Now that we require C++11, use std::unique_ptr and std::move directly.

gdb/ChangeLog:
2016-11-15  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (create_excep_cond_exprs): Use std::move instead of
	gdb::move.
	* break-catch-throw.c (handle_gnu_v3_exceptions): Use
	std::unique_ptr instead of gdb::unique_ptr.
	* breakpoint.c (watch_command_1): Use std::move instead of
	gdb::move.
	* cli/cli-dump.c (dump_memory_to_file, restore_binary_file): Use
	std::unique_ptr instead of gdb::unique_ptr.
	* dtrace-probe.c (dtrace_process_dof_probe): Use std::move instead
	of gdb::move.
	* elfread.c (elf_read_minimal_symbols): Use std::unique_ptr
	instead of gdb::unique_ptr.
	* mi/mi-main.c (mi_cmd_data_read_memory): Use std::unique_ptr
	instead of gdb::unique_ptr.
	* parse.c (parse_expression_for_completion): Use std::move instead
	of gdb::move.
	* printcmd.c (display_command): std::move instead of gdb::move.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb: update gnulib to pull in C++ namespace support fixes
@ 2016-11-16  0:24 sergiodj+buildbot
  2016-11-16  2:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-16  0:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c62b19fd2e6b81ce7cbb7d01e84c09352ccf224 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 4c62b19fd2e6b81ce7cbb7d01e84c09352ccf224

gdb: update gnulib to pull in C++ namespace support fixes

I've been experimenting with making use of gnulib's C++ namespace support:

 https://www.gnu.org/software/gnulib/manual/html_node/A-C_002b_002b-namespace-for-gnulib.html

That stumbled on a few gnulib issues, which I've fixed upstream:

 [PATCH] Fix gnulib C++ namespace support and std::frexp
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00039.html

 [PATCH] Fix real-floating argument functions in C++ mode
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00049.html

 [PATCH] Avoid having GNULIB_NAMESPACE::func always inject references to rpl_func
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00040.html

 [PATCH] C++: "#define timeval rpl_timeval" -> typedef in GNULIB_NAMESPACE
 https://lists.gnu.org/archive/html/bug-gnulib/2016-11/msg00058.html

This merge pulls those in.

gdb/ChangeLog:
2016-11-15  Pedro Alves  <palves@redhat.com>

	* gnulib/update-gnulib.sh (GNULIB_COMMIT_SHA1): Set to
	38237baf99386101934cd93278023aa4ae523ec0.
	* gnulib/configure, gnulib/config.in: Regenerate.
	* gnulib/import/Makefile.am: Regenerate.
	* gnulib/import/Makefile.in: Regenerate.
	* gnulib/import/canonicalize-lgpl.c: Update.
	* gnulib/import/extra/snippet/c++defs.h: Update.
	* gnulib/import/m4/stdint.m4: Update.
	* gnulib/import/m4/stdlib_h.m4: Update.
	* gnulib/import/math.in.h: Update.
	* gnulib/import/stdlib.in.h: Update.
	* gnulib/import/sys_time.in.h: Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs
@ 2016-11-16 20:01 sergiodj+buildbot
  2016-11-16 20:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4cb771f214ed6a2102e37bce255c6be5d0642f3a ***

Author: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com>
Branch: master
Commit: 4cb771f214ed6a2102e37bce255c6be5d0642f3a

Fix PR20789 - relaxation with negative valued diff relocs

Fix issues with diff relocs that have a negative value
i.e. sym2 - sym1 where sym2 is lesser than sym1.

The assembler generates a diff reloc with symbol as start of section
and addend as sym2 offset, and encodes assembly time difference at
the reloc offset.

The existing relaxation logic adjusts addends if the relaxed insn lies
between symbol and addend. That doesn't work for diff relocs where
sym2 is less than sym1 *and* the relaxed insn happens to be between
sym2 and sym1.

Fix the problems by

1. Using signed handling of the difference value (bfd_signed_vma instead
of bfd_vma, bfd_{get,set}_signed_xxx instead of bfd_{get,set}_xxx).

2. Not assuming sym2 is bigger than sym1. It instead computes the actual
addresses and sets the lower and higher addresses as start and end
addresses respectively and then sees if insn is between start and end.

3. Creating a new function elf32_avr_adjust_reloc_if_spans_insn to
centralize reloc adjustment, and ensuring diff relocs get adjusted
correctly even if their sym + addend doesn't overlap a relaxed insn.

It also removes a redundant variable did_pad. It is never set if
did_shrink is TRUE, and the code does a early return if did_shrink is
FALSE.

bfd/ChangeLog

2016-11-15  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

       PR ld/20789
       * bfd/elf32-avr.c (elf32_avr_adjust_diff_reloc_value): Do signed
       manipulation of diff value, and don't assume sym2 is less than sym1.
       (elf32_avr_adjust_reloc_if_spans_insn): New function.
       (elf32_avr_relax_delete_bytes): Use elf32_avr_adjust_diff_reloc_value,
       and remove redundant did_pad.

ld/ChangeLog

2016-11-15  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

       PR ld/20789
       * ld/testsuite/ld-avr/pr20789.d: New test.
       * ld/testsuite/ld-avr/pr20789.s: New test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp
@ 2016-11-16 20:03 sergiodj+buildbot
  2016-11-16 21:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a2f3d7ff1d79b1290704e48c71e905b987393a6 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 1a2f3d7ff1d79b1290704e48c71e905b987393a6

Extend test gdb.python/py-recurse-unwind.exp

This patch modifies the unwinder (sniffer) defined in
py-recurse-unwind.py so that, depending upon the value of one of its
class variables, it will take different paths through the code,
testing different functionality.

The original test attempted to obtain the value of an undefined
symbol.

This somewhat expanded test checks to see if 'pc' can be read via
gdb.PendingFrame.read_register() and also via gdb.parse_and_eval().

gdb/testsuite/ChangeLog:

	* gdb.python/py-recurse-unwind.c (main): Add loop.
	* gdb.python/py-recurse-unwind.py (TestUnwinder): Add calls
	to read_register() and gdb.parse_and_eval().  Make each code
	call a separate case that can be individually tested.
	* gdb.python/py-recurse-unwind.exp (cont_and_backtrace): New
	proc. Call cont_and_backtrace for each of the code paths that
	we want to test in the unwinder.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Stash frame id of current frame before stashing frame id for previous frame
@ 2016-11-17  0:20 sergiodj+buildbot
  2016-11-17  8:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-17  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 256ae5dbc73d1348850f86ee77a0dc3b04bc7cc0 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 256ae5dbc73d1348850f86ee77a0dc3b04bc7cc0

Stash frame id of current frame before stashing frame id for previous frame

This patch ensures that the frame id for the current frame is stashed
before that of the previous frame (to the current frame).

First, it should be noted that the frame id for the current frame is
not stashed by get_current_frame().  The current frame's frame id is
lazily computed and stashed via calls to get_frame_id().  However,
it's possible for get_prev_frame() to be called without first stashing
the current frame.

The frame stash is used not only to speed up frame lookups, but
also to detect cycles.  When attempting to compute the frame id
for a "previous" frame (in get_prev_frame_if_no_cycle), a cycle
is detected if the computed frame id is already in the stash.

If it should happen that a previous frame id is stashed which should
represent a cycle for the current frame, then an assertion failure
will trigger should get_frame_id() be later called to determine
the frame id for the current frame.

As of late 2016, with the "Tweak meaning of VALUE_FRAME_ID" patch in
place, this actually occurs when running the
gdb.dwarf2/dw2-dup-frame.exp test.  While attempting to generate a
backtrace, the python frame filter code is invoked, leading to
frame_info_to_frame_object() (in python/py-frame.c) being called.
That function will potentially call get_prev_frame() before
get_frame_id() is called.  The call to get_prev_frame() can eventually
end up in get_prev_frame_if_no_cycle() which, in turn, calls
compute_frame_id(), after which the frame id is stashed for the
previous frame.

If the frame id for the current frame is stashed, the cycle detection
code (which relies on the frame stash) in get_prev_frame_if_no_cycle()
will be triggered for a cycle starting with the current frame.  If the
current frame's id is not stashed, the cycle detecting code can't
operate as designed.  Instead, when get_frame_id() is called on the
current frame at some later point, the current frame's id will found
to be already in the stash, triggering an assertion failure.

Below is an in depth examination of the failure which lead to this change.
I've shortened pathnames for brevity and readability.

Here's the portion of the log file showing the failure/internal error:

(gdb) break stop_frame
Breakpoint 1 at 0x40059a: file dw2-dup-frame.c, line 22.
(gdb) run
Starting program: testsuite/outputs/gdb.dwarf2/dw2-dup-frame/dw2-dup-frame

Breakpoint 1, stop_frame () at dw2-dup-frame.c:22
22	}
(gdb) bt
gdb/frame.c:544: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
FAIL: gdb.dwarf2/dw2-dup-frame.exp: backtrace from stop_frame (GDB internal error)

Here's a partial backtrace from the internal error, showing the frames
which I think are relevant, plus several extra to provide context:

    #0  internal_error (
	file=0x932b98 "gdb/frame.c", line=544,
	fmt=0x932b20 "%s: Assertion `%s' failed.")
	at gdb/common/errors.c:54
    #1  0x000000000072207e in get_frame_id (fi=0xe5a760)
	at gdb/frame.c:544
    #2  0x00000000004eb50d in frame_info_to_frame_object (frame=0xe5a760)
	at gdb/python/py-frame.c:390
    #3  0x00000000004ef5be in bootstrap_python_frame_filters (frame=0xe5a760,
	frame_low=0, frame_high=-1)
	at gdb/python/py-framefilter.c:1453
    #4  0x00000000004ef7a9 in gdbpy_apply_frame_filter (
	extlang=0x8857e0 <extension_language_python>, frame=0xe5a760, flags=7,
	args_type=CLI_SCALAR_VALUES, out=0xf6def0, frame_low=0, frame_high=-1)
	at gdb/python/py-framefilter.c:1548
    #5  0x00000000005f2c5a in apply_ext_lang_frame_filter (frame=0xe5a760,
	flags=7, args_type=CLI_SCALAR_VALUES, out=0xf6def0, frame_low=0,
	frame_high=-1)
	at gdb/extension.c:572
    #6  0x00000000005ea896 in backtrace_command_1 (count_exp=0x0, show_locals=0,
	no_filters=0, from_tty=1)
	at gdb/stack.c:1834

Examination of the code in frame_info_to_frame_object(), which is in
python/py-frame.c, is key to understanding this problem:

      if (get_prev_frame (frame) == NULL
	  && get_frame_unwind_stop_reason (frame) != UNWIND_NO_REASON
	  && get_next_frame (frame) != NULL)
	{
	  frame_obj->frame_id = get_frame_id (get_next_frame (frame));
	  frame_obj->frame_id_is_next = 1;
	}
      else
	{
	  frame_obj->frame_id = get_frame_id (frame);
	  frame_obj->frame_id_is_next = 0;
	}

I will first note that the frame id for frame has not been computed yet.  (This
was verified by placing a breakpoint on compute_frame_id().)

The call to get_prev_frame() causes the the frame id to (eventually) be
computed for the previous frame.  Here's a backtrace showing how we
get there:

    #0  compute_frame_id (fi=0x10e2810)
	at gdb/frame.c:496
    #1  0x0000000000724a67 in get_prev_frame_if_no_cycle (this_frame=0xe5a760)
	at gdb/frame.c:1871
    #2  0x0000000000725136 in get_prev_frame_always_1 (this_frame=0xe5a760)
	at gdb/frame.c:2045
    #3  0x000000000072516b in get_prev_frame_always (this_frame=0xe5a760)
	at gdb/frame.c:2061
    #4  0x000000000072570f in get_prev_frame (this_frame=0xe5a760)
	at gdb/frame.c:2303
    #5  0x00000000004eb471 in frame_info_to_frame_object (frame=0xe5a760)
	at gdb/python/py-frame.c:381

For this particular case, we end up in the else clause of the code above
which calls get_frame_id (frame).  It's at this point that the frame id
for frame is computed.  Again, here's a backtrace:

    #0  compute_frame_id (fi=0xe5a760)
	at gdb/frame.c:496
    #1  0x000000000072203d in get_frame_id (fi=0xe5a760)
	at gdb/frame.c:539
    #2  0x00000000004eb50d in frame_info_to_frame_object (frame=0xe5a760)
	at gdb/python/py-frame.c:390

The test in question, dw2-dup-frame.exp, deliberately creates a broken
(cyclic) stack.  So, in this instance, the frame id for the prev
`frame' will be the same as that for `frame'.  But that particular
frame id ended up in the stash during the previous frame operation.
When, just a few lines later, we compute the frame id for `frame', the
id in question is already in the stash, thus triggering the assertion
failure.

I considered two other solutions to solving this problem:

We could prevent get_prev_frame() from being called before
get_frame_id() in frame_info_to_frame_object().  (See above for the
snippet of code where this happens.) A call to get_frame_id (frame)
could be placed ahead of that code snippet above.  I have tested this
approach and, while it does work, I can't be certain that
get_prev_frame() isn't called ahead of stashing the current frame
somewhere else in GDB, but in a less obvious way.

Another approach is to stash the current frame's id by calling
get_frame_id() in get_current_frame().  This approach is conceptually
simpler, but when importing a python unwinder, has the unwelcome side
effect of causing the unwinder to be called during import.

A cleaner looking fix would be to place this code after code
corresponding to the "Don't compute the frame id of the current frame
yet..." comment in get_prev_frame_if_no_cycle().  Sadly, this does not
work though; by the time we get to this point, the frame state for the
prev frame has been modified just enough to cause an internal error to
occur when attempting to compute the (current) frame id for inline
frames.  (The unexpected failure count increases by roughly 130
failures.)  Therefore, I decided to place it as early as possible
in get_prev_frame().

gdb/ChangeLog:

	* frame.c (get_prev_frame): Stash frame id for current frame
	prior to computing frame id for previous frame.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdb/tracepoint.c: Don't use printf_vma
@ 2016-11-17  1:28 sergiodj+buildbot
  2016-11-17 12:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-17  1:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 19f1935d91bfabbe4176ffdaca95bc789b593153 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 19f1935d91bfabbe4176ffdaca95bc789b593153

gdb/tracepoint.c: Don't use printf_vma

I noticed that bfd's printf_vma prints to stdout directly:

  bfd-in2.h:202:#define printf_vma(x) fprintf_vma(stdout,x)

This is a bad idea in gdb, where we should use
gdb_stdout/gdb_stderr/gdb_stdlog, etc., to support redirection.

Eliminate uses of sprintf_vma too while at it.

Tested on Fedora 23, w/ gdbserver.

gdb/ChangeLog:
2016-11-17  Pedro Alves  <palves@redhat.com>

	* tracepoint.c (collection_list::add_memrange): Add gdbarch
	parameter.  Use paddress instead of printf_vma.  Adjust recursive
	calls.
	(collection_list::stringify): Use paddress and phex_nz instead of
	sprintf_vma.  Adjust add_memrange call.
	* tracepoint.h (collection_list::add_memrange): Add gdbarch
	parameter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Document new hard requirement on GNU make
@ 2016-11-17 18:31 sergiodj+buildbot
  2016-11-17 19:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2ff9acd32b4667ee16a03ca8d10fd8b99e22f46 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: f2ff9acd32b4667ee16a03ca8d10fd8b99e22f46

Document new hard requirement on GNU make

As discussed in [1], it would be benificial for the GDB project to start
requiring GNU make to build its software.  It would allow using useful
GNU-specific constructs, such as pattern rules.  It would also allow
removing the alternative code paths in the Makefiles (guarded by
GMAKE_TRUE/GMAKE_FALSE), simplifying the Makefile code.

[1] https://sourceware.org/ml/gdb-patches/2016-11/msg00331.html

gdb/ChangeLog:

	* NEWS: Mention requirement of GNU make.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Help diagnose problems with the metag target when mixing static and shared binaries.
@ 2016-11-18  9:59 sergiodj+buildbot
  2016-11-18 10:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-18  9:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ec49e7c0aeb6d98e379319b565aee2c89388615 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 6ec49e7c0aeb6d98e379319b565aee2c89388615

Help diagnose problems with the metag target when mixing static and shared binaries.

	PR ld/20675
	* elf32-metag.c (elf_metag_relocate_section): Replace abort with
	an informative error message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 FCMLA and FCADD instructions
@ 2016-11-18 13:05 sergiodj+buildbot
  2016-11-18 15:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2c4ff8d52a2cd3263a547b0384692498714aa1b ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: c2c4ff8d52a2cd3263a547b0384692498714aa1b

[AArch64] Add ARMv8.3 FCMLA and FCADD instructions

Add support for FCMLA and FCADD complex arithmetic SIMD instructions.
FCMLA has an indexed element variant where the index range has to be
treated specially because a complex number takes two elements and the
indexed vector size depends on the other operands.

These complex number SIMD instructions are part of ARMv8.3
https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

include/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* opcode/aarch64.h (enum aarch64_opnd): Add AARCH64_OPND_IMM_ROT1,
	AARCH64_OPND_IMM_ROT2, AARCH64_OPND_IMM_ROT3.
	(enum aarch64_op): Add OP_FCMLA_ELEM.

opcodes/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-tbl.h (QL_V3SAMEHSD_ROT, QL_ELEMENT_ROT): Define.
	(aarch64_feature_simd_v8_3, SIMD_V8_3): Define.
	(aarch64_opcode_table): Add fcmla and fcadd.
	(AARCH64_OPERANDS): Add IMM_ROT{1,2,3}.
	* aarch64-asm.h (aarch64_ins_imm_rotate): Declare.
	* aarch64-asm.c (aarch64_ins_imm_rotate): Define.
	* aarch64-dis.h (aarch64_ext_imm_rotate): Declare.
	* aarch64-dis.c (aarch64_ext_imm_rotate): Define.
	* aarch64-opc.h (enum aarch64_field_kind): Add FLD_rotate{1,2,3}.
	* aarch64-opc.c (fields): Add FLD_rotate{1,2,3}.
	(operand_general_constraint_met_p): Rotate and index range check.
	(aarch64_print_operand): Handle rotate operand.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Likewise.
	* aarch64-opc-2.c: Likewise.

gas/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* config/tc-aarch64.c (parse_operands): Handle AARCH64_OPND_IMM_ROT*.
	* testsuite/gas/aarch64/advsimd-armv8_3.d: New.
	* testsuite/gas/aarch64/advsimd-armv8_3.s: New.
	* testsuite/gas/aarch64/illegal-fcmla.s: New.
	* testsuite/gas/aarch64/illegal-fcmla.l: New.
	* testsuite/gas/aarch64/illegal-fcmla.d: New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Implement P0012R1, Make exception specifications part of the type system.
@ 2016-11-18 16:45 sergiodj+buildbot
  2016-11-18 20:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4ddf8dc72f0ac10c3459a91949eb1bdb07ed10d ***

Author: Jason Merrill <jason@redhat.com>
Branch: master
Commit: a4ddf8dc72f0ac10c3459a91949eb1bdb07ed10d

Implement P0012R1, Make exception specifications part of the type system.

libiberty/
	* cp-demangle.c (is_fnqual_component_type): New.
	(d_encoding, d_print_comp_inner, d_print_mod_list): Use it.
	(FNQUAL_COMPONENT_CASE): New.
	(d_make_comp, has_return_type, d_print_comp_inner)
	(d_print_function_type): Use it.
	(next_is_type_qual): New.
	(d_cv_qualifiers, d_print_mod): Handle noexcept and throw-spec.
include/
	* demangle.h (enum demangle_component_type): Add
	DEMANGLE_COMPONENT_NOEXCEPT, DEMANGLE_COMPONENT_THROW_SPEC.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] libiberty: Add Rust symbol demangling.
@ 2016-11-18 19:31 sergiodj+buildbot
  2016-11-19  0:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 535aade664ac4170fe82e52c9addd686156220a1 ***

Author: David Tolnay <dtolnay@gmail.com>
Branch: master
Commit: 535aade664ac4170fe82e52c9addd686156220a1

libiberty: Add Rust symbol demangling.

Adds Rust symbol demangler. Rust mangles symbols using GNU_V3 style,
adding a hash and various special character subtitutions. This adds
a new rust style to cplus_demangle and adds 3 helper functions
rust_demangle, rust_demangle_sym and rust_is_mangled.

rust-demangle.c was written by David. Mark did the code formatting to
GNU style and integration into the gcc/libiberty build system and
testsuite.

include/ChangeLog:

2016-11-03  David Tolnay <dtolnay@gmail.com>
           Mark Wielaard  <mark@klomp.org>

       * demangle.h (DMGL_RUST): New macro.
       (DMGL_STYLE_MASK): Add DMGL_RUST.
       (demangling_styles): Add dlang_rust.
       (RUST_DEMANGLING_STYLE_STRING): New macro.
       (RUST_DEMANGLING): New macro.
       (rust_demangle): New prototype.
       (rust_is_mangled): Likewise.
       (rust_demangle_sym): Likewise.

libiberty/ChangeLog:

2016-11-03  David Tolnay <dtolnay@gmail.com>
           Mark Wielaard  <mark@klomp.org>

       * Makefile.in (CFILES): Add rust-demangle.c.
       (REQUIRED_OFILES): Add rust-demangle.o.
       * cplus-dem.c (libiberty_demanglers): Add rust_demangling case.
       (cplus_demangle): Handle RUST_DEMANGLING.
       (rust_demangle): New function.
       * rust-demangle.c: New file.
       * testsuite/Makefile.in (really-check): Add check-rust-demangle.
       (check-rust-demangle): New rule.
       * testsuite/rust-demangle-expected: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd: fix negative GOT offsets for non-local references on sparc64
@ 2016-11-19  0:43 sergiodj+buildbot
  2016-11-19  4:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-19  0:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc133f9f118ef4afd93da0ecba48151488c41c74 ***

Author: James Clarke <jrtc27@jrtc27.com>
Branch: master
Commit: cc133f9f118ef4afd93da0ecba48151488c41c74

bfd: fix negative GOT offsets for non-local references on sparc64

bfd/ChangeLog:

2016-11-18  James Clarke  <jrtc27@jrtc27.com>

	* elfxx-sparc.c (_bfd_sparc_elf_relocate_section): Don't convert
	R_SPARC_GOTDATA_OP_HIX22 and R_SPARC_GOTDATA_OP_LOX10 to
	R_SPARC_GOT* for non-local references. Instead, treat them like
	R_SPARC_GOTDATA_HIX22/R_SPARC_GOTDATA_LOX10 when filling in the
	immediate with the calculated relocation.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Makefile: fix typo
@ 2016-11-19  3:34 sergiodj+buildbot
  2016-11-19  9:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-19  3:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef787763b9495913d5be90bcdedcecb553cbf308 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ef787763b9495913d5be90bcdedcecb553cbf308

Makefile: fix typo

Thanks to Patrick Monnerat for reporting this typo.

gdb/ChangeLog:

	* Makefile.in (%.o: $(srcdir)/gdbtk/generic/%.c): Fix typo.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ARI: Add detection of printf_vma and sprintf_vma
@ 2016-11-19 19:14 sergiodj+buildbot
  2016-11-19 20:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-19 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc188e5fd6d4f8d3061ed6c58c432a150f7966e9 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: cc188e5fd6d4f8d3061ed6c58c432a150f7966e9

ARI: Add detection of printf_vma and sprintf_vma

We shouldn't be using these, since their output goes straight to
stdout, which doesn't allow redirection. So this patch updates
the ARI to detect any such use.

gdb/ChangeLog:

        * contrib/ari/gdb_ari.sh: Add detection of printf_vma and
        sprintf_vma.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Create subobject value in pretty printer
@ 2016-11-21 14:37 sergiodj+buildbot
  2016-11-21 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-21 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fff9862d5229def9318912c2de64a03dab74532 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3fff9862d5229def9318912c2de64a03dab74532

Create subobject value in pretty printer

Nowadays, we create a value of subobject in pretty printer with 'address'
being used,

  value = value_from_contents_and_address (type, valaddr + embedded_offset,
					   address + embedded_offset);

  set_value_component_location (value, val);
  /* set_value_component_location resets the address, so we may
     need to set it again.  */
  if (VALUE_LVAL (value) != lval_internalvar
      && VALUE_LVAL (value) != lval_internalvar_component
      && VALUE_LVAL (value) != lval_computed)
    set_value_address (value, address + embedded_offset);

value_from_contents_and_address creates a value from memory, but the
value we are pretty-printing may not from memory at all.

Instead of using value_from_contents_and_address, we create a value
of subobject with the same location as object's but different offset.
We avoid using address in this way.  As a result, parameter 'address'
in apply_val_pretty_printer is no longer needed, we can remove it in
next step.

We've already had the location of the 'whole' value, so it is safe
to assume we can create a value of 'component' or 'suboject' value
at the same location but with different offset.

gdb:

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

	* guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
	Don't call value_from_contents_and_address and
	set_value_address.  Call value_from_component.
	* python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
	Likewise.
	* value.c (value_from_component): New function.
	* value.h (value_from_component): Likewise.
	* valarith.c (value_subscripted_rvalue): Call
	value_from_component.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add missing POSTCOMPILE step to mi/ file generation rules
@ 2016-11-21 21:38 sergiodj+buildbot
  2016-11-21 22:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-21 21:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0de53e251ce60057d91536a4c71740b047be040 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: d0de53e251ce60057d91536a4c71740b047be040

Add missing POSTCOMPILE step to mi/ file generation rules

A little oversight from my part, it caused the Makefile not to track
the dependencies from mi/*.c files.

gdb/ChangeLog:

	* Makefile.in (%o: $(srcdir)/mi/%.c): Add missing POSTCOMPILE
	step.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use input_bfd in relocate_section
@ 2016-11-22 10:39 sergiodj+buildbot
  2016-11-22 11:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 10:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95f0d0d2338f8eba18d2b3c8cbe15b1d584b885c ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 95f0d0d2338f8eba18d2b3c8cbe15b1d584b885c

Use input_bfd in relocate_section

It makes just a little more sense to use input_bfd when retrieving
insns for relocation, since the relocations match the endianness of
the input bfd.

	* elf32-ppc.c (ppc64_elf_relocate_section): Calculate d_offset for
	input_bfd.  Replace occurrences of output_bfd as bfd_get_32 and
	bfd_put_32 param with input_bfd.
	* elf32-ppc.c (ppc_elf_relocate_section): Likewise.  Also
	ppc_elf_vle_split16 param.
	(ppc_elf_vle_split16): Rename output_bfd param to input_bfd.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gas, opcodes: fix hardware capabilities bumping in the sparc assembler.
@ 2016-11-22 13:53 sergiodj+buildbot
  2016-11-22 14:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6884417a0ff3555b192d4aceeacc5e7232cad207 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 6884417a0ff3555b192d4aceeacc5e7232cad207

gas,opcodes: fix hardware capabilities bumping in the sparc assembler.

When the assembler finds an instruction which is part of a higher
opcode architecture it bumps the current opcode architecture.  For
example:

   $ echo "mwait" | as -bump
   {standard input}: Assembler messages:
   {standard input}:1: Warning: architecture bumped from "v6" to "v9m" on "mwait"

However, when two instructions pertaining to the same opcode
architecture but associated to different SPARC hardware capabilities
are found in the input stream, and no GAS architecture is specified in
the command line, the assembler bangs:

   $ echo "mwait; wr %g0,%g1,%mcdper" | as -bump
   {standard input}: Assembler messages:
   {standard input}:1: Warning: architecture bumped from "v6" to "v9m" on "mwait"
   {standard input}:1: Error: Hardware capability "sparc5" not enabled for "wr".

... and it should'nt, as WRMCDPER pertains to the same architecture
level than MWAIT.

This patch fixes this by extending the definition of sparc opcode
architectures to contain a set of hardware capabilities and making the
assembler to take these capabilities into account when updating the
set of allowed hwcaps when an architecture bump is triggered by some
instruction.

This way, hwcaps associated to architecture levels are maintained in
opcodes, while the assembler keeps the flexibiity of defining GAS
architectures including additional hwcaps (like -Asparcfmaf or the
v8plus* variants).

A test covering this failure case is included.

gas/ChangeLog:

2016-11-22  Jose E. Marchesi  <jose.marchesi@oracle.com>

       	* config/tc-sparc.c: Move HWS_* and HWS2_* definitions to
       	opcodes/sparc-opc.c.
       	(sparc_arch): Clarify the new role of the hwcap_allowed and
       	hwcap2_allowed fields.
       	(sparc_arch_table): Remove HWS_* and HWS2_* instances from
       	hwcap_allowed and hwcap2_allowed respectively.
       	(md_parse_option): Include the opcode arch hwcaps when processing
       	-A.
       	(sparc_ip): Use the current opcode arch hwcaps to update
       	hwcap_allowed, as well of the hwcaps of the instruction triggering
       	the bump.
       	* testsuite/gas/sparc/hwcaps-bump.s: New file.
       	* testsuite/gas/sparc/hwcaps-bump.l: Likewise.
       	* testsuite/gas/sparc/sparc.exp (gas_64_check): Run tests in
       	hwcaps-bump.

include/ChangeLog:

2016-11-22  Jose E. Marchesi  <jose.marchesi@oracle.com>

       	* opcode/sparc.h (sparc_opcode_arch): New fields hwcaps and
       	hwcaps2.

opcodes/ChangeLog:

2016-11-22  Jose E. Marchesi  <jose.marchesi@oracle.com>

       	* sparc-opc.c (HWS_V8): Definition moved from
       	gas/config/tc-sparc.c.
       	(HWS_V9): Likewise.
       	(HWS_VA): Likewise.
       	(HWS_VB): Likewise.
       	(HWS_VC): Likewise.
       	(HWS_VD): Likewise.
       	(HWS_VE): Likewise.
       	(HWS_VV): Likewise.
       	(HWS_VM): Likewise.
       	(HWS2_VM): Likewise.
       	(sparc_opcode_archs): Initialize hwcaps and hwcaps2 fields of
       	existing entries.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] New regcache_raw_get_signed
@ 2016-11-22 15:10 sergiodj+buildbot
  2016-11-22 15:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fd15b2e80452f03edb3fb36c2b4c36d05f4ef4e ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 9fd15b2e80452f03edb3fb36c2b4c36d05f4ef4e

New regcache_raw_get_signed

This patch adds a new regcache api regcache_raw_get_signed.

gdb:

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

	* regcache.c (regcache_raw_get_signed): New function.
	* regcache.h (regcache_raw_get_signed): Declare.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: aarch64
@ 2016-11-22 15:55 sergiodj+buildbot
  2016-11-22 17:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0187a92f57b516f7171e70bec46701cfdaa6c6bd ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0187a92f57b516f7171e70bec46701cfdaa6c6bd

gdbarch software_single_step frame_info to regcache: aarch64

Use regcache in software_single_step.

gdb:

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

	* aarch64-tdep.c (aarch64_software_single_step): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: mips
@ 2016-11-22 17:49 sergiodj+buildbot
  2016-11-22 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 17:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7113a196bac7f1134bcdd79ad3e6badcb5d77f95 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7113a196bac7f1134bcdd79ad3e6badcb5d77f95

gdbarch software_single_step frame_info to regcache: mips

gdb:

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

	* mips-tdep.c (mips32_bc1_pc): Replace parameter frame with
	regcache.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.
	(mips32_next_pc): Likewise.
	(micromips_bc1_pc): Likewise.
	(micromips_next_pc): Likewise.
	(extended_mips16_next_pc): Likewise.
	(mips16_next_pc): Likewise.
	(mips_next_pc): Likewise.
	(mips_software_single_step): Call get_regcache_arch instead
	of get_frame_arch.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: nios2
@ 2016-11-22 19:25 sergiodj+buildbot
  2016-11-22 22:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3889f4909e0db5f5ca8ca043ef9825f0ad971fd6 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3889f4909e0db5f5ca8ca043ef9825f0ad971fd6

gdbarch software_single_step frame_info to regcache: nios2

gdb:

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

	* nios2-tdep.c (nios2_get_next_pc): Replace parameter frame
	with regcache.  Call regcache_raw_get_signed instead of
	get_frame_register_unsigned.
	(nios2_software_single_step): Call get_regcache_arch
	instead of get_frame_arch.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: rs6000
@ 2016-11-22 21:00 sergiodj+buildbot
  2016-11-23  1:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41e26ad32d17ee35f79f629654811f5e8656cab8 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 41e26ad32d17ee35f79f629654811f5e8656cab8

gdbarch software_single_step frame_info to regcache: rs6000

gdb:

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

	* rs6000-aix-tdep.c (branch_dest): Replace parameter frame with
	regcache.  Call get_regcache_arch instead of get_frame_arch.
	Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.
	(rs6000_software_single_step): Likewise.
	* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: spu
@ 2016-11-22 22:40 sergiodj+buildbot
  2016-11-23 15:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 22:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2260160f8cde8de118914ddeaf797bea42e65ce ***

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

gdbarch software_single_step frame_info to regcache: spu

gdb:

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

	* spu-tdep.c (spu_software_single_step): Call get_regcache_arch
	instead of get_frame_arch.  Call regcache_read_pc instead of
	get_frame_pc.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: tic6x
@ 2016-11-23  0:36 sergiodj+buildbot
  2016-11-23 11:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  0:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb090cfa157e35fac1c10c062fd005e38b894ea4 ***

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

gdbarch software_single_step frame_info to regcache: tic6x

gdb:

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

	* tic6x-tdep.c (tic6x_condition_true): Replace frame with
	regcache.  Call regcache_raw_get_signed instead of
	get_frame_register_signed.
	(tic6x_get_next_pc): Likewise.  Caller updated.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix spelling mistakes in comments in shell scripts
@ 2016-11-23  1:00 sergiodj+buildbot
  2016-11-23 18:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca3cbe5cd7715d1559d55f8e71be1dd7340f13b1 ***

Author: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
Branch: master
Commit: ca3cbe5cd7715d1559d55f8e71be1dd7340f13b1

Fix spelling mistakes in comments in shell scripts

gdb/ChangeLog:
2016-11-22  Ambrogino Modigliani  <ambrogino.modigliani@gmail.com>

        * contrib/expect-read1.sh: Fix spelling in comments.
        * gdb_buildall.sh: Fix spelling in comments.
        * gdb_mbuild.sh: Fix spelling in comments.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] gdbserver: Use warning for warnings
@ 2016-11-23  2:43 sergiodj+buildbot
  2016-11-23 22:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  2:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9986ba08876f86f7d36d230afc11b60a34287da8 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 9986ba08876f86f7d36d230afc11b60a34287da8

gdbserver: Use warning for warnings

gdb/gdbserver/ChangeLog:
2016-11-23  Pedro Alves  <palves@redhat.com>

	* event-loop.c (handle_file_event): Use warning.
	* linux-low.c (linux_resume_one_lwp_throw): Use warning.
	* mem-break.c (add_breakpoint_condition, add_breakpoint_commands):
	Use warning.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Makefiles: Flatten and sort file lists
@ 2016-11-23 15:19 sergiodj+buildbot
  2016-11-24  8:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b593ecca856860a8b38deb808493bba4beef3aee ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b593ecca856860a8b38deb808493bba4beef3aee

Makefiles: Flatten and sort file lists

I find the big file lists in the Makefiles a bit ugly and not very
practical.  Since there are multiple filenames on each line (as much as
fits in 80 columns), it's not easy to add, remove or change a name in
the middle.  As a result, we have a mix of long and short lines in no
particular order (ALL_TARGET_OBS is a good example).

I therefore suggest flattening the lists (one name per line) and keeping
them in alphabetical order.  The diffs will be much clearer and merge
conflicts will be easier to resolve.

A nice (IMO) side-effect I observed is that the files are compiled
alphabetically by make, so it gives a rough idea of the progress of the
build.

I added a comment in gdb/Makefile.in to mention to keep the file lists
ordered, and gave the general guidelines on what order to respect.  I
added a comment in other Makefiles which refers to gdb/Makefile.in, to
avoid duplication.

Running the patch through the buildbot found that gdb.base/default.exp
started to fail.  The languages in the error message shown when typing
"set language" have changed order.  We could probably improve gdb so
that it prints them in a stable order, regardless of the order of the
object list passed to the linked, but just fixing the test is easier for
now.

New in v2:

 - Change ordering style, directories go at the end.
 - Cleanup gdbserver's and data-directory's Makefile as well.
 - Add comments at top of Makefiles about the ordering.
 - Remove wrong trailing backslahes.
 - Fix test gdb.base/default.exp.

gdb/ChangeLog:

	* Makefile.in: Add comment about file lists ordering.
	(SUBDIR_CLI_OBS, SUBDIR_CLI_SRCS, SUBDIR_MI_OBS, SUBDIR_MI_SRCS,
	SUBDIR_TUI_OBS, SUBDIR_TUI_SRCS, SUBDIR_GCC_COMPILE_OBS,
	SUBDIR_GCC_COMPILE_SRCS, SUBDIR_GUILE_OBS, SUBDIR_GUILE_SRCS,
	SUBDIR_PYTHON_OBS, SUBDIR_PYTHON_SRCS, SUBDIR_GDBTK_OBS,
	SUBDIR_GDBTK_SRCS, XMLFILES, REMOTE_OBS, ALL_64_TARGET_OBS,
	ALL_TARGET_OBS, SFILES, HFILES_NO_SRCDIR, HFILES_WITH_SRCDIR,
	COMMON_OBS, YYFILES, YYOBJ, generated_files, ALLDEPFILES):
	Flatten list and order alphabetically.
	* data-directory/Makefile.in: Add comment about file lists
	ordering.
	(GEN_SYSCALLS_FILES, PYTHON_FILE_LIST): Flatten list and order
	alphabetically.

gdb/gdbserver/ChangeLog:

	* Makefile.in (SFILES, OBS): Flatten list and order
	alphabetically.

gdb/testsuite/ChangeLog:

	* gdb.base/default.exp: Fix output of "set language".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR12616 - gdb does not implement DW_AT_data_bit_offset
@ 2016-11-24 17:53 sergiodj+buildbot
  2016-11-24 18:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da5b30da2d1167591aa8d71b543f97bfdc2ec2a2 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: da5b30da2d1167591aa8d71b543f97bfdc2ec2a2

Fix PR12616 - gdb does not implement DW_AT_data_bit_offset

The DW_AT_data_bit_offset attribute was introduced by DWARF V4 and
allows specifying the offset of a data member within its containing
entity.  But although the new attribute was intended to replace
DW_AT_bit_offset for this purpose, GDB ignores it, and thus GCC still
emits DW_AT_bit_offset instead.  See also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71669.

This change fixes GDB's lack of support for DW_AT_data_bit_offset and
adds an appropriate test case.

gdb/ChangeLog:

	PR gdb/12616
	* dwarf2read.c (dwarf2_add_field): Handle the DWARF V4 attribute
	DW_AT_data_bit_offset.

gdb/testsuite/ChangeLog:

	PR gdb/12616
	* gdb.dwarf2/nonvar-access.exp: New testcase.  Check that GDB
	respects the DW_AT_data_bit_offset attribute.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add noexcept to custom non-throwing new operators.
@ 2016-11-24 21:00 sergiodj+buildbot
  2016-11-24 23:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbe910e6e1140cb484a74911f3cea854cf9e7e2a ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: bbe910e6e1140cb484a74911f3cea854cf9e7e2a

Add noexcept to custom non-throwing new operators.

Both libc++ and libstdc++ declare non-throwing new operators as
noexcept and overloads must also be noexcept.  This fixes a
-Wmissing-exception-spec warning with clang.

gdb/ChangeLog:

	* common/new-op.c (operator new): Mark 'noexcept'.
	(operator new[]): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix typos in comment
@ 2016-11-25 15:36 sergiodj+buildbot
  2016-11-25 17:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 15:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ce9efb079b6e7b3ab2e795db9477656375d7204 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 8ce9efb079b6e7b3ab2e795db9477656375d7204

Fix typos in comment

gdb/ChangeLog:

	* record-full.c (record_full_resume): Fix typos in comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove check requiring void argument to functions with no parameters.
@ 2016-11-25 21:27 sergiodj+buildbot
  2016-11-25 23:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8227ffad95fcd835dd5fcb3e4915159e4552b397 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 8227ffad95fcd835dd5fcb3e4915159e4552b397

Remove check requiring void argument to functions with no parameters.

C++ treats an empty parameter list as no parameters unlike C.

gdb/ChangeLog:

	* contrib/ari/gdb_ari.sh (no parameter function): Remove check.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Rename ui_out_data to mi_ui_out_data
@ 2016-11-27  4:37 sergiodj+buildbot
  2016-11-27 12:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  4:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0abe66b59fda0689c32fe9d96b3690b4d49a3027 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 0abe66b59fda0689c32fe9d96b3690b4d49a3027

Rename ui_out_data to mi_ui_out_data

Just a little cleanup, so the name is more consistent with the naming of
the equivalent structures of cli and tui.  It goes away in subsequent
patches anyway, but it might help follow the changes in those patches...

gdb/ChangeLog:

	* mi/mi-out.c (ui_out_data): Rename to ...
	(mi_ui_out_data): ... this.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Constify wrap_here/wrap_hint code path
@ 2016-11-27  8:16 sergiodj+buildbot
  2016-11-28  6:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-27  8:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2c0eef48a1bb331ca08f8f26ff82c5d4086ba0c ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: d2c0eef48a1bb331ca08f8f26ff82c5d4086ba0c

Constify wrap_here/wrap_hint code path

Constify the data path between ui_out_wrap_hint and the wrap_indent
global, because we can.  It's clearer that the argument passed to
wrap_hint is not intended to be modified by the ui_out implementation.

gdb/ChangeLog:

	* mi/mi-out.c (mi_wrap_hint): Constify argument.
	* cli-out.c (cli_wrap_hint): Likewise.
	* ui-out.c (ui_out_wrap_hint, uo_wrap_hint): Likewise.
	* ui-out.h (ui_out_wrap_hint, wrap_hint_ftype): Likewise.
	* utils.c (wrap_here): Likewise.
	(wrap_indent): Constify.
	* utils.h (wrap_here): Constify argument.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Move computed value's frame id to piece_closure
@ 2016-11-28 17:50 sergiodj+buildbot
  2016-11-28 18:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 17:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee40d8d45213caf0cfb63e603f0fd5a58532e751 ***

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

Move computed value's frame id to piece_closure

Nowadays, we set computed value's frame id, which is a misuse to me.
The computed value itself doesn't care about frame id, but function
value_computed_funcs (val)->read (or read_pieced_value) cares about
which frame the register is relative to, so 'struct piece_closure' is
a better place to fit frame id.

This patch adds a frame id in 'struct piece_closure', and use it
instead of using computed value's frame id.

gdb:

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

	* dwarf2loc.c (struct piece_closure) <frame_id>: New field.
	(allocate_piece_closure): Add new parameter 'frame' and set
	closure's frame_id field accordingly.
	(read_pieced_value): Get frame from closure instead of value.
	(dwarf2_evaluate_loc_desc_full): Remove code getting frame id.
	Don't set value's frame id.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR20886, looping in ppc64_elf_size_stubs
@ 2016-11-30  7:01 sergiodj+buildbot
  2016-11-30  8:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-30  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea3d7d1cab4221ab729327bb4d957352c79d05f0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ea3d7d1cab4221ab729327bb4d957352c79d05f0

PR20886, looping in ppc64_elf_size_stubs

The PR20886 binary is large enough that there are two stub sections
servicing .text (which is 88M).  It so happens that between one
iteration of sizing and the next that one stub section grows while
the other shrinks.  Since one section is always growing, the loop
never terminates.

This patch changes the algorithm to not update previous size on
shrinking, once we go past a certain number of iterations.

	PR ld/20886
	* elf64-ppc.c (ppc64_elf_size_stubs): Make rawsize max size seen
	on any pass past STUB_SHRINK_ITER.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Revert accidental elf.c change
@ 2016-11-30 12:13 sergiodj+buildbot
  2016-11-30 13:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-11-30 12:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9a38e0f5287ce7b4629f5f923191e38dd7355c0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e9a38e0f5287ce7b4629f5f923191e38dd7355c0

Revert accidental elf.c change

	* elf.c (get_program_header_size): Revert accidental change.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::vector for cli_ui_out_data::streams
@ 2016-12-01  5:08 sergiodj+buildbot
  2016-12-01  7:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  5:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b9b118c3bb29052ee76c6bf32b99962cda5113ba ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b9b118c3bb29052ee76c6bf32b99962cda5113ba

Use std::vector for cli_ui_out_data::streams

Use a standard vector instead of the home-made version.  I used a vector
of plain pointers, because the cli_ui_out_data object doesn't own the
streams objects (i.e. they shouldn't be deleted when the vector is
deleted).

gdb/ChangeLog:

	* cli-out.h (cli_ui_out_data) <streams>: Change type to
	std::vector.
	* cli-out.c: Remove vec.h include.
	(cli_uiout_dtor): Update.
	(cli_field_fmt): Update.
	(cli_spaces): Update.
	(cli_text): Update.
	(cli_message): Update.
	(cli_flush): Update.
	(cli_redirect): Update.
	(out_field_fmt): Update.
	(field_separator): Update.
	(cli_out_data_ctor): Update.
	(cli_out_new): Update.
	(cli_out_set_stream): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string in ui_out_table
@ 2016-12-01  5:58 sergiodj+buildbot
  2016-12-01  9:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-01  5:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95a23284a3db0ec85bb0b11c70e6b5acf00563f6 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 95a23284a3db0ec85bb0b11c70e6b5acf00563f6

Use std::string in ui_out_table

Use std::string for the id field of the ui_out_table object.

I found that all users of ui_out_table_begin passed a non-NULL value to
the tblid parameter, so we don't have to worry about the NULL case.  I
changed the tblid parameter to be a std::string while at it.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_table) <id>: Change type to
	std::string.
	(ui_out_table_begin): Change tblid parameter type to
	std::string, adapt code.
	update following type change.
	(clear_table): Update.
	(ui_out_new): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using gdb_test on a single line.
@ 2016-12-01 21:50 sergiodj+buildbot
  2016-12-01 23:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdc7edd7b17dddd3558bd04d9b2fb5a73dc75f1c ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: cdc7edd7b17dddd3558bd04d9b2fb5a73dc75f1c

Fix test names starting with uppercase using gdb_test on a single line.

Changes in v3:
  Fixed incorrect substitutions.

This fixes offender testcases that have test names starting with uppercase
when using gdb_test in a single line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.arch/i386-mpx-simple_segv.exp
	* gdb.arch/i386-mpx.exp
	* gdb.arch/i386-permbkpt.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.arch/vsx-regs.exp
	* gdb.base/bfp-test.exp
	* gdb.base/break.exp
	* gdb.base/breakpoint-shadow.exp
	* gdb.base/callfuncs.exp
	* gdb.base/charset.exp
	* gdb.base/commands.exp
	* gdb.base/completion.exp
	* gdb.base/dfp-test.exp
	* gdb.base/echo.exp
	* gdb.base/ending-run.exp
	* gdb.base/eval.exp
	* gdb.base/expand-psymtabs.exp
	* gdb.base/float128.exp
	* gdb.base/floatn.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/gdb1056.exp
	* gdb.base/gdb11531.exp
	* gdb.base/kill-after-signal.exp
	* gdb.base/multi-forks.exp
	* gdb.base/overlays.exp
	* gdb.base/pending.exp
	* gdb.base/sepdebug.exp
	* gdb.base/testenv.exp
	* gdb.base/valgrind-db-attach.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.base/watchpoint.exp
	* gdb.base/watchpoints.exp
	* gdb.cp/arg-reference.exp
	* gdb.cp/baseenum.exp
	* gdb.cp/operator.exp
	* gdb.cp/shadow.exp
	* gdb.dwarf2/dw2-op-out-param.exp
	* gdb.dwarf2/dw2-reg-undefined.exp
	* gdb.go/chan.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.go/methods.exp
	* gdb.go/package.exp
	* gdb.guile/scm-parameter.exp
	* gdb.guile/scm-progspace.exp
	* gdb.guile/scm-value.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.multi/multi-attach.exp
	* gdb.multi/tids.exp
	* gdb.opt/clobbered-registers-O2.exp
	* gdb.pascal/floats.exp
	* gdb.pascal/integers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-events.exp
	* gdb.python/py-parameter.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-type.exp
	* gdb.python/py-value.exp
	* gdb.python/py-xmethods.exp
	* gdb.python/python.exp
	* gdb.reverse/break-precsave.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/sigall-precsave.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.server/ext-attach.exp
	* gdb.server/ext-restart.exp
	* gdb.server/ext-run.exp
	* gdb.server/ext-wrapper.exp
	* gdb.stabs/gdb11479.exp
	* gdb.stabs/weird.exp
	* gdb.threads/attach-many-short-lived-threads.exp
	* gdb.threads/kill.exp
	* gdb.threads/watchpoint-fork.exp


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test
@ 2016-12-01 23:25 sergiodj+buildbot
  2016-12-02  9:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb95117e107fe58ecd35683bf0e8da3b414378ff ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: bb95117e107fe58ecd35683bf0e8da3b414378ff

Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test

This fixes offender testcases that have test names starting with uppercase
when using gdb_test/mi_gdb_test in a multi-line construct.

gdb/testsuite/ChangeLog
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout the files.

	* gdb.ada/array_return.exp
	* gdb.ada/expr_delims.exp
	* gdb.ada/mi_dyn_arr.exp
	* gdb.ada/mi_interface.exp
	* gdb.ada/mi_var_array.exp
	* gdb.ada/watch_arg.exp
	* gdb.arch/alpha-step.exp
	* gdb.arch/altivec-regs.exp
	* gdb.arch/e500-regs.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.base/arrayidx.exp
	* gdb.base/break.exp
	* gdb.base/checkpoint.exp
	* gdb.base/debug-expr.exp
	* gdb.base/dmsym.exp
	* gdb.base/radix.exp
	* gdb.base/sepdebug.exp
	* gdb.base/testenv.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.cell/break.exp
	* gdb.cell/ea-cache.exp
	* gdb.compile/compile.exp
	* gdb.cp/gdb2495.exp
	* gdb.gdb/selftest.exp
	* gdb.gdb/xfullpath.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.objc/basicclass.exp
	* gdb.pascal/hello.exp
	* gdb.pascal/integers.exp
	* gdb.python/py-breakpoint.exp
	* gdb.python/py-cmd.exp
	* gdb.python/py-linetable.exp
	* gdb.python/py-xmethods.exp
	* gdb.python/python.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/sigall-precsave.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.threads/leader-exit.exp
	* gdb.threads/pthreads.exp
	* gdb.threads/wp-replication.exp
	* gdb.trace/actions.exp
	* gdb.trace/mi-tsv-changed.exp
	* gdb.trace/tsv.exp


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fixup testcases outputting own name as a test name and standardize failed compilation messages
@ 2016-12-02  1:27 sergiodj+buildbot
  2016-12-02 11:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  1:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84c93cd5f1ff869eb8c04314738eaa2cddb3c29e ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 84c93cd5f1ff869eb8c04314738eaa2cddb3c29e

Fixup testcases outputting own name as a test name and standardize failed compilation messages

Changes in v3:

- Adjusted some testcases where the message "failed to compile" was not unique.

Changes in v2:

- Addressed comments from reviewers.
- Fixed spurious whitespaces.
- Changed compilation failure messages that included source/binary paths to
  ones that are short and deterministic.

---

Another bit of cleanup to the testsuite. We have a number of tests that are
not honoring the rule of not outputting their own name as a test name.

I fixed up all the offenders i could find with the following regular
expression:

"(xfail|kfail|kpass|fail|pass|unsupported|untested) ([A-Za-z0-9]+|\\\$(.)*testfile(.)*)\.exp$"

gdb/testsuite/ChangeLog:
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names and standardize compilation error messages throughout
	the following files:

	* gdb.ada/start.exp
	* gdb.arch/alpha-step.exp
	* gdb.arch/e500-prologue.exp
	* gdb.arch/ftrace-insn-reloc.exp
	* gdb.arch/gdb1291.exp
	* gdb.arch/gdb1431.exp
	* gdb.arch/gdb1558.exp
	* gdb.arch/i386-dr3-watch.exp
	* gdb.arch/i386-sse-stack-align.exp
	* gdb.arch/ia64-breakpoint-shadow.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-aix-prologue.exp
	* gdb.arch/thumb-bx-pc.exp
	* gdb.base/annota1.exp
	* gdb.base/annota3.exp
	* gdb.base/arrayidx.exp
	* gdb.base/assign.exp
	* gdb.base/attach.exp
	* gdb.base/auxv.exp
	* gdb.base/bang.exp
	* gdb.base/bfp-test.exp
	* gdb.base/bigcore.exp
	* gdb.base/bitfields2.exp
	* gdb.base/break-fun-addr.exp
	* gdb.base/break-probes.exp
	* gdb.base/call-rt-st.exp
	* gdb.base/callexit.exp
	* gdb.base/catch-fork-kill.exp
	* gdb.base/charset.exp
	* gdb.base/checkpoint.exp
	* gdb.base/comprdebug.exp
	* gdb.base/constvars.exp
	* gdb.base/coredump-filter.exp
	* gdb.base/cursal.exp
	* gdb.base/cvexpr.exp
	* gdb.base/detach.exp
	* gdb.base/display.exp
	* gdb.base/dmsym.exp
	* gdb.base/dprintf-pending.exp
	* gdb.base/dso2dso.exp
	* gdb.base/dtrace-probe.exp
	* gdb.base/dump.exp
	* gdb.base/enum_cond.exp
	* gdb.base/exe-lock.exp
	* gdb.base/exec-invalid-sysroot.exp
	* gdb.base/execl-update-breakpoints.exp
	* gdb.base/exprs.exp
	* gdb.base/fileio.exp
	* gdb.base/find.exp
	* gdb.base/finish.exp
	* gdb.base/fixsection.exp
	* gdb.base/foll-vfork.exp
	* gdb.base/frame-args.exp
	* gdb.base/gcore.exp
	* gdb.base/gdb1250.exp
	* gdb.base/global-var-nested-by-dso.exp
	* gdb.base/gnu-ifunc.exp
	* gdb.base/hashline1.exp
	* gdb.base/hashline2.exp
	* gdb.base/hashline3.exp
	* gdb.base/hbreak-in-shr-unsupported.exp
	* gdb.base/huge.exp
	* gdb.base/infcall-input.exp
	* gdb.base/info-fun.exp
	* gdb.base/info-shared.exp
	* gdb.base/jit-simple.exp
	* gdb.base/jit-so.exp
	* gdb.base/jit.exp
	* gdb.base/jump.exp
	* gdb.base/label.exp
	* gdb.base/lineinc.exp
	* gdb.base/logical.exp
	* gdb.base/longjmp.exp
	* gdb.base/macscp.exp
	* gdb.base/miscexprs.exp
	* gdb.base/new-ui-echo.exp
	* gdb.base/new-ui-pending-input.exp
	* gdb.base/new-ui.exp
	* gdb.base/nodebug.exp
	* gdb.base/nofield.exp
	* gdb.base/offsets.exp
	* gdb.base/overlays.exp
	* gdb.base/pending.exp
	* gdb.base/pointers.exp
	* gdb.base/pr11022.exp
	* gdb.base/printcmds.exp
	* gdb.base/prologue.exp
	* gdb.base/ptr-typedef.exp
	* gdb.base/realname-expand.exp
	* gdb.base/relativedebug.exp
	* gdb.base/relocate.exp
	* gdb.base/remote.exp
	* gdb.base/reread.exp
	* gdb.base/return2.exp
	* gdb.base/savedregs.exp
	* gdb.base/sep.exp
	* gdb.base/sepdebug.exp
	* gdb.base/sepsymtab.exp
	* gdb.base/set-inferior-tty.exp
	* gdb.base/setshow.exp
	* gdb.base/shlib-call.exp
	* gdb.base/sigaltstack.exp
	* gdb.base/siginfo-addr.exp
	* gdb.base/signals.exp
	* gdb.base/signull.exp
	* gdb.base/sigrepeat.exp
	* gdb.base/so-impl-ld.exp
	* gdb.base/solib-display.exp
	* gdb.base/solib-overlap.exp
	* gdb.base/solib-search.exp
	* gdb.base/solib-symbol.exp
	* gdb.base/structs.exp
	* gdb.base/structs2.exp
	* gdb.base/symtab-search-order.exp
	* gdb.base/twice.exp
	* gdb.base/unload.exp
	* gdb.base/varargs.exp
	* gdb.base/watchpoint-solib.exp
	* gdb.base/watchpoint.exp
	* gdb.base/whatis.exp
	* gdb.base/wrong_frame_bt_full.exp
	* gdb.btrace/dlopen.exp
	* gdb.cell/ea-standalone.exp
	* gdb.cell/ea-test.exp
	* gdb.cp/dispcxx.exp
	* gdb.cp/gdb2384.exp
	* gdb.cp/method2.exp
	* gdb.cp/nextoverthrow.exp
	* gdb.cp/pr10728.exp
	* gdb.disasm/am33.exp
	* gdb.disasm/h8300s.exp
	* gdb.disasm/mn10300.exp
	* gdb.disasm/sh3.exp
	* gdb.dwarf2/dw2-dir-file-name.exp
	* gdb.fortran/complex.exp
	* gdb.fortran/library-module.exp
	* gdb.guile/scm-pretty-print.exp
	* gdb.guile/scm-symbol.exp
	* gdb.guile/scm-type.exp
	* gdb.guile/scm-value.exp
	* gdb.linespec/linespec.exp
	* gdb.mi/gdb701.exp
	* gdb.mi/gdb792.exp
	* gdb.mi/mi-breakpoint-changed.exp
	* gdb.mi/mi-dprintf-pending.exp
	* gdb.mi/mi-dprintf.exp
	* gdb.mi/mi-exit-code.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/mi-solib.exp
	* gdb.mi/new-ui-mi-sync.exp
	* gdb.mi/pr11022.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.opt/solib-intra-step.exp
	* gdb.python/py-events.exp
	* gdb.python/py-finish-breakpoint.exp
	* gdb.python/py-mi.exp
	* gdb.python/py-prettyprint.exp
	* gdb.python/py-shared.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-template.exp
	* gdb.python/py-type.exp
	* gdb.python/py-value.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/solib-reverse.exp
	* gdb.server/solib-list.exp
	* gdb.stabs/weird.exp
	* gdb.threads/reconnect-signal.exp
	* gdb.threads/stepi-random-signal.exp
	* gdb.trace/actions.exp
	* gdb.trace/ax.exp
	* gdb.trace/backtrace.exp
	* gdb.trace/change-loc.exp
	* gdb.trace/deltrace.exp
	* gdb.trace/ftrace-lock.exp
	* gdb.trace/ftrace.exp
	* gdb.trace/infotrace.exp
	* gdb.trace/mi-tracepoint-changed.exp
	* gdb.trace/packetlen.exp
	* gdb.trace/passcount.exp
	* gdb.trace/pending.exp
	* gdb.trace/range-stepping.exp
	* gdb.trace/report.exp
	* gdb.trace/stap-trace.exp
	* gdb.trace/tfind.exp
	* gdb.trace/trace-break.exp
	* gdb.trace/trace-condition.exp
	* gdb.trace/trace-enable-disable.exp
	* gdb.trace/trace-mt.exp
	* gdb.trace/tracecmd.exp
	* gdb.trace/tspeed.exp
	* gdb.trace/tsv.exp
	* lib/perftest.exp


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use std::string for ui_out_hdr's text fields
@ 2016-12-02  2:20 sergiodj+buildbot
  2016-12-02 15:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  2:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5209615263fd0444da28cdfb6661ad287909a70 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: c5209615263fd0444da28cdfb6661ad287909a70

Use std::string for ui_out_hdr's text fields

This patch makes ui_out_hdr use std::string for its text fields.  It
makes freeing automatic when the object is deleted.

gdb/ChangeLog:

	* mi/mi-out.c (mi_table_header): Change char * args to
	std::string.
	* cli-out.c (cli_table_header): Likewise.
	* ui-out.h (table_header_ftype): Likewise.
	(ui_out_table_header): Constify colhdr argument.
	(ui_out_query_field): Constify col_name argument.
	* ui-out.c (ui_out_hdr) <col_name, colhdr>: Change type to
	std::string.
	(uo_table_header): Change char * args to std::string.
	(ui_out_table_header): Likewise.
	(get_next_header): Constify colhdr argument and adapt.
	(clear_header_list): Don't free col_name/colhdr fields.
	(append_header_to_list): Change char * args to std::string and
	adapt.
	(verify_field): Constify variable.
	(ui_out_query_field): Constify col_name argument and adapt.
	* breakpoint.c (wrap_indent_at_field): Constify variable.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Class-ify ui_out_hdr
@ 2016-12-02  2:49 sergiodj+buildbot
  2016-12-02 15:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  2:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37e20dd6599203c4e261fc3a2e86711c90cbbed9 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 37e20dd6599203c4e261fc3a2e86711c90cbbed9

Class-ify ui_out_hdr

This patch makes ui_out_hdr (the object that represents an ui-out table
header) a proper C++ class.  No behavior changes, it's all about
encapsulation.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_hdr): Replace with ...
	(class ui_out_hdr): ... this.
	(append_header_to_list): Update.
	(get_next_header): Update.
	(ui_out_query_field): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Class-ify ui_out_level
@ 2016-12-02  3:57 sergiodj+buildbot
  2016-12-02 16:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  3:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 909c0aa5824080c287b390f82726cf5bfb7011e3 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 909c0aa5824080c287b390f82726cf5bfb7011e3

Class-ify ui_out_level

This patch changes struct ui_out_level to be a real C++ class.  No
behavioral changes.

gdb/ChangeLog:

	* ui-out.c (struct ui_out_level): Replace with ...
	(class ui_out_level): ... this.
	(current_level): Update.
	(push_level): Update.
	(pop_level): Update.
	(verify_field): Update.
	(ui_out_new): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ui_out_table: Replace boolean flag with enum
@ 2016-12-02  5:00 sergiodj+buildbot
  2016-12-02 18:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  5:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77a179e77b38161e461f5e37512f0b3fc3582181 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 77a179e77b38161e461f5e37512f0b3fc3582181

ui_out_table: Replace boolean flag with enum

This patch is just a little cleanup, it replaces the body_flag field of
ui_out_table with an enum.  It expresses more explicitly the
intent of the field (check that state == TABLE_STATE_HEADERS conveys
more what we want to do than checking for !body_flag).

New in v2:

  - Remove unnecessary ui_out_table_state::.

gdb/ChangeLog:

	* ui-out.c (enum ui_out_table_state): New enum.
	(struct ui_out_table) <body_flag>: Remove field.
	<state>: New field.
	(ui_out_table_begin): Replace usages of body_flag with state.
	(ui_out_table_body): Likewise.
	(ui_out_table_end): Likewise.
	(ui_out_table_header): Likewise.
	(ui_out_begin): Likewise.
	(verify_field): Likewise.
	(ui_out_new): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove mi_out_data::suppress_output
@ 2016-12-02 15:26 sergiodj+buildbot
  2016-12-03  6:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 15:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 233c8c27eb81b0a3ab5182dcb59c7306ba9bd3f3 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 233c8c27eb81b0a3ab5182dcb59c7306ba9bd3f3

Remove mi_out_data::suppress_output

The suppress_output field of the mi_ui_out_data structure is never actually
set to 1/true.  We can therefore remove it, and remove all the

  if (suppress_output)

checks.

gdb/ChangeLog:

	* mi/mi-out.c (mi_ui_out_data) <suppress_output>: Remove.
	(mi_table_body): Remove suppress_output check.
	(mi_table_end): Likewise.
	(mi_table_header): Likewise.
	(mi_begin): Likewise.
	(mi_end): Likewise.
	(mi_field_int): Likewise.
	(mi_field_string): Likewise.
	(mi_field_fmt): Likewise.
	(mi_out_data_ctor): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution
@ 2016-12-02 19:55 sergiodj+buildbot
  2016-12-03 16:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 19:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01770bbde902e075e524b518ac6c1087a4cc1cfb ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 01770bbde902e075e524b518ac6c1087a4cc1cfb

Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution

It'd be handy to be able to iterate over command arguments in
user-defined commands, in order to support optional arguments
($arg0..$argN).

I thought I could make it work with "eval", but alas, it doesn't work
currently.  E.g., with:

 define test
   set $i = 0
   while $i < $argc
     eval "print $arg%d", $i
     set $i = $i + 1
   end
 end

we get:

 (gdb) test 1
 $1 = void
 (gdb) test 1 2 3
 $2 = void
 $3 = void
 $4 = void
 (gdb)

The problem is that "eval" doesn't do user-defined command arguments
substitution after expanding its own argument.  This patch fixes that,
which makes the example above work:

 (gdb) test 1
 $1 = 1
 (gdb) test 1 2 3
 $2 = 1
 $3 = 2
 $4 = 3
 (gdb)

New test included, similar the above, but also exercises expanding
$argc.

I think this is likely to simplify many scripts out there, so I'm
adding an example to the manual and mentioning it in NEWS as well.

gdb/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	PR cli/20559
	* NEWS: Mention "eval" expands user-defined command arguments.
	* cli/cli-script.c (execute_control_command): Adjust to rename.
	(insert_args): Rename to ...
	(insert_user_defined_cmd_args): ... this, and make extern.
	* cli/cli-script.h (insert_user_defined_cmd_args): New
	declaration.
	* printcmd.c: Include "cli/cli-script.h".
	(eval_command): Call insert_user_defined_cmd_args.

gdb/doc/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	PR cli/20559
	* gdb.texinfo (Define): Add example of using "eval" to process a
	variable number of arguments.
	(Output) <eval>: Add anchor.

gdb/testsuite/ChangeLog:
2016-12-02  Pedro Alves  <palves@redhat.com>

	PR cli/20559
	* gdb.base/commands.exp (user_defined_command_args_eval): New
	procedure.
	(top level): Call it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Indirect and warning symbols
@ 2016-12-03 11:55 sergiodj+buildbot
  2016-12-03 22:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8400d40d954ec3b4a3fe9200645a1b6e90ba46f4 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 8400d40d954ec3b4a3fe9200645a1b6e90ba46f4

Indirect and warning symbols

It's possible but unlikely that an indirect symbol points at a warning
symbol.

	* elf64-ppc.c (add_symbol_adjust): Correct order of tests for
	warning and indirect symbols.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix bugs with tbnz/tbz instructions.
@ 2016-12-04  2:02 sergiodj+buildbot
  2016-12-04 12:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-04  2:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 668650d58d61d9d170f3e5b5c1657ed1c3e2b34b ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: 668650d58d61d9d170f3e5b5c1657ed1c3e2b34b

Fix bugs with tbnz/tbz instructions.

sim/aarch64
	* simulator.c (tbnz, tbz): Cast 1 to uint64_t before shifting.
	(dexTestBranchImmediate): Shift high bit of pos by 5 not 4.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix seg-fault in linker parsing a corrupt input file.
@ 2016-12-05 13:22 sergiodj+buildbot
  2016-12-05 14:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 13:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT daae68f4f372e0618d6b9c64ec0f1f74eae6ab3d ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: daae68f4f372e0618d6b9c64ec0f1f74eae6ab3d

Fix seg-fault in linker parsing a corrupt input file.

	PR ld/20924
	(aout_link_add_symbols): Fix off by one error checking for
	overflow of string offset.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [ARM] Add ARMv8.3 command line option and feature flag
@ 2016-12-05 15:33 sergiodj+buildbot
  2016-12-05 17:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 15:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a12fd8e1b1c9c6a16e3cc9fc477d7e459776b587 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: a12fd8e1b1c9c6a16e3cc9fc477d7e459776b587

[ARM] Add ARMv8.3 command line option and feature flag

ARMv8.3 is an architectural extension of ARMv8.  Add the
feature macro and -march=armv8.3-a gas command line option
for the ARM target.

https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

gas/
	* config/tc-arm.c (arm_archs): Add "armv8.3-a".
	* doc/c-arm.texi (-march): Add "armv8.3-a".

include/
	* opcode/arm.h (ARM_EXT2_V8_3A, ARM_AEXT2_V8_3A): New.
	(ARM_ARCH_V8_3A): New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] argv.c (expandargv): Check for directories passed as @-files.
@ 2016-12-06  7:30 sergiodj+buildbot
  2016-12-06 10:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-06  7:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc72affa6875e81fc9d495a216a8bcb34045ffcd ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: fc72affa6875e81fc9d495a216a8bcb34045ffcd

argv.c (expandargv): Check for directories passed as @-files.

gcc pr 78584


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Assert on lval_register
@ 2016-12-06 14:59 sergiodj+buildbot
  2016-12-06 16:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-06 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c2ba67e6ab10879968c938aefd4d0d0b4ce79bc ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7c2ba67e6ab10879968c938aefd4d0d0b4ce79bc

Assert on lval_register

This patch adds asserts where the value's lval must be lval_register.
This triggers an error in frame_register_unwind because VALUE_REGNUM
is used but value's lval is not lval_register.

This also reveals a design issue in frame_register_unwind, that is
arguments addrp and realnump are mutually exclusive, we either use
addrp (for lval_memory), or use realnump (for lval_register).  This
can be done in a separate patch.

gdb:

2016-12-06  Yao Qi  <yao.qi@linaro.org>

	* frame.c (frame_register_unwind): Set *realnump if *lvalp is
	lval_register.
	* value.c (deprecated_value_next_frame_id_hack): Assert
	value->lval is lval_register.
	(deprecated_value_regnum_hack): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix seg-fault in strip when copying a corrupt binary.
@ 2016-12-06 17:12 sergiodj+buildbot
  2016-12-06 18:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-06 17:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f3ca05b487e9755018b4c9a053a2e6c35d8a7df ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 4f3ca05b487e9755018b4c9a053a2e6c35d8a7df

Fix seg-fault in strip when copying a corrupt binary.

	PR binutils/20931
	* elf.c (copy_special_section_fields): Check for an invalid
	sh_link field before attempting to follow it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix internal error in the linker by replacing a call to abort with an error message.
@ 2016-12-07 10:48 sergiodj+buildbot
  2016-12-07 12:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-07 10:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2596ca5d7f6ab6d38882bf0f0fc44fe352afcb1 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: c2596ca5d7f6ab6d38882bf0f0fc44fe352afcb1

Fix internal error in the linker by replacing a call to abort with an error message.

	PR ld/20932
	* elflink.c (bfd_elf_record_link_assignment): Replace call to
	abort with an error message and error return value.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/include: opcode/mips.h: Correct INSN_CHIP_MASK
@ 2016-12-07 15:39 sergiodj+buildbot
  2016-12-07 18:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-07 15:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b0781150f69b6ff251dac447c77e4d4f6598da8 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4b0781150f69b6ff251dac447c77e4d4f6598da8

MIPS/include: opcode/mips.h: Correct INSN_CHIP_MASK

Complement commit e407c74b5b60 ("Support for MIPS R5900 (Sony Playstation
2)"), <https://sourceware.org/ml/binutils/2012-12/msg00240.html>, and
commit 2c62985659da ("MIPS: Add Octeon 3 support") and update the chip
mask accordingly.

	include/
	* opcode/mips.h (INSN_CHIP_MASK): Update according to bit use.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Fix PC-relative operation delay-slot adjustment
@ 2016-12-09  0:50 sergiodj+buildbot
  2016-12-09  6:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09  0:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 860b03a8f357d1565bd9d79ae25121059b2d28ae ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 860b03a8f357d1565bd9d79ae25121059b2d28ae

MIPS16/opcodes: Fix PC-relative operation delay-slot adjustment

Complement commit dd8b7c222e0e ("MIPS: mips16e jalrc/jrc opcodes"),
<https://sourceware.org/ml/binutils/2005-07/msg00349.html>, and stop the
disassembler making a delay-slot adjustment for PC-relative operations
following either MIPS16e compact jumps, or undefined RR/J(AL)R(C)
encodings that have the `l' (link) and `ra' (source register is `ra')
bits set both at a time.  Adjust code description for accuracy.  Add a
suitable test case.

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Avoid delay-slot
	adjustment for PC-relative operations following MIPS16e compact
	jumps or undefined RR/J(AL)R(C) encodings.

	binutils/
	* testsuite/binutils-all/mips/mips16-pcrel.d: New test.
	* testsuite/binutils-all/mips/mips16-pcrel.s: New test source.
	* testsuite/binutils-all/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Fix off-by-one indentation in `print_mips16_insn_arg'
@ 2016-12-09  1:29 sergiodj+buildbot
  2016-12-09 15:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09  1:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39f66f3ae25ebd3a065218ce880280fd5b4b861c ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 39f66f3ae25ebd3a065218ce880280fd5b4b861c

MIPS16/opcodes: Fix off-by-one indentation in `print_mips16_insn_arg'

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Remove extraneous
	indentation space across.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Avoid PATH_MAX usage
@ 2016-12-09  7:23 sergiodj+buildbot
  2016-12-09 15:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09  7:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53488a6e194af11c2528e5e284facb8a6171b695 ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: 53488a6e194af11c2528e5e284facb8a6171b695

Avoid PATH_MAX usage

On GNU/Hurd, there is no "#define PATH_MAX", so this failed to build.

	gdb/
	* inferior.c (print_selected_inferior): Avoid PATH_MAX usage.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Hurd: Adjust to changes to "push pruning old threads down to the target"
@ 2016-12-09  8:00 sergiodj+buildbot
  2016-12-09 16:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09  8:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c752a4cccb99ba73f51eff74b394dcdcd26d4c59 ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: c752a4cccb99ba73f51eff74b394dcdcd26d4c59

Hurd: Adjust to changes to "push pruning old threads down to the target"

For "info threads", we currently run into:

    $ gdb/gdb -q -nw -nx --batch -ex start -ex info\ threads bfd/doc/chew
    Temporary breakpoint 1 at 0x80486e0: file ../../../W._C._Handy/bfd/doc/chew.c, line 1535.
    [New Thread 10656.5]

    Thread 4 hit Temporary breakpoint 1, main (ac=1, av=0x102cd84) at ../../../W._C._Handy/bfd/doc/chew.c:1535
    1535    {
      Id   Target Id         Frame
      1    bogus thread id 1 Can't fetch registers from thread bogus thread id 1: No such thread

Before commit e8032dde10b743253125d7defb5f5503b21c1d26,
gdb/thread.c:update_thread_list used to call prune_threads, after that change
it doesn't anymore, and we don't implement the to_update_thread_list target
method where the prune_threads call got moved.  For now, apply a fix, related
to commit c82f56d9d760a9b4034eeaac44f2f0fa5779ff69 "Hurd: Adjust to
startup-with-shell changes", which restores the previous behavior:

      Id   Target Id         Frame
    * 4    Thread 10688.4    main (ac=1, av=0x102cd84) at ../../../W._C._Handy/bfd/doc/chew.c:1535
      5    Thread 10688.5    0x0106096c in ?? () from /lib/i386-gnu/libc.so.0.3

Not perfect, but at least better.

	gdb/
	* gnu-nat.c (gnu_create_inferior): After startup_inferior, call
	prune_threads.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use code cache in aarch64 prologue analyzer
@ 2016-12-09 11:55 sergiodj+buildbot
  2016-12-09 20:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc2f703edb656c69b0026a006c6063cdb255e06a ***

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

Use code cache in aarch64 prologue analyzer

This patch change aarch prologue analyzer using code cache, in order
to improve the performance of remote debugging.

gdb.perf/skip-prologue.exp (measured by wall-time) is improved when
the program is compiled without debug information.

			Original	Patched		Original	Patched
			without dbg	without dbg	with dbg	with dbg

/			11.1635239124	9.99472999573	9.65339517593	9.66648793221
-fstack-protector-all	11.2560930252	9.338118	9.63896489143	9.59474396706

gdb:

2016-12-9  Yao Qi  <yao.qi@linaro.org>

	* aarch64-tdep.c (instruction_reader::read): Call
	read_code_unsigned_integer instead of
	read_memory_unsigned_integer.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Create tdep->rl78_psw_type lazily
@ 2016-12-09 16:12 sergiodj+buildbot
  2016-12-09 23:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a31b34a18d61dee55042f2ab23c8fa9203fe6ef ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1a31b34a18d61dee55042f2ab23c8fa9203fe6ef

Create tdep->rl78_psw_type lazily

I build GDB for all targets enabled.  When I "set architecture rl78",
GDB crashes,

(gdb) set architecture rl78

Program received signal SIGSEGV, Segmentation fault.
append_flags_type_flag (type=0x20cc0e0, bitpos=bitpos@entry=0, name=name@entry=0x11dba3f "CY") at ../../binutils-gdb/gdb/gdbtypes.c:4926
4926				   name);
(gdb) bt 10
 #0  append_flags_type_flag (type=0x20cc0e0, bitpos=bitpos@entry=0, name=name@entry=0x11dba3f "CY") at ../../binutils-gdb/gdb/gdbtypes.c:4926
 #1  0x00000000004aaca8 in rl78_gdbarch_init (info=..., arches=<optimized out>) at ../../binutils-gdb/gdb/rl78-tdep.c:1410
 #2  0x00000000006b05a4 in gdbarch_find_by_info (info=...) at ../../binutils-gdb/gdb/gdbarch.c:5269
 #3  0x000000000060eee4 in gdbarch_update_p (info=...) at ../../binutils-gdb/gdb/arch-utils.c:557
 #4  0x000000000060f8a8 in set_architecture (ignore_args=<optimized out>, from_tty=1, c=<optimized out>) at ../../binutils-gdb/gdb/arch-utils.c:531
 #5  0x0000000000593d0b in do_set_command (arg=<optimized out>, arg@entry=0x20be851 "rl78", from_tty=from_tty@entry=1, c=c@entry=0x20b1540)
    at ../../binutils-gdb/gdb/cli/cli-setshow.c:455
 #6  0x00000000007665c3 in execute_command (p=<optimized out>, p@entry=0x20be840 "set architecture rl78", from_tty=1) at ../../binutils-gdb/gdb/top.c:666
 #7  0x00000000006935f4 in command_handler (command=0x20be840 "set architecture rl78") at ../../binutils-gdb/gdb/event-top.c:577
 #8  0x00000000006938d8 in command_line_handler (rl=<optimized out>) at ../../binutils-gdb/gdb/event-top.c:767
 #9  0x0000000000692c2c in gdb_rl_callback_handler (rl=0x20be890 "") at ../../binutils-gdb/gdb/event-top.c:200

The cause is that we want to access some builtin types in gdbarch init, but
it is not initialized yet.  I fix it by creating the type when it is to be
used.  We've already done this in sparc, sparc64 and m68k.

gdb:

2016-12-09  Yao Qi  <yao.qi@linaro.org>

	PR tdep/20953
	* rl78-tdep.c (rl78_psw_type): New function.
	(rl78_register_type): Call rl78_psw_type.
	(rl78_gdbarch_init): Move code to rl78_psw_type.

gdb/testsuite:

2016-12-09  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/all-architectures.exp.in: Remove kfail for rl78.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Reformat raw EXTEND and undecoded output
@ 2016-12-09 23:59 sergiodj+buildbot
  2016-12-10  9:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 23:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55af478400524cba7994e353fd9a98ef1543df2f ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 55af478400524cba7994e353fd9a98ef1543df2f

MIPS16/opcodes: Reformat raw EXTEND and undecoded output

Use a tab rather than a space to separate `extend' and its uninterpreted
argument output, like with regular instructions.  Separate hexadecimal
halves of undecoded extended instructions output with a space instead of
presenting them concatenated.

	opcodes/
	* mips-dis.c (print_insn_mips16): Use a tab rather than a space
	to separate `extend' and its uninterpreted argument output.
	Separate hexadecimal halves of undecoded extended instructions
	output.

	binutils/
	* testsuite/binutils-all/mips/mips16-extend-noinsn.d: New test.
	* testsuite/binutils-all/mips/mips16-extend-noinsn.s: New test
	source.
	* testsuite/binutils-all/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16: Remove unused `>' operand code
@ 2016-12-10  1:40 sergiodj+buildbot
  2016-12-10 10:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-10  1:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64c111834081a117f902cffc15dadbc535f1c65e ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 64c111834081a117f902cffc15dadbc535f1c65e

MIPS16: Remove unused `>' operand code

This code has never been used throughout the repository history, and
likely not before either, as due to the assymetry of MIPS16 instruction
set encoding there are no 32-bit shift operations having their immediate
shift count placed in the position of the usual `rx' instruction field.

	gas/
	* config/tc-mips.c (mips16_macro_build) <'>'>: Remove case.

	include/
	* opcode/mips.h: Remove references to `>' operand code.

	opcodes/
	* mips16-opc.c (decode_mips16_operand) <'>'>: Remove cases.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Handle memory error in print_insn_rl78_common
@ 2016-12-12  9:28 sergiodj+buildbot
  2016-12-12 10:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-12  9:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3a0b8f7ddb874283879baaf8af6d11094f4c4999 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 3a0b8f7ddb874283879baaf8af6d11094f4c4999

Handle memory error in print_insn_rl78_common

Nowadays, memory error in rl78 disassembly is not handled, so if I
start a fresh GDB, and disassemble,

(gdb) set architecture rl78
The target architecture is assumed to be rl78
(gdb) disassemble 0x0,+4
Dump of assembler code from 0x0 to 0x4:
   0x00000000:	nop
   0x00000001:	nop
   0x00000002:	nop
   0x00000003:	nop

the output is wrong.  This patch adds code to call dis->memory_error_func
on memory error, and longjmp to print_insn_rl78_common.  With this
patch applied,

(gdb) set architecture rl78
The target architecture is assumed to be rl78
(gdb) disassemble 0,+4
Dump of assembler code from 0x0 to 0x4:
   0x00000000:	Cannot access memory at address 0x0

opcodes:

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

	* rl78-dis.c: Include <setjmp.h>.
	(struct private): New.
	(rl78_get_byte): Check return value of read_memory_func, and
	call memory_error_func and OPCODES_SIGLONGJMP on error.
	(print_insn_rl78_common): Call OPCODES_SIGJMP.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [Binutils][AARCH64]Remove Cn register for coprocessor CRn, CRm field
@ 2016-12-13 17:55 sergiodj+buildbot
  2016-12-13 20:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-13 17:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6a51754740513db76fdee3aa153cdd51e87a24a ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: a6a51754740513db76fdee3aa153cdd51e87a24a

[Binutils][AARCH64]Remove Cn register for coprocessor CRn, CRm field

The internal CN register representation for coprocessor fields used in aarch64
sys, sysl instructions are removed in this patch.

After the change, those fields are represented as immediate. Related checks are
added as well.

opcodes/

	* aarch64-opc.c (aarch64_opnd_qualifiers): New CR value range
	qualifier.
	(operand_general_constraint_met_p): Remove case for CP_REG.
	(aarch64_print_operand): Print CRn, CRm operand using imm field.
	* aarch64-tbl.h (QL_SYS): Use CR qualifier.
	(QL_SYSL): Likewise.
	(aarch64_opcode_table): Change CRn, CRm operand class and type.
	* aarch64-opc-2.c : Regenerate.
	* aarch64-asm-2.c : Likewise.
	* aarch64-dis-2.c : Likewise.

include/

	* opcode/aarch64.h (aarch64_operand_class): Remove
	AARCH64_OPND_CLASS_CP_REG.
	(enum aarch64_opnd): Change AARCH64_OPND_Cn to AARCH64_OPND_CRn,
	AARCH64_OPND_Cm to AARCH64_OPND_CRm.
	(aarch64_opnd_qualifier): Define AARCH64_OPND_QLF_CR qualifier.

gas/

	* config/tc-aarch64.c (AARCH64_REG_TYPES): Remove CN register.
	(get_reg_expected_msg): Remove CN register case.
	(parse_operands): rewrite parser for CRn, CRm operand.
	(reg_names): Remove CN register.
	* testsuite/gas/aarch64/diagnostic.s: Add a new test case.
	* testsuite/gas/aarch64/diagnostic.l: Adjust error message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ld: aarch64: fix TLS relaxation where TCB_SIZE is used
@ 2016-12-14  6:47 sergiodj+buildbot
  2016-12-14  7:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-14  6:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6650f7bd18f8161b9f666d3e65a6346e23a9d85f ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: 6650f7bd18f8161b9f666d3e65a6346e23a9d85f

ld: aarch64: fix TLS relaxation where TCB_SIZE is used

TCB_SIZE is 2*sizeof(void *), which is 0x10 for lp64, and 0x8 for
ilp32. During relaxation, ld goes to do a replace:
bl   __tls_get_addr => add R0, R0, TCB_SIZE

But actual implementation is:
bfd_putl32 (0x91004000, contents + rel->r_offset + 4);

Which is equivalent of add x0, x0, 0x10. This is wrong for ilp32.

The possible fix for it is:
bfd_putl32 (0x91000000 | (TCB_SIZE<<10), contents + rel->r_offset + 4);

But ilp32 also needs w-registers, so it's simpler to put proper
instruction in #if/#else condition.

THere are 2 such relaxations in elfNN_aarch64_tls_relax(), and so 2 new
tests added for ilp32 mode to test it.

Yury


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd: aarch64: fix word and arrdess size declaration in ilp32 mode
@ 2016-12-14  7:22 sergiodj+buildbot
  2016-12-14  8:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-14  7:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a02c3512655cc2c8ad68e4b656959b7d284acc7d ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: a02c3512655cc2c8ad68e4b656959b7d284acc7d

bfd: aarch64: fix word and arrdess size declaration in ilp32 mode


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Revert "ld: aarch64: fix TLS relaxation where TCB_SIZE is used"
@ 2016-12-14  8:12 sergiodj+buildbot
  2016-12-14  9:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-14  8:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98fa61facff8fb041205950d642f5403372bfd96 ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: 98fa61facff8fb041205950d642f5403372bfd96

Revert "ld: aarch64: fix TLS relaxation where TCB_SIZE is used"

This reverts commit 6650f7bd18f8161b9f666d3e65a6346e23a9d85f.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Revert "bfd: aarch64: fix word and arrdess size declaration in ilp32 mode"
@ 2016-12-14  8:26 sergiodj+buildbot
  2016-12-14 12:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-14  8:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7acd51d6971f12b832cd7281f669a7ae7feddf45 ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: 7acd51d6971f12b832cd7281f669a7ae7feddf45

Revert "bfd: aarch64: fix word and arrdess size declaration in ilp32 mode"

This reverts commit a02c3512655cc2c8ad68e4b656959b7d284acc7d.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] ld: aarch64: fix TLS relaxation where TCB_SIZE is used
@ 2016-12-14  9:08 sergiodj+buildbot
  2016-12-14 14:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-14  9:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1fc2d7ee590f3bc87ee79c36e7216b0b6bb054b ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: c1fc2d7ee590f3bc87ee79c36e7216b0b6bb054b

ld: aarch64: fix TLS relaxation where TCB_SIZE is used

TCB_SIZE is 2*sizeof(void *), which is 0x10 for lp64, and 0x8 for
ilp32. During relaxation, ld goes to do a replace:
bl   __tls_get_addr => add R0, R0, TCB_SIZE

But actual implementation is:
bfd_putl32 (0x91004000, contents + rel->r_offset + 4);

Which is equivalent of add x0, x0, 0x10. This is wrong for ilp32.

The possible fix for it is:
bfd_putl32 (0x91000000 | (TCB_SIZE<<10), contents + rel->r_offset + 4);

But ilp32 also needs w-registers, so it's simpler to put proper
instruction in #if/#else condition.

There are 2 such relaxations in elfNN_aarch64_tls_relax(), and so 2 new
tests added for ilp32 mode to test it.

Yury

	* bfd/elfnn-aarch64.c: fix TLS relaxations for ilp32 where
	TCB_SIZE is used.
	* ld/testsuite/ld-aarch64/aarch64-elf.exp: Add tests for the case.
	* ld/testsuite/ld-aarch64/tls-relax-ld-le-small-ilp32.d: New file.
	* ld/testsuite/ld-aarch64/tls-relax-ld-le-tiny-ilp32.d: New file.

Signed-off-by: Yury Norov <ynorov@caviumnetworks.com>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/opcodes: Reorder ELF file header flag handling in disassembler
@ 2016-12-15  0:13 sergiodj+buildbot
  2016-12-15  4:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-15  0:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8184783a4069e04deb2e43b4ad0d66d80f1ad2df ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 8184783a4069e04deb2e43b4ad0d66d80f1ad2df

MIPS/opcodes: Reorder ELF file header flag handling in disassembler

Move ELF file header flag interpretation code, used to set disassembler
options, beyond architecture setup.  No functional change as the effects
of both code sections are disjoint from each other, but this provides
for a further expansion of ELF file header flag interpretation.

	opcodes/
	* mips-dis.c (set_default_mips_dis_options): Reorder ELF file
	header flag interpretation code.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/opcodes: Only call `bfd_mips_elf_get_abiflags' if BFD64
@ 2016-12-19 11:44 sergiodj+buildbot
  2016-12-19 13:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-19 11:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4df995c77118d07c12fb260dbba0ca2b281324f1 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4df995c77118d07c12fb260dbba0ca2b281324f1

MIPS/opcodes: Only call `bfd_mips_elf_get_abiflags' if BFD64

Complement commit 5e7fc731f80e ("MIPS/opcodes: Also set disassembler's
ASE flags from ELF structures") and fix an `--enable-targets=all' GDB
build regression on 32-bit hosts where the MIPS target is a secondary:

../opcodes/libopcodes.a(mips-dis.o): In function `set_default_mips_dis_options':
mips-dis.c:(.text+0x906): undefined reference to `bfd_mips_elf_get_abiflags'
collect2: error: ld returned 1 exit status
make[2]: *** [gdb] Error 1

by avoiding making a call to the `bfd_mips_elf_get_abiflags' function,
which is not available, because there is no MIPS/ELF BFD included in
32-bit BFD builds.  This call is only made from a conditional code block
guarded by a check against `bfd_target_elf_flavour', which is dead in
such a configuration, however cannot be optimized away by the compiler.
Also some other MIPS BFDs may be available, such as a.out, ECOFF or PE,
so the disassembler has to remain functional.

	opcodes/
	* mips-dis.c (set_default_mips_dis_options) [BFD64]: Only call
	`bfd_mips_elf_get_abiflags' here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add opcodes RISC-V dependencies
@ 2016-12-20  2:03 sergiodj+buildbot
  2016-12-20  7:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20  2:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd1d944e2321de26f75a21f42750dd38ed964714 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: dd1d944e2321de26f75a21f42750dd38ed964714

Add opcodes RISC-V dependencies

	* Makefile.am (TARGET_LIBOPCODES_CFILES): Add riscv files.
	* Makefile.in: Regenerate.
	* po/POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix an integer overflow in RISC-V relocation handling
@ 2016-12-20  2:03 sergiodj+buildbot
  2016-12-20 14:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20  2:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d61f7949f77796ee407466f3ca7f42dcde9251b ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 1d61f7949f77796ee407466f3ca7f42dcde9251b

Fix an integer overflow in RISC-V relocation handling

	* elfnn-riscv.c (bfd_riscv_get_max_alignment): Return bfd_vma
	instead of unsigned int.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix disassembly of RISC-V CSR instructions under -Mno-aliases
@ 2016-12-20  2:06 sergiodj+buildbot
  2016-12-20 18:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04386d9ed5f068b74757bfac01670576e4e59b8a ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 04386d9ed5f068b74757bfac01670576e4e59b8a

Fix disassembly of RISC-V CSR instructions under -Mno-aliases

This fixes https://github.com/riscv/riscv-binutils-gdb/issues/36.

	* riscv-opc.c (riscv_opcodes): Mark the rd* and csr* aliases as
	INSN_ALIAS.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Correct assembler mnemonic for RISC-V aqrl AMOs
@ 2016-12-20  2:06 sergiodj+buildbot
  2016-12-20 20:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20  2:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e67a37820a2838cdbd50f3f697ddc929443ceaa ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 3e67a37820a2838cdbd50f3f697ddc929443ceaa

Correct assembler mnemonic for RISC-V aqrl AMOs

sc is a misnomer, because they aren't inherently sc.

	* riscv-opc.c (riscv_opcodes): Rename the "*.sc" instructions to
	"*.aqrl".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Improve RISC-V LD error message
@ 2016-12-20  2:12 sergiodj+buildbot
  2016-12-20 13:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20  2:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96b0927de3ebdb302d8d571c43da3db5ec23847e ***

Author: Palmer Dabbelt <palmer@dabbelt.com>
Branch: master
Commit: 96b0927de3ebdb302d8d571c43da3db5ec23847e

Improve RISC-V LD error message

I recently ran into this error message and found it's not helpful: it
just tells me some temporary file can't be linked.  This slightly
improved one at least tells me it's because of an elf32/elf64 conflict.

	* elfnn-riscv.c (_bfd_riscv_elf_merge_private_bfd_data): Improve
	error message when linking elf32 and elf64.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Set emacs default mode for the GDB directory to C++
@ 2016-12-20 16:15 sergiodj+buildbot
  2016-12-21  2:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 16:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff71884063d048e8f8c03de27d2bac343df4f77a ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: ff71884063d048e8f8c03de27d2bac343df4f77a

Set emacs default mode for the GDB directory to C++

Since GDB has switched to C++ but the file names are still .c emacs does
not load the proper mode when opening files in the gdb directory.

This patch fixes that by enabling c++ mode.

This patch also fixes indentation tweaks as discussed in this thread:
https://sourceware.org/ml/gdb-patches/2016-12/msg00074.html

Indent with gdb-code-style.el included and the .dir-locals.el is as such:

namespace TestNameSpace {

class test
{
public:
  test test() {}

  int m_a;
};

struct teststruct
{
  int a;
}
}

gdb/ChangeLog:

	* .dir-locals.el: Set c++ mode for the directory and set indent
	properly.
	* gdb-code-style.el: Set c-set-offset 'innamespace as a safe value
	to be used in .dir-locals.el.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains
@ 2016-12-20 17:00 sergiodj+buildbot
  2016-12-21  4:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 17:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2693a26216c329bd7ec2aae7743409f572de4fa5 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2693a26216c329bd7ec2aae7743409f572de4fa5

Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains

Nowadays, GDB propagates C++ exceptions across readline using
setjmp/longjmp 89525768cd08 ("Propagate GDB/C++ exceptions across
readline using sj/lj-based TRY/CATCH") because DWARF-based unwinding
can't cross C functions compiled without -fexceptions (see details
from the commit above).

Unfortunately, toolchains that use SjLj-based C++ exceptions got
broken with that fix, because _Unwind_SjLj_Unregister, which is put at
the exit of a function, is not executed due to the longjmp added by
that commit.

 (gdb) [New Thread 2936.0xb80]
 kill

 Thread 1 received signal SIGSEGV, Segmentation fault.
 0x03ff662b in ?? ()
 top?bt 15
 #0  0x03ff662b in ?? ()
 #1  0x00526b92 in stdin_event_handler (error=0, client_data=0x172ed8)
    at ../../binutils-gdb/gdb/event-top.c:555
 #2  0x00525a94 in handle_file_event (ready_mask=<optimized out>,
    file_ptr=0x3ff5cb8) at ../../binutils-gdb/gdb/event-loop.c:733
 #3  gdb_wait_for_event (block=block@entry=1)
    at ../../binutils-gdb/gdb/event-loop.c:884
 #4  0x00525bfb in gdb_do_one_event ()
    at ../../binutils-gdb/gdb/event-loop.c:347
 #5  0x00525ce5 in start_event_loop ()
    at ../../binutils-gdb/gdb/event-loop.c:371
 #6  0x0051fada in captured_command_loop (data=0x0)
    at ../../binutils-gdb/gdb/main.c:324
 #7  0x0051cf5d in catch_errors (
    func=func@entry=0x51fab0 <captured_command_loop(void*)>,
    func_args=func_args@entry=0x0,
    errstring=errstring@entry=0x7922bf <VEC_interp_factory_p_quick_push(VEC_inte rp_factory_p*, interp_factory*, char const*, unsigned int)::__PRETTY_FUNCTION__+351> "", mask=mask@entry=RETURN_MASK_ALL)
    at ../../binutils-gdb/gdb/exceptions.c:236
 #8  0x00520f0c in captured_main (data=0x328feb4)
    at ../../binutils-gdb/gdb/main.c:1149
 #9  gdb_main (args=args@entry=0x328feb4) at ../../binutils-gdb/gdb/main.c:1159
 #10 0x0071e400 in main (argc=1, argv=0x171220)
    at ../../binutils-gdb/gdb/gdb.c:32

Fix this by making the functions involved in setjmp/longjmp as
noexcept, so that the compiler knows it doesn't need to emit the
_Unwind_SjLj_Register / _Unwind_SjLj_Unregister calls for C++
exceptions.

Tested on x86_64 Fedora 23 with:
 - GCC 5.3.1 w/ DWARF-based exceptions.
 - GCC 7 built with --enable-sjlj-exceptions.

gdb/ChangeLog:
2016-12-20  Pedro Alves  <palves@redhat.com>
	    Yao Qi  <yao.qi@linaro.org>

	PR gdb/20977
	* event-top.c (gdb_rl_callback_read_char_wrapper_noexcept): New
	noexcept function, factored out from ...
	(gdb_rl_callback_read_char_wrapper): ... this.
	(gdb_rl_callback_handler): Mark noexcept.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16/opcodes: Correct I64/SDRASP opcode's ISA membership
@ 2016-12-20 23:46 sergiodj+buildbot
  2016-12-21  0:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-20 23:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c97dda72b905d5ba9b82004bf4e57dd4cf343147 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: c97dda72b905d5ba9b82004bf4e57dd4cf343147

MIPS16/opcodes: Correct I64/SDRASP opcode's ISA membership

Limit the `SD ra, offset(sp)' instruction (I64/SDRASP major/minor
opcode) to the MIPS III rather than MIPS I ISA.  This is a 64-bit
instruction requiring a 64-bit ISA.  This bug has been there since
forever.

	opcodes/
	* mips16-opc.c (mips16_opcodes): Set membership to I3 rather
	than I1 for the SP-relative "sd"/$ra entry (SDRASP minor
	opcode).

	gas/
	* testsuite/gas/mips/mips16-sdrasp.d: New test.
	* testsuite/gas/mips/mips16-sdrasp.l: New stderr output.
	* testsuite/gas/mips/mips16-sdrasp.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Remove high bit set characters
@ 2016-12-21 11:51 sergiodj+buildbot
  2016-12-21 12:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-21 11:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e25adb3956f880efc28bfebabe79be7338b413f ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 4e25adb3956f880efc28bfebabe79be7338b413f

Remove high bit set characters

gas/
	* doc/c-lm32.texi: Fix chars with high bit set.
	* testsuite/gas/bfin/vector2.s: Likewise.
gold/
	* arm.cc: Fix comment chars with high bit set.
include/
	* coff/pe.h: Fix comment chars with high bit set.
	* opcode/xgate.h: Likewise.
ld/
	* testsuite/ld-scripts/sysroot-prefix.exp: Fix chars with high bit set.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Avoid creating symbol table entries for registers
@ 2016-12-21 14:46 sergiodj+buildbot
  2016-12-21 15:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-21 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58a6d3c9d8d4d4be8f1dfc1a49fed264dceddaba ***

Author: Andrew Waterman <andrew@sifive.com>
Branch: master
Commit: 58a6d3c9d8d4d4be8f1dfc1a49fed264dceddaba

Avoid creating symbol table entries for registers

Instructions like "jal t0, foo" were erroneously creating symbol table
entries for t0 as well as foo, which causes linking problems.  Fix by
reordering instruction alternatives so that t0 is first attempted to
be parsed as a register, rather than as a symbol.

	* riscv-opc.c (riscv_opcodes): Reorder jal and call entries.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix bugs with float compare and Inf operands.
@ 2016-12-21 21:24 sergiodj+buildbot
  2016-12-21 23:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-21 21:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87903eafb083abbf330c22fbf941fcbad700c098 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: 87903eafb083abbf330c22fbf941fcbad700c098

Fix bugs with float compare and Inf operands.

	sim/aarch64/
	* simulator.c (set_flags_for_float_compare): Add code to handle Inf.
	Add comment to document NaN issue.
	(set_flags_for_double_compare): Likewise.

	sim/testsuite/sim/aarch64/
	* fcmp.s: New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Class-ify ui_out
@ 2016-12-22 22:01 sergiodj+buildbot
  2016-12-22 23:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-22 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 112e8700a6fd2fed65ca70132c9cbed4132e8bd4 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 112e8700a6fd2fed65ca70132c9cbed4132e8bd4

Class-ify ui_out

This patch finalizes the C++ conversion of the ui-out subsystem, by
turning the ui_out and ui_out_impl structures into a single class
hierarchy.  ui_out functions are turned into virtual methods of that new
class, so as a result there are a lot of call sites to update.

In the previous version of the patchset, there were separate ui_out and
ui_out_impl classes, but it wasn't really useful and added boilerplate.
In this version there is simply an ui_out base class that is
extended for CLI, TUI and MI.

It's a bit hard to maintain a ChangeLog for such a big patch, I did my
best but I'm sure there are some missing or outdated info in there...

gdb/ChangeLog:

    * ui-out.h (ui_out_begin, ui_out_end, ui_out_table_header,
    ui_out_table_body,  ui_out_field_int, ui_out_field_fmt_int,
    ui_out_field_core_addr, ui_out_field_string, ui_out_field_stream,
    ui_out_field_fmt, ui_out_field_skip, ui_out_spaces, ui_out_text,
    ui_out_message, ui_out_wrap_hint, ui_out_flush, ui_out_test_flags,
    ui_out_query_field, ui_out_is_mi_like_p, ui_out_redirect):
    Remove, replace with a method in class ui_out.
    (table_begin_ftype): Remove, replace with pure virtual method in
    class ui_out.
    (table_body_ftype): Likewise.
    (table_end_ftype): Likewise.
    (table_header_ftype): Likewise.
    (ui_out_begin_ftype): Likewise.
    (ui_out_end_ftype): Likewise.
    (field_int_ftype): Likewise.
    (field_skip_ftype): Likewise.
    (field_string_ftype): Likewise.
    (field_fmt_ftype): Likewise.
    (spaces_ftype): Likewise.
    (text_ftype): Likewise.
    (message_ftype): Likewise.
    (wrap_hint_ftype): Likewise.
    (flush_ftype): Likewise.
    (redirect_ftype): Likewise.
    (data_destroy_ftype): Likewise.
    (struct ui_out_impl): Remove, replace with class ui_out.
    (ui_out_new): Remove.
    (class ui_out): New class.
    * ui-out.c (struct ui_out): Remove, replaced with class ui_out.
    (current_level): Remove, replace with ui_out method.
    (push_level): Likewise.
    (pop_level): Likewise.
    (uo_table_begin, uo_table_body, uo_table_end, uo_table_header,
    uo_begin, uo_end, uo_field_int, uo_field_skip, uo_field_fmt,
    uo_spaces, uo_text, uo_message, uo_wrap_hint, uo_flush,
    uo_redirect, uo_field_string): Remove.
    (ui_out_table_begin): Replace with ...
    (ui_out::table_begin): ... this.
    (ui_out_table_body): Replace with ...
    (ui_out::table_body): ... this.
    (ui_out_table_end): Replace with ...
    (ui_out::table_end): ... this.
    (ui_out_table_header): Replace with ...
    (ui_out::table_header): ... this.
    (ui_out_begin): Replace with ...
    (ui_out::begin): ... this.
    (ui_out_end): Replace with ...
    (ui_out::end): ... this.
    (ui_out_field_int): Replace with ...
    (ui_out::field_int): ... this.
    (ui_out_field_fmt_int): Replace with ...
    (ui_out::field_fmt_int): ... this.
    (ui_out_field_core_addr): Replace with ...
    (ui_out::field_core_addr): ... this.
    (ui_out_field_stream): Replace with ...
    (ui_out::field_stream): ... this.
    (ui_out_field_skip): Replace with ...
    (ui_out::field_skip): ... this.
    (ui_out_field_string): Replace with ...
    (ui_out::field_string): ... this.
    (ui_out_field_fmt): Replace with ...
    (ui_out::field_fmt): ... this.
    (ui_out_spaces): Replace with ...
    (ui_out::spaces): ... this.
    (ui_out_text): Replace with ...
    (ui_out::text): ... this.
    (ui_out_message): Replace with ...
    (ui_out::message): ... this.
    (ui_out_wrap_hint): Replace with ...
    (ui_out::wrap_hint): ... this.
    (ui_out_flush): Replace with ...
    (ui_out::flush): ... this.
    (ui_out_redirect): Replace with ...
    (ui_out::redirect): ... this.
    (ui_out_test_flags): Replace with ...
    (ui_out::test_flags): ... this.
    (ui_out_is_mi_like_p): Replace with ...
    (ui_out::is_mi_like_p): ... this.
    (verify_field): Replace with ...
    (ui_out::verify_field): ... this.
    (ui_out_query_field): Replace with ...
    (ui_out::query_table_field): ... this.
    (ui_out_data): Remove.
    (ui_out_new): Remove, replace with ...
    (ui_out::ui_out): ... this constructor.
    (do_cleanup_table_end, make_cleanup_ui_out_tuple_begin_end,
    do_cleanup_end, make_cleanup_ui_out_tuple_begin_end,
    make_cleanup_ui_out_list_begin_end): Update fallouts of struct
    ui_out -> class ui_out change.
    * cli-out.c (cli_out_data): Remove.
    (cli_uiout_dtor): Remove.
    (cli_table_begin): Replace with ...
    (cli_ui_out::do_table_begin): ... this new method.
    (cli_table_body): Replace with ...
    (cli_ui_out::do_table_body): ... this new method.
    (cli_table_end): Replace with ...
    (cli_ui_out::do_table_end): ... this new method.
    (cli_table_header): Replace with ...
    (cli_ui_out::do_table_header): ... this new method.
    (cli_begin): Replace with ...
    (cli_ui_out::do_begin): ... this new method.
    (cli_end): Replace with ...
    (cli_ui_out::do_end): ... this new method.
    (cli_field_int): Replace with ...
    (cli_ui_out::do_field_int): ... this new method.
    (cli_field_skip): Replace with ...
    (cli_ui_out::do_field_skip): ... this new method.
    (cli_field_string): Replace with ...
    (cli_ui_out::do_field_string): ... this new method.
    (cli_field_fmt): Replace with ...
    (cli_ui_out::do_field_fmt): ... this new method.
    (cli_spaces): Replace with ...
    (cli_ui_out::do_spaces): ... this new method.
    (cli_text): Replace with ...
    (cli_ui_out::do_text): ... this new method.
    (cli_message): Replace with ...
    (cli_ui_out::do_message): ... this new method.
    (cli_wrap_hint): Replace with ...
    (cli_ui_out::do_wrap_hint): ... this new method.
    (cli_flush): Replace with ...
    (cli_ui_out::do_flush): ... this new method.
    (cli_redirect): Replace with ...
    (cli_ui_out::do_redirect): ... this new method.
    (out_field_fmt): Replace with ...
    (cli_ui_out::out_field_fmt): ... this new method.
    (field_separator): Replace with ...
    (cli_ui_out::field_separator): ... this new method.
    (cli_out_set_stream): Replace with ...
    (cli_ui_out::set_stream): ... this new method.
    (cli_ui_out_impl): Remove.
    (cli_out_data_ctor): Remove.
    (cli_ui_out_impl::cli_ui_out_impl): New constructor.
    (cli_ui_out_impl::~cli_ui_out_impl): New destructor.
    (cli_out_new): Change return type to cli_ui_out *, instantiate a
    cli_ui_out.
    * cli-out.h (cli_ui_out_data): Remove, replace with class
    cli_ui_out.
    (class cli_ui_out): New class.
    (cli_ui_out_impl): Remove.
    (cli_out_data_ctor): Remove.
    (cli_out_new): Change return type to cli_ui_out*.
    (cli_out_set_stream): Remove.
    * cli/cli-interp.c (struct cli_interp) <cli_uiout>: Change type
    to cli_ui_out*.
    (cli_interpreter_resume): Adapt.
    (cli_interpreter_exec): Adapt.
    * mi/mi-out.c (mi_ui_out_data, mi_out_data): Remove.
    (mi_ui_out_impl): Remove.
    (mi_table_begin): Replace with ...
    (mi_ui_out::do_table_begin): ... this.
    (mi_table_body): Replace with ...
    (mi_ui_out::do_table_body): ... this.
    (mi_table_end): Replace with ...
    (mi_ui_out::do_table_end): ... this.
    (mi_table_header): Replace with ...
    (mi_ui_out::do_table_header): ... this.
    (mi_begin): Replace with ...
    (mi_ui_out::do_begin): ... this.
    (mi_end): Replace with ...
    (mi_ui_out::do_end): ... this.
    (mi_field_int): Replace with ...
    (mi_ui_out::do_field_int): ... this.
    (mi_field_skip): Replace with ...
    (mi_ui_out::do_field_skip): ... this.
    (mi_field_string): Replace with ...
    (mi_ui_out::do_field_string): ... this.
    (mi_field_fmt): Replace with ...
    (mi_ui_out::do_field_fmt): ... this.
    (mi_spaces): Replace with ...
    (mi_ui_out::do_spaces): ... this.
    (mi_text): Replace with ...
    (mi_ui_out::do_text): ... this.
    (mi_message): Replace with ...
    (mi_ui_out::do_message): ... this.
    (mi_wrap_hint): Replace with ...
    (mi_ui_out::do_wrap_hint): ... this.
    (mi_flush): Replace with ...
    (mi_ui_out::do_flush): ... this.
    (mi_redirect): Replace with ...
    (mi_ui_out::do_redirect):
    (field_separator): Replace with ...
    (mi_ui_out::field_separator):
    (mi_open): Replace with ...
    (mi_ui_out::open): ... this.
    (mi_close): Replace with ...
    (mi_ui_out::close): ... this.
    (mi_out_rewind): Replace with ...
    (mi_ui_out::rewind): ... this.
    (mi_out_put): Replace with ...
    (mi_ui_out::put): ... this.
    (mi_version): Replace with ...
    (mi_ui_out::version): ... this.
    (mi_out_data_ctor): Replace with ...
    (mi_ui_out::mi_ui_out): ... this.
    (mi_out_data_dtor): Replace with ...
    (mi_ui_out::~mi_ui_out): ... this.
    (mi_out_new): Change return type to mi_ui_out*, instantiate
    an mi_ui_out object.
    (as_mi_ui_out): New function.
    (mi_version): Update fallouts of struct ui_out to class ui_out
    transition.
    (mi_out_put): Likewise.
    (mi_out_rewind): Likewise.
    * mi/mi-out.h (mi_out_new): Change return type to mi_ui_out*.
    * tui/tui-out.c (tui_ui_out_data, tui_out_data, tui_ui_out_impl):
    Remove.
    (tui_field_int): Replace with ...
    (tui_ui_out::do_field_int): ... this.
    (tui_field_string): Replace with ...
    (tui_ui_out::do_field_string): ... this.
    (tui_field_fmt): Replace with ...
    (tui_ui_out::do_field_fmt): ... this.
    (tui_text): Replace with ...
    (tui_ui_out::do_text): ... this.
    (tui_out_new): Change return type to tui_ui_out*, instantiate
    tui_ui_out object.
    (tui_ui_out::tui_ui_out): New.
    * tui/tui-out.h: New file.
    * tui/tui.h (tui_out_new): Move declaration to tui/tui-out.h.
    * tui/tui-io.c: Include tui/tui-out.h.
    (tui_old_uiout): Change type to cli_ui_out*.
    (tui_setup_io): Use dynamic_cast.
    * tui/tui-io.h (tui_old_uiout): Change type to cli_ui_out*.
    * tui/tui-interp.c (tui_resume): Adapt.
    * ada-lang.c (print_it_exception): Update fallouts of struct
    ui_out to class ui_out transition.
    (print_one_exception): Likewise.
    (print_mention_exception): Likewise.
    * ada-tasks.c (print_ada_task_info): Likewise.
    (info_task): Likewise.
    (task_command): Likewise.
    * auto-load.c (print_script): Likewise.
    (auto_load_info_scripts): Likewise.
    (info_auto_load_cmd): Likewise.
    * break-catch-sig.c (signal_catchpoint_print_one): Likewise.
    * break-catch-syscall.c (print_it_catch_syscall): Likewise.
    (print_one_catch_syscall): Likewise.
    * break-catch-throw.c (print_it_exception_catchpoint): Likewise.
    (print_one_exception_catchpoint): Likewise.
    (print_one_detail_exception_catchpoint): Likewise.
    (print_mention_exception_catchpoint): Likewise.
    * breakpoint.c (maybe_print_thread_hit_breakpoint): Likewise.
    (print_solib_event): Likewise.
    (watchpoint_check): Likewise.
    (wrap_indent_at_field): Likewise.
    (print_breakpoint_location): Likewise.
    (output_thread_groups): Likewise.
    (print_one_breakpoint_location): Likewise.
    (breakpoint_1): Likewise.
    (default_collect_info): Likewise.
    (watchpoints_info): Likewise.
    (print_it_catch_fork): Likewise.
    (print_one_catch_fork): Likewise.
    (print_it_catch_vfork): Likewise.
    (print_one_catch_vfork): Likewise.
    (print_it_catch_solib): Likewise.
    (print_one_catch_solib): Likewise.
    (print_it_catch_exec): Likewise.
    (print_one_catch_exec): Likewise.
    (mention): Likewise.
    (print_it_ranged_breakpoint): Likewise.
    (print_one_ranged_breakpoint): Likewise.
    (print_one_detail_ranged_breakpoint): Likewise.
    (print_mention_ranged_breakpoint): Likewise.
    (print_it_watchpoint): Likewise.
    (print_mention_watchpoint): Likewise.
    (print_it_masked_watchpoint): Likewise.
    (print_one_detail_masked_watchpoint): Likewise.
    (print_mention_masked_watchpoint): Likewise.
    (bkpt_print_it): Likewise.
    (tracepoint_print_one_detail): Likewise.
    (tracepoint_print_mention): Likewise.
    (update_static_tracepoint): Likewise.
    (tracepoints_info): Likewise.
    (save_breakpoints): Likewise.
    * cli/cli-cmds.c (complete_command): Likewise.
    * cli/cli-logging.c (set_logging_redirect): Likewise.
    (pop_output_files): Likewise.
    (handle_redirections): Likewise.
    * cli/cli-script.c (print_command_lines): Likewise.
    * cli/cli-setshow.c (do_show_command): Likewise.
    (cmd_show_list): Likewise.
    * cp-abi.c (list_cp_abis): Likewise.
    (show_cp_abi_cmd): Likewise.
    * darwin-nat-info.c (darwin_debug_regions_recurse): Likewise.
    * disasm.c (gdb_pretty_print_insn): Likewise.
    (do_mixed_source_and_assembly_deprecated): Likewise.
    (do_mixed_source_and_assembly): Likewise.
    * gdb_bfd.c (print_one_bfd): Likewise.
    (maintenance_info_bfds): Likewise.
    * guile/scm-breakpoint.c (gdbscm_breakpoint_commands): Likewise.
    * guile/scm-ports.c (ioscm_with_output_to_port_worker): Likewise.
    * i386-linux-tdep.c (i386_linux_handle_segmentation_fault): Likewise.
    * i386-tdep.c (i386_mpx_print_bounds): Likewise.
    * infcmd.c (run_command_1): Likewise.
    (print_return_value_1): Likewise.
    * inferior.c (print_selected_inferior): Likewise.
    (print_inferior): Likewise.
    * infrun.c (print_end_stepping_range_reason): Likewise.
    (print_signal_exited_reason): Likewise.
    (print_exited_reason): Likewise.
    (print_signal_received_reason): Likewise.
    (print_no_history_reason): Likewise.
    * interps.c (interp_set): Likewise.
    * linespec.c (decode_line_full): Likewise.
    * linux-thread-db.c (info_auto_load_libthread_db): Likewise.
    * mi/mi-cmd-env.c (mi_cmd_env_pwd): Likewise.
    (mi_cmd_env_path): Likewise.
    (mi_cmd_env_dir): Likewise.
    (mi_cmd_inferior_tty_show): Likewise.
    * mi/mi-cmd-file.c (mi_cmd_file_list_exec_source_file): Likewise.
    (print_partial_file_name): Likewise.
    (mi_cmd_file_list_exec_source_files): Likewise.
    * mi/mi-cmd-info.c (mi_cmd_info_ada_exceptions): Likewise.
    (mi_cmd_info_gdb_mi_command): Likewise.
    * mi/mi-cmd-stack.c (mi_cmd_stack_info_depth): Likewise.
    (mi_cmd_stack_list_args): Likewise.
    (list_arg_or_local): Likewise.
    * mi/mi-cmd-var.c (print_varobj): Likewise.
    (mi_cmd_var_create): Likewise.
    (mi_cmd_var_delete): Likewise.
    (mi_cmd_var_set_format): Likewise.
    (mi_cmd_var_show_format): Likewise.
    (mi_cmd_var_info_num_children): Likewise.
    (mi_cmd_var_list_children): Likewise.
    (mi_cmd_var_info_type): Likewise.
    (mi_cmd_var_info_path_expression): Likewise.
    (mi_cmd_var_info_expression): Likewise.
    (mi_cmd_var_show_attributes): Likewise.
    (mi_cmd_var_evaluate_expression): Likewise.
    (mi_cmd_var_assign): Likewise.
    (varobj_update_one): Likewise.
    * mi/mi-interp.c (as_mi_interp): Likewise.
    (mi_on_normal_stop_1): Likewise.
    (mi_tsv_modified): Likewise.
    (mi_breakpoint_created): Likewise.
    (mi_breakpoint_modified): Likewise.
    (mi_solib_loaded): Likewise.
    (mi_solib_unloaded): Likewise.
    (mi_command_param_changed): Likewise.
    (mi_memory_changed): Likewise.
    (mi_user_selected_context_changed): Likewise.
    * mi/mi-main.c (print_one_inferior): Likewise.
    (output_cores): Likewise.
    (list_available_thread_groups): Likewise.
    (mi_cmd_data_list_register_names): Likewise.
    (mi_cmd_data_list_changed_registers): Likewise.
    (output_register): Likewise.
    (mi_cmd_data_evaluate_expression): Likewise.
    (mi_cmd_data_read_memory): Likewise.
    (mi_cmd_data_read_memory_bytes): Likewise.
    (mi_cmd_list_features): Likewise.
    (mi_cmd_list_target_features): Likewise.
    (mi_cmd_add_inferior): Likewise.
    (mi_execute_command): Likewise.
    (mi_load_progress): Likewise.
    (print_variable_or_computed): Likewise.
    (mi_cmd_trace_frame_collected): Likewise.
    * mi/mi-symbol-cmds.c (mi_cmd_symbol_list_lines): Likewise.
    * osdata.c (info_osdata_command): Likewise.
    * probe.c (gen_ui_out_table_header_info): Likewise.
    (print_ui_out_not_applicables): Likewise.
    (print_ui_out_info): Likewise.
    (info_probes_for_ops): Likewise.
    (enable_probes_command): Likewise.
    (disable_probes_command): Likewise.
    * progspace.c (print_program_space): Likewise.
    * python/py-breakpoint.c (bppy_get_commands): Likewise.
    * python/py-framefilter.c (py_print_type): Likewise.
    (py_print_value): Likewise.
    (py_print_single_arg): Likewise.
    (enumerate_args): Likewise.
    (enumerate_locals): Likewise.
    (py_print_args): Likewise.
    (py_print_frame): Likewise.
    * record-btrace.c (btrace_ui_out_decode_error): Likewise.
    (btrace_call_history_insn_range): Likewise.
    (btrace_call_history_src_line): Likewise.
    (btrace_call_history): Likewise.
    * remote.c (show_remote_cmd): Likewise.
    * skip.c (skip_info): Likewise.
    * solib.c (info_sharedlibrary_command): Likewise.
    * source.c (print_source_lines_base): Likewise.
    * spu-tdep.c (info_spu_event_command): Likewise.
    (info_spu_signal_command): Likewise.
    (info_spu_mailbox_list): Likewise.
    (info_spu_dma_cmdlist): Likewise.
    (info_spu_dma_command): Likewise.
    (info_spu_proxydma_command): Likewise.
    * stack.c (print_stack_frame): Likewise.
    (print_frame_arg): Likewise.
    (read_frame_arg): Likewise.
    (print_frame_args): Likewise.
    (print_frame_info): Likewise.
    (print_frame): Likewise.
    * symfile.c (load_progress): Likewise.
    (generic_load): Likewise.
    (print_transfer_performance): Likewise.
    * thread.c (do_captured_list_thread_ids): Likewise.
    (print_thread_info_1): Likewise.
    (restore_selected_frame): Likewise.
    (do_captured_thread_select): Likewise.
    (print_selected_thread_frame): Likewise.
    * top.c (execute_command_to_string): Likewise.
    * tracepoint.c (tvariables_info_1): Likewise.
    (trace_status_mi): Likewise.
    (tfind_1): Likewise.
    (print_one_static_tracepoint_marker): Likewise.
    (info_static_tracepoint_markers_command): Likewise.
    * utils.c (do_ui_out_redirect_pop): Likewise.
    (fputs_maybe_filtered): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] infrun.c (set_step_over_info): Add comment.
@ 2016-12-23  1:16 sergiodj+buildbot
  2016-12-23  3:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23  1:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce0db13751aed2782c417bc4cf715313f9273e94 ***

Author: Doug Evans <xdje42@gmail.com>
Branch: master
Commit: ce0db13751aed2782c417bc4cf715313f9273e94

infrun.c (set_step_over_info): Add comment.

gdb/ChangeLog:

	* infrun.c (set_step_over_info): Add comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Regenerate pot files.
@ 2016-12-23  9:35 sergiodj+buildbot
  2016-12-23  9:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23  9:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0e7a9d436cb3c97ae89c9b0d2750a006746b233 ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: e0e7a9d436cb3c97ae89c9b0d2750a006746b233

Regenerate pot files.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Bump version to 2.28.51
@ 2016-12-23  9:49 sergiodj+buildbot
  2016-12-23 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23  9:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99b5dbf2e78a63ba4be067bfabb3bec1a6406f1c ***

Author: Tristan Gingold <gingold@adacore.com>
Branch: master
Commit: 99b5dbf2e78a63ba4be067bfabb3bec1a6406f1c

Bump version to 2.28.51

bfd/
2016-12-23  Tristan Gingold  <gingold@adacore.com>

	* version.m4: Bump version to 2.28.51
	* configure: Regenerate.

binutils/
2016-12-23  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

gas/
2016-12-23  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

gprof/
2016-12-23  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

ld/
2016-12-23  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.

opcodes/
2016-12-23  Tristan Gingold  <gingold@adacore.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Updated email address.
@ 2016-12-23 12:50 sergiodj+buildbot
  2016-12-23 13:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6096dda15babc5307b1a0e9624d4e0028fd429e1 ***

Author: Bernhard Heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 6096dda15babc5307b1a0e9624d4e0028fd429e1

Updated email address.

2016-12-23  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* MAINTAINERS (Write After Approval): Updated email address.

Change-Id: I46b81392c2bd4b04e8e2aea2bb4bef2d0b509d24


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] hppa-linux-gnu-ranlib: libcpp.a: File format not recognized
@ 2016-12-23 14:34 sergiodj+buildbot
  2016-12-23 15:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 865422fafaf387745b2979d47b6f448d28e0edb8 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 865422fafaf387745b2979d47b6f448d28e0edb8

hppa-linux-gnu-ranlib: libcpp.a: File format not recognized

This stops an --enable-targets selection affecting the main target in
regards to forcing 64-bit archives.  It also means mips64 and s390x
will revert to binutils-2.25 and binutils-2.26 behaviour of not
forcing 64-bit archives at least in the common case when plugins were
enabled.

	PR binutils/20464
	PR binutils/14625
	* configure.ac: Revert 2016-05-25 configure change setting
	want_64_bit_archive for mips64 and s390x.  Revise USE_64_BIT_ARCHIVE
	description.
	* configure: Regenerate.
	* config.in: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix incorrect reference to source files
@ 2016-12-23 18:37 sergiodj+buildbot
  2016-12-23 19:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 18:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7dc53023ec5d000b3b8d287720ed8d04d91e02ec ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 7dc53023ec5d000b3b8d287720ed8d04d91e02ec

Fix incorrect reference to source files

gdb/gdbserver/ChangeLog:

2016-12-23  Luis Machado  <lgustavo@codesourcery.com>

	* win32-i386-low.c: Fix incorrect reference to a couple source files.
	* nto-x86-low.c: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix more cases of improper test names
@ 2016-12-23 20:03 sergiodj+buildbot
  2016-12-23 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b362f04b2a56d446b024027963be52d61f939cb ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 5b362f04b2a56d446b024027963be52d61f939cb

Fix more cases of improper test names

I noticed more occurrences of improper test names. The rather mechanical,
tedious and large patch below addresses, hopefully, most of the leftover cases.

As usual, another pair of eyes is welcome to check if missed something or did
an invalid substitution.

This patch also fixes the prepare_for_testing calls to pass proper test names.

gdb/testsuite/ChangeLog:

2016-12-23  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names for the following files:

	* gdb.ada/exec_changed.exp
	* gdb.ada/info_types.exp
	* gdb.arch/aarch64-atomic-inst.exp
	* gdb.arch/aarch64-fp.exp
	* gdb.arch/altivec-abi.exp
	* gdb.arch/altivec-regs.exp
	* gdb.arch/amd64-byte.exp
	* gdb.arch/amd64-disp-step.exp
	* gdb.arch/amd64-dword.exp
	* gdb.arch/amd64-entry-value-inline.exp
	* gdb.arch/amd64-entry-value-param.exp
	* gdb.arch/amd64-entry-value-paramref.exp
	* gdb.arch/amd64-entry-value.exp
	* gdb.arch/amd64-i386-address.exp
	* gdb.arch/amd64-invalid-stack-middle.exp
	* gdb.arch/amd64-invalid-stack-top.exp
	* gdb.arch/amd64-optimout-repeat.exp
	* gdb.arch/amd64-prologue-skip.exp
	* gdb.arch/amd64-prologue-xmm.exp
	* gdb.arch/amd64-stap-special-operands.exp
	* gdb.arch/amd64-stap-wrong-subexp.exp
	* gdb.arch/amd64-tailcall-cxx.exp
	* gdb.arch/amd64-tailcall-noret.exp
	* gdb.arch/amd64-tailcall-ret.exp
	* gdb.arch/amd64-tailcall-self.exp
	* gdb.arch/amd64-word.exp
	* gdb.arch/arm-bl-branch-dest.exp
	* gdb.arch/arm-disp-step.exp
	* gdb.arch/arm-neon.exp
	* gdb.arch/arm-single-step-kernel-helper.exp
	* gdb.arch/avr-flash-qualifier.exp
	* gdb.arch/disp-step-insn-reloc.exp
	* gdb.arch/e500-abi.exp
	* gdb.arch/e500-regs.exp
	* gdb.arch/ftrace-insn-reloc.exp
	* gdb.arch/i386-avx512.exp
	* gdb.arch/i386-bp_permanent.exp
	* gdb.arch/i386-byte.exp
	* gdb.arch/i386-cfi-notcurrent.exp
	* gdb.arch/i386-disp-step.exp
	* gdb.arch/i386-dr3-watch.exp
	* gdb.arch/i386-float.exp
	* gdb.arch/i386-gnu-cfi.exp
	* gdb.arch/i386-mpx-map.exp
	* gdb.arch/i386-mpx-sigsegv.exp
	* gdb.arch/i386-mpx-simple_segv.exp
	* gdb.arch/i386-mpx.exp
	* gdb.arch/i386-permbkpt.exp
	* gdb.arch/i386-prologue.exp
	* gdb.arch/i386-signal.exp
	* gdb.arch/i386-size-overlap.exp
	* gdb.arch/i386-unwind.exp
	* gdb.arch/i386-word.exp
	* gdb.arch/mips-fcr.exp
	* gdb.arch/powerpc-d128-regs.exp
	* gdb.arch/powerpc-stackless.exp
	* gdb.arch/ppc64-atomic-inst.exp
	* gdb.arch/s390-stackless.exp
	* gdb.arch/s390-tdbregs.exp
	* gdb.arch/s390-vregs.exp
	* gdb.arch/sparc-sysstep.exp
	* gdb.arch/thumb-bx-pc.exp
	* gdb.arch/thumb-singlestep.exp
	* gdb.arch/thumb2-it.exp
	* gdb.arch/vsx-regs.exp
	* gdb.asm/asm-source.exp
	* gdb.base/a2-run.exp
	* gdb.base/advance.exp
	* gdb.base/all-bin.exp
	* gdb.base/anon.exp
	* gdb.base/args.exp
	* gdb.base/arithmet.exp
	* gdb.base/async-shell.exp
	* gdb.base/async.exp
	* gdb.base/attach-pie-noexec.exp
	* gdb.base/attach-twice.exp
	* gdb.base/auto-load.exp
	* gdb.base/bang.exp
	* gdb.base/bitfields.exp
	* gdb.base/break-always.exp
	* gdb.base/break-caller-line.exp
	* gdb.base/break-entry.exp
	* gdb.base/break-inline.exp
	* gdb.base/break-on-linker-gcd-function.exp
	* gdb.base/break-probes.exp
	* gdb.base/break.exp
	* gdb.base/breakpoint-shadow.exp
	* gdb.base/call-ar-st.exp
	* gdb.base/call-sc.exp
	* gdb.base/call-signal-resume.exp
	* gdb.base/call-strs.exp
	* gdb.base/callfuncs.exp
	* gdb.base/catch-fork-static.exp
	* gdb.base/catch-gdb-caused-signals.exp
	* gdb.base/catch-load.exp
	* gdb.base/catch-signal-fork.exp
	* gdb.base/catch-signal.exp
	* gdb.base/catch-syscall.exp
	* gdb.base/charset.exp
	* gdb.base/checkpoint.exp
	* gdb.base/chng-syms.exp
	* gdb.base/code-expr.exp
	* gdb.base/code_elim.exp
	* gdb.base/commands.exp
	* gdb.base/completion.exp
	* gdb.base/complex.exp
	* gdb.base/cond-expr.exp
	* gdb.base/condbreak.exp
	* gdb.base/consecutive.exp
	* gdb.base/continue-all-already-running.exp
	* gdb.base/coredump-filter.exp
	* gdb.base/corefile.exp
	* gdb.base/dbx.exp
	* gdb.base/debug-expr.exp
	* gdb.base/define.exp
	* gdb.base/del.exp
	* gdb.base/disabled-location.exp
	* gdb.base/disasm-end-cu.exp
	* gdb.base/disasm-optim.exp
	* gdb.base/display.exp
	* gdb.base/duplicate-bp.exp
	* gdb.base/ena-dis-br.exp
	* gdb.base/ending-run.exp
	* gdb.base/enumval.exp
	* gdb.base/environ.exp
	* gdb.base/eu-strip-infcall.exp
	* gdb.base/eval-avoid-side-effects.exp
	* gdb.base/eval-skip.exp
	* gdb.base/exitsignal.exp
	* gdb.base/expand-psymtabs.exp
	* gdb.base/filesym.exp
	* gdb.base/find-unmapped.exp
	* gdb.base/finish.exp
	* gdb.base/float.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/foll-exec.exp
	* gdb.base/foll-fork.exp
	* gdb.base/fortran-sym-case.exp
	* gdb.base/freebpcmd.exp
	* gdb.base/func-ptr.exp
	* gdb.base/func-ptrs.exp
	* gdb.base/funcargs.exp
	* gdb.base/gcore-buffer-overflow.exp
	* gdb.base/gcore-relro-pie.exp
	* gdb.base/gcore-relro.exp
	* gdb.base/gcore.exp
	* gdb.base/gdb1090.exp
	* gdb.base/gdb11530.exp
	* gdb.base/gdb11531.exp
	* gdb.base/gdb1821.exp
	* gdb.base/gdbindex-stabs.exp
	* gdb.base/gdbvars.exp
	* gdb.base/hbreak.exp
	* gdb.base/hbreak2.exp
	* gdb.base/included.exp
	* gdb.base/infcall-input.exp
	* gdb.base/inferior-died.exp
	* gdb.base/infnan.exp
	* gdb.base/info-macros.exp
	* gdb.base/info-os.exp
	* gdb.base/info-proc.exp
	* gdb.base/info-shared.exp
	* gdb.base/info-target.exp
	* gdb.base/infoline.exp
	* gdb.base/interp.exp
	* gdb.base/interrupt.exp
	* gdb.base/jit-reader.exp
	* gdb.base/jit-simple.exp
	* gdb.base/kill-after-signal.exp
	* gdb.base/kill-detach-inferiors-cmd.exp
	* gdb.base/label.exp
	* gdb.base/langs.exp
	* gdb.base/ldbl_e308.exp
	* gdb.base/line-symtabs.exp
	* gdb.base/linespecs.exp
	* gdb.base/list.exp
	* gdb.base/long_long.exp
	* gdb.base/longest-types.exp
	* gdb.base/maint.exp
	* gdb.base/max-value-size.exp
	* gdb.base/memattr.exp
	* gdb.base/mips_pro.exp
	* gdb.base/morestack.exp
	* gdb.base/moribund-step.exp
	* gdb.base/multi-forks.exp
	* gdb.base/nested-addr.exp
	* gdb.base/nextoverexit.exp
	* gdb.base/noreturn-finish.exp
	* gdb.base/noreturn-return.exp
	* gdb.base/nostdlib.exp
	* gdb.base/offsets.exp
	* gdb.base/opaque.exp
	* gdb.base/pc-fp.exp
	* gdb.base/permissions.exp
	* gdb.base/print-symbol-loading.exp
	* gdb.base/prologue-include.exp
	* gdb.base/psymtab.exp
	* gdb.base/ptype.exp
	* gdb.base/random-signal.exp
	* gdb.base/randomize.exp
	* gdb.base/range-stepping.exp
	* gdb.base/readline-ask.exp
	* gdb.base/recpar.exp
	* gdb.base/recurse.exp
	* gdb.base/relational.exp
	* gdb.base/restore.exp
	* gdb.base/return-nodebug.exp
	* gdb.base/return.exp
	* gdb.base/run-after-attach.exp
	* gdb.base/save-bp.exp
	* gdb.base/scope.exp
	* gdb.base/sect-cmd.exp
	* gdb.base/set-lang-auto.exp
	* gdb.base/set-noassign.exp
	* gdb.base/setvar.exp
	* gdb.base/sigall.exp
	* gdb.base/sigbpt.exp
	* gdb.base/siginfo-addr.exp
	* gdb.base/siginfo-infcall.exp
	* gdb.base/siginfo-obj.exp
	* gdb.base/siginfo.exp
	* gdb.base/signals-state-child.exp
	* gdb.base/signest.exp
	* gdb.base/sigstep.exp
	* gdb.base/sizeof.exp
	* gdb.base/skip.exp
	* gdb.base/solib-corrupted.exp
	* gdb.base/solib-nodir.exp
	* gdb.base/solib-search.exp
	* gdb.base/stack-checking.exp
	* gdb.base/stale-infcall.exp
	* gdb.base/stap-probe.exp
	* gdb.base/start.exp
	* gdb.base/step-break.exp
	* gdb.base/step-bt.exp
	* gdb.base/step-line.exp
	* gdb.base/step-over-exit.exp
	* gdb.base/step-over-syscall.exp
	* gdb.base/step-resume-infcall.exp
	* gdb.base/step-test.exp
	* gdb.base/store.exp
	* gdb.base/structs3.exp
	* gdb.base/sym-file.exp
	* gdb.base/symbol-without-target_section.exp
	* gdb.base/term.exp
	* gdb.base/testenv.exp
	* gdb.base/ui-redirect.exp
	* gdb.base/until.exp
	* gdb.base/unwindonsignal.exp
	* gdb.base/value-double-free.exp
	* gdb.base/vla-datatypes.exp
	* gdb.base/vla-ptr.exp
	* gdb.base/vla-sideeffect.exp
	* gdb.base/volatile.exp
	* gdb.base/watch-cond-infcall.exp
	* gdb.base/watch-cond.exp
	* gdb.base/watch-non-mem.exp
	* gdb.base/watch-read.exp
	* gdb.base/watch-vfork.exp
	* gdb.base/watchpoint-cond-gone.exp
	* gdb.base/watchpoint-delete.exp
	* gdb.base/watchpoint-hw-hit-once.exp
	* gdb.base/watchpoint-hw.exp
	* gdb.base/watchpoint-stops-at-right-insn.exp
	* gdb.base/watchpoints.exp
	* gdb.base/wchar.exp
	* gdb.base/whatis-exp.exp
	* gdb.btrace/buffer-size.exp
	* gdb.btrace/data.exp
	* gdb.btrace/delta.exp
	* gdb.btrace/dlopen.exp
	* gdb.btrace/enable.exp
	* gdb.btrace/exception.exp
	* gdb.btrace/function_call_history.exp
	* gdb.btrace/gcore.exp
	* gdb.btrace/instruction_history.exp
	* gdb.btrace/nohist.exp
	* gdb.btrace/reconnect.exp
	* gdb.btrace/record_goto-step.exp
	* gdb.btrace/record_goto.exp
	* gdb.btrace/rn-dl-bind.exp
	* gdb.btrace/segv.exp
	* gdb.btrace/step.exp
	* gdb.btrace/stepi.exp
	* gdb.btrace/tailcall-only.exp
	* gdb.btrace/tailcall.exp
	* gdb.btrace/tsx.exp
	* gdb.btrace/unknown_functions.exp
	* gdb.btrace/vdso.exp
	* gdb.compile/compile-ifunc.exp
	* gdb.compile/compile-ops.exp
	* gdb.compile/compile-print.exp
	* gdb.compile/compile-setjmp.exp
	* gdb.cp/abstract-origin.exp
	* gdb.cp/ambiguous.exp
	* gdb.cp/annota2.exp
	* gdb.cp/annota3.exp
	* gdb.cp/anon-ns.exp
	* gdb.cp/anon-struct.exp
	* gdb.cp/anon-union.exp
	* gdb.cp/arg-reference.exp
	* gdb.cp/baseenum.exp
	* gdb.cp/bool.exp
	* gdb.cp/breakpoint.exp
	* gdb.cp/bs15503.exp
	* gdb.cp/call-c.exp
	* gdb.cp/casts.exp
	* gdb.cp/chained-calls.exp
	* gdb.cp/class2.exp
	* gdb.cp/classes.exp
	* gdb.cp/cmpd-minsyms.exp
	* gdb.cp/converts.exp
	* gdb.cp/cp-relocate.exp
	* gdb.cp/cpcompletion.exp
	* gdb.cp/cpexprs.exp
	* gdb.cp/cplabel.exp
	* gdb.cp/cplusfuncs.exp
	* gdb.cp/cpsizeof.exp
	* gdb.cp/ctti.exp
	* gdb.cp/derivation.exp
	* gdb.cp/destrprint.exp
	* gdb.cp/dispcxx.exp
	* gdb.cp/enum-class.exp
	* gdb.cp/exception.exp
	* gdb.cp/exceptprint.exp
	* gdb.cp/expand-psymtabs-cxx.exp
	* gdb.cp/expand-sals.exp
	* gdb.cp/extern-c.exp
	* gdb.cp/filename.exp
	* gdb.cp/formatted-ref.exp
	* gdb.cp/fpointer.exp
	* gdb.cp/gdb1355.exp
	* gdb.cp/gdb2495.exp
	* gdb.cp/hang.exp
	* gdb.cp/impl-this.exp
	* gdb.cp/infcall-dlopen.exp
	* gdb.cp/inherit.exp
	* gdb.cp/iostream.exp
	* gdb.cp/koenig.exp
	* gdb.cp/local.exp
	* gdb.cp/m-data.exp
	* gdb.cp/m-static.exp
	* gdb.cp/mb-ctor.exp
	* gdb.cp/mb-inline.exp
	* gdb.cp/mb-templates.exp
	* gdb.cp/member-name.exp
	* gdb.cp/member-ptr.exp
	* gdb.cp/meth-typedefs.exp
	* gdb.cp/method.exp
	* gdb.cp/method2.exp
	* gdb.cp/minsym-fallback.exp
	* gdb.cp/misc.exp
	* gdb.cp/namelessclass.exp
	* gdb.cp/namespace-enum.exp
	* gdb.cp/namespace-nested-import.exp
	* gdb.cp/namespace.exp
	* gdb.cp/nextoverthrow.exp
	* gdb.cp/no-dmgl-verbose.exp
	* gdb.cp/non-trivial-retval.exp
	* gdb.cp/noparam.exp
	* gdb.cp/nsdecl.exp
	* gdb.cp/nsimport.exp
	* gdb.cp/nsnested.exp
	* gdb.cp/nsnoimports.exp
	* gdb.cp/nsrecurs.exp
	* gdb.cp/nsstress.exp
	* gdb.cp/nsusing.exp
	* gdb.cp/operator.exp
	* gdb.cp/oranking.exp
	* gdb.cp/overload-const.exp
	* gdb.cp/overload.exp
	* gdb.cp/ovldbreak.exp
	* gdb.cp/ovsrch.exp
	* gdb.cp/paren-type.exp
	* gdb.cp/parse-lang.exp
	* gdb.cp/pass-by-ref.exp
	* gdb.cp/pr-1023.exp
	* gdb.cp/pr-1210.exp
	* gdb.cp/pr-574.exp
	* gdb.cp/pr10687.exp
	* gdb.cp/pr12028.exp
	* gdb.cp/pr17132.exp
	* gdb.cp/pr17494.exp
	* gdb.cp/pr9067.exp
	* gdb.cp/pr9167.exp
	* gdb.cp/pr9631.exp
	* gdb.cp/printmethod.exp
	* gdb.cp/psmang.exp
	* gdb.cp/psymtab-parameter.exp
	* gdb.cp/ptype-cv-cp.exp
	* gdb.cp/ptype-flags.exp
	* gdb.cp/re-set-overloaded.exp
	* gdb.cp/ref-types.exp
	* gdb.cp/rtti.exp
	* gdb.cp/scope-err.exp
	* gdb.cp/shadow.exp
	* gdb.cp/smartp.exp
	* gdb.cp/static-method.exp
	* gdb.cp/static-print-quit.exp
	* gdb.cp/temargs.exp
	* gdb.cp/templates.exp
	* gdb.cp/try_catch.exp
	* gdb.cp/typedef-operator.exp
	* gdb.cp/typeid.exp
	* gdb.cp/userdef.exp
	* gdb.cp/using-crash.exp
	* gdb.cp/var-tag.exp
	* gdb.cp/virtbase.exp
	* gdb.cp/virtfunc.exp
	* gdb.cp/virtfunc2.exp
	* gdb.cp/vla-cxx.exp
	* gdb.disasm/t01_mov.exp
	* gdb.disasm/t02_mova.exp
	* gdb.disasm/t03_add.exp
	* gdb.disasm/t04_sub.exp
	* gdb.disasm/t05_cmp.exp
	* gdb.disasm/t06_ari2.exp
	* gdb.disasm/t07_ari3.exp
	* gdb.disasm/t08_or.exp
	* gdb.disasm/t09_xor.exp
	* gdb.disasm/t10_and.exp
	* gdb.disasm/t11_logs.exp
	* gdb.disasm/t12_bit.exp
	* gdb.disasm/t13_otr.exp
	* gdb.dlang/circular.exp
	* gdb.dwarf2/arr-stride.exp
	* gdb.dwarf2/arr-subrange.exp
	* gdb.dwarf2/atomic-type.exp
	* gdb.dwarf2/bad-regnum.exp
	* gdb.dwarf2/bitfield-parent-optimized-out.exp
	* gdb.dwarf2/callframecfa.exp
	* gdb.dwarf2/clztest.exp
	* gdb.dwarf2/corrupt.exp
	* gdb.dwarf2/data-loc.exp
	* gdb.dwarf2/dup-psym.exp
	* gdb.dwarf2/dw2-anon-mptr.exp
	* gdb.dwarf2/dw2-anonymous-func.exp
	* gdb.dwarf2/dw2-bad-mips-linkage-name.exp
	* gdb.dwarf2/dw2-bad-unresolved.exp
	* gdb.dwarf2/dw2-basic.exp
	* gdb.dwarf2/dw2-canonicalize-type.exp
	* gdb.dwarf2/dw2-case-insensitive.exp
	* gdb.dwarf2/dw2-common-block.exp
	* gdb.dwarf2/dw2-compdir-oldgcc.exp
	* gdb.dwarf2/dw2-compressed.exp
	* gdb.dwarf2/dw2-const.exp
	* gdb.dwarf2/dw2-cp-infcall-ref-static.exp
	* gdb.dwarf2/dw2-cu-size.exp
	* gdb.dwarf2/dw2-dup-frame.exp
	* gdb.dwarf2/dw2-entry-value.exp
	* gdb.dwarf2/dw2-icycle.exp
	* gdb.dwarf2/dw2-ifort-parameter.exp
	* gdb.dwarf2/dw2-inline-break.exp
	* gdb.dwarf2/dw2-inline-param.exp
	* gdb.dwarf2/dw2-intercu.exp
	* gdb.dwarf2/dw2-intermix.exp
	* gdb.dwarf2/dw2-lexical-block-bare.exp
	* gdb.dwarf2/dw2-linkage-name-trust.exp
	* gdb.dwarf2/dw2-minsym-in-cu.exp
	* gdb.dwarf2/dw2-noloc.exp
	* gdb.dwarf2/dw2-op-call.exp
	* gdb.dwarf2/dw2-op-out-param.exp
	* gdb.dwarf2/dw2-opt-structptr.exp
	* gdb.dwarf2/dw2-param-error.exp
	* gdb.dwarf2/dw2-producer.exp
	* gdb.dwarf2/dw2-ranges-base.exp
	* gdb.dwarf2/dw2-ref-missing-frame.exp
	* gdb.dwarf2/dw2-reg-undefined.exp
	* gdb.dwarf2/dw2-regno-invalid.exp
	* gdb.dwarf2/dw2-restore.exp
	* gdb.dwarf2/dw2-restrict.exp
	* gdb.dwarf2/dw2-single-line-discriminators.exp
	* gdb.dwarf2/dw2-strp.exp
	* gdb.dwarf2/dw2-undefined-ret-addr.exp
	* gdb.dwarf2/dw2-unresolved.exp
	* gdb.dwarf2/dw2-var-zero-addr.exp
	* gdb.dwarf2/dw4-sig-types.exp
	* gdb.dwarf2/dwz.exp
	* gdb.dwarf2/dynarr-ptr.exp
	* gdb.dwarf2/enum-type.exp
	* gdb.dwarf2/gdb-index.exp
	* gdb.dwarf2/implptr-64bit.exp
	* gdb.dwarf2/implptr-optimized-out.exp
	* gdb.dwarf2/implptr.exp
	* gdb.dwarf2/implref-array.exp
	* gdb.dwarf2/implref-const.exp
	* gdb.dwarf2/implref-global.exp
	* gdb.dwarf2/implref-struct.exp
	* gdb.dwarf2/mac-fileno.exp
	* gdb.dwarf2/main-subprogram.exp
	* gdb.dwarf2/member-ptr-forwardref.exp
	* gdb.dwarf2/method-ptr.exp
	* gdb.dwarf2/missing-sig-type.exp
	* gdb.dwarf2/nonvar-access.exp
	* gdb.dwarf2/opaque-type-lookup.exp
	* gdb.dwarf2/pieces-optimized-out.exp
	* gdb.dwarf2/pieces.exp
	* gdb.dwarf2/pr10770.exp
	* gdb.dwarf2/pr13961.exp
	* gdb.dwarf2/staticvirtual.exp
	* gdb.dwarf2/subrange.exp
	* gdb.dwarf2/symtab-producer.exp
	* gdb.dwarf2/trace-crash.exp
	* gdb.dwarf2/typeddwarf.exp
	* gdb.dwarf2/valop.exp
	* gdb.dwarf2/watch-notconst.exp
	* gdb.fortran/array-element.exp
	* gdb.fortran/charset.exp
	* gdb.fortran/common-block.exp
	* gdb.fortran/complex.exp
	* gdb.fortran/derived-type-function.exp
	* gdb.fortran/derived-type.exp
	* gdb.fortran/logical.exp
	* gdb.fortran/module.exp
	* gdb.fortran/multi-dim.exp
	* gdb.fortran/nested-funcs.exp
	* gdb.fortran/print-formatted.exp
	* gdb.fortran/subarray.exp
	* gdb.fortran/vla-alloc-assoc.exp
	* gdb.fortran/vla-datatypes.exp
	* gdb.fortran/vla-history.exp
	* gdb.fortran/vla-ptr-info.exp
	* gdb.fortran/vla-ptype-sub.exp
	* gdb.fortran/vla-ptype.exp
	* gdb.fortran/vla-sizeof.exp
	* gdb.fortran/vla-type.exp
	* gdb.fortran/vla-value-sub-arbitrary.exp
	* gdb.fortran/vla-value-sub-finish.exp
	* gdb.fortran/vla-value-sub.exp
	* gdb.fortran/vla-value.exp
	* gdb.fortran/whatis_type.exp
	* gdb.go/chan.exp
	* gdb.go/handcall.exp
	* gdb.go/hello.exp
	* gdb.go/integers.exp
	* gdb.go/methods.exp
	* gdb.go/package.exp
	* gdb.go/strings.exp
	* gdb.go/types.exp
	* gdb.go/unsafe.exp
	* gdb.guile/scm-arch.exp
	* gdb.guile/scm-block.exp
	* gdb.guile/scm-breakpoint.exp
	* gdb.guile/scm-cmd.exp
	* gdb.guile/scm-disasm.exp
	* gdb.guile/scm-equal.exp
	* gdb.guile/scm-frame-args.exp
	* gdb.guile/scm-frame-inline.exp
	* gdb.guile/scm-frame.exp
	* gdb.guile/scm-iterator.exp
	* gdb.guile/scm-math.exp
	* gdb.guile/scm-objfile.exp
	* gdb.guile/scm-ports.exp
	* gdb.guile/scm-symbol.exp
	* gdb.guile/scm-symtab.exp
	* gdb.guile/scm-value-cc.exp
	* gdb.guile/types-module.exp
	* gdb.linespec/break-ask.exp
	* gdb.linespec/cpexplicit.exp
	* gdb.linespec/explicit.exp
	* gdb.linespec/keywords.exp
	* gdb.linespec/linespec.exp
	* gdb.linespec/ls-dollar.exp
	* gdb.linespec/ls-errs.exp
	* gdb.linespec/skip-two.exp
	* gdb.linespec/thread.exp
	* gdb.mi/mi-async.exp
	* gdb.mi/mi-basics.exp
	* gdb.mi/mi-break.exp
	* gdb.mi/mi-catch-load.exp
	* gdb.mi/mi-cli.exp
	* gdb.mi/mi-cmd-param-changed.exp
	* gdb.mi/mi-console.exp
	* gdb.mi/mi-detach.exp
	* gdb.mi/mi-disassemble.exp
	* gdb.mi/mi-eval.exp
	* gdb.mi/mi-file-transfer.exp
	* gdb.mi/mi-file.exp
	* gdb.mi/mi-fill-memory.exp
	* gdb.mi/mi-inheritance-syntax-error.exp
	* gdb.mi/mi-linespec-err-cp.exp
	* gdb.mi/mi-logging.exp
	* gdb.mi/mi-memory-changed.exp
	* gdb.mi/mi-read-memory.exp
	* gdb.mi/mi-record-changed.exp
	* gdb.mi/mi-reg-undefined.exp
	* gdb.mi/mi-regs.exp
	* gdb.mi/mi-return.exp
	* gdb.mi/mi-reverse.exp
	* gdb.mi/mi-simplerun.exp
	* gdb.mi/mi-solib.exp
	* gdb.mi/mi-stack.exp
	* gdb.mi/mi-stepi.exp
	* gdb.mi/mi-syn-frame.exp
	* gdb.mi/mi-until.exp
	* gdb.mi/mi-var-block.exp
	* gdb.mi/mi-var-child.exp
	* gdb.mi/mi-var-cmd.exp
	* gdb.mi/mi-var-cp.exp
	* gdb.mi/mi-var-display.exp
	* gdb.mi/mi-var-invalidate.exp
	* gdb.mi/mi-var-list-children-invalid-grandchild.exp
	* gdb.mi/mi-vla-fortran.exp
	* gdb.mi/mi-watch.exp
	* gdb.mi/mi2-var-child.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.modula2/unbounded-array.exp
	* gdb.multi/dummy-frame-restore.exp
	* gdb.multi/multi-arch-exec.exp
	* gdb.multi/multi-arch.exp
	* gdb.multi/tids.exp
	* gdb.multi/watchpoint-multi.exp
	* gdb.opencl/callfuncs.exp
	* gdb.opencl/convs_casts.exp
	* gdb.opencl/datatypes.exp
	* gdb.opencl/operators.exp
	* gdb.opencl/vec_comps.exp
	* gdb.opt/clobbered-registers-O2.exp
	* gdb.opt/inline-break.exp
	* gdb.opt/inline-bt.exp
	* gdb.opt/inline-cmds.exp
	* gdb.opt/inline-locals.exp
	* gdb.pascal/case-insensitive-symbols.exp
	* gdb.pascal/floats.exp
	* gdb.pascal/gdb11492.exp
	* gdb.python/lib-types.exp
	* gdb.python/py-arch.exp
	* gdb.python/py-as-string.exp
	* gdb.python/py-bad-printers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-breakpoint-create-fail.exp
	* gdb.python/py-breakpoint.exp
	* gdb.python/py-caller-is.exp
	* gdb.python/py-cmd.exp
	* gdb.python/py-explore-cc.exp
	* gdb.python/py-explore.exp
	* gdb.python/py-finish-breakpoint.exp
	* gdb.python/py-finish-breakpoint2.exp
	* gdb.python/py-frame-args.exp
	* gdb.python/py-frame-inline.exp
	* gdb.python/py-frame.exp
	* gdb.python/py-framefilter-mi.exp
	* gdb.python/py-infthread.exp
	* gdb.python/py-lazy-string.exp
	* gdb.python/py-linetable.exp
	* gdb.python/py-mi-events.exp
	* gdb.python/py-mi-objfile.exp
	* gdb.python/py-mi.exp
	* gdb.python/py-objfile.exp
	* gdb.python/py-pp-integral.exp
	* gdb.python/py-pp-maint.exp
	* gdb.python/py-pp-re-notag.exp
	* gdb.python/py-pp-registration.exp
	* gdb.python/py-recurse-unwind.exp
	* gdb.python/py-strfns.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-sync-interp.exp
	* gdb.python/py-typeprint.exp
	* gdb.python/py-unwind-maint.exp
	* gdb.python/py-unwind.exp
	* gdb.python/py-value-cc.exp
	* gdb.python/py-xmethods.exp
	* gdb.reverse/amd64-tailcall-reverse.exp
	* gdb.reverse/break-precsave.exp
	* gdb.reverse/break-reverse.exp
	* gdb.reverse/consecutive-precsave.exp
	* gdb.reverse/consecutive-reverse.exp
	* gdb.reverse/finish-precsave.exp
	* gdb.reverse/finish-reverse-bkpt.exp
	* gdb.reverse/finish-reverse.exp
	* gdb.reverse/fstatat-reverse.exp
	* gdb.reverse/getresuid-reverse.exp
	* gdb.reverse/i386-precsave.exp
	* gdb.reverse/i386-reverse.exp
	* gdb.reverse/i386-sse-reverse.exp
	* gdb.reverse/i387-env-reverse.exp
	* gdb.reverse/i387-stack-reverse.exp
	* gdb.reverse/insn-reverse.exp
	* gdb.reverse/machinestate-precsave.exp
	* gdb.reverse/machinestate.exp
	* gdb.reverse/next-reverse-bkpt-over-sr.exp
	* gdb.reverse/pipe-reverse.exp
	* gdb.reverse/readv-reverse.exp
	* gdb.reverse/recvmsg-reverse.exp
	* gdb.reverse/rerun-prec.exp
	* gdb.reverse/s390-mvcle.exp
	* gdb.reverse/step-precsave.exp
	* gdb.reverse/step-reverse.exp
	* gdb.reverse/time-reverse.exp
	* gdb.reverse/until-precsave.exp
	* gdb.reverse/until-reverse.exp
	* gdb.reverse/waitpid-reverse.exp
	* gdb.reverse/watch-precsave.exp
	* gdb.reverse/watch-reverse.exp
	* gdb.rust/generics.exp
	* gdb.rust/methods.exp
	* gdb.rust/modules.exp
	* gdb.rust/simple.exp
	* gdb.server/connect-with-no-symbol-file.exp
	* gdb.server/ext-attach.exp
	* gdb.server/ext-restart.exp
	* gdb.server/ext-wrapper.exp
	* gdb.server/file-transfer.exp
	* gdb.server/server-exec-info.exp
	* gdb.server/server-kill.exp
	* gdb.server/server-mon.exp
	* gdb.server/wrapper.exp
	* gdb.stabs/exclfwd.exp
	* gdb.stabs/gdb11479.exp
	* gdb.threads/clone-new-thread-event.exp
	* gdb.threads/corethreads.exp
	* gdb.threads/current-lwp-dead.exp
	* gdb.threads/dlopen-libpthread.exp
	* gdb.threads/gcore-thread.exp
	* gdb.threads/sigstep-threads.exp
	* gdb.threads/watchpoint-fork.exp
	* gdb.trace/actions-changed.exp
	* gdb.trace/backtrace.exp
	* gdb.trace/change-loc.exp
	* gdb.trace/circ.exp
	* gdb.trace/collection.exp
	* gdb.trace/disconnected-tracing.exp
	* gdb.trace/ftrace.exp
	* gdb.trace/mi-trace-frame-collected.exp
	* gdb.trace/mi-trace-unavailable.exp
	* gdb.trace/mi-traceframe-changed.exp
	* gdb.trace/mi-tsv-changed.exp
	* gdb.trace/no-attach-trace.exp
	* gdb.trace/passc-dyn.exp
	* gdb.trace/qtro.exp
	* gdb.trace/range-stepping.exp
	* gdb.trace/read-memory.exp
	* gdb.trace/save-trace.exp
	* gdb.trace/signal.exp
	* gdb.trace/status-stop.exp
	* gdb.trace/tfile.exp
	* gdb.trace/trace-break.exp
	* gdb.trace/trace-buffer-size.exp
	* gdb.trace/trace-condition.exp
	* gdb.trace/tracefile-pseudo-reg.exp
	* gdb.trace/tstatus.exp
	* gdb.trace/unavailable.exp
	* gdb.trace/while-dyn.exp
	* gdb.trace/while-stepping.exp


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD
@ 2016-12-23 21:30 sergiodj+buildbot
  2016-12-23 21:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 21:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e76c212e6311abaee4d02473473f7d6dcad972f ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 9e76c212e6311abaee4d02473473f7d6dcad972f

opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD

Fix a regression introduced with commit 5e7fc731f80e ("MIPS/opcodes:
Also set disassembler's ASE flags from ELF structures"), further updated
with commit 4df995c77118 ("MIPS/opcodes: Also set disassembler's ASE
flags from ELF structures"), and use autoconf to check for the presence
of `bfd_mips_elf_get_abiflags' in BFD.

	opcodes/
	* mips-dis.c (set_default_mips_dis_options): Use
	HAVE_BFD_MIPS_ELF_GET_ABIFLAGS rather than BFD64 to guard the
	call to `bfd_mips_elf_get_abiflags'.
	* configure.ac: Check for `bfd_mips_elf_get_abiflags' in BFD.
	* Makefile.am (CONFIG_STATUS_DEPENDENCIES): Add `libbfd.la'.
	* aclocal.m4: Regenerate.
	* configure: Regenerate.
	* config.in: Regenerate.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16: Simplify extended operand handling
@ 2016-12-23 22:22 sergiodj+buildbot
  2016-12-24  3:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 22:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdd152861ce75c36828904cf3d10f8ce14da6cf5 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: bdd152861ce75c36828904cf3d10f8ce14da6cf5

MIPS16: Simplify extended operand handling

Simplify extended operand handling and only specially process immediates
which require bit shuffling, using the generic operand insertion and
extraction handlers for the '<' (5-bit shift amount) operand code in
particular.  Require the least significant bit of all extended operand
forms to be (artificially) set to 0 for their special processing to
trigger.

	gas/
	* config/tc-mips.c (mips16_immed): Limit `mips16_immed_extend'
	use to operands whose LSB position is zero.

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Simplify processing of
	extended operands.
	* mips16-opc.c (decode_mips16_operand): Switch the extended
	form of the `<' operand type to LSB position 22.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS16: Remove "extended" BREAK/SDBBP handling
@ 2016-12-23 22:25 sergiodj+buildbot
  2016-12-23 23:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-23 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2805ed55456cea2694d31fc8627cca17120267b ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: b2805ed55456cea2694d31fc8627cca17120267b

MIPS16: Remove "extended" BREAK/SDBBP handling

Remove special casing for the `6' operand code used for the embedded
trap code of the BREAK and the SDBBP instructions to support supposedly
extended forms of these instructions.

According to all versions of the MIPS16 ASE specifications these
instructions are not extensible [1][2][3][4][5][7][8][10][11], and as
from revision 2.50 of the MIPS16e ASE specifications it has been further
clarified what was previously implied, that non-extesiable instructions
when preceded with an EXTEND prefix must cause a Reserved Instruction
exception [5][6][9][10].

Therefore supposedly extended BREAK and SDBBP instructions do not serve
their purpose anymore as they do not cause a Bp and a Debug exception
respectively and supporting these forms in disassembly only causes
confusion.

References:

[1] "Product Description, MIPS16 Application-Specific Extension",
    Version 1.3, MIPS Technologies, Inc., 970130, Table 3. "MIPS16
    Instruction Set Summary", p. 5

[2] same, Table 5 "RR Minor Opcodes (RR-type instructions)", p.10

[3] same, Table 18. "Extendable MIPS16 Instructions", p. 24

[4] "MIPS32 Architecture for Programmers, Volume IV-a: The MIPS16e
    Application-Specific Extension to the MIPS32 Architecture", MIPS
    Technologies, Inc., Document Number: MD00076, Revision 2.63, July
    16, 2013, Table 3.8 "MIPS16e Special Instructions", p. 38

[5] same, Section 3.11 "MIPS16e Extensible Instructions, p. 41

[6] same, Table 3.15 "MIPS16e Extensible Instructions", p. 41

[7] same, Table 3.24 "MIPS16e RR Encoding of the Funct Field", p. 49

[8] "MIPS64 Architecture for Programmers, Volume IV-a: The MIPS16e
    Application-Specific Extension to the MIPS64 Architecture", MIPS
    Technologies, Inc., Document Number: MD00077, Revision 2.60, June
    25, 2008, Table 1.8 "MIPS16e Special Instructions", p. 39

[9] same, Section 1.11 "MIPS16e Extensible Instructions", p. 42

[10] same, Table 1.15 "MIPS16e Extensible Instructions", pp. 42-43

[11] same, Table 1.24 "MIPS16e RR Encoding of the Funct Field", p. 50

	gas/
	* config/tc-mips.c (match_mips16_insn): Remove the `6' operand
	code special case and its associated comment.

	opcodes/
	* mips16-opc.c (decode_mips16_operand) <'6'>: Remove extended
	encoding support.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] MIPS/BFD: Remove EI_ABIVERSION 5 allocation for PT_GNU_STACK support
@ 2016-12-24  3:33 sergiodj+buildbot
  2016-12-24  7:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-24  3:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d4f40e041ce7c8c7c8e50f957e0440b64ab7e95 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 4d4f40e041ce7c8c7c8e50f957e0440b64ab7e95

MIPS/BFD: Remove EI_ABIVERSION 5 allocation for PT_GNU_STACK support

Revert commit 17733f5be961 ("Increment the ABIVERSION to 5 for MIPS
objects with non-executable stacks.") and remove EI_ABIVERSION 5
allocation for PT_GNU_STACK support, which has not made it to glibc
and will be reassigned.

	bfd/
	* bfd/elfxx-mips.c (_bfd_mips_post_process_headers): Revert
	2016-02-23 change and remove EI_ABIVERSION 5 support.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Put .dynbss and .rel.bss shortcuts in main elf hash table
@ 2016-12-26  6:26 sergiodj+buildbot
  2016-12-26  7:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-26  6:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d19e4fdb7c684329c8b1b72796a0071708dabc7 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9d19e4fdb7c684329c8b1b72796a0071708dabc7

Put .dynbss and .rel.bss shortcuts in main elf hash table

Also, create .rel{,a}.bss for PIEs on all targets, not just x86.

	* elf-bfd.h (struct elf_link_hash_table): Add sdynbss and srelbss.
	* elflink.c (_bfd_elf_create_dynamic_sections): Set them.  Create
	.rel.bss/.rela.bss for executables, both PIE and non-PIE.
	* elf32-arc.c (struct elf_arc_link_hash_table): Delete srelbss.
	Use ELF hash table var throughout.
	* elf32-arm.c (struct elf32_arm_link_hash_table): Delete sdynbss
	and srelbss.  Use ELF hash table vars throughout.
	* elf32-hppa.c (struct elf32_hppa_link_hash_table): Likewise.
	* elf32-i386.c (struct elf_i386_link_hash_table): Likewise.
	* elf32-metag.c (struct elf_metag_link_hash_table): Likewise.
	* elf32-microblaze.c (struct elf32_mb_link_hash_table): Likewise.
	* elf32-nios2.c (struct elf32_nios2_link_hash_table): Likewise.
	* elf32-or1k.c (struct elf_or1k_link_hash_table): Likewise.
	* elf32-ppc.c (struct ppc_elf_link_hash_table): Likewise.
	* elf32-s390.c (struct elf_s390_link_hash_table): Likewise.
	* elf32-tic6x.c (struct elf32_tic6x_link_hash_table): Likewise.
	* elf32-tilepro.c (struct tilepro_elf_link_hash_table): Likewise.
	* elf64-ppc.c (struct ppc_link_hash_table): Likewise.
	* elf64-s390.c (struct elf_s390_link_hash_table): Likewise.
	* elf64-x86-64.c (struct elf_x86_64_link_hash_table): Likewise.
	* elfnn-aarch64.c (struct elf_aarch64_link_hash_table): Likewise.
	* elfnn-riscv.c (struct riscv_elf_link_hash_table): Likewise.
	* elfxx-mips.c (struct mips_elf_link_hash_table): Likewise.
	* elfxx-sparc.h (struct _bfd_sparc_elf_link_hash_table): Likewise.
	* elfxx-sparc.c: Likewise.
	* elfxx-tilegx.c (struct tilegx_elf_link_hash_table): Likewise.

	* elf32-arc.c (arc_elf_create_dynamic_sections): Delete.
	(elf_backend_create_dynamic_sections): Use base ELF version.
	* elf32-microblaze.c (microblaze_elf_create_dynamic_sections): Delete.
	(elf_backend_create_dynamic_sections): Use base ELF version.
	* elf32-or1k.c (or1k_elf_create_dynamic_sections): Delete.
	(elf_backend_create_dynamic_sections): Use base ELF version.
	* elf32-s390.c (elf_s390_create_dynamic_sections): Delete.
	(elf_backend_create_dynamic_sections): Use base ELF version.
	* elf64-ppc.c (ppc64_elf_create_dynamic_sections): Delete.
	(elf_backend_create_dynamic_sections): Use base ELF version.
	* elf64-s390.c (elf_s390_create_dynamic_sections): Delete.
	(elf_backend_create_dynamic_sections): Use base ELF version.

	* elf32-tilepro.c (tilepro_elf_create_dynamic_sections): Remove
	extraneous tests.
	* elfnn-aarch64.c (elfNN_aarch64_create_dynamic_sections): Likewise.
	* elfxx-mips.c (_bfd_mips_elf_create_dynamic_sections): Likewise.
	* elfxx-tilegx.c (tilegx_elf_create_dynamic_sections): Likewise.

	* elf32-i386.c (elf_i386_create_dynamic_sections): Don't create
	".rel.bss" for executables.
	* elf64-x86-64.c (elf_x86_64_create_dynamic_sections): Don't create
	".rela.bss" for executables.
	* elf32-nios2.c (nios2_elf32_create_dynamic_sections): Don't
	ignore return status from _bfd_elf_create_dynamic_sections.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use dynrelro for symbols in relro sections too
@ 2016-12-28 12:52 sergiodj+buildbot
  2016-12-28 13:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-28 12:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9acc85a62eb76c270724bba15c889d2d05567b6a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 9acc85a62eb76c270724bba15c889d2d05567b6a

Use dynrelro for symbols in relro sections too

	PR ld/20995
bfd/
	* elflink.c (elf_link_add_object_symbols): Mark relro sections
	in dynamic objects SEC_READONLY.
ld/
	* testsuite/ld-elf/pr20995c.s: New test file.
	* testsuite/ld-elf/pr20995-2so.r: Likewise.
	* testsuite/ld-elf/elf.exp: Run it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] link_hash_copy_indirect and symbol flags
@ 2016-12-29 14:37 sergiodj+buildbot
  2016-12-29 16:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-29 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e81830c5c61a8665c098189d069cc68b0df113d3 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e81830c5c61a8665c098189d069cc68b0df113d3

link_hash_copy_indirect and symbol flags

A while ago HJ fixed PR ld/18720 with commit 6e33951ed, which, among
other things, modified _bfd_elf_link_hash_copy_indirect to not copy
ref_dynamic, ref_regular, ref_regular_nonweak, non_got_ref, needs_plt
and pointer_equality_needed when setting up an indirect non-versioned
symbol pointing to a non-default versioned symbol.  I didn't notice at
the time, but the pr18720 testcase fails on hppa-linux with
"internal error, aborting at binutils-gdb-2.28/bfd/elf32-hppa.c:3933
in elf32_hppa_relocate_section".

Now hppa-linux creates entries in the plt even for local functions, if
they are referenced using plabel (function pointer) relocations.   So
needs_plt is set for foo when processing pr18720a.o.  When the aliases
in pr28720b.o are processed, we get an indirection from foo to
foo@FOO, but don't copy needs_plt.  Since foo@FOO is the "real" symbol
that is used after that point, no plt entry is made for foo and we
bomb when relocating the plabel.

As shown by the hppa-linux scenario, needs_plt should be copied even
for non-default versioned symbols.  I believe all of the others ought
to be copied too, with the exception of ref_dynamic.  Not copying
ref_dynamic is right because if a shared lib references "foo" it
should not be satisfied by any non-default version "foo@FOO".

	* elflink.c (_bfd_elf_link_hash_copy_indirect): Only omit
	copying one flag, ref_dynamic, when versioned_hidden.
	* elf64-ppc.c (ppc64_elf_copy_indirect_symbol): Likewise.
	* elf32-hppa.c (elf32_hppa_copy_indirect_symbol): Use same
	logic for copying weakdef flags.  Copy plabel flag and merge
	tls_type.
	* elf32-i386.c (elf_i386_copy_indirect_symbol): Use same logic
	for copying weakdef flags.
	* elf32-ppc.c (ppc_elf_copy_indirect_symbol): Likewise.
	* elf32-s390.c (elf_s390_copy_indirect_symbol): Likewise.
	* elf32-sh.c (sh_elf_copy_indirect_symbol): Likewise.
	* elf64-s390.c (elf_s390_copy_indirect_symbol): Likewise.
	* elfnn-ia64.c (elfNN_ia64_hash_copy_indirect): Likewise.
	* elf64-x86-64.c (elf_x86_64_copy_indirect_symbol): Likewise.
	Simplify.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Return 'int' rather than 'unsigned short' in avrdis_opcode
@ 2016-12-29 16:30 sergiodj+buildbot
  2016-12-29 19:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-29 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a7e10188e3c08403fb00b728644d7a95092c732 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0a7e10188e3c08403fb00b728644d7a95092c732

Return 'int' rather than 'unsigned short' in avrdis_opcode

avrdis_opcode return type is unsigned short, but -1 at the end of
this function is returned.  Additionally, print_insn_avr doesn't
handle when -1 (in case of memory error) is returned from
avrdis_opcode.

This patch changes avrdis_opcode returning int indicating the error,
and adds a new argument for instruction we got on success.  The
opcode is 16-bit, so I change local variables type to uint16_t,
and include "bfd_stdint.h" as a result.  On memory error,
print_insn_avr returns -1, which is a common convention among most
of print_insn_$ARCH functions.

opcodes:

2016-12-29  Yao Qi  <yao.qi@linaro.org>

	* avr-dis.c: Include "bfd_stdint.h"
	(avrdis_opcode): Change return type to int, add argument
	insn.  Set *INSN on success.
	(print_insn_avr): Check return value of avrdis_opcode, and
	return -1 on error.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Import config.sub
@ 2016-12-31  2:44 sergiodj+buildbot
  2016-12-31  2:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-31  2:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f66c01be30edcfaedd11d475078f78e464ca4a0 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 3f66c01be30edcfaedd11d475078f78e464ca4a0

Import config.sub

	* config.sub: Import from upstream.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PRU BFD support
@ 2016-12-31  3:06 sergiodj+buildbot
  2016-12-31  4:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-31  3:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 889294f6ffb380eb37b1f1f3bd22807fa9204c14 ***

Author: Dimitar Dimitrov <dimitar@dinux.eu>
Branch: master
Commit: 889294f6ffb380eb37b1f1f3bd22807fa9204c14

PRU BFD support

include/
	* elf/common.h: Add PRU ELF.
	* elf/pru.h: New file.
	* opcode/pru.h: New file.
	* dis-asm.h (print_insn_pru): Declare.
bfd/
	* archures.c: Add bfd_arch_pru.
	* Makefile.am: Add PRU target.
	* config.bfd: Ditto.
	* configure.ac: Ditto.
	* elf-bfd.h (enum elf_target_id): Add PRU_ELF_DATA.
	* targets.c: Add pru_elf32_vec.
	* reloc.c: Add PRU relocations.
	* cpu-pru.c: New file.
	* elf32-pru.c: New file.
	* Makefile.in: Regenerate.
	* configure: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.
	* bfd-in2.h: Regenerate
	* libbfd.h: Regenerate.

Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix riscv breakage
@ 2016-12-31 13:03 sergiodj+buildbot
  2016-12-31 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2016-12-31 13:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae4c0df4b6a76db172cc4d4c3f34fdd8064c80ed ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: ae4c0df4b6a76db172cc4d4c3f34fdd8064c80ed

Fix riscv breakage

	* disassemble.c (disassembler): Add break accidentally removed
	by PRU patch.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] PR20989, sparc GOT sequence optimisation
@ 2017-01-04  0:08 sergiodj+buildbot
  2017-01-04  2:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b86074c4a84e32ca55a6c72c5fca45d97dc9374 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 5b86074c4a84e32ca55a6c72c5fca45d97dc9374

PR20989, sparc GOT sequence optimisation

	PR ld/20989
	* elfxx-sparc.c (gdop_relative_offset_ok): New function.
	(_bfd_sparc_elf_relocate_section): Use it to validate GOT
	indirect to GOT pointer relative code edit.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't make symbols dynamic other than undef weak
@ 2017-01-04  1:22 sergiodj+buildbot
  2017-01-04  4:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  1:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 595e0a47f57b414843261303b8aa5036fd1fa1e3 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 595e0a47f57b414843261303b8aa5036fd1fa1e3

Don't make symbols dynamic other than undef weak

Fixes: tmpdir/pr14525: symbol lookup error: tmpdir/pr14525: undefined
symbol: __executable_start
FAIL: PIE PR ld/14525

	* elf32-hppa.c (ensure_undef_weak_dynamic): New function.
	(allocate_plt_static, allocate_dynrelocs): Use it.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Sync dwarf headers with master versions in gcc repository.
@ 2017-01-04  1:22 sergiodj+buildbot
  2017-01-04  6:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  1:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb9b4b7e534c4df7e8e0cb60c180e61f27617f0a ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: fb9b4b7e534c4df7e8e0cb60c180e61f27617f0a

Sync dwarf headers with master versions in gcc repository.

	* dwarf2.def: Sync with mainline gcc sources
	* dwarf2.h: Likewise.

	2016-12-21  Jakub Jelinek  <jakub@redhat.com>

	* dwarf2.def (DW_FORM_ref_sup): Renamed to ...
	(DW_FORM_ref_sup4): ... this.  New form.
	(DW_FORM_ref_sup8): New form.

	2016-10-17  Jakub Jelinek  <jakub@redhat.com>

	* dwarf2.h (enum dwarf_calling_convention): Add new DWARF5
	calling convention codes.
	(enum dwarf_line_number_content_type): New.
	(enum dwarf_location_list_entry_type): Add DWARF5 DW_LLE_*
	codes.
	(enum dwarf_source_language): Add new DWARF5 DW_LANG_* codes.
	(enum dwarf_macro_record_type): Add DWARF5 DW_MACRO_* codes.
	(enum dwarf_name_index_attribute): New.
	(enum dwarf_range_list_entry): New.
	(enum dwarf_unit_type): New.
	* dwarf2.def: Add new DWARF5 DW_TAG_*, DW_FORM_*, DW_AT_*,
	DW_OP_* and DW_ATE_* entries.

	2016-08-15  Jakub Jelinek  <jakub@redhat.com>

	* dwarf2.def (DW_AT_string_length_bit_size,
	DW_AT_string_length_byte_size): New attributes.

	2016-08-12  Alexandre Oliva <aoliva@redhat.com>

	PR debug/63240
	* dwarf2.def (DW_AT_deleted, DW_AT_defaulted): New.
	* dwarf2.h (enum dwarf_defaulted_attribute): New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix compile time warning about using a possibly uninitialised variable.
@ 2017-01-04  1:38 sergiodj+buildbot
  2017-01-04  7:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  1:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09fe2662a708aa4da665bcaf942b5529e6809220 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 09fe2662a708aa4da665bcaf942b5529e6809220

Fix compile time warning about using a possibly uninitialised variable.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add fall through comment.
@ 2017-01-04  3:11 sergiodj+buildbot
  2017-01-04 10:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  3:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b52d3cfcfb472263eca181da37dfc0377978acba ***

Author: Dilyan Palauzov <dilyan.palauzov@aegee.org>
Branch: master
Commit: b52d3cfcfb472263eca181da37dfc0377978acba

Add fall through comment.

	* riscv-dis.c (print_insn_args): Add fall through comment.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Add support for the Q extension to the RISCV ISA.
@ 2017-01-04  3:42 sergiodj+buildbot
  2017-01-04 12:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  3:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc917fd93d2a836adfd61b91df021cf835e88fd1 ***

Author: Kito Cheng <kito.cheng@gmail.com>
Branch: master
Commit: cc917fd93d2a836adfd61b91df021cf835e88fd1

Add support for the Q extension to the RISCV ISA.

gas    * config/tc-riscv.c (riscv_set_arch): Whitelist the "q" ISA
        extension.
        (riscv_after_parse_args): Set FLOAT_ABI_QUAD when the Q ISA is
        enabled and no other ABI is specified.

include * opcode/riscv-opc.h: Add support for the "q" ISA extension.

opcodes * riscv-opc.c (riscv-opcodes): Add support for the "q" ISA
        extension.
        * riscv-opcodes/all-opcodes: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] bfd: alpha: Fix crash caused by double free with --no-keep-memory
@ 2017-01-04  3:56 sergiodj+buildbot
  2017-01-04 13:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  3:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae4fda663812129df67e3a70691787060242c0f9 ***

Author: James Clarke <jrtc27@jrtc27.com>
Branch: master
Commit: ae4fda663812129df67e3a70691787060242c0f9

bfd: alpha: Fix crash caused by double free with --no-keep-memory

Without this, ld has been seen to crash in libc when freeing tsec_free:

*** Error in `/usr/bin/ld': double free or corruption (!prev): 0x0000000120ceb6a0 ***

_bfd_elf_link_read_relocs will always return the cached value if
present, even if keep_memory is false, therefore setting tsec_free to
NULL only when keep_memory is true is not sufficient.

	* elf64-alpha.c (elf64_alpha_relax_opt_call): Don't set tsec_free
	if relocs are cached.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix generation of GOT table when only GOT-relative relocs are used.
@ 2017-01-04  5:38 sergiodj+buildbot
  2017-01-04 11:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de1010f40884537cf0905ad134162cd2db71dc2a ***

Author: Rich Felker <bugdal@aerifal.cx>
Branch: master
Commit: de1010f40884537cf0905ad134162cd2db71dc2a

Fix generation of GOT table when only GOT-relative relocs are used.

	PR ld/21017
	* elf32-microblaze.c (microblaze_elf_check_relocs): Add an entry
	for R_MICROBLAZE_GOTOFF_64.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix an internal error on writing pieced value
@ 2017-01-04 10:10 sergiodj+buildbot
  2017-01-04 14:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 10:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2aaaf250e80afb4a5c66fb0b7801e24cc5c4e680 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 2aaaf250e80afb4a5c66fb0b7801e24cc5c4e680

Fix an internal error on writing pieced value

In ee40d8d (Move computed value's frame id to piece_closure), I only
updated read_pieced_value to use frame_id from piece_closure, but
forgot to update write_pieced_value, so it causes the following
internal error on arm-linux,

set variable l = 4^M
gdb/git/gdb/value.c:1579: internal-error: frame_id* deprecated_value_next_frame_id_hack(value*): Assertion `value->lval == lval_register' failed.^M
A problem internal to GDB has been detected,^M
further debugging may prove unreliable.^M
Quit this debugging session? (y or n) FAIL: gdb.base/store.exp: var longest l; setting l to 4 (GDB internal error)

This patch fixes the internal error.

gdb:

2017-01-04  Yao Qi  <yao.qi@linaro.org>

	* dwarf2loc.c (write_pieced_value): Don't use VALUE_FRAME_ID (to),
	use c->frame_id when the piece location is DWARF_VALUE_REGISTER.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [AArch64] Add separate feature flag for weaker release consistent load insns
@ 2017-01-04 12:49 sergiodj+buildbot
  2017-01-04 16:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 12:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d74d4880e23263bac3690bcb641af56bd13036e6 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: d74d4880e23263bac3690bcb641af56bd13036e6

[AArch64] Add separate feature flag for weaker release consistent load insns

The weaker release consistency support of ARMv8.3-A is allowed as an optional
extension for ARMv8.2-A, so separate command line option and feature flag is
added: -march=armv8.2-a+rcpc turns LDAPR, LDAPRB, LDAPRH instructions on.

opcodes/
	* aarch64-tbl.h (RCPC, RCPC_INSN): Define.
	(aarch64_opcode_table): Use RCPC_INSN.

include/
	* opcode/aarch64.h (AARCH64_FEATURE_RCPC): Define.
	(AARCH64_ARCH_V8_3): Update.

gas/
	* config/tc-aarch64.c (aarch64_features): Add rcpc.
	* doc/c-aarch64.texi (AArch64 Extensions): Document rcpc.
	* testsuite/gas/aarch64/ldst-exclusive-armv8_3.d: Rename to ...
	* testsuite/gas/aarch64/ldst-rcpc.d: This.
	* testsuite/gas/aarch64/ldst-exclusive-armv8_3.s: Rename to ...
	* testsuite/gas/aarch64/ldst-rcpc.s: This.
	* testsuite/gas/aarch64/ldst-rcpc-armv8_2.d: New test.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Sync libiberty from gcc
@ 2017-01-04 14:42 sergiodj+buildbot
  2017-01-04 18:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 14:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e495212d229d58eb4d70c94d7f828a04c386c3b2 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: e495212d229d58eb4d70c94d7f828a04c386c3b2

Sync libiberty from gcc

Picks up copyright year update and other recent fixes.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] update-copyright.py for binutils
@ 2017-01-04 14:57 sergiodj+buildbot
  2017-01-04 20:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c2a23b23e9ca7015acadbbc7a12c665791c8337 ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 7c2a23b23e9ca7015acadbbc7a12c665791c8337

update-copyright.py for binutils

This is a modified form of gcc's contrib/update-copyright.py.

	* update-copyright.py: New file.
	* add-log.el: Update copyright year range.
	* texi2pod.pl: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [DWARF] Sync GCC dwarf.def change on AArch64
@ 2017-01-04 16:08 sergiodj+buildbot
  2017-01-04 21:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 16:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8cf50cb070642d73acc537010d71c912f921861c ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 8cf50cb070642d73acc537010d71c912f921861c

[DWARF] Sync GCC dwarf.def change on AArch64

include/
	* dwarf2.def: Sync with mainline gcc sources.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use correct OSABI constant for FreeBSD/mips binaries.
@ 2017-01-04 20:32 sergiodj+buildbot
  2017-01-04 23:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-04 20:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c988ac1de5bc0efec2022fc6ce7d13b24e540099 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: c988ac1de5bc0efec2022fc6ce7d13b24e540099

Use correct OSABI constant for FreeBSD/mips binaries.

gdb/ChangeLog:

	* mips-fbsd-tdep.c (_initialize_mips_fbsd_tdep): Use
	GDB_OSABI_FREEBSD instead of GDB_OSABI_FREEBSD_ELF.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Five fixes, for fcsel, fcvtz, fminnm, mls, and non-widening mul.
@ 2017-01-05  0:23 sergiodj+buildbot
  2017-01-05  1:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-05  0:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0386d4d54d2cc33d6efc0b998fe6396bf92be15 ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: c0386d4d54d2cc33d6efc0b998fe6396bf92be15

Five fixes, for fcsel, fcvtz, fminnm, mls, and non-widening mul.

	sim/aarch64/
	* cpustate.c: Include math.h.
	(aarch64_set_FP_float): Use signbit to check for signed zero.
	(aarch64_set_FP_double): Likewise.
	* simulator.c (do_vec_MOV_immediate, case 0x8): Add missing break.
	(do_vec_mul): In all DO_VEC_WIDENING_MUL calls, make second and fourth
	args same size as third arg.
	(fmaxnm): Use isnan instead of fpclassify.
	(fminnm, dmaxnm, dminnm): Likewise.
	(do_vec_MLS): Reverse order of subtraction operands.
	(dexSimpleFPCondSelect): Call aarch64_get_FP_double or
	aarch64_get_FP_float to get source register contents.
	(UINT_MIN, ULONG_MIN, FLOAT_UINT_MAX, FLOAT_UINT_MIN,
	DOUBLE_UINT_MAX, DOUBLE_UINT_MIN, FLOAT_ULONG_MAX, FLOAT_ULONG_MIN,
	DOUBLE_ULONG_MAX, DOUBLE_ULONG_MIN): New.
	(do_fcvtzu): Use ULONG instead of LONG, and UINT instead of INT in
	raise_exception calls.

	sim/testsuite/sim/aarch64/
	* fcsel.s: New.
	* fcvtz.s: New.
	* fminnm.s: New.
	* mls.s: New.
	* mul.s: New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Prevent an abort in the FRV disassembler if the target bfd name is unknown.
@ 2017-01-05  9:19 sergiodj+buildbot
  2017-01-05 12:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-05  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae60c3ef45d41b34d40ed5c7b4fdfea289530de ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 0ae60c3ef45d41b34d40ed5c7b4fdfea289530de

Prevent an abort in the FRV disassembler if the target bfd name is unknown.

	PR 20946
	* frv-desc.c (lookup_mach_via_bfd_name): Return NULL if the name
	could not be matched.
	(frv_cgen_cpu_open): Allow for lookup_mach_via_bfd_name returning
	NULL.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update gdb_ptrace.h in HFILES_NO_SRCDIR
@ 2017-01-06 14:17 sergiodj+buildbot
  2017-01-06 15:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad5cba2adbdb8ec216d44515468bde8d96892c3d ***

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

Update gdb_ptrace.h in HFILES_NO_SRCDIR

Commit e379037 (Move gdb_ptrace.h to nat/), so we should update
file name in HFILES_NO_SRCDIR too.  Otherwise, 'make tags' complains,

$ make tags
make: *** No rule to make target `gdb_ptrace.h', needed by `TAGS'.  Stop.

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (HFILES_NO_SRCDIR): Replace gdb_ptrace.h
	with nat/gdb_ptrace.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include ax.h in ax-gdb.h
@ 2017-01-06 15:00 sergiodj+buildbot
  2017-01-06 16:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0b8369c8aa4e05bf8f1b2ce4a79133cf1192a16 ***

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

Include ax.h in ax-gdb.h

$ make check-headers CHECK_HEADERS="ax-gdb.h"
...

../../binutils-gdb/gdb/ax-gdb.h:104:8: error: 'agent_expr_up' does not name a type
 extern agent_expr_up gen_trace_for_expr (CORE_ADDR, struct expression *,
        ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* ax-gdb.h: Include "ax.h"


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include doublest.h and expression.h in dfp.h
@ 2017-01-06 15:35 sergiodj+buildbot
  2017-01-06 17:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8018d34f1e5d94ffe1f12ac2455429c6f713c518 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 8018d34f1e5d94ffe1f12ac2455429c6f713c518

Include doublest.h and expression.h in dfp.h

$ make check-headers CHECK_HEADERS="dfp.h"
...
../../binutils-gdb/gdb/dfp.h:39:8: error: 'DOUBLEST' does not name a type
 extern DOUBLEST decimal_to_doublest (const gdb_byte *from, int len,
        ^
../../binutils-gdb/gdb/dfp.h:41:33: error: use of enum 'exp_opcode' without previous declaration
 extern void decimal_binop (enum exp_opcode,
                                 ^
gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* dfp.h: Include "dboulest.h" and "expression.h".


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include target.h in inf-loop.h
@ 2017-01-06 16:36 sergiodj+buildbot
  2017-01-06 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 051d2ddae5a2289d1f253b563e57a8e8496a06bb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 051d2ddae5a2289d1f253b563e57a8e8496a06bb

Include target.h in inf-loop.h

$ make check-headers CHECK_HEADERS="target.h inf-loop.h"
...
../../binutils-gdb/gdb/inf-loop.h:23:42: error: use of enum 'inferior_event_type' without previous declaration
 extern void inferior_event_handler (enum inferior_event_type event_type,
                                          ^
gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* inf-loop.c: Don't include "target.h".
	* inf-loop.h: Include it here.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include mi-cmds.h in mi-parse.h
@ 2017-01-06 17:08 sergiodj+buildbot
  2017-01-06 19:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 66c80d03078b71470c66b8f00cab82d89daeea08 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 66c80d03078b71470c66b8f00cab82d89daeea08

Include mi-cmds.h in mi-parse.h

$ make check-headers CHECK_HEADERS="mi/mi-parse.h"
...
../../binutils-gdb/gdb/mi/mi-parse.h:77:6: error: use of enum 'print_values' without previous declaration
 enum print_values mi_parse_print_values (const char *name);
      ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* mi/mi-parse.h: Include mi-cmds.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include break-common.h in nat/aarch64-linux-hw-point.h
@ 2017-01-06 17:58 sergiodj+buildbot
  2017-01-06 20:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc3008c48f17aa67d39e539737a999737cd697a7 ***

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

Include break-common.h in nat/aarch64-linux-hw-point.h

$ make check-headers CHECK_HEADERS="nat/aarch64-linux-hw-point.h"
...
../../binutils-gdb/gdb/nat/aarch64-linux-hw-point.h:169:37: error: use of enum 'target_hw_bp_type' without previous declaration
 int aarch64_handle_breakpoint (enum target_hw_bp_type type, CORE_ADDR addr,
                                     ^
gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* nat/aarch64-linux-hw-point.h: Include break-common.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include signal.h in nat/amd64-linux-siginfo.h
@ 2017-01-06 18:31 sergiodj+buildbot
  2017-01-06 22:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ca8f924a46c620c7a7ddbd156c3a623a5a6d1fb ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1ca8f924a46c620c7a7ddbd156c3a623a5a6d1fb

Include signal.h in nat/amd64-linux-siginfo.h

$ make check-headers CHECK_HEADERS="nat/amd64-linux-siginfo.h"
....
../../binutils-gdb/gdb/nat/amd64-linux-siginfo.h:52:39: error: 'siginfo_t' was not declared in this scope
 int amd64_linux_siginfo_fixup_common (siginfo_t *native, gdb_byte *inf,
                                       ^
gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* nat/amd64-linux-siginfo.h: Include signal.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include serial.h in ser-base.h.
@ 2017-01-06 19:51 sergiodj+buildbot
  2017-01-07 22:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 44d6d3f93341387bd2c95ea4c941bf99127e7389 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 44d6d3f93341387bd2c95ea4c941bf99127e7389

Include serial.h in ser-base.h.

$ make check-headers CHECK_HEADERS="ser-base.h"
...
../../binutils-gdb/gdb/ser-base.h:33:8: error: 'serial_ttystate' does not name a type
 extern serial_ttystate ser_base_get_tty_state (struct serial *scb);
        ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* ser-base.h: Include serial.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Include gdb_proc_service.h in x86-linux-nat.h
@ 2017-01-06 20:40 sergiodj+buildbot
  2017-01-07 23:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-06 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e2d6fa6a38ae2b80a56d786a41d905c9541906f ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 0e2d6fa6a38ae2b80a56d786a41d905c9541906f

Include gdb_proc_service.h in x86-linux-nat.h

$ make check-headers CHECK_HEADERS="x86-linux-nat.h"
...
../../binutils-gdb/gdb/x86-linux-nat.h:29:8: error: 'ps_err_e' does not name a type
 extern ps_err_e x86_linux_get_thread_area (pid_t pid, void *addr,
        ^

gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* x86-linux-nat.h: Include gdb_proc_service.h.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] [D] Fix crash when debug expression enabled.
@ 2017-01-08 10:52 sergiodj+buildbot
  2017-01-08 13:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-08 10:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5e6296e2194add209b546ad49039753a10242f5 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: f5e6296e2194add209b546ad49039753a10242f5

[D] Fix crash when debug expression enabled.

While casting works as expected with expression debugging turned off,
this seems to be an indication that the D language parser function is
doing something wrong in the building of the expression.

Without changing the grammar, using UNOP_CAST_TYPE is the right thing to
do here, as the TypeExp handler has already wrapped the type around a
pair of OP_TYPE opcodes.

gdb/ChangeLog:

	* d-exp.y (CastExpression): Emit UNOP_CAST_TYPE.

gdb/testsuite/ChangeLog:

	* gdb.dlang/debug-expr.exp: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Speed up objdump when displaying disassembly mixed with line number and source code information.
@ 2017-01-09 17:05 sergiodj+buildbot
  2017-01-09 18:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-09 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd6581da62c32a391f9a4c2c5d248a11aa6fa8f7 ***

Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: cd6581da62c32a391f9a4c2c5d248a11aa6fa8f7

Speed up objdump when displaying disassembly mixed with line number and source code information.

bfd	* dwarf2.c (lookup_address_in_function_table): Return early if
	there are no functions in the given comp unit, or if the high
	address of the last function in the comp unit is less than the
	desired address.

binutils * objdump.c (display_file): Add new parameter 'last_file'.  If
	last_file is true, do not call bfd_close at the end of the
	function.
	(main): Set the value of the last_file parameter when calling
	display_file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Fix problems with the implementation of the uzp1 and uzp2 instructions.
@ 2017-01-10  0:02 sergiodj+buildbot
  2017-01-10  0:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-10  0:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4fb5981b7ec3d4006e93141afb1d0da566bb97b ***

Author: Jim Wilson <jim.wilson@linaro.org>
Branch: master
Commit: a4fb5981b7ec3d4006e93141afb1d0da566bb97b

Fix problems with the implementation of the uzp1 and uzp2 instructions.

	sim/aarch64/
	* simulator.c (do_vec_UZP): Rewrite.
	sim/testsuite/sim/aarch64/
	* uzp.s: New.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Update help of the "frame" command
@ 2017-01-10 15:35 sergiodj+buildbot
  2017-01-10 16:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-10 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df2946549f60624503663cc6c28cd5a6ef0ab434 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: df2946549f60624503663cc6c28cd5a6ef0ab434

Update help of the "frame" command

The help message of the "frame" command states that nothing is printed
if the command is executed from the command file or user-defined
command.  My testing leads me to think that this is not true (at least
today).

  (gdb) bt
  #0  bar (n=17) at test.c:9
  #1  0x00000000004006e0 in foo (v=17) at test.c:13
  #2  0x00000000004006f0 in main () at test.c:21
  (gdb) frame
  #0  bar (n=17) at test.c:9
  9	    baz(n);
  (gdb) define foo
  Type commands for definition of "foo".
  End with a line saying just "end".
  >frame 1
  >end
  (gdb) foo
  #1  0x00000000004006e0 in foo (v=17) at test.c:13
  13	    bar(v);

This patch simply removes that bit from the help message.  I didn't find
anything corresponding to this in the documentation that needs to be
fixed.

The behavior change corresponding to this documentation change was done
in commit b00771232fab861fb31e42dfd5f6643ba1b43cc9.

gdb/ChangeLog:

	* stack.c (_initialize_stack): Update "frame" command help message.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change return type of ui_out redirect to void
@ 2017-01-10 16:47 sergiodj+buildbot
  2017-01-10 17:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-10 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7becfd03bad526c02216eeb5ec2bebae694b1af1 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 7becfd03bad526c02216eeb5ec2bebae694b1af1

Change return type of ui_out redirect to void

All implementations of redirect/do_redirect in the ui_out subsystem
always return 0 (success).  We can therefore clean it up and make them
return void.

gdb/ChangeLog:

	* cli-out.c (cli_ui_out::do_redirect): Change return type to
	void.
	* cli-out.h (cli_ui_out::do_redirect): Likewise.
	* mi/mi-out.c (mi_ui_out::do_redirect): Likewise.
	* mi/mi-out.h (mi_ui_out::do_redirect): Likewise.
	* ui-out.c (ui_out::redirect): Likewise.
	* ui-out.h (ui_out::redirect, ui_out::do_redirect): Likewise.
	* cli/cli-logging.c (set_logging_redirect): Update call site of
	ui_out::redirect.
	(handle_redirections): Likewise.
	* scm-ports.c (ioscm_with_output_to_port_worker): Likewise.
	* top.c (execute_command_to_string): Likewise.
	* utils.c (do_ui_out_redirect_pop): Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Don't use elf_i386_eh_frame_plt directly
@ 2017-01-10 19:51 sergiodj+buildbot
  2017-01-10 20:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-10 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f129e49f4d07f4d36319ac757fdcf3a8ce7d605b ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: f129e49f4d07f4d36319ac757fdcf3a8ce7d605b

Don't use elf_i386_eh_frame_plt directly

Use eh_frame_plt_size and eh_frame_plt from elf_i386_plt_layout for
.eh_frame covering the .plt section.

	* elf32-i386.c (elf_i386_size_dynamic_sections): Set
	plt_eh_frame->size to eh_frame_plt_size and use eh_frame_plt.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] i386/x86-64: Add unwind info for .plt.got section
@ 2017-01-10 21:52 sergiodj+buildbot
  2017-01-10 22:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-10 21:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fff53daefb7838b5718422c87946330e4a8288ce ***

Author: H.J. Lu <hjl.tools@gmail.com>
Branch: master
Commit: fff53daefb7838b5718422c87946330e4a8288ce

i386/x86-64: Add unwind info for .plt.got section

When there are both PLT and GOT references to the same function symbol,
linker combines GOTPLT and GOT slots into a single GOT slot and create
an entry in .plt.got section for PLT access via the GOT slot.  This
patch adds unwind info for .plt.got section.

bfd/

	PR ld/20830
	* elf32-i386.c (elf_i386_eh_frame_plt_got): New.
	(PLT_GOT_FDE_LENGTH): Likewise.
	(elf_i386_plt_layout): Add eh_frame_plt_got and
	eh_frame_plt_got_size.
	(elf_i386_plt): Updated.
	(elf_i386_link_hash_table): Add plt_got_eh_frame.
	(elf_i386_check_relocs): Create .eh_frame section for .plt.got.
	(elf_i386_size_dynamic_sections): Allocate and initialize
	.eh_frame section for .plt.got.
	(elf_i386_finish_dynamic_sections): Adjust .eh_frame section for
	.plt.got.
	(elf_i386_nacl_plt): Add FIXME for eh_frame_plt_got and
	eh_frame_plt_got_size.
	* elf64-x86-64.c (elf_x86_64_eh_frame_plt_got): New.
	(PLT_GOT_FDE_LENGTH): Likewise.
	(elf_x86_64_backend_data): Add eh_frame_plt_got and
	eh_frame_plt_got_size.
	(elf_x86_64_arch_bed): Updated.
	(elf_x86_64_bnd_arch_bed): Add FIXME for eh_frame_plt_got and
	eh_frame_plt_got_size.
	(elf_x86_64_nacl_arch_bed): Likewise.
	(elf_x86_64_link_hash_table): Add plt_got_eh_frame.
	(elf_x86_64_check_relocs): Create .eh_frame section for .plt.got.
	(elf_x86_64_size_dynamic_sections): Allocate and initialize
	.eh_frame section for .plt.got.
	(elf_x86_64_finish_dynamic_sections): Adjust .eh_frame section
	for .plt.got.

ld/

	PR ld/20830
	* testsuite/ld-i386/i386.exp: Run pr20830.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-i386/pr20830.d: New file.
	* testsuite/ld-i386/pr20830.s: Likewise.
	* testsuite/ld-x86-64/pr20830.d: Likewise.
	* testsuite/ld-x86-64/pr20830.s: Likewise.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce py-ref.h
@ 2017-01-11  5:41 sergiodj+buildbot
  2017-01-11  7:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  5:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a68ff33e0dcb4733584265088030d12a31e740e4 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: a68ff33e0dcb4733584265088030d12a31e740e4

Introduce py-ref.h

This patch introduces class gdbpy_ref, which is a sort of smart
pointer that owns a single Python reference to a PyObject.  This class
acts a bit like unique_ptr, but also a bit like shared_ptr (in that
copies do what you might expect); I considered going solely with
unique_ptr but it seemed quite strange to have a unique_ptr that
actually manages a shared resource.

Subsequent patches use this new class to simplify logic in the Python
layer.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-ref.h: New file.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in gdbpy_breakpoints
@ 2017-01-11  7:09 sergiodj+buildbot
  2017-01-11 14:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  7:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf2a52fa2ac2c4486653993a765fd922b3cd64a6 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: bf2a52fa2ac2c4486653993a765fd922b3cd64a6

Use gdbpy_ref in gdbpy_breakpoints

This changes gdbpy_breakpoints to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-breakpoint.c (gdbpy_breakpoints): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change event code to use gdbpy_ref
@ 2017-01-11  7:18 sergiodj+buildbot
  2017-01-11  8:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  7:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abf5651e47c0396df58a37951bc03a349169c5f2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: abf5651e47c0396df58a37951bc03a349169c5f2

Change event code to use gdbpy_ref

This changes the event code in the Python layer to use
gdbpy_ref, simplifying the logic in many places.

It also changes evpy_emit_event not to steal a reference to its
argument.  This is simpler to do now that gdbpy_ref is in use;
it's also a reasonable cleanup in its own right.  While doing this I
realized that evpy_emit_event should not be calling gdbpy_print_stack
(all the outermost callers do this if needed), so I removed this as
well.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-threadevent.c (create_thread_event_object): Use
	gdbpy_ref.
	* python/py-stopevent.c (create_stop_event_object): Simplify.
	(emit_stop_event): Use gdbpy_ref.
	* python/py-signalevent.c (create_signal_event_object): Use
	gdbpy_ref.
	* python/py-newobjfileevent.c (create_new_objfile_event_object)
	(emit_new_objfile_event, create_clear_objfiles_event_object)
	(emit_clear_objfiles_event): Use gdbpy_ref.
	* python/py-infevents.c (create_inferior_call_event_object)
	(create_register_changed_event_object)
	(create_memory_changed_event_object, emit_inferior_call_event)
	(emit_memory_changed_event, emit_register_changed_event): Use
	gdbpy_ref.
	* python/py-exitedevent.c (create_exited_event_object)
	(emit_exited_event): Use gdbpy_ref.
	* python/py-event.h (evpy_emit_event): Remove
	CPYCHECKER_STEALS_REFERENCE_TO_ARG annotation.
	* python/py-event.c (evpy_emit_event): Use gdbpy_ref.
	* python/py-continueevent.c (emit_continue_event): Use
	gdbpy_ref.
	* python/py-breakpoint.c (gdbpy_breakpoint_created)
	(gdbpy_breakpoint_deleted, gdbpy_breakpoint_modified): Use
	gdbpy_ref.
	* python/py-bpevent.c (create_breakpoint_event_object): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-framefilter.c
@ 2017-01-11  7:59 sergiodj+buildbot
  2017-01-11 16:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  7:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee0a3fb85b33b172f704796612c4487ea368d675 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: ee0a3fb85b33b172f704796612c4487ea368d675

Use gdbpy_ref in py-framefilter.c

This changes some code in py-framefilter.c to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-framefilter.c (extract_sym, extract_value)
	(get_py_iter_from_func, bootstrap_python_frame_filters): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in gdbpy_string_to_argv
@ 2017-01-11  8:42 sergiodj+buildbot
  2017-01-11 10:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1b3de2e43380a0c51772a40315cd2268573d985 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: d1b3de2e43380a0c51772a40315cd2268573d985

Use gdbpy_ref in gdbpy_string_to_argv

This chanes gdbpy_string_to_argv to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-cmd.c (gdbpy_string_to_argv): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in call_doc_function
@ 2017-01-11  9:54 sergiodj+buildbot
  2017-01-11 18:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1bb44c9f567c75355c1b4417d88cda959e82a3a3 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1bb44c9f567c75355c1b4417d88cda959e82a3a3

Use gdbpy_ref in call_doc_function

This changes call_doc_function to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-param.c (call_doc_function): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-value.c
@ 2017-01-11 11:14 sergiodj+buildbot
  2017-01-11 21:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53a0cca3bd0f6ae80b2d6fc34b2873046965c7f0 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 53a0cca3bd0f6ae80b2d6fc34b2873046965c7f0

Use gdbpy_ref in py-value.c

This changes a few functions in py-value.c to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (value_has_field, get_field_flag)
	(get_field_type, valpy_getitem, convert_value_from_python): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in gdbpy_lookup_symbol
@ 2017-01-11 11:29 sergiodj+buildbot
  2017-01-11 23:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 11:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37fce74fb42f45ec340962170a4b297beede733a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 37fce74fb42f45ec340962170a4b297beede733a

Use gdbpy_ref in gdbpy_lookup_symbol

This changes gdbpy_lookup_symbol to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-symbol.c (gdbpy_lookup_symbol): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce gdbpy_enter
@ 2017-01-11 11:46 sergiodj+buildbot
  2017-01-12  0:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ecee2c47da3e91c0571683acb5cfb8400402663 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4ecee2c47da3e91c0571683acb5cfb8400402663

Introduce gdbpy_enter

This introduces gdbpy_enter, a class that can be used to acquire and
release the Python GIL, and also set other Python-related globals used
by gdb.  ensure_python_env is rewritten in terms of this new class.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (gdbpy_enter): New constructor.
	(~gdbpy_enter): New destructor.
	(restore_python_env, ensure_python_env): Rewrite.
	* python/python-internal.h (gdbpy_enter): New class.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-cmd.c
@ 2017-01-11 12:51 sergiodj+buildbot
  2017-01-12  3:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 12:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ba0cd406511d3edbe643f5e599d79538febedc5 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6ba0cd406511d3edbe643f5e599d79538febedc5

Use gdbpy_enter in py-cmd.c

Change py-cmd.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-cmd.c (cmdpy_destroyer)
	(cmdpy_completer_handle_brkchars, cmdpy_completer): Use
	gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-objfile.c
@ 2017-01-11 14:12 sergiodj+buildbot
  2017-01-12  7:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d38bcedc2f91692857d257e106dafc9269d8f1a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 2d38bcedc2f91692857d257e106dafc9269d8f1a

Use gdbpy_enter in py-objfile.c

Change py-objfile.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-objfile.c (py_free_objfile): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in python.c
@ 2017-01-11 14:43 sergiodj+buildbot
  2017-01-12  9:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60e600ec691255536ae53e365d0410ecf79bdea2 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 60e600ec691255536ae53e365d0410ecf79bdea2

Use gdbpy_enter in python.c

Change the simple parts of python.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (gdbpy_eval_from_control_command)
	(gdbpy_source_script, gdbpy_run_events)
	(gdbpy_source_objfile_script, gdbpy_execute_objfile_script)
	(gdbpy_free_type_printers, gdbpy_finish_initialization): Use
	gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-type.c
@ 2017-01-11 14:59 sergiodj+buildbot
  2017-01-12 10:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c57af3f12b91ca49adc2e06056f794cb09514897 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: c57af3f12b91ca49adc2e06056f794cb09514897

Use gdbpy_enter in py-type.c

Change py-type.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-type.c (save_objfile_types): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-xmethods.c
@ 2017-01-11 15:49 sergiodj+buildbot
  2017-01-12 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 15:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f18e226ff84f7fba9ce7197ed7a2969eba231b4d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: f18e226ff84f7fba9ce7197ed7a2969eba231b4d

Use gdbpy_enter in py-xmethods.c

Change the simple parts of py-xmethods.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-xmethods.c (gdbpy_free_xmethod_worker_data)
	(gdbpy_clone_xmethod_worker_data): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-unwind.c
@ 2017-01-11 16:05 sergiodj+buildbot
  2017-01-12 13:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0171de646ddd85bac9d4bb1ebdf601f7ba7eeab ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: c0171de646ddd85bac9d4bb1ebdf601f7ba7eeab

Use gdbpy_enter in py-unwind.c

Change py-unwind.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-unwind.c (pending_frame_invalidate): Remove.
	(pyuw_sniffer): Use gdbpy_enter and gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in python_interactive_command
@ 2017-01-11 18:16 sergiodj+buildbot
  2017-01-12 18:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 18:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 396a78b6271c45410fc22c4bc7f8cff75da3d153 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 396a78b6271c45410fc22c4bc7f8cff75da3d153

Use gdbpy_enter in python_interactive_command

This changes python_interactive_command to use gdbpy_enter.
Previously this function was leaving a dangling cleanup -- this is
sort of ok in a command function, but IMO it's still better to clean
up.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (python_interactive_command): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in gdbpy_get_matching_xmethod_workers
@ 2017-01-11 18:31 sergiodj+buildbot
  2017-01-12 20:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 572a5524c1eb50d8064a44108fd0ef22a0e63bf8 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 572a5524c1eb50d8064a44108fd0ef22a0e63bf8

Use gdbpy_enter in gdbpy_get_matching_xmethod_workers

Change gdbpy_get_matching_xmethod_workers to use gdbpy_enter and
gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-xmethods.c (gdbpy_get_matching_xmethod_workers): use
	gdbpy_enter, gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-xmethod.c
@ 2017-01-11 19:03 sergiodj+buildbot
  2017-01-12 22:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14b122bf1ce59f5f1b82f6e2a347f4ad89801f45 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 14b122bf1ce59f5f1b82f6e2a347f4ad89801f45

Use gdbpy_enter in py-xmethod.c

This changes the remaining functions in py-xmethod.c to use
gdbpy_enter; using gdbpy_ref and unique_xmalloc_ptr as
appropriate.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-xmethods.c (gdbpy_get_xmethod_result_type): Use
	gdbpy_enter, gdbpy_ref, unique_xmalloc_ptr.
	(gdbpy_invoke_xmethod): Use gdbpy_ref, gdbpy_enter.
	(gdbpy_get_xmethod_arg_types): Use gdbpy_ref,
	unique_xmalloc_ptr.
	(gdbpy_get_xmethod_arg_types): Use gdbpy_ref, gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-finishbreakpoint.c
@ 2017-01-11 19:07 sergiodj+buildbot
  2017-01-12  4:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e7c365ee0ea2551f9f840b71081fdf759088b5e ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6e7c365ee0ea2551f9f840b71081fdf759088b5e

Use gdbpy_enter in py-finishbreakpoint.c

Change py-finishbreakpoint.c to use gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-finishbreakpoint.c (bpfinishpy_handle_stop)
	(bpfinishpy_handle_exit): Use gdbpy_enter.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Introduce gdbpy_enter_varobj and use it
@ 2017-01-11 19:18 sergiodj+buildbot
  2017-01-13  0:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 19:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cd67beaae58c9e870b79feea3cf74ffdf7a9b33 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 6cd67beaae58c9e870b79feea3cf74ffdf7a9b33

Introduce gdbpy_enter_varobj and use it

This introduces gdbpy_enter_varobj, a subclass of gdbpy_enter; then
changes one function in py-varobj.c to use it.  gdbpy_enter_varobj
takes a varobj as an argument, similar to varobj_ensure_python_env.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* varobj.c (gdbpy_enter_varobj): New constructor.
	* python/python-internal.h (gdbpy_enter_varobj): New class.
	* python/py-varobj.c (py_varobj_get_iterator): Use
	gdbpy_enter_varobj.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in cmdpy_function
@ 2017-01-11 19:49 sergiodj+buildbot
  2017-01-13  3:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 19:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12a5cedd4f2c5b1f4e303efda6f8ac3e06eec944 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 12a5cedd4f2c5b1f4e303efda6f8ac3e06eec944

Use gdbpy_enter in cmdpy_function

This changes cmdpy_function to use gdbpy_enter and gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-cmd.c (cmdpy_function): Use gdbpy_enter, gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in py-param.c
@ 2017-01-11 20:19 sergiodj+buildbot
  2017-01-13  5:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2865bfce3875fa16046b0a987d98ab19fc8bbb9a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 2865bfce3875fa16046b0a987d98ab19fc8bbb9a

Use gdbpy_enter in py-param.c

This converts the remaining functions in py-param.c to use
gdbpy_enter.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-param.c (get_set_value, get_show_value): Use
	gdbpy_enter, gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in python.c
@ 2017-01-11 20:35 sergiodj+buildbot
  2017-01-13  6:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7785f8c797183eb363e95c201343df67d8536c6 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: a7785f8c797183eb363e95c201343df67d8536c6

Use gdbpy_enter in python.c

This changes the last functions in python.c to use gdbpy_enter.  I
split gdbpy_finish_initialization into two functions in order to avoid
some "goto"s.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (python_command): Use gdbpy_enter, gdbpy_ref.
	(do_finish_initialization): New function.  Use gdbpy_ref.
	(gdbpy_finish_initialization): Use gdbpy_enter.  Call
	do_finish_initialization.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change type of encoding argument to gdbpy_extract_lazy_string
@ 2017-01-11 21:40 sergiodj+buildbot
  2017-01-13  9:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eba63835ea23cbae6059c076db985a47e39ce24 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 1eba63835ea23cbae6059c076db985a47e39ce24

Change type of encoding argument to gdbpy_extract_lazy_string

This changes gdbpy_extract_lazy_string's "encoding" argument to be a
unique_xmalloc_ptr.  I chose this rather than std::string because it
can sometimes be NULL.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-prettyprint.c (print_string_repr, print_children):
	Update.
	* python/py-lazy-string.c (gdbpy_extract_lazy_string): Change type
	of "encoding".
	* varobj.c (varobj_value_get_print_value): Update.
	* python/python-internal.h (gdbpy_extract_lazy_string): Update.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter_varobj in varobj_value_get_print_value
@ 2017-01-11 21:55 sergiodj+buildbot
  2017-01-13 10:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68cdc55720bbe34d9d844ef2a0c4d75fcab4bc99 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 68cdc55720bbe34d9d844ef2a0c4d75fcab4bc99

Use gdbpy_enter_varobj in varobj_value_get_print_value

This changes the last function in varobj.c to use gdbpy_enter_varobj.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* varobj.c (varobj_value_get_print_value): Use
	gdbpy_enter_varobj.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py_print_frame
@ 2017-01-11 22:26 sergiodj+buildbot
  2017-01-13 12:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 22:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b4e0e01f8b19269d720948ee2350cb753f8ede4 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 3b4e0e01f8b19269d720948ee2350cb753f8ede4

Use gdbpy_ref in py_print_frame

This changes py_print_frame to use gdbpy_ref in a few spots.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-framefilter.c (py_print_frame): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Change python_run_simple_file to use gdbpy_ref
@ 2017-01-11 23:31 sergiodj+buildbot
  2017-01-13 15:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-11 23:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9de10f6d53dffbec12cec9843662d5764526983d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9de10f6d53dffbec12cec9843662d5764526983d

Change python_run_simple_file to use gdbpy_ref

This changes python_run_simple_file to use gdbpy_ref and
unique_xmalloc_ptr.  Thi fixes a latent bug in this function, where
the error path previously ran the cleanups and then referred to one of
the objects just freed.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (python_run_simple_file): Use
	unique_xmalloc_ptr, gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in archpy_disassemble
@ 2017-01-12  0:34 sergiodj+buildbot
  2017-01-13 16:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59e9e83119a528f17afea89ee22195a95322c6d6 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 59e9e83119a528f17afea89ee22195a95322c6d6

Use gdbpy_ref in archpy_disassemble

This changes archpy_disassemble to use gdbpy_ref.  It also fixes a
latent bug where archpy_disassemble was decref'ing the results of a
all to PyArg_ParseTupleAndKeywords.  This is incorrect because
PyArg_ParseTupleAndKeywords returns borrowed references.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-arch.c (archpy_disassemble): Use gdbpy_ref.  Don't
	decref results of PyArg_ParseTupleAndKeywords.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-inferior.c
@ 2017-01-12  1:51 sergiodj+buildbot
  2017-01-13 23:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  1:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9205649a38c609a42ba52680a316fceaa08c1543 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9205649a38c609a42ba52680a316fceaa08c1543

Use gdbpy_ref in py-inferior.c

This changes py-inferior.c to use gdbpy_ref in more places.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-inferior.c (find_thread_object, build_inferior_list):
	Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-param.c
@ 2017-01-12  2:37 sergiodj+buildbot
  2017-01-14  1:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  2:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97d83487d5fbffd04d68a049f97009e1df2562a3 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 97d83487d5fbffd04d68a049f97009e1df2562a3

Use gdbpy_ref in py-param.c

This changes py-param.c to use gdbpy_ref in a couple more spots.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-param.c (get_doc_string, compute_enum_values): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in python.c
@ 2017-01-12  2:53 sergiodj+buildbot
  2017-01-14  9:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  2:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59876f8f9f32081b2831aed83a03a815e8d85a97 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 59876f8f9f32081b2831aed83a03a815e8d85a97

Use gdbpy_ref in python.c

This changes more places in python.c to use gdbpy_ref.

Additionally, previously gdbpy_apply_type_printers would return
EXT_LANG_RC_ERROR if a type printer returned None.  However, that
doesn't seem correct to me; this patch changes it to return
EXT_LANG_RC_NOP in this case.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/python.c (eval_python_command, gdbpy_decode_line)
	(gdbpy_run_events, gdbpy_start_type_printers)
	(gdbpy_apply_type_printers): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in pyuw_object_attribute_to_pointer
@ 2017-01-12  3:09 sergiodj+buildbot
  2017-01-14 16:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  3:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4586d54305ed275bb909f3373a7372c02d7e579e ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 4586d54305ed275bb909f3373a7372c02d7e579e

Use gdbpy_ref in pyuw_object_attribute_to_pointer

This changes pyuw_object_attribute_to_pointer to use gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-unwind.c (pyuw_object_attribute_to_pointer): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in invoke_match_method
@ 2017-01-12  5:21 sergiodj+buildbot
  2017-01-12 21:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  5:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf1ca3b9476185fb6e301d85e646f5d2af95e257 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: bf1ca3b9476185fb6e301d85e646f5d2af95e257

Use gdbpy_ref in invoke_match_method

Change invoke_match_method to use gdbpy_ref.
I neglected to convert this function in my earlier series.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-xmethods.c (invoke_match_method): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter_varobj in py-varobj.c
@ 2017-01-12  7:27 sergiodj+buildbot
  2017-01-13  1:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  7:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 788f258604773ccbe9ccba71f9b1725930324275 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 788f258604773ccbe9ccba71f9b1725930324275

Use gdbpy_enter_varobj in py-varobj.c

This converts the remaining functions in py-varobj.c to use
gdbpy_enter_varobj.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-varobj.c (py_varobj_iter_dtor, py_varobj_iter_next):
	Use gdbpy_enter_varobj.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter in fnpy_call
@ 2017-01-12  8:52 sergiodj+buildbot
  2017-01-13  4:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e9dcc758786feaaaf5026c6e59af42b30a35d36 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0e9dcc758786feaaaf5026c6e59af42b30a35d36

Use gdbpy_enter in fnpy_call

This changes fnpy_call to use gdbpy_enter and gdbpy_ref.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-function.c (fnpy_call): Use gdbpy_enter, gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_enter_varobj in more of varobj.c
@ 2017-01-12 10:32 sergiodj+buildbot
  2017-01-13  8:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12 10:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bde7b3e3a0d5e1f0b66730d692b21c98a8686f75 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: bde7b3e3a0d5e1f0b66730d692b21c98a8686f75

Use gdbpy_enter_varobj in more of varobj.c

This converts most of the remaining functions in varobj.c to use
gdbpy_enter_varobj.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* varobj.c (varobj_get_display_hint)
	(dynamic_varobj_has_child_method, install_new_value_visualizer)
	(varobj_set_visualizer, free_variable): Use
	gdbpy_enter_varobj.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-prettyprint.c
@ 2017-01-12 14:12 sergiodj+buildbot
  2017-01-13 14:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2bd5759dcb71adfb26b1c7cf20b3b032af29b845 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 2bd5759dcb71adfb26b1c7cf20b3b032af29b845

Use gdbpy_ref in py-prettyprint.c

This changes some spots in py-prettyprint.c to use gdbpy_ref.  It also
changes push_dummy_python_frame to be a class, rather than having it
create a cleanup.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-prettyprint.c (print_stack_unless_memory_error)
	(print_string_repr, print_children): Use gdbpy_ref.
	(dummy_python_frame): New class.
	(dummy_python_frame::dummy_python_frame): Rename from
	push_dummy_python_frame.
	(py_restore_tstate): Remove.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in gdbpy_breakpoint_cond_says_stop
@ 2017-01-12 15:55 sergiodj+buildbot
  2017-01-13 18:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64081434cce13f38288d82d3d31b6199e9deff4a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 64081434cce13f38288d82d3d31b6199e9deff4a

Use gdbpy_ref in gdbpy_breakpoint_cond_says_stop

This changes gdbpy_breakpoint_cond_says_stop to use gdbpy_ref rather
than explicit reference management.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-breakpoint.c (gdbpy_breakpoint_cond_says_stop): Use
	gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py-cmd.c
@ 2017-01-12 16:30 sergiodj+buildbot
  2017-01-13 19:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 905f2ccab1b7070c7953e9f12de638e2dc147a9a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 905f2ccab1b7070c7953e9f12de638e2dc147a9a

Use gdbpy_ref in py-cmd.c

This changes py-cmd.c to use gdbpy_ref in more places.  This also
fixes a latent memory leak in cmdpy_completer_helper, which
unnecessarily increfs the result of PyObject_CallMethodObjArgs.  This
is not needed because that function returns a new reference.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-cmd.c (cmdpy_completer_helper): Use gdbpy_ref.  Remove
	extra incref.
	(cmdpy_completer_handle_brkchars, cmdpy_completer, cmdpy_init):
	Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
* [binutils-gdb] Use gdbpy_ref in py_print_frame
@ 2017-01-12 17:47 sergiodj+buildbot
  2017-01-13 22:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
  0 siblings, 1 reply; 3232+ messages in thread
From: sergiodj+buildbot @ 2017-01-12 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74c49d454b81c84fcffbc090466e241bdefd2f3a ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 74c49d454b81c84fcffbc090466e241bdefd2f3a

Use gdbpy_ref in py_print_frame

This changes py_print_frame to use gdbpy_ref in more places.

2017-01-10  Tom Tromey  <tom@tromey.com>

	* python/py-framefilter.c (py_print_frame): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 3232+ messages in thread
end of thread, other threads:[~2017-01-14 16:24 UTC | newest]

Thread overview: 3232+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-27 16:26 [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in sergiodj+buildbot
2015-07-27 16:26 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2015-07-27 16:46 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-07-27 16:58 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-07-27 17:02 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-07-27 17:04 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-27 17:05 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-27 18:20 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-07-27 19:17 ` Failures on Debian-i686, " sergiodj+buildbot
2015-07-27 19:29 ` Failures on Debian-MIPS-m64, " sergiodj+buildbot
2015-07-27 19:34 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-07-27 19:58 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-07-27 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-29  4:06 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-07-29  4:22 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-07-29  4:43 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-29 14:25 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-12 20:57 [binutils-gdb] Use target_terminal_ours_for_output in warning/internal_error sergiodj+buildbot
2016-04-13 15:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-12 23:43 [binutils-gdb] Decouple target_interrupt from all-stop/non-stop modes sergiodj+buildbot
2016-04-13  9:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  1:16 [binutils-gdb] ada-lang.c: Introduce type_as_string and use it sergiodj+buildbot
2016-04-13 12:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  2:05 [binutils-gdb] Fix inconsistent handling of EINTR in ser-*.c backends sergiodj+buildbot
2016-04-13 11:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  2:29 [binutils-gdb] Use target_terminal_ours_for_output in exceptions.c sergiodj+buildbot
2016-04-13 13:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  5:01 [binutils-gdb] Use target_terminal_ours_for_output in MI sergiodj+buildbot
2016-04-13 17:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  5:12 [binutils-gdb] Use target_terminal_ours_for_output in infcmd.c sergiodj+buildbot
2016-04-13 14:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  5:54 [binutils-gdb] target remote: Don't rely on immediate_quit (introduce quit handlers) sergiodj+buildbot
2016-04-13 19:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  6:32 [binutils-gdb] Eliminate immediate_quit sergiodj+buildbot
2016-04-13 20:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  6:59 [binutils-gdb] Eliminate target_check_pending_interrupt sergiodj+buildbot
2016-04-13 20:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  7:30 [binutils-gdb] Eliminate prepare_to_throw_exception sergiodj+buildbot
2016-04-13 21:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  8:11 [binutils-gdb] Do target_terminal_ours in query & friends instead of in all callers sergiodj+buildbot
2016-04-13 16:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  8:30 [binutils-gdb] Use setjmp/longjmp for TRY/CATCH instead of sigsetjmp/siglongjmp sergiodj+buildbot
2016-04-13 22:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13  9:19 [binutils-gdb] TUI: GC tui_target_has_run sergiodj+buildbot
2016-04-13 18:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 12:28 [binutils-gdb] [C++] Switch TRY/CATCH to real C++ try/catch by default again sergiodj+buildbot
2016-04-13 23:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 13:01 [binutils-gdb] Fix typo in ftrace.exp condition testing sergiodj+buildbot
2016-04-14  0:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 13:43 [binutils-gdb] btrace: fix test build error in gdb.btrace/instruction_history.c sergiodj+buildbot
2016-04-14  2:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 14:46 [binutils-gdb] Fix PR remote/19840: gdb crashes on reverse-stepi sergiodj+buildbot
2016-04-14  7:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 15:21 [binutils-gdb] Fix aarch64 ftrace JIT condition testcase sergiodj+buildbot
2016-04-14  8:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 16:19 [binutils-gdb] Fix disassembly of the V850's LD.BU instruction sergiodj+buildbot
2016-04-14  9:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 17:17 [binutils-gdb] Fix and improve comment in gdb_remote_download sergiodj+buildbot
2016-04-14 10:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-13 21:23 [binutils-gdb] Test GDB connection to GDBserver with no symbol files sergiodj+buildbot
2016-04-14 12:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-14 12:27 [binutils-gdb] Avoid implicit float <-> integer conversion warnings sergiodj+buildbot
2016-04-14 14:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-14 12:49 [binutils-gdb] Avoid "format not a string literal" warnings sergiodj+buildbot
2016-04-14 14:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-14 15:50 [binutils-gdb] Replace "link" with "sh_link" sergiodj+buildbot
2016-04-14 16:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-14 16:59 [binutils-gdb] bfd/arc: Rename enum entries to avoid conflicts sergiodj+buildbot
2016-04-14 17:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-14 17:59 [binutils-gdb] arc/nps400 : New cmem instructions and associated relocation sergiodj+buildbot
2016-04-14 18:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-15 14:55 [binutils-gdb] [ARM] minor opt in thumb_stack_frame_destroyed_p sergiodj+buildbot
2016-04-15 14:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-15 23:19 [binutils-gdb] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT sergiodj+buildbot
2016-04-15 23:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-16  0:51 [binutils-gdb] Regenerate Makefile.in/aclocal.m4 automake 1.11.6 sergiodj+buildbot
2016-04-16  5:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-16  1:25 [binutils-gdb] Fix gdb C++ build when libipt is available sergiodj+buildbot
2016-04-16  7:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-16  2:42 [binutils-gdb] gdb/ada-exp.y: Remap yydefred sergiodj+buildbot
2016-04-16 11:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-18  8:16 [binutils-gdb] Revert 415fa612 sergiodj+buildbot
2016-04-18  8:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-18 12:17 [binutils-gdb] testsuite: Support detection of Intel compilers via test_compiler_version sergiodj+buildbot
2016-04-18 12:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-18 13:05 [binutils-gdb] Testsuite: Fix compiling of shared libraries with ICC sergiodj+buildbot
2016-04-18 13:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-18 13:32 [binutils-gdb] fortran: Testsuite, fix different type naming across compilers sergiodj+buildbot
2016-04-18 13:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-18 14:16 [binutils-gdb] Fix gdb crash when trying to print the address of a synthetic C++ reference sergiodj+buildbot
2016-04-18 14:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19  8:50 [binutils-gdb] Sync Makefile.tpl with gcc sergiodj+buildbot
2016-04-19  8:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 14:07 [binutils-gdb] Add target descriptions for AVX + MPX sergiodj+buildbot
2016-04-19 14:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 14:47 [binutils-gdb] Re-factor (i386|amd64)mpx target descriptions sergiodj+buildbot
2016-04-19 15:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 15:07 [binutils-gdb] linux-record: Squash cases with identical handling sergiodj+buildbot
2016-04-19 15:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 16:33 [binutils-gdb] * source.c (is_regular_file): New arg errno_ptr sergiodj+buildbot
2016-04-19 16:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 16:46 [binutils-gdb] Fix copyright year, remove linux only test sergiodj+buildbot
2016-04-19 17:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 17:34 [binutils-gdb] symmisc.c (dump_symtab_1, dump_symtab): Delete arg objfile sergiodj+buildbot
2016-04-19 18:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 22:17 [binutils-gdb] opcodes/arc: Add more nps instructions sergiodj+buildbot
2016-04-19 22:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-19 23:53 [binutils-gdb] Handle void * conversions in FreeBSD/x86 native code to fix C++ build sergiodj+buildbot
2016-04-20  2:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 11:08 [binutils-gdb] arc: Fix relocation formula for ARC_NPS_CMEM16 relocation sergiodj+buildbot
2016-04-20 11:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 11:27 [binutils-gdb] change argument type to bfd_byte sergiodj+buildbot
2016-04-20 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 12:15 [binutils-gdb] update many old style function definitions sergiodj+buildbot
2016-04-20 12:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 12:32 [binutils-gdb] Move ARM_CPSR_GREGNUM to arch/arm-linux.h sergiodj+buildbot
2016-04-20 13:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 13:16 [binutils-gdb] Check ELF relocs after opening all input files sergiodj+buildbot
2016-04-20 14:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 13:35 [binutils-gdb] Call _bfd_elf_create_ifunc_sections only for ifunc sergiodj+buildbot
2016-04-20 15:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 17:31 [binutils-gdb] symmisc.c (dump_symtab_1): Print owning compunit for identical blockvectors sergiodj+buildbot
2016-04-20 17:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 18:32 [binutils-gdb] Check run-time R_X86_64_32 relocation overflow sergiodj+buildbot
2016-04-20 18:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 21:09 [binutils-gdb] gdb/darwin-nat.c: Fix "cast to pointer from integer of different size" warning sergiodj+buildbot
2016-04-20 21:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 22:24 [binutils-gdb] Fix "incompatible pointer type" warning in gdb/aarch64-tdep.c sergiodj+buildbot
2016-04-20 22:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-20 22:56 [binutils-gdb] Fix host signal vs gdb signal mixup in gdb/darwin-nat.c sergiodj+buildbot
2016-04-20 23:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-21 10:39 [binutils-gdb] Add missing sentinel 'char *' casts in concat/reconcat calls sergiodj+buildbot
2016-04-21 10:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-21 11:15 [binutils-gdb] Fix s390 GNU/Linux gdb and gdbserver builds sergiodj+buildbot
2016-04-21 12:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-21 13:06 [binutils-gdb] Fix AIX gdb build with C++ compiler sergiodj+buildbot
2016-04-21 13:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-21 14:48 [binutils-gdb] Add support for non-ELF targets to check their relocs sergiodj+buildbot
2016-04-21 15:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-21 16:36 [binutils-gdb] Switch gdb's TRY/CATCH to sjlj again sergiodj+buildbot
2016-04-21 16:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22  0:52 [binutils-gdb] MIPS: Go back with the default Linux # of registers to 90 sergiodj+buildbot
2016-04-22  1:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22  2:30 [binutils-gdb] Set dynobj to a normal input file if possible sergiodj+buildbot
2016-04-22  3:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22  5:18 [binutils-gdb] Exclude linker created file from dynobj sergiodj+buildbot
2016-04-22  5:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 11:40 [binutils-gdb] Deliver signal in hardware single step sergiodj+buildbot
2016-04-22 12:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 12:44 [binutils-gdb] [obv] [PR gdb/19980] Typo in gdbserver/configure.srv sergiodj+buildbot
2016-04-22 13:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 14:40 [binutils-gdb] Joel Brobecker stepping down as AIX Maintainer sergiodj+buildbot
2016-04-22 14:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 15:00 [binutils-gdb] Fix fail in gdb.base/annota1.exp and gdb.base/annota3.exp sergiodj+buildbot
2016-04-22 15:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 15:39 [binutils-gdb] [ARM] Clear reserved bits in CPSR sergiodj+buildbot
2016-04-22 16:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 16:05 [binutils-gdb] Rename rl_callback_read_char_wrapper -> gdb_rl_callback_read_char_wrapper sergiodj+buildbot
2016-04-22 17:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 16:34 [binutils-gdb] Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CATCH sergiodj+buildbot
2016-04-22 17:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 17:51 [binutils-gdb] Switch gdb's TRY/CATCH to C++ try/catch sergiodj+buildbot
2016-04-22 18:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 18:39 [binutils-gdb] Centralize yacc interface names remapping (yyparse, yylex, yyerror, etc) sergiodj+buildbot
2016-04-22 19:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-22 19:48 [binutils-gdb] Fix fails in gdb.trace/unavailable.exp sergiodj+buildbot
2016-04-22 21:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-23 17:00 [binutils-gdb] Skip if size of bfd_vma is smaller than address size sergiodj+buildbot
2016-04-23 17:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-25  8:34 [binutils-gdb] Force to insert software single step breakpoint sergiodj+buildbot
2016-04-25  8:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-25  9:03 [binutils-gdb] Insert breakpoint even when the raw breakpoint is found sergiodj+buildbot
2016-04-25  9:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-25  9:46 [binutils-gdb] [GDBserver] Don't error in reinsert_raw_breakpoint if bp->inserted sergiodj+buildbot
2016-04-25 10:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-26 11:09 [binutils-gdb] Always count the NULL entry in dynamic symbol table sergiodj+buildbot
2016-04-26 11:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-26 14:47 [binutils-gdb] fort_dyn_array: Enable dynamic member types inside a structure sergiodj+buildbot
2016-04-26 14:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-26 15:59 [binutils-gdb] fort_dyn_array: Use value constructor instead of raw-buffer manipulation sergiodj+buildbot
2016-04-26 16:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27  0:26 [binutils-gdb] add casts to avoid arithmetic on void * sergiodj+buildbot
2016-04-27  2:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27  7:52 [binutils-gdb] Cache result of scan for __start_* and __stop_* sections sergiodj+buildbot
2016-04-27  8:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 10:52 [binutils-gdb] Add support for the --trace-decode option to the AArch64 simulator sergiodj+buildbot
2016-04-27 11:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 12:00 [binutils-gdb] Fix a typo in the check for SNANs in the RX simulator sergiodj+buildbot
2016-04-27 12:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 15:34 [binutils-gdb] c_value_print: Revert 'val' to a reference for TYPE_CODE_STRUCT sergiodj+buildbot
2016-04-27 15:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 15:46 [binutils-gdb] Skip gdb.base/branch-to-self.exp if gdb, nosignals exists sergiodj+buildbot
2016-04-27 17:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 16:28 [binutils-gdb] Skip debug sections when estimating distances sergiodj+buildbot
2016-04-27 18:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 19:55 [binutils-gdb] Workaround gdbserver<7.7 for setfs sergiodj+buildbot
2016-04-27 19:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-27 22:25 [binutils-gdb] Make gdb_load_shlibs return the destination path of the library sergiodj+buildbot
2016-04-27 22:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-28 11:08 [binutils-gdb] Remove need_step_over from struct lwp_info sergiodj+buildbot
2016-04-28 11:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-28 13:24 [binutils-gdb] Updated Chinese (simplified) translations for bfd, binutils and gold sergiodj+buildbot
2016-04-28 13:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-28 15:16 [binutils-gdb] ftrace tests: Use gdb_load_shlib result to lookup IPA in info sharedlibrary sergiodj+buildbot
2016-04-28 15:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-28 17:19 [binutils-gdb] Fix write endianness/size problem for fast tracepoint enabled flag sergiodj+buildbot
2016-04-28 17:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-28 17:38 [binutils-gdb] Add test for tracepoint enable/disable sergiodj+buildbot
2016-04-28 18:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-28 18:29 [binutils-gdb] Don't show deprecated commands in help sergiodj+buildbot
2016-04-28 19:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-29  8:54 [binutils-gdb] Enhance support for copying and stripping Solaris and ARM binaries sergiodj+buildbot
2016-04-29  9:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-29 12:01 [binutils-gdb] X86-64: Set check_relocs_failed on error sergiodj+buildbot
2016-04-29 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-29 12:43 [binutils-gdb] i386: Don't relocate section when check_relocs failed sergiodj+buildbot
2016-04-29 13:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-29 15:45 [binutils-gdb] Pass GOT_RELOC to UNDEFINED_WEAK_RESOLVED_TO_ZERO sergiodj+buildbot
2016-04-29 15:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-04-29 16:02 [binutils-gdb] Set interpreter in x86 create_dynamic_sections sergiodj+buildbot
2016-04-29 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-02 17:20 [binutils-gdb] Fix annota-input-while-running.exp remote check sergiodj+buildbot
2016-05-02 17:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-02 18:22 [binutils-gdb] Fix detach.exp remote check sergiodj+buildbot
2016-05-02 19:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-03  9:05 [binutils-gdb] [gdb] Fix -Wparentheses warnings sergiodj+buildbot
2016-05-03  9:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-03  9:56 [binutils-gdb] Fix "-Wl,--dynamic-list" gdb/configure test sergiodj+buildbot
2016-05-03 11:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-03 11:07 [binutils-gdb] Fix generation of AArhc64 instruction table sergiodj+buildbot
2016-05-03 13:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-03 11:27 [binutils-gdb] [AArch64] Also puts value in place for R_AARCH64_RELATIVE sergiodj+buildbot
2016-05-03 14:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-03 23:21 [binutils-gdb] PR 10549: MIPS/LD: Handle OSABI setting for STB_GNU_UNIQUE sergiodj+buildbot
2016-05-03 23:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-03 23:36 [binutils-gdb] Fix typos in gdb_pipe function comment sergiodj+buildbot
2016-05-04  0:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-04  0:22 [binutils-gdb] PR symtab/19914 fix handling of dwp + split debug sergiodj+buildbot
2016-05-04  1:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-04 13:48 [binutils-gdb] Introduce procedure use_gdb_stub sergiodj+buildbot
2016-05-04 13:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-04 14:35 [binutils-gdb] Fix solib-display.exp remote check sergiodj+buildbot
2016-05-04 14:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-04 14:42 [binutils-gdb] Throw NOT_AVAILABLE_ERROR in read_stack and read_code sergiodj+buildbot
2016-05-04 15:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-04 15:43 [binutils-gdb] [ARC] Add SYNTAX_NOP and SYNTAX_1OP for extension instructions sergiodj+buildbot
2016-05-04 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-05  0:11 [binutils-gdb] [spu] Fix C++ build problems sergiodj+buildbot
2016-05-05  0:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-05  8:19 [binutils-gdb] Change type of cpsr in arm_sigreturn_next_pc sergiodj+buildbot
2016-05-05  8:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-05  9:13 [binutils-gdb] Initialize res in get_next_pcs_read_memory_unsigned_integer sergiodj+buildbot
2016-05-05  9:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-05 11:45 [binutils-gdb] Cache the section contents in x86 check_relocs sergiodj+buildbot
2016-05-05 11:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-05 12:11 [binutils-gdb] Extract convert_load_reloc from x86 convert_load sergiodj+buildbot
2016-05-05 12:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-06 15:44 [binutils-gdb] Define elf_backend_add_symbol_hook for Intel MCU sergiodj+buildbot
2016-05-06 15:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-08  0:20 [binutils-gdb] remove trivialy unused variables sergiodj+buildbot
2016-05-08  1:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-09  8:25 [binutils-gdb] Redundant hash table check sergiodj+buildbot
2016-05-09  8:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-09  8:38 [binutils-gdb] Regenerate configure sergiodj+buildbot
2016-05-09  9:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-09 11:17 [binutils-gdb] opcodes,gas: sparc: fix mnemonic of faligndatai sergiodj+buildbot
2016-05-09 11:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-09 12:01 [binutils-gdb] Revert accidental commit sergiodj+buildbot
2016-05-09 12:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-09 13:29 [binutils-gdb] [ARM/STM32L4XX] PR 20030: --fix-stm32l4xx-629360 fails to create vldm/vpop veneers for double-precision registers sergiodj+buildbot
2016-05-09 14:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-09 16:52 [binutils-gdb] Fix seg fault objdumping a corrupt binary with an invalid sh_link field sergiodj+buildbot
2016-05-09 16:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10  2:02 [binutils-gdb] PR 20059 _bfd_elf_copy_link_hash_symbol_type segfault sergiodj+buildbot
2016-05-10  2:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 16:24 [binutils-gdb] Allow extension availability to depend on several architecture bits sergiodj+buildbot
2016-05-10 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 16:40 [binutils-gdb] Add support for ARMv8-M Mainline with DSP extension sergiodj+buildbot
2016-05-10 17:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 17:24 [binutils-gdb] Refactor Cortex-A8 erratum workaround in preparation sergiodj+buildbot
2016-05-10 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 17:37 [binutils-gdb] Factor our stub creation in ARM backend sergiodj+buildbot
2016-05-10 19:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 18:12 [binutils-gdb] Allow stubs without associated input section in ARM backend sergiodj+buildbot
2016-05-10 20:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 18:49 [binutils-gdb] Use getters/setters to access ARM branch type sergiodj+buildbot
2016-05-10 21:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 19:10 [binutils-gdb] Allow veneers to claim veneered symbols sergiodj+buildbot
2016-05-10 22:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-10 19:42 [binutils-gdb] Enable Intel RDPID instruction sergiodj+buildbot
2016-05-10 23:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-11  1:45 [binutils-gdb] fix up two issues with the removal of unused variables sergiodj+buildbot
2016-05-11  1:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-11 11:26 [binutils-gdb] [AArch64] Remove redundant tls relax in elfNN_aarch64_final_link_relocate sergiodj+buildbot
2016-05-11 11:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-11 14:06 [binutils-gdb] [HPPA] Attach linker created dynamic sections to stub bfd sergiodj+buildbot
2016-05-11 14:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-11 16:26 [binutils-gdb] Add MIPS32 DSPr3 support sergiodj+buildbot
2016-05-11 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-12 15:11 [binutils-gdb] ld -z combreloc reloc sorting sergiodj+buildbot
2016-05-12 15:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-13  6:13 [binutils-gdb] Set dynamic tag VMA and size from dynamic section when possible sergiodj+buildbot
2016-05-13  6:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-13 18:25 [binutils-gdb] Don't convert GOTPCREL relocation against large section sergiodj+buildbot
2016-05-13 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-13 20:38 [binutils-gdb] Accept valid one byte signed and unsigned values for the IMM8 operand sergiodj+buildbot
2016-05-13 20:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17  8:00 [binutils-gdb] Use unsuspend_all_lwps sergiodj+buildbot
2016-05-17  8:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 11:40 [binutils-gdb] LD/ELF: Unify STB_GNU_UNIQUE handling sergiodj+buildbot
2016-05-17 11:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 20:49 [binutils-gdb] Fix latent yacc-related bug in gdb/Makefile.in init.c rule sergiodj+buildbot
2016-05-17 20:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 21:21 [binutils-gdb] Make gdb expression debugging handle OP_F90_RANGE sergiodj+buildbot
2016-05-17 21:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 21:36 [binutils-gdb] Update gdb test suite for Rust sergiodj+buildbot
2016-05-18  4:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 21:52 [binutils-gdb] Add self-test framework to gdb sergiodj+buildbot
2016-05-17 22:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 22:37 [binutils-gdb] Add array start and end strings to generic_val_print_decorations sergiodj+buildbot
2016-05-17 23:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 22:44 [binutils-gdb] Add support for the Rust language sergiodj+buildbot
2016-05-18  1:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-17 23:52 [binutils-gdb] Add Rust documentation sergiodj+buildbot
2016-05-18  6:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18  0:39 [binutils-gdb] Rename OP_F90_RANGE to OP_RANGE sergiodj+buildbot
2016-05-18  9:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18  1:09 [binutils-gdb] Fix -exec-run not running asynchronously with mi-async on (PR gdb/18077) sergiodj+buildbot
2016-05-18 10:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18  6:45 [binutils-gdb] elf32-arm.c build breakage sergiodj+buildbot
2016-05-18 13:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18 12:06 [binutils-gdb] Updated Swedish translations for bfd and binutils sergiodj+buildbot
2016-05-18 14:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18 14:45 [binutils-gdb] Fix double prompt output after run control MI commands with mi-async on (PR 20045) sergiodj+buildbot
2016-05-18 16:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18 15:15 [binutils-gdb] Add mi-threads-interrupt.exp test (PR 20039) sergiodj+buildbot
2016-05-18 17:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-18 17:49 [binutils-gdb] Fix build failure with GCC 4.1 sergiodj+buildbot
2016-05-18 20:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19  5:14 [binutils-gdb] Fix ppc64le S-record test fail sergiodj+buildbot
2016-05-19  5:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19  5:57 [binutils-gdb] Fix powerpc subis range sergiodj+buildbot
2016-05-19  6:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19  7:41 [binutils-gdb] Correct "Fix powerpc subis range" sergiodj+buildbot
2016-05-19  7:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19 10:25 [binutils-gdb] Remove unsupported `am34-*-linux*' target triplet sergiodj+buildbot
2016-05-19 10:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19 13:20 [binutils-gdb] [ARC] BFD fixes sergiodj+buildbot
2016-05-19 13:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19 13:44 [binutils-gdb] Fix invalid implicit conversions from void * sergiodj+buildbot
2016-05-19 14:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19 15:18 [binutils-gdb] Set sh_entsize for .init_array and similar sergiodj+buildbot
2016-05-19 15:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-19 20:17 [binutils-gdb] Don't convert R_386_GOT32 relocation sergiodj+buildbot
2016-05-19 20:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-20 13:05 [binutils-gdb] MIPS: Fix the encoding of immediates with microMIPS JALX sergiodj+buildbot
2016-05-20 13:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-20 17:00 [binutils-gdb] Don't check R_386_GOT32 when setting need_convert_load sergiodj+buildbot
2016-05-20 17:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23  5:30 [binutils-gdb] tic54x: rename typedef of struct symbol_ sergiodj+buildbot
2016-05-23  5:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23  8:08 [binutils-gdb] Search for libutil-freebsd as alternative to libutil sergiodj+buildbot
2016-05-23  8:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23  8:59 [binutils-gdb] Support for dedicated output section for some ARM veneer types sergiodj+buildbot
2016-05-23  9:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23 11:03 [binutils-gdb] Sync config.guess and config.sub with FSF GCC mainline versions sergiodj+buildbot
2016-05-23 11:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23 12:49 [binutils-gdb] Remove unused libthread_db td_thr_validate reference sergiodj+buildbot
2016-05-23 13:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23 15:08 [binutils-gdb] Use standard_testfile in gdb.arch/thumb-prologue.exp and gdb.arch/thumb2-it.exp sergiodj+buildbot
2016-05-23 15:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23 15:43 [binutils-gdb] [ARC] Rename "class" named attributes sergiodj+buildbot
2016-05-23 16:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23 16:28 [binutils-gdb] [ARC] Add XY registers, update neg instruction sergiodj+buildbot
2016-05-23 16:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-23 23:52 [binutils-gdb] Enable R_AARCH64_NONE for 64-bit code sergiodj+buildbot
2016-05-24  0:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24  9:33 [binutils-gdb] Add myself as a write-after-approval GDB maintainer sergiodj+buildbot
2016-05-24 10:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 11:32 [binutils-gdb] Fix syntax error in annota-input-while-running.exp sergiodj+buildbot
2016-05-24 12:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 14:15 [binutils-gdb] [Linux] Read vDSO range from /proc/PID/task/PID/maps instead of /proc/PID/maps sergiodj+buildbot
2016-05-24 15:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 14:24 [binutils-gdb] [Linux] Avoid refetching core-of-thread if thread hasn't run sergiodj+buildbot
2016-05-24 16:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 14:34 [binutils-gdb] [Linux] Optimize PID -> struct lwp_info lookup sergiodj+buildbot
2016-05-24 17:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 14:44 [binutils-gdb] Make gdb/linux-nat.c consider a waitstatus pending on the infrun side sergiodj+buildbot
2016-05-24 19:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 14:54 [binutils-gdb] Fix PR gdb/19828: gdb -p <process from a container>: internal error sergiodj+buildbot
2016-05-24 19:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 16:15 [binutils-gdb] Fix PR python/17981 sergiodj+buildbot
2016-05-24 20:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 16:24 [binutils-gdb] add nb_inplace_divide for python 2 sergiodj+buildbot
2016-05-24 21:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 16:34 [binutils-gdb] Fix PR python/17386 - add __index__ method to gdb.Value sergiodj+buildbot
2016-05-24 22:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-24 20:01 [binutils-gdb] MIPS/BFD: Unify `bfd_reloc_outofrange' error reporting code sergiodj+buildbot
2016-05-24 23:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25  7:20 [binutils-gdb] Fortran, typeprint: Fix wrong indentation when ptype nested structures sergiodj+buildbot
2016-05-25  8:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25  7:30 [binutils-gdb] Fortran, typeprint: Take level of details into account when printing elements of a structure sergiodj+buildbot
2016-05-25  9:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25  7:40 [binutils-gdb] Fortran, typeprint: Decrease level of details when printing elements of a structure sergiodj+buildbot
2016-05-25 10:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25  7:51 [binutils-gdb] Fortran, testsuite: Add testcases for nested structures sergiodj+buildbot
2016-05-25 11:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25  8:02 [binutils-gdb] Fortran, testsuite: Fix duplicate testcase name sergiodj+buildbot
2016-05-25 12:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 14:18 [binutils-gdb] fix spelling of HAVE_LIBPYTHON2_4 in py-value.c sergiodj+buildbot
2016-05-25 15:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 15:55 [binutils-gdb] Skip an archive element if not added by linker sergiodj+buildbot
2016-05-25 16:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 17:04 [binutils-gdb] Enable 64-bit archives in ar and ranlib sergiodj+buildbot
2016-05-25 17:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 17:39 [binutils-gdb] Reimplement .no87/.nommx/.nosse/.noavx directives sergiodj+buildbot
2016-05-25 19:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 18:50 [binutils-gdb] Enable VREX for AVX512 directives sergiodj+buildbot
2016-05-25 22:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 19:18 [binutils-gdb] Enable VREX for all AVX512 directives sergiodj+buildbot
2016-05-25 23:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-25 20:20 [binutils-gdb] MIPS/BFD: Report `bfd_reloc_outofrange' errors as such sergiodj+buildbot
2016-05-26  0:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-26 10:15 [binutils-gdb] metag: add extern C to header sergiodj+buildbot
2016-05-26 11:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-26 11:56 [binutils-gdb] MIPS/BFD: Don't stop processing on `bfd_reloc_outofrange' sergiodj+buildbot
2016-05-26 12:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27  0:21 [binutils-gdb] Add support for new POWER ISA 3.0 instructions sergiodj+buildbot
2016-05-27  2:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27 12:58 [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT sergiodj+buildbot
2016-05-27 15:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27 13:08 [binutils-gdb] Improve the MSP430 disassembler's handling of memory read errors sergiodj+buildbot
2016-05-27 16:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27 14:08 [binutils-gdb] Correct CpuMax in i386-opc.h sergiodj+buildbot
2016-05-27 19:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27 15:15 [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64 sergiodj+buildbot
2016-05-27 20:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27 21:56 [binutils-gdb] MIPS/BFD: Fix section symbol name fetching in relocation sergiodj+buildbot
2016-05-27 23:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-27 22:07 [binutils-gdb] MIPS/BFD: Include the addend in JALX's target alignment verification sergiodj+buildbot
2016-05-28  0:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-28  2:08 [binutils-gdb] Return void from linker callbacks sergiodj+buildbot
2016-05-28  3:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-28 10:13 [binutils-gdb] MIPS/BFD: Enable local R_MIPS_26 overflow detection sergiodj+buildbot
2016-05-28 11:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-28 10:23 [binutils-gdb] MIPS/BFD: Correctly handle `bfd_reloc_outofrange' with branches sergiodj+buildbot
2016-05-28 12:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-29 15:10 [binutils-gdb] Add .noavx512XX directives to x86 assembler sergiodj+buildbot
2016-05-29 16:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-29 16:52 [binutils-gdb] NEWS: Remove empty line sergiodj+buildbot
2016-05-29 18:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-29 18:59 [binutils-gdb] NEWS: QCatchSyscalls: simplify sergiodj+buildbot
2016-05-29 19:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-30 12:29 [binutils-gdb] Code cleanup: dwarf2_get_pc_bounds: -1/0/+1 -> enum sergiodj+buildbot
2016-05-30 13:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-30 12:38 [binutils-gdb] PR 15231: import bare DW_TAG_lexical_block sergiodj+buildbot
2016-05-30 14:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-30 17:04 [binutils-gdb] Add counter-cases for trace-condition.exp tests sergiodj+buildbot
2016-05-30 17:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-30 17:13 [binutils-gdb] Move trace conditions tests from ftrace.exp to trace-condition.exp sergiodj+buildbot
2016-05-30 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-30 17:22 [binutils-gdb] Add emit_less_unsigned test in trace-condition.exp sergiodj+buildbot
2016-05-30 19:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-30 17:30 [binutils-gdb] Add variable length tests for emit_ref in trace-condition.exp sergiodj+buildbot
2016-05-30 20:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-31 11:20 [binutils-gdb] Don't needlessly clear xmemdup allocated memory sergiodj+buildbot
2016-05-31 12:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-05-31 19:07 [binutils-gdb] [PR gdb/19893] Fix handling of synthetic C++ references sergiodj+buildbot
2016-05-31 20:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01  3:22 [binutils-gdb] sh: make constant unsigned to avoid narrowing sergiodj+buildbot
2016-06-01  8:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01  8:46 [binutils-gdb] Wake up interruptible_select in remote_fileio ctrl-c handler sergiodj+buildbot
2016-06-01  9:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01  9:27 [binutils-gdb] infcmd, btrace: fix crash in 'finish' for tailcall-only frames sergiodj+buildbot
2016-06-01 10:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01 10:56 [binutils-gdb] Add xmalloc_failed() function to common-utils.c in to avoid the need to link in libiberty's xmalloc code sergiodj+buildbot
2016-06-01 11:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01 15:39 [binutils-gdb] Add support for some variants of the ARC nps400 rflt instruction sergiodj+buildbot
2016-06-01 16:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01 15:48 [binutils-gdb] gdb/remote-fileio.c: Eliminate custom SIGINT signal handler sergiodj+buildbot
2016-06-01 17:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-01 16:03 [binutils-gdb] Add new Serbian translation for the bfd library sergiodj+buildbot
2016-06-01 18:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02  1:33 [binutils-gdb] add more extern C sergiodj+buildbot
2016-06-02  2:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02  3:32 [binutils-gdb] Revert PR16467 change sergiodj+buildbot
2016-06-02 13:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02 13:17 [binutils-gdb] Add support for 48 and 64 bit ARC instructions sergiodj+buildbot
2016-06-02 14:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02 14:30 [binutils-gdb] Replace data32 with data16 in comments sergiodj+buildbot
2016-06-02 15:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02 15:31 [binutils-gdb] Allow ARC Linux targets that do not use uclibc sergiodj+buildbot
2016-06-02 16:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02 15:40 [binutils-gdb] mi-memory-changed.exp: Fix filename passed to untested sergiodj+buildbot
2016-06-02 17:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02 16:28 [binutils-gdb] Add "arm_any" architecture type to allow -m option to various binutils to match any ARM architecture sergiodj+buildbot
2016-06-02 18:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-02 19:39 [binutils-gdb] Fix PR python/18984 sergiodj+buildbot
2016-06-03 11:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-03 11:47 [binutils-gdb] Fix C++ build for Cygwin sergiodj+buildbot
2016-06-03 12:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-03 23:50 [binutils-gdb] Re-add support for lbarx, lharx, stbcx. and sthcx. insns back to the E6500 cpu sergiodj+buildbot
2016-06-04  1:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-04 20:35 [binutils-gdb] Add z8k ld testsuite and fix range check in coff-z8k.c sergiodj+buildbot
2016-06-04 21:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-06 18:25 [binutils-gdb] Support x86-64 TLS code sequences without PLT sergiodj+buildbot
2016-06-06 18:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-06 21:21 [binutils-gdb] Add method/format information to =record-started sergiodj+buildbot
2016-06-06 21:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-07  9:09 [binutils-gdb] [ARM] Add command line option for RAS extension sergiodj+buildbot
2016-06-07  9:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-07 11:49 [binutils-gdb] Frame static link: Handle null pointer sergiodj+buildbot
2016-06-07 12:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-07 15:04 [binutils-gdb] Fix PLT first entry GOT operand calculation sergiodj+buildbot
2016-06-07 15:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-07 16:28 [binutils-gdb] bfd/s390: Misc minor fixes sergiodj+buildbot
2016-06-07 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-08 19:36 [binutils-gdb] Support i386 TLS code sequences without PLT sergiodj+buildbot
2016-06-08 19:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-09 16:17 [binutils-gdb] Print symbol names in comments for LDS/STS disassembly sergiodj+buildbot
2016-06-09 16:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-10  5:39 [binutils-gdb] Add myself as a write-after-approval GDB maintainer sergiodj+buildbot
2016-06-10  5:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-10  6:19 [binutils-gdb] Add negative repeat count to 'x' command sergiodj+buildbot
2016-06-10  6:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-10  9:37 [binutils-gdb] Fortran: Testsuite, non-local references in nested functions sergiodj+buildbot
2016-06-10  9:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-10 16:12 [binutils-gdb] Fix rust-exp handling in makefile sergiodj+buildbot
2016-06-10 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-10 16:15 [binutils-gdb] Fix PR rust/20110 sergiodj+buildbot
2016-06-10 17:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-10 16:24 [binutils-gdb] Constify arch_type and friends sergiodj+buildbot
2016-06-10 18:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-11  8:19 [binutils-gdb] Use size_t rather than bfd_size_type sergiodj+buildbot
2016-06-11  8:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-11  9:15 [binutils-gdb] sparc-coff writing uninitialized memory sergiodj+buildbot
2016-06-11  9:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-12  4:48 [binutils-gdb] Subtract GOT base only with a base register sergiodj+buildbot
2016-06-12  4:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 14:52 [binutils-gdb] [ARC] Generate DT_RELACOUNT sergiodj+buildbot
2016-06-13 14:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 15:47 [binutils-gdb] [ARC] General bug fixes sergiodj+buildbot
2016-06-13 16:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 16:49 [binutils-gdb] gdb: Use UNSUPPORTED not XFAIL for unsupported target features sergiodj+buildbot
2016-06-13 17:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 17:17 [binutils-gdb] [ARC] Fix condition sergiodj+buildbot
2016-06-13 18:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 19:01 [binutils-gdb] Add 2 i386 tests to call IFUNC functions via GOT sergiodj+buildbot
2016-06-13 21:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 19:23 [binutils-gdb] Add the GOT base for GOT32 relocs against IFUNC sergiodj+buildbot
2016-06-13 22:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-13 20:20 [binutils-gdb] MIPS/BFD: Update outdated comment about o32 R_MIPS_PC32 reloc support sergiodj+buildbot
2016-06-13 20:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14  6:01 [binutils-gdb] Set my_archive for thin archives sergiodj+buildbot
2016-06-14  5:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14  6:41 [binutils-gdb] Delete bfd_my_archive macro sergiodj+buildbot
2016-06-14  7:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14 15:50 [binutils-gdb] [ARC] Add arithmetic and logic instructions for nps sergiodj+buildbot
2016-06-14 15:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14 16:46 [binutils-gdb] [ARC] Add deep packet inspection instructions for nps sergiodj+buildbot
2016-06-14 16:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14 17:03 [binutils-gdb] [ARC] Add ldbit for nps sergiodj+buildbot
2016-06-14 17:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14 17:58 [binutils-gdb] Fix elf_x86_64_reloc_type_class sergiodj+buildbot
2016-06-14 19:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14 20:17 [binutils-gdb] Pass a NULL pointer as the last argument to find_pc_partial_function sergiodj+buildbot
2016-06-14 23:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-14 21:49 [binutils-gdb] Change the size field of MSP430_Opcode_Decoded to a plain integer sergiodj+buildbot
2016-06-14 21:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-15  0:47 [binutils-gdb] Remove unneeded checks on type lengths sergiodj+buildbot
2016-06-15  0:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-15  8:13 [binutils-gdb] Fix PR ld/20254 sergiodj+buildbot
2016-06-15  7:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-15  8:34 [binutils-gdb] opcodes/arc: Fix extract for some add_s instructions sergiodj+buildbot
2016-06-15  8:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-15 15:51 [binutils-gdb] Fix simple gas testsuite failures sergiodj+buildbot
2016-06-15 15:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-16  2:00 [binutils-gdb] Check SEC_ALLOC before allocating dynamic relocation sergiodj+buildbot
2016-06-16  2:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-16 13:19 [binutils-gdb] Skip relocations in non-loaded, non-alloced sections sergiodj+buildbot
2016-06-16 13:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-16 18:57 [binutils-gdb] Don't check undefined symbol for IFUNC reloc sergiodj+buildbot
2016-06-16 19:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17  9:36 [binutils-gdb] bfd, opcodes: sparc: new opcode v9{c, d, e, v, m} architectures and bfd machine numbers sergiodj+buildbot
2016-06-17 10:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 10:05 [binutils-gdb] opcodes, gas: adjust sparc insns and make GAS aware of it sergiodj+buildbot
2016-06-17 11:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 11:24 [binutils-gdb] opcodes, gas: sparc: fix rdasr, wrasr, rdpr, wrpr, rdhpr, wrhpr insns sergiodj+buildbot
2016-06-17 12:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 11:35 [binutils-gdb] gdb: new AndesTech NDS32 port sergiodj+buildbot
2016-06-17 13:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 12:52 [binutils-gdb] More assert checks on reinsert breakpoint sergiodj+buildbot
2016-06-17 15:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 13:31 [binutils-gdb] Switch to current thread in finish_step_over sergiodj+buildbot
2016-06-17 14:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 13:51 [binutils-gdb] Step over exit with reinsert breakpoints sergiodj+buildbot
2016-06-17 16:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 14:33 [binutils-gdb] Delete reinsert breakpoints from forked child sergiodj+buildbot
2016-06-17 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 15:07 [binutils-gdb] Extend step-over-syscall.exp with different detach-on-fork and follow-fork modes sergiodj+buildbot
2016-06-17 19:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 18:03 [binutils-gdb] Handle reinsert breakpoints for vforked child sergiodj+buildbot
2016-06-17 18:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-17 18:13 [binutils-gdb] Add support for Thumb-2 long branch veneers sergiodj+buildbot
2016-06-17 20:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-18 16:43 [binutils-gdb] Don't generate PLT for IFUNC GOT/pointer reference sergiodj+buildbot
2016-06-18 16:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-18 21:39 [binutils-gdb] Rename bfd_plugin_uknown to bfd_plugin_unknown sergiodj+buildbot
2016-06-18 21:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-20  2:13 [binutils-gdb] PR ld/20276: Set non_ir_ref on common symbol sergiodj+buildbot
2016-06-20  2:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  1:41 [binutils-gdb] [Ada catchpoints] Fix "warning: failed to get exception name: No definition of \"e.full_name\" in current context" sergiodj+buildbot
2016-06-21  1:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  1:57 [binutils-gdb] Introduce "struct ui" sergiodj+buildbot
2016-06-21  2:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  2:22 [binutils-gdb] Make gdb_stdout&co be per UI sergiodj+buildbot
2016-06-21  3:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  3:09 [binutils-gdb] Make the interpreters be per UI sergiodj+buildbot
2016-06-21  4:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  4:34 [binutils-gdb] Make the intepreters output to all UIs sergiodj+buildbot
2016-06-21  6:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  5:16 [binutils-gdb] Always run async signal handlers in the main UI sergiodj+buildbot
2016-06-21  7:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  5:39 [binutils-gdb] Introduce interpreter factories sergiodj+buildbot
2016-06-21  5:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  5:42 [binutils-gdb] Make instream be per UI sergiodj+buildbot
2016-06-21  8:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  6:37 [binutils-gdb] Make input_fd be per UI sergiodj+buildbot
2016-06-21  9:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  7:51 [binutils-gdb] Delete def_uiout sergiodj+buildbot
2016-06-21 11:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  9:06 [binutils-gdb] Make command line editing (use of readline) be per UI sergiodj+buildbot
2016-06-21 13:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21  9:34 [binutils-gdb] Always process target events in the main UI sergiodj+buildbot
2016-06-21 14:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 10:04 [binutils-gdb] Make out and error streams be per UI sergiodj+buildbot
2016-06-21 10:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 11:28 [binutils-gdb] Make raw_stdout be per MI instance sergiodj+buildbot
2016-06-21 16:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 11:56 [binutils-gdb] Make current_ui_out be per UI sergiodj+buildbot
2016-06-21 11:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 12:26 [binutils-gdb] Make gdb_in_secondary_prompt_p() be per UI sergiodj+buildbot
2016-06-21 18:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 13:19 [binutils-gdb] Replace the sync_execution global with a new enum prompt_state tristate sergiodj+buildbot
2016-06-21 19:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 14:06 [binutils-gdb] Fix for spurious prompts in secondary UIs sergiodj+buildbot
2016-06-21 20:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 14:53 [binutils-gdb] New function should_print_stop_to_console sergiodj+buildbot
2016-06-21 21:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 16:17 [binutils-gdb] Introduce display_mi_prompt sergiodj+buildbot
2016-06-21 15:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 16:21 [binutils-gdb] Only send sync execution command output to the UI that ran the command sergiodj+buildbot
2016-06-21 23:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 16:33 [binutils-gdb] Make main_ui be heap allocated sergiodj+buildbot
2016-06-22  1:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 17:20 [binutils-gdb] Handle UI's terminal closing sergiodj+buildbot
2016-06-22  3:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 18:04 [binutils-gdb] Make stdin be per UI sergiodj+buildbot
2016-06-22  6:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 18:51 [binutils-gdb] Add new command to create extra console/mi UIs sergiodj+buildbot
2016-06-22  9:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 19:51 [binutils-gdb] [DOC] Document support for running interpreters on separate UIs sergiodj+buildbot
2016-06-22 12:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 21:17 [binutils-gdb] Add testing infrastruture bits for running with MI on a separate UI sergiodj+buildbot
2016-06-22 13:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 21:40 [binutils-gdb] Make mi-break.exp always expect breakpoint commands output on the main UI sergiodj+buildbot
2016-06-22 18:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 22:18 [binutils-gdb] Always switch fork child to the main UI sergiodj+buildbot
2016-06-22 21:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-21 23:24 [binutils-gdb] Add "new-ui console" tests sergiodj+buildbot
2016-06-22 22:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22  1:37 [binutils-gdb] S390: Fix typo "s930" -> "s390" sergiodj+buildbot
2016-06-22 23:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22  3:18 [binutils-gdb] Arc assembler: Convert nps400 from a machine type to an extension sergiodj+buildbot
2016-06-23  3:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22  9:22 [binutils-gdb] tilegx: move TILEGX_NUM_PIPELINE_ENCODINGS to tilegx_pipeline enum sergiodj+buildbot
2016-06-23  9:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22 11:03 [binutils-gdb] Send deleted watchpoint-scope output to all UIs sergiodj+buildbot
2016-06-22 17:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22 16:52 [binutils-gdb] S390 gdbserver: Mark local funcs/vars as static sergiodj+buildbot
2016-06-23  1:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22 17:38 [binutils-gdb] addmore extern C sergiodj+buildbot
2016-06-23 12:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22 19:19 [binutils-gdb] Improve user experience in printing Fortran derived types sergiodj+buildbot
2016-06-23  5:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-22 23:12 [binutils-gdb] Add support for yet some more new ISA 3.0 instructions sergiodj+buildbot
2016-06-23 13:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-23  9:16 [binutils-gdb] [ARC] Misc minor edits/fixes sergiodj+buildbot
2016-06-23 14:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-23 14:21 [binutils-gdb] PR gdb/16483 - simplify "info frame-filters" output sergiodj+buildbot
2016-06-23 15:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24  3:10 [binutils-gdb] Make gdbpy_parameter static sergiodj+buildbot
2016-06-24  3:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24  3:40 [binutils-gdb] Use VEC for filename_language_table sergiodj+buildbot
2016-06-24  4:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24  4:36 [binutils-gdb] Move filename extensions into language_defn sergiodj+buildbot
2016-06-24  4:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 14:28 [binutils-gdb] MIPS objcopy --rename-section fix sergiodj+buildbot
2016-06-24 15:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 17:34 [binutils-gdb] fix undefined reference to bfd_link_plugin_object_p during link sergiodj+buildbot
2016-06-24 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 18:28 [binutils-gdb] Add constants for FreeBSD-specific auxiliary vector entry types sergiodj+buildbot
2016-06-24 18:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 18:39 [binutils-gdb] Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes sergiodj+buildbot
2016-06-24 19:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 19:32 [binutils-gdb] Fetch the ELF auxiliary vector from live processes on FreeBSD sergiodj+buildbot
2016-06-24 20:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 20:19 [binutils-gdb] Create a pseudo section for the ELF AUXV core dump note on FreeBSD sergiodj+buildbot
2016-06-24 21:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 20:57 [binutils-gdb] Add a new gdbarch method to print a single AUXV entry sergiodj+buildbot
2016-06-24 22:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 22:12 [binutils-gdb] Add support for catching system calls to native FreeBSD targets sergiodj+buildbot
2016-06-25  0:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 22:59 [binutils-gdb] Add myself as a Write After Approval maintainer sergiodj+buildbot
2016-06-25  1:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-24 22:59 [binutils-gdb] Add a gdbarch 'print_auxv_entry' method for FreeBSD ABIs sergiodj+buildbot
2016-06-24 23:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-25  1:36 [binutils-gdb] Support structure offsets that are 512K or larger sergiodj+buildbot
2016-06-25  1:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-25  6:25 [binutils-gdb] Make evaluation and type-printing of all NonZero optimized enums work sergiodj+buildbot
2016-06-25  6:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-25  7:24 [binutils-gdb] Add tests for printing of NonZero-optimized enums in Rust sergiodj+buildbot
2016-06-25  7:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-25 15:10 [binutils-gdb] Fix formatting in rust-lang.c sergiodj+buildbot
2016-06-25 15:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-25 16:01 [binutils-gdb] xtensa: prototype xtensa_make_property_section in elf/xtensa.h sergiodj+buildbot
2016-06-25 16:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-25 16:48 [binutils-gdb] remove a few sentinals sergiodj+buildbot
2016-06-25 17:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-27 10:18 [binutils-gdb] dlx: move prototype of dlx_set_skip_hi16 to elf/dlx.h sergiodj+buildbot
2016-06-27 10:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-27 10:42 [binutils-gdb] Fix use of a dangling pointer for Python breakpoint objects sergiodj+buildbot
2016-06-27 11:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-27 17:03 [binutils-gdb] Print void types correctly in Rust sergiodj+buildbot
2016-06-27 17:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28  0:55 [binutils-gdb] MIPS16: Add R_MIPS16_PC16_S1 branch relocation support sergiodj+buildbot
2016-06-28  1:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28  8:38 [binutils-gdb] [AArch64] Make register indices be full 64-bit values sergiodj+buildbot
2016-06-28  8:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28 11:18 [binutils-gdb] Don't convert R_SPARC_32 to R_SPARC_RELATIVE if class is ELFCLASS64 sergiodj+buildbot
2016-06-28 11:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28 13:01 [binutils-gdb] Remove parameter sysret from linux_target_ops.get_syscall_trapinfo sergiodj+buildbot
2016-06-28 13:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28 14:32 [binutils-gdb] Implement get_syscall_trapinfo for arm-linux sergiodj+buildbot
2016-06-28 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28 15:00 [binutils-gdb] Mark ARM mapping symbols in object files are precious, so that strip will not remove them sergiodj+buildbot
2016-06-28 17:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28 16:19 [binutils-gdb] Fix typo in previous commit sergiodj+buildbot
2016-06-28 18:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-28 17:17 [binutils-gdb] [AArch64] Use int64_t for address offset sergiodj+buildbot
2016-06-28 20:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 10:35 [binutils-gdb] Preserve all mapping symbols in ARM and AArch64 object files sergiodj+buildbot
2016-06-29 11:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 11:32 [binutils-gdb] Use strtok_r instead of strsep in rust_get_disr_info sergiodj+buildbot
2016-06-29 12:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 12:11 [binutils-gdb] sparc: make SPARC_OPCODE_ARCH_MAX part of its enum sergiodj+buildbot
2016-06-29 12:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 14:20 [binutils-gdb] Set unknown_syscall differently on arm linux sergiodj+buildbot
2016-06-29 14:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 14:59 [binutils-gdb] Initialize strtok_r's saveptr to NULL sergiodj+buildbot
2016-06-29 15:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 16:36 [binutils-gdb] PR gdb/17210 - fix possible memory leak in read_memory_robust sergiodj+buildbot
2016-06-29 16:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 16:58 [binutils-gdb] Fix PR python/20129 - use of non-existing variable sergiodj+buildbot
2016-06-29 17:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-29 18:30 [binutils-gdb] Add copyright header in gdb.base/return.c sergiodj+buildbot
2016-06-29 18:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-30  8:28 [binutils-gdb] Add support for simulating big-endian AArch64 binaries sergiodj+buildbot
2016-06-30  8:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-30 10:07 [binutils-gdb] [ARM][GAS] ARMv8.2 should enable ARMv8.1 NEON instructions sergiodj+buildbot
2016-06-30 10:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-06-30 11:43 [binutils-gdb] Fix gdbserver/MI testing regression sergiodj+buildbot
2016-06-30 12:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01  7:09 [binutils-gdb] x86/Intel: fix operand checking for MOVSD sergiodj+buildbot
2016-07-01  7:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01  7:49 [binutils-gdb] x86: remove stray instruction attributes sergiodj+buildbot
2016-07-01  8:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01  8:42 [binutils-gdb] x86: allow suffix-less movzw and 64-bit movzb sergiodj+buildbot
2016-07-01  9:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 10:53 [binutils-gdb] Factor out "Detaching from program" message printing sergiodj+buildbot
2016-07-01 11:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 11:56 [binutils-gdb] Forget watchpoint locations when inferior exits or is killed/detached sergiodj+buildbot
2016-07-01 11:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 12:41 [binutils-gdb] Fix failure to detach if process exits while detaching on Linux sergiodj+buildbot
2016-07-01 13:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 12:59 [binutils-gdb] Extend JIT-reader test and fix GDB problems that exposes sergiodj+buildbot
2016-07-01 14:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 14:59 [binutils-gdb] Consolidate x86 debug register code for BSD native targets sergiodj+buildbot
2016-07-01 15:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 15:50 [binutils-gdb] Set debug registers on all threads belonging to the current inferior sergiodj+buildbot
2016-07-01 16:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 16:41 [binutils-gdb] Fix Thumb-2 BL detection sergiodj+buildbot
2016-07-01 16:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 17:17 [binutils-gdb] Honor detach-on-fork on FreeBSD sergiodj+buildbot
2016-07-01 17:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 18:48 [binutils-gdb] Fake VFORK_DONE events when following only the parent after a vfork sergiodj+buildbot
2016-07-01 19:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 19:44 [binutils-gdb] [AArch64] Fix +nofp16 handling sergiodj+buildbot
2016-07-01 20:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-01 19:49 [binutils-gdb] Optimize memory_xfer_partial for remote sergiodj+buildbot
2016-07-01 21:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-05  9:02 [binutils-gdb] babeltrace compilation regression sergiodj+buildbot
2016-07-05  9:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-05 11:42 [binutils-gdb] [ARM] Purecode compatible long branch veneer for M-profile targets with MOVW sergiodj+buildbot
2016-07-05 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-05 14:06 [binutils-gdb] Fix fail in gdb.mi/mi-reverse.exp sergiodj+buildbot
2016-07-05 14:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06  5:38 [binutils-gdb] Allow subscripting raw pointers sergiodj+buildbot
2016-07-06  5:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06  7:38 [binutils-gdb] [ARM] Fix endless recursion on calculating CPRC candidate sergiodj+buildbot
2016-07-06  7:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06 13:45 [binutils-gdb] Remove check for negative size sergiodj+buildbot
2016-07-06 14:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06 14:25 [binutils-gdb] Set uses_fp for frames with a valid FP register explicitly sergiodj+buildbot
2016-07-06 15:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06 15:28 [binutils-gdb] Use unsigned integer constant with left shifts sergiodj+buildbot
2016-07-06 16:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06 15:43 [binutils-gdb] Remove extraneous parentheses sergiodj+buildbot
2016-07-06 17:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06 16:12 [binutils-gdb] Remove extra output directory level for Ada tests sergiodj+buildbot
2016-07-06 18:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-06 17:08 [binutils-gdb] gdb.ada/arraydim.exp: Fix directory layout sergiodj+buildbot
2016-07-06 19:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-07 15:52 [binutils-gdb] Fix of default lookup for "this" symbol sergiodj+buildbot
2016-07-07 16:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-07 17:47 [binutils-gdb] [obv] Fix broken build on Fedora 23 sergiodj+buildbot
2016-07-07 17:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-08 19:25 [binutils-gdb] FT32: adjust disassembly opcode match fields sergiodj+buildbot
2016-07-08 19:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-11 14:19 [binutils-gdb] Fixes done to TLS sergiodj+buildbot
2016-07-11 14:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-11 14:57 [binutils-gdb] Enable relocation overflow messages by default sergiodj+buildbot
2016-07-11 15:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-12 10:20 [binutils-gdb] Fix grammar in error message sergiodj+buildbot
2016-07-12 10:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-12 13:25 [binutils-gdb] Add type casts to allow C++ compile sergiodj+buildbot
2016-07-12 13:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-12 15:23 [binutils-gdb] Second fix for grammar in error message sergiodj+buildbot
2016-07-12 16:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-12 20:41 [binutils-gdb] PR python/19293 - invalidate frame cache when unwinders change sergiodj+buildbot
2016-07-12 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-12 23:02 [binutils-gdb] Align x86-64 .got/.got.plt sections to 8 bytes sergiodj+buildbot
2016-07-12 23:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-13 14:28 [binutils-gdb] opcodes, gas: support for the ldtxa SPARC instructions sergiodj+buildbot
2016-07-13 14:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-13 17:04 [binutils-gdb] MIPS/opcodes: Address issues with NAL disassembly sergiodj+buildbot
2016-07-13 17:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-13 19:38 [binutils-gdb] Fix PR cli/18053 sergiodj+buildbot
2016-07-13 19:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-13 20:39 [binutils-gdb] use user_breakpoint_p in python code sergiodj+buildbot
2016-07-13 20:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-13 20:53 [binutils-gdb] PR python/17698 - add Breakpoint.pending sergiodj+buildbot
2016-07-13 22:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-14  9:52 [binutils-gdb] Small improvements to the ARM simulator to cope with illegal binaries sergiodj+buildbot
2016-07-14 10:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-14 17:26 [binutils-gdb] Add one use of ATTRIBUTE_UNUSED sergiodj+buildbot
2016-07-14 18:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-14 17:32 [binutils-gdb] Change reopen_exec_file to check result of stat sergiodj+buildbot
2016-07-14 17:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-14 20:44 [binutils-gdb] Add missing newline to py-breakpoint.c sergiodj+buildbot
2016-07-14 23:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-14 21:08 [binutils-gdb] Remove some variables but call functions for side effects sergiodj+buildbot
2016-07-14 21:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-14 21:44 [binutils-gdb] BFD: Let targets handle relocations against absolute symbols sergiodj+buildbot
2016-07-15  0:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-15 10:05 [binutils-gdb] COFF buffer overflow in mark_relocs sergiodj+buildbot
2016-07-15 10:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-15 11:25 [binutils-gdb] Tidy up debugging in the ARC port of the BFD library sergiodj+buildbot
2016-07-15 11:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-15 14:01 [binutils-gdb] Pass SIGLIBRT directly to child processes sergiodj+buildbot
2016-07-15 14:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-15 18:48 [binutils-gdb] GDB testsuite: Escape paths used in regular expressions sergiodj+buildbot
2016-07-15 18:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-16 14:06 [binutils-gdb] Don't include libbfd.h outside of bfd, part 2 sergiodj+buildbot
2016-07-16 14:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-16 15:07 [binutils-gdb] Don't include libbfd.h outside of bfd, part 6 sergiodj+buildbot
2016-07-16 16:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-19  8:17 [binutils-gdb] Update PC when simulate break instruction sergiodj+buildbot
2016-07-19  8:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-19 10:01 [binutils-gdb] Use do_self_tests in selftest.exp sergiodj+buildbot
2016-07-19 10:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-19 14:34 [binutils-gdb] MIPS: Verify the ISA mode and alignment of branch and jump targets sergiodj+buildbot
2016-07-19 15:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-19 16:20 [binutils-gdb] MIPS: Convert cross-mode BAL to JALX sergiodj+buildbot
2016-07-19 16:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-19 18:00 [binutils-gdb] Build gdb.opt/inline-*.exp tests at -O0, rely on __attribute__((always_inline)) sergiodj+buildbot
2016-07-19 18:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20  4:10 [binutils-gdb] Mark some more powerpc relocs as not handled by generic linker sergiodj+buildbot
2016-07-20  4:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 15:41 [binutils-gdb] testsuite patch: Skip py-unwind.exp on x86_64 -m32 sergiodj+buildbot
2016-07-20 15:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 16:06 [binutils-gdb] testsuite: Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32 sergiodj+buildbot
2016-07-20 17:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 17:08 [binutils-gdb] testsuite: Fix gdb.gdb/selftest.exp for C++-O2-g-built GDB sergiodj+buildbot
2016-07-20 17:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 18:26 [binutils-gdb] Check p_paddr for program header space sergiodj+buildbot
2016-07-20 18:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 20:07 [binutils-gdb] Consolidate code to enable optional FreeBSD native target event reporting sergiodj+buildbot
2016-07-20 22:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 20:22 [binutils-gdb] Enable ptrace events on new child processes sergiodj+buildbot
2016-07-20 23:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-20 21:44 [binutils-gdb] Use a real vfork done event on FreeBSD when available sergiodj+buildbot
2016-07-21  0:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21  4:17 [binutils-gdb] Fix implib test failures sergiodj+buildbot
2016-07-21  6:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 10:51 [binutils-gdb] Use fsqrt() to calculate float (rather than double) square root sergiodj+buildbot
2016-07-21 11:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 11:10 [binutils-gdb] Skip gdb.server/ tests if lack of XML support sergiodj+buildbot
2016-07-21 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 12:41 [binutils-gdb] Create sub classes of 'struct breakpoint' sergiodj+buildbot
2016-07-21 14:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 13:37 [binutils-gdb] Refactor clone_all_breakpoints sergiodj+buildbot
2016-07-21 15:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 14:36 [binutils-gdb] Make reinsert_breakpoint thread specific sergiodj+buildbot
2016-07-21 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 14:58 [binutils-gdb] Switch current_thread to lwp's thread in install_software_single_step_breakpoints sergiodj+buildbot
2016-07-21 17:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 15:20 [binutils-gdb] Use enqueue_pending_signal in linux_resume_one_thread sergiodj+buildbot
2016-07-21 18:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 15:58 [binutils-gdb] Enqueue signal even when resuming threads sergiodj+buildbot
2016-07-21 19:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 17:08 [binutils-gdb] Use reinsert_breakpoint for vCont;s sergiodj+buildbot
2016-07-21 21:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 17:54 [binutils-gdb] Support vCont s and S actions with software single step sergiodj+buildbot
2016-07-21 22:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 18:25 [binutils-gdb] Fix cast to 'gdb_breakpoint *' sergiodj+buildbot
2016-07-21 23:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 19:45 [binutils-gdb] Remove unused variable in windows-nat.c sergiodj+buildbot
2016-07-22  1:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-21 20:40 [binutils-gdb] Fix djgpp gdb build sergiodj+buildbot
2016-07-22  2:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-22  0:11 [binutils-gdb] Set BFD_VERSION to 2.27.51 sergiodj+buildbot
2016-07-22  5:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-22  3:02 [binutils-gdb] Allow empty struct expressions in Rust sergiodj+buildbot
2016-07-22  4:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-22 16:29 [binutils-gdb] Fix segfault in ARC linker when generating got entries for local symbols sergiodj+buildbot
2016-07-22 16:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-22 17:58 [binutils-gdb] Get "num" as unsigned in ctf sergiodj+buildbot
2016-07-22 18:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-07-23 19:48 [binutils-gdb] Fix ARMv8.1/v8.2 for hw watchpoint and breakpoint sergiodj+buildbot
2016-07-23 22:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
     [not found] <e34879080d8935792ef3942efa5f25b4c3169b5a@gdb-build>
2016-07-24  4:11 ` sergiodj+buildbot
     [not found] <c0272db5854a799a9f3bb3803c3d03d1a62b9ac2@gdb-build>
2016-07-25 11:24 ` sergiodj+buildbot
     [not found] <3a1518e4f3c467cfee2786b0af3388529f14d23b@gdb-build>
2016-07-25 17:40 ` sergiodj+buildbot
     [not found] <0e1a6a5169023ee0c19de2c9160b469e43634b21@gdb-build>
2016-07-26  6:33 ` sergiodj+buildbot
     [not found] <e0461dbb653dbb3c46ea7a15054fd2c98f879f31@gdb-build>
2016-07-26 19:11 ` sergiodj+buildbot
     [not found] <9cf12d57c58a82cfe3e6fee26d1ea55dfe49f9c4@gdb-build>
2016-07-26 21:20 ` sergiodj+buildbot
     [not found] <40c31709c6a51926fcb409611caa52b2da6515c0@gdb-build>
2016-07-26 22:14 ` sergiodj+buildbot
     [not found] <54806ffa85643c3a1ee721d5c3f5586d32f86ee1@gdb-build>
2016-07-27  0:21 ` sergiodj+buildbot
     [not found] <6598661d14c90cabac1daa5e683d1e17883b2e41@gdb-build>
2016-07-27  3:43 ` sergiodj+buildbot
     [not found] <293acfae4e3c9aad417e262edc9847c79bbbbb11@gdb-build>
2016-07-27  5:15 ` sergiodj+buildbot
     [not found] <147d994bcdd36a177e49e7b6ac8d9c1f7b4cdcf5@gdb-build>
2016-07-27 14:41 ` sergiodj+buildbot
     [not found] <db18dbabad8e7b63e98d47813ef20acac7072350@gdb-build>
2016-07-27 17:53 ` sergiodj+buildbot
     [not found] <7bd374a44d1db21b54a9a52ecde1d064cdaa8cd1@gdb-build>
2016-07-28  1:01 ` sergiodj+buildbot
2016-08-01  9:52 [binutils-gdb] Tweak gdb.cp tests for aarch32 sergiodj+buildbot
2016-08-01 10:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-01 10:35 [binutils-gdb] Update Swedish translation in bfd directory sergiodj+buildbot
2016-08-01 10:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-01 17:20 [binutils-gdb] Bump version to 7.12.50.DATE-git sergiodj+buildbot
2016-08-01 18:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-01 18:17 [binutils-gdb] Update NEWS post GDB 7.12 branch creation sergiodj+buildbot
2016-08-01 19:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-01 21:12 [binutils-gdb] Fix some PowerPC VLE BFD issues and add some PowerPC VLE instructions sergiodj+buildbot
2016-08-02  2:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-02 12:23 [binutils-gdb] Fix SH GOT allocation in the presence of linker garbage collection sergiodj+buildbot
2016-08-02 12:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-02 14:43 [binutils-gdb] Synchronize libiberty sources with FSF GCC mainline version sergiodj+buildbot
2016-08-02 14:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-02 16:45 [binutils-gdb] [GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg sergiodj+buildbot
2016-08-02 19:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-03 16:11 [binutils-gdb] Add myself as Rust maintainer sergiodj+buildbot
2016-08-03 16:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-03 17:44 [binutils-gdb] Update NEWS to mention Python breakpoint events sergiodj+buildbot
2016-08-03 18:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-04 10:44 [binutils-gdb] Quiet ptrace error ESRCH in regsets_fetch_inferior_registers sergiodj+buildbot
2016-08-04 10:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-04 11:45 [binutils-gdb] Determine target description for native aarch64 sergiodj+buildbot
2016-08-04 12:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-04 16:49 [binutils-gdb] 2016-08-04 Thomas Preud'homme <thomas.preudhomme@arm.com> sergiodj+buildbot
2016-08-04 19:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-05 17:17 [binutils-gdb] gdb/configure --help: suggest --disable-build-with-cxx instead of --enable sergiodj+buildbot
2016-08-05 17:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-05 18:21 [binutils-gdb] gdb/NEWS: Mention that C++ is now the default sergiodj+buildbot
2016-08-05 19:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-05 22:57 [binutils-gdb] Remove unused cli_command_loop declaration sergiodj+buildbot
2016-08-06  2:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-08 16:36 [binutils-gdb] Fix memory leaks in chew program sergiodj+buildbot
2016-08-08 17:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-09  7:29 [binutils-gdb] Regenerate some target description files sergiodj+buildbot
2016-08-09  7:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-09 13:06 [binutils-gdb] linux-procfs: Introduce enum proc_state sergiodj+buildbot
2016-07-26  3:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-09 13:28 [binutils-gdb] Handle correctly passing a bad interpreter name to new-ui sergiodj+buildbot
2016-07-26 12:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-09 13:36 [binutils-gdb] Fix PR gdb/20295: GDB segfaults printing bitfield member of optimized out value sergiodj+buildbot
2016-08-09 13:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-09 13:48 [binutils-gdb] PR python/20190 - compute TLS symbol without a frame sergiodj+buildbot
2016-07-27  1:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-09 22:30 [binutils-gdb] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions sergiodj+buildbot
2016-08-09 22:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-10  0:26 [binutils-gdb] Fix PR mi/20431 - Missing MI prompts after sync execution MI command (-exec-continue, etc.) errors sergiodj+buildbot
2016-08-10  0:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-10  1:19 [binutils-gdb] Fix PR gdb/20418 - Problems with synchronous commands and new-ui sergiodj+buildbot
2016-08-10  1:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-10 21:20 [binutils-gdb] Quiet ARI gettext checks sergiodj+buildbot
2016-08-10 22:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11  0:35 [binutils-gdb] Support setting thread names (MS-Windows) sergiodj+buildbot
2016-08-11  0:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11  0:52 [binutils-gdb] MIPS/BFD: Set the ISA bit in microMIPS LA25 stub references sergiodj+buildbot
2016-08-11  1:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11  1:15 [binutils-gdb] MIPS/BFD: Add microMIPS annotation to LA25 stub symbols sergiodj+buildbot
2016-08-11  1:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11  5:30 [binutils-gdb] Simplify remove_breakpoint interface sergiodj+buildbot
2016-08-11 16:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11  7:55 [binutils-gdb] Fix PR gdb/19187 (process record over a fork causes internal error) sergiodj+buildbot
2016-08-12  0:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11  8:00 [binutils-gdb] Introduce 'enum remove_bp_reason' sergiodj+buildbot
2016-08-11 22:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-11 10:04 [binutils-gdb] PowerPC64 ELFv1 undefined weak functions sergiodj+buildbot
2016-08-12  1:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-12 10:33 [binutils-gdb] Fix fallout from gdb/20413's fix (x32: linux_ptrace_test_ret_to_nx: Cannot PTRACE_PEEKUSER) sergiodj+buildbot
2016-08-12 11:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-12 11:02 [binutils-gdb] Export the single step function from the AArch64 simulator sergiodj+buildbot
2016-08-12 12:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-12 13:46 [binutils-gdb] Fix warning in gdb.base/signals-state-child.c sergiodj+buildbot
2016-08-12 14:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-12 18:13 [binutils-gdb] Undo the previous change to the aarch64 sim - exporting aarch64_step() - and instead make aarch64_run correctly process sim events sergiodj+buildbot
2016-08-13 20:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-13 21:55 [binutils-gdb] Correct .dynsym sh_info sergiodj+buildbot
2016-08-13 21:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-14  1:05 [binutils-gdb] sim: bfin: split out common mach/model defines into arch.h [PR sim/20438] sergiodj+buildbot
2016-08-14  6:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-14  7:01 [binutils-gdb] sim: cgen: drop unused argv/envp definitions sergiodj+buildbot
2016-08-14 11:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-15 12:16 [binutils-gdb] sim: cgen: constify mode_names sergiodj+buildbot
2016-08-15 12:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-15 14:48 [binutils-gdb] Fix heap-buffer-overflow in explicit_location_lex_one sergiodj+buildbot
2016-08-15 14:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-17 21:25 [binutils-gdb] sim: m68hc11: use standard STATIC_INLINE helper sergiodj+buildbot
2016-08-17 21:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-18 14:37 [binutils-gdb] Add remove-inferiors test sergiodj+buildbot
2016-08-18 14:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-18 15:13 [binutils-gdb] Fix remove-inferior error message sergiodj+buildbot
2016-08-18 17:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-18 21:19 [binutils-gdb] ppc: Fix record of HTM instructions sergiodj+buildbot
2016-08-18 21:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19  5:31 [binutils-gdb] Add myself as write-after-approval GDB maintainer sergiodj+buildbot
2016-08-19  8:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 12:02 [binutils-gdb] PR 20472, PowerPC64 ifunc confusion sergiodj+buildbot
2016-08-19 12:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 12:40 [binutils-gdb] PowerPC64, Don't copy weak symbol dyn_relocs to weakdef sergiodj+buildbot
2016-08-19 13:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 14:59 [binutils-gdb] Place .shstrtab section after .symtab and .strtab, thus restoring monotonically increasing section offsets sergiodj+buildbot
2016-08-19 15:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 16:06 [binutils-gdb] x32 Fast tracepoints: IPA target descriptions sergiodj+buildbot
2016-08-19 16:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 16:23 [binutils-gdb] x32 Fast tracepoints: Customize jump pad address sergiodj+buildbot
2016-08-19 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 16:52 [binutils-gdb] x32: gdbserver's agent bytecode JIT: fix "call" emission sergiodj+buildbot
2016-08-19 17:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 17:02 [binutils-gdb] x32: Avoid unsigned long when installing fast tracepoint jump pads sergiodj+buildbot
2016-08-19 17:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 18:19 [binutils-gdb] x32: gdb: Fix 'call' insn relocation with qRelocInsn sergiodj+buildbot
2016-08-19 19:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-19 19:59 [binutils-gdb] [AArch64] Match instruction "STP with base register" in prologue sergiodj+buildbot
2016-08-20  8:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-22 20:15 [binutils-gdb] Error on unsupported PowerPC ifuncs sergiodj+buildbot
2016-08-22 20:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-22 21:15 [binutils-gdb] Free the string buffer used by the chew program to hold each file it parses sergiodj+buildbot
2016-08-22 23:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23  4:03 [binutils-gdb] Fix PR gdb/20505 - Make vDSO detection work with core files sergiodj+buildbot
2016-08-23  4:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23 13:28 [binutils-gdb] R_OR1K_GOTOFF_* relocations sergiodj+buildbot
2016-08-23 13:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23 14:15 [binutils-gdb] [AArch64] Add OP parameter to aarch64-tbl.h macros sergiodj+buildbot
2016-08-23 14:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23 14:27 [binutils-gdb] [AArch64] Make more use of CORE/FP/SIMD_INSN sergiodj+buildbot
2016-08-23 15:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23 15:22 [binutils-gdb] Fix seg-fault in ARM linker when trying to parse a binary file sergiodj+buildbot
2016-08-23 16:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23 16:22 [binutils-gdb] Fix signals-state-child.exp in remote testing sergiodj+buildbot
2016-08-23 17:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-23 17:39 [binutils-gdb] gdbserver_spawn "" rather than gdbserver_spawn ${binfile} sergiodj+buildbot
2016-08-23 22:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-24 18:02 [binutils-gdb] [ARC] Parse NOTE section in core dump files sergiodj+buildbot
2016-08-24 18:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-24 18:43 [binutils-gdb] Fix for gdb.base/pc-fp.exp sergiodj+buildbot
2016-08-24 18:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-24 20:24 [binutils-gdb] Allow resetting an empty inferior-tty sergiodj+buildbot
2016-08-24 21:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-25  7:58 [binutils-gdb] Test case to detect recursive unwinding in Python-based unwinders sergiodj+buildbot
2016-08-25  7:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-25  8:11 [binutils-gdb] X86: Add ptwrite instruction sergiodj+buildbot
2016-08-25  8:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-25 10:27 [binutils-gdb] Sync proc_service definition with GLIBC sergiodj+buildbot
2016-08-25 12:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 10:59 [binutils-gdb] xtensa: Avoid designated inits, for C++ compliance sergiodj+buildbot
2016-08-26 11:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 11:41 [binutils-gdb] S390: Indentation fixes in elf32/64-s390.c sergiodj+buildbot
2016-08-26 12:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 15:04 [binutils-gdb] Add support for stable secure gateway veneers addresses sergiodj+buildbot
2016-08-26 14:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 15:37 [binutils-gdb] Fixes to legacy ARC relocations sergiodj+buildbot
2016-08-26 15:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 15:56 [binutils-gdb] Several fixes related to ARC PIE support sergiodj+buildbot
2016-08-26 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 16:13 [binutils-gdb] Content for TLS_IE_GOT not written to .got sergiodj+buildbot
2016-08-26 16:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 16:28 [binutils-gdb] Fixed -init, -fini linker options sergiodj+buildbot
2016-08-26 18:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 17:24 [binutils-gdb] Dynamic TLS GOT entries would not be relocated sergiodj+buildbot
2016-08-26 19:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 17:28 [binutils-gdb] Add missing ARMv8-M special registers sergiodj+buildbot
2016-08-26 22:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-26 20:45 [binutils-gdb] Reduce parameter list in bfd_elf32_arm_target_relocs sergiodj+buildbot
2016-08-27  5:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-27  0:57 [binutils-gdb] opcodes, gas: fix mnemonic of sparc camellia_fl sergiodj+buildbot
2016-08-27  6:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-27  2:17 [binutils-gdb] 2016-08-26 Thomas Preud'homme <thomas.preudhomme@arm.com> sergiodj+buildbot
2016-08-27  2:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-27 12:09 [binutils-gdb] Fix commit 980aa3e6 sergiodj+buildbot
2016-08-27 12:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-27 13:37 [binutils-gdb] Lack of SHF_GROUP sections result in ld segfault sergiodj+buildbot
2016-08-29 13:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-30  6:44 [binutils-gdb] gdb.base/default.exp regression sergiodj+buildbot
2016-08-30 11:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-30 16:56 [binutils-gdb] i386: Issue an error on non-PIC call to IFUNC in PIC object sergiodj+buildbot
2016-08-30 17:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-30 18:41 [binutils-gdb] ppc apuinfo for spe parsed incorrectly sergiodj+buildbot
2016-08-30 18:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-31  4:17 [binutils-gdb] Fix order of inferiors in "thread apply all" sergiodj+buildbot
2016-08-31  4:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-31  5:42 [binutils-gdb] Fixed issue with NULL pointer access on header var sergiodj+buildbot
2016-08-31  7:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-31 18:21 [binutils-gdb] PowerPC VLE sh_flags and p_flags sergiodj+buildbot
2016-08-31 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-08-31 20:01 [binutils-gdb] Fix a typo in comment sergiodj+buildbot
2016-08-31 20:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-01  7:16 [binutils-gdb] Fix lwp_suspend/unsuspend imbalance in linux_wait_1 sergiodj+buildbot
2016-09-01  7:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-01 20:40 [binutils-gdb] Don't treat .opd section specially when ELFv2 sergiodj+buildbot
2016-09-01 20:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-01 21:43 [binutils-gdb] 2016-09-01 Thomas Preud'homme <thomas.preudhomme@arm.com> sergiodj+buildbot
2016-09-01 23:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-02  9:02 [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume sergiodj+buildbot
2016-09-02  9:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-02 14:53 [binutils-gdb] Share target_wait prototype between GDB and gdbserver sergiodj+buildbot
2016-09-02 16:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-02 17:12 [binutils-gdb] Detect broken ptrace in gdb_skip_float_test sergiodj+buildbot
2016-09-02 18:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-02 19:40 [binutils-gdb] Skip floating point tests in return-nodebug.exp if gdb_skip_float_test is true sergiodj+buildbot
2016-09-02 19:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-02 22:03 [binutils-gdb] [GDBserver] Replace "reinsert_breakpoint" with "single_step_breakpoint" sergiodj+buildbot
2016-09-03 11:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-03 12:46 [binutils-gdb] Handle DW_OP_form_tls_address sergiodj+buildbot
2016-09-03 19:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-05 19:41 [binutils-gdb] Removed redundant line remote-utils.c sergiodj+buildbot
2016-09-05 20:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06  8:12 [binutils-gdb] Fix PR19927: Avoid unwinder recursion if sniffer uses calls parse_and_eval sergiodj+buildbot
2016-09-06  8:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 16:28 [binutils-gdb] gdb/: Require a C++ compiler sergiodj+buildbot
2016-09-06 17:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 18:54 [binutils-gdb] Fix typo in ada_language_arch_info sergiodj+buildbot
2016-09-06 19:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 19:59 [binutils-gdb] Fix TYPE_SPECIFIC_FIELD for types created via arch_type sergiodj+buildbot
2016-09-06 20:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 20:46 [binutils-gdb] Add some missing arch_..._type helpers sergiodj+buildbot
2016-09-06 22:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 22:01 [binutils-gdb] Remove obsolete TYPE_FLAG_... values sergiodj+buildbot
2016-09-07  0:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 23:33 [binutils-gdb] Remove TYPE_NOSIGN "char" hack sergiodj+buildbot
2016-09-07  1:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-06 23:37 [binutils-gdb] Add missing format for built-in floating-point types sergiodj+buildbot
2016-09-07  6:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-07  0:39 [binutils-gdb] Support 128-bit IEEE floating-point types on Intel and Power sergiodj+buildbot
2016-09-07 10:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-07  1:30 [binutils-gdb] Resolve size relocation with copy relocation sergiodj+buildbot
2016-09-07 13:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-07  5:56 [binutils-gdb] Introduce make_cleanup_restore_current_ui sergiodj+buildbot
2016-09-07 17:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-07  7:09 [binutils-gdb] new-ui command: gdb internal errors if input is already pending sergiodj+buildbot
2016-09-07 18:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-07 21:00 [binutils-gdb] [arm] Automatically enable CRC instructions on supported ARMv8-A CPUs sergiodj+buildbot
2016-09-07 20:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-10 20:57 [binutils-gdb] Remove some unneeded casts from remote.c sergiodj+buildbot
2016-09-10 20:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-10 23:25 [binutils-gdb] Pass HWCAP to ifunc resolver sergiodj+buildbot
2016-09-12  5:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-12 15:28 [binutils-gdb] Use target_sim_options for sim target sergiodj+buildbot
2016-09-12 15:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-12 17:26 [binutils-gdb] Fix false FAIL on gdb.base/stap-probe.exp, due to ICF optimization sergiodj+buildbot
2016-09-12 17:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-13 17:42 [binutils-gdb] S/390: Fix kmctr instruction type sergiodj+buildbot
2016-09-13 17:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-13 18:36 [binutils-gdb] S/390: Add alternate processor names sergiodj+buildbot
2016-09-13 20:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-14 12:25 [binutils-gdb] Fix for gdb.server/non-existing-program.exp test case sergiodj+buildbot
2016-09-14 12:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-14 13:01 [binutils-gdb] Fix for gdb.server/non-existing-program.exp test case sergiodj+buildbot
2016-09-14 14:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-14 16:07 [binutils-gdb] Stop the ARC disassembler from seg-faulting if initialised without a BFD present sergiodj+buildbot
2016-09-14 16:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-14 17:34 [binutils-gdb] Prevent segfault in GDB when searching for architecture matches sergiodj+buildbot
2016-09-14 17:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-15  4:45 [binutils-gdb] Fix ld --gc-section segfault with ARMv8-M entry function in absolute section sergiodj+buildbot
2016-09-15 12:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-15 21:47 [binutils-gdb] Modify POWER9 support to match final ISA 3.0 documentation sergiodj+buildbot
2016-09-15 22:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-15 23:31 [binutils-gdb] testsuite: Disable ccache sergiodj+buildbot
2016-09-15 23:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-16 18:19 [binutils-gdb] testsuite: Fix C++11 compilation failure for gdb.cp/m-static.exp sergiodj+buildbot
2016-09-16 18:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-16 19:43 [binutils-gdb] [ARC] Disassemble correctly extension instructions sergiodj+buildbot
2016-09-16 19:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-16 20:49 [binutils-gdb] testsuite: Fix false FAIL in gdb.cp/casts.exp sergiodj+buildbot
2016-09-16 21:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-16 22:36 [binutils-gdb] S390: Migrate watch areas from list to VEC type sergiodj+buildbot
2016-09-17  0:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-16 23:12 [binutils-gdb] S390: Multi-inferior watchpoint support sergiodj+buildbot
2016-09-17  1:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-17  0:28 [binutils-gdb] linux-nat: Add function lwp_is_stepping sergiodj+buildbot
2016-09-17  8:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-17  1:02 [binutils-gdb] S390: Hardware breakpoint support sergiodj+buildbot
2016-09-17 10:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-19  6:16 [binutils-gdb] gdb: Fix std::{min, max}-related build breakage on 32-bit hosts sergiodj+buildbot
2016-09-19 13:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-19 12:42 [binutils-gdb] gdb/s390: Fix build breakage due to std::min/std::max usage without header sergiodj+buildbot
2016-09-19 15:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-19 16:45 [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver sergiodj+buildbot
2016-09-19 17:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-20  9:06 [binutils-gdb] gdb: Fix build breakage with GCC 4.1 and --disable-nls sergiodj+buildbot
2016-09-20  8:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-20 17:47 [binutils-gdb] Use 'event_ptid' instead of 'resume_ptid' on startup_inferior (fix for regression on my last commit) sergiodj+buildbot
2016-09-20 17:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-20 20:52 [binutils-gdb] ppc: Fix record support of Store String Word instructions sergiodj+buildbot
2016-09-20 20:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 15:44 [binutils-gdb] Keep reserved bits in CPSR on write sergiodj+buildbot
2016-09-21 15:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 17:21 [binutils-gdb] MIPS/testsuite: mips16-thunks: Use `standard_output_file' sergiodj+buildbot
2016-09-21 18:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 19:48 [binutils-gdb] [AArch64][SVE 02/32] Avoid hard-coded limit in indented_print sergiodj+buildbot
2016-09-21 20:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 20:22 [binutils-gdb] [AArch64][SVE 13/32] Add an F_STRICT flag sergiodj+buildbot
2016-09-21 21:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 21:23 [binutils-gdb] [AArch64][SVE 14/32] Make aarch64_logical_immediate_p take an element size sergiodj+buildbot
2016-09-21 23:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 21:52 [binutils-gdb] [AArch64][SVE 15/32] Add {insert, extract}_all_fields helpers sergiodj+buildbot
2016-09-22  0:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-21 23:40 [binutils-gdb] [AArch64][SVE 17/32] Add a prefix parameter to print_register_list sergiodj+buildbot
2016-09-22  3:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  0:34 [binutils-gdb] [AArch64][SVE 18/32] Tidy definition of aarch64-opc.c:int_reg sergiodj+buildbot
2016-09-22  5:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  1:25 [binutils-gdb] [AArch64][SVE 19/32] Refactor address-printing code sergiodj+buildbot
2016-09-22  6:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  2:10 [binutils-gdb] [AArch64][SVE 20/32] Add support for tied operands sergiodj+buildbot
2016-09-22  8:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  2:34 [binutils-gdb] [AArch64][SVE 21/32] Add Zn and Pn registers sergiodj+buildbot
2016-09-22 10:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  4:21 [binutils-gdb] [AArch64][SVE 22/32] Add qualifiers for merging and zeroing predication sergiodj+buildbot
2016-09-22 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  4:41 [binutils-gdb] [AArch64][SVE 23/32] Add SVE pattern and prfop operands sergiodj+buildbot
2016-09-22 13:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  5:23 [binutils-gdb] [AArch64][SVE 24/32] Add AARCH64_OPND_SVE_PATTERN_SCALED sergiodj+buildbot
2016-09-22 15:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  7:02 [binutils-gdb] [AArch64][SVE 26/32] Add SVE MUL VL addressing modes sergiodj+buildbot
2016-09-22 19:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  8:06 [binutils-gdb] [AArch64][SVE 27/32] Add SVE integer immediate operands sergiodj+buildbot
2016-09-22 19:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  8:08 [binutils-gdb] [AArch64][SVE 28/32] Add SVE FP immediate operands sergiodj+buildbot
2016-09-22 22:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22  9:31 [binutils-gdb] [AArch64][SVE 30/32] Add SVE instruction classes sergiodj+buildbot
2016-09-23  3:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22 11:51 [binutils-gdb] [AArch64] Add SVE condition codes sergiodj+buildbot
2016-09-23  7:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22 12:08 [binutils-gdb] [AArch64] Use "must" rather than "should" in error messages sergiodj+buildbot
2016-09-23  7:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22 12:46 [binutils-gdb] [AArch64] Print spaces after commas in addresses sergiodj+buildbot
2016-09-23  8:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-22 23:04 [binutils-gdb] Fix build breakage from commit 6ec2b2 sergiodj+buildbot
2016-09-23 15:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-23  0:46 [binutils-gdb] Close gdbserver in mi_gdb_exit sergiodj+buildbot
2016-09-23 16:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-23 19:06 [binutils-gdb] Delete relocations associatesd with deleted exidx entries sergiodj+buildbot
2016-09-23 20:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-23 20:08 [binutils-gdb] gdb: Replace operator new / operator new[] sergiodj+buildbot
2016-09-23 21:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-23 21:43 [binutils-gdb] Replace sprintf with xsnprintf in nat/linux-osdata.c sergiodj+buildbot
2016-09-23 23:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-23 22:27 [binutils-gdb] Remove some unnecessary code sergiodj+buildbot
2016-09-24  0:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-23 23:51 [binutils-gdb] Use std::string in break-catch-sig.c sergiodj+buildbot
2016-09-24  5:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-24  0:14 [binutils-gdb] Use std::string in cp-namespace.c sergiodj+buildbot
2016-09-24  9:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-24  2:55 [binutils-gdb] Use std::string, std::vector in rust-lang.c sergiodj+buildbot
2016-09-24 12:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-24  4:16 [binutils-gdb] Use std::vector in objfiles.c sergiodj+buildbot
2016-09-24 14:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-24  7:30 [binutils-gdb] Use std::string rather than dyn-string sergiodj+buildbot
2016-09-24 15:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-25  5:08 [binutils-gdb] Fix a use of target_mourn_inferior in windows-nat.c sergiodj+buildbot
2016-09-25  5:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-26 11:09 [binutils-gdb] Call debug_exit in linux_wait_1 sergiodj+buildbot
2016-09-26 15:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-26 16:58 [binutils-gdb] PowerPC .gnu.attributes sergiodj+buildbot
2016-09-26 17:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-26 19:24 [binutils-gdb] [ARC] ISA alignment sergiodj+buildbot
2016-09-26 20:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-26 22:57 [binutils-gdb] Fix the calculation of AMD64_PCRQUAD relocations sergiodj+buildbot
2016-09-27  2:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-27 11:34 [binutils-gdb] Detect the magic address of EXC_RETURN in ARM coretx-m profile sergiodj+buildbot
2016-09-27 11:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-28  0:56 [binutils-gdb] Ensure that the timestamp in PE/COFF headers is always initialised sergiodj+buildbot
2016-09-28  1:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-28 12:00 [binutils-gdb] Add archives and make stamps to the .gitignore file sergiodj+buildbot
2016-09-28 12:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-28 22:44 [binutils-gdb] [ARM] PR ld/20608 Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry sergiodj+buildbot
2016-09-28 22:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-28 23:53 [binutils-gdb] Fix seg-fault in the linker introduced by the previous delta sergiodj+buildbot
2016-09-29  0:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-29  6:35 [binutils-gdb] Fix PR 20345 - call_function_by_hand_dummy: Assertion `tp->thread_fsm == &sm->thread_fsm' failed sergiodj+buildbot
2016-09-29  6:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-29 21:17 [binutils-gdb] PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression sergiodj+buildbot
2016-09-29 21:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-30 10:59 [binutils-gdb] Update tests to account for the L operand being compulsory sergiodj+buildbot
2016-09-30 11:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-30 15:11 [binutils-gdb] Remove syntactic sugar sergiodj+buildbot
2016-09-30 16:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-09-30 19:17 [binutils-gdb] Add missing dependencies to BFD_H_FILES sergiodj+buildbot
2016-09-30 19:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-03 21:15 [binutils-gdb] Emit inferior, thread and frame selection events to all UIs sergiodj+buildbot
2016-10-03 21:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-03 22:01 [binutils-gdb] Add test for user context selection sync sergiodj+buildbot
2016-10-03 22:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05  8:44 [binutils-gdb] Clean up the XML files for ARM sergiodj+buildbot
2016-10-05  9:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05  9:01 [binutils-gdb] Simplify i386, amd64 and x32 expedite registers sergiodj+buildbot
2016-10-05  9:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05  9:34 [binutils-gdb] Regenerate some regformats/rs6000/*.dat files sergiodj+buildbot
2016-10-05 12:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05 11:11 [binutils-gdb] Update the path arm-*.xml files for aarch64 sergiodj+buildbot
2016-10-05 13:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05 14:41 [binutils-gdb] arc: Remove annoying debug message sergiodj+buildbot
2016-10-05 14:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05 16:25 [binutils-gdb] Skip complex types tests if gdb_skip_float_test sergiodj+buildbot
2016-10-05 16:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05 17:49 [binutils-gdb] PR symtab/20652 - fix psymbol_compare sergiodj+buildbot
2016-10-05 17:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05 19:49 [binutils-gdb] PR remote/20655 - small fix in handle_tracepoint_bkpts sergiodj+buildbot
2016-10-05 19:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-05 20:50 [binutils-gdb] testsuite: Fix recent GCC FAIL: gdb.arch/i386-signal.exp sergiodj+buildbot
2016-10-05 20:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06  0:04 [binutils-gdb] Don't use boolean OR in arithmetic expressions sergiodj+buildbot
2016-10-06  0:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06  0:52 [binutils-gdb] -Wimplicit-fallthrough error fixes sergiodj+buildbot
2016-10-06  1:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06  1:07 [binutils-gdb] -Wimplicit-fallthrough warning fixes sergiodj+buildbot
2016-10-06  3:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 11:32 [binutils-gdb] Make "end" field in feature specs required again sergiodj+buildbot
2016-10-06 12:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 12:17 [binutils-gdb] Fix a few gdb.base/jit-simple.exp problems sergiodj+buildbot
2016-10-06 13:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 13:14 [binutils-gdb] Fix PR11094: JIT breakpoint is not properly recreated on reruns sergiodj+buildbot
2016-10-06 14:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 15:03 [binutils-gdb] stack: fix gdb.dwarf2/dw2-undefined-ret-addr.exp regression sergiodj+buildbot
2016-10-06 17:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 16:49 [binutils-gdb] testsuite: solib-disc: Use `standard_output_file' sergiodj+buildbot
2016-10-06 19:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 17:15 [binutils-gdb] mips-tdep: Rearrange comments in `mips_pseudo_register_type' sergiodj+buildbot
2016-10-06 20:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 17:57 [binutils-gdb] mips-tdep: Make FCRs always 32-bit sergiodj+buildbot
2016-10-06 21:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 22:11 [binutils-gdb] frame.h: Forward-declare struct ui_out sergiodj+buildbot
2016-10-07  4:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 23:29 [binutils-gdb] gdb: Remove some C compiler support leftovers sergiodj+buildbot
2016-10-07  7:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-06 23:56 [binutils-gdb] Consolidate API of target_supports_multi_process sergiodj+buildbot
2016-10-07  8:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-07  2:07 [binutils-gdb] Pass link_info to _bfd_merge_private_bfd_data sergiodj+buildbot
2016-10-07 10:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-07  4:51 [binutils-gdb] Fix gdb.Value->python conversion for large unsigned ints sergiodj+buildbot
2016-10-07  6:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-07  7:33 [binutils-gdb] bfd_merge_private_bfd_data tidy sergiodj+buildbot
2016-10-07  9:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-09  0:26 [binutils-gdb] ui-out.c: Remove unused parameter to push_level sergiodj+buildbot
2016-10-09  0:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-10  9:44 [binutils-gdb] Remove v850_dbtrap_breakpoint_from_pc sergiodj+buildbot
2016-10-10  9:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-10 10:37 [binutils-gdb] Rename 'arch' by 'gdbarch' in m32c_gdbarch_init sergiodj+buildbot
2016-10-10 10:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-10 11:41 [binutils-gdb] Share enum arm_breakpoint_kinds sergiodj+buildbot
2016-10-10 11:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-11 10:42 [binutils-gdb] [AArch64] PR target/20666, fix wrong encoding of new introduced BFC pseudo sergiodj+buildbot
2016-10-11 11:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-11 15:00 [binutils-gdb] testsuite: Use standard_output_file sergiodj+buildbot
2016-10-11 15:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-11 17:27 [binutils-gdb] testsuite: Fix gdb.arch/powerpc-prologue.c compilation sergiodj+buildbot
2016-10-11 17:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-12 11:51 [binutils-gdb] [AArch64] Track FP registers in prologue analyzer sergiodj+buildbot
2016-10-12 12:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-12 13:32 [binutils-gdb] arc: Add evaluation of long jump targets sergiodj+buildbot
2016-10-12 15:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-12 15:51 [binutils-gdb] Fixup gdb.python/py-value.exp for bare-metal aarch64-elf sergiodj+buildbot
2016-10-12 17:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-12 16:00 [binutils-gdb] arc: Add support for Newlib sergiodj+buildbot
2016-10-12 16:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13  1:21 [binutils-gdb] Convert tid_range_parser and get_number_or_range to classes sergiodj+buildbot
2016-10-13  1:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13  2:25 [binutils-gdb] Change selttest.c to use use std::vector sergiodj+buildbot
2016-10-13  2:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13  2:59 [binutils-gdb] Turn wchar iterator into a class sergiodj+buildbot
2016-10-13  3:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13  4:50 [binutils-gdb] Remove unnecessary null_cleanup sergiodj+buildbot
2016-10-13  4:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13  5:24 [binutils-gdb] Use std::string in macho_symfile_read_all_oso sergiodj+buildbot
2016-10-13  5:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13 14:54 [binutils-gdb] Skip testing structures with floating points sergiodj+buildbot
2016-10-13 15:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-13 17:38 [binutils-gdb] ARI: Remove true/false checks sergiodj+buildbot
2016-10-13 18:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-14  7:30 [binutils-gdb] Include strings.h where available sergiodj+buildbot
2016-10-14  7:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-14 13:25 [binutils-gdb] Fix set sysroot command on AIX sergiodj+buildbot
2016-10-14 13:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-14 16:29 [binutils-gdb] Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h sergiodj+buildbot
2016-10-14 16:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-14 16:54 [binutils-gdb] FINAL/OVERRIDE: Define to empty on g++ < 4.7 sergiodj+buildbot
2016-10-14 17:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-17  9:46 [binutils-gdb] Sync libiberty sources with gcc mainline sergiodj+buildbot
2016-10-17  9:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-17 11:03 [binutils-gdb] Update list of ELF machine numbers sergiodj+buildbot
2016-10-17 11:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-17 13:56 [binutils-gdb] Removed pseudo invalid instructions opcodes sergiodj+buildbot
2016-10-17 13:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-17 16:34 [binutils-gdb] gdb: Fix phony iconv build sergiodj+buildbot
2016-10-17 17:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-17 21:50 [binutils-gdb] Fix comment in mi-trace-save.exp sergiodj+buildbot
2016-10-17 23:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-17 23:24 [binutils-gdb] Fix duplicate test message in mi-trace-save.exp sergiodj+buildbot
2016-10-18  0:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-24 18:51 [binutils-gdb] testsuite: Fix gcc_compiled for gcc 6 & 7 sergiodj+buildbot
2016-10-26  0:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-24 18:58 [binutils-gdb] Check invalid mask registers sergiodj+buildbot
2016-10-26  1:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25  5:31 [binutils-gdb] ARM/BFD: Correct an `index' global shadowing error sergiodj+buildbot
2016-10-25  8:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25  8:56 [binutils-gdb] tilegx-tdep: Correct aliasing errors in `tilegx_analyze_prologue' sergiodj+buildbot
2016-10-25 11:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25  9:45 [binutils-gdb] Updated Danish translation for the BFD library sergiodj+buildbot
2016-10-25 13:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 11:26 [binutils-gdb] i386-tdep: Verify architecture before proceeding with `set/show mpx' sergiodj+buildbot
2016-10-25 12:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 14:27 [binutils-gdb] common/common-defs.h: Define __STDC_FORMAT_MACROS as well sergiodj+buildbot
2016-10-27  7:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 16:26 [binutils-gdb] Update gnulib to current upstream master sergiodj+buildbot
2016-10-25 17:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 17:13 [binutils-gdb] gdb: no longer define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS sergiodj+buildbot
2016-10-25 18:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 19:09 [binutils-gdb] Add c-format tags to translatable strings with more than one argument-using formatting token sergiodj+buildbot
2016-10-25 20:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 20:01 [binutils-gdb] testsuite: Fix gdb.base/killed-outside.exp using irrelevant stale options sergiodj+buildbot
2016-10-25 20:54 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-25 23:12 [binutils-gdb] Regenerate bfd.pot sergiodj+buildbot
2016-10-25 22:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  0:57 [binutils-gdb] Delete target_so_ops->special_symbol_handling hook sergiodj+buildbot
2016-10-26  1:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  3:15 [binutils-gdb] Use RAII to save and restore scalars sergiodj+buildbot
2016-10-26  4:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  4:10 [binutils-gdb] Record minimal symbols directly in reader sergiodj+buildbot
2016-10-26  8:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  5:16 [binutils-gdb] Use scoped_restore for current_ui sergiodj+buildbot
2016-10-26  5:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  6:04 [binutils-gdb] Change command stats reporting to use class sergiodj+buildbot
2016-10-26 12:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  7:29 [binutils-gdb] Replace two xmallocs with unique_ptr sergiodj+buildbot
2016-10-26 13:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  8:46 [binutils-gdb] Remove make_cleanup_restore_current_ui sergiodj+buildbot
2016-10-26  9:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26  9:49 [binutils-gdb] Remove some cleanups in MI sergiodj+buildbot
2016-10-26 10:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 11:13 [binutils-gdb] Use gdb::unique_ptr in elf_read_minimal_symbols sergiodj+buildbot
2016-10-26 13:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 12:26 [binutils-gdb] Convert dwarf_expr_context_funcs to methods sergiodj+buildbot
2016-10-26 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 13:44 [binutils-gdb] Initial conversion of dwarf_expr_ctx sergiodj+buildbot
2016-10-26 16:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 14:01 [binutils-gdb] Change minimal_symbol_reader::record_full to take a bool sergiodj+buildbot
2016-10-26 21:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 15:19 [binutils-gdb] Make some dwarf_expr_context methods pure virtual sergiodj+buildbot
2016-10-26 22:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 18:48 [binutils-gdb] gdbserver: Leave already-vCont-resumed threads as they were sergiodj+buildbot
2016-10-27 12:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 19:43 [binutils-gdb] [GDBserver] Fix conversion warning sergiodj+buildbot
2016-10-26 23:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 21:08 [binutils-gdb] Fix obvious gotcha in string comparison sergiodj+buildbot
2016-10-27  2:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 21:15 [binutils-gdb] Fix potential NULL pointer dereference sergiodj+buildbot
2016-10-27  3:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-26 21:33 [binutils-gdb] Make symfile_add_flags and objfile->flags strongly typed sergiodj+buildbot
2016-10-27 15:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27  1:11 [binutils-gdb] Make dwarf_expr_context's destructor virtual sergiodj+buildbot
2016-10-27 11:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27  2:24 [binutils-gdb] Don't override operator new if GDB is built with -fsanitize=address sergiodj+buildbot
2016-10-27  4:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27  4:28 [binutils-gdb] new-op.c: Add comment about -fsanitize=address sergiodj+buildbot
2016-10-27  6:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27  4:45 [binutils-gdb] Define __STDC_CONSTANT_MACROS/__STDC_LIMIT_MACROS again sergiodj+buildbot
2016-10-27  5:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27 12:23 [binutils-gdb] gas/arc: Don't rely on bfd list of cpu type for cpu selection sergiodj+buildbot
2016-10-27 16:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27 13:09 [binutils-gdb] gdb: Coalesce/aggregate (async) vCont packets/actions sergiodj+buildbot
2016-10-27 13:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27 17:15 [binutils-gdb] Get pending events in random sergiodj+buildbot
2016-10-27 19:06 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-27 17:39 [binutils-gdb] Enable range stepping if software single step is supported sergiodj+buildbot
2016-10-27 20:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28  9:54 [binutils-gdb] btrace: fix gap indication sergiodj+buildbot
2016-10-28 10:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28 10:04 [binutils-gdb] btrace: allow leading trace gaps sergiodj+buildbot
2016-10-28 11:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28 12:51 [binutils-gdb] btrace: bridge gaps sergiodj+buildbot
2016-10-28 15:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28 14:01 [binutils-gdb] Fix gdb.base/maint.exp regressions sergiodj+buildbot
2016-10-28 15:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28 15:01 [binutils-gdb] Make gdb.base/foll-exec.exp test pattern more general sergiodj+buildbot
2016-10-28 16:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28 15:46 [binutils-gdb] gdb/testsuite: Avoid a buffer overrun in `gdb.base/maint.exp' sergiodj+buildbot
2016-10-28 17:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-28 17:46 [binutils-gdb] gdb: Require C++11 sergiodj+buildbot
2016-10-28 22:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-29 16:13 [binutils-gdb] Support command-line redirection in native MS-Windows debugging sergiodj+buildbot
2016-10-29 16:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-31 18:27 [binutils-gdb] MIPS: Remove remains of legacy remote target support sergiodj+buildbot
2016-10-31 18:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-10-31 19:02 [binutils-gdb] Remove IRIX 5 <sys/proc.h> _KMEMUSER workaround sergiodj+buildbot
2016-11-01 16:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-04 14:52 [binutils-gdb] Fix building binutils for all 32-bit targets by moving riscv32 target into 64-bit builds only sergiodj+buildbot
2016-11-04 16:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-05  4:41 [binutils-gdb] Fix a few typos sergiodj+buildbot
2016-11-05  5:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-08  1:46 [binutils-gdb] Fix ext lang calls to value_struct_elt sergiodj+buildbot
2016-11-08 10:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-08 17:10 [binutils-gdb] gdbarch software_single_step returns VEC (CORE_ADDR) * sergiodj+buildbot
2016-11-08 18:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-08 23:02 [binutils-gdb] Use ui_file_as_string in dwarf2_compute_name sergiodj+buildbot
2016-11-09  5:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09  2:14 [binutils-gdb] Use ui_file_as_string in gdb/ui-out.c sergiodj+buildbot
2016-11-09  8:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09  8:07 [binutils-gdb] Use ui_file_as_string in gdb/python/ sergiodj+buildbot
2016-11-09 16:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 10:10 [binutils-gdb] Use ui_file_as_string in gdb/compile/ sergiodj+buildbot
2016-11-09 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 10:46 [binutils-gdb] Use ui_file_as_string in gdb/c-exp.y sergiodj+buildbot
2016-11-09 22:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 15:45 [binutils-gdb] Use ui_file_as_string in gdb/language.c sergiodj+buildbot
2016-11-10  9:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 17:48 [binutils-gdb] 'struct agent_expr *' -> unique_ptr<agent_expr> sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 18:35 [binutils-gdb] Use ui_file_as_string throughout more sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 18:42 [binutils-gdb] Eliminate agent_expr_p; VEC -> std::vector in struct bp_target_info sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 19:49 [binutils-gdb] Use get_frame_register_value instead of deprecated_frame_register_read sergiodj+buildbot
2016-11-10 10:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 20:30 [binutils-gdb] Remove parameter valaddr from la_val_print sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 21:50 [binutils-gdb] Fix some error-handling bugs in python frame filters sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 23:16 [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry sergiodj+buildbot
2016-11-10 10:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-09 23:50 [binutils-gdb] Fix py-value.exp failure on Python 3 sergiodj+buildbot
2016-11-10 10:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  1:21 [binutils-gdb] darwin-nat.c: handle Darwin 16 (aka Sierra) sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  3:59 [binutils-gdb] tui-winsource: Allocate for actual lines only sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  4:19 [binutils-gdb] tui-disasm: Fix line buffer size calculation sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  5:47 [binutils-gdb] gdb: Use vector::emplace_back sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  6:36 [binutils-gdb] tui-winsource: Remove failed-allocation logic sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:45 [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:45 [binutils-gdb] gdb/testsuite: Introduce "proc_with_prefix" sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:46 [binutils-gdb] Make gdb.mi/user-selected-context-sync.exp use proc_with_prefix sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:47 [binutils-gdb] X86: Remove the .s suffix from EVEX vpextrw sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:47 [binutils-gdb] X86: Merge AVX512F vmovq sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:48 [binutils-gdb] Further cleanup/modernization of gdb.base/commands.exp sergiodj+buildbot
2016-11-10 10:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  7:49 [binutils-gdb] Use unique_xmalloc_ptr in Python code sergiodj+buildbot
2016-11-10 10:13 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  8:07 [binutils-gdb] tui-disasm: Fix window content buffer overrun sergiodj+buildbot
2016-11-10  9:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10  9:30 [binutils-gdb] [AArch64] Bind defined symbol locally in PIE sergiodj+buildbot
2016-11-10 10:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-10 12:31 [binutils-gdb] Provide a more helpful error message when the BFD library is unable to load an extremely large section sergiodj+buildbot
2016-11-10 12:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-11 10:09 [binutils-gdb] sim: mips: fix dv-tx3904cpu build error sergiodj+buildbot
2016-11-11 11:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-11 10:40 [binutils-gdb] Remove parameter valaddr from c print functions sergiodj+buildbot
2016-11-11 12:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-11 12:02 [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr sergiodj+buildbot
2016-11-11 13:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-11 12:40 [binutils-gdb] Accept hidden COFF symbols, but treat them as if they were debugging symbols sergiodj+buildbot
2016-11-11 15:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-11 14:42 [binutils-gdb] [AArch64] Increase max_num_aliases in aarch64-gen sergiodj+buildbot
2016-11-11 17:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-11 21:18 [binutils-gdb] Don't handle unavailable/optimized-out in spu_software_single_step sergiodj+buildbot
2016-11-12  2:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-12 19:05 [binutils-gdb] Use std::string in rust_get_disr_info sergiodj+buildbot
2016-11-12 19:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-15 20:24 [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition sergiodj+buildbot
2016-11-15 21:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-15 20:54 [binutils-gdb] gdb::{unique_ptr,move} -> std::{unique_ptr,move} sergiodj+buildbot
2016-11-15 23:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-16  0:24 [binutils-gdb] gdb: update gnulib to pull in C++ namespace support fixes sergiodj+buildbot
2016-11-16  2:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-16 20:01 [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs sergiodj+buildbot
2016-11-16 20:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-16 20:03 [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp sergiodj+buildbot
2016-11-16 21:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-17  0:20 [binutils-gdb] Stash frame id of current frame before stashing frame id for previous frame sergiodj+buildbot
2016-11-17  8:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-17  1:28 [binutils-gdb] gdb/tracepoint.c: Don't use printf_vma sergiodj+buildbot
2016-11-17 12:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-17 18:31 [binutils-gdb] Document new hard requirement on GNU make sergiodj+buildbot
2016-11-17 19:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-18  9:59 [binutils-gdb] Help diagnose problems with the metag target when mixing static and shared binaries sergiodj+buildbot
2016-11-18 10:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-18 13:05 [binutils-gdb] [AArch64] Add ARMv8.3 FCMLA and FCADD instructions sergiodj+buildbot
2016-11-18 15:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-18 16:45 [binutils-gdb] Implement P0012R1, Make exception specifications part of the type system sergiodj+buildbot
2016-11-18 20:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-18 19:31 [binutils-gdb] libiberty: Add Rust symbol demangling sergiodj+buildbot
2016-11-19  0:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-19  0:43 [binutils-gdb] bfd: fix negative GOT offsets for non-local references on sparc64 sergiodj+buildbot
2016-11-19  4:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-19  3:34 [binutils-gdb] Makefile: fix typo sergiodj+buildbot
2016-11-19  9:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-19 19:14 [binutils-gdb] ARI: Add detection of printf_vma and sprintf_vma sergiodj+buildbot
2016-11-19 20:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-21 14:37 [binutils-gdb] Create subobject value in pretty printer sergiodj+buildbot
2016-11-21 16:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-21 21:38 [binutils-gdb] Add missing POSTCOMPILE step to mi/ file generation rules sergiodj+buildbot
2016-11-21 22:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 10:39 [binutils-gdb] Use input_bfd in relocate_section sergiodj+buildbot
2016-11-22 11:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 13:53 [binutils-gdb] gas, opcodes: fix hardware capabilities bumping in the sparc assembler sergiodj+buildbot
2016-11-22 14:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 15:10 [binutils-gdb] New regcache_raw_get_signed sergiodj+buildbot
2016-11-22 15:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 15:55 [binutils-gdb] gdbarch software_single_step frame_info to regcache: aarch64 sergiodj+buildbot
2016-11-22 17:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 17:49 [binutils-gdb] gdbarch software_single_step frame_info to regcache: mips sergiodj+buildbot
2016-11-22 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 19:25 [binutils-gdb] gdbarch software_single_step frame_info to regcache: nios2 sergiodj+buildbot
2016-11-22 22:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 21:00 [binutils-gdb] gdbarch software_single_step frame_info to regcache: rs6000 sergiodj+buildbot
2016-11-23  1:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-22 22:40 [binutils-gdb] gdbarch software_single_step frame_info to regcache: spu sergiodj+buildbot
2016-11-23 15:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-23  0:36 [binutils-gdb] gdbarch software_single_step frame_info to regcache: tic6x sergiodj+buildbot
2016-11-23 11:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-23  1:00 [binutils-gdb] Fix spelling mistakes in comments in shell scripts sergiodj+buildbot
2016-11-23 18:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-23  2:43 [binutils-gdb] gdbserver: Use warning for warnings sergiodj+buildbot
2016-11-23 22:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-23 15:19 [binutils-gdb] Makefiles: Flatten and sort file lists sergiodj+buildbot
2016-11-24  8:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-24 17:53 [binutils-gdb] Fix PR12616 - gdb does not implement DW_AT_data_bit_offset sergiodj+buildbot
2016-11-24 18:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-24 21:00 [binutils-gdb] Add noexcept to custom non-throwing new operators sergiodj+buildbot
2016-11-24 23:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-25 15:36 [binutils-gdb] Fix typos in comment sergiodj+buildbot
2016-11-25 17:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-25 21:27 [binutils-gdb] Remove check requiring void argument to functions with no parameters sergiodj+buildbot
2016-11-25 23:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-27  4:37 [binutils-gdb] Rename ui_out_data to mi_ui_out_data sergiodj+buildbot
2016-11-27 12:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-27  8:16 [binutils-gdb] Constify wrap_here/wrap_hint code path sergiodj+buildbot
2016-11-28  6:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-28 17:50 [binutils-gdb] Move computed value's frame id to piece_closure sergiodj+buildbot
2016-11-28 18:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-30  7:01 [binutils-gdb] PR20886, looping in ppc64_elf_size_stubs sergiodj+buildbot
2016-11-30  8:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-11-30 12:13 [binutils-gdb] Revert accidental elf.c change sergiodj+buildbot
2016-11-30 13:37 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-01  5:08 [binutils-gdb] Use std::vector for cli_ui_out_data::streams sergiodj+buildbot
2016-12-01  7:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-01  5:58 [binutils-gdb] Use std::string in ui_out_table sergiodj+buildbot
2016-12-01  9:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-01 21:50 [binutils-gdb] Fix test names starting with uppercase using gdb_test on a single line sergiodj+buildbot
2016-12-01 23:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-01 23:25 [binutils-gdb] Fix test names starting with uppercase using multi-line gdb_test/mi_gdb_test sergiodj+buildbot
2016-12-02  9:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02  1:27 [binutils-gdb] Fixup testcases outputting own name as a test name and standardize failed compilation messages sergiodj+buildbot
2016-12-02 11:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02  2:20 [binutils-gdb] Use std::string for ui_out_hdr's text fields sergiodj+buildbot
2016-12-02 15:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02  2:49 [binutils-gdb] Class-ify ui_out_hdr sergiodj+buildbot
2016-12-02 15:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02  3:57 [binutils-gdb] Class-ify ui_out_level sergiodj+buildbot
2016-12-02 16:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02  5:00 [binutils-gdb] ui_out_table: Replace boolean flag with enum sergiodj+buildbot
2016-12-02 18:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02 15:26 [binutils-gdb] Remove mi_out_data::suppress_output sergiodj+buildbot
2016-12-03  6:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-02 19:55 [binutils-gdb] Fix PR 20559 - "eval" command and $arg0...$arg9/$argc substitution sergiodj+buildbot
2016-12-03 16:19 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-03 11:55 [binutils-gdb] Indirect and warning symbols sergiodj+buildbot
2016-12-03 22:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-04  2:02 [binutils-gdb] Fix bugs with tbnz/tbz instructions sergiodj+buildbot
2016-12-04 12:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-05 13:22 [binutils-gdb] Fix seg-fault in linker parsing a corrupt input file sergiodj+buildbot
2016-12-05 14:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-05 15:33 [binutils-gdb] [ARM] Add ARMv8.3 command line option and feature flag sergiodj+buildbot
2016-12-05 17:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-06  7:30 [binutils-gdb] argv.c (expandargv): Check for directories passed as @-files sergiodj+buildbot
2016-12-06 10:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-06 14:59 [binutils-gdb] Assert on lval_register sergiodj+buildbot
2016-12-06 16:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-06 17:12 [binutils-gdb] Fix seg-fault in strip when copying a corrupt binary sergiodj+buildbot
2016-12-06 18:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-07 10:48 [binutils-gdb] Fix internal error in the linker by replacing a call to abort with an error message sergiodj+buildbot
2016-12-07 12:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-07 15:39 [binutils-gdb] MIPS/include: opcode/mips.h: Correct INSN_CHIP_MASK sergiodj+buildbot
2016-12-07 18:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09  0:50 [binutils-gdb] MIPS16/opcodes: Fix PC-relative operation delay-slot adjustment sergiodj+buildbot
2016-12-09  6:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09  1:29 [binutils-gdb] MIPS16/opcodes: Fix off-by-one indentation in `print_mips16_insn_arg' sergiodj+buildbot
2016-12-09 15:21 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09  7:23 [binutils-gdb] Avoid PATH_MAX usage sergiodj+buildbot
2016-12-09 15:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09  8:00 [binutils-gdb] Hurd: Adjust to changes to "push pruning old threads down to the target" sergiodj+buildbot
2016-12-09 16:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09 11:55 [binutils-gdb] Use code cache in aarch64 prologue analyzer sergiodj+buildbot
2016-12-09 20:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09 16:12 [binutils-gdb] Create tdep->rl78_psw_type lazily sergiodj+buildbot
2016-12-09 23:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-09 23:59 [binutils-gdb] MIPS16/opcodes: Reformat raw EXTEND and undecoded output sergiodj+buildbot
2016-12-10  9:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-10  1:40 [binutils-gdb] MIPS16: Remove unused `>' operand code sergiodj+buildbot
2016-12-10 10:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-12  9:28 [binutils-gdb] Handle memory error in print_insn_rl78_common sergiodj+buildbot
2016-12-12 10:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-13 17:55 [binutils-gdb] [Binutils][AARCH64]Remove Cn register for coprocessor CRn, CRm field sergiodj+buildbot
2016-12-13 20:36 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-14  6:47 [binutils-gdb] ld: aarch64: fix TLS relaxation where TCB_SIZE is used sergiodj+buildbot
2016-12-14  7:22 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-14  7:22 [binutils-gdb] bfd: aarch64: fix word and arrdess size declaration in ilp32 mode sergiodj+buildbot
2016-12-14  8:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-14  8:12 [binutils-gdb] Revert "ld: aarch64: fix TLS relaxation where TCB_SIZE is used" sergiodj+buildbot
2016-12-14  9:52 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-14  8:26 [binutils-gdb] Revert "bfd: aarch64: fix word and arrdess size declaration in ilp32 mode" sergiodj+buildbot
2016-12-14 12:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-14  9:08 [binutils-gdb] ld: aarch64: fix TLS relaxation where TCB_SIZE is used sergiodj+buildbot
2016-12-14 14:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-15  0:13 [binutils-gdb] MIPS/opcodes: Reorder ELF file header flag handling in disassembler sergiodj+buildbot
2016-12-15  4:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-19 11:44 [binutils-gdb] MIPS/opcodes: Only call `bfd_mips_elf_get_abiflags' if BFD64 sergiodj+buildbot
2016-12-19 13:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20  2:03 [binutils-gdb] Add opcodes RISC-V dependencies sergiodj+buildbot
2016-12-20  7:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20  2:03 [binutils-gdb] Fix an integer overflow in RISC-V relocation handling sergiodj+buildbot
2016-12-20 14:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20  2:06 [binutils-gdb] Fix disassembly of RISC-V CSR instructions under -Mno-aliases sergiodj+buildbot
2016-12-20 18:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20  2:06 [binutils-gdb] Correct assembler mnemonic for RISC-V aqrl AMOs sergiodj+buildbot
2016-12-20 20:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20  2:12 [binutils-gdb] Improve RISC-V LD error message sergiodj+buildbot
2016-12-20 13:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20 16:15 [binutils-gdb] Set emacs default mode for the GDB directory to C++ sergiodj+buildbot
2016-12-21  2:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20 17:00 [binutils-gdb] Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains sergiodj+buildbot
2016-12-21  4:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-20 23:46 [binutils-gdb] MIPS16/opcodes: Correct I64/SDRASP opcode's ISA membership sergiodj+buildbot
2016-12-21  0:45 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-21 11:51 [binutils-gdb] Remove high bit set characters sergiodj+buildbot
2016-12-21 12:51 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-21 14:46 [binutils-gdb] Avoid creating symbol table entries for registers sergiodj+buildbot
2016-12-21 15:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-21 21:24 [binutils-gdb] Fix bugs with float compare and Inf operands sergiodj+buildbot
2016-12-21 23:15 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-22 22:01 [binutils-gdb] Class-ify ui_out sergiodj+buildbot
2016-12-22 23:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23  1:16 [binutils-gdb] infrun.c (set_step_over_info): Add comment sergiodj+buildbot
2016-12-23  3:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23  9:35 [binutils-gdb] Regenerate pot files sergiodj+buildbot
2016-12-23  9:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23  9:49 [binutils-gdb] Bump version to 2.28.51 sergiodj+buildbot
2016-12-23 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 12:50 [binutils-gdb] Updated email address sergiodj+buildbot
2016-12-23 13:20 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 14:34 [binutils-gdb] hppa-linux-gnu-ranlib: libcpp.a: File format not recognized sergiodj+buildbot
2016-12-23 15:39 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 18:37 [binutils-gdb] Fix incorrect reference to source files sergiodj+buildbot
2016-12-23 19:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 20:03 [binutils-gdb] Fix more cases of improper test names sergiodj+buildbot
2016-12-23 20:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 21:30 [binutils-gdb] opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD sergiodj+buildbot
2016-12-23 21:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 22:22 [binutils-gdb] MIPS16: Simplify extended operand handling sergiodj+buildbot
2016-12-24  3:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-23 22:25 [binutils-gdb] MIPS16: Remove "extended" BREAK/SDBBP handling sergiodj+buildbot
2016-12-23 23:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-24  3:33 [binutils-gdb] MIPS/BFD: Remove EI_ABIVERSION 5 allocation for PT_GNU_STACK support sergiodj+buildbot
2016-12-24  7:03 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-26  6:26 [binutils-gdb] Put .dynbss and .rel.bss shortcuts in main elf hash table sergiodj+buildbot
2016-12-26  7:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-28 12:52 [binutils-gdb] Use dynrelro for symbols in relro sections too sergiodj+buildbot
2016-12-28 13:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-29 14:37 [binutils-gdb] link_hash_copy_indirect and symbol flags sergiodj+buildbot
2016-12-29 16:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-29 16:30 [binutils-gdb] Return 'int' rather than 'unsigned short' in avrdis_opcode sergiodj+buildbot
2016-12-29 19:47 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-31  2:44 [binutils-gdb] Import config.sub sergiodj+buildbot
2016-12-31  2:48 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-31  3:06 [binutils-gdb] PRU BFD support sergiodj+buildbot
2016-12-31  4:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2016-12-31 13:03 [binutils-gdb] Fix riscv breakage sergiodj+buildbot
2016-12-31 12:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  0:08 [binutils-gdb] PR20989, sparc GOT sequence optimisation sergiodj+buildbot
2017-01-04  2:11 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  1:22 [binutils-gdb] Don't make symbols dynamic other than undef weak sergiodj+buildbot
2017-01-04  4:28 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  1:22 [binutils-gdb] Sync dwarf headers with master versions in gcc repository sergiodj+buildbot
2017-01-04  6:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  1:38 [binutils-gdb] Fix compile time warning about using a possibly uninitialised variable sergiodj+buildbot
2017-01-04  7:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  3:11 [binutils-gdb] Add fall through comment sergiodj+buildbot
2017-01-04 10:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  3:42 [binutils-gdb] Add support for the Q extension to the RISCV ISA sergiodj+buildbot
2017-01-04 12:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  3:56 [binutils-gdb] bfd: alpha: Fix crash caused by double free with --no-keep-memory sergiodj+buildbot
2017-01-04 13:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04  5:38 [binutils-gdb] Fix generation of GOT table when only GOT-relative relocs are used sergiodj+buildbot
2017-01-04 11:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04 10:10 [binutils-gdb] Fix an internal error on writing pieced value sergiodj+buildbot
2017-01-04 14:56 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04 12:49 [binutils-gdb] [AArch64] Add separate feature flag for weaker release consistent load insns sergiodj+buildbot
2017-01-04 16:17 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04 14:42 [binutils-gdb] Sync libiberty from gcc sergiodj+buildbot
2017-01-04 18:43 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04 14:57 [binutils-gdb] update-copyright.py for binutils sergiodj+buildbot
2017-01-04 20:29 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04 16:08 [binutils-gdb] [DWARF] Sync GCC dwarf.def change on AArch64 sergiodj+buildbot
2017-01-04 21:40 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-04 20:32 [binutils-gdb] Use correct OSABI constant for FreeBSD/mips binaries sergiodj+buildbot
2017-01-04 23:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-05  0:23 [binutils-gdb] Five fixes, for fcsel, fcvtz, fminnm, mls, and non-widening mul sergiodj+buildbot
2017-01-05  1:34 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-05  9:19 [binutils-gdb] Prevent an abort in the FRV disassembler if the target bfd name is unknown sergiodj+buildbot
2017-01-05 12:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 14:17 [binutils-gdb] Update gdb_ptrace.h in HFILES_NO_SRCDIR sergiodj+buildbot
2017-01-06 15:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 15:00 [binutils-gdb] Include ax.h in ax-gdb.h sergiodj+buildbot
2017-01-06 16:23 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 15:35 [binutils-gdb] Include doublest.h and expression.h in dfp.h sergiodj+buildbot
2017-01-06 17:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 16:36 [binutils-gdb] Include target.h in inf-loop.h sergiodj+buildbot
2017-01-06 18:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 17:08 [binutils-gdb] Include mi-cmds.h in mi-parse.h sergiodj+buildbot
2017-01-06 19:50 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 17:58 [binutils-gdb] Include break-common.h in nat/aarch64-linux-hw-point.h sergiodj+buildbot
2017-01-06 20:59 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 18:31 [binutils-gdb] Include signal.h in nat/amd64-linux-siginfo.h sergiodj+buildbot
2017-01-06 22:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 19:51 [binutils-gdb] Include serial.h in ser-base.h sergiodj+buildbot
2017-01-07 22:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-06 20:40 [binutils-gdb] Include gdb_proc_service.h in x86-linux-nat.h sergiodj+buildbot
2017-01-07 23:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-08 10:52 [binutils-gdb] [D] Fix crash when debug expression enabled sergiodj+buildbot
2017-01-08 13:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-09 17:05 [binutils-gdb] Speed up objdump when displaying disassembly mixed with line number and source code information sergiodj+buildbot
2017-01-09 18:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-10  0:02 [binutils-gdb] Fix problems with the implementation of the uzp1 and uzp2 instructions sergiodj+buildbot
2017-01-10  0:57 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-10 15:35 [binutils-gdb] Update help of the "frame" command sergiodj+buildbot
2017-01-10 16:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-10 16:47 [binutils-gdb] Change return type of ui_out redirect to void sergiodj+buildbot
2017-01-10 17:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-10 19:51 [binutils-gdb] Don't use elf_i386_eh_frame_plt directly sergiodj+buildbot
2017-01-10 20:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-10 21:52 [binutils-gdb] i386/x86-64: Add unwind info for .plt.got section sergiodj+buildbot
2017-01-10 22:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11  5:41 [binutils-gdb] Introduce py-ref.h sergiodj+buildbot
2017-01-11  7:01 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11  7:09 [binutils-gdb] Use gdbpy_ref in gdbpy_breakpoints sergiodj+buildbot
2017-01-11 14:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11  7:18 [binutils-gdb] Change event code to use gdbpy_ref sergiodj+buildbot
2017-01-11  8:10 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11  7:59 [binutils-gdb] Use gdbpy_ref in py-framefilter.c sergiodj+buildbot
2017-01-11 16:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11  8:42 [binutils-gdb] Use gdbpy_ref in gdbpy_string_to_argv sergiodj+buildbot
2017-01-11 10:58 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11  9:54 [binutils-gdb] Use gdbpy_ref in call_doc_function sergiodj+buildbot
2017-01-11 18:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 11:14 [binutils-gdb] Use gdbpy_ref in py-value.c sergiodj+buildbot
2017-01-11 21:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 11:29 [binutils-gdb] Use gdbpy_ref in gdbpy_lookup_symbol sergiodj+buildbot
2017-01-11 23:02 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 11:46 [binutils-gdb] Introduce gdbpy_enter sergiodj+buildbot
2017-01-12  0:14 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 12:51 [binutils-gdb] Use gdbpy_enter in py-cmd.c sergiodj+buildbot
2017-01-12  3:32 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 14:12 [binutils-gdb] Use gdbpy_enter in py-objfile.c sergiodj+buildbot
2017-01-12  7:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 14:43 [binutils-gdb] Use gdbpy_enter in python.c sergiodj+buildbot
2017-01-12  9:31 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 14:59 [binutils-gdb] Use gdbpy_enter in py-type.c sergiodj+buildbot
2017-01-12 10:41 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 15:49 [binutils-gdb] Use gdbpy_enter in py-xmethods.c sergiodj+buildbot
2017-01-12 12:27 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 16:05 [binutils-gdb] Use gdbpy_enter in py-unwind.c sergiodj+buildbot
2017-01-12 13:38 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 18:16 [binutils-gdb] Use gdbpy_enter in python_interactive_command sergiodj+buildbot
2017-01-12 18:44 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 18:31 [binutils-gdb] Use gdbpy_enter in gdbpy_get_matching_xmethod_workers sergiodj+buildbot
2017-01-12 20:00 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 19:03 [binutils-gdb] Use gdbpy_enter in py-xmethod.c sergiodj+buildbot
2017-01-12 22:35 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 19:07 [binutils-gdb] Use gdbpy_enter in py-finishbreakpoint.c sergiodj+buildbot
2017-01-12  4:46 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 19:18 [binutils-gdb] Introduce gdbpy_enter_varobj and use it sergiodj+buildbot
2017-01-13  0:04 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 19:49 [binutils-gdb] Use gdbpy_enter in cmdpy_function sergiodj+buildbot
2017-01-13  3:07 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 20:19 [binutils-gdb] Use gdbpy_enter in py-param.c sergiodj+buildbot
2017-01-13  5:42 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 20:35 [binutils-gdb] Use gdbpy_enter in python.c sergiodj+buildbot
2017-01-13  6:55 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 21:40 [binutils-gdb] Change type of encoding argument to gdbpy_extract_lazy_string sergiodj+buildbot
2017-01-13  9:16 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 21:55 [binutils-gdb] Use gdbpy_enter_varobj in varobj_value_get_print_value sergiodj+buildbot
2017-01-13 10:25 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 22:26 [binutils-gdb] Use gdbpy_ref in py_print_frame sergiodj+buildbot
2017-01-13 12:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-11 23:31 [binutils-gdb] Change python_run_simple_file to use gdbpy_ref sergiodj+buildbot
2017-01-13 15:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  0:34 [binutils-gdb] Use gdbpy_ref in archpy_disassemble sergiodj+buildbot
2017-01-13 16:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  1:51 [binutils-gdb] Use gdbpy_ref in py-inferior.c sergiodj+buildbot
2017-01-13 23:53 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  2:37 [binutils-gdb] Use gdbpy_ref in py-param.c sergiodj+buildbot
2017-01-14  1:12 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  2:53 [binutils-gdb] Use gdbpy_ref in python.c sergiodj+buildbot
2017-01-14  9:33 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  3:09 [binutils-gdb] Use gdbpy_ref in pyuw_object_attribute_to_pointer sergiodj+buildbot
2017-01-14 16:24 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  5:21 [binutils-gdb] Use gdbpy_ref in invoke_match_method sergiodj+buildbot
2017-01-12 21:18 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  7:27 [binutils-gdb] Use gdbpy_enter_varobj in py-varobj.c sergiodj+buildbot
2017-01-13  1:49 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12  8:52 [binutils-gdb] Use gdbpy_enter in fnpy_call sergiodj+buildbot
2017-01-13  4:26 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12 10:32 [binutils-gdb] Use gdbpy_enter_varobj in more of varobj.c sergiodj+buildbot
2017-01-13  8:05 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12 14:12 [binutils-gdb] Use gdbpy_ref in py-prettyprint.c sergiodj+buildbot
2017-01-13 14:08 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12 15:55 [binutils-gdb] Use gdbpy_ref in gdbpy_breakpoint_cond_says_stop sergiodj+buildbot
2017-01-13 18:09 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12 16:30 [binutils-gdb] Use gdbpy_ref in py-cmd.c sergiodj+buildbot
2017-01-13 19:30 ` Failures on Debian-i686, branch master sergiodj+buildbot
2017-01-12 17:47 [binutils-gdb] Use gdbpy_ref in py_print_frame sergiodj+buildbot
2017-01-13 22:08 ` Failures on Debian-i686, branch master sergiodj+buildbot

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).