public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] S/390: Fix kmctr instruction type.
@ 2016-09-13 17:42 sergiodj+buildbot
  2016-09-13 17:43 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
                   ` (12 more replies)
  0 siblings, 13 replies; 1903+ 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] 1903+ messages in thread
[parent not found: <@gdb-build>]
* [binutils-gdb] Don't add PHDR for objcopy/strip or ld script specifying PHDRS
@ 2016-12-13  0:21 sergiodj+buildbot
  2016-12-20  2:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  2016-12-23 13:19 ` sergiodj+buildbot
  0 siblings, 2 replies; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-13  0:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22b05d33b4c870d65972ff8aefdd297ddc66d139 ***

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

Don't add PHDR for objcopy/strip or ld script specifying PHDRS

HPPA64 needs to add a DT_PHDR header for shared libs.  That's fine
when linking but shouldn't happen for strip/objcopy.  Also PHDR must
come first so there's no need to look at all program headers.

bfd/
	* elf64-hppa.c (elf64_hppa_modify_segment_map): Don't add PHDR
	for objcopy/strip or when a ld script specifies PHDRS.
ld/
	* testsuite/ld-elf/nobits-1.d: Remove xfail for hppa64.
	* testsuite/ld-elf/note-1.d: Likewise.
	* testsuite/ld-elf/note-2.d: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't fudge p_vaddr when PHDR in segment
@ 2016-12-12 23:39 sergiodj+buildbot
  2017-01-14 14:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-12 23:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6392030005291f7c783da2247b63ae31dc8352e0 ***

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

Don't fudge p_vaddr when PHDR in segment

RX does horrible fudges to PT_LOAD p_vaddr, that affect the testsuite
and mean the target won't support dynamic objects.  The latter
probably doesn't matter too much since RX is an embedded target, but
it's easy to stop some of the fudges in order to reduce special cases
for RX in the testsuite.  The changes make sense in isolation too.

bfd/
	* elf32-rx.c (elf32_rx_modify_program_headers): Don't adjust
	segments that include the ELF file header or program headers.
ld/
	* testsuite/ld-elf/flags1.d: Run for RX.
	* testsuite/ld-scripts/phdrs.exp: Likewise.
	* testsuite/ld-scripts/pr14962.d: Likewise.
	* testsuite/ld-scripts/pr14962-2.d: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Port c++/78252 from GCC
@ 2016-12-12 18:30 sergiodj+buildbot
  2016-12-12 19:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-12 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88acc2e16743fc1e6384758c9a68cd6d2a8bbd46 ***

Author: Nathan Sidwell <nathan@acm.org>
Branch: master
Commit: 88acc2e16743fc1e6384758c9a68cd6d2a8bbd46

Port c++/78252 from GCC

	PR c++/78252
	* cp-demangle.c (struct d_print_info): Add is_lambda_arg field.
	(d_print_init): Initialize it.
	(d_print_comp_inner) <DEMANGLE_COMPONENT_TEMPLATE_PARAM>: Check
	is_lambda_arg for auto.
	<DEMANGLE_COMPONENT_REFERENCE,
	DEMANGLE_COMPONENT_RVALUE_REFERENCE>: Skip smashing check when
	is_lambda_arg.
	<DEMANGLE_COMPONENT_LAMBDA>: Increment is_lambda_arg around arg
	printing.
	* testsuite/demangle-expected: Add lambda auto mangling cases.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove assert on exec_bfd in cris_delayed_get_disassembler
@ 2016-12-12 10:51 sergiodj+buildbot
  2016-12-12 14:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-12 10:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d36cab83a963f5bb3773e0218cc02f63b0851d0b ***

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

Remove assert on exec_bfd in cris_delayed_get_disassembler

cris_delayed_get_disassembler has an assert that exec_bfd can't be
NULL, but this assert can be triggered like this,

(gdb) set architecture cris
The target architecture is assumed to be cris
(gdb) disassemble 0x0,+4
Dump of assembler code from 0x0 to 0x4:
   0x00000000:
../../binutils-gdb/gdb/cris-tdep.c:3798: internal-error: int cris_delayed_get_disassembler(bfd_vma, disassemble_info*): Assertion `exec_bfd != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

however, cris_get_disassembler does have code to handle the case that
bfd is NULL,

  /* If there's no bfd in sight, we return what is valid as input in all
     contexts if fed back to the assembler: disassembly *with* register
     prefix.  Unfortunately this will be totally wrong for v32.  */
  if (abfd == NULL)
    return print_insn_cris_with_register_prefix;

This patch is to remove this assert.

gdb:

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

	PR tdep/20955
	* cris-tdep.c (cris_delayed_get_disassembler): Remove the
	assert.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Handle memory error in print_insn_rx
@ 2016-12-12 10:38 sergiodj+buildbot
  2016-12-12 12:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-12 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 029e9d52de3ac7fe984dc079ebd24506fd1eace7 ***

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

Handle memory error in print_insn_rx

Nowadays, memory error in rx disassembly is not handled, so if I
start a fresh GDB, and disassemble,

(gdb) set architecture rx
The target architecture is assumed to be rx
(gdb) disassemble 0x0,+4
Dump of assembler code from 0x0 to 0x4:
   0x00000000:	brk
   0x00000001:	brk
   0x00000002:	brk
   0x00000003:	brk

the output is wrong.  This patch adds code to call dis->memory_error_func
on memory error, and longjmp to print_insn_rx.  With this patch applied,

(gdb) set architecture rx
The target architecture is assumed to be rx
(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>

	* rx-dis.c: Include <setjmp.h>
	(struct private): New.
	(rx_get_byte): Check return value of read_memory_func, and
	call memory_error_func and OPCODES_SIGLONGJMP on error.
	(print_insn_rx): Call OPCODES_SIGSETJMP.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Handle memory error in print_insn_rl78_common
@ 2016-12-12  9:28 sergiodj+buildbot
  2016-12-12 11:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Create tdep->rx_psw_type and tdep->rx_fpsw_type lazily
@ 2016-12-09 17:14 sergiodj+buildbot
  2016-12-10  0:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a28aa6edd4ba848c110cd73fd4e29c2bbdb2cb72 ***

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

Create tdep->rx_psw_type and tdep->rx_fpsw_type lazily

I build GDB with all targets enabled, and "set architecture rx",
GDB crashes,

(gdb) set architecture rx

Program received signal SIGSEGV, Segmentation fault.
append_flags_type_flag (type=0x20cc360, bitpos=bitpos@entry=0, name=name@entry=0xd27529 "C") at ../../binutils-gdb/gdb/gdbtypes.c:4926
4926				   name);
(gdb) bt 10
 #0  append_flags_type_flag (type=0x20cc360, bitpos=bitpos@entry=0, name=name@entry=0xd27529 "C") at ../../binutils-gdb/gdb/gdbtypes.c:4926
 #1  0x00000000004ce725 in rx_gdbarch_init (info=..., arches=<optimized out>) at ../../binutils-gdb/gdb/rx-tdep.c:1051
 #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=0x20bee81 "rx ", 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=0x20bee70 "set architecture rx ", from_tty=1) at ../../binutils-gdb/gdb/top.c:666
 #7  0x00000000006935f4 in command_handler (command=0x20bee70 "set architecture rx ") 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=0x20be7f0 "") 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/20954
	* rx-tdep.c (rx_psw_type): New function.
	(rx_fpsw_type): New function.
	(rx_register_type): Call rx_psw_type and rx_fpsw_type.
	(rx_gdbarch_init): Move code to rx_psw_type and
	rx_fpsw_type.

gdb/testsuite:

2016-12-09  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/all-architectures.exp.in: Remove kfail for "rx".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use code cache in arm prologue analyzer
@ 2016-12-09 11:10 sergiodj+buildbot
  2016-12-09 20:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-09 11:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 198cd59d289209ad63cdd6da45e02a1c12b423a7 ***

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

Use code cache in arm prologue analyzer

This patch change arm 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 a lot,

			Original	Patched		Original	Patched
			without dbg	without dbg	with dbg	with dbg

-marm			14.166741848	9.32852292061  	11.4908499718  	9.16302204132
-marm   		14.6705040932  	9.34849786758  	18.2788009644  	9.14823913574
\-fstack-protector-all
-mthumb			34.4391930103	10.6062178612 	13.7886838913	10.3094120026
-mthumb
\-fstack-protector-all	34.9310460091	10.6413481236	25.3875930309	10.6294929981

gdb:

2016-12-09  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (skip_prologue_function): Call
	read_code_unsigned_integer instead of
	read_memory_unsigned_integer.
	(thumb_analyze_prologue): Likewise.
	(arm_analyze_load_stack_chk_guard): Likewise.
	(arm_skip_stack_protector): Likewise.
	(arm_analyze_prologue):Likewise.
	(extend_buffer_earlier): Call target_read_code instead
	of target_read_memory.
	(arm_adjust_breakpoint_address): Likewise.


^ permalink raw reply	[flat|nested] 1903+ 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 17:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] AArch64/opcodes: Correct another `index' global shadowing error
@ 2016-12-09  0:14 sergiodj+buildbot
  2016-12-09  1:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-09  0:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 329d01f70ea6367a9593c9b31e268c06dd729ec9 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 329d01f70ea6367a9593c9b31e268c06dd729ec9

AArch64/opcodes: Correct another `index' global shadowing error

Fix a commit c2c4ff8d52a2 ("[AArch64] Add ARMv8.3 FCMLA and FCADD
instructions") build regression:

cc1: warnings being treated as errors
.../opcodes/aarch64-dis.c: In function 'aarch64_ext_sve_addr_rr_lsl':
.../opcodes/aarch64-dis.c:1324: error: declaration of 'index' shadows a global declaration
/usr/include/string.h:303: error: shadowed declaration is here
make[4]: *** [aarch64-asm.lo] Error 1

in a way following commit 91d6fa6a035c ("Add -Wshadow to the gcc command
line options used when compiling the binutils.").

	opcodes/
	* aarch64-asm.c (aarch64_ins_reglane): Rename `index' local
	variable to `reglane_index'.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Hurd, C++: Mach/Hurd headers and MIG stubs are not yet fit for C++
@ 2016-12-08 11:25 sergiodj+buildbot
  2016-12-08 13:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-08 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 21389b7f3451a482e14fef9bd32257c4c87f4317 ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: 21389b7f3451a482e14fef9bd32257c4c87f4317

Hurd, C++: Mach/Hurd headers and MIG stubs are not yet fit for C++

..., so handle these in "C" mode still:

	gdb/
	* config/i386/i386gnu.mh (%_S.o %_U.o): Add "-x c" to
	"COMPILE.post".
	* gnu-nat.c: #include Mach/Hurd headers before all others.  Wrap
	Mach/Hurd headers and MIG stubs' prototypes in 'extern "C"'.
	* i386-gnu-nat.c: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Hurd, C++: Avoid GNU C nested functions
@ 2016-12-08  9:00 sergiodj+buildbot
  2016-12-08 10:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-08  9:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9617a426d001a748168fbc399fcc77e6d8d3cac ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: a9617a426d001a748168fbc399fcc77e6d8d3cac

Hurd, C++: Avoid GNU C nested functions

..., which C++ doesn't allow, so...

	gdb/
	* gnu-nat.c (gnu_create_inferior): Move nested "trace_me"
	function...
	(gnu_ptrace_me): ... here.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Hurd, C++: Explicitly cast "void *"
@ 2016-12-08  8:11 sergiodj+buildbot
  2016-12-08  9:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-08  8:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9e431d19426a6dd6b8923850398b847af0a1532 ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: e9e431d19426a6dd6b8923850398b847af0a1532

Hurd, C++: Explicitly cast "void *"

C++ doesn't do implicit type conversions from "void *", so we have to...

	gdb/
	* i386-gnu-nat.c (i386_gnu_dr_set_control_one)
	(i386_gnu_dr_set_addr_one): Explicitly cast "void *".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] MIPS/opcodes: Correct an `interaction' comment typo
@ 2016-12-07 14:36 sergiodj+buildbot
  2016-12-07 18:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-07 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f5c6e032e8d5303e9903c0538f84f76bb4d8733 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 5f5c6e032e8d5303e9903c0538f84f76bb4d8733

MIPS/opcodes: Correct an `interaction' comment typo

	opcodes/
	* mips-dis.c (print_mips16_insn_arg): Fix comment typo.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Add ARMv8.3 VCMLA and VCADD instructions
@ 2016-12-05 16:45 sergiodj+buildbot
  2016-12-05 21:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 16:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c28eeff2eabbba2246799470f3713716fa629680 ***

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

[ARM] Add ARMv8.3 VCMLA and VCADD instructions

Add support for VCMLA and VCADD advanced SIMD complex number instructions.

The command line option is -march=armv8.3-a+fp16+simd for enabling all
instructions.

In arm-dis.c the formatting syntax was abused a bit to select between
0 vs 90 or 180 vs 270 or 90 vs 270 based on a bit value instead of
duplicating entries in the opcode table.

gas/
	* config/tc-arm.c (do_vcmla, do_vcadd): Define.
	(neon_scalar_for_vcmla): Define.
	(enum operand_parse_code): Add OP_IROT1 and OP_IROT2.
	(NEON_ENC_TAB): Add DDSI and QQSI variants.
	(insns): Add vcmla and vcadd.
	* testsuite/gas/arm/armv8_3-a-simd.d: New.
	* testsuite/gas/arm/armv8_3-a-simd.s: New.
	* testsuite/gas/arm/armv8_3-a-simd-bad.d: New.
	* testsuite/gas/arm/armv8_3-a-simd-bad.l: New.
	* testsuite/gas/arm/armv8_3-a-simd-bad.s: New.

opcodes/
	* arm-dis.c (coprocessor_opcodes): Add vcmla and vcadd.
	(print_insn_coprocessor): Add 'V' format for neon D or Q regs.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Add ARMv8.3 VJCVT instruction
@ 2016-12-05 16:01 sergiodj+buildbot
  2016-12-05 19:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49e8a725825c77aacc7458b9d7771cb2fa2f64c7 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 49e8a725825c77aacc7458b9d7771cb2fa2f64c7

[ARM] Add ARMv8.3 VJCVT instruction

Add support for VJCVT javascript conversion instruction.

gas/
	* config/tc-arm.c (arm_ext_v8_3, do_vjcvt): Define.
	(insns): Add vjcvt.
	* testsuite/gas/aarch64/armv8_3-a-fp.s: New.
	* testsuite/gas/aarch64/armv8_3-a-fp.d: New.
	* testsuite/gas/aarch64/armv8_3-a-fp-bad.s: New.
	* testsuite/gas/aarch64/armv8_3-a-fp-bad.d: New.
	* testsuite/gas/aarch64/armv8_3-a-fp-bad.l: New.

opcodes/
	* arm-dis.c (coprocessor_opcodes): Add vjcvt.


^ permalink raw reply	[flat|nested] 1903+ 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:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] bfd, ld: Continue after partially-successful relaxed call relocations in sparc.
@ 2016-12-05 15:01 sergiodj+buildbot
  2016-12-05 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 15:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 597e138ca0cf96889a1965d06d28552c1d1174d2 ***

Author: Alyssa Milburn <amilburn@zall.org>
Branch: master
Commit: 597e138ca0cf96889a1965d06d28552c1d1174d2

bfd,ld: Continue after partially-successful relaxed call relocations in sparc.

bfd/ChangeLog:

2016-12-05  Alyssa Milburn <amilburn@zall.org>

  	* elfxx-sparc.c: Do not stop processing relocations after
    	partially relaxing a call with WDISP30.

ld/ChangeLog:

2016-12-05  Alyssa Milburn <amilburn@zall.org>

	* testsuite/ld-sparc/wdispcall.s: New file.
    	* testsuite/ld-sparc/wdispcall.dd: Likewise.
    	* testsuite/ld-sparc/sparc.exp: Run new test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix seg-fault attempting to strip a corrupt binary.
@ 2016-12-05 14:06 sergiodj+buildbot
  2016-12-05 15:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a55c9876bb111fd301b4762cf501de0040b8f9db ***

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

Fix seg-fault attempting to strip a corrupt binary.

	PR binutils/20922
	* elf.c (find_link): Check for null headers before attempting to
	match them.


^ permalink raw reply	[flat|nested] 1903+ 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:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix assertion failure in linker triggered by corrupt input file.
@ 2016-12-05 12:47 sergiodj+buildbot
  2016-12-05 13:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-05 12:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39d4daf68e696bbf2db417abe677b2e68f3aace9 ***

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

Fix assertion failure in linker triggered by corrupt input file.

	PR ld/20925
	* aoutx.h (aout_link_add_symbols): Replace BFD_ASSERT with return
	FALSE.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Tidy ppc64_elf_hide_symbol
@ 2016-12-03 13:02 sergiodj+buildbot
  2016-12-04  4:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-03 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8ac28419be22fe0cc72f6eaaba1ab029610fc71 ***

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

Tidy ppc64_elf_hide_symbol

	* elf64-ppc.c (ppc64_elf_hide_symbol): Access hash table as
	elf_link_hash_table rather than ppc_link_hash_table.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Test user-defined gdb commands and arguments stack
@ 2016-12-02 20:34 sergiodj+buildbot
  2016-12-03 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec835369f121c11d6e9484ed8c6c11097ad545c5 ***

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

Test user-defined gdb commands and arguments stack

We're missing a test that makes sure that arguments to user-defined
commands are handled correctly when a user-defined command calls
another user-defined command / recurses.

The following patch changes that code, so add such a test first so we
can be confident won't be breaking this use case.

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

	* gdb.base/commands.exp (user_defined_command_args_stack_test):
	New procedure.
	(top level): Call it.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Revert change to gdb.cp/ovldbreak.exp
@ 2016-12-02 18:11 sergiodj+buildbot
  2016-12-03 14:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 18:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 008459ea88ad4fdcb7da37dad7f68888ef6ecc47 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 008459ea88ad4fdcb7da37dad7f68888ef6ecc47

Revert change to gdb.cp/ovldbreak.exp

This reverts the timeout handling (removed by
018572b88885ae67d22612937fa1e4fd98d5f5ad) for gdb.cp/ovldbreak.exp until we
decide what to do about this particular function.

gdb/testsuite/ChangeLog:

2016-12-02  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/ovldbreak.exp (take_gdb_out_of_choice_menu): Restore
	timeout handling.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix seg-fault in the linker when examining a corrupt binary.
@ 2016-12-02 17:12 sergiodj+buildbot
  2016-12-03 13:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 17:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 531336e3a0b79ed60cfc36ad2d6579b6a71175da ***

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

Fix seg-fault in the linker when examining a corrupt binary.

	PR ld/20909
	* aoutx.h (aout_link_add_symbols): Fix off-by-one error in check
	for an illegal string offset.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR symtab/16264 - support DW_AT_main_subprogram
@ 2016-12-02 16:48 sergiodj+buildbot
  2016-12-03 12:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 16:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c1b455e294c6debb4efedc7f1346f3c43249f15 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 0c1b455e294c6debb4efedc7f1346f3c43249f15

PR symtab/16264 - support DW_AT_main_subprogram

This patch adds support for DW_AT_main_subprogram.
This is PR symtab/16264.

DW_AT_main_subprogram is used to mark a program's entry point.  GCC
can emit this, and I hope to change the Rust compiler to emit it as
well.

GDB already supports an older, pre-DWARF 4 convention adopted by
FORTRAN compilers, namely to emit DW_AT_calling_convention for the
"main" function.  However, I think this support in GDB had a small
bug, in that it seems to rely on the DW_AT_name being read before
DW_AT_calling_convention.  This patch fixes this as well.

Built and regtested on x86-64 Fedora 24 and the buildbot.  New test
case included.

2016-12-02  Tom Tromey  <tom@tromey.com>

	PR symtab/16264:
	* dwarf2read.c (struct partial_die_info) <main_subprogram>: New
	member.
	(add_partial_symbol): Call set_objfile_main_name.
	(read_partial_die): Handle DW_AT_main_subprogram.
	<DW_AT_calling_convention>: don't call set_objfile_main_name, but
	set main_subprogram flag.

2016-12-02  Tom Tromey  <tom@tromey.com>

	* gdb.dwarf2/main-subprogram.c: New file.
	* gdb.dwarf2/main-subprogram.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Recognize STR instruction in prologue
@ 2016-12-02 10:50 sergiodj+buildbot
  2016-12-02 20:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 432ec0814b01a93b88eddf13092ea6abef34652d ***

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

[AArch64] Recognize STR instruction in prologue

This patch teaches GDB AArch64 backend to recognize STR instructions
in prologue, like 'str x19, [sp, #-48]!' or 'str w0, [sp, #44]'.
The unit test is added too.

gdb:

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

	* aarch64-tdep.c (aarch64_analyze_prologue): Recognize STR
	instruction.
	(aarch64_analyze_prologue_test): More tests.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't handle timeout inside gdb_test_multiple
@ 2016-12-02  6:01 sergiodj+buildbot
  2016-12-02 17:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  6:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 018572b88885ae67d22612937fa1e4fd98d5f5ad ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 018572b88885ae67d22612937fa1e4fd98d5f5ad

Don't handle timeout inside gdb_test_multiple

This fixes a few cases where the testcase is explicitly handling timeouts
inside gdb_test_multiple when it is not necessary.

It also converts two gdb_test_multiple calls to gdb_test_no_output calls
(also removing the timeout handling).

gdb/testsuite/ChangeLog:

2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.base/maint.exp: Remove timeout handling for gdb_test_multiple.
	* gdb.cp/gdb2495.exp: Likewise and convert gdb_test_multiple into
	gdb_test_no_output for a couple of cases.
	* gdb.cp/ovldbreak.exp: Remove timeout handling for gdb_test_multiple.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Class-ify ui_out_table
@ 2016-12-02  5:34 sergiodj+buildbot
  2016-12-02 16:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  5:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36d18bc526b055be896d8dc319cb3ade42238534 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 36d18bc526b055be896d8dc319cb3ade42238534

Class-ify ui_out_table

This patch makes a class out of the ui_out_table structure, the
structure responsible for managing the generation of an UI table.

To simplify the ui_out_table object, I changed it so that it can only be
used for generating a single object.  Instead of clearing the header
list when starting a new table, we an ui_out_table when starting a
table and delete it when we're done.  Therefore, the checks:

  if (uiout->table->flag)
  if (!uiout->table->flag)

are respectively replaced with

  if (uiout->table != nullptr)
  if (uiout->table == nullptr)

Note: I removed the check at the beginning of ui_out_begin, because
there is an equivalent check at the beginning of verify_field.

New in v2:

  - use "enum class" for ui_out_table::state and update references.

gdb/ChangeLog:

	* ui-out.c (enum ui_out_table_state): Move to class
	ui_out_table as ui_out_table::state.
	(struct ui_out_table): Change to ...
	(class ui_out_table): ... this.
	<flag>: Remove.
	<entry_level>: Rename to ...
	<m_entry_level>: ... this.
	<columns>: Rename to ...
	<m_nr_cols>: ... this.
	<id>: Rename to ...
	<m_id>: ... this.
	<headers>: Rename to ...
	<m_headers>: ... this.
	<headers_iterator>: Rename to ...
	<m_headers_iterator>: ... this.
	<start_body, append_header, start_row, get_next_header,
	query_field, current_state, entry_level>: New methods.
	(struct ui_out) <table>: Change type to unique_ptr to
	ui_out_table.
	(append_header_to_list, get_next_header, clear_header_list,
	clear_table): Remove.
	(ui_out_table_begin): Instantiate ui_out_table object.  Update
	table check.
	(ui_out_table_body): Update table check, replace code with call
	to ui_out_table::start_body.
	(ui_out_table_end): Update table check, replace manual cleanup
	with assignment of uiout->table unique_ptr to nullptr.
	(ui_out_table_header): Update table check, replace call to
	append_header_to_list with call to append_header method.
	(ui_out_begin): Remove one table state check, update another.
	Replace code with call to start_row method.
	(verify_field): Update table checks.
	(ui_out_query_field): Update table check, replace code with call
	to query_field method.
	(ui_out_new): Remove table initialization code.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Simplify ui-out level code
@ 2016-12-02  4:41 sergiodj+buildbot
  2016-12-02 15:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-02  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33b2fac610fff1255a24763277a4bf77f1b59ef1 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 33b2fac610fff1255a24763277a4bf77f1b59ef1

Simplify ui-out level code

Now that we use a vector to store the levels, we don't have to keep a
separate level field in ui_out to keep track of the current level.  We
can efficiently derive it from the vector size.  That causes a little
change in the meaning of the level, as in they are now 1-based instead
of 0-based (the initial level has the "id" 1 now), but it shouldn't
change anything in the behavior.

Additionally, push_level and pop_level don't really need to return the
new level, making them return void simplifies the code a bit.

Finally, the ui_out_begin/ui_out_end callbacks in the ui_out_impl
interface don't need to be passed the level, it's never actually used.

New in v2:

 - Remove or update stale comments.

gdb/ChangeLog:

	* ui-out.h (ui_out_begin_ftype): Remove level parameter.
	(ui_out_end_ftype): Likewise.
	* ui-out.c (struct ui_out) <level>: Replace field with a method
	that dynamically computes the result.
	(current_level): Get vector's back item instead of using
	uiout->level.
	(push_level): Make return type void.
	(pop_level): Make return type void and update access to
	ui_out::level.
	(uo_begin): Remove level parameter.
	(uo_end): Likewise.
	(ui_out_table_begin): Update access to uiout::level.
	(ui_out_begin): Don't read return value from push_level, call
	uiout->level() instead, update call to uo_begin.
	(ui_out_end): Don't read return value from pop_level, update
	call to uo_end.
	(verify_field): Update access to uiout->level.
	(ui_out_new): Don't initialize ui_out::level, call push_level
	to push the initial level instead of doing it by hand.
	* cli-out.c (cli_begin): Remove level parameter.
	(cli_end): Likewise.
	* mi/mi-out.c (mi_begin): Likewise.
	(mi_end): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Class-ify ui_out_level
@ 2016-12-02  3:57 sergiodj+buildbot
  2016-12-02 13:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Class-ify ui_out_hdr
@ 2016-12-02  2:49 sergiodj+buildbot
  2016-12-02 11:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase using gdb_test_no_output
@ 2016-12-01 22:09 sergiodj+buildbot
  2016-12-02  0:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f058c10cef5987ee1f1cb28c9a8cf5ef1ec4d11 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 9f058c10cef5987ee1f1cb28c9a8cf5ef1ec4d11

Fix test names starting with uppercase using gdb_test_no_output

This fixes offender testcases that have test names starting with uppercase
when using gdb_test_no_output 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.base/charset.exp
	* gdb.base/eval.exp
	* gdb.base/multi-forks.exp
	* gdb.guile/scm-progspace.exp
	* gdb.opencl/datatypes.exp
	* gdb.python/py-block.exp
	* gdb.python/py-function.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-xmethods.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-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/sigall-precsave.exp
	* gdb.reverse/sigall-reverse.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/solib-reverse.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


^ permalink raw reply	[flat|nested] 1903+ 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:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix test names starting with uppercase output by basic functions
@ 2016-12-01 21:12 sergiodj+buildbot
  2016-12-01 22:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc6c7af4a2f23c48a38139fc7e0ed2ac7b12bb69 ***

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

Fix test names starting with uppercase output by basic functions

The following patch is based on the previous patch i sent and handles cases of
test names that start with an uppercase letter. Test names should start with
lowercase unless it starts with the name of a technology, architecture, ISA
etc.

This first patch addresses cases of test names output explicitly via xfail,
kfail, kpass, fail, pass, unsupported, untested and also names set with the
pattern "set test" and "set testname".

gdb/testsuite/ChangeLog:
2016-12-01  Luis Machado  <lgustavo@codesourcery.com>

	Fix test names starting with uppercase throughout all the files below.

	* gdb.ada/array_return.exp
	* gdb.ada/catch_ex.exp
	* gdb.ada/info_exc.exp
	* gdb.ada/mi_catch_ex.exp
	* gdb.ada/mi_dyn_arr.exp
	* gdb.ada/mi_ex_cond.exp
	* gdb.ada/mi_exc_info.exp
	* gdb.ada/mi_interface.exp
	* gdb.ada/mi_task_arg.exp
	* gdb.ada/mi_task_info.exp
	* gdb.ada/mi_var_array.exp
	* gdb.arch/alpha-step.exp
	* gdb.arch/amd64-disp-step.exp
	* gdb.arch/arm-disp-step.exp
	* gdb.arch/disp-step-insn-reloc.exp
	* gdb.arch/e500-prologue.exp
	* gdb.arch/ftrace-insn-reloc.exp
	* gdb.arch/gdb1558.exp
	* gdb.arch/i386-bp_permanent.exp
	* gdb.arch/i386-disp-step.exp
	* gdb.arch/i386-float.exp
	* gdb.arch/i386-gnu-cfi.exp
	* gdb.arch/ia64-breakpoint-shadow.exp
	* gdb.arch/mips16-thunks.exp
	* gdb.arch/pa-nullify.exp
	* gdb.arch/powerpc-aix-prologue.exp
	* gdb.arch/powerpc-power.exp
	* gdb.arch/ppc-dfp.exp
	* gdb.arch/s390-tdbregs.exp
	* gdb.arch/spu-info.exp
	* gdb.arch/spu-ls.exp
	* gdb.arch/thumb-bx-pc.exp
	* gdb.base/advance.exp
	* gdb.base/annota-input-while-running.exp
	* gdb.base/arrayidx.exp
	* gdb.base/asmlabel.exp
	* gdb.base/async.exp
	* gdb.base/attach-wait-input.exp
	* gdb.base/auto-connect-native-target.exp
	* gdb.base/batch-preserve-term-settings.exp
	* gdb.base/bfp-test.exp
	* gdb.base/bigcore.exp
	* gdb.base/bp-permanent.exp
	* gdb.base/break-always.exp
	* gdb.base/break-fun-addr.exp
	* gdb.base/break-idempotent.exp
	* gdb.base/break-main-file-remove-fail.exp
	* gdb.base/break-probes.exp
	* gdb.base/break-unload-file.exp
	* gdb.base/break.exp
	* gdb.base/call-ar-st.exp
	* gdb.base/call-rt-st.exp
	* gdb.base/call-sc.exp
	* gdb.base/call-signal-resume.exp
	* gdb.base/call-strs.exp
	* gdb.base/callexit.exp
	* gdb.base/callfuncs.exp
	* gdb.base/catch-gdb-caused-signals.exp
	* gdb.base/catch-signal-siginfo-cond.exp
	* gdb.base/catch-syscall.exp
	* gdb.base/compare-sections.exp
	* gdb.base/cond-eval-mode.exp
	* gdb.base/condbreak-call-false.exp
	* gdb.base/consecutive-step-over.exp
	* gdb.base/cursal.exp
	* gdb.base/disabled-location.exp
	* gdb.base/disasm-end-cu.exp
	* gdb.base/display.exp
	* gdb.base/double-prompt-target-event-error.exp
	* gdb.base/dprintf-bp-same-addr.exp
	* gdb.base/dprintf-detach.exp
	* gdb.base/dprintf-next.exp
	* gdb.base/dprintf-non-stop.exp
	* gdb.base/dprintf-pending.exp
	* gdb.base/dso2dso.exp
	* gdb.base/ending-run.exp
	* gdb.base/enum_cond.exp
	* gdb.base/examine-backward.exp
	* gdb.base/exe-lock.exp
	* gdb.base/exec-invalid-sysroot.exp
	* gdb.base/execl-update-breakpoints.exp
	* gdb.base/execution-termios.exp
	* gdb.base/fileio.exp
	* gdb.base/fixsection.exp
	* gdb.base/foll-exec-mode.exp
	* gdb.base/foll-exec.exp
	* gdb.base/fork-running-state.exp
	* gdb.base/frame-args.exp
	* gdb.base/fullpath-expand.exp
	* gdb.base/func-ptr.exp
	* gdb.base/gcore-relro-pie.exp
	* gdb.base/gdb1090.exp
	* gdb.base/gdb1555.exp
	* gdb.base/global-var-nested-by-dso.exp
	* gdb.base/gnu-ifunc.exp
	* gdb.base/hbreak-in-shr-unsupported.exp
	* gdb.base/hbreak-unmapped.exp
	* gdb.base/hook-stop.exp
	* gdb.base/infcall-input.exp
	* gdb.base/info-fun.exp
	* gdb.base/info-shared.exp
	* gdb.base/interrupt-noterm.exp
	* gdb.base/jit-so.exp
	* gdb.base/jit.exp
	* gdb.base/line-symtabs.exp
	* gdb.base/list.exp
	* gdb.base/longjmp.exp
	* gdb.base/macscp.exp
	* gdb.base/max-value-size.exp
	* gdb.base/nodebug.exp
	* gdb.base/nofield.exp
	* gdb.base/overlays.exp
	* gdb.base/paginate-after-ctrl-c-running.exp
	* gdb.base/paginate-bg-execution.exp
	* gdb.base/paginate-inferior-exit.exp
	* gdb.base/pending.exp
	* gdb.base/pr11022.exp
	* gdb.base/printcmds.exp
	* gdb.base/ptr-typedef.exp
	* gdb.base/ptype.exp
	* gdb.base/randomize.exp
	* gdb.base/range-stepping.exp
	* gdb.base/realname-expand.exp
	* gdb.base/relativedebug.exp
	* gdb.base/remote.exp
	* gdb.base/savedregs.exp
	* gdb.base/sepdebug.exp
	* gdb.base/set-noassign.exp
	* gdb.base/shlib-call.exp
	* gdb.base/shreloc.exp
	* gdb.base/sigaltstack.exp
	* gdb.base/sigbpt.exp
	* gdb.base/siginfo-addr.exp
	* gdb.base/siginfo-obj.exp
	* gdb.base/siginfo-thread.exp
	* gdb.base/signest.exp
	* gdb.base/signull.exp
	* gdb.base/sigrepeat.exp
	* gdb.base/skip.exp
	* gdb.base/so-impl-ld.exp
	* gdb.base/solib-corrupted.exp
	* gdb.base/solib-disc.exp
	* gdb.base/solib-display.exp
	* gdb.base/solib-overlap.exp
	* gdb.base/solib-search.exp
	* gdb.base/solib-symbol.exp
	* gdb.base/source-execution.exp
	* gdb.base/sss-bp-on-user-bp-2.exp
	* gdb.base/sss-bp-on-user-bp.exp
	* gdb.base/stack-checking.exp
	* gdb.base/stale-infcall.exp
	* gdb.base/step-break.exp
	* gdb.base/step-line.exp
	* gdb.base/step-over-exit.exp
	* gdb.base/step-test.exp
	* gdb.base/structs.exp
	* gdb.base/sym-file.exp
	* gdb.base/symtab-search-order.exp
	* gdb.base/term.exp
	* gdb.base/type-opaque.exp
	* gdb.base/unload.exp
	* gdb.base/until-nodebug.exp
	* gdb.base/until.exp
	* gdb.base/unwindonsignal.exp
	* gdb.base/watch-cond.exp
	* gdb.base/watch-non-mem.exp
	* gdb.base/watch_thread_num.exp
	* gdb.base/watchpoint-reuse-slot.exp
	* gdb.base/watchpoint-solib.exp
	* gdb.base/watchpoint.exp
	* gdb.btrace/dlopen.exp
	* gdb.cell/arch.exp
	* gdb.cell/break.exp
	* gdb.cell/bt.exp
	* gdb.cell/core.exp
	* gdb.cell/data.exp
	* gdb.cell/dwarfaddr.exp
	* gdb.cell/ea-cache.exp
	* gdb.cell/ea-standalone.exp
	* gdb.cell/ea-test.exp
	* gdb.cell/f-regs.exp
	* gdb.cell/fork.exp
	* gdb.cell/gcore.exp
	* gdb.cell/mem-access.exp
	* gdb.cell/ptype.exp
	* gdb.cell/registers.exp
	* gdb.cell/sizeof.exp
	* gdb.cell/solib-symbol.exp
	* gdb.cell/solib.exp
	* gdb.compile/compile-tls.exp
	* gdb.cp/exception.exp
	* gdb.cp/gdb2495.exp
	* gdb.cp/local.exp
	* gdb.cp/mb-inline.exp
	* gdb.cp/mb-templates.exp
	* gdb.cp/pr10687.exp
	* gdb.cp/pr9167.exp
	* gdb.cp/scope-err.exp
	* gdb.cp/templates.exp
	* gdb.cp/virtfunc.exp
	* gdb.dwarf2/dw2-dir-file-name.exp
	* gdb.dwarf2/dw2-single-line-discriminators.exp
	* gdb.fortran/complex.exp
	* gdb.fortran/library-module.exp
	* gdb.guile/guile.exp
	* gdb.guile/scm-cmd.exp
	* gdb.guile/scm-frame-inline.exp
	* gdb.guile/scm-objfile.exp
	* gdb.guile/scm-pretty-print.exp
	* gdb.guile/scm-symbol.exp
	* gdb.guile/scm-type.exp
	* gdb.guile/scm-value.exp
	* gdb.linespec/keywords.exp
	* gdb.linespec/ls-errs.exp
	* gdb.linespec/macro-relative.exp
	* gdb.linespec/thread.exp
	* gdb.mi/mi-breakpoint-changed.exp
	* gdb.mi/mi-dprintf-pending.exp
	* gdb.mi/mi-fullname-deleted.exp
	* gdb.mi/mi-logging.exp
	* gdb.mi/mi-pending.exp
	* gdb.mi/mi-solib.exp
	* gdb.mi/new-ui-mi-sync.exp
	* gdb.mi/user-selected-context-sync.exp
	* gdb.multi/dummy-frame-restore.exp
	* gdb.multi/multi-arch-exec.exp
	* gdb.multi/remove-inferiors.exp
	* gdb.multi/watchpoint-multi-exit.exp
	* gdb.opt/solib-intra-step.exp
	* gdb.perf/backtrace.exp
	* gdb.perf/single-step.exp
	* gdb.perf/skip-command.exp
	* gdb.perf/skip-prologue.exp
	* gdb.perf/solib.exp
	* gdb.python/lib-types.exp
	* gdb.python/py-as-string.exp
	* gdb.python/py-bad-printers.exp
	* gdb.python/py-block.exp
	* gdb.python/py-breakpoint.exp
	* gdb.python/py-cmd.exp
	* gdb.python/py-events.exp
	* gdb.python/py-evthreads.exp
	* gdb.python/py-finish-breakpoint.exp
	* gdb.python/py-finish-breakpoint2.exp
	* gdb.python/py-frame-inline.exp
	* gdb.python/py-frame.exp
	* gdb.python/py-inferior.exp
	* gdb.python/py-infthread.exp
	* gdb.python/py-mi.exp
	* gdb.python/py-objfile.exp
	* gdb.python/py-pp-maint.exp
	* gdb.python/py-pp-registration.exp
	* gdb.python/py-prettyprint.exp
	* gdb.python/py-recurse-unwind.exp
	* gdb.python/py-shared.exp
	* gdb.python/py-symbol.exp
	* gdb.python/py-symtab.exp
	* gdb.python/py-template.exp
	* gdb.python/py-type.exp
	* gdb.python/py-unwind-maint.exp
	* gdb.python/py-unwind.exp
	* gdb.python/py-value.exp
	* gdb.python/python.exp
	* gdb.reverse/finish-reverse-bkpt.exp
	* gdb.reverse/insn-reverse.exp
	* gdb.reverse/next-reverse-bkpt-over-sr.exp
	* gdb.reverse/solib-precsave.exp
	* gdb.reverse/solib-reverse.exp
	* gdb.stabs/gdb11479.exp
	* gdb.stabs/weird.exp
	* gdb.threads/fork-child-threads.exp
	* gdb.threads/fork-plus-threads.exp
	* gdb.threads/fork-thread-pending.exp
	* gdb.threads/forking-threads-plus-breakpoint.exp
	* gdb.threads/hand-call-in-threads.exp
	* gdb.threads/interrupted-hand-call.exp
	* gdb.threads/linux-dp.exp
	* gdb.threads/local-watch-wrong-thread.exp
	* gdb.threads/next-while-other-thread-longjmps.exp
	* gdb.threads/non-ldr-exit.exp
	* gdb.threads/pending-step.exp
	* gdb.threads/print-threads.exp
	* gdb.threads/process-dies-while-detaching.exp
	* gdb.threads/process-dies-while-handling-bp.exp
	* gdb.threads/pthreads.exp
	* gdb.threads/queue-signal.exp
	* gdb.threads/reconnect-signal.exp
	* gdb.threads/signal-command-handle-nopass.exp
	* gdb.threads/signal-command-multiple-signals-pending.exp
	* gdb.threads/signal-delivered-right-thread.exp
	* gdb.threads/signal-sigtrap.exp
	* gdb.threads/sigthread.exp
	* gdb.threads/staticthreads.exp
	* gdb.threads/stepi-random-signal.exp
	* gdb.threads/thread-unwindonsignal.exp
	* gdb.threads/thread_check.exp
	* gdb.threads/thread_events.exp
	* gdb.threads/tid-reuse.exp
	* gdb.threads/tls-nodebug.exp
	* gdb.threads/tls-shared.exp
	* gdb.threads/tls-so_extern.exp
	* gdb.threads/tls.exp
	* gdb.threads/wp-replication.exp
	* gdb.trace/actions-changed.exp
	* gdb.trace/actions.exp
	* gdb.trace/backtrace.exp
	* gdb.trace/change-loc.exp
	* gdb.trace/collection.exp
	* gdb.trace/deltrace.exp
	* gdb.trace/disconnected-tracing.exp
	* gdb.trace/entry-values.exp
	* gdb.trace/ftrace-lock.exp
	* gdb.trace/ftrace.exp
	* gdb.trace/infotrace.exp
	* gdb.trace/mi-trace-frame-collected.exp
	* gdb.trace/mi-trace-unavailable.exp
	* gdb.trace/mi-traceframe-changed.exp
	* gdb.trace/mi-tracepoint-changed.exp
	* gdb.trace/mi-tsv-changed.exp
	* gdb.trace/no-attach-trace.exp
	* gdb.trace/packetlen.exp
	* gdb.trace/passc-dyn.exp
	* gdb.trace/passcount.exp
	* gdb.trace/pending.exp
	* gdb.trace/pr16508.exp
	* gdb.trace/qtro.exp
	* gdb.trace/range-stepping.exp
	* gdb.trace/read-memory.exp
	* gdb.trace/report.exp
	* gdb.trace/save-trace.exp
	* gdb.trace/signal.exp
	* gdb.trace/stap-trace.exp
	* gdb.trace/status-stop.exp
	* gdb.trace/strace.exp
	* gdb.trace/tfile.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/tracefile-pseudo-reg.exp
	* gdb.trace/tspeed.exp
	* gdb.trace/tstatus.exp
	* gdb.trace/tsv.exp
	* gdb.trace/unavailable.exp
	* gdb.trace/while-dyn.exp
	* gdb.trace/while-stepping.exp
	* lib/gdb-guile.exp
	* lib/gdb.exp
	* lib/mi-support.exp
	* lib/pascal.exp
	* lib/perftest.exp
	* lib/prelink-support.exp
	* lib/selftest-support.exp


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix accesses to the GOT for AARCH64 operating in 32-bit mode.
@ 2016-12-01 14:12 sergiodj+buildbot
  2016-12-01 17:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-12-01 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5cd1d8bcc24e948e86a636161e6d72f6316545a7 ***

Author: Yury Norov <ynorov@caviumnetworks.com>
Branch: master
Commit: 5cd1d8bcc24e948e86a636161e6d72f6316545a7

Fix accesses to the GOT for AARCH64 operating in 32-bit mode.

	PR ld/20868
bfd	* elfnn-aarch64.c (elfNN_aarch64_tls_relax): Use 32-bit accesses
	to the GOT when operating in 32-bit mode.

ld	* testsuite/ld-aarch64/tls-relax-gd-ie-ilp32.d: New test.
	* testsuite/ld-aarch64/relocs-ilp32.ld: Linker script for the new
	test.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Makefiles: Disable suffix rules and implicit rules
@ 2016-11-30 21:56 sergiodj+buildbot
  2016-12-01  0:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-30 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad02e4fe877f3a874145dd045626501245e65624 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ad02e4fe877f3a874145dd045626501245e65624

Makefiles: Disable suffix rules and implicit rules

Since we don't use suffix rules nor implicit rules in gdb, we can
disable them.  The advantage is a slightly faster make [1].

Here are some numbers about the speedup.  I ran this on my trusty old
Intel Q6600, so the time numbers are probably higher than what you'd get
on any recent hardware.  I ran "make" in the gdb/ directory of an
already built repository (configured with --enable-targets=all).  I
recorded the time of execution (average of 5).  I then ran "make -d" and
recorded the number of printed lines, which gives a rough idea of the
number of operations done.

I compared the following configurations, to see the impact of both the
empty .SUFFIXES target and the empty pattern rules, as well as running
"make -r", which can be considered the "ideal" case.

 A - baseline
 B - baseline + .SUFFIXES
 C - baseline + pattern rules
 D - baseline + .SUFFIXES + pattern rules
 E - baseline + make -r

 config | time (s) | "make -d"
 -----------------------------
    A   |   5.74   |  2396643
    B   |   1.19   |   298469
    C   |   2.81   |  1266573
    D   |   1.13   |   245489
    E   |   1.01   |   163914

We can see that the empty .SUFFIXES target has a bigger impact than the
empty pattern rules, but still it doesn't hurt to disable the implicit
pattern rules as well.

There are still some mentions of implicit rules I can't get rid of in
the "make -d" output.  For example, it's trying to build .c files from
.w files:

  Looking for an implicit rule for '/home/simark/src/binutils-gdb/gdb/infrun.c'.
  Trying pattern rule with stem 'infrun'.
  Trying implicit prerequisite '/home/simark/src/binutils-gdb/gdb/infrun.w'.

and trying to build Makefile.in from a bunch of extensions:

  Looking for an implicit rule for 'Makefile.in'.
  Trying pattern rule with stem 'Makefile.in'.
  Trying implicit prerequisite 'Makefile.in.o'.
  Trying pattern rule with stem 'Makefile.in'.
  Trying implicit prerequisite 'Makefile.in.c'.
  Trying pattern rule with stem 'Makefile.in'.
  Trying implicit prerequisite 'Makefile.in.cc'.
  ... many more ...

If somebody knows how to disable them, we can do it, but at this point
the returns are minimal, so it is not that important.

I verified that both in-tree and out-of-tree builds work.

[1] Switching from explicit rules to pattern rules for files in
    subdirectories actually made it slower, so this is kind of a way to
    redeem myself.  But it the end it's faster than it was previously,
    so it was all worth it. :)

gdb/ChangeLog:

	* disable-implicit-rules.mk: New file.
	* Makefile.in: Include disable-implicit-rules.mk.
	* data-directory/Makefile.in: Likewise.
	* gnulib/Makefile.in: Likewise.

gdb/doc/ChangeLog:

	* Makefile.in: Likewise.

gdb/gdbserver/ChangeLog:

	* Makefile.in: Include disable-implicit-rules.mk.

gdb/testsuite/ChangeLog:

	* Makefile.in: Include disable-implicit-rules.mk.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Read memory as unsigned integer
@ 2016-11-30 12:39 sergiodj+buildbot
  2016-11-30 15:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-30 12:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7913a64cab3930fe524f0e38f85cfca11bd52dcb ***

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

[ARM] Read memory as unsigned integer

When GDB read inferior memory as an address or an instruction,
it should be unsigned.

gdb:

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

	* arm-tdep.c (arm_scan_prologue): Read memory as unsigned integer.
	(arm_exidx_unwind_sniffer): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Properly hide hidden versioned symbol in executable
@ 2016-11-28 16:35 sergiodj+buildbot
  2016-11-28 17:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-28 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4deb8f714d555a2f530e37c3e7af32bc42fdda58 ***

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

Properly hide hidden versioned symbol in executable

A hidden versioned symbol in executable should be forced local if it is
locally defined, not referenced by shared library and not exported.  We
must do it before _bfd_elf_link_renumber_dynsyms.

bfd/

	* elflink.c (_bfd_elf_fix_symbol_flags): Hide hidden versioned
	symbol in executable.
	(elf_link_output_extsym): Don't change bind from global to
	local when linking executable.

ld/

	* testsuite/ld-elf/indirect.exp: Add a test for PR 18720.
	* testsuite/ld-elf/pr18720.rd: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix typo in comment
@ 2016-11-25 16:29 sergiodj+buildbot
  2016-11-25 16:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-25 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17e5269b995b0560dc74af78ba134cf1fcd9d56a ***

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

Fix typo in comment

gdb/ChangeLog:

	* infcmd.c (interrupt_command): Fix typo in comment.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix typos in comment
@ 2016-11-25 15:36 sergiodj+buildbot
  2016-11-25 16:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Do not use std::move when assigning an anonymous object to a unique_ptr.
@ 2016-11-24 21:27 sergiodj+buildbot
  2016-11-25  1:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 036e657b48144d7449ddfcfcf9214bcd7bcf268b ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 036e657b48144d7449ddfcfcf9214bcd7bcf268b

Do not use std::move when assigning an anonymous object to a unique_ptr.

Using std::move forces an extra copy of the object.  These changes fix
-Wpessimizing-move warnings from clang.

gdb/ChangeLog:

	* ada-lang.c (create_excep_cond_exprs): Do not use 'std::move'.
	* ax-gdb.c (agent_eval_command_one): Likewise.
	(agent_eval_command_one): Likewise.
	* breakpoint.c (parse_cond_to_aexpr): Likewise.
	(parse_cmd_to_aexpr): Likewise.
	* dtrace-probe.c (dtrace_process_dof_probe): Likewise.
	* parse.c (parse_expression_for_completion): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add noexcept to custom non-throwing new operators.
@ 2016-11-24 21:00 sergiodj+buildbot
  2016-11-24 23:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Optimize byte-aligned copies in copy_bitwise()
@ 2016-11-24 19:17 sergiodj+buildbot
  2016-11-24 21:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 19:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 793c128d03113816db85e8d1fa0bcd4982e246ee ***

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

Optimize byte-aligned copies in copy_bitwise()

The function copy_bitwise used for copying DWARF pieces can potentially
be invoked for large chunks of data.  For instance, consider a large
struct one of whose members is currently located in a register.  In this
case copy_bitwise would still copy the data bitwise in a loop, which is
much slower than necessary.

This change uses memcpy for the large part instead, if possible.

gdb/ChangeLog:

	* dwarf2loc.c (copy_bitwise): Use memcpy for the middle part, if
	it is byte-aligned.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add unit test for copy_bitwise
@ 2016-11-24 19:13 sergiodj+buildbot
  2016-11-24 20:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad06383f106ccfa299a6c7ac9720178d2d3d583f ***

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

Add unit test for copy_bitwise

This adds a unit test for the copy_bitwise function in dwarf2loc.c.
With the old (broken) version of copy_bitwise this test would generate
the following failure message:

(gdb) maintenance selftest
Self test failed: copy_bitwise 11000000 != 10000000 (7+2 -> 0)

gdb/ChangeLog:
2016-11-24  Andreas Arnez  <arnez@linux.vnet.ibm.com>
	    Pedro Alves  <palves@redhat.com>

	* dwarf2loc.c (bits_to_str, check_copy_bitwise)
	(copy_bitwise_tests): New functions.
	(_initialize_dwarf2loc): Register the new function
	copy_bitwise_tests as a unit test.
	* selftest.c (run_self_tests): Improve the failure message's
	wording and formatting.


^ permalink raw reply	[flat|nested] 1903+ 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:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARM] Bind defined symbol locally in PIE
@ 2016-11-24 14:48 sergiodj+buildbot
  2016-11-24 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-24 14:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1dcb9720d62cd053a72c31881b7724ce9f74332c ***

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

[ARM] Bind defined symbol locally in PIE

bfd/
	PR target/20737
	* elf32-arm.c (elf32_arm_final_link_relocate): Bind defined symbol
	locally in PIE.

ld/
	* testsuite/ld-arm/pie-bind-locally-a.s: New test source.
	* testsuite/ld-arm/pie-bind-locally-b.s: Likewise.
	* testsuite/ld-arm/pie-bind-locally.d: New testcase.
	* testsuite/ld-arm/arm-elf.exp: Run new testcase.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Normalize names of some source files
@ 2016-11-23 16:36 sergiodj+buildbot
  2016-11-23 21:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-23 16:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03b62bbbce3dc5f15131d9e78f77d035cd1cffb3 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 03b62bbbce3dc5f15131d9e78f77d035cd1cffb3

Normalize names of some source files

Most tdep/nat files are named:

  <cpu>-<os>-tdep.c
  <cpu>-<os>-nat.c

A few files do not respect this scheme.  This patch renames them so that
they are consistent with the rest of the files.  It builds fine with
--enable-targets=all, but that doesn't test the nat files.  I can only
hope that my grep skill is good enough.

gdb/ChangeLog:

	* Makefile.in (ALL_64_TARGET_OBS, ALL_TARGET_OBS,
	HFILES_NO_SRCDIR, ALLDEPFILES): Rename files.
	* alphabsd-nat.c: Rename to ...
	* alpha-bsd-nat.c: ... this, adjust include.
	* alphabsd-tdep.c: Rename to ...
	* alpha-bsd-tdep.c: ... this, adjust include.
	* alphabsd-tdep.h: Rename to ...
	* alpha-bsd-tdep.h: ... this, adjust include barrier and comment.
	* alphafbsd-tdep.c: Rename to ...
	* alpha-fbsd-tdep.c: ... this.
	* alphanbsd-tdep.c: Rename to ...
	* alpha-nbsd-tdep.c: ... this, adjust include.
	* alphaobsd-tdep.c: Rename to ...
	* alpha-obsd-tdep.c: ... this, adjust include.
	* amd64bsd-nat.c: Rename to ...
	* amd64-bsd-nat.c: ... this, adjust include.
	* amd64fbsd-nat.c: Rename to ...
	* amd64-fbsd-nat.c: ... this, adjust include.
	* amd64fbsd-tdep.c: Rename to ...
	* amd64-fbsd-tdep.c: ... this, adjust include.
	* amd64nbsd-nat.c: Rename to ...
	* amd64-nbsd-nat.c: ... this.
	* amd64nbsd-tdep.c: Rename to ...
	* amd64-nbsd-tdep.c: ... this.
	* amd64obsd-nat.c: Rename to ...
	* amd64-obsd-nat.c: ... this.
	* amd64obsd-tdep.c: Rename to ...
	* amd64-obsd-tdep.c: ... this.
	* amd64-tdep.h: Update comments.
	* armbsd-tdep.c: Rename to ...
	* arm-bsd-tdep.c: ... this.
	* armnbsd-nat.c: Rename to ...
	* arm-nbsd-nat.c: ... this.
	* armnbsd-tdep.c: Rename to ...
	* arm-nbsd-tdep.c: ... this.
	* armobsd-tdep.c: Rename to ...
	* arm-obsd-tdep.c: ... this.
	* arm-tdep.h: Update comments.
	* hppabsd-tdep.c: Rename to ...
	* hppa-bsd-tdep.c: ... this, adjust include.
	* hppabsd-tdep.h: Rename to ...
	* hppa-bsd-tdep.h: ... this, adjust include barrier and comment.
	* hppanbsd-nat.c: Rename to ...
	* hppa-nbsd-nat.c: ... this.
	* hppanbsd-tdep.c: Rename to ...
	* hppa-nbsd-tdep.c: ... this, adjust include.
	* hppaobsd-nat.c: Rename to ...
	* hppa-obsd-nat.c: ... this.
	* hppaobsd-tdep.c: Rename to ...
	* hppa-obsd-tdep.c: ... this, adjust include.
	* i386bsd-nat.c: Rename to ...
	* i386-bsd-nat.c: ... this, adjust include.
	* i386bsd-nat.h: Rename to ...
	* i386-bsd-nat.h: ... this, adjust include barrier and comment.
	* i386bsd-tdep.c: Rename to ...
	* i386-bsd-tdep.c: ... this.
	* i386fbsd-nat.c: Rename to ...
	* i386-fbsd-nat.c: ... this, adjust include.
	* i386fbsd-tdep.c: Rename to ...
	* i386-fbsd-tdep.c: ... this, adjust include.
	* i386fbsd-tdep.h: Rename to ...
	* i386-fbsd-tdep.h: ... this, adjust include barrier and comment.
	* i386gnu-nat.c: Rename to ...
	* i386-gnu-nat.c: ... this.
	* i386gnu-tdep.c: Rename to ...
	* i386-gnu-tdep.c: ... this.
	* i386nbsd-nat.c: Rename to ...
	* i386-nbsd-nat.c: ... this, adjust include.
	* i386nbsd-tdep.c: Rename to ...
	* i386-nbsd-tdep.c: ... this.
	* i386obsd-nat.c: Rename to ...
	* i386-obsd-nat.c: ... this, adjust include.
	* i386obsd-tdep.c: Rename to ...
	* i386-obsd-tdep.c: ... this.
	* i386v4-nat.c: Rename to ...
	* i386-v4-nat.c: ... this.
	* i386-tdep.h: Update comments.
	* m68k-tdep.h: Update comments.
	* m68kbsd-nat.c: Rename to ...
	* m68k-bsd-nat.c: ... this.
	* m68kbsd-tdep.c: Rename to ...
	* m68k-bsd-tdep.c: ... this.
	* m68klinux-nat.c: Rename to ...
	* m68k-linux-nat.c: ... this.
	* m68klinux-tdep.c: Rename to ...
	* m68k-linux-tdep.c: ... this.
	* m88kbsd-nat.c: Rename to ...
	* m88k-bsd-nat.c: ... this.
	* mipsnbsd-nat.c: Rename to ...
	* mips-nbsd-nat.c: ... this, adjust include.
	* mipsnbsd-tdep.c: Rename to ...
	* mips-nbsd-tdep.c: ... this, adjust include.
	* mipsnbsd-tdep.h: Rename to ...
	* mips-nbsd-tdep.h: ... this, adjust include barrier and comment.
	* mips64obsd-nat.c: Rename to ...
	* mips64-obsd-nat.c: ... this.
	* mips64obsd-tdep.c: Rename to ...
	* mips64-obsd-tdep.c: ... this.
	* ppcfbsd-nat.c: Rename to ...
	* ppc-fbsd-nat.c: ... this, adjust include.
	* ppcfbsd-tdep.c: Rename to ...
	* ppc-fbsd-tdep.c: ... this, adjust include.
	* ppcfbsd-tdep.h: Rename to ...
	* ppc-fbsd-tdep.h: ... this, adjust include barrier and comment.
	* ppcnbsd-nat.c: Rename to ...
	* ppc-nbsd-nat.c: ... this, adjust include.
	* ppcnbsd-tdep.c: Rename to ...
	* ppc-nbsd-tdep.c: ... this, adjust include.
	* ppcnbsd-tdep.h: Rename to ...
	* ppc-nbsd-tdep.h: ... this, adjust include barrier and comment.
	* ppcobsd-nat.c: Rename to ...
	* ppc-obsd-nat.c: ... this, adjust include.
	* ppcobsd-tdep.c: Rename to ...
	* ppc-obsd-tdep.c: ... this, adjust include.
	* ppcobsd-tdep.h: Rename to ...
	* ppc-obsd-tdep.h: ... this, adjust include barrier and comment.
	* shnbsd-nat.c: Rename to ...
	* sh-nbsd-nat.c: ... this.
	* shnbsd-tdep.c: Rename to ...
	* sh-nbsd-tdep.c: ... this.
	* sparcnbsd-nat.c: Rename to ...
	* sparc-nbsd-nat.c: ... this.
	* sparcnbsd-tdep.c: Rename to ...
	* sparc-nbsd-tdep.c: ... this.
	* sparcobsd-tdep.c: Rename to ...
	* sparc-obsd-tdep.c: ... this.
	* sparc64fbsd-nat.c: Rename to ...
	* sparc64-fbsd-nat.c: ... this.
	* sparc64fbsd-tdep.c: Rename to ...
	* sparc64-fbsd-tdep.c: ... this.
	* sparc64nbsd-nat.c: Rename to ...
	* sparc64-nbsd-nat.c: ... this.
	* sparc64nbsd-tdep.c: Rename to ...
	* sparc64-nbsd-tdep.c: ... this.
	* sparc64obsd-nat.c: Rename to ...
	* sparc64-obsd-nat.c: ... this.
	* sparc64obsd-tdep.c: Rename to ...
	* sparc64-obsd-tdep.c: ... this.
	* sparc64-tdep.h: Update comments.
	* vaxbsd-nat.c: Rename to ...
	* vax-bsd-nat.c: ... this.
	* vaxnbsd-tdep.c: Rename to ...
	* vax-nbsd-tdep.c: ... this.
	* vaxobsd-tdep.c: Rename to ...
	* vax-obsd-tdep.c: ... this.
	* x86bsd-nat.h: Rename to ...
	* x86-bsd-nat.h: ... this, adjust include barrier and comment.
	* x86bsd-nat.c: Rename to ...
	* x86-bsd-nat.c: ... this, adjust include.
	* configure.tgt: Update renamed files.
	* config/alpha/fbsd.mh: Update renamed files.
	* config/alpha/nbsd.mh: Update renamed files.
	* config/arm/nbsdelf.mh: Update renamed files.
	* config/djgpp/fnchange.lst: Update renamed files.
	* config/i386/fbsd.mh: Update renamed files.
	* config/i386/fbsd64.mh: Update renamed files.
	* config/i386/i386gnu.mh: Update renamed files.
	* config/i386/i386sol2.mh: Update renamed files.
	* config/i386/nbsd64.mh: Update renamed files.
	* config/i386/nbsdelf.mh: Update renamed files.
	* config/i386/obsd.mh: Update renamed files.
	* config/i386/obsd64.mh: Update renamed files.
	* config/i386/sol2-64.mh: Update renamed files.
	* config/m68k/linux.mh: Update renamed files.
	* config/m68k/nbsdelf.mh: Update renamed files.
	* config/m68k/obsd.mh: Update renamed files.
	* config/m88k/obsd.mh: Update renamed files.
	* config/mips/nbsd.mh: Update renamed files.
	* config/mips/obsd64.mh: Update renamed files.
	* config/pa/nbsd.mh: Update renamed files.
	* config/pa/obsd.mh: Update renamed files.
	* config/powerpc/fbsd.mh: Update renamed files.
	* config/powerpc/nbsd.mh: Update renamed files.
	* config/powerpc/obsd.mh: Update renamed files.
	* config/sh/nbsd.mh: Update renamed files.
	* config/sparc/fbsd.mh: Update renamed files.
	* config/sparc/nbsd64.mh: Update renamed files.
	* config/sparc/nbsdelf.mh: Update renamed files.
	* config/sparc/obsd64.mh: Update renamed files.
	* config/vax/nbsdelf.mh: Update renamed files.
	* config/vax/obsd.mh: Update renamed files.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Makefiles: Flatten and sort file lists
@ 2016-11-23 15:19 sergiodj+buildbot
  2016-11-23 20:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Delete duplicate target short-cuts to dynamic sections
@ 2016-11-23  8:40 sergiodj+buildbot
  2016-11-23 15:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  8:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce558b89b15a18fd67fdc02a4d410a6d92d2ba63 ***

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

Delete duplicate target short-cuts to dynamic sections

We'd like to have the elf_link_hash_table srelplt field rather than
some private target field used to save short-cuts to a PLT relocation
section.  This save a little space but mainly is so that the generic
ELF code can access the field.  Ditto for other dynamic sections.

	* elf-m10300.c (mn10300_elf_check_relocs): Use elf htab shortcuts
	to dynamic sections.
	(mn10300_elf_final_link_relocate): Likewise.
	(_bfd_mn10300_elf_adjust_dynamic_symbol): Likewise.
	(_bfd_mn10300_elf_size_dynamic_sections): Likewise.
	(_bfd_mn10300_elf_finish_dynamic_symbol): Likewise.
	(_bfd_mn10300_elf_finish_dynamic_sections): Likewise.
	* elf32-bfin.c (bfin_check_relocs): Likewise.
	(bfin_relocate_section): Likewise.
	(bfin_gc_sweep_hook): Likewise.
	(struct bfinfdpic_elf_link_hash_table): Delete sgot, sgotrel, splt
	and spltrel.
	(bfinfdpic_got_section, bfinfdpic_gotrel_section,
	bfinfdpic_plt_section, bfinfdpic_pltrel_section): Define using elf
	shortcut sections.
	(_bfin_create_got_section): Use elf htab shortcuts to dyn sections.
	Delete dead code.
	(bfin_finish_dynamic_symbol): Use elf htab shortcuts to dyn sections.
	(bfin_size_dynamic_sections): Likewise.
	* elf32-cr16.c (_bfd_cr16_elf_create_got_section): Likewise.
	(cr16_elf_check_relocs): Likewise.
	(cr16_elf_final_link_relocate): Likewise.
	(_bfd_cr16_elf_create_dynamic_sections): Likewise.
	(_bfd_cr16_elf_adjust_dynamic_symbol): Likewise.
	(_bfd_cr16_elf_size_dynamic_sections): Likewise.
	(_bfd_cr16_elf_finish_dynamic_symbol): Likewise.
	(_bfd_cr16_elf_finish_dynamic_sections): Likewise.
	* elf32-cris.c (cris_elf_relocate_section): Likewise.
	(elf_cris_finish_dynamic_symbol): Likewise.
	(elf_cris_finish_dynamic_sections): Likewise.
	(cris_elf_gc_sweep_hook): Likewise.
	(elf_cris_adjust_gotplt_to_got): Likewise.
	(elf_cris_adjust_dynamic_symbol): Likewise.
	(cris_elf_check_relocs): Likewise.  Delete dead code.
	(elf_cris_size_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(elf_cris_discard_excess_program_dynamics): Likewise.
	* elf32-frv.c (struct frvfdpic_elf_link_hash_table): Delete sgot,
	sgotrel, splt and spltrel.
	(frvfdpic_got_section, frvfdpic_gotrel_section,
	frvfdpic_plt_section, frvfdpic_pltrel_section): Define using elf
	shortcut sections.
	(_frv_create_got_section): Likewise.
	* elf32-hppa.c (struct elf32_hppa_link_hash_table): Delete sgot,
	srelgot, splt and srelplt.
	(hppa_build_one_stub): Use elf htab shortcuts to dynamic sections.
	(elf32_hppa_create_dynamic_sections): Likewise.
	(elf32_hppa_check_relocs): Likewise.
	(allocate_plt_static): Likewise.
	(allocate_dynrelocs): Likewise.
	(elf32_hppa_size_dynamic_sections): Likewise.
	(elf32_hppa_relocate_section): Likewise.
	(elf32_hppa_finish_dynamic_symbol): Likewise.
	(elf32_hppa_finish_dynamic_sections): Likewise.
	* elf32-i370.c (i370_elf_finish_dynamic_sections): Likewise.
	* elf32-lm32.c (struct elf_lm32_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(lm32fdpic_got_section, lm32fdpic_gotrel_section): Define using elf
	shortcut sections.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(lm32_elf_relocate_section): Use elf htab shortcuts to dyn sections.
	(lm32_elf_check_relocs): Likewise.
	(lm32_elf_finish_dynamic_sections): Likewise.
	(lm32_elf_finish_dynamic_symbol): Likewise.
	(allocate_dynrelocs): Likewise.
	(lm32_elf_size_dynamic_sections): Likewise.
	(lm32_elf_create_dynamic_sections): Likewise.
	* elf32-m32c.c (m32c_elf_relocate_section): Likewise.
	(m32c_elf_check_relocs): Likewise.
	(m32c_elf_finish_dynamic_sections): Likewise.
	(m32c_elf_always_size_sections): Likewise.
	* elf32-m32r.c (struct elf_m32r_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(m32r_elf_create_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(allocate_dynrelocs): Likewise.
	(m32r_elf_size_dynamic_sections): Likewise.
	(m32r_elf_relocate_section): Likewise.
	(m32r_elf_finish_dynamic_symbol): Likewise.
	(m32r_elf_finish_dynamic_sections): Likewise.
	(m32r_elf_check_relocs): Likewise.
	* elf32-m68k.c (elf_m68k_partition_multi_got): Likewise.
	(elf_m68k_check_relocs): Likewise.
	(elf_m68k_adjust_dynamic_symbol): Likewise.
	(elf_m68k_size_dynamic_sections): Likewise.
	(elf_m68k_relocate_section): Likewise.
	(elf_m68k_finish_dynamic_symbol): Likewise.
	(elf_m68k_finish_dynamic_sections): Likewise.
	* elf32-metag.c (struct elf_metag_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(elf_metag_relocate_section): Use elf htab shortcuts to dynamic
	sections.
	(elf_metag_create_dynamic_sections): Likewise.  Allocate got header
	here in .got.
	(elf_metag_check_relocs): Use elf htab shortcuts to dynamic sections.
	(allocate_dynrelocs): Likewise.
	(elf_metag_size_dynamic_sections): Likewise.
	(elf_metag_finish_dynamic_symbol): Likewise.
	(elf_metag_finish_dynamic_sections): Likewise.
	(elf_metag_size_stubs): Likewise.
	(elf_backend_got_header_size): Don't define.
	(elf_backend_want_got_plt): Define.
	* elf32-microblaze.c (struct elf32_mb_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelpl.
	(microblaze_elf_relocate_section): Use elf htab shortcuts to dynamic
	sections.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(microblaze_elf_check_relocs): Use elf htab shortcuts to dyn sections.
	(microblaze_elf_create_dynamic_sections): Likewise.
	(allocate_dynrelocs): Likewise.
	(microblaze_elf_size_dynamic_sections): Likewise.
	(microblaze_elf_finish_dynamic_symbol): Likewise.
	(microblaze_elf_finish_dynamic_sections): Likewise.
	* elf32-nds32.c (nds32_elf_link_hash_table_create): Don't NULL
	already zero fields.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(nds32_elf_create_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(allocate_dynrelocs): Likewise.
	(nds32_elf_size_dynamic_sections): Likewise.
	(nds32_elf_relocate_section): Likewise.
	(nds32_elf_finish_dynamic_symbol): Likewise.
	(nds32_elf_finish_dynamic_sections): Likewise.
	(nds32_elf_check_relocs): Likewise.
	(calculate_plt_memory_address): Likewise.
	(calculate_got_memory_address): Likewise.
	* elf32-nds32.h (struct elf_nds32_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	* elf32-or1k.c (struct elf_or1k_link_hash_table): Likewise.
	(or1k_elf_relocate_section): Use elf htab shortcuts to dyn sections.
	(create_got_section): Delete.  Use _bfd_elf_create_got_section instead.
	(or1k_elf_check_relocs): Use elf htab shortcuts to dynamic sections.
	(or1k_elf_finish_dynamic_sections): Likewise.
	(or1k_elf_finish_dynamic_symbol): Likewise.
	(allocate_dynrelocs): Likewise.
	(or1k_elf_size_dynamic_sections): Likewise.
	(or1k_elf_create_dynamic_sections): Likewise.
	* elf32-ppc.c (struct ppc_elf_link_hash_table): Delete got, relgot,
	plt, relplt, iplt, reliplt and sgotplt.
	(ppc_elf_create_got): Use elf htab shortcuts to dynamic sections.
	(ppc_elf_create_glink): Likewise.
	(ppc_elf_create_dynamic_sections): Likewise.
	(ppc_elf_check_relocs): Likewise.
	(ppc_elf_select_plt_layout): Likewise.
	(ppc_elf_tls_setup): Likewise.
	(allocate_got): Likewise.
	(allocate_dynrelocs): Likewise.
	(ppc_elf_size_dynamic_sections): Likewise.
	(ppc_elf_relax_section): Likewise.
	(ppc_elf_relocate_section): Likewise.
	(ppc_elf_finish_dynamic_symbol): Likewise.
	(ppc_elf_reloc_type_class): Likewise.
	(ppc_elf_finish_dynamic_sections): Likewise.
	* elf32-rl78.c (rl78_elf_relocate_section): Likewise.
	(rl78_elf_check_relocs): Likewise.
	(rl78_elf_finish_dynamic_sections): Likewise.
	(rl78_elf_always_size_sections): Likewise.
	* elf32-s390.c 	(create_got_section): Delete.
	(elf_s390_create_dynamic_sections): Use _bfd_elf_create_got_section.
	(elf_s390_check_relocs): Likewise.
	* elf32-score.c (score_elf_create_got_section): Set elf shortcuts.
	(s3_bfd_score_elf_finish_dynamic_sections): Use elf shortcuts.
	* elf32-score7.c (score_elf_create_got_section): As above.
	(s7_bfd_score_elf_finish_dynamic_sections): As above.
	* elf32-sh.c (struct elf_sh_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(create_got_section): Don't set them.
	(sh_elf_create_dynamic_sections): Use elf htab shortcuts to dynamic
	sections.
	(allocate_dynrelocs): Likewise.
	(sh_elf_size_dynamic_sections): Likewise.
	(sh_elf_add_rofixup): Likewise.
	(sh_elf_relocate_section): Likewise.
	(sh_elf_check_relocs): Likewise.
	(sh_elf_finish_dynamic_symbol): Likewise.
	(sh_elf_finish_dynamic_sections): Likewise.
	* elf32-tic6x.c (elf32_tic6x_finish_dynamic_symbol): Likewise.
	* elf32-tilepro.c (tilepro_elf_create_got_section): Likewise.
	* elf32-vax.c (elf_vax_check_relocs): Likewise.
	(elf_vax_adjust_dynamic_symbol): Likewise.
	(elf_vax_always_size_sections): Likewise.
	(elf_vax_instantiate_got_entries): Likewise.
	(elf_vax_relocate_section): Likewise.
	(elf_vax_finish_dynamic_symbol): Likewise.
	(elf_vax_finish_dynamic_sections): Likewise.
	* elf32-xstormy16.c (xstormy16_elf_check_relocs): Likewise.
	(xstormy16_elf_always_size_sections): Likewise.
	(xstormy16_elf_relocate_section): Likewise.
	(xstormy16_elf_finish_dynamic_sections): Likewise.
	* elf32-xtensa.c (struct elf_xtensa_link_hash_table): Delete sgot,
	sgotplt, srelgot, splt and srelplt.
	(elf_xtensa_create_dynamic_sections): Use elf htab shortcuts to
	dynamic sections.
	(elf_xtensa_allocate_dynrelocs): Likewise.
	(elf_xtensa_allocate_local_got_size): Likewise.
	(elf_xtensa_size_dynamic_sections): Likewise.
	(elf_xtensa_relocate_section): Likewise.
	(elf_xtensa_finish_dynamic_sections): Likewise.
	(shrink_dynamic_reloc_sections): Likewise.
	(elf_xtensa_get_plt_section): Likewise.
	(elf_xtensa_get_gotplt_section): Likewise.
	(xtensa_callback_required_dependence): Likewise.
	* elf64-alpha.c (elf64_alpha_create_dynamic_sections): Set elf htab
	shortcuts to dynamic sections.
	(elf64_alpha_adjust_dynamic_symbol): Use elf htab shortcuts to
	dynamic sections.
	(elf64_alpha_size_plt_section): Likewise.
	(elf64_alpha_size_rela_got_1): Likewise.
	(elf64_alpha_size_rela_got_section): Likewise.
	(elf64_alpha_relocate_section): Likewise.
	(elf64_alpha_finish_dynamic_symbol): Likewise.
	(elf64_alpha_finish_dynamic_sections): Likewise.
	* elf64-hppa.c (elf64_hppa_size_dynamic_sections): Likewise.
	* elf64-s390.c (create_got_section): Delete.
	(elf_s390_create_dynamic_sections): Use _bfd_elf_create_got_section.
	(elf_s390_check_relocs): Likewise.
	* elf64-sh64.c (sh_elf64_relocate_section): Use elf htab shortcuts to
	dynamic sections.
	(sh_elf64_check_relocs): Likewise.
	(sh64_elf64_adjust_dynamic_symbol): Likewise.
	(sh64_elf64_size_dynamic_sections): Likewise.
	(sh64_elf64_finish_dynamic_symbol): Likewise.
	(sh64_elf64_finish_dynamic_sections): Likewise.
	* elflink.c (_bfd_elf_create_got_section): Likewise.
	* elfnn-aarch64.c (aarch64_elf_create_got_section): Likewise.
	* elfnn-ia64.c (elfNN_ia64_size_dynamic_sections): Likewise.
	(elfNN_ia64_finish_dynamic_sections): Likewise.
	* elfnn-riscv.c (riscv_elf_create_got_section): Likewise.
	* elfxx-mips.c (struct mips_elf_link_hash_table): Delete srellt,
	sgotplt, splt and sgot.
	(mips_elf_initialize_tls_slots): Use elf htab shortcuts to dynamic
	sections.
	(mips_elf_gotplt_index): Likewise.
	(mips_elf_primary_global_got_index): Likewise.
	(mips_elf_global_got_index): Likewise.
	(mips_elf_got_offset_from_index): Likewise.
	(mips_elf_create_local_got_entry): Likewise.
	(mips_elf_create_got_section): Likewise.
	(mips_elf_calculate_relocation): Likewise.
	(_bfd_mips_elf_create_dynamic_sections): Likewise.
	(_bfd_mips_elf_adjust_dynamic_symbol): Likewise.
	(mips_elf_lay_out_got): Likewise.
	(mips_elf_set_plt_sym_value): Likewise.
	(_bfd_mips_elf_size_dynamic_sections): Likewise.
	(_bfd_mips_elf_finish_dynamic_symbol): Likewise.
	(_bfd_mips_vxworks_finish_dynamic_symbol): Likewise.
	(mips_finish_exec_plt): Likewise.
	(mips_vxworks_finish_exec_plt): Likewise.
	(mips_vxworks_finish_shared_plt): Likewise.
	(_bfd_mips_elf_finish_dynamic_sections): Likewise.
	* elfxx-sparc.c (sparc_finish_dyn): Likewise.
	* elfxx-tilegx.c (tilegx_elf_create_got_section): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Regen POTFILES.in
@ 2016-11-23  7:46 sergiodj+buildbot
  2016-11-23 14:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-23  7:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ae0486cdce5d2ed4c922c598a3258fcbd9c8f29 ***

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

Regen POTFILES.in

bfd/
	* po/BLD-POTFILES.in: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.
gas/
	* po/POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: s390
@ 2016-11-22 20:47 sergiodj+buildbot
  2016-11-23  2:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad76968956f30bed6d120e0dfd247034e0855fea ***

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

gdbarch software_single_step frame_info to regcache: s390

gdb:

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

	* s390-linux-tdep.c (s390_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] 1903+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: sparc
@ 2016-11-22 20:15 sergiodj+buildbot
  2016-11-23  0:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd76b525eda02c30c4412698a2ff309b975d417a ***

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

gdbarch software_single_step frame_info to regcache: sparc

gdb:

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

	* sparc-tdep.c (sparc_analyze_control_transfer): Replace parameter
	frame with regcache.  Call get_current_frame.
	(sparc_software_single_step): Call get_regcache_arch instead of
	get_frame_arch.  Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 1903+ 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: moxie
@ 2016-11-22 18:47 sergiodj+buildbot
  2016-11-22 22:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8f341826d63a5c216c41e10bf1e4e6c3db3ce65 ***

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

gdbarch software_single_step frame_info to regcache: moxie

gdb:

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

	* moxie-tdep.c (moxie_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] 1903+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: cris
@ 2016-11-22 17:26 sergiodj+buildbot
  2016-11-22 19:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b6e2eee087cf206d5c2bf1f9523217aaf5938aa ***

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

gdbarch software_single_step frame_info to regcache: cris

gdb:

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

	* cris-tdep.c (find_step_target): 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.
	(cris_software_single_step): Call get_regcache_arch instead
	of get_frame_arch.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha
@ 2016-11-22 16:56 sergiodj+buildbot
  2016-11-22 18:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-22 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ab2d0874025af6ee858b32c576f2461c0a1df3d ***

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

gdbarch software_single_step frame_info to regcache: alpha

gdb:

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

	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Call
	get_regcache_arch instead of get_frame_arch.  Call
	regcache_read_pc instead of get_frame_pc.
	(alpha_next_pc): Replace parameter frame with regcache.
	Call regcache_raw_get_unsigned instead of
	get_frame_register_unsigned.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use input_bfd in relocate_section
@ 2016-11-22 10:39 sergiodj+buildbot
  2016-11-22 11:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add missing POSTCOMPILE step to mi/ file generation rules
@ 2016-11-21 21:38 sergiodj+buildbot
  2016-11-22  2:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Create subobject value in pretty printer
@ 2016-11-21 14:37 sergiodj+buildbot
  2016-11-21 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 12:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 combined pointer authentication load instructions
@ 2016-11-18 11:23 sergiodj+buildbot
  2016-11-18 12:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-18 11:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f06e55061d0d8f72dfd11f6c432c23f45d9b597 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 3f06e55061d0d8f72dfd11f6c432c23f45d9b597

[AArch64] Add ARMv8.3 combined pointer authentication load instructions

Add support for ARMv8.3 LDRAA and LDRAB combined pointer authentication and
load instructions.

These instructions authenticate the base register and load 8 byte from it plus
a scaled 10-bit offset with optional writeback to update the base register.

A new instruction class (ldst_imm10) and operand type (AARCH64_OPND_ADDR_SIMM10)
were introduced to handle the special addressing form.

include/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* opcode/aarch64.h (enum aarch64_opnd): Add AARCH64_OPND_ADDR_SIMM10.
	(enum aarch64_insn_class): Add ldst_imm10.

opcodes/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-tbl.h (QL_X1NIL): New.
	(arch64_opcode_table): Add ldraa, ldrab.
	(AARCH64_OPERANDS): Add "ADDR_SIMM10".
	* aarch64-asm.h (aarch64_ins_addr_simm10): Declare.
	* aarch64-asm.c (aarch64_ins_addr_simm10): Define.
	* aarch64-dis.h (aarch64_ext_addr_simm10): Declare.
	* aarch64-dis.c (aarch64_ext_addr_simm10): Define.
	* aarch64-opc.h (enum aarch64_field_kind): Add FLD_S_simm10.
	* aarch64-opc.c (fields): Add data for FLD_S_simm10.
	(operand_general_constraint_met_p): Handle AARCH64_OPND_ADDR_SIMM10.
	(aarch64_print_operand): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

gas/
2016-11-18  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* config/tc-aarch64.c (parse_operands): Handle AARCH64_OPND_ADDR_SIMM10.
	(fix_insn): Likewise.
	(warn_unpredictable_ldst): Handle ldst_imm10.
	* testsuite/gas/aarch64/pac.s: Add ldraa and ldrab tests.
	* testsuite/gas/aarch64/pac.d: Likewise.
	* testsuite/gas/aarch64/illegal-ldraa.s: New.
	* testsuite/gas/aarch64/illegal-ldraa.l: New.
	* testsuite/gas/aarch64/illegal-ldraa.d: New.


^ permalink raw reply	[flat|nested] 1903+ 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 12:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Makefile: Replace explicit subdir rules with pattern rules
@ 2016-11-17 20:10 sergiodj+buildbot
  2016-11-17 23:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 20:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 470dd0a647c95a2e88c5b0f8df538826b08959a8 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 470dd0a647c95a2e88c5b0f8df538826b08959a8

Makefile: Replace explicit subdir rules with pattern rules

When adding a .c file in subdirectory (e.g. mi/), the current practice
is to add an explicit rule, such as:

  mi-cmd-break.o: $(srcdir)/mi/mi-cmd-break.c
          $(COMPILE) $(srcdir)/mi/mi-cmd-break.c
          $(POSTCOMPILE)

I find it a bit verbose and cumbersome.  Since we now require GNU make,
we can change those rules with pattern rules, one for each subdirectory.
For example, the following rule works for all files under mi:

  %.o: $(srcdir)/mi/%.c
          $(COMPILE) $<
          $(POSTCOMPILE)

Those pattern rules assume that the source and target files have the
same stem (foo.c and foo.o).  In one case, common-agent.o is generated
from common/agent.c, to avoid a conflict with the agent.o in gdb/.  In
this case, I kept the explicit rule, which takes precedence over the
pattern rule.  We could also rename common/agent.c to
common/common-agent.c to get rid of the special case and still avoid the
clash, as it is done with common/common-regcache.c, for example.

This strategy was the least intrusive I found, as it only requires
changing the rules, not the target names.

I also considered two other solutions, which I did not like because I
would have had to change target names a bit everywhere.

  - Replicate the source directory structure in the build directory,
    which would generate common/agent.o from common/agent.c.  However,
    something was not right with the dependency tracking (the .deps
    directory).  It's probably not hard to fix, but I did not
    investigate further.
  - Name the object files after the directory they are in, so that
    common/agent.c would generate common_agent.c.

GDBserver can benefit from the same treatment, but I'll do it in another
patch.

Built-tested with --enable-targets=all.

New in v2:

  - Regroup pattern rules for .c -> .o compilation in a single place.
  - Add comment about common-agent.o.

gdb/ChangeLog:

	(PYTHON_CFLAGS): Move up.
	(%.o: $(srcdir)/arch/%.c): New rule.
	(%.o: $(srcdir)/cli/%.c): New rule.
	(%.o: $(srcdir)/common/%.c): New rule.
	(%.o: $(srcdir)/compile/%.c): New rule.
	(%.o: $(srcdir)/gdbtk/generic/%.c): New rule.
	(%.o: $(srcdir)/guile/%.c): New rule.
	(%.o: $(srcdir)/mi/%.c): New rule.
	(%.o: $(srcdir)/nat/%.c): New rule.
	(%.o: $(srcdir)/python/%.c): New rule.
	(%.o: $(srcdir)/target/%.c): New rule.
	(%.o: $(srcdir)/tui/%.c): New rule.
	(cli-cmds.o): Remove.
	(cli-decode.o): Likewise.
	(cli-dump.o): Likewise.
	(cli-interp.o): Likewise.
	(cli-logging.o): Likewise.
	(cli-script.o): Likewise.
	(cli-setshow.o): Likewise.
	(cli-utils.o): Likewise.
	(compile.o): Likewise.
	(compile-c-types.o): Likewise.
	(compile-c-symbols.o): Likewise.
	(compile-object-load.o): Likewise.
	(compile-object-run.o): Likewise.
	(compile-loc2c.o): Likewise.
	(compile-c-support.o): Likewise.
	(gdbtk.o): Likewise.
	(gdbtk-bp.o): Likewise.
	(gdbtk-cmds.o): Likewise.
	(gdbtk-hooks.o): Likewise.
	(gdbtk-interp.o): Likewise.
	(gdbtk-main.o): Likewise.
	(gdbtk-register.o): Likewise.
	(gdbtk-stack.o): Likewise.
	(gdbtk-varobj.o): Likewise.
	(gdbtk-wrapper.o): Likewise.
	(mi-cmd-break.o): Likewise.
	(mi-cmd-catch.o): Likewise.
	(mi-cmd-disas.o): Likewise.
	(mi-cmd-env.o): Likewise.
	(mi-cmd-file.o): Likewise.
	(mi-cmd-info.o): Likewise.
	(mi-cmds.o): Likewise.
	(mi-cmd-stack.o): Likewise.
	(mi-cmd-target.o): Likewise.
	(mi-cmd-var.o): Likewise.
	(mi-console.o): Likewise.
	(mi-getopt.o): Likewise.
	(mi-interp.o): Likewise.
	(mi-main.o): Likewise.
	(mi-out.o): Likewise.
	(mi-parse.o): Likewise.
	(mi-symbol-cmds.o): Likewise.
	(mi-common.o): Likewise.
	(signals.o): Likewise.
	(common-utils.o): Likewise.
	(gdb_vecs.o): Likewise.
	(xml-utils.o): Likewise.
	(ptid.o): Likewise.
	(buffer.o): Likewise.
	(filestuff.o): Likewise.
	(format.o): Likewise.
	(vec.o): Likewise.
	(print-utils.o): Likewise.
	(rsp-low.o): Likewise.
	(errors.o): Likewise.
	(common-debug.o): Likewise.
	(cleanups.o): Likewise.
	(common-exceptions.o
	(posix-strerror.o): Likewise.
	(mingw-strerror.o): Likewise.
	(btrace-common.o): Likewise.
	(fileio.o): Likewise.
	(common-regcache.o): Likewise.
	(signals-state-save-restore.o): Likewise.
	(new-op.o): Likewise.
	(waitstatus.o): Likewise.
	(arm.o): Likewise.
	(arm-linux.o): Likewise.
	(arm-get-next-pcs.o): Likewise.
	(x86-dregs.o): Likewise.
	(linux-btrace.o): Likewise.
	(linux-osdata.o): Likewise.
	(linux-procfs.o): Likewise.
	(linux-ptrace.o): Likewise.
	(linux-waitpid.o): Likewise.
	(mips-linux-watch.o): Likewise.
	(ppc-linux.o): Likewise.
	(linux-personality.o): Likewise.
	(x86-linux.o): Likewise.
	(x86-linux-dregs.o): Likewise.
	(amd64-linux-siginfo.o): Likewise.
	(linux-namespaces.o): Likewise.
	(aarch64-linux-hw-point.o): Likewise.
	(aarch64-linux.o): Likewise.
	(aarch64-insn.o): Likewise.
	(tui.o): Likewise.
	(tui-command.o): Likewise.
	(tui-data.o): Likewise.
	(tui-disasm.o): Likewise.
	(tui-file.o): Likewise.
	(tui-hooks.o): Likewise.
	(tui-interp.o): Likewise.
	(tui-io.o): Likewise.
	(tui-layout.o): Likewise.
	(tui-out.o): Likewise.
	(tui-regs.o): Likewise.
	(tui-source.o): Likewise.
	(tui-stack.o): Likewise.
	(tui-win.o): Likewise.
	(tui-windata.o): Likewise.
	(tui-wingeneral.o): Likewise.
	(tui-winsource.o): Likewise.
	(guile.o): Likewise.
	(scm-arch.o): Likewise.
	(scm-auto-load.o): Likewise.
	(scm-block.o): Likewise.
	(scm-breakpoint.o): Likewise.
	(scm-cmd.o): Likewise.
	(scm-disasm.o): Likewise.
	(scm-exception.o): Likewise.
	(scm-frame.o): Likewise.
	(scm-gsmob.o): Likewise.
	(scm-iterator.o): Likewise.
	(scm-lazy-string.o): Likewise.
	(scm-math.o): Likewise.
	(scm-objfile.o): Likewise.
	(scm-param.o): Likewise.
	(scm-ports.o): Likewise.
	(scm-pretty-print.o): Likewise.
	(scm-progspace.o): Likewise.
	(scm-safe-call.o): Likewise.
	(scm-string.o): Likewise.
	(scm-symbol.o): Likewise.
	(scm-symtab.o): Likewise.
	(scm-type.o): Likewise.
	(scm-utils.o): Likewise.
	(scm-value.o): Likewise.
	(python.o): Likewise.
	(py-arch.o): Likewise.
	(py-auto-load.o): Likewise.
	(py-block.o): Likewise.
	(py-bpevent.o): Likewise.
	(py-breakpoint.o): Likewise.
	(py-cmd.o): Likewise.
	(py-continueevent.o): Likewise.
	(py-xmethods.o): Likewise.
	(py-event.o): Likewise.
	(py-evtregistry.o): Likewise.
	(py-evts.o): Likewise.
	(py-exitedevent.o): Likewise.
	(py-finishbreakpoint.o): Likewise.
	(py-frame.o): Likewise.
	(py-framefilter.o): Likewise.
	(py-function.o): Likewise.
	(py-gdb-readline.o): Likewise.
	(py-inferior.o): Likewise.
	(py-infevents.o): Likewise.
	(py-infthread.o): Likewise.
	(py-lazy-string.o): Likewise.
	(py-linetable.o): Likewise.
	(py-newobjfileevent.o): Likewise.
	(py-objfile.o): Likewise.
	(py-param.o): Likewise.
	(py-prettyprint.o): Likewise.
	(py-progspace.o): Likewise.
	(py-signalevent.o): Likewise.
	(py-stopevent.o): Likewise.
	(py-symbol.o): Likewise.
	(py-symtab.o): Likewise.
	(py-threadevent.o): Likewise.
	(py-type.o): Likewise.
	(py-unwind.o): Likewise.
	(py-utils.o): Likewise.
	(py-value.o): Likewise.
	(py-varobj.o): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Makefile: Replace old suffix rules with pattern rules
@ 2016-11-17 19:35 sergiodj+buildbot
  2016-11-17 22:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 19:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5443506ee45cb94769db7e76dd2021a96f2f0680 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 5443506ee45cb94769db7e76dd2021a96f2f0680

Makefile: Replace old suffix rules with pattern rules

As mentioned here [1], suffix rules are obsolete and have been
superseeded with pattern rules.  People (myself included, before writing
this patch) are more likely to know what pattern rules are than suffix
rules.

AFAIK, .SUFFIXES targets are only used for those rules, and can be
removed as well.

New in v2:

  - Replace rule in gdbserver/Makefile.in as well.

[1] https://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html

gdb/ChangeLog:

	* Makefile.in (.c.o): Replace rule with ...
	(%.o: %.c): ... this one.
	(.po.gmo): Replace rule with ...
	(%.gmo: %.po): ... this one.
	(.po.pox): Replace rule with ...
	(%.pox: %.po): ... this one.
	(.y.c): Replace rule with ...
	(%.c: %.y): ... this one.
	(.l.c): Replace rule with ...
	(%.c: %.l): ... this one.
	(.SUFFIXES): Remove all instances.

gdb/gdbserver/ChangeLog:

	* Makefile.in (.c.o): Replace rule with ...
	(%.o: %.c): ... this one.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Document new hard requirement on GNU make
@ 2016-11-17 18:31 sergiodj+buildbot
  2016-11-17 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb/c-exp.y: fprintf -> parser_fprintf
@ 2016-11-17 16:49 sergiodj+buildbot
  2016-11-17 17:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-17 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 66be918f5f9f78d74c70aa332756286ff9d0ccf2 ***

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

gdb/c-exp.y: fprintf -> parser_fprintf

Switching GDB to make use of gnulib's C++ namespace support mode
revealed these direct uses of fprintf in the C parser, where
parser_fprintf should be used to handle rewiring stderr to gdb_stderr:

 ..../src/gdb/c-exp.y: In function void c_print_token(FILE*, int, YYSTYPE):
 ..../src/gdb/c-exp.y:3220:45: error: call to fprintf declared with attribute warning: The symbol ::fprintf refers to the system function. Use gnulib::fprintf instead. [-Werror]
	  pulongest (value.typed_val_int.val));
					      ^
 ..../src/gdb/c-exp.y:3231:62: error: call to fprintf declared with attribute warning: The symbol ::fprintf refers to the system function. Use gnulib::fprintf instead. [-Werror]
   fprintf (file, "tsval<type=%d, %s>", value.tsval.type, copy);
							       ^
 ..../src/gdb/c-exp.y:3237:57: error: call to fprintf declared with attribute warning: The symbol ::fprintf refers to the system function. Use gnulib::fprintf instead. [-Werror]
	fprintf (file, "sval<%s>", copy_name (value.sval));
							  ^
 ..../src/gdb/c-exp.y:3243:39: error: call to fprintf declared with attribute warning: The symbol ::fprintf refers to the system function. Use gnulib::fprintf instead. [-Werror]
	  copy_name (value.tsym.stoken));
					^
 ..../src/gdb/c-exp.y:3254:39: error: call to fprintf declared with attribute warning: The symbol ::fprintf refers to the system function. Use gnulib::fprintf instead. [-Werror]
	  value.ssym.is_a_field_of_this);
					^
 ..../src/gdb/c-exp.y:3258:70: error: call to fprintf declared with attribute warning: The symbol ::fprintf refers to the system function. Use gnulib::fprintf instead. [-Werror]
	fprintf (file, "bval<%s>", host_address_to_string (value.bval));
                                                                      ^

gdb/ChangeLog:
2016-11-17  Pedro Alves  <palves@redhat.com>

	* c-exp.y (c_print_token): Use parser_fprintf instead of fprintf.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID
@ 2016-11-16 22:04 sergiodj+buildbot
  2016-11-17  1:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 22:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41b56feb5063aee4fefb4a991eb796d1e8a7475e ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 41b56feb5063aee4fefb4a991eb796d1e8a7475e

Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID

The VALUE_FRAME_ID macro provides access to a member in struct value
that's used to hold the frame id that's used when determining a
register's value or when assigning to a register.  The underlying
member has a long and obscure name.  I won't refer to it here, but
will simply refer to VALUE_FRAME_ID as if it's the struct value member
instead of being a convenient macro.

At the moment, without this patch in place, VALUE_FRAME_ID is set in
value_of_register_lazy() and several other locations to hold the frame
id of the frame passed to those functions.

VALUE_FRAME_ID is used in the lval_register case of
value_fetch_lazy().  To fetch the register's value, it calls
get_frame_register_value() which, in turn, calls
frame_unwind_register_value() with frame->next.

A python based unwinder may wish to determine the value of a register
or evaluate an expression containing a register.  When it does this,
value_fetch_lazy() will be called under some circumstances.  It will
attempt to determine the frame id associated with the frame passed to
it.  In so doing, it will end up back in the frame sniffer of the very
same python unwinder that's attempting to learn the value of a
register as part of the sniffing operation.  This recursion is not
desirable.

As noted above, when value_fetch_lazy() wants to fetch a register's
value, it does so (indirectly) by unwinding from frame->next.

With this in mind, a solution suggests itself:  Change VALUE_FRAME_ID
to hold the frame id associated with the next frame.  Then, when it
comes time to obtain the value associated with the register, we can
simply unwind from the frame corresponding to the frame id stored in
VALUE_FRAME_ID.  This neatly avoids the python unwinder recursion
problem by changing when the "next" operation occurs.  Instead of the
"next" operation occuring when the register value is fetched, it
occurs earlier on when assigning a frame id to VALUE_FRAME_ID.
(Thanks to Pedro for this suggestion.)

This patch implements this idea.

It builds on the patch "Distinguish sentinel frame from null frame".
Without that work in place, it's necessary to check for null_id at
several places and then obtain the sentinel frame.

It also renames most occurences of VALUE_FRAME_ID to
VALUE_NEXT_FRAME_ID to reflect the new meaning of this field.

There are several uses of VALUE_FRAME_ID which were not changed.  In
each case, the original meaning of VALUE_FRAME_ID is required to get
correct results.  In all but one of these uses, either
put_frame_register_bytes() or get_frame_register_bytes() is being
called with the frame value obtained from VALUE_FRAME_ID.  Both of
these functions perform some unwinding by performing a "->next"
operation on the frame passed to it.  If we were to use the new
VALUE_NEXT_FRAME_ID macro, this would effectively do two "->next"
operations, which is not what we want.

The VALUE_FRAME_ID macro has been redefined in terms of
VALUE_NEXT_FRAME_ID.  It simply fetches the previous frame's id,
providing this id as the value of the macro.

gdb/ChangeLog:

	* value.h (VALUE_FRAME_ID): Rename to VALUE_NEXT_FRAME_ID. Update
	comment.  Create new VALUE_FRAME_ID which is defined in terms of
	VALUE_NEXT_FRAME_ID.
	(deprecated_value_frame_id_hack): Rename to
	deprecated_value_next_frame_id_hack.
	* dwarf2loc.c, findvar.c, frame-unwind.c, sentinel-frame.c,
	valarith.c, valops.c, value.c: Adjust nearly all occurences of
	VALUE_FRAME_ID to VALUE_NEXT_FRAME_ID.	Add comments for those
	which did not change.
	* value.c (struct value): Rename frame_id field to next_frame_id.
	Update comment.
	(deprecated_value_frame_id_hack): Rename to
	deprecated_value_next_frame_id_hack.
	(value_fetch_lazy): Call frame_unwind_register_value()
	instead of get_frame_register_value().
	* frame.c (get_prev_frame_id_by_id): New function.
	* frame.h (get_prev_frame_id_by_id): Declare.
	* dwarf2loc.c (dwarf2_evaluate_loc_desc_full): Make
	VALUE_NEXT_FRAME_ID refer to the next frame.
	* findvar.c (value_of_register_lazy): Likewise.
	(default_value_from_register): Likewise.
	(value_from_register): Likewise.
	* frame_unwind.c (frame_unwind_got_optimized): Likewise.
	* sentinel-frame.c (sentinel_frame_prev_register): Likewise.
	* value.h (VALUE_FRAME_ID): Update comment describing this macro.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Distinguish sentinel frame from null frame.
@ 2016-11-16 21:50 sergiodj+buildbot
  2016-11-17  0:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-16 21:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df433d316277ff5293832d3cd6cbc30b5c38dec0 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: df433d316277ff5293832d3cd6cbc30b5c38dec0

Distinguish sentinel frame from null frame.

This patch replaces the `current_frame' static global in frame.c with
`sentinel_frame'.  It also makes the sentinel frame id unique and
different from the null frame.

By itself, there is not much point to this patch, but it makes
the code cleaner for the VALUE_FRAME_ID changes in another patch.
Since we now allow "navigation" to the sentinel frame, it removes
the necessity of adding special cases to other parts of GDB.

Note that a new function, get_next_frame_sentinel_okay, is introduced
in this patch.  It will be used by the VALUE_FRAME_ID changes that
I've made.

Thanks to Pedro Alves for this suggestion.

gdb/ChangeLog:

    	* frame.h (enum frame_id_stack_status): Add FID_STACK_SENTINEL.
    	(struct frame_id): Increase number of bits required for storing
    	stack status to 3 from 2.
    	(sentinel_frame_id): New declaration.
    	(get_next_frame_sentinel_okay): Declare.
    	(frame_find_by_id_sentinel_okay): Declare.
    	* frame.c (current_frame): Rename this static global to...
    	(sentinel_frame): ...this static global, which has also been
    	moved an earlier location in the file.
    	(fprint_frame_id): Add case for sentinel frame id.
    	(get_frame_id): Return early for sentinel frame.
    	(sentinel_frame_id): Define.
    	(frame_find_by_id): Add case for sentinel_frame_id.
    	(create_sentinel_frame): Use sentinel_frame_id for this_id.value
    	instead of null_frame_id.
    	(get_current_frame): Add local declaration for `current_frame'.
    	Remove local declaration for `sentinel_frame.'
    	(get_next_frame_sentinel_okay): New function.
    	(reinit_frame_cache): Use `sentinel_frame' in place of
    	`current_frame'.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp
@ 2016-11-16 20:03 sergiodj+buildbot
  2016-11-16 22:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs
@ 2016-11-16 20:01 sergiodj+buildbot
  2016-11-16 21:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb::{unique_ptr,move} -> std::{unique_ptr,move}
@ 2016-11-15 20:54 sergiodj+buildbot
  2016-11-15 23:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition
@ 2016-11-15 20:24 sergiodj+buildbot
  2016-11-15 21:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] btrace: read entire aux buffer
@ 2016-11-14 10:28 sergiodj+buildbot
  2016-11-14 13:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-14 10:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db58b3735f45345c06cb9a14d0f83f5b26c1ebf3 ***

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

btrace: read entire aux buffer

The data_head of a perf event data buffer grows indefinitely.  Users are
expected to compute data_head % data_size to find the location inside the perf
event data buffer.

The aux_head of a perf event aux buffer wraps around and always stays within the
perf event aux buffer.

Well, at least that's the behaviour for BTS and PT - where BTS uses the data
buffer and PT the aux buffer.

GDB does not read beyond data_head or aux_head.  This is OK for BTS but wrong
for PT.  It causes only a portion of the trace to be considered by GDB.  In the
extreme case, the buffer may appear (almost) empty.

Thanks to Tim Wiederhake  <tim.wiederhake@intel.com> for reporting the anomaly.

Change it to read the entire aux buffer for PT.  The buffer is initially zero so
any extra zeroes we read before aux_head wraps around the first time will be
ignored when searching for the first PSB packet in order to synchronize onto the
trace stream.

gdb/
	* nat/linux-btrace.c (perf_event_read): Allow data_head < size.
	* nat/linux-btrace.c (perf_event_read_all): Do not adjust size.

Change-Id: If4f8049a2080a5f16f336309450b32a3eb1e3ec9


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix typo "Faal through" should be "Fall through".
@ 2016-11-14  9:18 sergiodj+buildbot
  2016-11-14 10:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-14  9:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63f2433dbccc7ddf8812fefd6eed0e6dd2f88955 ***

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

Fix typo "Faal through" should be "Fall through".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 instructions which are in the NOP space
@ 2016-11-11 15:42 sergiodj+buildbot
  2016-11-11 17:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8787d804e1cbbd1946239d6c5e560c87d38bac06 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 8787d804e1cbbd1946239d6c5e560c87d38bac06

[AArch64] Add ARMv8.3 instructions which are in the NOP space

This patch adds support for a subset of the ARMv8.3 pointer authentication
instructions: XPACLRI, PACIA1716, PACIB1716, AUTIA1716, AUTIA1716, PACIAZ,
PACIASP, PACIBZ, PACISP, AUTIAZ, AUTIASP, AUTIBZ, AUTIBSP.

These are aliases to HINT #0x7, HINT #0x8, HINT #0xa, HINT #0xc, HINT #0xe,
HINT #0x18, HINT #0x19, ..., HINT #0x1f respectively.

For more details about pointer authentication in ARMv8.3 see
https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

opcodes/
2016-11-11  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* aarch64-tbl.h (aarch64_feature_v8_3, ARMV8_3, V8_3_INSN): New.
	(arch64_opcode_table): Add xpaclri, pacia1716, pacib1716, autia1716,
	autib1716, paciaz, paciasp, pacibz, pacibsp, autiaz, autiasp, autibz,
	autibsp.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.

gas/
2016-11-11  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* testsuite/gas/aarch64/system-3.s: New.
	* testsuite/gas/aarch64/system-3.d: New.
	* testsuite/gas/aarch64/system.d: Update expected output.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Add ARMv8.3 command line option and feature flag
@ 2016-11-11 13:30 sergiodj+buildbot
  2016-11-11 15:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-11 13:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1924ff7567abf9e1341ae135fb5097bc5f7b76f4 ***

Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Branch: master
Commit: 1924ff7567abf9e1341ae135fb5097bc5f7b76f4

[AArch64] Add ARMv8.3 command line option and feature flag

ARMv8.3 can be selected with -march=armv8.3-a command line option.
An overview of the ARMv8.3 architecture extension is at
https://community.arm.com/groups/processors/blog/2016/10/27/armv8-a-architecture-2016-additions

gas/
2016-11-11  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* config/tc-aarch64.c (aarch64_archs): Add "armv8.3-a".
	* doc/c-aarch64.texi (-march): Likewise.

include/
2016-11-11  Szabolcs Nagy  <szabolcs.nagy@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_V8_3): Define.
	(AARCH64_ARCH_V8_3): Define.
	(AARCH64_ARCH_V8_1, AARCH64_ARCH_V8_2): Simplify.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr
@ 2016-11-11 12:02 sergiodj+buildbot
  2016-11-11 13:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove parameter valaddr from c print functions
@ 2016-11-11 10:40 sergiodj+buildbot
  2016-11-11 12:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] sim: mips: fix dv-tx3904cpu build error
@ 2016-11-11 10:09 sergiodj+buildbot
  2016-11-11 11:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] Bind defined symbol locally in PIE
@ 2016-11-10  9:30 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] tui-disasm: Fix window content buffer overrun
@ 2016-11-10  8:07 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use unique_xmalloc_ptr in Python code
@ 2016-11-10  7:49 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Further cleanup/modernization of gdb.base/commands.exp
@ 2016-11-10  7:48 sergiodj+buildbot
  2016-11-10 11:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] X86: Merge AVX512F vmovq
@ 2016-11-10  7:47 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] X86: Remove the .s suffix from EVEX vpextrw
@ 2016-11-10  7:47 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] agent_expr_up: gdb::unique_ptr -> std::unique_ptr
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb/testsuite: Introduce "proc_with_prefix"
@ 2016-11-10  7:45 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] tui-winsource: Remove failed-allocation logic
@ 2016-11-10  6:36 sergiodj+buildbot
  2016-11-10 12:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: Use vector::emplace_back
@ 2016-11-10  5:47 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] tui-disasm: Fix line buffer size calculation
@ 2016-11-10  4:19 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] tui-winsource: Allocate for actual lines only
@ 2016-11-10  3:59 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] darwin-nat.c: handle Darwin 16 (aka Sierra).
@ 2016-11-10  1:21 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix py-value.exp failure on Python 3
@ 2016-11-09 23:50 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry
@ 2016-11-09 23:16 sergiodj+buildbot
  2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix some error-handling bugs in python frame filters
@ 2016-11-09 21:50 sergiodj+buildbot
  2016-11-10 11:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove parameter valaddr from la_val_print
@ 2016-11-09 20:30 sergiodj+buildbot
  2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 11:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] 'struct agent_expr *' -> unique_ptr<agent_expr>
@ 2016-11-09 17:48 sergiodj+buildbot
  2016-11-10 11:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/language.c
@ 2016-11-09 15:45 sergiodj+buildbot
  2016-11-10  5:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/cli/cli-setshow.c
@ 2016-11-09  9:53 sergiodj+buildbot
  2016-11-09 16:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  9:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d8b0d9483f6eabc2c1739ac3dd64c30061a6a72 ***

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

Use ui_file_as_string in gdb/cli/cli-setshow.c

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* cli/cli-setshow.c (do_show_command): Adjust to use
	ui_file_as_string and std::string.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/remote.c
@ 2016-11-09  8:18 sergiodj+buildbot
  2016-11-09 15:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  8:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3ced9bad2d8d5eb9ebabc5f8f7c6ab871f63748 ***

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

Use ui_file_as_string in gdb/remote.c

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* remote.c (escape_buffer): Use ui_file_as_string and return
	std::string.
	(putpkt_binary, read_frame): Adjust to use std::string.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/python/
@ 2016-11-09  8:07 sergiodj+buildbot
  2016-11-09 13:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use ui_file_as_string in gdb/printcmd.c
@ 2016-11-09  6:37 sergiodj+buildbot
  2016-11-09 12:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-09  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02030646c2a799614d31e52008403d8be067ac5d ***

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

Use ui_file_as_string in gdb/printcmd.c

Yet another cleanup eliminated.

gdb/ChangeLog:
2016-11-08  Pedro Alves  <palves@redhat.com>

	* printcmd.c (eval_command): Use ui_file_as_string and
	std::string.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR breakpoints/20739: Badly formatted adress string in error message
@ 2016-11-08 14:21 sergiodj+buildbot
  2016-11-08 14:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 14:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53c3572a9f5b03a92292cb6d24bf69b52c95500e ***

Author: Cordian A. Daniluk <th3c0r1uk@gmail.com>
Branch: master
Commit: 53c3572a9f5b03a92292cb6d24bf69b52c95500e

Fix PR breakpoints/20739: Badly formatted adress string in error message

Remove duplicate `0x'-prefix for the hex address printed.  `paddress'
already prepends this, so no need to do it manually.

gdb/ChangeLog:
2016-11-08  Cordian A. Daniluk  <th3c0r1uk@gmail.com>

	PR breakpoints/20739
	* breakpoint.c (check_fast_tracepoint_sals): Don't print duplicate
	0x prefix.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix indentation
@ 2016-11-08 12:26 sergiodj+buildbot
  2016-11-08 12:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20955dbf718992e83b7c971344931934b62a784f ***

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

Fix indentation

gdb:

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

	* rust-lang.c (val_print_struct): Fix indentation.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Check for truncated registers in process_g_packet
@ 2016-11-08 11:14 sergiodj+buildbot
  2016-11-08 12:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-08 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9dc193c3be85aafa60ceff57d3b0430af607b4ce ***

Author: Lionel Flandrin <lionel@svkt.org>
Branch: master
Commit: 9dc193c3be85aafa60ceff57d3b0430af607b4ce

Check for truncated registers in process_g_packet

While investigating an unrelated issue in remote.c I noticed that the
bound checking for 'g' packets was bogus:

The previous code would only check that the first byte of the register
was within bounds before passing the buffer to regcache_raw_supply.
If it turned out that the register in the 'g' packet was incomplete
then regcache_raw_supply would proceed to memcpy out-of-bounds.

Since the buffer is allocated with alloca it's relatively unlikely to
crash (you just end up dumping gdb's stack into the cache) but it's
still a bit messy.

I changed this logic to check for truncated registers and raise an
error if one is encountered.  Hopefully it should make debugging
remote stubs a bit easier.

gdb/ChangeLog:
2016-11-08  Lionel Flandrin  <lionel@svkt.org>

	* remote.c (process_g_packet): Detect truncated registers in 'g'
	packets and raise an error.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Sync config.sub,config.guess with upstream.
@ 2016-11-07 21:48 sergiodj+buildbot
  2016-11-07 22:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-07 21:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ada5c6fca335963b0b9fb9e91c999fcdaab2f89 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 5ada5c6fca335963b0b9fb9e91c999fcdaab2f89

Sync config.sub,config.guess with upstream.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] arc/nps400: Validate address type operands correctly
@ 2016-11-04 23:14 sergiodj+buildbot
  2016-11-05  0:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-04 23:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b437d035ddf4e4c0c566c577ee059790ed28ad9b ***

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

arc/nps400: Validate address type operands correctly

When we match against an address type operand within an instruction it
is important that we match exactly the right address type operand early
on, during the opcode selection phase.  If we wait until the operand
insertion phase to check that we have the correct address operand, then
it is too late to select an alternative opcode.  This becomes important
only when we have multiple opcodes with the same mnemonic, and operand
lists that differ only in the type of the address operands.

This commit fixes this issue, and adds some example instructions that
require this issue to be fixed (the instructions are identical except
for the address type operand).

gas/ChangeLog:

	* config/tc-arc.c (find_opcode_match): Use insert function to
	validate matching address type operands.
	* testsuite/gas/arc/nps400-10.d: New file.
	* testsuite/gas/arc/nps400-10.s: New file.

opcodes/ChangeLog:

	* arc-opc.c (arc_flag_operands): Add F_DI14.
	(arc_flag_classes): Add C_DI14.
	* arc-nps400-tbl.h: Add new exc instructions.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix handling of discriminantless univariant enums in Rust; fix bug with encoded enums
@ 2016-11-03 23:05 sergiodj+buildbot
  2016-11-04 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 23:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51a789c3bf3d9b04d3d81493fda7f2514ae43add ***

Author: Manish Goregaokar <manish@mozilla.com>
Branch: master
Commit: 51a789c3bf3d9b04d3d81493fda7f2514ae43add

Fix handling of discriminantless univariant enums in Rust; fix bug with encoded enums

2016-10-27  Manish Goregaokar  <manish@mozilla.com>

gdb/ChangeLog:
    * rust-lang.c (rust_get_disr_info): Treat univariant enums
    without discriminants as encoded enums with a real field
    * rust-lang.c (rust_evaluate_subexp): Handle field access
    on encoded struct-like enums

gdb/testsuite/ChangeLog:
    * simple.rs: Add test for univariant enums without discriminants
    and for encoded struct-like enums
    * simple.exp: Add test expectations


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] arc: Implement NPS-400 dcmac instruction
@ 2016-11-03 18:59 sergiodj+buildbot
  2016-11-04 14:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a736821eff3aa4a8da237778526f9f700759c7a ***

Author: Graham Markall <graham.markall@embecosm.com>
Branch: master
Commit: 5a736821eff3aa4a8da237778526f9f700759c7a

arc: Implement NPS-400 dcmac instruction

gas/ChangeLog:

       * testsuite/gas/arc/nps-400-9.d: Added.
       * testsuite/gas/arc/nps-400-9.s: Added.

include/ChangeLog:

       * opcode/arc.h: Add PROTOCOL_DECODE to insn_class_t.

opcodes/ChangeLog:

       * arc-dis.c (arc_insn_length): Return length 8 for instructions with
       major opcode 0xa.
       * arc-nps-400-tbl.h: Add dcmac instruction.
       * arc-opc.c (arc_operands): Added operands for dcmac instruction.
       (insert_nps_rbdouble_64): Added.
       (extract_nps_rbdouble_64): Added.
       (insert_nps_proto_size): Added.
       (extract_nps_proto_size): Added.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove gdbarch_remote_breakpoint_from_pc
@ 2016-11-03 15:50 sergiodj+buildbot
  2016-11-03 22:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-03 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0f4a997c26760d2584946196ee5c411d1a632a6 ***

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

Remove gdbarch_remote_breakpoint_from_pc

This patch removes gdbarch method remote_breakpoint_from_pc, as it
is no longer used.

gdb:

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

	* arch-utils.c (default_remote_breakpoint_from_pc): Remove.
	* arch-utils.h (default_remote_breakpoint_from_pc): Remove.
	* arm-tdep.c (arm_remote_breakpoint_from_pc): Remove.
	(arm_gdbarch_init): Don't call
	set_gdbarch_remote_breakpoint_from_pc.
	* gdbarch.sh (remote_breakpoint_from_pc): Remove.
	* gdbarch.c, gdbarch.h: Regenerate.
	* mips-tdep.c (mips_remote_breakpoint_from_pc): Remove.
	(mips_gdbarch_init): Don't call
	set_gdbarch_remote_breakpoint_from_pc.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] BFD: Fix double BFD_FAIL calls in `bfd_default_reloc_type_lookup'
@ 2016-11-01 23:28 sergiodj+buildbot
  2016-11-02 19:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-11-01 23:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af955fe696088e69b436947b4a6f134567d31793 ***

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

BFD: Fix double BFD_FAIL calls in `bfd_default_reloc_type_lookup'

Break out of the outer switch statement once the inner switch for the
BFD_RELOC_CTOR relocation has been processed, preventing double BFD_FAIL
calls from being made, once from the inner switch and then again from
the default case of the outer switch.

Noticed with a `-Wimplicit-fallthrough' build error reported by a recent
GCC version:

In file included from .../bfd/reloc.c:52:0:
.../bfd/reloc.c: In function 'bfd_default_reloc_type_lookup':
.../bfd/libbfd.h:779:8: error: this statement may fall through [-Werror=implicit-fallthrough=]
   do { bfd_assert(__FILE__,__LINE__); } while (0)
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.../bfd/reloc.c:7780:4: note: in expansion of macro 'BFD_FAIL'
    BFD_FAIL ();
    ^~~~~~~~
.../bfd/reloc.c:7782:5: note: here
     default:
     ^~~~~~~
cc1: all warnings being treated as errors
make[4]: *** [reloc.lo] Error 1

	bfd/
	* reloc.c (bfd_default_reloc_type_lookup) <BFD_RELOC_CTOR>: Do
	not fall through to the default case.


^ permalink raw reply	[flat|nested] 1903+ 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-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix duplicate test message in mi-trace-save.exp
@ 2016-10-17 23:24 sergiodj+buildbot
  2016-10-17 23:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix comment in mi-trace-save.exp
@ 2016-10-17 21:50 sergiodj+buildbot
  2016-10-17 22:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: Fix phony iconv build
@ 2016-10-17 16:34 sergiodj+buildbot
  2016-10-17 16:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Removed pseudo invalid instructions opcodes.
@ 2016-10-17 13:56 sergiodj+buildbot
  2016-10-17 15:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Update list of ELF machine numbers.
@ 2016-10-17 11:03 sergiodj+buildbot
  2016-10-17 12:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Sync libiberty sources with gcc mainline.
@ 2016-10-17  9:46 sergiodj+buildbot
  2016-10-17 10:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix set sysroot command on AIX
@ 2016-10-14 13:25 sergiodj+buildbot
  2016-10-14 14:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Share proc get_var_address
@ 2016-10-13 15:27 sergiodj+buildbot
  2016-10-13 17:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-10-13 15:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ad9dba7519caa3e6193c87699ae37e24d0fe05c ***

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

Share proc get_var_address

This patch moves proc get_var_address into lib/gdb.exp, and remove the
duplicate copy in gdb.base/*.exp files.

gdb/testsuite:

2016-10-13  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/code_elim.exp (get_var_address): Remove.
	* gdb.base/relocate.exp: Likewise.
	* gdb.base/shreloc.exp: Likewise.
	* lib/gdb.exp (get_var_address): New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use std::string in macho_symfile_read_all_oso
@ 2016-10-13  5:24 sergiodj+buildbot
  2016-10-13  6:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove unnecessary null_cleanup
@ 2016-10-13  4:50 sergiodj+buildbot
  2016-10-13  5:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Turn wchar iterator into a class
@ 2016-10-13  2:59 sergiodj+buildbot
  2016-10-13  4:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] arc: Add support for Newlib
@ 2016-10-12 16:00 sergiodj+buildbot
  2016-10-12 17:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] arc: Add evaluation of long jump targets
@ 2016-10-12 13:32 sergiodj+buildbot
  2016-10-12 16:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] BFD_FAKE_SECTION macro params
@ 2016-10-11 23:35 sergiodj+buildbot
  2016-10-12  0:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-10-11 23:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 821e6ff6299aa39e841ca50e1ae8a98e3554fd5f ***

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

BFD_FAKE_SECTION macro params

Order NAME, IDX, FLAGS as per STD_SECTION macro.

	* section.c (BFD_FAKE_SECTION): Reorder parameters.  Formatting.
	(STD_SECTION): Adjust to suit.
	* elf.c (_bfd_elf_large_com_section): Likewise.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ 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:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Always descend into output section statements in lang_do_assignments
@ 2016-10-11  7:59 sergiodj+buildbot
  2016-10-11  8:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-10-11  7:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f02cb058822459ea29a9fdaa928c2623df435908 ***

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

Always descend into output section statements in lang_do_assignments

See https://sourceware.org/ml/binutils/2016-07/msg00091.html
This patch stop --gc-sections elf_gc_sweep_symbol localizing symbols
that ought to remain global.

The difficulty with always descending into output section statements
is that symbols defined by the script in such statements don't have
a bfd section when lang_do_assignments runs early in the link process.
There are two approaches to curing this problem.  Either we can
create the bfd section early, or we can use a special section.  This
patch takes the latter approach and uses bfd_und_section.  (Creating
bfd sections early results in changed output section order, and thus
lots of testsuite failures.  You can't create all output sections
early to ensure proper ordering as KEEP then stops empty sections
from being stripped.)

The wrinkle with this approach is that some code that runs at
gc-sections time needs to be made aware of the odd defined symbols
using bfd_und_section.

bfd/
	* elf64-x86-64.c (elf_x86_64_convert_load_reloc): Handle symbols
	defined temporarily with bfd_und_section.
	* elflink.c (_bfd_elf_gc_keep): Don't set SEC_KEEP for bfd_und_section.
	* elfxx-mips.c (mips_elf_local_pic_function_p): Exclude defined
	symbols with bfd_und_section.
ld/
	* ldlang.c (lang_do_assignments_1): Descend into output section
	statements that do not yet have bfd sections.  Set symbol section
	temporarily for symbols defined in such statements to the undefined
	section.  Don't error on data or reloc statements until final phase.
	* ldexp.c (exp_fold_tree_1 <etree_assign>): Handle bfd_und_section
	in expld.section.
	* testsuite/ld-mmix/bpo-10.d: Adjust.
	* testsuite/ld-mmix/bpo-11.d: Adjust.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Rename 'arch' by 'gdbarch' in m32c_gdbarch_init
@ 2016-10-10 10:37 sergiodj+buildbot
  2016-10-10 11:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] python: accept address and explicit locations in gdb.decode_line
@ 2016-10-07  7:22 sergiodj+buildbot
  2016-10-07 13:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-10-07  7:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68dadef54c216f7ec75c27d74193897b18c5f9ab ***

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

python: accept address and explicit locations in gdb.decode_line

The gdb.decode_line python function is documented to support the same location
expressions as the "break" command.  It currently expects a linespec location.

Instead of creating a linespec location directly, create the location via
string_to_event_location_basic.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.Value->python conversion for large unsigned ints.
@ 2016-10-07  4:51 sergiodj+buildbot
  2016-10-07  8:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Pass link_info to _bfd_merge_private_bfd_data
@ 2016-10-07  2:07 sergiodj+buildbot
  2016-10-07 12:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: Remove some C compiler support leftovers
@ 2016-10-06 23:29 sergiodj+buildbot
  2016-10-07  9:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove Java support
@ 2016-10-06 21:27 sergiodj+buildbot
  2016-10-06 21:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-10-06 21:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c37b5aed98e5996a9777a366bfcc371c0e1a92d ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9c37b5aed98e5996a9777a366bfcc371c0e1a92d

Remove Java support

This patch removes the Java support from gdb.  gcj has not seen much
development or use for years now, and was recently removed from GCC.
This patch changes gdb to follow; in the unlikely event that there are
still users using gcj, they can continue to use an older gdb to debug.
Or, they can debug in C++ mode.

Built and regtested on x86-64 Fedora 24.

2016-10-06  Tom Tromey  <tom@tromey.com>

	* MAINTAINERS: Remove Java test maintainer.
	* varobj.h (java_varobj_ops): Don't declare.
	* valprint.h (struct value_print_options)
	<pascal_static_field_print>: Update comment.
	* utils.c (producer_is_gcc): Remove java reference.
	* symtab.h (struct general_symbol_info): Remove java references.
	(SYMBOL_SEARCH_NAME): Likewise.
	* objfiles.c (allocate_objfile): Update comment.
	* linespec.c (find_linespec_symbols): Remove java references.
	* gnu-v3-abi.c (gnuv3_rtti_type, gnuv3_baseclass_offset): Remove
	java references.
	* gdbtypes.h (struct cplus_struct_type) <is_java>: Remove.
	(TYPE_CPLUS_REALLY_JAVA): Remove.
	* c-varobj.c (enum vsections): Update comment.
	* symtab.c (symbol_set_language, symbol_set_names)
	(symbol_natural_name, symbol_demangled_name)
	(demangle_for_lookup, symbol_matches_domain)
	(default_make_symbol_completion_list_break_on_1): Remove java
	references.
	(JAVA_PREFIX, JAVA_PREFIX_LEN): Remove.
	* psymtab.c (match_partial_symbol, psymtab_search_name)
	(lookup_partial_symbol): Remove java references.
	* dwarf2read.c (find_slot_in_mapped_hash): Remove java references.
	(add_partial_symbol, dwarf2_compute_name, dwarf2_physname)
	(dwarf2_add_member_fn, is_vtable_name, read_structure_type)
	(process_structure_scope, read_subroutine_type)
	(read_subrange_type, load_partial_dies)
	(new_symbol_full, determine_prefix, typename_concat)
	(dwarf2_name): Remove java references.
	(set_cu_language): Treat Java as C++.
	* c-typeprint.c (c_type_print_args): Remove java reference.
	* defs.h (enum language) <language_java>: Remove.
	* Makefile.in (SFILES, HFILES_NO_SRCDIR, COMMON_OBS, YYFILES)
	(YYOBJ, local-maintainer-clean): Don't mention java files.
	* jv-exp.y, jv-lang.c, jv-lang.h, jv-typeprint.c, jv-valprint.c,
	jv-varobj.c: Remove.

2016-10-06  Tom Tromey  <tom@tromey.com>

	* guile.texi (Types In Guile): Remove Java mentions.
	* python.texi (Types In Python): Remove Java mentions.
	* gdb.texinfo (Address Locations, Supported Languages)
	(Index Section Format): Remove Java mentions.

2016-10-06  Tom Tromey  <tom@tromey.com>

	* gdb.compile/compile.exp: Change java tests to rust.
	* gdb.base/setshow.exp: Change java tests to rust.
	* gdb.base/default.exp: Remove java from language list.
	* README (Examples): Update language example.
	* gdb.python/py-lookup-type.exp (test_lookup_type): Remove java
	test.
	* lib/gdb.exp (skip_java_tests): Remove.
	* lib/java.exp: Remove.
	* gdb.java: Remove.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] mips-tdep: Make FCRs always 32-bit
@ 2016-10-06 17:57 sergiodj+buildbot
  2016-10-06 20:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] -Wimplicit-fallthrough error fixes
@ 2016-10-06  0:52 sergiodj+buildbot
  2016-10-06  5:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Don't use boolean OR in arithmetic expressions
@ 2016-10-06  0:04 sergiodj+buildbot
  2016-10-06  4:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PR remote/20655 - small fix in handle_tracepoint_bkpts
@ 2016-10-05 19:49 sergiodj+buildbot
  2016-10-05 21:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Allow DW_OP_GNU_uninit in dwarf_expr_require_composition
@ 2016-10-05 13:07 sergiodj+buildbot
  2016-10-05 16:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-10-05 13:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f206f69cb43e420f92a63464036b342386963261 ***

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

Allow DW_OP_GNU_uninit in dwarf_expr_require_composition

In DWARF expression handling, some operators are required to be either
at the end of an expression or followed by a composition operator.  So
far only the operators DW_OP_reg0-31 were allowed to be followed by
DW_OP_GNU_uninit instead, and particularly DW_OP_regx was not, which is
obviously inconsistent.

This patch allows DW_OP_GNU_uninit after all operators requiring a
composition, to simplify the code and make it more consistent.  This
policy may be more permissive than necessary, but in the worst case just
leads to a DWARF location description resulting in an uninitialized
value instead of an error message.

gdb/ChangeLog:

	* dwarf2expr.c (dwarf_expr_require_composition): Allow
	DW_OP_GNU_uninit.
	(execute_stack_op): Use dwarf_expr_require_composition instead of
	copying its logic.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Regenerate some regformats/rs6000/*.dat files
@ 2016-10-05  9:34 sergiodj+buildbot
  2016-10-05 13:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Clean up the XML files for ARM
@ 2016-10-05  8:44 sergiodj+buildbot
  2016-10-05  9:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] PR target/20553, fix opcode mask for SIMD multiply by element
@ 2016-09-30 17:36 sergiodj+buildbot
  2016-09-30 18:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-30 17:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 744ce3025e82a59c13642c57e38febd8ff531f9b ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 744ce3025e82a59c13642c57e38febd8ff531f9b

[AArch64] PR target/20553, fix opcode mask for SIMD multiply by element

opcode/
	PR target/20553
        * aarch64-tbl.h (fmla, fmls, fmul, fmulx): Fix opcode mask field.

gas/
        * testsuite/gas/aarch64/advsimd-fp16.s (indexed_elem): New high index
        testcases for H and S variants.  New low index testcases for D variant.
        * testsuite/gas/aarch64/advsimd-fp16.d: Update expected results.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove syntactic sugar
@ 2016-09-30 15:11 sergiodj+buildbot
  2016-09-30 16:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make bfd_error_handler_type like vprintf
@ 2016-09-30 14:26 sergiodj+buildbot
  2016-09-30 15:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-30 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52d45da3f275b5d1c8ef2e96a7760585c736133b ***

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

Make bfd_error_handler_type like vprintf

It was like printf, which means you can't use bfd_set_error_handler to
hook in a function to do something and then call the original handler.

The patch also deletes some unused functions and makes pointers local.

bfd/
	* bfd-in.h: Include stdarg.h.
	* bfd.c (bfd_error_handler_type): Make like vprintf.
	(_bfd_error_internal): Rename from _bfd_error_handler.  Make static.
	(error_handler_internal): New function, split out from..
	(_bfd_default_error_handler): ..here.  Rename to _bfd_error_handler.
	(bfd_set_error_handler): Update.
	(bfd_get_error_handler, bfd_get_assert_handler): Delete.
	(_bfd_assert_handler): Make static.
	* coffgen.c (null_error_handler): Update params.
	* elf-bfd.h (struct elf_backend_data <link_order_error_handler>):
	Don't use bfd_error_handler_type.
	* elf64-mmix.c (mmix_dump_bpo_gregs): Likewise.
	* elfxx-target.h (elf_backend_link_order_error_handler): Default
	to _bfd_error_handler.
	* libbfd-in.h (_bfd_default_error_handler): Don't declare.
	(bfd_assert_handler_type): Likewise.
	(_bfd_error_handler): Update.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
ld/
	* ldlang.c (ignore_bfd_errors): Update params.


^ permalink raw reply	[flat|nested] 1903+ 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 13:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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-30  9:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Disallow 3-operand cmp[l][i] for ppc64
@ 2016-09-29 17:39 sergiodj+buildbot
  2016-09-29 19:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-29 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a5721ba270ddf860e0e5a45bba456214e8eac2be ***

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

Disallow 3-operand cmp[l][i] for ppc64

cmp[l][o] get an optional L field only when generating 32-bit code.
dcbf, tlbie and tlbiel keep their optional L field, ditto for R field
of tbegin.  cmprb, tsr., wlcr[all] and mtsle all change to a
compulsory L field.

L field of dcbf and wclr is 2 bits.

	PR 20641
include/
	* opcode/ppc.h (PPC_OPERAND_OPTIONAL32): Define.
opcodes/
	* ppc-opc.c (L): Make compulsory.
	(LOPT): New, optional form of L.
	(HTM_R): Define as LOPT.
	(L0, L1): Delete.
	(L32OPT): New, optional for 32-bit L.
	(L2OPT): New, 2-bit L for dcbf.
	(SVC_LEC): Update.
	(L2): Define.
	(insert_l0, extract_l0, insert_l1, extract_l2): Delete.
	(powerpc_opcodes <cmpli, cmpi, cmpl, cmp>): Use L32OPT.
	<dcbf>: Use L2OPT.
	<tlbiel, tlbie>: Use LOPT.
	<wclr, wclrall>: Use L2.
gas/
	* config/tc-ppc.c (md_assemble): Handle PPC_OPERAND_OPTIONAL32.
	* testsuite/gas/ppc/power8.s: Provide tbegin. operand.
	* testsuite/gas/ppc/power9.d: Update cmprb disassembly.


^ permalink raw reply	[flat|nested] 1903+ 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 16:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  2:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add archives and make stamps to the .gitignore file.
@ 2016-09-28 12:00 sergiodj+buildbot
  2016-09-28 22:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 11:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 15:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] When building target binaries, ensure that the warning flags selected for the command line match the target compiler.
@ 2016-09-27  2:10 sergiodj+buildbot
  2016-09-27  3:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-27  2:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5da193232ea0452f714dffee0d417d965590476 ***

Author: Vlad Zakharov <vzakhar@synopsys.com>
Branch: master
Commit: c5da193232ea0452f714dffee0d417d965590476

When building target binaries, ensure that the warning flags selected for the command line match the target compiler.

bfd	* warning.m4 (AC_EGREP_CPP_FOR_BUILD): Introduce macro
	to verify CC_FOR_BUILD compiler.
	(AM_BINUTILS_WARNINGS): Introduce ac_cpp_for_build variable
	and add CC_FOR_BUILD compiler checks.
	* Makefile.in: Regenerate.
	* configure: Likewise.
	* doc/Makefile.in: Likewise.

binutils	* Makefile.am: Replace AM_CLFAGS with AM_CFLAGS_FOR_BUILD
	when building with CC_FOR_BUILD compiler.
	* Makefile.in: Regenerate.
	* configure: Likewise.
	* doc/Makefile.in: Likewise.

gas	* Makefile.in: Regenerate.
	* configure: Likewise.
	* doc/Makefile.in: Likewise.

gold	* Makefile.in: Regenerate.
	* configure: Likewise.
	* testsuite/Makefile.in: Likewise.

gprof	* Makefile.in: Regenerate.
	* configure: Likewise.

ld	* Makefile.in: Regenerate.
	* configure: Likewise.

opcodes	* Makefile.in: Regenerate.
	* configure: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix the calculation of AMD64_PCRQUAD relocations.
@ 2016-09-26 22:57 sergiodj+buildbot
  2016-09-27  2:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] ISA alignment.
@ 2016-09-26 19:24 sergiodj+buildbot
  2016-09-27  1:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PowerPC .gnu.attributes
@ 2016-09-26 16:58 sergiodj+buildbot
  2016-09-26 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Call debug_exit in linux_wait_1
@ 2016-09-26 11:09 sergiodj+buildbot
  2016-09-26 16:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  9:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use std::string rather than dyn-string
@ 2016-09-24  7:30 sergiodj+buildbot
  2016-09-24 21:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use std::vector in objfiles.c
@ 2016-09-24  4:16 sergiodj+buildbot
  2016-09-24 19:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use std::string, std::vector in rust-lang.c
@ 2016-09-24  2:55 sergiodj+buildbot
  2016-09-24 15:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: Replace operator new / operator new[]
@ 2016-09-23 20:08 sergiodj+buildbot
  2016-09-24  8:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Delete relocations associatesd with deleted exidx entries.
@ 2016-09-23 19:06 sergiodj+buildbot
  2016-09-24  5:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Close gdbserver in mi_gdb_exit
@ 2016-09-23  0:46 sergiodj+buildbot
  2016-09-24  1:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix build breakage from commit 6ec2b2
@ 2016-09-22 23:04 sergiodj+buildbot
  2016-09-23 23:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use gdbserver-base in remote-gdbserver-on-localhost.exp
@ 2016-09-22 21:20 sergiodj+buildbot
  2016-09-23 21:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 21:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90681dabc79316d382aae5e932303f61bd705b16 ***

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

Use gdbserver-base in remote-gdbserver-on-localhost.exp

This patch is to make remote-gdbserver-on-localhost.exp use gdbserver-base
and remove duplicated code.

gdb/testsuite:

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

	* boards/gdbserver-base.exp (gdb_server_prog): Set the absolute
	path.
	* boards/remote-gdbserver-on-localhost.exp: Use gdbserver-base.
	Remove duplication.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] arc: Fix ARI warning for printf(%p)
@ 2016-09-22 20:53 sergiodj+buildbot
  2016-09-23 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 20:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa42dd2e8328560e65c888277ab146810c1763a8 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: fa42dd2e8328560e65c888277ab146810c1763a8

arc: Fix ARI warning for printf(%p)

Replace printf ("%p") with printf ("%s", host_address_to_string ()). Printing
host addrss might make sense here because pointers can be null and this would
affect how function behaves.

This particular warning is printed only when option -Wari is passed to
contrib/ari/gdb_ari.sh

gdb/ChangeLog:

	* arc-tdep.c: Fix ARI warning for printf(%p).


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Check the right proc name
@ 2016-09-22 19:54 sergiodj+buildbot
  2016-09-23 18:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 19:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c211fd8d6c7a600a7e55f272e21a967377a7c87 ***

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

Check the right proc name

In lib/gdbserver-support.exp, we rename gdb_exit to
gdbserver_orig_gdb_exit, but we check the existence gdbserver_gdb_exit.
We should check gdbserver_orig_gdb_exit instead.  Looks it is a typo
or an oversight.

gdb/testsuite:

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

	* lib/gdbserver-support.exp: Check the existence of
	gdbserver_orig_gdb_exit rather than gdbserver_gdb_exit.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add myself as a write-after-approval GDB maintainer
@ 2016-09-22 17:56 sergiodj+buildbot
  2016-09-23 18:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31da3f27d765612d3f067467ad39e386da7bacd7 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: 31da3f27d765612d3f067467ad39e386da7bacd7

Add myself as a write-after-approval GDB maintainer

gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add Anton Kolesov.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] arc: New Synopsys ARC port
@ 2016-09-22 17:43 sergiodj+buildbot
  2016-09-23 17:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 17:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad0a504f7e10ea11dbf58eb9990a5180f781b695 ***

Author: Anton Kolesov <Anton.Kolesov@synopsys.com>
Branch: master
Commit: ad0a504f7e10ea11dbf58eb9990a5180f781b695

arc: New Synopsys ARC port

ARC is a family of licensable processors developed by Synopsys.

This is an initial patch that doesn't yet support some of the features, that
are already available in Synopsys' fork of GDB, namely:

  * longjmp support
  * signal frame handling
  * prologue analysis
  * Linux targets support
  * native Linux support

ARC cores are configurable and extensible, which means from debugger
perspective that some registers and debug capabilities are optional, therefore
it is up to the GDB stub to determine exact list of register available on
target and supply it to GDB via XML target descriptions.  List of registers
that is known to GDB and is required is intentionally kept small to simplify
requirements to GDB stub and implementation of a GDB client.

gdb/ChangeLog:

	* Makefile.in (ALL_TARGET_OBS): Add arc-tdep.o.
	(HFILES_NO_SRCDIR): Add arc-tdep.h.
	(ALLDEPFILES): Add arc-tdep.c.
	* NEWS: Mention new ARC port.
	* configure.tgt: Add ARC.
	* arc-tdep.c: New file.
	* arc-tdep.h: New file.
	* features/Makefile (XMLTOC): Add arc-v2.xml and arc-arcompact.xml.
	* features/arc-v2.xml: New file.
	* features/arc-v2.c: New file (generated).
	* features/arc-arcompact.xml: New file.
	* features/arc-arcompact.c: New file (generated).

gdb/doc/ChangeLog:

	* gdb.texinfo (Embedded Processors): Document ARC.
	(Synopsys ARC): New section.
	(Standard Target Features): Document ARC features.
	(ARC Features): New section.

gdb/testsuite/ChangeLog:

	* gdb.xml/tdesc-regs.exp: set core-regs for arc*-*-elf32.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ppc: Fix return of instruction handlers in ppc_process_record_op63
@ 2016-09-22 16:46 sergiodj+buildbot
  2016-09-23 17:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8aabe2e254e6a0419db9c6397c4068c69bfd95b0 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: 8aabe2e254e6a0419db9c6397c4068c69bfd95b0

ppc: Fix return of instruction handlers in ppc_process_record_op63

some instruction handlers in ppc_process_record_op63() seem to be missing
return or incorrectly using break. This patch aims to fix that.

gdb/ChangeLog:
2016-09-21  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (ppc_process_record_op63): Fix return of instruction
	handlers.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR gdb/20604 - fix "quit" when an invalid expression is used
@ 2016-09-22 14:56 sergiodj+buildbot
  2016-09-23 16:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36cf1806a87fdd208c704d0768af232ce35aae9f ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 36cf1806a87fdd208c704d0768af232ce35aae9f

PR gdb/20604 - fix "quit" when an invalid expression is used

This fixes PR gdb/20604.  The bug here is that passing an invalid
expression to "quit" -- e.g., "quit()" -- causes gdb to enter a
non-functioning state.

The immediate problem is that quit_force resets the terminal before
evaluating the expression.  However, it seemed to me that it doesn't
really make sense to pass the quit_force argument to kill_or_detach
(which passes it to to_detach), first because conflating the exit
status for "quit" and the signal to pass when detaching doesn't make
sense, and second because to_detach implementations generally only
accept a constant here, while "quit" accepts an expression.  So, I
removed that.

As an aside, I think the "detach SIGNO" functionality is not
documented.

Built and regtested on x86-64 Fedora 24.

2016-09-21  Tom Tromey  <tom@tromey.com>

	PR gdb/20604:
	* top.h (quit_force): Update.
	* top.c (quit_force): Changed type of first argument.  Don't
	evaluate expression.  Pass NULL to kill_or_detach.
	* cli/cli-cmds.c (quit_command): Evaluate "args".

2016-09-21  Tom Tromey  <tom@tromey.com>

	PR gdb/20604:
	* gdb.base/quit.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Update and add .gitignore's
@ 2016-09-22 14:12 sergiodj+buildbot
  2016-09-23 16:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74172ecf37e5877085c5d01f335db94e8091ba97 ***

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

Update and add .gitignore's

This patch adds a bunch of generated files to gdb's gitignore files.
There are still a bunch of "stamp" files that are not ignored, but I
think the rule for them should be put in the top-level gitignore.

Users and developers are encouraged to build out-of-tree, but some
people prefer the simplicity to build in-tree, so it should be useful
for them.

gdb/ChangeLog:

	* .gitignore: Ignore more files.
	* data-directory/.gitignore: Likewise.

gdb/doc/ChangeLog:

	* .gitignore: New file.

gdb/gdbserver/ChangeLog:

	* .gitinore: Ignore more files.

gdb/testsuite/ChangeLog:

	* .gitignore: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ppc: Add Power ISA 3.0/POWER9 instructions record support
@ 2016-09-22 13:27 sergiodj+buildbot
  2016-09-23 11:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 13:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ec2b213de6962ceeb81bfa33354ea6e60c57049 ***

Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Branch: master
Commit: 6ec2b213de6962ceeb81bfa33354ea6e60c57049

ppc: Add Power ISA 3.0/POWER9 instructions record support

gdb/ChangeLog:
2016-09-21  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

	* rs6000-tdep.c (PPC_DQ): New macro.
	(ppc_process_record_op4): Add Power ISA 3.0 instructions.
	(ppc_process_record_op19): Likewise.
	(ppc_process_record_op31): Likewise.
	(ppc_process_record_op59): Likewise.
	(ppc_process_record_op60): Likewise.
	(ppc_process_record_op63): Likewise.
	(ppc_process_record): Likewise.
	(ppc_process_record_op61): New function.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Print spaces after commas in addresses
@ 2016-09-22 12:46 sergiodj+buildbot
  2016-09-23  8:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] Add SVE condition codes
@ 2016-09-22 11:51 sergiodj+buildbot
  2016-09-23  6:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 31/32] Add SVE instructions
@ 2016-09-22 10:26 sergiodj+buildbot
  2016-09-23  4:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0890d26289c4dad0e2ddedb7822a32a0645d150 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: c0890d26289c4dad0e2ddedb7822a32a0645d150

[AArch64][SVE 31/32] Add SVE instructions

This patch adds the SVE instruction definitions and associated OP_*
enum values.

include/
	* opcode/aarch64.h (AARCH64_FEATURE_SVE): New macro.
	(OP_MOV_P_P, OP_MOV_Z_P_Z, OP_MOV_Z_V, OP_MOV_Z_Z, OP_MOV_Z_Zi)
	(OP_MOVM_P_P_P, OP_MOVS_P_P, OP_MOVZS_P_P_P, OP_MOVZ_P_P_P)
	(OP_NOTS_P_P_P_Z, OP_NOT_P_P_P_Z): New aarch64_ops.

opcodes/
	* aarch64-tbl.h (OP_SVE_B, OP_SVE_BB, OP_SVE_BBBU, OP_SVE_BMB)
	(OP_SVE_BPB, OP_SVE_BUB, OP_SVE_BUBB, OP_SVE_BUU, OP_SVE_BZ)
	(OP_SVE_BZB, OP_SVE_BZBB, OP_SVE_BZU, OP_SVE_DD, OP_SVE_DDD)
	(OP_SVE_DMD, OP_SVE_DMH, OP_SVE_DMS, OP_SVE_DU, OP_SVE_DUD, OP_SVE_DUU)
	(OP_SVE_DUV_BHS, OP_SVE_DUV_BHSD, OP_SVE_DZD, OP_SVE_DZU, OP_SVE_HB)
	(OP_SVE_HMD, OP_SVE_HMS, OP_SVE_HU, OP_SVE_HUU, OP_SVE_HZU, OP_SVE_RR)
	(OP_SVE_RURV_BHSD, OP_SVE_RUV_BHSD, OP_SVE_SMD, OP_SVE_SMH, OP_SVE_SMS)
	(OP_SVE_SU, OP_SVE_SUS, OP_SVE_SUU, OP_SVE_SZS, OP_SVE_SZU, OP_SVE_UB)
	(OP_SVE_UUD, OP_SVE_UUS, OP_SVE_VMR_BHSD, OP_SVE_VMU_SD)
	(OP_SVE_VMVD_BHS, OP_SVE_VMVU_BHSD, OP_SVE_VMVU_SD, OP_SVE_VMVV_BHSD)
	(OP_SVE_VMVV_SD, OP_SVE_VMV_BHSD, OP_SVE_VMV_HSD, OP_SVE_VMV_SD)
	(OP_SVE_VM_SD, OP_SVE_VPU_BHSD, OP_SVE_VPV_BHSD, OP_SVE_VRR_BHSD)
	(OP_SVE_VRU_BHSD, OP_SVE_VR_BHSD, OP_SVE_VUR_BHSD, OP_SVE_VUU_BHSD)
	(OP_SVE_VUVV_BHSD, OP_SVE_VUVV_SD, OP_SVE_VUV_BHSD, OP_SVE_VUV_SD)
	(OP_SVE_VU_BHSD, OP_SVE_VU_HSD, OP_SVE_VU_SD, OP_SVE_VVD_BHS)
	(OP_SVE_VVU_BHSD, OP_SVE_VVVU_SD, OP_SVE_VVV_BHSD, OP_SVE_VVV_SD)
	(OP_SVE_VV_BHSD, OP_SVE_VV_HSD_BHS, OP_SVE_VV_SD, OP_SVE_VWW_BHSD)
	(OP_SVE_VXX_BHSD, OP_SVE_VZVD_BHS, OP_SVE_VZVU_BHSD, OP_SVE_VZVV_BHSD)
	(OP_SVE_VZVV_SD, OP_SVE_VZV_SD, OP_SVE_V_SD, OP_SVE_WU, OP_SVE_WV_BHSD)
	(OP_SVE_XU, OP_SVE_XUV_BHSD, OP_SVE_XVW_BHSD, OP_SVE_XV_BHSD)
	(OP_SVE_XWU, OP_SVE_XXU): New macros.
	(aarch64_feature_sve): New variable.
	(SVE): New macro.
	(_SVE_INSN): Likewise.
	(aarch64_opcode_table): Add SVE instructions.
	* aarch64-opc.h (extract_fields): Declare.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.c (do_misc_encoding): Handle the new SVE aarch64_ops.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.c (extract_fields): Make global.
	(do_misc_decoding): Handle the new SVE aarch64_ops.
	* aarch64-dis-2.c: Regenerate.

gas/
	* doc/c-aarch64.texi: Document the "sve" feature.
	* config/tc-aarch64.c (REG_TYPE_R_Z_BHSDQ_VZP): New register type.
	(get_reg_expected_msg): Handle it.
	(parse_operands): When parsing operands of an SVE instruction,
	disallow immediates that match REG_TYPE_R_Z_BHSDQ_VZP.
	(aarch64_features): Add an entry for SVE.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 29/32] Add new SVE core & FP register operands
@ 2016-09-22  9:37 sergiodj+buildbot
  2016-09-22 23:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  9:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 047cd301d40288d13e44f3322541ac28ebe06078 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 047cd301d40288d13e44f3322541ac28ebe06078

[AArch64][SVE 29/32] Add new SVE core & FP register operands

SVE uses some new fields to store W, X and scalar FP registers.
This patch adds corresponding operands.

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_Rm): New aarch64_opnd.
	(AARCH64_OPND_SVE_Rn_SP, AARCH64_OPND_SVE_VZn, AARCH64_OPND_SVE_Vd)
	(AARCH64_OPND_SVE_Vm, AARCH64_OPND_SVE_Vn): Likewise.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for the new SVE core
	and FP register operands.
	* aarch64-opc.h (FLD_SVE_Rm, FLD_SVE_Rn, FLD_SVE_Vd, FLD_SVE_Vm)
	(FLD_SVE_Vn): New aarch64_field_kinds.
	* aarch64-opc.c (fields): Add corresponding entries.
	(aarch64_print_operand): Handle the new SVE core and FP register
	operands.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm-2.c: Likewise.
	* aarch64-dis-2.c: Likewise.

gas/
	* config/tc-aarch64.c (parse_operands): Handle the new SVE core
	and FP register operands.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 30/32] Add SVE instruction classes
@ 2016-09-22  9:31 sergiodj+buildbot
  2016-09-23  2:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 28/32] Add SVE FP immediate operands
@ 2016-09-22  8:08 sergiodj+buildbot
  2016-09-22 20:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 18:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 25/32] Add support for SVE addressing modes
@ 2016-09-22  6:53 sergiodj+buildbot
  2016-09-22 17:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-22  6:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4df068de5214ff55b01ae320ec580f2928eb74e5 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: 4df068de5214ff55b01ae320ec580f2928eb74e5

[AArch64][SVE 25/32] Add support for SVE addressing modes

This patch adds most of the new SVE addressing modes and associated
operands.  A follow-on patch adds MUL VL, since handling it separately
makes the changes easier to read.

The patch also introduces a new "operand-dependent data" field to the
operand flags, based closely on the existing one for opcode flags.
For SVE this new field needs only 2 bits, but it could be widened
in future if necessary.

include/
	* opcode/aarch64.h (AARCH64_OPND_SVE_ADDR_RI_U6): New aarch64_opnd.
	(AARCH64_OPND_SVE_ADDR_RI_U6x2, AARCH64_OPND_SVE_ADDR_RI_U6x4)
	(AARCH64_OPND_SVE_ADDR_RI_U6x8, AARCH64_OPND_SVE_ADDR_RR)
	(AARCH64_OPND_SVE_ADDR_RR_LSL1, AARCH64_OPND_SVE_ADDR_RR_LSL2)
	(AARCH64_OPND_SVE_ADDR_RR_LSL3, AARCH64_OPND_SVE_ADDR_RX)
	(AARCH64_OPND_SVE_ADDR_RX_LSL1, AARCH64_OPND_SVE_ADDR_RX_LSL2)
	(AARCH64_OPND_SVE_ADDR_RX_LSL3, AARCH64_OPND_SVE_ADDR_RZ)
	(AARCH64_OPND_SVE_ADDR_RZ_LSL1, AARCH64_OPND_SVE_ADDR_RZ_LSL2)
	(AARCH64_OPND_SVE_ADDR_RZ_LSL3, AARCH64_OPND_SVE_ADDR_RZ_XTW_14)
	(AARCH64_OPND_SVE_ADDR_RZ_XTW_22, AARCH64_OPND_SVE_ADDR_RZ_XTW1_14)
	(AARCH64_OPND_SVE_ADDR_RZ_XTW1_22, AARCH64_OPND_SVE_ADDR_RZ_XTW2_14)
	(AARCH64_OPND_SVE_ADDR_RZ_XTW2_22, AARCH64_OPND_SVE_ADDR_RZ_XTW3_14)
	(AARCH64_OPND_SVE_ADDR_RZ_XTW3_22, AARCH64_OPND_SVE_ADDR_ZI_U5)
	(AARCH64_OPND_SVE_ADDR_ZI_U5x2, AARCH64_OPND_SVE_ADDR_ZI_U5x4)
	(AARCH64_OPND_SVE_ADDR_ZI_U5x8, AARCH64_OPND_SVE_ADDR_ZZ_LSL)
	(AARCH64_OPND_SVE_ADDR_ZZ_SXTW, AARCH64_OPND_SVE_ADDR_ZZ_UXTW):
	Likewise.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERANDS): Add entries for the new SVE
	address operands.
	* aarch64-opc.h (FLD_SVE_imm6, FLD_SVE_msz, FLD_SVE_xs_14)
	(FLD_SVE_xs_22): New aarch64_field_kinds.
	(OPD_F_OD_MASK, OPD_F_OD_LSB, OPD_F_NO_ZR): New flags.
	(get_operand_specific_data): New function.
	* aarch64-opc.c (fields): Add entries for FLD_SVE_imm6, FLD_SVE_msz,
	FLD_SVE_xs_14 and FLD_SVE_xs_22.
	(operand_general_constraint_met_p): Handle the new SVE address
	operands.
	(sve_reg): New array.
	(get_addr_sve_reg_name): New function.
	(aarch64_print_operand): Handle the new SVE address operands.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-asm.h (ins_sve_addr_ri_u6, ins_sve_addr_rr_lsl)
	(ins_sve_addr_rz_xtw, ins_sve_addr_zi_u5, ins_sve_addr_zz_lsl)
	(ins_sve_addr_zz_sxtw, ins_sve_addr_zz_uxtw): New inserters.
	* aarch64-asm.c (aarch64_ins_sve_addr_ri_u6): New function.
	(aarch64_ins_sve_addr_rr_lsl): Likewise.
	(aarch64_ins_sve_addr_rz_xtw): Likewise.
	(aarch64_ins_sve_addr_zi_u5): Likewise.
	(aarch64_ins_sve_addr_zz): Likewise.
	(aarch64_ins_sve_addr_zz_lsl): Likewise.
	(aarch64_ins_sve_addr_zz_sxtw): Likewise.
	(aarch64_ins_sve_addr_zz_uxtw): Likewise.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_sve_addr_ri_u6, ext_sve_addr_rr_lsl)
	(ext_sve_addr_rz_xtw, ext_sve_addr_zi_u5, ext_sve_addr_zz_lsl)
	(ext_sve_addr_zz_sxtw, ext_sve_addr_zz_uxtw): New extractors.
	* aarch64-dis.c (aarch64_ext_sve_add_reg_imm): New function.
	(aarch64_ext_sve_addr_ri_u6): Likewise.
	(aarch64_ext_sve_addr_rr_lsl): Likewise.
	(aarch64_ext_sve_addr_rz_xtw): Likewise.
	(aarch64_ext_sve_addr_zi_u5): Likewise.
	(aarch64_ext_sve_addr_zz): Likewise.
	(aarch64_ext_sve_addr_zz_lsl): Likewise.
	(aarch64_ext_sve_addr_zz_sxtw): Likewise.
	(aarch64_ext_sve_addr_zz_uxtw): Likewise.
	* aarch64-dis-2.c: Regenerate.

gas/
	* config/tc-aarch64.c (REG_TYPE_SVE_BASE, REG_TYPE_SVE_OFFSET): New
	register types.
	(get_reg_expected_msg): Handle them.
	(aarch64_addr_reg_parse): New function, split out from
	aarch64_reg_parse_32_64.  Handle Z registers too.
	(aarch64_reg_parse_32_64): Call it.
	(parse_address_main): Add base_qualifier, offset_qualifier,
	base_type and offset_type parameters.  Handle SVE base and offset
	registers.
	(parse_address): Update call to parse_address_main.
	(parse_sve_address): New function.
	(parse_operands): Parse the new SVE address operands.


^ permalink raw reply	[flat|nested] 1903+ 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 14:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 11:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 19/32] Refactor address-printing code
@ 2016-09-22  1:25 sergiodj+buildbot
  2016-09-22  7:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  6:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  5:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 16/32] Use specific insert/extract methods for fpimm
@ 2016-09-21 23:35 sergiodj+buildbot
  2016-09-22  3:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-21 23:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa2aa4c69429444836821a92cb99396d02dcb996 ***

Author: Richard Sandiford <richard.sandiford@arm.com>
Branch: master
Commit: aa2aa4c69429444836821a92cb99396d02dcb996

[AArch64][SVE 16/32] Use specific insert/extract methods for fpimm

FPIMM used the normal "imm" insert/extract methods, with a specific
test for FPIMM in the extract method.  SVE needs to use the same
extractors, so rather than add extra checks for specific operand types,
it seemed cleaner to use a separate insert/extract method.

opcodes/
	* aarch64-tbl.h (AARCH64_OPERNADS): Use fpimm rather than imm
	for FPIMM.
	* aarch64-asm.h (ins_fpimm): New inserter.
	* aarch64-asm.c (aarch64_ins_fpimm): New function.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis.h (ext_fpimm): New extractor.
	* aarch64-dis.c (aarch64_ext_imm): Remove fpimm test.
	(aarch64_ext_fpimm): New function.
	* aarch64-dis-2.c: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ 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  1:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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-22  0:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64][SVE 13/32] Add an F_STRICT flag
@ 2016-09-21 20:22 sergiodj+buildbot
  2016-09-21 22:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] MIPS/testsuite: mips16-thunks: Use `standard_output_file'
@ 2016-09-21 17:21 sergiodj+buildbot
  2016-09-21 19:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Keep reserved bits in CPSR on write
@ 2016-09-21 15:44 sergiodj+buildbot
  2016-09-21 17:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Avoid -Wduplicated-cond warnings in gdb/python
@ 2016-09-20 21:40 sergiodj+buildbot
  2016-09-21 13:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-20 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12c58cd4dc805cbac97a6d93c971c2496313dce4 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 12c58cd4dc805cbac97a6d93c971c2496313dce4

Avoid -Wduplicated-cond warnings in gdb/python

I tried building gdb with -Wduplicated-cond.  This patch fixes the
simpler issue that was found.

In Python 3, "int" and "long" are synonyms, so code like:

      else if (PyLong_Check (obj))
...
      else if (PyInt_Check (obj))

.... will trigger this warning.  The fix is to conditionalize the
PyInt_Check branches on Python 2.

Tested by rebuilding, with both version of Python, on x86-64 Fedora 24.

2016-09-20  Tom Tromey  <tom@tromey.com>

	* python/py-value.c (convert_value_from_python): Make PyInt_Check
	conditional on Python 2.
	* python/py-arch.c (archpy_disassemble): Make PyInt_Check
	conditional on Python 2.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ppc: Fix record support of Store String Word instructions
@ 2016-09-20 20:52 sergiodj+buildbot
  2016-09-20 22:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 19:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 12:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC
@ 2016-09-19 23:22 sergiodj+buildbot
  2016-09-20  5:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-19 23:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b19753ce31da347605dfa903c6fd2158e2444f0d ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: b19753ce31da347605dfa903c6fd2158e2444f0d

bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC

The code compiled with the -fpic model in SPARC uses 13-bit signed
immediate PC-relative loads to fetch entries from the GOT table.  In
theory this would allow using a GOT table (.got section) containing up
to 1024 entries in elf32 or 512 entries in elf64.

However, in elf64 sparc GNU targets _GLOBAL_OFFSET_TABLE_ is always
placed at the beginning of the .got section, making it impossible to use
negative offsets.  This limits the usage of -fpic to GOT tables
containing a maximum of 257 entries in elf64.

This patch activates an optimization that is already used in sparc-elf32
also in sparc-elf64, that sets _GLOBAL_OFFSET_TABLE_ to point 0x1000
into the .got section if the section size is bigger than 0x1000.

2016-09-19  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* elfxx-sparc.c (_bfd_sparc_elf_size_dynamic_sections): Allow
	negative offsets to _GLOBAL_OFFSET_TABLE_ if the .got section is
	bigger than 0x1000 bytes.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver
@ 2016-09-19 16:45 sergiodj+buildbot
  2016-09-19 22:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 16:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Improve MinGW support in Readline
@ 2016-09-18 23:24 sergiodj+buildbot
  2016-09-19  5:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-18 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f3c5ec870943f7f32c946ff9459dfd04fcb8e07 ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 7f3c5ec870943f7f32c946ff9459dfd04fcb8e07

Improve MinGW support in Readline

These changes were already accepted upstream in Readline,
but GDB did not yet import a newer Readline version.

readline/Changelog.gdb:

	* util.c: Include rlshell.h.
	(_rl_tropen) [_WIN32 && !__CYGWIN__]: Open the trace file in the
	user's temporary directory.
	* tcap.h [HAVE_NCURSES_TERMCAP_H]: Include ncurses/termcap.h.
	* input.c (w32_isatty) [_WIN32 && !__CYGWIN__]: New function, to
	replace isatty that is not reliable enough on MS-Windows.
	(isatty) [_WIN32 && !__CYGWIN__]: Redirect to w32_isatty.
	(rl_getc): Call _getch, not getch, which could be an ncurses
	function when linked with ncurses, in which case getch will return
	EOF for any keystroke, because there's no curses window.
	* tilde.c (tilde_expand_word) [_WIN32]:
	* histfile.c (history_filename) [_WIN32]: Windows-specific
	environment variable to replace HOME if that is undefined.
	* funmap.c (default_funmap): Compile rl_paste_from_clipboard on
	all Windows platforms, not just Cygwin.
	* readline.h (rl_paste_from_clipboard): Include declaration for
	all Windows platforms.
	* display.c (insert_some_chars, delete_chars): Don't use the
	MinGW-specific code if linked with ncurses.
	* configure.in:
	* config.h.in: Support ncurses/termcap.h.  The configure script
	was updated accordingly.
	* complete.c [_WIN32 && !__CYGWIN__]: Initialize
	_rl_completion_case_fold to 1.
	(printable_part, rl_filename_completion_function)
	[_WIN32 && !__CYGWIN__]: Handle the drive letter.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Introduce cleanup to restore current_uiout
@ 2016-09-17  5:15 sergiodj+buildbot
  2016-09-19  4:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-17  5:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd94f6d535d1ebd8f252185cd84d21fe0df3c893 ***

Author: Simon Marchi <simark@simark.ca>
Branch: master
Commit: cd94f6d535d1ebd8f252185cd84d21fe0df3c893

Introduce cleanup to restore current_uiout

Make a globally available cleanup from a pre-existing one in infrun.c.
This is used in a following patch.

gdb/ChangeLog:

	* infrun.c (restore_current_uiout_cleanup): Move to ui-out.c.
	(print_stop_event): Use make_cleanup_restore_current_uiout.
	* python/python.c (execute_gdb_command): Likewise.
	* ui-out.c (restore_current_uiout_cleanup): Move from infrun.c.
	(make_cleanup_restore_current_uiout): New function definition.
	* ui-out.h (make_cleanup_restore_current_uiout): New function
	declaration.
	* utils.c (do_restore_ui_out): Remove.
	(make_cleanup_restore_ui_out): Remove.
	* utils.h (make_cleanup_restore_ui_out): Remove.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Use std::min and std::max throughout
@ 2016-09-17  3:34 sergiodj+buildbot
  2016-09-19  2:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-17  3:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 325fac504a327de9c46a4e5cf9c88ece9d9d7701 ***

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

gdb: Use std::min and std::max throughout

Otherwise including <string> or some other C++ header is broken.
E.g.:

  In file included from /opt/gcc/include/c++/7.0.0/bits/char_traits.h:39:0,
		   from /opt/gcc/include/c++/7.0.0/string:40,
		   from /home/pedro/gdb/mygit/cxx-convertion/src/gdb/infrun.c:68:
  /opt/gcc/include/c++/7.0.0/bits/stl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2
       min(const _Tp& __a, const _Tp& __b, _Compare __comp)
							  ^
  /opt/gcc/include/c++/7.0.0/bits/stl_algobase.h:265:56: error: macro "max" passed 3 arguments, but takes just 2
       max(const _Tp& __a, const _Tp& __b, _Compare __comp)
							  ^
  In file included from .../src/gdb/infrun.c:21:0:

To the best of my grepping abilities, I believe I adjusted all min/max
calls.

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

	* defs.h (min, max): Delete.
	* aarch64-tdep.c: Include <algorithm> and use std::min and
	std::max throughout.
	* aarch64-tdep.c: Likewise.
	* alpha-tdep.c: Likewise.
	* amd64-tdep.c: Likewise.
	* amd64-windows-tdep.c: Likewise.
	* arm-tdep.c: Likewise.
	* avr-tdep.c: Likewise.
	* breakpoint.c: Likewise.
	* btrace.c: Likewise.
	* ctf.c: Likewise.
	* disasm.c: Likewise.
	* doublest.c: Likewise.
	* dwarf2loc.c: Likewise.
	* dwarf2read.c: Likewise.
	* environ.c: Likewise.
	* exec.c: Likewise.
	* f-exp.y: Likewise.
	* findcmd.c: Likewise.
	* ft32-tdep.c: Likewise.
	* gcore.c: Likewise.
	* hppa-tdep.c: Likewise.
	* i386-darwin-tdep.c: Likewise.
	* i386-tdep.c: Likewise.
	* linux-thread-db.c: Likewise.
	* lm32-tdep.c: Likewise.
	* m32r-tdep.c: Likewise.
	* m88k-tdep.c: Likewise.
	* memrange.c: Likewise.
	* minidebug.c: Likewise.
	* mips-tdep.c: Likewise.
	* moxie-tdep.c: Likewise.
	* nds32-tdep.c: Likewise.
	* nios2-tdep.c: Likewise.
	* nto-procfs.c: Likewise.
	* parse.c: Likewise.
	* ppc-sysv-tdep.c: Likewise.
	* probe.c: Likewise.
	* record-btrace.c: Likewise.
	* remote.c: Likewise.
	* rs6000-tdep.c: Likewise.
	* rx-tdep.c: Likewise.
	* s390-linux-nat.c: Likewise.
	* s390-linux-tdep.c: Likewise.
	* ser-tcp.c: Likewise.
	* sh-tdep.c: Likewise.
	* sh64-tdep.c: Likewise.
	* source.c: Likewise.
	* sparc-tdep.c: Likewise.
	* symfile.c: Likewise.
	* target-memory.c: Likewise.
	* target.c: Likewise.
	* tic6x-tdep.c: Likewise.
	* tilegx-tdep.c: Likewise.
	* tracefile-tfile.c: Likewise.
	* tracepoint.c: Likewise.
	* valprint.c: Likewise.
	* value.c: Likewise.
	* xtensa-tdep.c: Likewise.
	* cli/cli-cmds.c: Likewise.
	* compile/compile-object-load.c: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Hardware breakpoint support
@ 2016-09-17  1:02 sergiodj+buildbot
  2016-09-19  1:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] linux-nat: Add function lwp_is_stepping
@ 2016-09-17  0:28 sergiodj+buildbot
  2016-09-19  0:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] S390: Enable "maint set show-debug-regs"
@ 2016-09-16 23:32 sergiodj+buildbot
  2016-09-17 15:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 23:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 169fe0df159c04cd7344d24cc6b1268bd219f830 ***

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

S390: Enable "maint set show-debug-regs"

Implement a new function for dumping the S390 "debug
registers" (actually, the PER info) and invoke it at appropriate places.
Respect the variable show_debug_regs and make it settable by the user.

gdb/ChangeLog:

	* s390-linux-nat.c (gdbcmd.h): New include.
	(s390_show_debug_regs): New function.
	(s390_stopped_by_watchpoint): Call it, if show_debug_regs is set.
	(s390_prepare_to_resume): Likewise.
	(_initialize_s390_nat): Register the command "maint set
	show-debug-regs".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Multi-inferior watchpoint support
@ 2016-09-16 23:12 sergiodj+buildbot
  2016-09-17  3:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] S390: Migrate watch areas from list to VEC type
@ 2016-09-16 22:36 sergiodj+buildbot
  2016-09-17  1:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] S390: Avoid direct access to lwp_info structure
@ 2016-09-16 21:38 sergiodj+buildbot
  2016-09-16 23:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 21:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c2996c98278a95593afaa79db0dc00bb2aff189 ***

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

S390: Avoid direct access to lwp_info structure

When using the lwp_info structure, avoid accessing its members directly,
and use the advertised function interfaces instead.  This is according
to the instructions in linux-nat.h and prepares for making some of the
code common between gdb and gdbserver.

gdb/ChangeLog:

	* s390-linux-nat.c (s390_prepare_to_resume): Use advertised lwp
	functions instead of accessing lwp_info structure members.
	(s390_mark_per_info_changed): New function.
	(s390_new_thread): Use it.
	(s390_refresh_per_info_cb): New function.
	(s390_refresh_per_info): Remove parameter.  Refresh all lwps of
	the current process.
	(s390_insert_watchpoint): Adjust call to s390_refresh_per_info.
	(s390_remove_watchpoint): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Fix false FAIL in gdb.cp/casts.exp
@ 2016-09-16 20:49 sergiodj+buildbot
  2016-09-16 22:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] Disassemble correctly extension instructions.
@ 2016-09-16 19:43 sergiodj+buildbot
  2016-09-16 20:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 19:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Update ISA 3.0 / POWER9 gdb tests to match GAS test cases.
@ 2016-09-16 14:17 sergiodj+buildbot
  2016-09-16 17:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-16 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2a92b16496f418e3c2c3b69eb5203b0b335df87 ***

Author: Peter Bergner <bergner@vnet.ibm.com>
Branch: master
Commit: e2a92b16496f418e3c2c3b69eb5203b0b335df87

Update ISA 3.0 / POWER9 gdb tests to match GAS test cases.

	* gdb.arch/powerpc-power.s: Update Power9 instruction tests
	and sync up the test with tests in gas/testsuite/gas/ppc.
	* gdb.arch/powerpc-power.exp: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Disable ccache
@ 2016-09-15 23:31 sergiodj+buildbot
  2016-09-16  2:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 13:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix seg-fault in objdump when run on a fuzzed PE binary.
@ 2016-09-15  3:38 sergiodj+buildbot
  2016-09-15  5:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-15  3:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6d042fe27102cb789407ccb2ec1663aa9c65129 ***

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

Fix seg-fault in objdump when run on a fuzzed PE binary.

	PR binutils/20605
	* peicode.h (pe_bfd_read_buildid): Check that the Data Directory
	contains a valid size for the Debug directory.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Prevent segfault in GDB when searching for architecture matches.
@ 2016-09-14 17:34 sergiodj+buildbot
  2016-09-14 21:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 15:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 14:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] S/390: Add alternate processor names.
@ 2016-09-13 18:36 sergiodj+buildbot
  2016-09-13 20:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 18:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use target_sim_options for sim target.
@ 2016-09-12 15:28 sergiodj+buildbot
  2016-09-12 16:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Pass HWCAP to ifunc resolver
@ 2016-09-10 23:25 sergiodj+buildbot
  2016-09-12  6:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove some unneeded casts from remote.c
@ 2016-09-10 20:57 sergiodj+buildbot
  2016-09-10 21:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] X86: Allow additional ISAs for IAMCU in assembler
@ 2016-09-08  0:06 sergiodj+buildbot
  2016-09-08 21:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-08  0:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b64d091e9ede49e402cb9697d35a40559ee7ff0 ***

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

X86: Allow additional ISAs for IAMCU in assembler

Originally only Pentium integer instructions are allowed for IAMCU.
This patch removes such a restriction.  For example, 387 and SSE2
instructions can be enabled by passing "-march=iamcu+sse2+387" to
assembler.

gas/

	* config/tc-i386.c (valid_iamcu_cpu_flags): Removed.
	(set_cpu_arch): Updated.
	(md_parse_option): Likewise.
	* testsuite/gas/i386/i386.exp: Run iamcu-4 and iamcu-5.  Remove
	iamcu-inval-2 and iamcu-inval-3.
	* testsuite/gas/i386/iamcu-4.d: New file.
	* testsuite/gas/i386/iamcu-4.s: Likewise.
	* testsuite/gas/i386/iamcu-5.d: Likewise.
	* testsuite/gas/i386/iamcu-5.s: Likewise.
	* testsuite/gas/i386/iamcu-inval-2.l: Removed.
	* testsuite/gas/i386/iamcu-inval-2.s: Likewise.
	* testsuite/gas/i386/iamcu-inval-3.l: Likewise.
	* testsuite/gas/i386/iamcu-inval-3.s: Likewise.

opcodes/

	* i386-gen.c (cpu_flag_init): Remove CPU_IAMCU_COMPAT_FLAGS.
	* i386-init.h: Regenerated.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [arm] Automatically enable CRC instructions on supported ARMv8-A CPUs.
@ 2016-09-07 21:00 sergiodj+buildbot
  2016-09-08  6:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 20:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Introduce make_cleanup_restore_current_ui
@ 2016-09-07  5:56 sergiodj+buildbot
  2016-09-07 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Resolve size relocation with copy relocation
@ 2016-09-07  1:30 sergiodj+buildbot
  2016-09-07 17:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 16:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add gdbarch callback to provide formats for debug info float types
@ 2016-09-07  0:07 sergiodj+buildbot
  2016-09-07 15:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-07  0:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9b790ce7227fa346d08a41462119e9a3e93f5e80 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 9b790ce7227fa346d08a41462119e9a3e93f5e80

Add gdbarch callback to provide formats for debug info float types

At this point, all TYPE_CODE_FLT types carry their floating-point format,
except for those creating from reading DWARF or stabs debug info.  Those
will be addressed by this commit.

The main issue here is that we actually have to determine which floating-
point format to use.  Currently, we only have the type length as input
to this decision.  In the future, we may hopefully get --at least in
DWARF-- additional information to help disambiguate multiple different
formats of the same length.  For now, we can still look at the type name
as a hint.

This decision logic is encapsulated in a gdbarch callback to allow
platform-specific overrides.  The default implementation use the same
logic (compare type length against the various gdbarch_..._bit sizes)
that is currently implemented in floatformat_from_length.

With this commit, all platforms still use the default logic, so there
should be no actual change in behavior.  A follow-on commit will add
support for __float128 on Intel and Power.

Once dwarf2read.c and stabsread.c make use of the new callback to
determine floating-point formats, we're now sure every TYPE_CODE_FLT
type will always carry its format.  The commit therefore adds asserts
to verify_floatformat to ensure new code will continue to always
provide formats, and removes the code in floatformat_from_type that
used to handle types with a NULL TYPE_FLOATFORMAT.

gdb/ChangeLog:

	* gdbarch.sh (floatformat_for_type): New gdbarch callback.
	* gdbarch.h, gdbarch.c: Re-generate.
	* arch-utils.h (default_floatformat_for_type): New prototype.
	* arch-utils.c (default_floatformat_for_type): New function.

	* doublest.c (floatformat_from_length): Remove.
	(floatformat_from_type): Assume TYPE_FLOATFORMAT is non-NULL.
	* gdbtypes.c (verify_floatformat): Require non-NULL format.

	* dwarf2read.c (dwarf2_init_float_type): New function.
	(read_base_type): Use it.
	* stabsread.c (dbx_init_float_type): New function.
	(read_sun_floating_type): Use it.
	(read_range_type): Likewise.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add missing format for built-in floating-point types
@ 2016-09-06 23:37 sergiodj+buildbot
  2016-09-07 11:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove TYPE_NOSIGN "char" hack
@ 2016-09-06 23:33 sergiodj+buildbot
  2016-09-07  1:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove obsolete TYPE_FLAG_... values
@ 2016-09-06 22:01 sergiodj+buildbot
  2016-09-07  0:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Unify init_type and arch_type interface and helpers
@ 2016-09-06 21:12 sergiodj+buildbot
  2016-09-06 23:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 19f392bc2a93d9e64d063b884cd6eca547c8dad0 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 19f392bc2a93d9e64d063b884cd6eca547c8dad0

Unify init_type and arch_type interface and helpers

This adds a number of helper routines for creating objfile-owned types;
these correspond 1:1 to the already existing helper routines for creating
gdbarch-owned types, and are intended to be used instead of init_type.
A shared fragment of init_float_type and arch_float_type is extracted into
a separate subroutine verify_subroutine.

The commit also brings the interface of init_type in line with the one for
arch_type.  In particular, this means removing the FLAGS argument; callers
now set the required flags directly.  (Since most callers use the new
helper routines, very few callers actually need to set any additional
flags directly any more.)

Note that this means all the TYPE_FLAGS_... defined are no longer needed
anywhere; they will be removed by a follow-on commit.

All users of init_type are changed to use on of the new helpers where
possible.  No functional change intended.

gdb/ChangeLog:

	* gdbtypes.h (init_type): Remove FLAGS argument.  Move OBJFILE
	argument to first position.
	(init_integer_type): New prototype.
	(init_character_type): Likewise.
	(init_boolean_type): Likewise.
	(init_float_type): Likewise.
	(init_decfloat_type): Likewise.
	(init_complex_type): Likewise.
	(init_pointer_type): Likewise.
	* gdbtypes.c (verify_floatflormat): New function.
	(init_type): Remove FLAGS argument and processing.  Move OBJFILE
	argument to first position.
	(init_integer_type): New function.
	(init_character_type): Likewise.
	(init_boolean_type): Likewise.
	(init_float_type): Likewise.
	(init_decfloat_type): Likewise.
	(init_complex_type): Likewise.
	(init_pointer_type): Likewise.
	(arch_float_type): Use verify_floatflormat.
	(objfile_type): Use init_..._type helpers instead of calling
	init_type directly.
	* dwarf2read.c (fixup_go_packaging): Update to changed init_type
	prototype.
	(read_namespace_type): Likewise.
	(read_module_type): Likewise.
	(read_typedef): Likewise.
	(read_unspecified_type): Likewise.
	(build_error_marker_type): Likewise.
	(read_base_type): Use init_..._type helpers.
	* mdebugread.c (basic_type): Use init_..._type helpers.
	(parse_type): Update to changed init_type prototype.
	(cross_ref): Likewise.
	* stabsread.c (rs6000_builtin_type): Use init_..._type helpers.
	(read_sun_builtin_type): Likewise.
	(read_sun_floating_type): Likewise.
	(read_range_type): Likewise.  Also update to changed init_type
	prototype.

Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add some missing arch_..._type helpers
@ 2016-09-06 20:46 sergiodj+buildbot
  2016-09-06 22:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 21:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix typo in ada_language_arch_info
@ 2016-09-06 18:54 sergiodj+buildbot
  2016-09-06 19:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix PR ld/20545 - relaxation bugs in avr backend
@ 2016-09-06 18:00 sergiodj+buildbot
  2016-09-06 18:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-09-06 18:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf1865065f64af2f32798c0327143baf99634e8d ***

Author: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com>
Branch: master
Commit: bf1865065f64af2f32798c0327143baf99634e8d

Fix PR ld/20545 - relaxation bugs in avr backend

Prior to the patch, addends for relocs were being adjusted even if
they went beyond an alignment boundary. This is wrong - to
preserve alignment constraints, the relaxation logic adds as many padding
bytes at the alignment boundary as was deleted, so addends beyond the
boundary should not be adjusted. avr-prop-7.s reproduces this
scenario.

Also, prior to this patch, the relaxation logic assumed that the addr
parameter pointed to the middle of the instruction to be deleted, and
that addr - count would therefore be the shrinked instruction's
address. This is true when actually shrinking instructions.

The alignment constraints handling logic also invokes the same logic
though, with addr as the starting offset of padding bytes and
with count as the number of bytes to be deleted. Calculating the
shrinked insn's address as addr - count is obviously wrong in this
case - that offset would point to count bytes before the last
non-padded byte. avr-prop-8.s reproduces this scenario.

To fix scenario 1, the patch adds an additional check to ensure reloc addends
aren't adjusted if they cross a shrink boundary. The shrink boundary
is either the section size or an alignment boundary. Addends pointing
at an alignment boundary don't need to be adjusted, as padding would
occur and keep the boundary the same. Addends pointing at section size
need to be adjusted though, as no padding occurs and the section size
itself would get decremented. The patch records whether padding
occured (did_pad) and uses that to detect and handle this condition.

To fix scenario 2, the patch adds an additional parameter
(delete_shrinks_insn) to elf32_avr_relax_delete_bytes to distinguish
instruction bytes deletion from padding bytes deletion. It then uses that to
correctly set shrinked_insn_address.

bfd/ChangeLog:

2016-09-02  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

	PR ld/20545
	* elf32-avr.c (elf32_avr_relax_delete_bytes): Add parameter
	delete_shrinks_insn. Modify computation of shrinked_insn_address.
	Compute shrink_boundary and adjust addend only if
	addend_within_shrink_boundary.
	(elf32_avr_relax_section): Modify calls to
	elf32_avr_relax_delete_bytes to pass extra parameter.

ld/ChangeLog:

2016-09-02  Senthil Kumar Selvaraj  <senthil_kumar.selvaraj@atmel.com>

	PR ld/20545
	* testsuite/ld-avr/avr-prop-7.d: New test.
	* testsuite/ld-avr/avr-prop-7.s: New test.
	* testsuite/ld-avr/avr-prop-8.d: New test.
	* testsuite/ld-avr/avr-prop-8.s: New test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb/: Require a C++ compiler
@ 2016-09-06 16:28 sergiodj+buildbot
  2016-09-06 17:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 15:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Removed redundant line remote-utils.c
@ 2016-09-05 19:41 sergiodj+buildbot
  2016-09-05 22:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Handle DW_OP_form_tls_address
@ 2016-09-03 12:46 sergiodj+buildbot
  2016-09-05 18:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [GDBserver] Replace "reinsert_breakpoint" with "single_step_breakpoint"
@ 2016-09-02 22:03 sergiodj+buildbot
  2016-09-03 12:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 20:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Detect broken ptrace in gdb_skip_float_test
@ 2016-09-02 17:12 sergiodj+buildbot
  2016-09-02 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Share target_wait prototype between GDB and gdbserver
@ 2016-09-02 14:53 sergiodj+buildbot
  2016-09-02 16:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use target_continue{, _no_signal} instead of target_resume
@ 2016-09-02  9:02 sergiodj+buildbot
  2016-09-02 11:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Don't treat .opd section specially when ELFv2
@ 2016-09-01 20:40 sergiodj+buildbot
  2016-09-01 21:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix a typo in comment
@ 2016-08-31 20:01 sergiodj+buildbot
  2016-08-31 22:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PowerPC64, correct grouping of stubs for ld.bfd
@ 2016-08-31 19:13 sergiodj+buildbot
  2016-08-31 19:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-31 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09f92717713cfc7595b29caa3f017f88e7f7e279 ***

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

PowerPC64, correct grouping of stubs for ld.bfd

Like 57f6d32d, this patch ensures that sections containing external
conditional branches limit the group size.

	* elf64-ppc.c (group_sections): Delete stub14_group_size.  Instead,
	track max group size with a new "group_size" var that is reduced
	by a factor of 1024 from the 24-bit branch size whenever a 14-bit
	branch is seen.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PowerPC VLE sh_flags and p_flags
@ 2016-08-31 18:21 sergiodj+buildbot
  2016-08-31 18:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] ppc apuinfo for spe parsed incorrectly
@ 2016-08-30 18:41 sergiodj+buildbot
  2016-08-30 19:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Lack of SHF_GROUP sections result in ld segfault
@ 2016-08-27 13:37 sergiodj+buildbot
  2016-08-29 14:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix commit 980aa3e6
@ 2016-08-27 12:09 sergiodj+buildbot
  2016-08-29 14:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  3:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Reduce parameter list in bfd_elf32_arm_target_relocs
@ 2016-08-26 20:45 sergiodj+buildbot
  2016-08-27  7:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add missing ARMv8-M special registers
@ 2016-08-26 17:28 sergiodj+buildbot
  2016-08-27  1:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fixed -init, -fini linker options.
@ 2016-08-26 16:28 sergiodj+buildbot
  2016-08-26 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fixes to legacy ARC relocations.
@ 2016-08-26 15:37 sergiodj+buildbot
  2016-08-26 15:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] S390: Add support for core dump NOTE sections
@ 2016-08-26 12:23 sergiodj+buildbot
  2016-08-26 13:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-26 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e3e9290d6c7bc276ac6a15a9d5793a49dde92c41 ***

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

S390: Add support for core dump NOTE sections

This enhances the 32-bit and 64-bit s390 ELF backends with support for
reading and writing the core dump note sections NT_PRSTATUS and
NT_PRPSINFO.  Byte swapping is done as appropriate, such that core files
can now be processed correctly on non-s390 platforms.

bfd/ChangeLog:

	* elf32-s390.c (stdarg.h): New include.
	(elf_s390_grok_psinfo): New function.
	(elf_s390_write_core_note): New function.
	(elf_backend_grok_psinfo): Declare backend hook.
	(elf_backend_write_core_note): Likewise.
	* elf64-s390.c (stdarg.h): New include.
	(elf_s390_grok_prstatus): New function.
	(elf_s390_grok_psinfo): New function.
	(elf_s390_write_core_note): New function.
	(elf_backend_grok_prstatus): Declare backend hook.
	(elf_backend_grok_psinfo): Likewise.
	(elf_backend_write_core_note): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Sync proc_service definition with GLIBC
@ 2016-08-25 10:27 sergiodj+buildbot
  2016-08-25 14:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Allow resetting an empty inferior-tty
@ 2016-08-24 20:24 sergiodj+buildbot
  2016-08-25  9:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] Parse NOTE section in core dump files
@ 2016-08-24 18:02 sergiodj+buildbot
  2016-08-25  8:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix typo in comment
@ 2016-08-24  0:00 sergiodj+buildbot
  2016-08-24  0:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-24  0:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34f81801be0b294a93ac73bac6f6195a66d10b98 ***

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

Fix typo in comment

gdb/ChangeLog:

	* stack.c (parse_frame_specification): Fix typo in comment.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR20494 - User input stops being echoed in CLI
@ 2016-08-23 22:53 sergiodj+buildbot
  2016-08-23 23:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-23 22:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9de1fe3d5607f96491e8f16f474b9441cbec849 ***

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

Fix PR20494 - User input stops being echoed in CLI

This patch fixes a problem that problem triggers if you start an
inferior, e.g., with the "start" command, in a UI created with the
new-ui command, and then run a foreground execution command in the
main UI.  Once the program stops for the latter command, typing in the
main UI no longer echoes back to the user.

The problem revolves around this:

- gdb_has_a_terminal computes its result lazily, on first call.

  that is what saves gdb's initial main UI terminal state (the UI
  associated with stdin):

          our_terminal_info.ttystate = serial_get_tty_state (stdin_serial);

  This is the state that target_terminal_ours() restores.

- In this scenario, the gdb_has_a_terminal function happens to be
  first ever called from within the target_terminal_init call in
  startup_inferior:

      (top-gdb) bt
      #0  gdb_has_a_terminal () at src/gdb/inflow.c:157
      #1  0x000000000079db22 in child_terminal_init_with_pgrp () at src/gdb/inflow.c:217
       [...]
      #4  0x000000000065bacb in target_terminal_init () at src/gdb/target.c:456
      #5  0x00000000004676d2 in startup_inferior () at src/gdb/fork-child.c:531
       [...]
      #7  0x000000000046b168 in linux_nat_create_inferior () at src/gdb/linux-nat.c:1112
       [...]
      #9  0x00000000005f20c9 in start_command (args=0x0, from_tty=1) at src/gdb/infcmd.c:657

If the command to start the inferior is issued on the main UI, then
readline will have deprepped the terminal when we reach the above, and
the problem doesn't appear.

If however the command is issued on a non-main UI, then when we reach
that gdb_has_a_terminal call, the main UI's terminal state is still
set to whatever readline has sets it to in rl_prep_terminal, which
happens to have echo disabled.  Later, when the following synchronous
execution command finishes, we'll call target_terminal_ours to restore
gdb's the main UI's terminal settings, and that restores the terminal
state with echo disabled...

Conceptually, the fix is to move the gdb_has_a_terminal call earlier,
to someplace during GDB initialization, before readline/ncurses have
had a chance to change terminal settings.  Turns out that
"set_initial_gdb_ttystate" is exactly such a place.

I say conceptually, because the fix actually inlines the
gdb_has_a_terminal part that saves the terminal state in
set_initial_gdb_ttystate and then simplifies gdb_has_a_terminal, since
there's no point in making gdb_has_a_terminal do lazy computation.

gdb/ChangeLog:
2016-08-23  Pedro Alves  <palves@redhat.com>

	PR gdb/20494
	* inflow.c (our_terminal_info, initial_gdb_ttystate): Update
	comments.
	(enum gdb_has_a_terminal_flag_enum, gdb_has_a_terminal_flag):
	Delete.
	(set_initial_gdb_ttystate): Record our_terminal_info here too,
	instead of ...
	(gdb_has_a_terminal): ... here.  Reimplement in terms of
	initial_gdb_ttystate.  Make static.
	* terminal.h (gdb_has_a_terminal): Delete declaration.
	(set_initial_gdb_ttystate): Add comment.
	* top.c (show_interactive_mode): Use input_interactive_p instead
	of gdb_has_a_terminal.

gdb/testsuite/ChangeLog:
2016-08-23  Pedro Alves  <palves@redhat.com>

	PR gdb/20494
	* gdb.base/new-ui-echo.c: New file.
	* gdb.base/new-ui-echo.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver_spawn "" rather than gdbserver_spawn ${binfile}
@ 2016-08-23 17:39 sergiodj+buildbot
  2016-08-23 22:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  9:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Error on unsupported PowerPC ifuncs
@ 2016-08-22 20:15 sergiodj+buildbot
  2016-08-22 21:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] Match instruction "STP with base register" in prologue
@ 2016-08-19 19:59 sergiodj+buildbot
  2016-08-20  7:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] x32: gdb: Fix 'call' insn relocation with qRelocInsn
@ 2016-08-19 18:19 sergiodj+buildbot
  2016-08-19 18:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 14:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PR 20472, PowerPC64 ifunc confusion
@ 2016-08-19 12:02 sergiodj+buildbot
  2016-08-19 13:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add myself as write-after-approval GDB maintainer.
@ 2016-08-19  5:31 sergiodj+buildbot
  2016-08-19  6:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add remove-inferiors test
@ 2016-08-18 14:37 sergiodj+buildbot
  2016-08-18 15:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] sim: m68hc11: use standard STATIC_INLINE helper
@ 2016-08-17 21:25 sergiodj+buildbot
  2016-08-17 21:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix heap-buffer-overflow in explicit_location_lex_one
@ 2016-08-15 14:48 sergiodj+buildbot
  2016-08-15 15:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] sim: m68hc11: fix up various prototype related warnings
@ 2016-08-15 12:44 sergiodj+buildbot
  2016-08-15 13:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-15 12:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 527aaa4a3143afedd8dd85aa70862328a9dbe627 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 527aaa4a3143afedd8dd85aa70862328a9dbe627

sim: m68hc11: fix up various prototype related warnings

A few funcs are only used locally, so mark them static to avoid warnings
due to -Wmissing-prototypes.

Some funcs cast the return value wrong, so drop them (and let void * just
work by default).

Update some prototypes to be new style.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Correct .dynsym sh_info
@ 2016-08-13 21:55 sergiodj+buildbot
  2016-08-13 22:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix warning in gdb.base/signals-state-child.c
@ 2016-08-12 13:46 sergiodj+buildbot
  2016-08-13 21:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Export the single step function from the AArch64 simulator.
@ 2016-08-12 11:02 sergiodj+buildbot
  2016-08-13 20:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] MIPS/BFD: Actually produce short microMIPS LA25 stubs
@ 2016-08-11  1:27 sergiodj+buildbot
  2016-08-11  9:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-11  1:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe152e64f65de9cfb6f2059b76be98712baa7b56 ***

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

MIPS/BFD: Actually produce short microMIPS LA25 stubs

For the case where a function which requires an LA25 stub is at the
beginning of a section we use a short sequence comprised of a LUI/ADDIU
instruction pair only and prepended to the associated function rather
than using a trailing jump to reach the function.  This works by
checking for the offset into section of the function symbol being 0.

This is however never the case for microMIPS function symbols, which
have the ISA bit set.  Consequently the short LA25 sequence is never
produced for microMIPS functions, like with the following example:

$ 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
$ objdump -d la25

la25:     file format elf32-tradbigmips

Disassembly of section .text:

004000d0 <.pic.f2>:
  4000d0:	41b9 0040 	lui	t9,0x40
  4000d4:	d420 0083 	j	400106 <f2>
  4000d8:	3339 0107 	addiu	t9,t9,263
  4000dc:	0000 0000 	nop

004000e0 <.pic.f1>:
  4000e0:	41b9 0040 	lui	t9,0x40
  4000e4:	d420 0078 	j	4000f0 <f1>
  4000e8:	3339 00f1 	addiu	t9,t9,241
  4000ec:	0000 0000 	nop

004000f0 <f1>:
  4000f0:	41bc 0002 	lui	gp,0x2
  4000f4:	339c 801f 	addiu	gp,gp,-32737
  4000f8:	033c e150 	addu	gp,gp,t9
  4000fc:	f420 0083 	jal	400106 <f2>
  400100:	0000 0000 	nop
  400104:	45bf      	jrc	ra

00400106 <f2>:
  400106:	45bf      	jrc	ra
	...

00400110 <__start>:
  400110:	f420 0070 	jal	4000e0 <.pic.f1>
  400114:	0000 0000 	nop
  400118:	f420 0068 	jal	4000d0 <.pic.f2>
  40011c:	0000 0000 	nop
$

where `.pic.f1' could omit the trailing jump and the filler NOP and just
fall through to `f1'.

Correct the problem by masking out the ISA bit from microMIPS functions,
which fixes the earlier example:

$ objdump -d la25

la25:     file format elf32-tradbigmips

Disassembly of section .text:

004000d0 <.pic.f2>:
  4000d0:	41b9 0040 	lui	t9,0x40
  4000d4:	d420 0083 	j	400106 <f2>
  4000d8:	3339 0107 	addiu	t9,t9,263
	...

004000e8 <.pic.f1>:
  4000e8:	41b9 0040 	lui	t9,0x40
  4000ec:	3339 00f1 	addiu	t9,t9,241

004000f0 <f1>:
  4000f0:	41bc 0002 	lui	gp,0x2
  4000f4:	339c 801f 	addiu	gp,gp,-32737
  4000f8:	033c e150 	addu	gp,gp,t9
  4000fc:	f420 0083 	jal	400106 <f2>
  400100:	0000 0000 	nop
  400104:	45bf      	jrc	ra

00400106 <f2>:
  400106:	45bf      	jrc	ra
	...

00400110 <__start>:
  400110:	f420 0074 	jal	4000e8 <.pic.f1>
  400114:	0000 0000 	nop
  400118:	f420 0068 	jal	4000d0 <.pic.f2>
  40011c:	0000 0000 	nop
$

There is no need to do anything for MIPS16 functions, because if any
LA25 stub has been generated for such a function, then it is only
required for an associated call thunk only, which is regular MIPS code
and the address of which, with the ISA bit clear, is returned by
`mips_elf_get_la25_target'.

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_add_la25_stub): Clear the ISA bit of
	the stub address retrieved if associated with a microMIPS
	function.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Support setting thread names (MS-Windows)
@ 2016-08-11  0:35 sergiodj+buildbot
  2016-08-11  0:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Quiet ARI gettext checks
@ 2016-08-10 21:20 sergiodj+buildbot
  2016-08-10 23:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 23:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Correct the calculation of the use_counts of merged .got entries.
@ 2016-08-09 20:38 sergiodj+buildbot
  2016-08-09 21:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-09 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68994ca2c06b55c46e53d670bc10869e7f1bc5fe ***

Author: Jiaming Wei <jmwei@hxgpt.com>
Branch: master
Commit: 68994ca2c06b55c46e53d670bc10869e7f1bc5fe

Correct the calculation of the use_counts of merged .got entries.

	* elf64-alpha.c (elf64_alpha_copy_indirect_symbol): Fix thinko
	adjusting the use_count of merged .got entries.


^ permalink raw reply	[flat|nested] 1903+ 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 19:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Regenerate some target description files
@ 2016-08-09  7:29 sergiodj+buildbot
  2016-08-09 12:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix memory leaks in chew program.
@ 2016-08-08 16:36 sergiodj+buildbot
  2016-08-09 12:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove unused cli_command_loop declaration
@ 2016-08-05 22:57 sergiodj+buildbot
  2016-08-06  3:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix PR remote/20398: File-IO write always outputs "Quit"
@ 2016-08-05 20:42 sergiodj+buildbot
  2016-08-06  2:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-05 20:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3906a8fc773a405b511faed030e4630ecbd4b8a9 ***

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

Fix PR remote/20398: File-IO write always outputs "Quit"

Commit bb7c96deb1a1 ("gdb/remote-fileio.c: Eliminate custom SIGINT
signal handler") regressed the File-IO support.

Failed output:

  (gdb) target remote :8888
  Remote debugging using :8888
  0x00008098 in _start ()
  (gdb) c
  Continuing.
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  Quit
  [Inferior 1 (Remote target) exited normally]

Expected output:

  (gdb) target remote :8888
  Remote debugging using :8888
  0x00008098 in _start ()
  (gdb) c
  Continuing.
  i: 0
  i: 1
  i: 2
  i: 3
  i: 4
  i: 5
  i: 6
  i: 7
  i: 8
  i: 9
  [Inferior 1 (Remote target) exited normally]

The problem that the new File-IO quit handler forgets to check the
quit flag before calling throwing a quit.

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

	PR remote/20398
	* remote-fileio.c (remote_fileio_quit_handler): Check the quit
	flag before calling quit.


^ permalink raw reply	[flat|nested] 1903+ 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 18:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 21:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] 2016-08-04 Thomas Preud'homme <thomas.preudhomme@arm.com>
@ 2016-08-04 16:00 sergiodj+buildbot
  2016-08-04 18:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-04 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ba2ef8fbe74716708e5ce0bcba4f3b1cc8ac99a ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 4ba2ef8fbe74716708e5ce0bcba4f3b1cc8ac99a

2016-08-04  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (CMSE_PREFIX): Define macro.
	(elf32_arm_stub_cmse_branch_thumb_only): Define stub sequence.
	(cmse_branch_thumb_only): Declare stub.
	(struct elf32_arm_link_hash_table): Define cmse_stub_sec field.
	(elf32_arm_get_plt_info): Add globals parameter.  Use it to return
	FALSE if there is no PLT.
	(arm_type_of_stub): Adapt to new elf32_arm_get_plt_info signature.
	(elf32_arm_final_link_relocate): Likewise.
	(elf32_arm_gc_sweep_hook): Likewise.
	(elf32_arm_gc_mark_extra_sections): Mark sections holding ARMv8-M
	secure entry functions.
	(arm_stub_is_thumb): Add case for arm_stub_cmse_branch_thumb_only.
	(arm_dedicated_stub_output_section_required): Change to a switch case
	and add a case for arm_stub_cmse_branch_thumb_only.
	(arm_dedicated_stub_output_section_required_alignment): Likewise.
	(arm_stub_dedicated_output_section_name): Likewise.
	(arm_stub_dedicated_input_section_ptr): Likewise and remove
	ATTRIBUTE_UNUSED for htab parameter.
	(arm_stub_required_alignment): Likewise.
	(arm_stub_sym_claimed): Likewise.
	(arm_dedicated_stub_section_padding): Likewise.
	(cmse_scan): New function.
	(elf32_arm_size_stubs): Call cmse_scan for ARM M profile targets.
	Set stub_changed to TRUE if such veneers were created.
	(elf32_arm_swap_symbol_in): Add detection code for CMSE special
	symbols.

include/
	* arm.h (ARM_GET_SYM_CMSE_SPCL): Define macro.
	(ARM_SET_SYM_CMSE_SPCL): Likewise.

ld/
	* ld.texinfo (Placement of SG veneers): New concept entry.
	* testsuite/ld-arm/arm-elf.exp
	(Secure gateway veneers: no .gnu.sgstubs section): New test.
	(Secure gateway veneers: wrong entry functions): Likewise.
	(Secure gateway veneers (ARMv8-M Baseline)): Likewise.
	(Secure gateway veneers (ARMv8-M Mainline)): Likewise.
	* testsuite/ld-arm/cmse-veneers.s: New file.
	* testsuite/ld-arm/cmse-veneers.d: Likewise.
	* testsuite/ld-arm/cmse-veneers.rd: Likewise.
	* testsuite/ld-arm/cmse-veneers.sd: Likewise.
	* testsuite/ld-arm/cmse-veneers-no-gnu_sgstubs.out: Likewise.
	* testsuite/ld-arm/cmse-veneers-wrong-entryfct.out: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add myself as Rust maintainer
@ 2016-08-03 16:11 sergiodj+buildbot
  2016-08-03 16:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 13:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Bump version to 7.12.50.DATE-git.
@ 2016-08-01 17:20 sergiodj+buildbot
  2016-08-01 18:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Swap "single-process" and "multi-process" in process-dies-while-detaching.exp
@ 2016-08-01 13:20 sergiodj+buildbot
  2016-08-01 14:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-08-01 13:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41bfcd638a4e0e48b96ce4de2845372dea481322 ***

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

Swap "single-process" and "multi-process" in process-dies-while-detaching.exp

"single-process" and "multi-process" are used in the test message of
process-dies-while-detaching.exp, but they are misplaced due to

    set mode [expr {$multi_process ? "single-process" : "multi-process"}]

This patch is to swap them.

gdb/testsuite:

2016-08-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.threads/process-dies-while-detaching.exp (do_test): Set
	variable mode to "multi-process" if $multi_process is 1, otherwise
	set it to "single-process".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <147d994bcdd36a177e49e7b6ac8d9c1f7b4cdcf5@gdb-build>]
[parent not found: <40c31709c6a51926fcb409611caa52b2da6515c0@gdb-build>]
[parent not found: <e0461dbb653dbb3c46ea7a15054fd2c98f879f31@gdb-build>]
[parent not found: <3a1518e4f3c467cfee2786b0af3388529f14d23b@gdb-build>]
[parent not found: <e34879080d8935792ef3942efa5f25b4c3169b5a@gdb-build>]
* [binutils-gdb] Fix ARMv8.1/v8.2 for hw watchpoint and breakpoint
@ 2016-07-23 19:48 sergiodj+buildbot
  2016-07-23 20:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PR rust/20162 - fix gdb regressions caused by rust 1.10
@ 2016-07-22 21:05 sergiodj+buildbot
  2016-07-23  0:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-22 21:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e98c9e7ce1c9fd2a5ad99ae2de637b4c16d999b3 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: e98c9e7ce1c9fd2a5ad99ae2de637b4c16d999b3

PR rust/20162 - fix gdb regressions caused by rust 1.10

PR rust/20162 started life as a reminder to test gdb with versions of
rust after 1.8; but now concerns some gdb regressions seen with rust
1.10 ("beta") and 1.11 ("nightly").

The failures turn out to be a discrepancy between how rustc emits
DWARF and how gdb interprets it.  In particular, rustc will emit DWARF
like:

 <2><bc>: Abbrev Number: 9 (DW_TAG_structure_type)
    <bd>   DW_AT_name        : (indirect string, offset: 0x46a): HasMethods
    <c1>   DW_AT_byte_size   : 4
...
 <3><cc>: Abbrev Number: 11 (DW_TAG_subprogram)
...
    <df>   DW_AT_name        : (indirect string, offset: 0x514f): new

gdb wants to see a separate top-level DW_TAG_subprogram that refers to
this one via DW_AT_specification; but rustc doesn't emit one.  By my
reading of DWARF 4 5.5.7, this is ok, and gdb is incorrect here.

Fixing this involved a new case in scan_partial_symbols, and then a
further change in process_structure_scope to account for the fact
that, in Rust, such functions are not methods and should not be
attached to the structure type.

Next, it turns out that rust is emitting bad values for
DW_AT_linkage_name, e.g.:

    <db>   DW_AT_linkage_name: (indirect string, offset: 0x422): _ZN7methods8{{impl}}3newE

The the "{{impl}}" stuff is apparently some side effect of a change to
the compiler's internal representation.  Oops!

This also had a simple fix -- disregard these mangled names.

With these changes, there are no regressions in the gdb Rust tests
with either 1.10 or 1.11.  1.9, the stable release, is still pretty
broken, but I think there's nothing much to do about that.

These changes are a bit hackish, but no worse, I think, than other
kinds of quirk handling already done in the DWARF parser.  I have
reported all the rustc bugs upstream.  I plan to remove these hacks
from gdb some suitable time after they have been fixed in released
versions of Rust.

2016-07-22  Tom Tromey  <tom@tromey.com>

	PR rust/20162:
	* dwarf2read.c (scan_partial_symbols) <DW_TAG_structure_type>:
	Call scan_partial_symbols for children when reading a Rust CU.
	(dwarf2_physname): Ignore invalid DW_AT_linkage_name generated by
	rustc.
	(process_structure_scope) <DW_TAG_subprogram>: Call
	read_func_scope for Rust.


^ permalink raw reply	[flat|nested] 1903+ 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:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Allow empty struct expressions in Rust
@ 2016-07-22  3:02 sergiodj+buildbot
  2016-07-22  3:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix djgpp gdb build
@ 2016-07-21 20:40 sergiodj+buildbot
  2016-07-22  1:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove unused variable in windows-nat.c
@ 2016-07-21 19:45 sergiodj+buildbot
  2016-07-21 23:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Enqueue signal even when resuming threads
@ 2016-07-21 15:58 sergiodj+buildbot
  2016-07-21 19:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make reinsert_breakpoint thread specific
@ 2016-07-21 14:36 sergiodj+buildbot
  2016-07-21 16:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Refactor clone_all_breakpoints
@ 2016-07-21 13:37 sergiodj+buildbot
  2016-07-21 15:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Pass breakpoint type in set_breakpoint_at
@ 2016-07-21 13:09 sergiodj+buildbot
  2016-07-21 13:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-21 13:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 811f8301f8054eb964e92af63930c4495207e7d5 ***

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

Pass breakpoint type in set_breakpoint_at

Nowadays, set_breakpoint_at creates breakpoint of type
other_breakpoint, but we also use set_breakpoint_at
in set_reinsert_breakpoint to create breakpoint, so that
we have to overwrite the breakpoint type like this,

  bp = set_breakpoint_at (stop_at, NULL);
  bp->type = reinsert_breakpoint;

which looks not very good.  This patch changes set_breakpoint_at
to receive breakpoint type.  Since set_breakpoint_at is
used in many places, I rename it to set_breakpoint_type_at, and wrap
it with set_breakpoint_at, and pass other_breakpoint.  In this way,
we can call set_breakpoint_type_at with reinsert_breakpoint in
set_reinsert_breakpoint too, and code looks cleaner.

gdb/gdbserver:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* mem-break.c (set_breakpoint_at): Rename it to ...
	(set_breakpoint_type_at): ... it.
	(set_breakpoint_at): Call set_breakpoint_type_at.
	(set_reinsert_breakpoint): Call set_breakpoint_type_at.
	* mem-break.h (set_breakpoint_at): Update comments.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix fail in gdb.server/solib-list.exp
@ 2016-07-21  9:38 sergiodj+buildbot
  2016-07-21 10:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-21  9:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1b53fb3ef077bf4412da53f0057b9c0e9ed4f3e ***

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

Fix fail in gdb.server/solib-list.exp

If I run single test solib-list.exp, it is OK.  If I run two, as below,
there are fails,

$ make check RUNTESTFLAGS="server-run.exp solib-list.exp"
FAIL: gdb.server/solib-list.exp: non-stop 0: continue (the program exited)
FAIL: gdb.server/solib-list.exp: non-stop 0: p libvar
FAIL: gdb.server/solib-list.exp: non-stop 1: continue (the program exited)
FAIL: gdb.server/solib-list.exp: non-stop 1: p libvar

in gdb.log,

/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.server/server-run/server-run /lib64/ld-linux-x86-64.so.2 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.server/solib-list/solib-list

server-run is spawned, which is wrong.  If I only run solib-list.exp, ld-linux
is spawned, which is right.

/scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../../gdb/gdbserver/gdbserver --once :2346 /lib64/ld-linux-x86-64.so.2 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/outputs/gdb.server/solib-list/solib-list

in test, we spawn gdbserver this way,

    # Note we pass ${interp_system}, the program gdbserver spawns, as
    # argument here, instead of using gdb_load, because we don't want
    # to download the interpreter to the target (it's already there)
    # or to the test output directory.
    set res [gdbserver_spawn "${interp_system} ${remote_binfile}"]

in gdbserver_spawn -> gdbserver_download_current_prog, if
last_loaded_file is set (when you run multiple tests), it is
returned.

This patch is to unset last_loaded_file in solib-list.exp.

gdb/testsuite:

2016-07-21  Yao Qi  <yao.qi@linaro.org>

	* gdb.server/solib-list.exp: Unset last_loaded_file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix implib test failures
@ 2016-07-21  4:17 sergiodj+buildbot
  2016-07-21  9:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  2:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Enable ptrace events on new child processes.
@ 2016-07-20 20:22 sergiodj+buildbot
  2016-07-21  2:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add support to the ARC disassembler for selecting instruction classes.
@ 2016-07-20 18:55 sergiodj+buildbot
  2016-07-20 21:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 18:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37fd5ef3ecc58caacd6abb4ace3d8b559e3db53d ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 37fd5ef3ecc58caacd6abb4ace3d8b559e3db53d

Add support to the ARC disassembler for selecting instruction classes.

gas	* testsuite/gas/arc/dsp.d: New file.
	* testsuite/gas/arc/dsp.s: Likewise.
	* testsuite/gas/arc/fpu.d: Likewise.
	* testsuite/gas/arc/fpu.s: Likewise.
	* testsuite/gas/arc/ext2op.d: Add specific disassembler option.
	* testsuite/gas/arc/ext3op.d: Likewise.
	* testsuite/gas/arc/tdpfp.d: Likewise.
	* testsuite/gas/arc/tfpuda.d: Likewise.

opcodes	* arc-dis.c (skipclass): New structure.
	(decodelist): New variable.
	(is_compatible_p): New function.
	(new_element): Likewise.
	(skip_class_p): Likewise.
	(find_format_from_table): Use skip_class_p function.
	(find_format): Decode first the extension instructions.
	(print_insn_arc): Select either ARCEM or ARCHS based on elf
	e_flags.
	(parse_option): New function.
	(parse_disassembler_options): Likewise.
	(print_arc_disassembler_options): Likewise.
	(print_insn_arc): Use parse_disassembler_options function.  Proper
	select ARCv2 cpu variant.
	* disassemble.c (disassembler_usage): Add ARC disassembler
	options.

binutils* doc/binutils.texi (objdump): Add ARC disassembler options.
	* testsuite/binutils-all/arc/dsp.s: New file.
	* testsuite/binutils-all/arc/objdump.exp: Likewise.

include	* dis-asm.h: Declare print_arc_disassembler_options.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Handle version 1a of FreeBSD's NT_PRSINFO.
@ 2016-07-20 18:21 sergiodj+buildbot
  2016-07-20 20:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 18:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0064d22386b99c047bbff3bcc73b6bfce9c29b4c ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 0064d22386b99c047bbff3bcc73b6bfce9c29b4c

Handle version 1a of FreeBSD's NT_PRSINFO.

Version 1a adds a pr_pid member containing the process ID of the
terminating process.  The presence of pr_pid is inferred from the
note's size.

bfd/ChangeLog:

	* elf.c (elfcore_grok_freebsd_psinfo): Check for minimum note size
	and handle pr_pid if present.


^ permalink raw reply	[flat|nested] 1903+ 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:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Enable the configuration of GDB for the NDS32 target.
@ 2016-07-20 10:29 sergiodj+buildbot
  2016-07-20 14:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-20 10:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bedbe19cc09fbb6e921872334bfcd371ac5b769d ***

Author: Yan-Ting Lin <currygt52@gmail.com>
Branch: master
Commit: bedbe19cc09fbb6e921872334bfcd371ac5b769d

Enable the configuration of GDB for the NDS32 target.

    * configure.ac (nds32*-*-*): Remove entry to enable gdb.
    * configure: Regenerated.


^ permalink raw reply	[flat|nested] 1903+ 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 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] MIPS: Convert cross-mode BAL to JALX
@ 2016-07-19 16:20 sergiodj+buildbot
  2016-07-19 17:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use do_self_tests in selftest.exp
@ 2016-07-19 10:01 sergiodj+buildbot
  2016-07-19 11:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] GDB testsuite: Escape paths used in regular expressions
@ 2016-07-15 18:48 sergiodj+buildbot
  2016-07-15 19:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add support for creating ELF import libraries
@ 2016-07-15 17:10 sergiodj+buildbot
  2016-07-15 17:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-15 17:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 76359541825cf36ecd14ab6b5974ee56e1c59eff ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 76359541825cf36ecd14ab6b5974ee56e1c59eff

Add support for creating ELF import libraries

2016-07-15  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf-bfd.h (elf_backend_filter_implib_symbols): Declare backend hook.
	(_bfd_elf_filter_global_symbols): Declare.
	* elf.c (_bfd_elf_filter_global_symbols): New function.
	* elflink.c (elf_filter_global_symbols): Likewise.
	(elf_output_implib): Likewise.
	(bfd_elf_final_link): Call above function, failing if it does.
	* elfxx-target.h (elf_backend_filter_implib_symbols): Define macro and
	default it to NULL.
	(elf_backend_copy_indirect_symbol): Fix spacing.
	(elf_backend_hide_symbol): Likewise.
	(elfNN_bed): Initialize elf_backend_filter_implib_symbols backend hook.

include/
	* bfdlink.h (struct bfd_link_info): Declare new ldscript_def and
	out_implib_bfd fields.

2016-07-15  Thomas Preud'homme  <thomas.preudhomme@arm.com>
	    Nick Clifton  <nickc@redhat.com>

ld/
	* emultempl/elf32.em (gld${EMULATION_NAME}_after_open): Open import
	library file for writing and initialize implib_bfd field of link_info
	structure.
	* emultempl/pe.em (pe_implib_filename): Remove variable declaration.
	(OPTION_IMPLIB_FILENAME): Remove macro definition.
	(gld${EMULATION_NAME}_add_options): Remove --out-implib option.
	(gld_${EMULATION_NAME}_list_options): Likewise.
	(gld${EMULATION_NAME}_handle_option): Likewise.
	(gld_${EMULATION_NAME}_finish): Use command_line.out_implib_filename
	instead of pe_implib_filename.
	* emultempl/pep.em (pep_implib_filename): Remove variable declaration.
	(OPTION_IMPLIB_FILENAME): Remove enumerator.
	(gld${EMULATION_NAME}_add_options): Remove --out-implib option.
	(gld_${EMULATION_NAME}_list_options): Likewise.
	(gld${EMULATION_NAME}_handle_option): Likewise.
	(gld_${EMULATION_NAME}_finish): Use command_line.out_implib_filename
	instead of pep_implib_filename.
	* ld.h (args_type): Declare new out_implib_filename field.
	* ld.texinfo (--out-implib): Move documentation to arch-independent
	part and rephrase to apply to ELF targets.
	* ldexp.c (exp_fold_tree_1): Set ldscript_def field to 1 for symbols
	defined in linker scripts.
	* ldlex.h (enum option_values): Declare new OPTION_OUT_IMPLIB
	enumerator.
	* lexsup.c (ld_options): Add entry for new --out-implib switch.
	(parse_args): Handle OPTION_OUT_IMPLIB case.
	* testsuite/ld-elf/elf.exp (Generate empty import library): New test.
	(Generate import library): Likewise.
	* testsuite/ld-elf/implib.s: Likewise.
	* testsuite/ld-elf/implib.rd: New file.
	* testsuite/ld-elf/empty-implib.out: Likewise


^ permalink raw reply	[flat|nested] 1903+ 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] BFD: Let targets handle relocations against absolute symbols
@ 2016-07-14 21:44 sergiodj+buildbot
  2016-07-15  2:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use getcurx in curses code
@ 2016-07-14 18:10 sergiodj+buildbot
  2016-07-14 19:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-14 18:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cecc8b99060bf82632345bd1c07d50c7ae8d81ef ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: cecc8b99060bf82632345bd1c07d50c7ae8d81ef

Use getcurx in curses code

As suggested by Pedro, this changes a few spots to use getcurx, rather
than getyx.  This avoids some unused variable warnings.

2016-07-14  Tom Tromey  <tom@tromey.com>

	* tui/tui-winsource.c (tui_show_source_line): Use getcurx.
	* tui/tui-io.c (tui_puts): Use getcurx.
	(tui_redisplay_readline): Likewise.


^ permalink raw reply	[flat|nested] 1903+ 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:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] Fix/improve small data support.
@ 2016-07-14  8:46 sergiodj+buildbot
  2016-07-14  9:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-14  8:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa1c0170176a5e4820f43824cffe80ffc4e7a717 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: fa1c0170176a5e4820f43824cffe80ffc4e7a717

[ARC] Fix/improve small data support.

The R_ARC_SDA32 is wrongly described as a ME relocation, fix it.  Offset the
__SDATA_BEGIN__ to take advantage of the signed 9-bit field of the
load/store instructions.

include/
2016-07-08  Claudiu Zissulescu  <claziss@synopsys.com>

	* elf/arc-reloc.def (ARC_SDA32): Don't use ME transformation.

ld/
2016-07-08  Claudiu Zissulescu  <claziss@synopsys.com>

	* emulparams/arcelf.sh (SDATA_START_SYMBOLS): Add offset.
	* testsuite/ld-arc/sda-relocs.dd: New file.
	* testsuite/ld-arc/sda-relocs.ld: Likewise.
	* testsuite/ld-arc/sda-relocs.rd: Likewise.
	* testsuite/ld-arc/sda-relocs.s: Likewise.
	* testsuite/ld-arc/arc.exp: Add SDA tests.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR python/15620, PR python/18620 - breakpoint events in Python
@ 2016-07-13 21:51 sergiodj+buildbot
  2016-07-14  6:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-13 21:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dac790e1b9048a318e1882979d7188d82c3bd757 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: dac790e1b9048a318e1882979d7188d82c3bd757

PR python/15620, PR python/18620 - breakpoint events in Python

This patch adds some breakpoint events to Python.  In particular,
there is a creation event that is emitted when a breakpoint is
created; a modification event that is emitted when a breakpoint
changes somehow; and a deletion event that is emitted when a
breakpoint is deleted.

In this patch, the event's payload is the breakpoint itself.  I
considered making a new event type to hold the breakpoint, but I
didn't see a need.  Still, I thought I would mention this as a spot
where some other choice is possible.

Built and regtested on x86-64 Fedora 23.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR python/15620, PR python/18620:
	* python/py-evts.c (gdbpy_initialize_py_events): Call
	add_new_registry for new events.
	* python/py-events.h (events_object) <breakpoint_created,
	breakpoint_deleted, breakpoint_modified>: New fields.
	* python/py-breakpoint.c (gdbpy_breakpoint_created): Emit the
	breakpoint changed event.
	(gdbpy_breakpoint_deleted): Emit the breakpoint deleted event.
	(gdbpy_breakpoint_modified): New function.
	(gdbpy_initialize_breakpoints): Attach to the breakpoint modified
	observer.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR python/15620, PR python/18620:
	* python.texi (Events In Python): Document new breakpoint events.

2016-07-13  Tom Tromey  <tom@tromey.com>

	PR python/15620, PR python/18620:
	* gdb.python/py-breakpoint.exp (connect_event, check_last_event)
	(test_bkpt_events): New procs.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] use user_breakpoint_p in python code
@ 2016-07-13 20:39 sergiodj+buildbot
  2016-07-13 21:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix PR cli/18053
@ 2016-07-13 19:38 sergiodj+buildbot
  2016-07-13 20:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] MIPS/opcodes: Address issues with NAL disassembly
@ 2016-07-13 17:04 sergiodj+buildbot
  2016-07-13 17:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Second fix for grammar in error message.
@ 2016-07-12 15:23 sergiodj+buildbot
  2016-07-12 16:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Match the selftest output when captured_main is inlined
@ 2016-07-12 14:56 sergiodj+buildbot
  2016-07-12 15:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-12 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cfe46b618f140ce93de3cdbe9693b51eea4acf3 ***

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

Match the selftest output when captured_main is inlined

In gdb.gdb/observer.exp, I see the following fail,

(gdb) break captured_main^M
Breakpoint 1 at 0x57e409: file ../../binutils-gdb/gdb/main.c, line 492.^M
(gdb) PASS: gdb.gdb/observer.exp: breakpoint in captured_main
run -nw -nx -data-directory /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../data-directory^M
Starting program: /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/outputs/gdb.gdb/observer/xgdb -nw -nx -data-directory /home/yao.qi/SourceCode/gnu/build/gdb/testsuite/../data-directory^M
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".^M
^M
Breakpoint 1, gdb_main (args=args@entry=0x7fffffffdca0) at ../../binutils-gdb/gdb/main.c:1157^M
1157          captured_main (args);^M
(gdb) FAIL: gdb.gdb/observer.exp: run until breakpoint at captured_main

looks the test sets breakpoint on captured_main, and expects program
stops at captured_main.  However, program stops at the place where
captured_main is called, because captured_main is inlined,

 <1><8519e3>: Abbrev Number: 58 (DW_TAG_subprogram)
    <8519e4>   DW_AT_name        : (indirect string, offset: 0x880d3): captured_main
    <8519e8>   DW_AT_decl_file   : 1
    <8519e9>   DW_AT_decl_line   : 444
    <8519eb>   DW_AT_type        : <0x846e48>
    <8519ef>   DW_AT_inline      : 1    (inlined)
    <8519f0>   DW_AT_sibling     : <0x851c01>

The test passes if I build GDB with '-O0 -g3', because captured_main
isn't inlined.  This patch is to match the output when captured_main
is inlined.

gdb/testsuite:

2016-07-12  Yao Qi  <yao.qi@linaro.org>

	* lib/selftest-support.exp (selftest_setup): Match the output
	when captured_main is inlined.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Enable relocation overflow messages by default.
@ 2016-07-11 14:57 sergiodj+buildbot
  2016-07-11 15:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] FT32: Correct 32-bit reloc for BFD_RELOC_32
@ 2016-07-08 19:38 sergiodj+buildbot
  2016-07-08 20:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-08 19:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 458653a9b2cf311e7bbb71efd1b410216e0ce059 ***

Author: jamesbowman <jamesb@excamera.com>
Branch: master
Commit: 458653a9b2cf311e7bbb71efd1b410216e0ce059

FT32: Correct 32-bit reloc for BFD_RELOC_32

The reloc for BFD_RELOC_32 was using the the 20-bit. This hack causes
problems in gdb.  Fixed it to be the proper 32-bit reloc, R_FT32_32.

bfd/ChangeLog:

	* elf32-ft32.c (ft32_reloc_map): Use R_FT32_32 for BFD_RELOC_32.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] FT32: adjust disassembly opcode match fields
@ 2016-07-08 19:25 sergiodj+buildbot
  2016-07-08 19:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [obv] Fix broken build on Fedora 23.
@ 2016-07-07 17:47 sergiodj+buildbot
  2016-07-07 18:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix of default lookup for "this" symbol.
@ 2016-07-07 15:52 sergiodj+buildbot
  2016-07-07 16:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove extra output directory level for Ada tests
@ 2016-07-06 16:12 sergiodj+buildbot
  2016-07-06 18:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove extraneous parentheses.
@ 2016-07-06 15:43 sergiodj+buildbot
  2016-07-06 17:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type.
@ 2016-07-06 13:14 sergiodj+buildbot
  2016-07-06 13:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-07-06 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee950322ca2c77494b1742f304632f667ed6ce79 ***

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

Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type.

'ptid' compiles in C++, but not C.

gdb/ChangeLog:
	* fbsd-nat.c (fbsd_is_vfork_done_pending): Fix return type.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Fix endless recursion on calculating CPRC candidate
@ 2016-07-06  7:38 sergiodj+buildbot
  2016-07-06  8:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix fail in gdb.mi/mi-reverse.exp
@ 2016-07-05 14:06 sergiodj+buildbot
  2016-07-05 14:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 13:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 20:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Honor detach-on-fork on FreeBSD.
@ 2016-07-01 17:17 sergiodj+buildbot
  2016-07-01 18:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Factor out "Detaching from program" message printing
@ 2016-07-01 10:53 sergiodj+buildbot
  2016-07-01 11:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] x86/Intel: fix operand checking for MOVSD
@ 2016-07-01  7:09 sergiodj+buildbot
  2016-07-01  7:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix typo in comment
@ 2016-06-30 15:32 sergiodj+buildbot
  2016-06-30 16:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 15:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 838441e4a2a041e3a5dd26e886c67be22529502d ***

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

Fix typo in comment

This patch fixes the typo "uf" in the comment.  I'll push it in as the
change is obvious.

2016-06-30  Yao Qi  <yao.qi@linaro.org>

	* arm-dis.c (print_insn): Fix typo in comment.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work
@ 2016-06-30 11:28 sergiodj+buildbot
  2016-06-30 11:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-30 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 994e9c834d916af85e0fe0e8c3e18259aa4be389 ***

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

Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work

Runing the whole gdb testsuite with MI on a separate tty, with:

  make check RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1"

Doesn't actually work because commit 51f77c3704a6 ("Add testing
infrastruture bits for running with MI on a separate UI") included a
last-minute rename typo, now fixed with this commit.

gdb/testsuite/ChangeLog:
2016-06-30  Pedro Alves  <palves@redhat.com>

	* lib/mi-support.exp (default_mi_gdb_start): Declare global
	FORCE_SEPARATE_MI_TTY, not SEPARATE_MI_TTY.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR python/20129 - use of non-existing variable
@ 2016-06-29 16:58 sergiodj+buildbot
  2016-06-29 18:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 17:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] Use int64_t for address offset
@ 2016-06-28 17:17 sergiodj+buildbot
  2016-06-28 18:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Implement get_syscall_trapinfo for arm-linux
@ 2016-06-28 14:32 sergiodj+buildbot
  2016-06-28 15:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Implement get_syscall_trapinfo for aarch64-linux
@ 2016-06-28 13:31 sergiodj+buildbot
  2016-06-28 14:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-28 13:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 061fc021d5d110cc37a4c06c4ed94b87be00610a ***

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

Implement get_syscall_trapinfo for aarch64-linux

gdb/gdbserver:

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

	* linux-aarch64-low.c (aarch64_get_syscall_trapinfo): New
	function.
	(the_low_target): Install aarch64_get_syscall_trapinfo.


^ permalink raw reply	[flat|nested] 1903+ 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 14:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [AArch64] Make register indices be full 64-bit values
@ 2016-06-28  8:38 sergiodj+buildbot
  2016-06-28  9:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PR 19264 looping in ppc64_elf_size_stubs
@ 2016-06-27 12:10 sergiodj+buildbot
  2016-06-27 12:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-27 12:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9301e31817019c38ab52da0e72fa1e3bf75332c ***

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

PR 19264 looping in ppc64_elf_size_stubs

b399102 fixed the testcase in this PR but it may be possible to
trigger the problem in other ways.

	PR ld/19264
	* elf64-ppc.c (STUB_SHRINK_ITER): Define.
	(ppc64_elf_size_stubs): Exit stub sizing loop past STUB_SHRINK_ITER
	if shrinking stubs.
	(ppc64_elf_size_stubs): Adjust to suit.


^ permalink raw reply	[flat|nested] 1903+ 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 11:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] remove a few sentinals
@ 2016-06-25 16:48 sergiodj+buildbot
  2016-06-25 17:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix formatting in rust-lang.c
@ 2016-06-25 15:10 sergiodj+buildbot
  2016-06-25 15:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add myself as a Write After Approval maintainer.
@ 2016-06-24 22:59 sergiodj+buildbot
  2016-06-25  1:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add constants for FreeBSD-specific auxiliary vector entry types.
@ 2016-06-24 18:28 sergiodj+buildbot
  2016-06-24 19:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PR gdb/16483 - simplify "info frame-filters" output
@ 2016-06-23 14:21 sergiodj+buildbot
  2016-06-24  3:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] addmore extern C
@ 2016-06-22 17:38 sergiodj+buildbot
  2016-06-24  0:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add "new-ui console" tests
@ 2016-06-21 23:24 sergiodj+buildbot
  2016-06-23 18:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Always switch fork child to the main UI
@ 2016-06-21 22:18 sergiodj+buildbot
  2016-06-23 16:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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-23 12:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [DOC] Document support for running interpreters on separate UIs
@ 2016-06-21 19:51 sergiodj+buildbot
  2016-06-23 11:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add new command to create extra console/mi UIs
@ 2016-06-21 18:51 sergiodj+buildbot
  2016-06-22 23:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Simplify starting the command event loop
@ 2016-06-21 18:08 sergiodj+buildbot
  2016-06-21 20:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2d86570b316c347384c4ba9bb3933ed5e807fca ***

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

Simplify starting the command event loop

All interpreter types (CLI/TUI/MI) print the prompt, and then call
start_event_loop.

Because we'll need an interpreter hook to display the
interpreter-specific prompt before going back to the event loop,
without actually starting an event loop, this patch moves the
start_event_loop call to common code, and replaces the command_loop
hook with a pre_command_look hook, that now just prints the prompt.

Turns out to be a cleanup on its own right anyway.

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

	* cli/cli-interp.c (cli_interpreter_pre_command_loop): New
	function.
	(cli_interp_procs): Install it instead of cli_command_loop.
	* cli/cli-interp.h (cli_interpreter_pre_command_loop): Declare.
	* event-top.c (cli_command_loop): Delete.
	* interps.c (interp_new): Remove reference to command_loop_proc.
	(current_interp_command_loop): Delete.
	(interp_pre_command_loop): New function.
	(interp_command_loop_ftype): Delete.
	* interps.h (interp_pre_command_loop_ftype): New typedef.
	(struct interp_procs) <command_loop_proc>: Delele field.
	<pre_command_loop_proc>: New field.
	(current_interp_command_loop): Delete declaration.
	(interp_pre_command_loop): New declaration.
	* main.c (captured_command_loop): Call interp_pre_command_loop
	instead of current_interp_command_loop and start an event loop.
	* mi/mi-interp.c (mi_command_loop): Delete.
	(mi_interpreter_pre_command_loop): New.
	(mi_interp_procs): Update.
	* tui/tui-interp.c (tui_interp_procs): Install
	cli_interpreter_pre_command_loop instead of cli_command_loop.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Make stdin be per UI
@ 2016-06-21 18:04 sergiodj+buildbot
  2016-06-22 22:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 21:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make current_ui_out be per UI
@ 2016-06-21 11:56 sergiodj+buildbot
  2016-06-21 13:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make raw_stdout be per MI instance
@ 2016-06-21 11:28 sergiodj+buildbot
  2016-06-21 19:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make target_terminal_inferior/ours almost nops on non-main UIs
@ 2016-06-21 10:12 sergiodj+buildbot
  2016-06-21 16:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-21 10:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 215d3118fe5f120c1deba66943329e30073ed780 ***

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

Make target_terminal_inferior/ours almost nops on non-main UIs

Since we always run the inferior in the main console (unless "set
inferior-tty" is in effect), when some UI other than the main one
calls target_terminal_inferior/target_terminal_inferior, then we only
register/unregister the UI's input from the event loop, but leave the
main UI's terminal settings as is.

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

	* target.c (target_terminal_inferior): Bail out after
	unregistering input_fd if not on the main UI.
	(target_terminal_ours): Bail out after registering input_fd if not
	on the main UI.
	(target_terminal_ours_for_output): Bail out if not on the main UI.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Make out and error streams be per UI
@ 2016-06-21 10:04 sergiodj+buildbot
  2016-06-21 11:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Always process target events in the main UI
@ 2016-06-21  9:34 sergiodj+buildbot
  2016-06-21 15:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 14:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make input_fd be per UI
@ 2016-06-21  6:37 sergiodj+buildbot
  2016-06-21 10:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make the intepreters output to all UIs
@ 2016-06-21  4:34 sergiodj+buildbot
  2016-06-21  7:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Make gdb_stdout&co be per UI
@ 2016-06-21  2:22 sergiodj+buildbot
  2016-06-21  4:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Introduce "struct ui"
@ 2016-06-21  1:57 sergiodj+buildbot
  2016-06-21  3:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  2:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use the IR symbol table for the IR input object
@ 2016-06-20 12:50 sergiodj+buildbot
  2016-06-20 13:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-20 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7dc3990e4002e0062007c1d41b56e04b5b8ec1ec ***

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

Use the IR symbol table for the IR input object

ELF linker shouldn't skip the IR object when searching the symbol table
of an archive element.  If linker doesn't know if the object file is an
IR object, it should give LTO plugin a chance to get the correct symbol
table and use the IR symbol table if the input is an IR object.

bfd/

	PR ld/18250
	PR ld/20267
	* elflink.c: Include plugin.h if BFD_SUPPORTS_PLUGINS is
	defined.
	(elf_link_is_defined_archive_symbol): Call
	bfd_link_plugin_object_p on unknown plugin object and use the
	IR symbol table if the input is an IR object.
	* plugin.c (bfd_link_plugin_object_p): New function.
	* plugin.h (bfd_link_plugin_object_p): New prototype.

ld/

	PR ld/20267
	* testsuite/ld-plugin/lto.exp (lto_link_tests): Add test for
	PR ld/20267.
	(lto_run_tests): Likewise.
	* testsuite/ld-plugin/pr20267a.c: New file.
	* testsuite/ld-plugin/pr20267b.c: Likewise.


^ permalink raw reply	[flat|nested] 1903+ 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  3:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Delete reinsert breakpoints from forked child
@ 2016-06-17 14:33 sergiodj+buildbot
  2016-06-17 18:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] More assert checks on reinsert breakpoint
@ 2016-06-17 12:52 sergiodj+buildbot
  2016-06-17 15:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: new AndesTech NDS32 port
@ 2016-06-17 11:35 sergiodj+buildbot
  2016-06-17 13:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Don't check undefined symbol for IFUNC reloc
@ 2016-06-16 18:57 sergiodj+buildbot
  2016-06-16 19:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Check SEC_ALLOC before allocating dynamic relocation
@ 2016-06-16  2:00 sergiodj+buildbot
  2016-06-16  3:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove unneeded checks on type lengths.
@ 2016-06-15  0:47 sergiodj+buildbot
  2016-06-15  0:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Check R_*_IRELATIVE in x86 reloc_type_class
@ 2016-06-14 18:11 sergiodj+buildbot
  2016-06-14 21:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 18:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c428ce9d900c4acc4a7ee74791c55676d96f0818 ***

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

Check R_*_IRELATIVE in x86 reloc_type_class

elf_{i386|x86_64}_reloc_type_class should return reloc_class_ifunc for
R_386_IRELATIVE/R_X86_64_IRELATIVE relocations.  There is no need to
check symbol type for STN_UNDEF symbol index.

	* elf32-i386.c (elf_i386_reloc_type_class): Check R_386_IRELATIVE.
	Don't check symbol type for STN_UNDEF symbol index.
	* elf64-x86-64.c (elf_x86_64_reloc_type_class): Check
	R_X86_64_IRELATIVE.  Don't check symbol type for STN_UNDEF symbol
	index.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] Add ldbit for nps
@ 2016-06-14 17:03 sergiodj+buildbot
  2016-06-14 18:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] Add arithmetic and logic instructions for nps
@ 2016-06-14 15:50 sergiodj+buildbot
  2016-06-14 16:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix feature checks based on ARM architecture value
@ 2016-06-14 11:26 sergiodj+buildbot
  2016-06-14 12:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-14 11:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 60a019a089177f3f58f636580857414d769b8c11 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 60a019a089177f3f58f636580857414d769b8c11

Fix feature checks based on ARM architecture value

2016-06-14  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* elf32-arm.c (using_thumb_only): Force review of arch check logic for
	new architecture.
	(using_thumb2): Try Tag_THUMB_ISA_use first and check
	for exact arch value then.  Force review of arch check logic for new
	architecture.
	(arch_has_arm_nop): Update and fix arch check logic.  Force review of
	that logic for new architecture.
	(arch_has_thumb2_nop): Remove.
	(elf32_arm_tls_relax): Use using_thumb2 instead of above function.
	(elf32_arm_final_link_relocate): Likewise but using thumb2.


^ permalink raw reply	[flat|nested] 1903+ 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:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] Fix condition.
@ 2016-06-13 17:17 sergiodj+buildbot
  2016-06-13 20:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: Use UNSUPPORTED not XFAIL for unsupported target features
@ 2016-06-13 16:49 sergiodj+buildbot
  2016-06-13 19:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] General bug fixes
@ 2016-06-13 15:47 sergiodj+buildbot
  2016-06-13 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARC] Generate DT_RELACOUNT.
@ 2016-06-13 14:52 sergiodj+buildbot
  2016-06-13 15:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Subtract GOT base only with a base register
@ 2016-06-12  4:48 sergiodj+buildbot
  2016-06-12  5:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Constify arch_type and friends
@ 2016-06-10 16:24 sergiodj+buildbot
  2016-06-10 19:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix PR rust/20110
@ 2016-06-10 16:15 sergiodj+buildbot
  2016-06-10 18:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] S/390: Dump unknown instructions according to their length.
@ 2016-06-10 11:59 sergiodj+buildbot
  2016-06-10 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-10 11:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b2cc3f6fc2c5abc0a5ac7e0f2b5fb2365e89d33f ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: b2cc3f6fc2c5abc0a5ac7e0f2b5fb2365e89d33f

S/390: Dump unknown instructions according to their length.

Unknown instructions are currently just dumped as .long 1234.  On
S/390 we can do a bit better since the instruction length is encoded
in the opcode.  That way also unknown instructions can be skipped
according to their real length.  That way we can continue correctly
after that instruction.  However, there are also some drawbacks with
that behavior when dumping data.  So for now that behavior is only
enabled for text section but even there it might mess things up when
having a literal pool embedded in the code.  Therefore I've left the
feature disabled by default and have added the -Minsnlength option to
enable it explicitely.

opcodes/ChangeLog:

2016-06-10  Andreas Krebbel  <krebbel@linux.vnet.ibm.com>

	* s390-dis.c (option_use_insn_len_bits_p): New file scope
	variable.
	(init_disasm): Handle new command line option "insnlength".
	(print_s390_disassembler_options): Mention new option in help
	output.
	(print_insn_s390): Use the encoded insn length when dumping
	unknown instructions.


^ permalink raw reply	[flat|nested] 1903+ 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:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix PR 20221 - adjust syms and relocs only if relax shrunk section.
@ 2016-06-09 16:34 sergiodj+buildbot
  2016-06-09 18:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-09 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c41dbc302c2dd87e201e4fd1d9ae3186f6e51a0 ***

Author: Denis Chertykov <chertykov@gmail.com>
Branch: master
Commit: 5c41dbc302c2dd87e201e4fd1d9ae3186f6e51a0

Fix PR 20221 - adjust syms and relocs only if relax shrunk section.

This patch fixes an edge case in linker relaxation that causes symbol
values to be computed incorrectly in the presence of align directives
in input source code.

bfd/
	* elf32-avr.c (elf32_avr_relax_delete_bytes): Adjust syms
	and relocs only if shrinking occurred.

ld/
	* testsuite/ld-avr/avr-prop-5.d: New.
	* testsuite/ld-avr/avr-prop-5.s: New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Print symbol names in comments for LDS/STS disassembly.
@ 2016-06-09 16:17 sergiodj+buildbot
  2016-06-09 17:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] sparc: add missing comment about hyperprivileged register operands
@ 2016-06-09 12:08 sergiodj+buildbot
  2016-06-09 12:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-09 12:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 337c570c5f4442459d3324c9429ad80840094015 ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 337c570c5f4442459d3324c9429ad80840094015

sparc: add missing comment about hyperprivileged register operands

include/ChangeLog:

2016-06-08  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* opcode/sparc.h: Add missing documentation for hyperprivileged
	registers in rd (%) and rs1 ($).


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] mi/mi-interp.c: Add missing braces
@ 2016-06-07 16:02 sergiodj+buildbot
  2016-06-07 17:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1aec0b6ad6eae1fa97bb1a4a47959ff204aa15a2 ***

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

mi/mi-interp.c: Add missing braces

gdb/ChangeLog:

	* mi/mi-interp.c (mi_record_changed): Add missing braces.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PowerPC VLE
@ 2016-06-07 13:02 sergiodj+buildbot
  2016-06-07 13:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-07 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14b57c7c6a53c747a8819fed3da858eae4195a0e ***

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

PowerPC VLE

VLE is an encoding, not a particular processor architecture, so it
isn't really proper to select insns based on PPC_OPCODE_VLE.  For
example
{"evaddw",  VX (4, 512), VX_MASK, PPCSPE|PPCVLE, PPCNONE, {RS, RA, RB}},
{"vaddubs", VX (4, 512), VX_MASK, PPCVEC|PPCVLE, PPCNONE, {VD, VA, VB}},
shows two insns that have the same encoding, both available with VLE.
Enabling both with VLE means we can't disassemble the second variant
even if -Maltivec is given rather than -Mspe.  Also, we don't check
user assembly against the processor type as well as we could.

Another problem is that when using the VLE encoding, insns from the
main ppc opcode table are not available, except those using opcode 4
and 31.  Correcting this revealed two errors in the ld testsuite,
use of "nop" and "rfmci" when -mvle.

This patch fixes those problems in the opcode table, and removes
PPCNONE.  I find a plain 0 distracts less from other values.

In addition, I've implemented code to recognize some machine values
from the apuinfo note present in ppc32 objects.  It's not a complete
disambiguation since we're lacking info to detect newer chips, but
what we have should help with disassembly.

include/
	* elf/ppc.h (APUINFO_SECTION_NAME, APUINFO_LABEL, PPC_APUINFO_ISEL,
	PPC_APUINFO_PMR, PPC_APUINFO_RFMCI, PPC_APUINFO_CACHELCK,
	PPC_APUINFO_SPE, PPC_APUINFO_EFS, PPC_APUINFO_BRLOCK,
	PPC_APUINFO_VLE: Define.
opcodes/
	* ppc-dis.c (ppc_opts): Delete extraneous parentheses.  Default
	cpu for "vle" to e500.
	* ppc-opc.c (ALLOW8_SPRG): Remove PPC_OPCODE_VLE.
	(NO371, PPCSPE, PPCISEL, PPCEFS, MULHW, DCBT_EO): Likewise.
	(PPCNONE): Delete, substitute throughout.
	(powerpc_opcodes): Remove PPCVLE from "flags".  Add to "deprecated"
	except for major opcode 4 and 31.
	(vle_opcodes <se_rfmci>): Add PPCRFMCI to flags.
bfd/
	* cpu-powerpc.c (powerpc_compatible): Allow bfd_mach_ppc_vle entry
	to match other 32-bit archs.
	* elf32-ppc.c (_bfd_elf_ppc_set_arch): New function.
	(ppc_elf_object_p): Call it.
	(ppc_elf_special_sections): Use APUINFO_SECTION_NAME.  Fix
	overlong line.
	(APUINFO_SECTION_NAME, APUINFO_LABEL): Don't define here.
	* elf64-ppc.c (ppc64_elf_object_p): Call _bfd_elf_ppc_set_arch.
	* bfd-in.h (_bfd_elf_ppc_at_tls_transform,
	_bfd_elf_ppc_at_tprel_transform): Move to..
	* elf-bfd.h: ..here.
	(_bfd_elf_ppc_set_arch): Declare.
	* bfd-in2.h: Regenerate.
gas/
	* config/tc-ppc.c (PPC_APUINFO_ISEL, PPC_APUINFO_PMR,
	PPC_APUINFO_RFMCI, PPC_APUINFO_CACHELCK, PPC_APUINFO_SPE,
	PPC_APUINFO_EFS, PPC_APUINFO_BRLOCK, PPC_APUINFO_VLE): Don't define.
	(ppc_setup_opcodes): Check vle disables powerpc_opcodes overridden
	by vle_opcodes, and that vle flag doesn't enable opcodes.  Don't
	add vle_opcodes twice.
	(ppc_cleanup): Use APUINFO_SECTION_NAME and APUINFO_LABEL.
ld/
	* testsuite/ld-powerpc/apuinfo1.s: Delete nop.
	* testsuite/ld-powerpc/apuinfo-vle2.s: New.
	* testsuite/ld-powerpc/powerpc.exp: Use apuinfo-vle2.s.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Frame static link: Handle null pointer.
@ 2016-06-07 11:49 sergiodj+buildbot
  2016-06-07 12:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add method/format information to =record-started
@ 2016-06-06 21:21 sergiodj+buildbot
  2016-06-06 22:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 20:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Handle indirect branches for AMD64 and Intel64
@ 2016-06-03 23:15 sergiodj+buildbot
  2016-06-04  0:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-06-03 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07f5af7d3c635234284e7a0f7dd7a410b1628b8b ***

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

Handle indirect branches for AMD64 and Intel64

AMD64 spec and Intel64 spec differ in indirect branches in 64-bit mode.
AMD64 supports indirect branches with 16-bit address via the data size
prefix while the data size prefix is ignored by Intel64.

gas/

	PR binutis/18386
	* testsuite/gas/i386/i386.exp: Run x86-64-branch-4.
	* testsuite/gas/i386/x86-64-branch.d: Updated.
	* testsuite/gas/i386/ilp32/x86-64-branch.d: Likewise.
	* testsuite/gas/i386/x86-64-branch-4.l: New file.
	* testsuite/gas/i386/x86-64-branch-4.s: Likewise.

opcodes/

	PR binutis/18386
	* i386-dis.c (indirEv): Replace stack_v_mode with indir_v_mode.
	(indir_v_mode): New.
	Add comments for '&'.
	(reg_table): Replace "{T|}" with "{&|}" on call and jmp.
	(putop): Handle '&'.
	(intel_operand_size): Handle indir_v_mode.
	(OP_E_register): Likewise.
	* i386-opc.tbl: Mark 64-bit indirect call/jmp as AMD64.  Add
	64-bit indirect call/jmp for AMD64.
	* i386-tbl.h: Regenerated


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR python/18984
@ 2016-06-02 19:39 sergiodj+buildbot
  2016-06-02 20:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Replace data32 with data16 in comments
@ 2016-06-02 14:30 sergiodj+buildbot
  2016-06-02 15:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add new Serbian translation for the bfd library.
@ 2016-06-01 16:03 sergiodj+buildbot
  2016-06-02  1:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 15:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 21:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add emit_less_unsigned test in trace-condition.exp
@ 2016-05-30 17:22 sergiodj+buildbot
  2016-05-30 20:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] PR 15231: import bare DW_TAG_lexical_block
@ 2016-05-30 12:38 sergiodj+buildbot
  2016-05-30 14:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add dependencies to configure rule
@ 2016-05-28 13:19 sergiodj+buildbot
  2016-05-29 15:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-28 13:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0597bdc443005c70f0fd474279098ee17db882eb ***

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

Add dependencies to configure rule

	* Makefile.tpl (configure): Depend on m4 files included.
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Update x86 CPU_XXX_FLAGS handling
@ 2016-05-27 17:19 sergiodj+buildbot
  2016-05-28 17:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1848e567343e9c50979453463f34e0a55ba892eb ***

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

Update x86 CPU_XXX_FLAGS handling

Support defining CPU_XXX_FLAGS with other CPU_XXX_FLAGS.  Update
CPU_XXX_FLAGS to enable more bits like x87 and SYSCALL.  Don't enable
MMX when enabling SSE, AVX or AVX512.  Don't disable AVX nor AVX512 when
disabling SSE.  Don't disable AVX512 when disabling AVX.  Disable F16C,
FMA, FMA4 and XOP when disabling AVX.  Add 87, no287, no387, no687,
nosse2, nosse3, nossse3, nosse4.1, nosse4.2, nosse4 and noavx2 directives
to x86 assembler.

TODO: Add more .noXXX, like .noavx512f, directives to x86 assembler.

gas/

	PR gas/20145
	* config/tc-i386.c (cpu_arch): Add 687.
	(cpu_noarch): Add no287, no387, no687, nosse2, nosse3, nossse3,
	nosse4.1, nosse4.2, nosse4 and noavx2.
	(parse_real_register): Check cpuregmmx instead of cpummx for MMX
	register.  Check cpuregxmm instead of cpusse for XMM register.
	Check cpuregymm instead of cpuavx for YMM register.  Check
	cpuregzmm/cpuregmask instead of cpuavx512f for ZMMM/mask register.
	* doc/c-i386.texi: Mention 687, no287, no387, no687, nosse2,
	nosse3, nossse3, nosse4.1, nosse4.2, nosse4 and noavx2.
	* testsuite/gas/i386/arch-10-prefetchw.d (as): Add mmx.
	* testsuite/gas/i386/arch-10.d (as): Likewise.
	* testsuite/gas/i386/arch-11.s: Add ".arch .mmx".
	* testsuite/gas/i386/i386.exp: Pass mmx to assembler for
	arch-10-3 and arch-10-4.  Run no87-3, nosse-4, nosse-5, noavx-3
	and noavx-4.
	* testsuite/gas/i386/no87-3.l: New file.
	* testsuite/gas/i386/no87-3.s: Likewise.
	* testsuite/gas/i386/noavx-3.l: Likewise.
	* testsuite/gas/i386/noavx-3.s: Likewise.
	* testsuite/gas/i386/noavx-4.d: Likewise.
	* testsuite/gas/i386/noavx-4.s: Likewise.
	* testsuite/gas/i386/nosse-4.l: Likewise.
	* testsuite/gas/i386/nosse-4.s: Likewise.
	* testsuite/gas/i386/nosse-5.d: Likewise.
	* testsuite/gas/i386/nosse-5.s: Likewise.

opcodes/

	PR gas/20145
	* i386-gen.c (cpu_flag_init): Update CPU_XXX_FLAGS.  Remove
	CpuMMX from CPU_SSE_FLAGS.  Remove AVX and AVX512 bits from
	CPU_ANY_SSE_FLAGS.  Remove AVX512 bits from CPU_ANY_AVX_FLAGS.
	Add CPU_XSAVE_FLAGS to CPU_XSAVEOPT_FLAGS, CPU_XSAVE_FLAGS and
	CpuXSAVEC.  Add CPU_AVX_FLAGS to CpuF16C.  Remove CpuMMX from
	CPU_AVX512F_FLAGS, CPU_AVX512CD_FLAGS, CPU_AVX512ER_FLAGS,
	CPU_AVX512PF_FLAGS, CPU_AVX512DQ_FLAGS and CPU_AVX512BW_FLAGS.
	Add CPU_SSE2_FLAGS to CPU_SHA_FLAGS.   Add CPU_ANY_287_FLAGS,
	CPU_ANY_387_FLAGS, CPU_ANY_687_FLAGS, CPU_ANY_SSE2_FLAGS,
	CPU_ANY_SSE3_FLAGS, CPU_ANY_SSSE3_FLAGS, CPU_ANY_SSE4_1_FLAGS,
	CPU_ANY_SSE4_2_FLAGS and CPU_ANY_AVX2_FLAGS.  Enable CpuRegMMX
	for MMX.  Enable CpuRegXMM for SSE, AVX and AVX512.  Enable
	CpuRegYMM for AVX and AVX512VL,  Enable CpuRegZMM and
	CpuRegMask for AVX512.
	(cpu_flags): Add CpuRegMMX, CpuRegXMM, CpuRegYMM, CpuRegZMM
	and CpuRegMask.
	(set_bitfield_from_cpu_flag_init): New function.
	(set_bitfield): Remove const on f.  Call
	set_bitfield_from_cpu_flag_init to handle CPU_XXX_FLAGS.
	* i386-opc.h (CpuRegMMX): New.
	(CpuRegXMM): Likewise.
	(CpuRegYMM): Likewise.
	(CpuRegZMM): Likewise.
	(CpuRegMask): Likewise.
	(i386_cpu_flags): Add cpuregmmx, cpuregxmm, cpuregymm, cpuregzmm
	and cpuregmask.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64
@ 2016-05-27 15:15 sergiodj+buildbot
  2016-05-28 15:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Correct CpuMax in i386-opc.h
@ 2016-05-27 14:08 sergiodj+buildbot
  2016-05-28  8:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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-28  2:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_PTR
@ 2016-05-27 12:46 sergiodj+buildbot
  2016-05-27 19:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-27 12:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac775bf4d35b7a2d5715e0ccf3d648d4670213fd ***

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

gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_PTR

Assume that we have a C program like this:

  struct foo_type
  {
    int var;
  } foo;

  struct foo_type *foo_ptr = &foo;

  int
  main ()
  {
    return foo_ptr->var;
  }

Then GDB should be able to evaluate the following, however, it currently
does not:

  (gdb) start
  ...
  (gdb) whatis &(foo_ptr->var)
  Attempt to take address of value not located in memory.

The problem is that in EVAL_AVOID_SIDE_EFFECTS mode,
eval.c:evaluate_subexp_standard always returns a not_lval value as the
result for a STRUCTOP_PTR operation. As a consequence, the rest of
the code believes that one cannot take the address of the returned
value.

This patch fixes STRUCTOP_PTR handling so that the VALUE_LVAL
attribute for the returned value is properly initialized.  After this
change, the above session becomes:

  (gdb) start
  ...
  (gdb) whatis &(foo_ptr->var)
  type = int *

This commit is largely the same as commit 2520f728b710 (Forward
VALUE_LVAL when avoiding side effects for STRUCTOP_STRUCT) but applied
to STRUCTOP_PTR rather than STRUCTOP_STRUCT.  Both of these commits are
building on top of commit ac1ca910d74d (Fixes for PR exp/15364).

gdb/ChangeLog:

	* eval.c (evaluate_subexp_standard): If EVAL_AVOID_SIDE_EFFECTS
	mode, forward the VALUE_LVAL attribute to the returned value in
	the STRUCTOP_PTR case.

gdb/testsuite/ChangeLog:

	* gdb.base/whatis.c: Extend the test case.
	* gdb.base/whatis.exp: Add additional tests.


^ permalink raw reply	[flat|nested] 1903+ 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:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] MIPS/BFD: Report `bfd_reloc_outofrange' errors as such
@ 2016-05-25 20:20 sergiodj+buildbot
  2016-05-25 23:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Reimplement .no87/.nommx/.nosse/.noavx directives
@ 2016-05-25 17:39 sergiodj+buildbot
  2016-05-25 18:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 10:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] add nb_inplace_divide for python 2
@ 2016-05-24 16:24 sergiodj+buildbot
  2016-05-24 22:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 20:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 17:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Linux native thread create/exit events support
@ 2016-05-24 14:06 sergiodj+buildbot
  2016-05-24 15:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-24 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa01bd3689d204ce3d657cf7eb17b8343d79a080 ***

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

Linux native thread create/exit events support

A following patch (fix for gdb/19828) makes linux-nat.c add threads to
GDB's thread list earlier in the "attach" sequence, and that causes a
surprising regression on
gdb.threads/attach-many-short-lived-threads.exp on my machine.  The
extra "thread x exited" handling and traffic slows down that test
enough that GDB core has trouble keeping up with new threads that are
spawned while trying to stop existing ones.

I saw the exact same issue with remote/gdbserver a while ago and fixed
it in 65706a29bac5 (Remote thread create/exit events) so part of the
fix here is the exact same -- add support for thread created events to
gdb/linux-nat.c.  infrun.c:stop_all_threads enables those events when
it tries to stop threads, which ensures that new threads never get a
chance to themselves start new threads, thus fixing the race.

gdb/
2016-05-24  Pedro Alves  <palves@redhat.com>

	PR gdb/19828
	* linux-nat.c (report_thread_events): New global.
	(linux_handle_extended_wait): Report
	TARGET_WAITKIND_THREAD_CREATED if thread event reporting is
	enabled.
	(wait_lwp, linux_nat_filter_event): Report all thread exits if
	thread event reporting is enabled.  Remove comment.
	(filter_exit_event): New function.
	(linux_nat_wait_1): Use it.
	(linux_nat_thread_events): New function.
	(linux_nat_add_target): Install it as target_thread_events method.


^ permalink raw reply	[flat|nested] 1903+ 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:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Skip unwritable frames in command "finish"
@ 2016-05-23 17:14 sergiodj+buildbot
  2016-05-23 19:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-23 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7eb895307f53af3435440d3fe67c0e4e679d99b2 ***

Author: Yao Qi <yao.qi@arm.com>
Branch: master
Commit: 7eb895307f53af3435440d3fe67c0e4e679d99b2

Skip unwritable frames in command "finish"

Nowadays, GDB can't insert breakpoint on the return address of the
exception handler on ARM M-profile, because the address is a magic
one 0xfffffff9,

 (gdb) bt
 #0  CT32B1_IRQHandler () at ../src/timer.c:67
 #1  <signal handler called>
 #2  main () at ../src/timer.c:127

(gdb) info frame
Stack level 0, frame at 0x200ffa8:
 pc = 0x4ec in CT32B1_IRQHandler (../src/timer.c:67); saved pc = 0xfffffff9
 called by frame at 0x200ffc8
 source language c.
 Arglist at 0x200ffa0, args:
 Locals at 0x200ffa0, Previous frame's sp is 0x200ffa8
 Saved registers:
  r7 at 0x200ffa0, lr at 0x200ffa4

(gdb) x/x 0xfffffff9
0xfffffff9:     Cannot access memory at address 0xfffffff9

(gdb) finish
Run till exit from #0  CT32B1_IRQHandler () at ../src/timer.c:67
Ed:15: Target error from Set break/watch: Et:96: Pseudo-address (0xFFFFFFxx) for EXC_RETURN is invalid (GDB error?)

Warning:
Cannot insert hardware breakpoint 0.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.

even some debug probe can't set hardware breakpoint on the magic
address too,

(gdb) hbreak *0xfffffff9
Hardware assisted breakpoint 2 at 0xfffffff9
(gdb) c
Continuing.
Ed:15: Target error from Set break/watch: Et:96: Pseudo-address (0xFFFFFFxx) for EXC_RETURN is invalid (GDB error?)

Warning:
Cannot insert hardware breakpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

Command aborted.

The problem described above is quite similar to PR 8841, in which GDB
can't set breakpoint on signal trampoline, which is mapped to a read-only
page by kernel.  The rationale of this patch is to skip "unwritable"
frames when looking for caller frames in command "finish", and a new
gdbarch method code_of_frame_writable is added.  This patch fixes
the problem on ARM cortex-m target, but it can be used to fix
PR 8841 too.

gdb:

2016-05-10  Yao Qi  <yao.qi@arm.com>

	* arch-utils.c (default_code_of_frame_writable): New function.
	* arch-utils.h (default_code_of_frame_writable): Declare.
	* arm-tdep.c (arm_code_of_frame_writable): New function.
	(arm_gdbarch_init): Install gdbarch method
	code_of_frame_writable if the target is M-profile.
	* frame.c (skip_unwritable_frames): New function.
	* frame.h (skip_unwritable_frames): Declare.
	* gdbarch.sh (code_of_frame_writable): New.
	* gdbarch.c, gdbarch.h: Re-generated.
	* infcmd.c (finish_command): Call skip_unwritable_frames.


^ permalink raw reply	[flat|nested] 1903+ 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:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Set sh_entsize for .init_array and similar.
@ 2016-05-19 15:18 sergiodj+buildbot
  2016-05-19 15:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix invalid implicit conversions from void *
@ 2016-05-19 13:44 sergiodj+buildbot
  2016-05-19 14:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove unsupported `am34-*-linux*' target triplet
@ 2016-05-19 10:25 sergiodj+buildbot
  2016-05-19 12:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix powerpc subis range
@ 2016-05-19  5:57 sergiodj+buildbot
  2016-05-19 10:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix ppc64le S-record test fail
@ 2016-05-19  5:14 sergiodj+buildbot
  2016-05-19  9:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Updated Swedish translations for bfd and binutils
@ 2016-05-18 12:06 sergiodj+buildbot
  2016-05-19  3:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Rename OP_F90_RANGE to OP_RANGE.
@ 2016-05-18  0:39 sergiodj+buildbot
  2016-05-18 23:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add self-test framework to gdb
@ 2016-05-17 21:52 sergiodj+buildbot
  2016-05-17 22:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Update gdb test suite for Rust
@ 2016-05-17 21:36 sergiodj+buildbot
  2016-05-18 13:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] LD/ELF: Unify STB_GNU_UNIQUE handling
@ 2016-05-17 11:40 sergiodj+buildbot
  2016-05-17 12:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] ld -z combreloc elf_link_sort_relocs
@ 2016-05-13  5:36 sergiodj+buildbot
  2016-05-13  5:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-13  5:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8e44c6d168f8e68b7bbb1119065e0059a16fe34 ***

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

ld -z combreloc elf_link_sort_relocs

A linker script may put .rela.plt in with other .rela.dyn relocs.
The change to elf_reloc_type_class puts any PLT relocs last.  This
patch makes the input section layout better match the sorted relocs.

	* elflink.c (elf_link_sort_relocs): Wrap overlong lines.  Fix
	octets_per_byte.  Put dynamic .rela.plt last in link orders.
	Assign output_offset for reloc sections rather than writing
	sorted relocs from block corresponding to output_offset.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR symtab/19999 gdb unable to resolve vars with fission+PIE
@ 2016-05-12 16:48 sergiodj+buildbot
  2016-05-12 17:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-12 16:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ddd5a6cd692ca8c4041d9fb64cbb4e0585d4aa1 ***

Author: Doug Evans <dje@google.com>
Branch: master
Commit: 8ddd5a6cd692ca8c4041d9fb64cbb4e0585d4aa1

PR symtab/19999 gdb unable to resolve vars with fission+PIE

gdb/ChangeLog:

	* dwarf2loc.c (dwarf2_find_location_expression): For DWO files still
	add base_offset.

gdb/testsuite/ChangeLog:

	* lib/dwarf.exp (build_executable_from_fission_assembler): Pass
	$options when building executable.
	* gdb.dwarf2/fission-loclists-pie.c: New file.
	* gdb.dwarf2/fission-loclists-pie.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ld -z combreloc reloc sorting
@ 2016-05-12 15:11 sergiodj+buildbot
  2016-05-12 15:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  2:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Factor our stub creation in ARM backend
@ 2016-05-10 17:37 sergiodj+buildbot
  2016-05-10 19:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] opcodes,gas: sparc: fix mnemonic of faligndatai
@ 2016-05-09 11:17 sergiodj+buildbot
  2016-05-09 11:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Regenerate configure
@ 2016-05-09  8:38 sergiodj+buildbot
  2016-05-09  9:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Define elf_backend_add_symbol_hook for Intel MCU
@ 2016-05-06 15:44 sergiodj+buildbot
  2016-05-06 16:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add support for FMLA (by element) to AArch64 sim.
@ 2016-05-06  9:55 sergiodj+buildbot
  2016-05-06 10:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-06  9:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd7ed446fbee07c70ebc7d1e92f1ece665d7fc64 ***

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

Add support for FMLA (by element) to AArch64 sim.

	* simulator.c (do_FMLA_by_element): New function.
	(do_vec_op2): Call it.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Cache the section contents in x86 check_relocs
@ 2016-05-05 11:45 sergiodj+buildbot
  2016-05-05 11:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [spu] Fix C++ build problems
@ 2016-05-05  0:11 sergiodj+buildbot
  2016-05-05  0:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 17:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix gdb/python/python.c use-after-free
@ 2016-05-03 12:30 sergiodj+buildbot
  2016-05-03 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-03 12:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86f1abec458df24ea7d4a38a7b3e21861c5b9bd8 ***

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

Fix gdb/python/python.c use-after-free

Valgrind shows:

 ==26964== Invalid read of size 1
 ==26964==    at 0x6E14100: __GI_strcmp (strcmp.S:180)
 ==26964==    by 0x6DB55AA: setlocale (setlocale.c:238)
 ==26964==    by 0x4E0455: _initialize_python() (python.c:1731)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)
 ==26964==  Address 0x81d30a0 is 0 bytes inside a block of size 181 free'd
 ==26964==    at 0x4C29CF0: free (vg_replace_malloc.c:530)
 ==26964==    by 0x6DB5B65: setname (setlocale.c:201)
 ==26964==    by 0x6DB5B65: setlocale (setlocale.c:388)
 ==26964==    by 0x4E037F: _initialize_python() (python.c:1712)
 ==26964==    by 0x786731: initialize_all_files() (init.c:319)
 ==26964==    by 0x72EF0A: gdb_init(char*) (top.c:1929)
 ==26964==    by 0x60BCAC: captured_main(void*) (main.c:863)
 ==26964==    by 0x606AD5: catch_errors(int (*)(void*), void*, char*, return_mask) (exceptions.c:234)
 ==26964==    by 0x60C608: gdb_main(captured_main_args*) (main.c:1165)
 ==26964==    by 0x40CAEC: main (gdb.c:32)

The problem is doing this:

  oldloc = setlocale (LC_ALL, NULL);
  setlocale (LC_ALL, "");
  ...
  setlocale (LC_ALL, oldloc);

I.e., the second setlocale call frees 'oldloc'.

>From http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html :

 "The returned string pointer might be invalidated or the string
 content might be overwritten by a subsequent call to setlocale()."

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

	PR python/20037
	* python/python.c (_initialize_python) [IS_PY3K]: xstrdup/xfree
	oldloc.


^ permalink raw reply	[flat|nested] 1903+ 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 15:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix "-Wl,--dynamic-list" gdb/configure test
@ 2016-05-03  9:56 sergiodj+buildbot
  2016-05-03 12:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix startup on MS-Windows when 'gdb.ini' is found in $HOME
@ 2016-05-02 17:09 sergiodj+buildbot
  2016-05-02 17:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-05-02 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1270fac69d2f7e89161ccb780ce3b17466da34ea ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 1270fac69d2f7e89161ccb780ce3b17466da34ea

Fix startup on MS-Windows when 'gdb.ini' is found in $HOME

	* windows-nat.c (_initialize_check_for_gdb_ini): Fix off-by-one
	error in allocation of space for "$HOME/.gdbinit" string.  This
	caused GDB to abort on startup whenever a '~/gdb.ini' file was
	actually found, because xsnprintf would hit an assertion
	violation.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Set interpreter in x86 create_dynamic_sections
@ 2016-04-29 16:02 sergiodj+buildbot
  2016-04-29 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] X86-64: Set check_relocs_failed on error
@ 2016-04-29 12:01 sergiodj+buildbot
  2016-04-29 12:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove need_step_over from struct lwp_info
@ 2016-04-28 11:08 sergiodj+buildbot
  2016-04-28 11:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Rename gdb_load_shlibs to gdb_load_shlib
@ 2016-04-27 22:52 sergiodj+buildbot
  2016-04-27 23:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-27 22:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9019901f830e58b0b16793ffe6e70b9afd26ea6 ***

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

Rename gdb_load_shlibs to gdb_load_shlib

Rename gdb_load_shlibs to gdb_load_shlib to reflect that it can only
load a single shlib at the time.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_load_shlibs): Rename to...
	(gdb_load_shlib): ... this.
	* gdb.arch/ftrace-insn-reloc.exp: Adjust gdb_load_shlibs ->
	gdb_load_shlib.
	* gdb.base/catch-load.exp (one_catch_load_test): Likewise.
	* gdb.base/ctxobj.exp: Likewise.
	* gdb.base/dprintf-pending.exp: Likewise.
	* gdb.base/dso2dso.exp: Likewise.
	* gdb.base/fixsection.exp: Likewise.
	* gdb.base/gcore-relro.exp: Likewise.
	* gdb.base/gdb1555.exp: Likewise.
	* gdb.base/global-var-nested-by-dso.exp: Likewise.
	* gdb.base/gnu-ifunc.exp: Likewise.
	* gdb.base/hbreak-in-shr-unsupported.exp: Likewise.
	* gdb.base/jit-so.exp (one_jit_test): Likewise.
	* gdb.base/pending.exp: Likewise.
	* gdb.base/print-file-var.exp: Likewise.
	* gdb.base/print-symbol-loading.exp: Likewise.
	* gdb.base/shlib-call.exp: Likewise.
	* gdb.base/shreloc.exp: Likewise.
	* gdb.base/so-impl-ld.exp: Likewise.
	* gdb.base/solib-disc.exp: Likewise.
	* gdb.base/solib-nodir.exp: Likewise.
	* gdb.base/solib-overlap.exp: Likewise.
	* gdb.base/solib-symbol.exp: Likewise.
	* gdb.base/solib-weak.exp (do_test): Likewise.
	* gdb.base/sym-file.exp: Likewise.
	* gdb.base/symtab-search-order.exp: Likewise.
	* gdb.base/type-opaque.exp: Likewise.
	* gdb.base/unload.exp: Likewise.
	* gdb.base/watchpoint-solib.exp: Likewise.
	* gdb.compile/compile.exp: Likewise.
	* gdb.cp/gdb2384.exp: Likewise.
	* gdb.cp/infcall-dlopen.exp: Likewise.
	* gdb.cp/re-set-overloaded.exp: Likewise.
	* gdb.fortran/library-module.exp: Likewise.
	* gdb.opt/solib-intra-step.exp: Likewise.
	* gdb.python/py-finish-breakpoint.exp: Likewise.
	* gdb.python/py-shared.exp: Likewise.
	* gdb.reverse/solib-precsave.exp: Likewise.
	* gdb.reverse/solib-reverse.exp: Likewise.
	* gdb.server/solib-list.exp: Likewise.
	* gdb.threads/dlopen-libpthread.exp: Likewise.
	* gdb.threads/tls-shared.exp: Likewise.
	* gdb.threads/tls-so_extern.exp: Likewise.
	* gdb.trace/change-loc.exp: Likewise.
	* gdb.trace/ftrace-lock.exp: Likewise.
	* gdb.trace/ftrace.exp: Likewise.
	* gdb.trace/mi-tracepoint-changed.exp (test_reconnect): Likewise.
	* gdb.trace/pending.exp: Likewise.
	* gdb.trace/range-stepping.exp: Likewise.
	* gdb.trace/strace.exp (strace_remove_socket): Likewise.
	(strace_info_marker): Likewise.
	(strace_probe_marker): Likewise.
	(strace_trace_on_same_addr): Likewise.
	(strace_trace_on_diff_addr): Likewise.
	* gdb.trace/trace-break.exp: Likewise.
	* gdb.trace/trace-condition.exp: Likewise.
	* gdb.trace/trace-mt.exp: Likewise.


^ permalink raw reply	[flat|nested] 1903+ 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 19:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 18:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 13:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] fort_dyn_array: Support evaluation of dynamic elements inside arrays.
@ 2016-04-26 15:16 sergiodj+buildbot
  2016-04-26 15:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-26 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f07e298b16e6419a11f9e9d75b15658e42ea775 ***

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

fort_dyn_array: Support evaluation of dynamic elements inside arrays.

Resolve type of an array's element to be printed in case it is dynamic.
Otherwise we don't use the correct boundaries nor the right location.

Before:
  ptype fivearr(1)
  type = Type five
      Type one
          integer(kind=4) :: ivla(34196784:34196832,34197072:34197120,34197360:34197408)
      End Type one :: tone
  End Type five

After:
  ptype fivearr(1)
  type = Type five
      Type one
          integer(kind=4) :: ivla(2,4,6)
      End Type one :: tone
  End Type five

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

gdb/Changelog:
	* valarith.c (value_address): Resolve dynamic types.

gdb/testsuite/Changelog:
	* gdb.fortran/vla-type.f90: Add test for static and dynamic arrays
	of dynamic types.
	* gdb.fortran/vla-type.exp: Add test for static and dynamic arrays
	of dynamic types.


^ permalink raw reply	[flat|nested] 1903+ 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:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  9:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Choose TARGET_OBJECT_STACK_MEMORY and TARGET_OBJECT_MEMORY in read_value_memory
@ 2016-04-22 18:06 sergiodj+buildbot
  2016-04-22 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 18:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d7e9d3b8dbbf46a0cd5dc4f6341c1f9eb8cd6ae ***

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

Choose TARGET_OBJECT_STACK_MEMORY and TARGET_OBJECT_MEMORY in read_value_memory

Before this patch
https://sourceware.org/ml/gdb-patches/2014-02/msg00709.html
read_value_memory checks parameter 'stack', and call read_stack or
read_memory respectively.  However, 'stack' is not checked and
TARGET_OBJECT_MEMORY is always used in target_xfer_partial, which is
a mistake in the patch above.

This patch checks parameter 'stack', and choose TARGET_OBJECT_MEMORY
or TARGET_OBJECT_STACK_MEMORY accordingly.

gdb:

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

	* valops.c (read_value_memory): New local variable 'stack'.
	Set it to either TARGET_OBJECT_STACK_MEMORY or
	TARGET_OBJECT_MEMORY.


^ permalink raw reply	[flat|nested] 1903+ 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 16:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 16:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARM] Clear reserved bits in CPSR
@ 2016-04-22 15:39 sergiodj+buildbot
  2016-04-22 15:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Joel Brobecker stepping down as AIX Maintainer
@ 2016-04-22 14:40 sergiodj+buildbot
  2016-04-22 14:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Tweak gdb.reverse/step-precsave.exp and gdb.reverse/step-reverse.exp
@ 2016-04-22 12:23 sergiodj+buildbot
  2016-04-22 12:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a7e075c3fdb862d1a9632fc3500c6e5111013fc ***

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

Tweak gdb.reverse/step-precsave.exp and gdb.reverse/step-reverse.exp

I see the following test fail in arm-linux with -marm and -fomit-frame-pointer,

 step
 callee () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c:27
 27      }                       /* RETURN FROM CALLEE */
 (gdb) step
 main () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c:58
 58         callee();    /* STEP INTO THIS CALL */
 (gdb) FAIL: gdb.reverse/step-precsave.exp: reverse step into fn call

As we can see, the "step" has already stepped into the function callee,
but in the last line.  The second "step" attempts to step to function
body, but it goes out of callee, which isn't expected.

The program is compiled with -marm and -fomit-frame-pointer, the
function callee is prologue-less, because nothing needs to be saved
on stack,

(gdb) disassemble callee
Dump of assembler code for function callee:
   0x00010680 <+0>:	movw	r3, #2364	; 0x93c
   0x00010684 <+4>:	movt	r3, #2
   0x00010688 <+8>:	ldr	r3, [r3]
   0x0001068c <+12>:	add	r2, r3, #1
   0x00010690 <+16>:	movw	r3, #2364	; 0x93c
   0x00010694 <+20>:	movt	r3, #2
   0x00010698 <+24>:	str	r2, [r3]
   0x0001069c <+28>:	mov	r3, #0
   0x000106a0 <+32>:	mov	r0, r3
   0x000106a4 <+36>:	bx	lr

program stops at the 0x106a0 (passed the epilogue) after the first
"step".  When second "step" is executed, the stepping range is
[0x10680-0x106a0], which starts from the first instruction of function
callee (because it doesn't have prologue).

infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=0, current thread [LWP 2461] at 0x1069c^M
infrun: prepare_to_wait^M
infrun: target_wait (-1.0.0, status) =^M
infrun:   2461.2461.0 [LWP 2461],^M
infrun:   status->kind = stopped, signal = GDB_SIGNAL_TRAP^M
infrun: TARGET_WAITKIND_STOPPED^M
infrun: stop_pc = 0x10698^M
infrun: stepping inside range [0x10680-0x106a0]

When program goes out of the range, it stops at the caller of callee,
and test fails.  IOW, if function callee has prologue, the stepping
range won't start from the first instruction of the function, and
program stops at the prologue and test passes.

IMO, GDB does nothing wrong, but test shouldn't expect the program
stops in callee after the second "step".  I decide to fix test rather
than GDB.  In this patch, I change to test to do one "step", and check
the program is still in callee, then, do multiple "step" until program
goes out of the callee.

gdb/testsuite:

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

	* gdb.reverse/step-precsave.exp: Do one step and test program
	stops in "callee" and do multiple steps until program goes out
	of "callee".
	* gdb.reverse/step-reverse.exp: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] New test case gdb.trace/signal.exp
@ 2016-04-22 11:21 sergiodj+buildbot
  2016-04-22 11:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-22 11:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c5dc57fcf2f543b7b8bdd2c3cfdabc74c39041b ***

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

New test case gdb.trace/signal.exp

This is to test whether GDBserver deliver signal to the inferior while
doing the step over.  Nowadays, GDBserver doesn't deliver signal, so
there won't be spurious collection, however, if GDBserver does deliver
signal, there might be spurious collection.

gdb/testsuite:

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

	* gdb.trace/signal.c: New file.
	* gdb.trace/signal.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Exclude linker created file from dynobj
@ 2016-04-22  5:18 sergiodj+buildbot
  2016-04-22  7:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Switch gdb's TRY/CATCH to sjlj again
@ 2016-04-21 16:36 sergiodj+buildbot
  2016-04-21 17:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix AIX gdb build with C++ compiler
@ 2016-04-21 13:06 sergiodj+buildbot
  2016-04-21 13:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix s390 GNU/Linux gdb and gdbserver builds
@ 2016-04-21 11:15 sergiodj+buildbot
  2016-04-21 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Add missing sentinel 'char *' casts in concat/reconcat calls
@ 2016-04-21 10:39 sergiodj+buildbot
  2016-04-21 11:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 22:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Build GDB as a C++ program by default
@ 2016-04-20 22:27 sergiodj+buildbot
  2016-04-20 23:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a23585089d7ba710b238d3d1ab3d34320afa48d0 ***

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

Build GDB as a C++ program by default

This makes --enable-build-with-cxx be "yes" by default.

One must now configure with --enable-build-with-cxx=no in order to
build with a C compiler.

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

	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Default to yes.
	* configure: Renegerate.

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

	* configure: Renegerate.


^ permalink raw reply	[flat|nested] 1903+ 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:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Include arch/arm-linux.h in aarch32-linux-nat.c
@ 2016-04-20 14:26 sergiodj+buildbot
  2016-04-20 14:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-20 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8cef59a2e32816d5fbbe1cfebfca3e3d6abd4d33 ***

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

Include arch/arm-linux.h in aarch32-linux-nat.c

Fix the compilation failure by including arch/arm-linux.h in
aarch32-linux-nat.c.

gdb:

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

	* aarch32-linux-nat.c: Include "arch/arm-linux.h".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Call _bfd_elf_create_ifunc_sections only for ifunc
@ 2016-04-20 13:35 sergiodj+buildbot
  2016-04-20 13:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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  5:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] opcodes/arc: Add yet more nps instructions
@ 2016-04-19 22:36 sergiodj+buildbot
  2016-04-19 23:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-19 22:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 537aefaf18444430df8126b474cf11ff7201b4c6 ***

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

opcodes/arc: Add yet more nps instructions

Add some more arc/nps400 instructions and the associated operands.
There's also a test added into the assembler.

gas/ChangeLog:

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

include/ChangeLog:

	* opcode/arc.h (MAX_INSN_ARGS): Increase 6 to 8.

opcodes/ChangeLog:

	* arc-nps400-tbl.h: Add addb, subb, adcb, sbcb, andb, xorb, orb,
	fxorb, wxorb, shlb, shrb, notb, cntbb, div, mod, divm, and qcmp
	instructions.
	* arc-opc.c (insert_nps_bitop_size): Delete.
	(extract_nps_bitop_size): Delete.
	(MAKE_SRC_POS_INSERT_EXTRACT_FUNCS): Define, and use.
	(extract_nps_qcmp_m3): Define.
	(extract_nps_qcmp_m2): Define.
	(extract_nps_qcmp_m1): Define.
	(arc_flag_operands): Add F_NPS_SX, F_NPS_AR, F_NPS_AL.
	(arc_flag_classes): Add C_NPS_SX, C_NPS_AR_AL
	(arc_operands): Add NPS_SRC2_POS, NPS_SRC1_POS, NPS_ADDB_SIZE,
	NPS_ANDB_SIZE, NPS_FXORB_SIZ, NPS_WXORB_SIZ, NPS_R_XLDST,
	NPS_DIV_UIMM4, NPS_QCMP_SIZE, NPS_QCMP_M1, NPS_QCMP_M2, and
	NPS_QCMP_M3.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] opcodes/arc: Add more nps instructions
@ 2016-04-19 22:17 sergiodj+buildbot
  2016-04-19 22:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] linux-record: Squash cases with identical handling
@ 2016-04-19 15:07 sergiodj+buildbot
  2016-04-19 15:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Re-factor (i386|amd64)mpx target descriptions.
@ 2016-04-19 14:47 sergiodj+buildbot
  2016-04-19 14:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Sync Makefile.tpl with gcc.
@ 2016-04-19  8:50 sergiodj+buildbot
  2016-04-19  8:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] gdb/ada-exp.y: Remap yydefred
@ 2016-04-16  2:42 sergiodj+buildbot
  2016-04-16 14:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix gdb build with --enable-build-with-cxx --disable-nls
@ 2016-04-16  2:10 sergiodj+buildbot
  2016-04-16 13:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-16  2:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b2798cc9716f45f752ea03411b6f9c9afc17cc6 ***

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

Fix gdb build with --enable-build-with-cxx --disable-nls

Compiling gdb with --enable-build-with-cxx --disable-nls, we get:

 .../src/gdb/ada-lang.c:7657:16: error: invalid conversion from const char* to char* [-fpermissive]
	type_str = (type != NULL
		 ^
 In file included from .../src/gdb/common/common-defs.h:67:0,
		  from .../src/gdb/defs.h:28,
		  from .../src/gdb/ada-lang.c:21:
 .../src/gdb/common/gdb_locale.h:40:27: error: invalid conversion from const char* to char* [-fpermissive]
  # define _(String) (String)
			    ^
 .../src/gdb/ada-lang.c:7730:46: note: in expansion of macro _
	char *name_str = name != NULL ? name : _("<null>");
					       ^
 Makefile:1140: recipe for target 'ada-lang.o' failed

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

	* ada-lang.c (ada_lookup_struct_elt_type): Constify 'type_str' and
	'name_str' locals.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Regenerate Makefile.in/aclocal.m4 automake 1.11.6
@ 2016-04-16  0:51 sergiodj+buildbot
  2016-04-16 11:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] [ARM] minor opt in thumb_stack_frame_destroyed_p
@ 2016-04-15 14:55 sergiodj+buildbot
  2016-04-15 15:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] bfd/arc: Rename enum entries to avoid conflicts
@ 2016-04-14 16:59 sergiodj+buildbot
  2016-04-14 17:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Avoid "format not a string literal" warnings
@ 2016-04-14 12:49 sergiodj+buildbot
  2016-04-14 14:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Avoid implicit float <-> integer conversion warnings
@ 2016-04-14 12:27 sergiodj+buildbot
  2016-04-14 12:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Fix copying Solaris binaries with objcopy.
@ 2016-04-14 11:19 sergiodj+buildbot
  2016-04-14 11:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-14 11:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84865015459b4e9e8ac67f9b91617fbd856d5119 ***

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

Fix copying Solaris binaries with objcopy.

	PR target/19938
bfd	* elf-bbfd.h (struct elf_backend_data): New field:
	elf_strtab_flags.
	New field: elf_backend_set_special_section_info_and_link
	* elfxx-target.h (elf_backend_strtab_flags): Define if not already
	defined.
	(elf_backend_set_special_section_info_and_link): Define if not
	already defined.
	(elfNN_bed): Use elf_backend_set_special_section_info_and_link and
	elf_backend_strtab_flags macros to initialise fields in structure.
	* elf.c (_bfd_elf_make_section_from_shdr): Check for SHF_STRINGS
	being set even if SHF_MERGE is not set.
	(elf_fake_sections): Likewise.
	(section_match): New function.  Matches two ELF sections based
	upon fixed characteristics.
	(find_link): New function.  Locates a section in a BFD that
	matches a section in a different BFD.
	(_bfd_elf_copy_private_bfd_data): Copy the sh_info and sh_link
	fields of reserved sections.
	(bfd_elf_compute_section_file_positions): Set the flags for the
	.shstrtab section based upon the elf_strtab_flags field in the
	elf_backend_data structure.
	(swap_out_syms): Likewise for the .strtab section.
	* elflink.c (bfd_elf_final_link): Set the flags for the
	.strtab section based upon the elf_strtab_flags field in the
	elf_backend_data structure.
	* elf32-i386.c (elf32_i386_set_special_info_link): New function.
	(elf_backend_strtab_flags): Set to SHF_STRINGS for Solaris
	targets.
	(elf_backend_set_special_section_info_and_link): Define for
	Solaris targets.
	* elf32-sparc.c: Likewise.
	* elf64-x86-64.c: Likewise.

binutils* testsuite/binutils-all/i386/compressed-1b.d: Allow for the
	string sections possibly having the SHF_STRINGS flag bit set.
	* testsuite/binutils-all/i386/compressed-1c.d: Likewise.
	* testsuite/binutils-all/readelf.s: Likewise.
	* testsuite/binutils-all/readelf.s-64: Likewise.
	* testsuite/binutils-all/x86-64/compressed-1b.d: Likewise.
	* testsuite/binutils-all/x86-64/compressed-1c.d: Likewise.

gas	* testsuite/gas/i386/ilp32/x86-64-unwind.d: Allow for the string
	sections possibly having the SHF_STRINGS flag bit set.
	* testsuite/gas/i386/x86-64-unwind.d: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Test GDB connection to GDBserver with no symbol files
@ 2016-04-13 21:23 sergiodj+buildbot
  2016-04-14  9:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Debugging without a binary (regression)
@ 2016-04-13 20:40 sergiodj+buildbot
  2016-04-14  9:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-13 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d

Debugging without a binary (regression)

When we attempt to debug a process using GDBserver in standard remote mode
without a symbol file on GDB's end, we may run into an issue where GDB cuts
the connection attempt short due to an error. The error is caused by not
being able to open a symbol file, like so:

--

(gdb) set sysroot
(gdb) tar rem :2345
Remote debugging using :2345
/proc/23769/exe: Permission denied.
(gdb) i r
The program has no registers now.
(gdb)

It should've been like this:

(gdb) set sysroot
(gdb) tar rem :2345
Remote debugging using :2345
warning: /tmp/symbol-file: Permission denied.
0xf7ddb2d0 in ?? ()
(gdb) i r
eax            0x0  0
ecx            0x0  0
edx            0x0  0
ebx            0x0  0
esp            0xffffdfa0 0xffffdfa0
ebp            0x0  0x0
esi            0x0  0
edi            0x0  0
eip            0xf7ddb2d0 0xf7ddb2d0
eflags         0x200  [ IF ]
cs             0x33 51
ss             0x2b 43
ds             0x0  0
es             0x0  0
fs             0x0  0
gs             0x0  0
(gdb)

This is caused by a couple of function calls within exec_file_locate_attach
that can potentially throw errors.

The following patch guards both exec_file_attach and symbol_file_add_main to
prevent the errors from disrupting the connection process.

There was also a case where native GDB tripped on this problem, but it was
mostly fixed by bf74e428bca61022bd5cdf6bf28789a184748b4d.

Regression-tested on x86-64/Ubuntu.

gdb/ChangeLog:

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

	* exec.c (exec_file_locate_attach): Guard a couple functions
	that can throw errors.
	(exception_print_same): New helper function.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use setjmp/longjmp for TRY/CATCH instead of sigsetjmp/siglongjmp
@ 2016-04-13  8:30 sergiodj+buildbot
  2016-04-14  4:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Eliminate prepare_to_throw_exception
@ 2016-04-13  7:30 sergiodj+buildbot
  2016-04-13 23:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 20:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in infcmd.c
@ 2016-04-13  5:12 sergiodj+buildbot
  2016-04-13 15:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Use target_terminal_ours_for_output in MI
@ 2016-04-13  5:01 sergiodj+buildbot
  2016-04-13 18:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Decouple target_interrupt from all-stop/non-stop modes
@ 2016-04-12 23:43 sergiodj+buildbot
  2016-04-13 10:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ 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 16:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ 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] 1903+ messages in thread
* [binutils-gdb] Remove unused struct serial::name field
@ 2016-04-12 20:26 sergiodj+buildbot
  2016-04-12 20:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 20:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f5219fc34f7557296272230123a3837960a6f09 ***

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

Remove unused struct serial::name field

Not used by anything.

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

	* serial.c (serial_open, serial_fdopen_ops, do_serial_close):
	Remove references to name.
	* serial.h (struct serial) <name>: Delete.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Introduce interruptible_select
@ 2016-04-12 20:21 sergiodj+buildbot
  2016-04-12 23:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 20:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0881b37b6734328118a5683e1e18f65a8987c89 ***

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

Introduce interruptible_select

We have places where we call a blocking gdb_select expecting that a
Ctrl-C will unblock it.  However, if the Ctrl-C is pressed just before
gdb_select, the SIGINT handler runs before gdb_select, and thus
gdb_select won't return.

For example gdb_readline_no_editing:

       QUIT;

       /* Wait until at least one byte of data is available.  Control-C
          can interrupt gdb_select, but not fgetc.  */
       FD_ZERO (&readfds);
       FD_SET (fd, &readfds);
       if (gdb_select (fd + 1, &readfds, NULL, NULL, NULL) == -1)

and stdio_file_read:

     /* For the benefit of Windows, call gdb_select before reading from
	the file.  Wait until at least one byte of data is available.
	Control-C can interrupt gdb_select, but not read.  */
     {
       fd_set readfds;
       FD_ZERO (&readfds);
       FD_SET (stdio->fd, &readfds);
       if (gdb_select (stdio->fd + 1, &readfds, NULL, NULL, NULL) == -1)
	 return -1;
     }
     return read (stdio->fd, buf, length_buf);


This is a race classically fixed with either the self-pipe trick, or
by blocking SIGINT and then using pselect instead of select.

Blocking SIGINT most of the time would mean that check_quit_flag (and
thus QUIT) would need to do a syscall every time it is called, which
sounds best avoided, since QUIT is called in many loops.  Thus we take
the self-pipe trick route (wrapped in a serial event).

Instead of having all places that need this manually add an extra file
descriptor to the set of gdb_select's watched file descriptors, we
introduce a wrapper, interruptible_select, that does that.

The Windows version of gdb_select actually does not suffer from this,
because mingw-hdep.c:gdb_call_async_signal_handler sets a Windows
event that gdb_select always waits on.  So this patch can be seen as
generalization of that technique.  We can't remove that extra event
from mingw-hdep.c until we get rid of immediate_quit though.

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

	* defs.h: Extend QUIT-related comments to mention
	interruptible_select.
	(quit_serial_event_set, quit_serial_event_clear): Declare.
	* event-top.c: Include "ser-event.h" and "gdb_select.h".
	(quit_serial_event): New global.
	(async_init_signals): Make quit_serial_event.
	(quit_serial_event_set, quit_serial_event_clear)
	(quit_serial_event_fd, interruptible_select): New functions.
	* extension.c (set_quit_flag): Set the quit serial event.
	(check_quit_flag): Clear the quit serial event.
	* gdb_select.h (interruptible_select): New declaration.
	* guile/scm-ports.c (ioscm_input_waiting): Use
	interruptible_select instead of gdb_select.
	* top.c (gdb_readline_no_editing): Likewise.
	* ui-file.c (stdio_file_read): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't set immediate_quit in prompt_for_continue
@ 2016-04-12 18:29 sergiodj+buildbot
  2016-04-12 19:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 18:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2acc30bb60357815c3965c058965d0f5313f814 ***

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

Don't set immediate_quit in prompt_for_continue

immediate_quit used to be necessary back when prompt_for_continue used
blocking fread, but nowadays it uses gdb_readline_wrapper, which is
implemented in terms of a nested event loop, which already knows how
to react to SIGINT:

 #0  throw_it (reason=RETURN_QUIT, error=GDB_NO_ERROR, fmt=0x9d6d7e "Quit", ap=0x7fffffffcb88)
     at .../src/gdb/common/common-exceptions.c:324
 #1  0x00000000007bab5d in throw_vquit (fmt=0x9d6d7e "Quit", ap=0x7fffffffcb88) at .../src/gdb/common/common-exceptions.c:366
 #2  0x00000000007bac9f in throw_quit (fmt=0x9d6d7e "Quit") at .../src/gdb/common/common-exceptions.c:385
 #3  0x0000000000773a2d in quit () at .../src/gdb/utils.c:1039
 #4  0x000000000065d81b in async_request_quit (arg=0x0) at .../src/gdb/event-top.c:893
 #5  0x000000000065c27b in invoke_async_signal_handlers () at .../src/gdb/event-loop.c:949
 #6  0x000000000065aeef in gdb_do_one_event () at .../src/gdb/event-loop.c:280
 #7  0x0000000000770838 in gdb_readline_wrapper (prompt=0x7fffffffcd40 "---Type <return> to continue, or q <return> to quit---")
     at .../src/gdb/top.c:873

The need for the QUIT in stdin_event_handler is then exposed by the
gdb.base/double-prompt-target-event-error.exp test, which has:

	# We're now stopped in a pagination query while handling a
	# target event (printing where the program stopped).  Quitting
	# the pagination should result in only one prompt being
	# output.
	send_gdb "\003p 1\n"

Without that change we'd get:

 Continuing.
 ---Type <return> to continue, or q <return> to quit---PASS: gdb.base/double-prompt-target-event-error.exp: ctrlc target event: continue: continue to pagination
 ^CpQuit
 (gdb)  1
 Undefined command: "1".  Try "help".
 (gdb) PASS: gdb.base/double-prompt-target-event-error.exp: ctrlc target event: continue: first prompt
 ERROR: Undefined command "".
 UNRESOLVED: gdb.base/double-prompt-target-event-error.exp: ctrlc target event: continue: no double prompt

Vs:

 Continuing.
 ---Type <return> to continue, or q <return> to quit---PASS: gdb.base/double-prompt-target-event-error.exp: ctrlc target event: continue: continue to pagination
 ^CQuit
 (gdb) p 1
 $1 = 1
 (gdb) PASS: gdb.base/double-prompt-target-event-error.exp: ctrlc target event: continue: first prompt
 PASS: gdb.base/double-prompt-target-event-error.exp: ctrlc target event: continue: no double prompt

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

	* event-top.c (stdin_event_handler): Call QUIT;
	(prompt_for_continue): Don't run with immediate_quit set.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Stop remote-fileio.c from throwing from SIGINT handler
@ 2016-04-12 18:20 sergiodj+buildbot
  2016-04-12 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 18:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acd5494dd868ae849b4544abdc50dc8b10ba6f54 ***

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

Stop remote-fileio.c from throwing from SIGINT handler

This code installs a custom signal handler that throws a quit
exception if remote_fio_no_longjmp is not set.

AFAICS, the only real reason for this might have been to unblock the
ui_file_read call, in remote_fileio_func_read.  But ever since:

  2009-11-13  Daniel Jacobowitz  <dan@codesourcery.com>

	* ui-file.c (stdio_file_read): Call gdb_select before read.

at:

  https://sourceware.org/ml/gdb-patches/2009-11/msg00321.html

that call is interruptible.

This is not only useful for switching to native C++ exceptions, but
AFAICS, also fixes a potential mess up of the remote protocol
connection, since there are target_read_memory calls done while
remote_fio_no_longjmp is clear.  If the user presses ctrl-c while GDB
is sending or receiving a packet, we'll stop the communication
immediately, at a point where it isn't safe.

gdbserver doesn't support the File I/O remote protocol extension so I
can't test this.

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

	* remote-fileio.c (sigint_fileio_token, remote_fio_no_longjmp):
	Delete.
	(async_remote_fileio_interrupt): Delete.
	(remote_fileio_ctrl_c_signal_handler): Don't call the async signal
	handler.  Instead just always set the ctrl_c flag.
	(remote_fileio_reply): Clear remote_fio_ctrl_c_flag before
	re-enabling the SIGINT handler.
	(remote_fileio_func_open, remote_fileio_func_close)
	(remote_fileio_func_read, remote_fileio_func_write)
	(remote_fileio_func_lseek, remote_fileio_func_rename)
	(remote_fileio_func_unlink, remote_fileio_func_stat)
	(remote_fileio_func_fstat, remote_fileio_func_gettimeofday)
	(remote_fileio_func_isatty, remote_fileio_func_system)
	(remote_fileio_request): Remove references to
	remote_fio_no_longjmp.
	(initialize_remote_fileio): Don't create an async signal handler.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't rely on immediate_quit in command_line_input
@ 2016-04-12 16:23 sergiodj+buildbot
  2016-04-12 16:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3212b858458dc3f2ae73e32fa066dabd56919a13 ***

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

Don't rely on immediate_quit in command_line_input

AFAICS, immediate_quit was only needed here nowdays to be able to
interrupt gdb_readline_no_editing.

command_line_input can also take the gdb_readline_wrapper path, but
since that is built on top of the event loop (gdb_select / poll and
asynchronous signal handlers), it can be interrupted.

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

	* top.c: Include "gdb_select.h".
	(gdb_readline_no_editing): Wait for input with gdb_select instead
	of blocking in fgetc.
	(command_line_input): Don't set immediate_quit.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add support for .extCondCode, .extCoreRegister and .extAuxRegister.
@ 2016-04-12 10:00 sergiodj+buildbot
  2016-04-12 10:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f36e33dac1a97cca8f79ca8b20cf0fb05f1e25f4 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: f36e33dac1a97cca8f79ca8b20cf0fb05f1e25f4

Add support for .extCondCode, .extCoreRegister and .extAuxRegister.

gas/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/gas/arc/textauxregister.d: New file.
	* testsuite/gas/arc/textauxregister.s: Likewise.
	* testsuite/gas/arc/textcondcode.d: Likewise.
	* testsuite/gas/arc/textcondcode.s: Likewise.
	* testsuite/gas/arc/textcoreregister.d: Likewise.
	* testsuite/gas/arc/textcoreregister.s: Likewise.
	* testsuite/gas/arc/textpseudoop.d: Likewise.
	* testsuite/gas/arc/textpseudoop.s: Likewise.
	* testsuite/gas/arc/ld2.d: Update test.
	* testsuite/gas/arc/st.d: Likewise.
	* testsuite/gas/arc/taux.d: Likewise.
	* doc/c-arc.texi (ARC Directives): Add .extCondCode,
	.extCoreRegister and .extAuxRegister documentation.
	* config/tc-arc.c (arc_extcorereg): New function.
	(md_pseudo_table): Add .extCondCode, .extCoreRegister and
	.extAuxRegister pseudo-ops.
	(extRegister_t): New type.
	(ext_condcode, arc_aux_hash): New global variable.
	(find_opcode_match): Check for extensions.
	(preprocess_operands): Likewise.
	(md_begin): Add aux registers in a hash.
	(assemble_insn): Update use arc_flags member.
	(tokenize_extregister): New function.
	(create_extcore_section): Likewise.
	* config/tc-arc.h (MAX_FLAG_NAME_LENGHT): Increase to 10.
	(arc_flags): Delete code, add flgp.

include/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (flag_class_t): Update.
	(ARC_OPCODE_NONE): Define.
	(ARC_OPCODE_ARCALL): Likewise.
	(ARC_OPCODE_ARCFPX): Likewise.
	(ARC_REGISTER_READONLY): Likewise.
	(ARC_REGISTER_WRITEONLY): Likewise.
	(ARC_REGISTER_NOSHORT_CUT): Likewise.
	(arc_aux_reg): Add cpu.

opcodes/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-dis.c (find_format): Check for extension flags.
	(print_flags): New function.
	(print_insn_arc): Update for .extCondCode, .extCoreRegister and
	.extAuxRegister.
	* arc-ext.c (arcExtMap_coreRegName): Use
	LAST_EXTENSION_CORE_REGISTER.
	(arcExtMap_coreReadWrite): Likewise.
	(dump_ARC_extmap): Update printing.
	* arc-opc.c (arc_flag_classes): Add F_CLASS_EXTEND flag.
	(arc_aux_regs): Add cpu field.
	* arc-regs.h: Add cpu field, lower case name aux registers.

Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com>


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Update ARC instruction data-base.
@ 2016-04-12  9:33 sergiodj+buildbot
  2016-04-12  9:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-12  9:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c2e355e4830814e18329a53d01cfa634d576211 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 1c2e355e4830814e18329a53d01cfa634d576211

Update ARC instruction data-base.

gas/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* testsuite/gas/arc/noargs_a7.d: New file.
	* testsuite/gas/arc/noargs_a7.s: Likewise.
	* testsuite/gas/arc/noargs_hs.d: Likewise.
	* testsuite/gas/arc/noargs_hs.s: Likewise.

opcode/
2016-04-05  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-tbl.h: Add rtsc, sleep with no arguments.

Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com>


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb.python/py-mi-events-gdb.py: Add parentheses to print
@ 2016-04-09 12:55 sergiodj+buildbot
  2016-04-09 13:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-09 12:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2e88a1ea30deecac47d89b03f6d60ca04245c36f ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 2e88a1ea30deecac47d89b03f6d60ca04245c36f

gdb.python/py-mi-events-gdb.py: Add parentheses to print

Required for Python 3

gdb/testsuite/ChangeLog:

	* gdb.python/py-mi-events-gdb.py (signal_stop_handler): Add
	parentheses to print.
	(continue_handler): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Fix for gcc-4.8: gdb.base/jit.exp gdb.base/jit-so.exp
@ 2016-04-08 13:52 sergiodj+buildbot
  2016-04-08 14:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-08 13:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 065005336492337c92d06e87544646635a5b9566 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 065005336492337c92d06e87544646635a5b9566

testsuite: Fix for gcc-4.8: gdb.base/jit.exp gdb.base/jit-so.exp

on CentOS-7.2 I get

Running /home/jkratoch/redhat/gdb-test-reg/gdb/testsuite/gdb.base/jit.exp ...
FAIL: gdb.base/jit.exp: one_jit_test-1: continue to breakpoint: break here 2 (the program exited)
FAIL: gdb.base/jit.exp: one_jit_test-2: continue to breakpoint: break here 2 (the program exited)
FAIL: gdb.base/jit.exp: attach: one_jit_test-2: continue to breakpoint: break here 2 (the program exited)
FAIL: gdb.base/jit.exp: attach: one_jit_test-2: break here 2: set var wait_for_gdb = 1
FAIL: gdb.base/jit.exp: attach: one_jit_test-2: break here 2: detach (the program is no longer running)
FAIL: gdb.base/jit.exp: attach: one_jit_test-2: break here 2: attach
FAIL: gdb.base/jit.exp: attach: one_jit_test-2: break here 2: set var wait_for_gdb = 0
FAIL: gdb.base/jit.exp: PIE: one_jit_test-1: continue to breakpoint: break here 2 (the program exited)
Running /home/jkratoch/redhat/gdb-test-reg/gdb/testsuite/gdb.base/jit-so.exp ...
FAIL: gdb.base/jit-so.exp: one_jit_test-1: continue to breakpoint: break here 2 (the program exited)
FAIL: gdb.base/jit-so.exp: one_jit_test-2: continue to breakpoint: break here 2 (the program exited)

since:

85af34ee0211eedf8d30a5c44dfc59dddf8b512a is the first bad commit
commit 85af34ee0211eedf8d30a5c44dfc59dddf8b512a
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Mar 31 19:28:47 2016 +0100
    Add regression test for PR gdb/19858 (JIT code registration on attach)

The compiled code's .debug_line is wrong (for the simplistic approach of GDB
to put a breakpoint on the first address belonging to that source line) and so
GDB misses the breakpoint at the last line:
          WAIT_FOR_GDB; return 0;  /* gdb break here 2  */

Most of the patch is just about reindentation, no changes there.

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

	Fix compatibility with gcc-4.8.5-4.el7.x86_64.
	* gdb.base/jit-main.c: Use exit after usage.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gas/arc: Handle multiple arc_opcode chains for same mnemonic
@ 2016-04-07 17:52 sergiodj+buildbot
  2016-04-07 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1328504b287b2c284419d989e0d05e7d6d3ffa59 ***

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

gas/arc: Handle multiple arc_opcode chains for same mnemonic

This commit completes support for having multiple instructions with the
same mnemonic in non-contiguous blocks within the arc_opcodes table.

The commit adds an iterator mechanism for the arc_opcode_hash_entry
structure, which is then used in find_opcode_match to consider all
arc_opcode entries with the same mnemonic, even when these instructions
are stored in non-contiguous blocks.

I extend the comment on the arc_opcodes table to discuss how entries
within the table are organised, and to mention how instructions can be
split into multiple groups if needed, but that the table is still
searched in table order.

There should be no user visible changes after this commit.

gas/ChangeLog:

	* config/tc-arc.c (struct arc_opcode_hash_entry_iterator): New
	structure.
	(arc_opcode_hash_entry_iterator_init): New function.
	(arc_opcode_hash_entry_iterator_next): New function.
	(find_opcode_match): Iterate over all arc_opcode entries
	referenced by the arc_opcode_hash_entry passed in as a parameter.

opcodes/ChangeLog:

	* arc-opc.c (arc_opcodes): Extend comment to discus table layout.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.reverse/next-reverse-bkpt-over-sr.exp
@ 2016-04-07 16:55 sergiodj+buildbot
  2016-04-07 17:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bde475616e3fdb6d41c047956aaf627fbf34a85d ***

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

Fix gdb.reverse/next-reverse-bkpt-over-sr.exp

I see the fail on aarch64-linux,

(gdb) reverse-next

Breakpoint 2, callee () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c:26^M
26        myglob++; return 0;   /* ARRIVED IN CALLEE */
(gdb) FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: reverse-next over call trips user breakpoint at function entry

The test expects program stops at line 25, but program stops at line 26.

(gdb) maintenance info line-table
objfile: /scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/testsuite/outputs/gdb.reverse/next-reverse-bkpt-over-sr/next-reverse-bkpt-over-sr ((struct objfile *) 0x613000002880)
compunit_symtab: ((struct compunit_symtab *) 0x621000121760)
symtab: /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.reverse/step-reverse.c ((struct symtab *) 0x6210001217e0)
linetable: ((struct linetable *) 0x6210001520d0):
INDEX    LINE ADDRESS
0          25 0x0000000000400890
1          26 0x0000000000400890
2          27 0x00000000004008b0

(gdb) disassemble callee
Dump of assembler code for function callee:
   0x0000000000400890 <+0>:     adrp    x0, 0x410000
   0x0000000000400894 <+4>:     add     x0, x0, #0xcac

the line-table show that the first instruction of function callee is
mapped line 25 and 26.  I am not sure the line-table is correct, but
it is not the point of this test.  The goal of this test is to test
program hits the breakpoint on the first instruction of function after
'reverse-next', so I change this test to expect the breakpoint number
the program hits.

gdb/testsuite:

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

	* gdb.reverse/next-reverse-bkpt-over-sr.exp: Match the breakpoint
	number instead of the comments on some line.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Set bp_tgt->reqstd_address and bp_tgt->placed_size in record_full_insert_breakpoint
@ 2016-04-07 16:05 sergiodj+buildbot
  2016-04-07 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-07 16:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ccd06e498586b39f06447cbf3f2fad50120fde6 ***

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

Set bp_tgt->reqstd_address and bp_tgt->placed_size in record_full_insert_breakpoint

I notice that bp_tgt won't be fully initialized if to_insert_breakpoint
isn't called in record_full_insert_breakpoint, and bp_tgt->reqstd_address
is zero, so an entry is added to record_full_breakpoints, but its address
is zero, which is wrong.  This patch is to call gdbarch_breakpoint_from_pc
in the else branch to set bp_tgt->reqstd_address and bp_tgt->placed_size.

gdb:

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

	* record-full.c (record_full_insert_breakpoint): Set
	bp_tgt->reqstd_address and bp_tgt->placed_size.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Optimized-out pointer: New test for error handling
@ 2016-04-06 21:44 sergiodj+buildbot
  2016-04-06 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-06 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b16f8a3b1ecce592fe331a5b1ce6632951350e9c ***

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

Optimized-out pointer: New test for error handling

This patch implements a test that ensures that with "set print object
on", -var-create returns "<optimized out>" for an optimized out pointer
to structure, rather than throwing an error, while also ensuring that
any attempt to dereference the pointer *will* throw an error.

It uses the dwarf assembler to construct the appropriate debug info
to represent a pointer-to-struct in the program as optimized out,
and then accesses that pointer in various ways.  The test uses both
the console interpreter and the MI interpreter.

gdb/testsuite/ChangeLog:
2016-04-06  Don Breazeal  <donb@codesourcery.com>

	* gdb.dwarf2/dw2-opt-structptr.c: New test program.
	* gdb.dwarf2/dw2-opt-structptr.exp: New test script.


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

*** TEST RESULTS FOR COMMIT 319cb5d0cf7ba3bc0e77ab420cfcf75568d722b4 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 319cb5d0cf7ba3bc0e77ab420cfcf75568d722b4

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-06  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* remote.c (struct remote_state): New field unknown_v_replies_ok.
	(packet_config_support): Read it.
	(remote_start_remote): Set it.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix memory leak in ld ARM backend
@ 2016-04-06  8:42 sergiodj+buildbot
  2016-04-06  8:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-06  8:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15dd01b1209ec92b361dd2547708dd17ffc2a786 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: 15dd01b1209ec92b361dd2547708dd17ffc2a786

Fix memory leak in ld ARM backend

2016-04-06  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	bfd/
	* elf32-arm.c (elf32_arm_size_stubs): Move error_ret_free_local to be
	a fall through from error_ret_free_internal.  Free local_syms in
	error_ret_free_local if allocated from bfd_elf_get_elf_syms ().


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix IPA detection in ftrace-insn-reloc.exp
@ 2016-04-06  1:00 sergiodj+buildbot
  2016-04-06  1:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-06  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03a8c4dfc295fdebf4dac7a5ee91592e69b404a6 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 03a8c4dfc295fdebf4dac7a5ee91592e69b404a6

Fix IPA detection in ftrace-insn-reloc.exp

In commit 6e774b13c3b, I forgot to update this test.

gdb/testsuite/ChangeLog:

	* gdb.arch/ftrace-insn-reloc.exp: Check for IPA basename instead of
	absolute.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Make ftrace tests work with remote targets
@ 2016-04-05 19:25 sergiodj+buildbot
  2016-04-05 22:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6e774b13c3b81ac2599812adf058796948ce7e95 ***

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

Make ftrace tests work with remote targets

When we build a shared library for testing, it is built differently
whether it is meant for the local system or a remote one.  When it is
for the local system, the library is built with no SONAME.  So when the
executable is built, roughly in this way:

  $ gcc testfile.c /path/to/library.so

the executable will contain an absolute reference to the library.  For
example:

  $ readelf -a testsuite/gdb.python/py-shared | grep NEEDED
   0x0000000000000001 (NEEDED)             Shared library: [/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.python/py-shared-sl.sl]

When testing is done remotely, the absolute path obviously doesn't work.
Therefore, we build the library with an SONAME:

  $ readelf -a testsuite/gdb.python/py-shared-sl.sl | grep SONAME
   0x000000000000000e (SONAME)             Library soname: [py-shared-sl.sl]

which ends up in the executable's NEEDED field:

  $ readelf -a testsuite/gdb.python/py-shared | grep NEEDED
   0x0000000000000001 (NEEDED)             Shared library: [py-shared-sl.sl]

The executable and the library are then uploaded side-by-side on the
remote system.  To allow the dynamic linker to find the shared library,
we have to add the special RPATH value $ORIGIN, which tells it to search
in the executable's directory:

  $ readelf -a testsuite/gdb.python/py-shared | grep ORIGIN
   0x000000000000000f (RPATH)              Library rpath: [$ORIGIN]

The problem with the IPA library is that it doesn't have an SONAME,
making it very difficult to do testing on a remote board.  When a
test executable is linked with it, it contains an absolute reference to
the library path.  Therefore, unless the paths on the target are the
same as on the build system, it won't work.

To make it possible for tests using the IPA library to run test on
remote boards, I suggest adding an SONAME to libinproctrace.so.  I don't
think it should be a big problem for users.  All the libraries installed
on my system have an SONAME, so it should be fine if libinproctrace.so
does too.

As a consequence, native testing does not work anymore, since
executables do not contain the absolute path to the library anymore.  To
keep them working, we can have gdb_load_shlibs copy the library to the
test directory when testing natively.  That's done by modifying
gdb_load_shlibs.  We also have to add RPATH=$ORIGIN to executables, even
when testing natively.

I think it's a good change in general, as it reduces the differences
between testing a native and a remote target.  To further reduce those
differences, we can also always build test shared libraries with an
SONAME.

ftrace.exp and ftrace-lock.exp need to be modified slightly.  The code
checks that the IPA library is loaded using the absolute path on the
build machine.  That obviously doesn't work if the test is done
remotely, as the path will be different.  I changed the tests to only
search for the library basename (e.g. libinproctrace.so).

gdb/gdbserver/ChangeLog:

	* Makefile.in ($(IPA_LIB)): Set SONAME of the IPA lib.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace-lock.exp: Check for IPA basename instead of
	absolute.
	* gdb.trace/ftrace.exp: Likewise.
	* lib/gdb.exp (gdb_compile): Set rpath $ORIGIN for non-remote
	targets as well.
	(gdb_compile_shlib): Set SONAME for non-remote targets as well.
	(gdb_load_shlibs): Copy libraries to test directory when testing
	natively.  Only set solib-search-path if testing remotely.
	* lib/mi-support.exp (mi_load_shlibs): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Improve gdb_remote_download, remove gdb_download
@ 2016-04-05 18:35 sergiodj+buildbot
  2016-04-05 21:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7817ea46148df2931cf00d17aeedb844b6e4e4db ***

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

Improve gdb_remote_download, remove gdb_download

This patch removes gdb_download in favor of gdb_remote_download, since
they are very close in functionality.  Also, in preparation for the
following patch about shared library handling during tests, it improves
gdb_remote_download so that it uses standard_output_file for any
destination board that is local, not only host.

If the destination board is remote, gdb_remote_download will use the
standard remote_download from DejaGnu, resulting in the file being
transferred on the remote system.

If the destination is local, gdb_remote_download will copy the file to
the standard test directory (found using standard_output_file).  Tcl's
file copy seems to handle gracefully cases where the source file is the
same as the destination, so I don't think it's necessary to check for
that case ourselves, as a previous version of the patch did.

I'd prefer to keep the name gdb_download instead of gdb_remote_download,
since I don't like the fact that gdb_remote_download implies that the
destination is remote, when it's not always the case.  However,
gdb_remote_download is used at many more places than gdb_download, so
it's easier to reuse that.  Also, since it's a wrapper around DejaGnu's
remote_download, it might be better to keep that name.  I don't know.

I ran the testsuite native, with native-gdbserver and with a
remote gdbserver, and didn't see any related failure.

gdb/testsuite/ChangeLog:

	* gdb.base/jit-so.exp: Use gdb_remote_download instead of
	gdb_download.  Use it even if the target is not remote.
	* gdb.base/jit.exp (compile_jit_test): Likewise.
	* lib/gdb.exp (gdb_remote_download): Copy files to the standard
	output directory if the destination board is local, otherwise use
	the standard remote_download from DejaGnu.
	(gdb_download): Remove.
	(gdb_load_shlibs): Use gdb_remote_download instead of
	gdb_download.
	* lib/gdbserver-support.exp (gdbserver_download_current_prog):
	Use gdb_remote_download instead of gdb_download.  Use it even if
	the target is not remote.
	* lib/mi-support.exp (mi_load_shlibs): Use gdb_remote_download
	instead of gdb_download.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] PLT content endianess awareness.
@ 2016-04-05 17:01 sergiodj+buildbot
  2016-04-05 18:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e5885b72e20ef874f526e77a4946b2655e6d3c3 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 1e5885b72e20ef874f526e77a4946b2655e6d3c3

[ARC] PLT content endianess awareness.

bfd/
2016-04-05  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (plt_do_relocs_for_symbol): Changed.
	(relocate_plt_for_entry): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] Dynamic relocs verification for dynindx == -1.
@ 2016-04-05 15:04 sergiodj+buildbot
  2016-04-05 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94e5c97160abbcf2274f8d58dc2900bc85c1c384 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 94e5c97160abbcf2274f8d58dc2900bc85c1c384

[ARC] Dynamic relocs verification for dynindx == -1.

bfd/
2016-04-05  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (name_for_global_symbol): Added assert to check for
	symbol index.
	(elf_arc_relocate_section): Added and changed asserts, validating
	the synamic symbol index.
	(elf_arc_finish_dynamic_symbol): Do not fill the dynamic
	relocation if symbol has dynindx set to -1.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ELF/LD: Avoid producing hidden and internal dynamic symbols
@ 2016-04-05 14:39 sergiodj+buildbot
  2016-04-05 14:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-05 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f599d0e7b5039c814731293043e247304ec006b ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 1f599d0e7b5039c814731293043e247304ec006b

ELF/LD: Avoid producing hidden and internal dynamic symbols

Always turn hidden and internal symbols which have a dynamic index into
local ones.  This is required by the the ELF gABI[1]:

"A hidden symbol contained in a relocatable object must be either
removed or converted to STB_LOCAL binding by the link-editor when the
relocatable object is included in an executable file or shared object."

"An internal symbol contained in a relocatable object must be either
removed or converted to STB_LOCAL binding by the link-editor when the
relocatable object is included in an executable file or shared object."

The ELF linker usually respects this requirement, however in the case
where a dynamic symbol has been preallocated due to a reference of the
default export class aka visibility from the object being linked, and
then merged with a hidden or internal symbol definition from within the
same object, then the original export class is carried over to the
output dynamic symbol table, because while merging the generic ELF
linker only converts affected dynamic symbols to local when they are
defined or referenced by the object being linked and a dynamic object
involved in the link both at a time.

The dynamic symbol produced confuses then the dynamic loader at the run
time -- the hidden or internal export class is ignored and the symbol
follows preemption rules as with the default export class.

In the MIPS target it happens when `mips_elf_record_global_got_symbol'
creates a dynamic symbol when a call relocation is encountered.
Additionally if the undefined symbol referred by such a relocation does
specify the intended export class, then a local dynamic symbol is
created instead, which is harmless and allowed, but useless.  Normally
no local dynamic symbols are created, except for a single dummy one at
the beginning.

Correct the problem by removing the extra check for a dynamic symbol
being defined or referenced by the object being linked and a dynamic
object involved in the link both at a time.  The test cases included
cover the internal and hidden symbol cases, as well as a protected
symbol for a reference, the handling of which is unchanged by this fix.
Both cases described above are covered, that is where an internal or
hidden dynamic symbol is produced and where a local one is.

NB this change affects CRIS results where some symbols in the static
table produced in a final link are now converted from STV_HIDDEN to
STB_LOCAL.  This happens whenever the `elf_backend_hide_symbol' handler
is called, so the affected symbols must have been chosen for entering
into the dynamic symbol table, except in these test cases no such symbol
table is produced.  In fully linked binaries the static symbol table is
only used for debugging though, so such a change is fine.

References:

[1] "System V Application Binary Interface - DRAFT - 24 April 2001",
    The Santa Cruz Operation, Inc., "Symbol Table",
    <http://www.sco.com/developers/gabi/2001-04-24/ch4.symtab.html>

	bfd/
	PR ld/19908
	* elflink.c (elf_link_add_object_symbols): Always turn hidden
	and internal symbols which have a dynamic index into local
	ones.

	ld/
	PR ld/19908
	* testsuite/ld-cris/tls-e-20.d: Adjust for hidden symbol
	handling fix.
	* testsuite/ld-cris/tls-e-20a.d: Likewise.
	* testsuite/ld-cris/tls-e-21.d: Likewise.
	* testsuite/ld-cris/tls-e-23.d: Likewise.
	* testsuite/ld-cris/tls-e-80.d: Likewise.
	* testsuite/ld-cris/tls-gd-3h.d: Likewise.
	* testsuite/ld-cris/tls-leie-19.d: Likewise.
	* testsuite/ld-mips-elf/export-class-ref-lib.sd: New test.
	* testsuite/ld-mips-elf/export-hidden-ref.sd: New test.
	* testsuite/ld-mips-elf/export-internal-ref.sd: New test.
	* testsuite/ld-mips-elf/export-protected-ref.sd: New test.
	* testsuite/ld-mips-elf/export-class-ref-f0.s: New test source.
	* testsuite/ld-mips-elf/export-class-ref-f1.s: New test source.
	* testsuite/ld-mips-elf/export-class-ref-f2.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] IPA: Fix build problem on !HAVE_GETAUXVAL
@ 2016-04-03 16:59 sergiodj+buildbot
  2016-04-03 16:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-03 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0a9981f372e636508b9a235017f2aba565e435d ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: d0a9981f372e636508b9a235017f2aba565e435d

IPA: Fix build problem on !HAVE_GETAUXVAL

These files need AT_PHDR, which is defined in elf.h.  If HAVE_GETAUXVAL
is set, it's implicitely included by sys/auxv.h.  Include it manually
for the opposite case.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-ipa.c: Add <elf.h> include.
	* linux-ppc-ipa.c: Add <elf.h> include.
	* linux-s390-ipa.c: Add <elf.h> include.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR19886, --as-needed regression
@ 2016-04-01 13:05 sergiodj+buildbot
  2016-04-01 13:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-04-01 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b15fa7ac802f430f7fb7c2b77f40ab78c2e4018 ***

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

PR19886, --as-needed regression

This isn't perfect in checking whether libraries will be loaded since
elf_link_add_object_symbols doesn't recurse down DT_NEEDED links.
(That happens later in ld/emultempl/elf32.em after_open.)  So in
effect this recursive check really only looks one level down the
DT_NEEDED tree.  Which is enough for the most common case, and
libc.so/ld.so in particular.

	PR 19886
	* elflink.c (on_needed_list): Recursively check needed status.
	(elf_link_add_object_symbols): Adjust.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add regression test for PR gdb/19858 (JIT code registration on attach)
@ 2016-03-31 19:22 sergiodj+buildbot
  2016-03-31 21:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 19:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64cdf930d9ed85e93ae55adbc20b0f9848ef863b ***

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

Add regression test for PR gdb/19858 (JIT code registration on attach)

This test would fail without the previous gdb/jit.c fix:

  (gdb) attach 23031
  Attaching to program: .../build/gdb/testsuite/outputs/gdb.base/jit/jit-main, process 23031
  [...]
  207           WAIT_FOR_GDB; i = 0;  /* gdb break here 1 */
  (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: attach
  set var wait_for_gdb = 0
  (gdb) PASS: gdb.base/jit.exp: attach: one_jit_test-2: set var wait_for_gdb = 0
  info function ^jit_function
  All functions matching regular expression "^jit_function":
  (gdb) FAIL: gdb.base/jit.exp: attach: one_jit_test-2: info function ^jit_function

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

	PR gdb/19858
	* gdb.base/jit-main.c: Include unistd.h.
	(ATTACH): Define to 0 if not already defined.
	(wait_for_gdb, mypid): New globals.
	(WAIT_FOR_GDB): New macro.
	(MAIN): Set an alarm.  Store the process's pid.  Wait for GDB at
	some breakpoint locations.
	* gdb.base/jit.exp (clean_reattach, continue_to_test_location):
	New procedures.
	(one_jit_test): Add REATTACH parameter, and handle it.  Use
	continue_to_test_location.
	(top level): Test attach, and adjusts calls to one_jit_test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver: Add emit_ops for powerpc.
@ 2016-03-31 15:30 sergiodj+buildbot
  2016-03-31 17:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 15:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14e2b6d93d461334049ed350cf88fcd2a490de2c ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 14e2b6d93d461334049ed350cf88fcd2a490de2c

gdbserver: Add emit_ops for powerpc.

gdb/gdbserver/ChangeLog:

2016-03-31  Wei-cheng Wang  <cole945@gmail.com>
	    Marcin Kocielnicki  <koriakin@0x04.net>

	PR/17221
	* linux-ppc-low.c (emit_insns): New function.
	(__EMIT_ASM, _EMIT_ASM, EMIT_ASM): New macros.
	(ppc_emit_prologue): New function.
	(ppc_emit_epilogue): New function.
	(ppc_emit_add): New function.
	(ppc_emit_sub): New function.
	(ppc_emit_mul): New function.
	(ppc_emit_lsh): New function.
	(ppc_emit_rsh_signed): New function.
	(ppc_emit_rsh_unsigned): New function.
	(ppc_emit_ext): New function.
	(ppc_emit_zero_ext): New function.
	(ppc_emit_log_not): New function.
	(ppc_emit_bit_and): New function.
	(ppc_emit_bit_or): New function.
	(ppc_emit_bit_xor): New function.
	(ppc_emit_bit_not): New function.
	(ppc_emit_equal): New function.
	(ppc_emit_less_signed): New function.
	(ppc_emit_less_unsigned): New function.
	(ppc_emit_ref): New function.
	(ppc_emit_const): New function.
	(ppc_emit_reg): New function.
	(ppc_emit_pop): New function.
	(ppc_emit_stack_flush): New function.
	(ppc_emit_swap): New function.
	(ppc_emit_stack_adjust): New function.
	(ppc_emit_call): New function.
	(ppc_emit_int_call_1): New function.
	(ppc_emit_void_call_2): New function.
	(ppc_emit_if_goto): New function.
	(ppc_emit_goto): New function.
	(ppc_emit_eq_goto): New function.
	(ppc_emit_ne_goto): New function.
	(ppc_emit_lt_goto): New function.
	(ppc_emit_le_goto): New function.
	(ppc_emit_gt_goto): New function.
	(ppc_emit_ge_goto): New function.
	(ppc_write_goto_address): New function.
	(ppc_emit_ops_impl): New static variable.
	(ppc64v1_emit_prologue): New function.
	(ppc64v2_emit_prologue): New function.
	(ppc64_emit_epilogue): New function.
	(ppc64_emit_add): New function.
	(ppc64_emit_sub): New function.
	(ppc64_emit_mul): New function.
	(ppc64_emit_lsh): New function.
	(ppc64_emit_rsh_signed): New function.
	(ppc64_emit_rsh_unsigned): New function.
	(ppc64_emit_ext): New function.
	(ppc64_emit_zero_ext): New function.
	(ppc64_emit_log_not): New function.
	(ppc64_emit_bit_and): New function.
	(ppc64_emit_bit_or): New function.
	(ppc64_emit_bit_xor): New function.
	(ppc64_emit_bit_not): New function.
	(ppc64_emit_equal): New function.
	(ppc64_emit_less_signed): New function.
	(ppc64_emit_less_unsigned): New function.
	(ppc64_emit_ref): New function.
	(ppc64_emit_const): New function.
	(ppc64v1_emit_reg): New function.
	(ppc64v2_emit_reg): New function.
	(ppc64_emit_pop): New function.
	(ppc64_emit_stack_flush): New function.
	(ppc64_emit_swap): New function.
	(ppc64v1_emit_call): New function.
	(ppc64v2_emit_call): New function.
	(ppc64v1_emit_int_call_1): New function.
	(ppc64v2_emit_int_call_1): New function.
	(ppc64v1_emit_void_call_2): New function.
	(ppc64v2_emit_void_call_2): New function.
	(ppc64_emit_if_goto): New function.
	(ppc64_emit_eq_goto): New function.
	(ppc64_emit_ne_goto): New function.
	(ppc64_emit_lt_goto): New function.
	(ppc64_emit_le_goto): New function.
	(ppc64_emit_gt_goto): New function.
	(ppc64_emit_ge_goto): New function.
	(ppc64v1_emit_ops_impl): New static variable.
	(ppc64v2_emit_ops_impl): New static variable.
	(ppc_emit_ops): New function.
	(linux_low_target): Wire in ppc_emit_ops.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] IPA: Add alloc_jump_pad_buffer target hook.
@ 2016-03-31 14:33 sergiodj+buildbot
  2016-03-31 15:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 14:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a13c46966d308297a1273e35ccc807a3912d573d ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a13c46966d308297a1273e35ccc807a3912d573d

IPA: Add alloc_jump_pad_buffer target hook.

Targets may have various requirements on the required location of the jump
pad area.  Currently IPA allocates it at the lowest possible address,
so that it is reachable by branches from the executable.  However, this
fails on powerpc, which has executable link address (0x10000000) much
larger than branch reach (+/- 32MiB).

This makes jump pad buffer allocation a target hook instead.  The current
implementations are as follows:

- i386 and s390: Branches can reach anywhere, so just mmap it.  This
  avoids the linear search dance.
- x86_64: Branches have +/-2GiB of reach, and executable is loaded low,
  so just call mmap with MAP_32BIT.  Likewise avoids the linear search.
- aarch64: Branches have +-128MiB of reach, executable loaded at 4MiB.
  Do a linear search from 4MiB-size downwards to page_size.
- s390x: Branches have +-4GiB of reach, executable loaded at 2GiB.
  Do like on aarch64.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-ipa.c: Add <sys/mman.h> and <sys/auxv.h> includes.
	(alloc_jump_pad_buffer): New function.
	* linux-amd64-ipa.c: Add <sys/mman.h> include.
	(alloc_jump_pad_buffer): New function.
	* linux-i386-ipa.c (alloc_jump_pad_buffer): New function.
	* linux-s390-ipa.c: Add <sys/mman.h> and <sys/auxv.h> includes.
	(alloc_jump_pad_buffer): New function.
	* tracepoint.c (getauxval) [!HAVE_GETAUXVAL]: New function.
	(initialize_tracepoint): Delegate to alloc_jump_pad_buffer.
	* tracepoint.h (alloc_jump_pad_buffer): New prototype.
	(getauxval) [!HAVE_GETAUXVAL]: New prototype.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] python: Use console format for output of gdb.execute command
@ 2016-03-31 12:58 sergiodj+buildbot
  2016-03-31 13:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-31 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7ea3ec7c623be0b9be1eaf4929794652a84be11 ***

Author: Catalin Udma <catalin.udma@freescale.com>
Branch: master
Commit: e7ea3ec7c623be0b9be1eaf4929794652a84be11

python: Use console format for output of gdb.execute command

When gdb is started in MI mode, the output of gdb.execute
command is in MI-format in case when it is executed from python stop
handler while for all other cases the output is in console-format.

To assure consistent output format, this is fixed by using the console
format for all python gdb command executions.

PR python/19743

gdb/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

	PR python/19743
	* python/python.c (execute_gdb_command): Use console uiout
	when executing gdb command.
	* utils.c (restore_ui_out_closure): New structure.
	(do_restore_ui_out): New function.
	(make_cleanup_restore_ui_out): Likewise.
	* utils.h (make_cleanup_restore_ui_out): Declare.

gdb/testsuite/ChangeLog:
2016-03-31  Catalin Udma  <catalin.udma@freescale.com>

	PR python/19743
	* gdb.python/py-mi-events-gdb.py: New file.
	* gdb.python/py-mi-events.c: New file.
	* gdb.python/py-mi-events.exp: New file.

Signed-off-by: Catalin Udma <catalin.udma@freescale.com>


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Check func against 0 rather than NULL
@ 2016-03-30 17:59 sergiodj+buildbot
  2016-03-30 19:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-30 17:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb3f3d25c3cbf561d33b258ff11fd8139f6ad75d ***

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

Check func against 0 rather than NULL

Variable 'func''s type is CORE_ADDR, so it should be compared with 0
rather than NULL.  This causes a build error.

This patch fixes this.

gdb:

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

	* arm-tdep.c (arm_epilogue_frame_this_id): Check 'func' against
	0 rather than NULL.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] Cleanup AUX register names.
@ 2016-03-30 14:57 sergiodj+buildbot
  2016-03-30 15:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-30 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd05ac5f5e7cb753ae6772edcf4dfba5b416a169 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: bd05ac5f5e7cb753ae6772edcf4dfba5b416a169

[ARC] Cleanup AUX register names.

opcodes/
2016-03-30  Claudiu Zissulescu  <claziss@synopsys.com>

        * arc-regs.h (IC_RAM_ADDRESS, IC_TAG, IC_WP, IC_DATA, CONTROL0)
        (AX2, AY2, MX2, MY2, AY0, AY1, DC_RAM_ADDR, DC_TAG, CONTROL1)
        (RTT): Remove duplicate.
        (LCDINSTR, LCDDATA, LCDSTAT, CC_*, PCT_COUNT*, PCT_SNAP*)
        (PCT_CONFIG*): Remove.
        (D1L, D1H, D2H, D2L): Define.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver: Handle 'v' packet while processing qSymbol.
@ 2016-03-30  0:32 sergiodj+buildbot
  2016-03-30 10:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-30  0:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28170b88cc8b40fdea2b065dafe6e1872a47ee4e ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 28170b88cc8b40fdea2b065dafe6e1872a47ee4e

gdbserver: Handle 'v' packet while processing qSymbol.

On powerpc64, qSymbol query may require gdb to read a function
descriptor, sending a vFile packet to gdbserver.  Thus, we need
to handle 'v' packet in look_up_one_symbol.

vFile replies may be quite long, and require reallocating own_buf.
Since handle_v_requests assumes the buffer is the static global own_buf
from server.c and reallocates it, we need to make own_buf global and
use it from look_up_one_symbol instead of using our own auto variable.
I've also done the same change in relocate_instruction, just in case.

On gdb side, in remote_check_symbols, rs->buf may be clobbered by vFile
handling, yet we need its contents for the reply (the symbol name is
stored there).  Allocate a new buffer instead.

This broke fast tracepoints on powerpc64, due to errors in reading IPA
symbols.

gdb/ChangeLog:

	* remote.c (remote_check_symbols): Allocate own buffer for reply.

gdbserver/ChangeLog:

	* remote-utils.c (look_up_one_symbol): Remove own_buf, handle 'v'
	packets.
	(relocate_instruction): Remove own_buf.
	* server.c (own_buf): Make global.
	(handle_v_requests): Make global.
	* server.h (own_buf): New declaration.
	(handle_v_requests): New prototype.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver/s390: Add fast tracepoint support.
@ 2016-03-29 22:02 sergiodj+buildbot
  2016-03-29 23:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 22:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT abd9baf9c61a76537766c81e235a4a5a49b7dee3 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: abd9baf9c61a76537766c81e235a4a5a49b7dee3

gdbserver/s390: Add fast tracepoint support.

Fast tracepoints will only work on 6-byte intructions, and assume at least
a z900 CPU.  s390 also has 4-byte jump instructions, which also work on
pre-z900, but their range is limitted to +-64kiB, which is not very useful
(and wouldn't work at all with current jump pad allocation).

There's a little problem with s390_relocate_instruction function: it
converts BRAS/BRASL instructions to LARL of the return address + JG
to the target address.  On 31-bit, this sets the high bit of the target
register to 0, while BRAS/BRASL would set it to 1.  While this is not
a problem when the result is only used to address memory, it could
possibly break something that expects to compare such addresses for
equality without first masking the bit off.  In particular, I'm not sure
whether leaving the return address high bit unset is ABI-compliant
(could confuse some unwinder?).  If that's a problem, it could be fixed
by handling it in the jump pad (since at that point we can just modify
the GPRs in the save area without having to worry about preserving
CCs and only having that one GPR to work with - I'm not sure if it's
even possible to set the high bit with such constraints).

gdb/gdbserver/ChangeLog:

	PR 18377
	* Makefile.in: Add s390 IPA files.
	* configure.srv: Build IPA for s390.
	* linux-s390-ipa.c: New file.
	* linux-s390-low.c: New includes - inttypes.h and linux-s390-tdesc.h.
	(init_registers_s390_linux32): Move declaration to linux-s390-tdesc.h.
	(tdesc_s390_linux32): Likewise.
	(init_registers_s390_linux32v1): Likewise.
	(tdesc_s390_linux32v1): Likewise.
	(init_registers_s390_linux32v2): Likewise.
	(tdesc_s390_linux32v2): Likewise.
	(init_registers_s390_linux64): Likewise.
	(tdesc_s390_linux64): Likewise.
	(init_registers_s390_linux64v1): Likewise.
	(tdesc_s390_linux64v1): Likewise.
	(init_registers_s390_linux64v2): Likewise.
	(tdesc_s390_linux64v2): Likewise.
	(init_registers_s390_te_linux64): Likewise.
	(tdesc_s390_te_linux64): Likewise.
	(init_registers_s390_vx_linux64): Likewise.
	(tdesc_s390_vx_linux64): Likewise.
	(init_registers_s390_tevx_linux64): Likewise.
	(tdesc_s390_tevx_linux64): Likewise.
	(init_registers_s390x_linux64): Likewise.
	(tdesc_s390x_linux64): Likewise.
	(init_registers_s390x_linux64v1): Likewise.
	(tdesc_s390x_linux64v1): Likewise.
	(init_registers_s390x_linux64v2): Likewise.
	(tdesc_s390x_linux64v2): Likewise.
	(init_registers_s390x_te_linux64): Likewise.
	(tdesc_s390x_te_linux64): Likewise.
	(init_registers_s390x_vx_linux64): Likewise.
	(tdesc_s390x_vx_linux64): Likewise.
	(init_registers_s390x_tevx_linux64): Likewise.
	(tdesc_s390x_tevx_linux64): Likewise.
	(have_hwcap_s390_vx): New static variable.
	(s390_arch_setup): Fill have_hwcap_s390_vx.
	(s390_get_thread_area): New function.
	(s390_ft_entry_gpr_esa): New const.
	(s390_ft_entry_gpr_zarch): New const.
	(s390_ft_entry_misc): New const.
	(s390_ft_entry_fr): New const.
	(s390_ft_entry_vr): New const.
	(s390_ft_main_31): New const.
	(s390_ft_main_64): New const.
	(s390_ft_exit_fr): New const.
	(s390_ft_exit_vr): New const.
	(s390_ft_exit_misc): New const.
	(s390_ft_exit_gpr_esa): New const.
	(s390_ft_exit_gpr_zarch): New const.
	(append_insns): New function.
	(s390_relocate_instruction): New function.
	(s390_install_fast_tracepoint_jump_pad): New function.
	(s390_get_min_fast_tracepoint_insn_len): New function.
	(s390_get_ipa_tdesc_idx): New function.
	(struct linux_target_ops): Wire in the above functions.
	(initialize_low_arch) [!__s390x__]: Don't initialize s390x tdescs.
	* linux-s390-tdesc.h: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver/s390: Switch on tracepoint support.
@ 2016-03-29 21:56 sergiodj+buildbot
  2016-03-29 22:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4105d04e19efdf89d0fa56b62675d7d7ee82a9b ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: a4105d04e19efdf89d0fa56b62675d7d7ee82a9b

gdbserver/s390: Switch on tracepoint support.

Also adds s390 support to gdb.trace testsuite.

gdb/gdbserver/ChangeLog:

	* linux-s390-low.c (s390_supports_tracepoints): New function.
	(struct linux_target_ops): Fill supports_tracepoints hook.

gdb/testsuite/ChangeLog:

	* gdb.trace/ftrace.exp: Set arg0exp for s390.
	* gdb.trace/mi-trace-frame-collected.exp: Expect 4 registers on s390.
	* gdb.trace/mi-trace-unavailable.exp: Set pcnum for s390, add gpr0num
	variable for GPR 0 instead of assuming it is register 0.
	* gdb.trace/trace-common.h: Add s390 fast tracepoint placeholder.
	* lib/trace-support.exp: Add s390 registers.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] Fix typo in extension instruction name.
@ 2016-03-29 17:29 sergiodj+buildbot
  2016-03-29 17:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9885948fc910a77d04f27a7683f5edd0989d818a ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 9885948fc910a77d04f27a7683f5edd0989d818a

[ARC] Fix typo in extension instruction name.

opcodes/
2016-03-29  Claudiu Zissulescu  <claziss@synopsys.com>

        * arc-ext-tbl.h (dsp_fp_i2flt): Fix typo.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Compile gdb.arch/arm-neon.exp with debug info
@ 2016-03-29 14:25 sergiodj+buildbot
  2016-03-29 14:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 14:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfa6adb959345850305d2f3e8b581149a066c4f8 ***

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

Compile gdb.arch/arm-neon.exp with debug info

Pass "debug" to prepare_for_testing otherwise, some tests fail.

gdb/testsuite:

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

	* gdb.arch/arm-neon.exp: Pass debug to prepare_for_testing.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Tidy up AArch64 simulator code.
@ 2016-03-29 10:50 sergiodj+buildbot
  2016-03-29 11:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-29 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef0d8ffc45aa32ed1e49051a344fa6c8cff583f4 ***

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

Tidy up AArch64 simulator code.

	* cpustate.c: Remove space after asterisk in function parameters.
	* decode.h (greg): Delete unused function.
	(vreg, shift, extension, scaling, writeback, condcode): Likewise.
	* simulator.c: Use INSTR macro in more places.
	(HALT_NYI): Use sim_io_eprintf in place of fprintf.
	Remove extraneous whitespace.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PE/COFF regression in base of code and data calculation
@ 2016-03-29  5:59 sergiodj+buildbot
  2016-03-29  6:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-29  5:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2b4fc913bad3b6a6e4b00b11c7c75268892150d ***

Author: Toni Spets <toni.spets@iki.fi>
Branch: master
Commit: e2b4fc913bad3b6a6e4b00b11c7c75268892150d

PE/COFF regression in base of code and data calculation

	PR 19878
	* coffcode.h (coff_write_object_contents): Revert accidental
	2014-11-10 change.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add quotation mark in test message
@ 2016-03-24 10:29 sergiodj+buildbot
  2016-03-24 11:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-24 10:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfa3faca36ccd86cf300f59b4f482c02e3e0518b ***

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

Add quotation mark in test message

I happen to see a quotation mark is missing the following test,

 gdb_test "break $end_location" \
     "Breakpoint $decimal at .* line $end_location\." \
     set breakpoint at end of main"

so the test result is

PASS: gdb.reverse/break-reverse.exp: set

This patch is to add the missing quotation mark back, and the test
result becomes

PASS: gdb.reverse/break-reverse.exp: set breakpoint at end of main

gdb/testsuite:

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

	* gdb.reverse/break-reverse.exp: Add quotation mark in the
	test message.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Attribute with DW_FORM_flag_present
@ 2016-03-22 12:26 sergiodj+buildbot
  2016-03-22 12:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-22 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97fbc7e3ca781b8d95ed8591c6ee65f2d8a798a ***

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

Attribute with DW_FORM_flag_present

	PR 19850
	* dwarf2.c (read_attribute_value): Skip info_ptr check for
	DW_FORM_flag_present.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Restore v850-rh850 as a recognised v850 architecture name for backwards compatibility.
@ 2016-03-22 11:38 sergiodj+buildbot
  2016-03-22 12:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-22 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96254e5c28ebcaaa89b4bdc24eab0a546dd269f2 ***

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

Restore v850-rh850 as a recognised v850 architecture name for backwards compatibility.

bfd	* cpu-v850_rh850.c (arch_info_struct): Restore v850-rh850 as an
	architecture name for backwards compatibility.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add -Wstack-usage to the gcc warning flags list, but only if using a sufficiently recent version of gcc.
@ 2016-03-22  9:46 sergiodj+buildbot
  2016-03-22 10:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-22  9:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9780e045073b1719a7a4c6cbe00e4aa7525bd180 ***

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

Add -Wstack-usage to the gcc warning flags list, but only if using a sufficiently recent version of gcc.

bfd	* warning.m4 (GCC_WARN_CFLAGS): Only add -Wstack-usage if using a
	sufficiently recent version of GCC.
	* configure: Regenerate.

others	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Make sparc_software_single_step static
@ 2016-03-18 15:45 sergiodj+buildbot
  2016-03-19 17:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c3f22346dd632201807c0718d5281ed1eea329f ***

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

Make sparc_software_single_step static

sparc_software_single_step is not used out of sparc-tdep.c, so this
patch makes it static.

gdb:

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

	* sparc-tdep.c (sparc_software_single_step): Make it static.
	* sparc-tdep.h (sparc_software_single_step): Remove declaration.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix generation of as.1 manual page so that it can be converted to DocBook format.
@ 2016-03-18 13:21 sergiodj+buildbot
  2016-03-18 23:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-18 13:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6387924ae329fe2a89abb48b9868a340e23a9630 ***

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

Fix generation of as.1 manual page so that it can be converted to DocBook format.

gas	* doc/as.texinfo: Place the target specific command line options
	into their own man page section.

etc	* texi2pod.pl: Add TARGET to the list of recognised man page
	sections.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add mips and s390 build targets for gold.
@ 2016-03-17 23:01 sergiodj+buildbot
  2016-03-18 12:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 23:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea01647092eefeca9336b36809962ff097306b41 ***

Author: Cary Coutant <ccoutant@gmail.com>
Branch: master
Commit: ea01647092eefeca9336b36809962ff097306b41

Add mips and s390 build targets for gold.

	* configure.ac: Add mips and s390 to the gold target check.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Add syscall info for syscalls up to 374
@ 2016-03-17 10:26 sergiodj+buildbot
  2016-03-18  6:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-17 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bba960fc4b3f330ec75ef7d3581aaaed4c560c49 ***

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

S390: Add syscall info for syscalls up to 374

Represent new Linux syscalls for s390 and s390x in GDB's syscall info.
Add the syscalls from 355 (userfaultfd) up to 374 (mlock2) as well as
the previously reserved NUMA syscalls 268-270, 287, and 310.

gdb/ChangeLog:

	* syscalls/s390-linux.xml: Add NUMA syscalls and new syscalls up
	to 374.
	* syscalls/s390x-linux.xml: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] linux-record: Simplify with record_mem_at_reg()
@ 2016-03-17  9:47 sergiodj+buildbot
  2016-03-18  4:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fd0888aff1abfa6e06cfa48164e72c48072ac79 ***

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

linux-record: Simplify with record_mem_at_reg()

The function record_linux_system_call() often records a memory area
whose address is contained in a register.  So far this required two
function calls: one for fetching the register value, and another one for
recording the memory area.  These two function calls are now merged into
a new local helper function, and all occurrences are adjusted.  This
reduces the source code and makes it more readable.

gdb/ChangeLog:

	* linux-record.c (record_mem_at_reg): New helper function.
	(record_linux_system_call): Exploit new helper function where
	applicable.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2
@ 2016-03-17  9:19 sergiodj+buildbot
  2016-03-18  2:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-17  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afdab9165435e17169b4984eeb29ea751319aa74 ***

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

linux-record: Fix bad fall-through for pipe/pipe2

This patch added handling for some syscalls to linux-record.c:

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

But for both `pipe' and `pipe2' the patch lacks a statement after an
`if', such that the following `break' is interpreted as the `if'-body
instead.

This adds the missing (return-) statements for the conditionals.

gdb/ChangeLog:

	* linux-record.c (record_linux_system_call): Add missing return
	statements to handling of pipe and pipe2 syscalls.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Process record: Fix arm-linux syscall arguments
@ 2016-03-16 19:42 sergiodj+buildbot
  2016-03-16 21:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b94a855beef3a301509dfac6bf5446d1953524b ***

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

Process record: Fix arm-linux syscall arguments

Arguments are passed in r0-r6 on arm linux syscall (both EABI and OABI).
This patch is to set arm_linux_record_tdep.arg{1-7} to the right
register number.

This patch fixes the following test failures...

-FAIL: gdb.reverse/getresuid-reverse.exp: check ruid record
-FAIL: gdb.reverse/getresuid-reverse.exp: check rgid record
-FAIL: gdb.reverse/pipe-reverse.exp: check pipe record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/readv-reverse.exp: check readv record
-FAIL: gdb.reverse/waitpid-reverse.exp: check waitpid record

gdb:

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

	* arm-linux-tdep.c (arm_linux_init_abi): Fix
	arm_linux_record_tdep.arg1, arm_linux_record_tdep.arg2 and
	arm_linux_record_tdep.arg3.  Set arm_linux_record_tdep.arg4,
	arm_linux_record_tdep.arg5, arm_linux_record_tdep.arg6, and
	arm_linux_record_tdep.arg7.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build.
@ 2016-03-16 17:48 sergiodj+buildbot
  2016-03-17 21:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 17:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfeeb14b8468ab3f60d719f2cde697d1b537eba8 ***

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

xml-tdesc.c (tdesc_start_enum): Fix c++ build.

gdb/ChangeLog:

	* xml-tdesc.c (tdesc_start_enum): Fix c++ build.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions
@ 2016-03-16 16:29 sergiodj+buildbot
  2016-03-17  1:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-16 16:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc9333013723880949a1e07a3e04bdbc1a3c3032 ***

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

[ARM] Support ARMv8.2 FP16 simd instructions

gas/
	* config/tc-arm.c (N_S_32): New.
	(N_F_16_32): Likewise.
	(N_SUF_32): Support N_F16.
	(N_IF_32): Likewise.
	(neon_dyadic_misc): Likewise.
	(do_neon_cmp): Likewise.
	(do_neon_cmp_inv): Likewise.
	(do_neon_mul): Likewise.
	(do_neon_fcmp_absolute): Likewise.
	(do_neon_step): Likewise.
	(do_neon_abs_neg): Likewise.
	(CVT_FLAVOR_VAR): Likewise.
	(do_neon_cvt_1): Likewise.
	(do_neon_recip_est): Likewise.
	(do_vmaxnm): Likewise.
	(do_vrint_1): Likewise.
	(neon_check_type): Check architecture support for FP16 extension.
	(insns): Update comments.
	* testsuite/gas/arm/armv8-2-fp16-simd.s: New test source.
	* testsuite/gas/arm/armv8-2-fp16-simd.d: New testcase for arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-thumb.d: Likewise for thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.d: New rejection test for
	arm mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning-thumb.d: Likewise for
	thumb mode.
	* testsuite/gas/arm/armv8-2-fp16-simd-warning.l: New expected rejection
	error file.

opcode/
	* arm-dis.c (neon_opcodes): Support new FP16 instructions.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR gdb/19676: Disable displaced stepping if /proc not mounted
@ 2016-03-15 16:47 sergiodj+buildbot
  2016-03-15 17:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-15 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16b4184277c4ad5b4a20278060fd3f6259d1ed49 ***

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

Fix PR gdb/19676: Disable displaced stepping if /proc not mounted

On GNU/Linux archs that support displaced stepping, if /proc is not
mounted, GDB gets stuck not able to step past breakpoints:

 (gdb) c
 Continuing.
 dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2163
 2163      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot find AT_ENTRY auxiliary vector entry.
 (gdb) c
 Continuing.
 dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=<optimized out>) at rtld.c:2163
 2163      LIBC_PROBE (init_complete, 2, LM_ID_BASE, r);
 Cannot find AT_ENTRY auxiliary vector entry.
 (gdb)

That's because GDB can't figure out where the scratch pad is.

This is a regression introduced by the earlier changes to make the
Linux native target always work in non-stop mode.

This commit makes GDB detect the case and fallback to stepping over
breakpoints in-line.

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

	PR gdb/19676
	* infrun.c (displaced_step_prepare): Also disable displaced
	stepping on NOT_SUPPORTED_ERROR.
	* linux-tdep.c (linux_displaced_step_location): If reading auxv
	fails, throw NOT_SUPPORTED_ERROR instead of generic error.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Regenerate bfd-in2.h
@ 2016-03-14 20:28 sergiodj+buildbot
  2016-03-14 20:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbe48798204180aa11c55e5377c1e23700b9c280 ***

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

Regenerate bfd-in2.h

	* bfd-in2.h: Regenerated.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test
@ 2016-03-14 16:56 sergiodj+buildbot
  2016-03-14 17:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-14 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa4ff313317d6234bbd818b09332e7d85349a56a ***

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

gdb.base/default.exp: Add missing $_as_string to "show convenience" test

When adding the $_as_string convenience function, I missed a new test
failure in default.exp.  The tests lists the convenience functions, so
$_as_string should be added to the expected list.

Fixes:

+FAIL: gdb.base/default.exp: show convenience ($_caller_is = <internal function _caller_is> not found)

gdb/testsuite/ChangeLog:

	* gdb.base/default.exp: Add $_as_string to the list of expected
	convenience functions.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb/s390: Fill gen_return_address hook.
@ 2016-03-13 10:06 sergiodj+buildbot
  2016-03-13 10:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-13 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70104a908773d7df0af48ca5c48856886bafea13 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 70104a908773d7df0af48ca5c48856886bafea13

gdb/s390: Fill gen_return_address hook.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_gen_return_address): New function.
	(s390_gdbarch_init): Fill gen_return_address hook.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb/s390: Fill pseudo register agent expression hooks.
@ 2016-03-11 10:15 sergiodj+buildbot
  2016-03-11 11:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-11 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4b3e547d50b01dcf909498119ff6c0af482f2c8 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: c4b3e547d50b01dcf909498119ff6c0af482f2c8

gdb/s390: Fill pseudo register agent expression hooks.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_ax_pseudo_register_collect): New function.
	(s390_ax_pseudo_register_push_stack): New function.
	(s390_gdbarch_init): Fill ax_pseudo_register_collect and
	ax_pseudo_register_push_stack hooks.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add $_as_string convenience function
@ 2016-03-10 22:34 sergiodj+buildbot
  2016-03-11  6:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-10 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2f3ccb9f81255fd1b4f877600f39979c2d7ece5 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: f2f3ccb9f81255fd1b4f877600f39979c2d7ece5

Add $_as_string convenience function

This patch is a follow-up to "Add printf format specifier for printing
enumerator":

  https://sourceware.org/ml/gdb-patches/2016-02/msg00144.html

Instead of having a solution specific to the printf command, Pedro
suggested adding a general purpose function $_as_string() that would
cover this use case and more.

So, in order to print the textual label of an enum, one can use:

  (gdb) printf "Visiting node of type %s\n", $_as_string(node)
  Visiting node of type NODE_INTEGER

gdb/ChangeLog:

	* data-directory/Makefile.in (PYTHON_FILE_LIST): Install
	gdb/function/as_string.py.
	* python/lib/gdb/function/as_string.py: New file.
	* NEWS: Mention the new $_as_string function.

gdb/testsuite/ChangeLog:

	* gdb.python/py-as-string.exp: New file.
	* gdb.python/py-as-string.c: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Convenience Functions): Document $_as_string.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb.trace/tfind.exp: Force call via global entry point on ppc64le.
@ 2016-03-10  1:30 sergiodj+buildbot
  2016-03-10  6:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-10  1:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f77198c878424891f11d6550370f8d9382f412de ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: f77198c878424891f11d6550370f8d9382f412de

gdb.trace/tfind.exp: Force call via global entry point on ppc64le.

tfind.exp sets a breakpoint on *gdb_recursion_test, which is the global
entry point on ppc64le, and won't be hit, since the call uses
the local entry.  Fix by calling the function via a pointer in a global
variable, forcing use of the global entry.

This patch is a slightly modified hunk extracted from
https://sourceware.org/ml/gdb-patches/2015-07/msg00353.html

gdb/testsuite/ChangeLog:

2016-03-09  Wei-cheng Wang  <cole945@gmail.com>
	    Marcin Kocielnicki  <koriakin@0x04.net>

	* gdb.trace/actions.c (gdb_recursion_test_fp): New typedef.
	(gdb_recursion_test_ptr): New global variable.
	(gdb_recursion_test): Call gdb_recursion_test_ptr instead of
	gdb_recursion_test.
	(gdb_c_test): Ditto.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.
@ 2016-03-09 22:03 sergiodj+buildbot
  2016-03-10  5:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba84e0da35d29dd8969a4bcdd84e3eaa48927a84 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: ba84e0da35d29dd8969a4bcdd84e3eaa48927a84

gdb.trace/change-loc.exp: Don't depend on tracepoint ordering.

powerpc (32-bit) loads shared libraries below the main executable, so
the PENDING location is the first one, which the current regex doesn't
match.  Split it into two tests instead, one looking for the pending
tracepoint location, and the other for two installed locations.

gdb/testsuite/ChangeLog:

	* gdb.trace/change-loc.exp: Don't depend on tracepoint location
	ordering.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: fix doc string of target_can_use_hardware_watchpoint.
@ 2016-03-09 21:46 sergiodj+buildbot
  2016-03-11  2:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2343b78a778af9fe496c521bd49ba027cb8b48ae ***

Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Branch: master
Commit: 2343b78a778af9fe496c521bd49ba027cb8b48ae

gdb: fix doc string of target_can_use_hardware_watchpoint.

gdb/ChangeLog

2016-03-09  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* target.h: Fix doc string of target_can_use_hardware_watchpoint.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Command line input handling TLC
@ 2016-03-09 21:19 sergiodj+buildbot
  2016-03-11  0:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 21:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b69d38afdea34e4fecab5ea47ffe1e594e0b6233 ***

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

Command line input handling TLC

I didn't manage to usefully split this further into smaller
independent pieces, so:

 - Use "struct buffer" more.

 - Split out the responsibility of composing a complete command line
   from multiple input lines split with backslash

    (
    E.g.:

       (gdb) print \
       1 + \
       2
       $1 = 3
       (gdb)
    )

   to a separate function.  Note we don't need the separate
   readline_input_state and more_to_come globals at all.  They were
   just obfuscating the logic.

 - Factor out the tricky mostly duplicated code in
   command_line_handler and command_line_input.

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

	* event-top.c (more_to_come): Delete.
	(struct readline_input_state): Delete.
	(readline_input_state): Delete.
	(get_command_line_buffer): New function.
	(command_handler): Update comments.  Don't handle NULL commands
	here.  Do not execute commented lines.
	(command_line_append_input_line): New function.
	(handle_line_of_input): New function, partly based on
	command_line_handler and command_line_input.
	(command_line_handler): Rewrite.
	* event-top.h (command_handler): New declaration.
	(command_loop): Defer command execution to command_handler.
	(command_line_input): Update comments.  Simplify, using struct
	buffer and handle_line_of_input.
	* top.h (struct buffer): New forward declaration.
	(handle_line_of_input): New declaration.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use struct buffer in gdb_readline_no_editing_callback
@ 2016-03-09 20:57 sergiodj+buildbot
  2016-03-10 22:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 187212b3c1aa55d9a5b544a6af3af0b5ce457403 ***

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

Use struct buffer in gdb_readline_no_editing_callback

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

	* event-top.c: Include buffer.h.
	(gdb_readline_no_editing_callback): Use struct buffer instead
	of xrealloc.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb_readline -> gdb_readline_no_editing
@ 2016-03-09 20:36 sergiodj+buildbot
  2016-03-10 19:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5c136ea94f21e5ff968d5b402494611464c7b31 ***

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

gdb_readline -> gdb_readline_no_editing

Name this such that it's clearer that this is not a wrapper for the
real readline, but instead a replacement that provides no command line
editing features.

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

	* defs.h (gdb_readline): Delete declaration.
	* top.c (gdb_readline): Rename to ...
	(gdb_readline_no_editing): ... this, and make static.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Update prompt_for_continue comments
@ 2016-03-09 20:27 sergiodj+buildbot
  2016-03-10 17:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 720d2e96b424bb4bb1f7021f86763ff3df078e2b ***

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

Update prompt_for_continue comments

These comments are out of date -- we no longer call gdb_readline.  And
I think that mentioning the event loop is more useful here than
whatever GO32 issue had with gdb_readline, which may even no longer be
an issue.

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

	* utils.c (prompt_for_continue): Update comments.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Eliminate async_annotation_suffix
@ 2016-03-09 20:15 sergiodj+buildbot
  2016-03-10 15:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 608ff013aae02e3ac4687691db57bbcb8984fe18 ***

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

Eliminate async_annotation_suffix

The comments and existence of this global are a bit of misleading
obfuscation, since this is only ever used to print the prompt
annotation, and never changes.  Just hardcode "prompt" where
necessary, as done for most other annotations.

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

	* event-top.c (async_annotation_suffix): Delete.
	(top_level_prompt, command_line_handler): Don't use
	'async_annotation_suffix' and simplify.
	* event-top.h (async_annotation_suffix): Delete declaration.
	(init_main): Remove reference to 'async_annotation_suffix'.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback
@ 2016-03-09 20:06 sergiodj+buildbot
  2016-03-10 14:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 20:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c70061cf94691182484924c79cbbdd2203ef92d5 ***

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

gdb_readline2 -> gdb_readline_no_editing_callback

The "2" in "gdb_readline2" doesn't really convey much.  Rename for
clarity.

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

	* event-top.c (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this.
	(change_line_handler, stdin_event_handler)
	(gdb_setup_readline): Adjust.
	* event-top.h (gdb_readline2): Rename to ...
	(gdb_readline_no_editing_callback): ... this, and move closer to
	other readline-related declarations.
	* mi/mi-interp.c (mi_interpreter_resume): Adjust.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Garbage collect window_hook
@ 2016-03-09 19:54 sergiodj+buildbot
  2016-03-10 11:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a243832540cb3bd246192db1f0a4dfa44d92dcf ***

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

Garbage collect window_hook

I checked, and Insight doesn't set this.

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

	* top.c (window_hook): Delete.
	(command_loop): Remove references to window_hook.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Test issuing a command split in multiple lines with continuation chars
@ 2016-03-09 19:42 sergiodj+buildbot
  2016-03-10 10:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c32e87066a216dbcd9daa36100975a5ecb471bb9 ***

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

Test issuing a command split in multiple lines with continuation chars

I happened to break this locally and the testsuite didn't notice it.
Add some tests.

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

	* gdb.base/command-line-input.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb.trace/entry-values.exp: Fixes for powerpc64.
@ 2016-03-09 19:21 sergiodj+buildbot
  2016-03-10  7:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98fa59e9b06fa479cafb852ef87e5a9bfd87ae54 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 98fa59e9b06fa479cafb852ef87e5a9bfd87ae54

gdb.trace/entry-values.exp: Fixes for powerpc64.

On powerpc64, "disassemble foo" doesn't work properly on object files
(it can't process the relocations in .opd section) - instead, let's
link it into an executable and load that.

Also, backtrace displays .main, not main.  Accept both.

gdb/testsuite/ChangeLog:

	* gdb.trace/entry-values.exp: Link ${binfile}1.o to ${binfile}1 and
	use it for disassembly; accept .main in addition to main in backtrace.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb/rs6000: Read backchain as unsigned.
@ 2016-03-09 18:40 sergiodj+buildbot
  2016-03-10  3:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc2c4da8813b980a4e68272bb43583f4af6fe89c ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: cc2c4da8813b980a4e68272bb43583f4af6fe89c

gdb/rs6000: Read backchain as unsigned.

Previously, backchain was read as a signed quantity, resulting in
addresses like 0xfffffffffffeded0 instead of 0xfffeded0 returned by
unwinder on 32-bit powerpc.  While normally such addresses are masked
off, this causes problems for tracepoints, since 0xfffffffffffeded0
is considered unavailable.

Fixes a test failure in gdb.trace/entry-values.exp.

gdb/ChangeLog:

	* corefile.c (safe_read_memory_unsigned_integer): New function.
	* gdbcore.h (safe_read_memory_unsigned_integer): New prototype.
	* rs6000-tdep.c (rs6000_frame_cache): Read backchain as unsigned.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Recognize special jumps in prologue parser
@ 2016-03-09 16:41 sergiodj+buildbot
  2016-03-09 23:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc0e3f49c84055034cae31bba169100d107b28f4 ***

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

S390: Recognize special jumps in prologue parser

Functions compiled with the gcc option `-mhotpatch' may start with a
branch-never BRCL instruction as a 6-byte NOP.  And functions compiled
with `-mstack-size' contain a BRC instruction in their prologue that is
actually a conditional trap.  Both of these special jumps cause the
prologue parser to stop and yield bad unwinding results.

This change makes the prologue analyzer recognize such special jumps and
ignore them.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_analyze_prologue): Ignore BRC and BRCL
	instructions that do nothing or are conditional traps.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Add use of unavailable-stack frame ID
@ 2016-03-09 16:30 sergiodj+buildbot
  2016-03-09 22:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d53bec88f4c1576f74e918400aa2ccac2d129db ***

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

S390: Add use of unavailable-stack frame ID

When determining the frame ID of an inline frame, GDB currently asserts
that a valid ID of the underlying real frame is found, and that it does
not match outer_frame_id.  From inline_frame_this_id():

  /* For now, require we don't match outer_frame_id either (see
     comment above).  */
  gdb_assert (!frame_id_eq (*this_id, outer_frame_id));

However, this assertion may fail when the real frame's unwinder can not
determine the frame ID.  This happened on an s390x target with a binary
that lacked call frame information and also confused the prologue
analyzer, because then s390_frame_this_id() left the frame ID at its
default.

To fix this, this change enhances s390_frame_this_id such that an
unavailable-stack frame ID is built if no frame base can be determined
but the function address is available.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_prologue_frame_unwind_cache): Store
	frame func's PC in info->func before any other failure can occur.
	(s390_frame_this_id): Use frame_id_build_unavailable_stack if
	info->func has been filled out.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Avoid spaces in osabi names
@ 2016-03-09 16:19 sergiodj+buildbot
  2016-03-09 20:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7990f1690e9ef0471634c871c790f6cf706866d ***

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

Avoid spaces in osabi names

It's not possible today to select some of the osabis by name.
Specifically, those that have spaces in their names and then the first
word is ambiguous...

For example:
 (gdb) set osabi <TAB>
 [...]
 FreeBSD ELF
 FreeBSD a.out
 [...]
 (gdb) set osabi FreeBSD ELF
 Ambiguous item "FreeBSD ELF".

In reality, because "set osabi" is an enum command, that was
equivalent to trying "set osabi FreeBSD", which is then obviously
ambiguous, because of "FreeBSD ELF" and "FreeBSD a.out".

Also, even if the first word is not ambiguous, we actually ignore
whatever comes after the first word:

 (gdb) set osabi GNU/Linux
 (gdb) show osabi
 The current OS ABI is "GNU/Linux".
 The default OS ABI is "GNU/Linux".
 (gdb) set osabi Windows SomeNonsense
                         ^^^^^^^^^^^^
 (gdb) show osabi
 The current OS ABI is "Windows CE".
 The default OS ABI is "GNU/Linux".
 (gdb)

Fix this by avoiding spaces in osabi names.

We could instead make "set osabi" have a custom set hook, or
alternatively make the enum set hook (in cli-setshow.c) handle values
with spaces, but OTOH, I have a feeling that could cause trouble.
E.g., in cases where we might want to write more than one enum value
in the same line.  We could support quoting as workaround, but, not
sure we want that.  "No spaces" seems like a simpler rule.

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

	* osabi.c (gdb_osabi_names): Avoid spaces in osabi names.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix v850 bfd arch info printable names
@ 2016-03-09 15:59 sergiodj+buildbot
  2016-03-09 17:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b05e0a74b3fb21b56e821423b8a334e4be9cfe7 ***

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

Fix v850 bfd arch info printable names

Currently, it's not possible to manually set some of the v850 archs in
gdb:

 (gdb) set architecture v850<TAB>
 v850 (using old gcc ABI)
 v850-rh850
 v850e
 v850e (using old gcc ABI)
 v850e1
 [...]
 (gdb) set architecture v850 (using old gcc ABI)
 Ambiguous item "v850 (using old gcc ABI)".

The problem is that "set architecture" is a GDB "enum command", and
GDB only considers an enum value to be the string up until the first
space.  So writing "v850 (using old gcc ABI)" is the same as writing
"v850", and then that's not an unambiguous arch printable name prefix.

v850 is actually the only arch that has spaces in its printable name.
One can conveniently see that with e.g.:

 (gdb) set max-completions unlimited
 (gdb) complete set architecture
 ...

Rather than hack GDB into accepting this somehow, make v850 arch
printable names more like the printable names of the other archs, and
put the abi variant in the "machine" part, after a ':'.

We now get:

 (gdb) set architecture v850<TAB>
 v850:old-gcc-abi
 v850:rh850
 v850e
 v850e1
 v850e1:old-gcc-abi
 v850e2
 v850e2:old-gcc-abi
 [...]

And now "set architecture v850:old-gcc-abi" works as expected.

I ran the binutils/gas/ld testsuites, and found no regressions.  I
don't have a cross compiler handy, but I ran the gdb tests anyway,
which covers at least some snoke testing.

I think that the OUTPUT_ARCH in ld/scripttempl/v850.sc may have got
broken with the previous 2012 change, since I hacked v850_rh850.sc to
output "v850" and ld failed to grok it.  I think it only works if the
old GCC ABI is the configured v850 default ABI.  That's now fixed by
changing to use explicit v850:old-gcc-abi.

Also, this actually "fixes" an existing GDB test, which isn't likewise
expecting spaces in arch names, when GDB is configured for
--target=v850:

  (gdb) FAIL: gdb.xml/tdesc-arch.exp: read valid architectures

bfd/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* cpu-v850.c (N): Append ":old-gcc-abi" instead of " (using old
	gcc ABI)" to printable name.
	* cpu-v850_rh850.c (bfd_v850_rh850_arch): Use "v850:rh850" instead
	of "v850-rh850" as printable name.

ld/ChangeLog:
2016-03-09  Pedro Alves  <palves@redhat.com>

	* scripttempl/v850.sc: Use "v850:old-gcc-abi" as OUTPUT_ARCH.
	* scripttempl/v850_rh850.sc: Use "v850:rh850" as OUTPUT_ARCH.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols.
@ 2016-03-09 15:43 sergiodj+buildbot
  2016-03-09 16:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26c62da040fb9d602da269a3bdffdea13a4367c7 ***

Author: Leon Winter <winter-gcc@bfw-online.de>
Branch: master
Commit: 26c62da040fb9d602da269a3bdffdea13a4367c7

For COFF and COFF/PE targets, skip relocations against absolute symbols.

	PR ld/19623
	* cofflink.c (_bfd_coff_generic_relocate_section): Do not apply
	relocations against absolute symbols.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Allow zero length archive elements
@ 2016-03-09  6:37 sergiodj+buildbot
  2016-03-09  9:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  6:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03ee85837ec2e10f7b67c417b17ab3ffa97a98d2 ***

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

Allow zero length archive elements

	PR binutils/19775
	* coff-alpha.c (alpha_ecoff_openr_next_archived_file): Allow zero
	length elements in the archive.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [CRIS] Don't internal error if forced big endian
@ 2016-03-09  3:39 sergiodj+buildbot
  2016-03-09  7:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 114d7832b0e07452277d748c81d8bc0c5675a1bc ***

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

[CRIS] Don't internal error if forced big endian

This fixes:

  $ ./gdb -q -ex "set endian big" -ex "set architecture cris"
  The target is assumed to be big endian
  .../src/gdb/cris-tdep.c:4051: internal-error: cris_gdbarch_init: big endian byte order in info
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)

The "set cris-version" command can likewise cause internal errors.

The gdbarch init routine should be returning 0 to reject the
architecture instead of internal erroring on user input.

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

	* cris-tdep.c (cris_gdbarch_init): Return 0 if the info's byte
	order is BFD_ENDIAN_BIG or if the cris version is unsupported.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Assert that a floating type's length is at least as long as its format
@ 2016-03-09  3:19 sergiodj+buildbot
  2016-03-09  4:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  3:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b79497cb1cdc9b3053e5f0387bf3056c08c9bbdd ***

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

Assert that a floating type's length is at least as long as its format

This would have caught the HP/PA bug fixed in the previous patch:

 .../src/gdb/gdbtypes.c:4690: internal-error: arch_float_type: Assertion `len >= floatformat_totalsize_bytes (floatformats[0])' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

Tested on x86-64 Fedora 23, --enable-targets=all.

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

	* doublest.c (floatformat_totalsize_bytes): New function.
	(floatformat_from_type): Assert that the type's length is at least
	as long as the floatformat's totalsize.
	* doublest.h (floatformat_totalsize_bytes): New declaration.
	* gdbtypes.c (arch_float_type): Assert that the type's length is
	at least as long as the floatformat's totalsize.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix HP/PA GNU/Linux "long double" format
@ 2016-03-09  2:37 sergiodj+buildbot
  2016-03-09  3:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-09  2:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aacca8a7a9c7f93955fa9dbf796b030ffce1b956 ***

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

Fix HP/PA GNU/Linux "long double" format

This:

 $ ./gdb -ex "set architecture hppa1.0" -ex "set osabi GNU/Linux" -ex "ptype 1.0L"

Shows that HPPA/Linux support for long doubles is broken.  It causes
GDB to access memory out of bounds.  With Valgrind, we see:

 The target architecture is assumed to be hppa1.0
 ==4371== Invalid write of size 8
 ==4371==    at 0x4C2F21F: memset (vg_replace_strmem.c:1224)
 ==4371==    by 0x8451C4: convert_doublest_to_floatformat (doublest.c:362)
 ==4371==    by 0x845F86: floatformat_from_doublest (doublest.c:769)
 ==4371==    by 0x84628E: store_typed_floating (doublest.c:873)
 ==4371==    by 0x6A7C3D: value_from_double (value.c:3662)
 ==4371==    by 0x6AA211: evaluate_subexp_standard (eval.c:745)
 ==4371==    by 0x7F306D: evaluate_subexp_c (c-lang.c:716)
 ==4371==    by 0x6A8C6A: evaluate_subexp (eval.c:79)
 ==4371==    by 0x6A8E87: evaluate_type (eval.c:174)
 ==4371==    by 0x817B8D: whatis_exp (typeprint.c:456)
 ==4371==    by 0x817D68: ptype_command (typeprint.c:508)
 ==4371==    by 0x5F2977: do_cfunc (cli-decode.c:105)
 ==4371==  Address 0x8998d18 is 0 bytes after a block of size 8 alloc'd
 ==4371==    at 0x4C2AA98: calloc (vg_replace_malloc.c:711)
 ==4371==    by 0x8732B6: xcalloc (common-utils.c:83)
 ==4371==    by 0x8732F5: xzalloc (common-utils.c:93)
 ==4371==    by 0x6A37AF: allocate_value_contents (value.c:1036)
 ==4371==    by 0x6A37E5: allocate_value (value.c:1047)
 ==4371==    by 0x6A7BEE: value_from_double (value.c:3656)
 ==4371==    by 0x6AA211: evaluate_subexp_standard (eval.c:745)
 ==4371==    by 0x7F306D: evaluate_subexp_c (c-lang.c:716)
 ==4371==    by 0x6A8C6A: evaluate_subexp (eval.c:79)
 ==4371==    by 0x6A8E87: evaluate_type (eval.c:174)
 ==4371==    by 0x817B8D: whatis_exp (typeprint.c:456)
 ==4371==    by 0x817D68: ptype_command (typeprint.c:508)

The trouble is that hppa_linux_init_abi overrides the default
long_double_bit set by the generic hppa-tdep.c:

  set_gdbarch_long_double_bit (gdbarch, 128);
  set_gdbarch_long_double_format (gdbarch, floatformats_ia64_quad);

with:

  /* On hppa-linux, currently, sizeof(long double) == 8.  There has been
     some discussions to support 128-bit long double, but it requires some
     more work in gcc and glibc first.  */
  set_gdbarch_long_double_bit (gdbarch, 64);

which misses overriding the long_double_format, so we end with a weird
combination of:

  set_gdbarch_long_double_bit (gdbarch, 64);
  set_gdbarch_long_double_format (gdbarch, floatformats_ia64_quad);

Weird because floatformats_ia64_quad's totalsize is longer than 64-bits.

The floatformat conversion routines use the struct floatformat's
totalsize (in bits) to know how much to copy/convert, thus the buffer
overruns.

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

	* hppa-linux-tdep.c (hppa_linux_init_abi): Set the long double
	format to floatformats_ieee_double.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Handle local IFUNC symbols in shared object
@ 2016-03-08 17:47 sergiodj+buildbot
  2016-03-08 18:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1ed1c7d69e6656de213b12594e702afec31a66d ***

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

Handle local IFUNC symbols in shared object

Increment PLT reference count for locally defined local IFUNC symbols
in shared object since STT_GNU_IFUNC symbol must go through PLT even
if it is locally defined and undefined symbol may turn out to be a
STT_GNU_IFUNC symbol later.

bfd/

	PR ld/19784
	* elf32-i386.c (elf_i386_check_relocs): Increment PLT reference
	count for locally defined local IFUNC symbols in shared object.
	* elf64-x86-64.c (elf_x86_64_check_relocs): Likewise.

ld/

	PR ld/19784
	* testsuite/ld-i386/i386.exp: Remove pr19636-2e-nacl test.
	* testsuite/ld-i386/pr19636-2e-nacl.d: Moved to ...
	* testsuite/ld-i386/pr19636-2e.d: Here.  Remove notarget.
	* testsuite/ld-ifunc/ifunc.exp: Run PR ld/19784 tests.
	* testsuite/ld-ifunc/pass.out: New file.
	* testsuite/ld-ifunc/pr19784a.c: Likewise.
	* testsuite/ld-ifunc/pr19784b.c: Likewise.
	* testsuite/ld-ifunc/pr19784c.c: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Group common symbol checking together
@ 2016-03-08 13:50 sergiodj+buildbot
  2016-03-08 15:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-08 13:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 202ac193bbbecc96a4978d1ac3d17148253f9b01 ***

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

Group common symbol checking together

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Group common symbol checking
	together.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix "set architecture mips:10000" crash
@ 2016-03-07 16:52 sergiodj+buildbot
  2016-03-07 19:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6c2f47b45315ba13f25fb57e51389d0c5ed0701 ***

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

Fix "set architecture mips:10000" crash

Fix this GDB crash:

  $ gdb -ex "set architecture mips:10000"
  Segmentation fault (core dumped)

Backtrace:

  Program received signal SIGSEGV, Segmentation fault.
  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at /home/pedro/gdb/mygit/cxx-convertion/src/gdb/mips-tdep.c:8436
  8436              if (bfd_get_flavour (info.abfd) == bfd_target_elf_flavour
  (top-gdb) bt
  #0  0x0000000000495b1b in mips_gdbarch_init (info=..., arches=0x0) at .../src/gdb/mips-tdep.c:8436
  #1  0x00000000007348a6 in gdbarch_find_by_info (info=...) at .../src/gdb/gdbarch.c:5155
  #2  0x000000000073563c in gdbarch_update_p (info=...) at .../src/gdb/arch-utils.c:522
  #3  0x0000000000735585 in set_architecture (ignore_args=0x0, from_tty=1, c=0x26bc870) at .../src/gdb/arch-utils.c:496
  #4  0x00000000005f29fd in do_sfunc (c=0x26bc870, args=0x0, from_tty=1) at .../src/gdb/cli/cli-decode.c:121
  #5  0x00000000005fd3f3 in do_set_command (arg=0x7fffffffdcdd "mips:10000", from_tty=1, c=0x26bc870) at .../src/gdb/cli/cli-setshow.c:455
  #6  0x0000000000836157 in execute_command (p=0x7fffffffdcdd "mips:10000", from_tty=1) at .../src/gdb/top.c:460
  #7  0x000000000071abfb in catch_command_errors (command=0x835f6b <execute_command>, arg=0x7fffffffdccc "set architecture mips:10000", from_tty=1)
      at .../src/gdb/main.c:368
  #8  0x000000000071bf4f in captured_main (data=0x7fffffffd750) at .../src/gdb/main.c:1132
  #9  0x0000000000716737 in catch_errors (func=0x71af44 <captured_main>, func_args=0x7fffffffd750, errstring=0x106b9a1 "", mask=RETURN_MASK_ALL)
      at .../src/gdb/exceptions.c:240
  #10 0x000000000071bfe6 in gdb_main (args=0x7fffffffd750) at .../src/gdb/main.c:1164
  #11 0x000000000040a6ad in main (argc=4, argv=0x7fffffffd858) at .../src/gdb/gdb.c:32
  (top-gdb)

We already check whether info.abfd is NULL before all other
bfd_get_flavour calls in the same function.  Just this one case was
missing.

(This was exposed by a WIP test that tries all "set architecture ARCH"
values.)

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

	* mips-tdep.c (mips_gdbarch_init): Check whether info.abfd is NULL
	before calling bfd_get_flavour.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced
@ 2016-03-07 15:51 sergiodj+buildbot
  2016-03-07 17:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-07 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 18f822a08fd5cb8fed8b0b318e7945545c255081 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 18f822a08fd5cb8fed8b0b318e7945545c255081

[AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced

2016-03-07  Jiong Wang  <jiong.wang@arm.com>

bfd/
  * elfnn-aarch64.c (elfNN_aarch64_check_relocs): Always create .got section
  if the symbol "_GLOBAL_OFFSET_TABLE_" referenced.

ld/
  * testsuite/ld-aarch64/implicit_got_section_1.s: New test source file.
  * testsuite/ld-aarch64/implicit_got_section_1.d: New test expected result.
  * testsuite/ld-aarch64/aarch64-elf.exp: Run new test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Set executable bit on analyze-racy-logs.py
@ 2016-03-06 22:42 sergiodj+buildbot
  2016-03-06 23:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-06 22:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5eb264df40e1e3ffeb2627456889a1dc5df00f16 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 5eb264df40e1e3ffeb2627456889a1dc5df00f16

Set executable bit on analyze-racy-logs.py

I forgot to do it in my previous commit.  This is necessary because we
execute the script directly on gdb/testsuite/Makefile.in.

gdb/testsuite/ChangeLog:
2016-03-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* analyze-racy-logs.py: Set executable bit.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Improve analysis of racy testcases
@ 2016-03-06  1:57 sergiodj+buildbot
  2016-03-06  3:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-06  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb6a751f5f1fe7912e84dd90d06395c357da47c2 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fb6a751f5f1fe7912e84dd90d06395c357da47c2

Improve analysis of racy testcases

This is an initial attempt to introduce some mechanisms to identify
racy testcases present in our testsuite.  As can be seen in previous
discussions, racy tests are really bothersome and cause our BuildBot
to pollute the gdb-testers mailing list with hundreds of
false-positives messages every month.  Hopefully, identifying these
racy tests in advance (and automatically) will contribute to the
reduction of noise traffic to gdb-testers, maybe to the point where we
will be able to send the failure messages directly to the authors of
the commits.

I spent some time trying to decide the best way to tackle this
problem, and decided that there is no silver bullet.  Racy tests are
tricky and it is difficult to catch them, so the best solution I could
find (for now?) is to run our testsuite a number of times in a row,
and then compare the results (i.e., the gdb.sum files generated during
each run).  The more times you run the tests, the more racy tests you
are likely to detect (at the expense of waiting longer and longer).
You can also run the tests in parallel, which makes things faster (and
contribute to catching more racy tests, because your machine will have
less resources for each test and some of them are likely to fail when
this happens).  I did some tests in my machine (8-core i7, 16GB RAM),
and running the whole GDB testsuite 5 times using -j6 took 23 minutes.
Not bad.

In order to run the racy test machinery, you need to specify the
RACY_ITER environment variable.  You will assign a number to this
variable, which represents the number of times you want to run the
tests.  So, for example, if you want to run the whole testsuite 3
times in parallel (using 2 cores), you will do:

  make check RACY_ITER=3 -j2

It is also possible to use the TESTS variable and specify which tests
you want to run:

  make check TEST='gdb.base/default.exp' RACY_ITER=3 -j2

And so on.  The output files will be put at the directory
gdb/testsuite/racy_outputs/.

After make invokes the necessary rules to run the tests, it finally
runs a Python script that will analyze the resulting gdb.sum files.
This Python script will read each file, and construct a series of sets
based on the results of the tests (one set for FAIL's, one for
PASS'es, one for KFAIL's, etc.).  It will then do some set operations
and come up with a list of unique, sorted testcases that are racy.
The algorithm behind this is:

  for state in PASS, FAIL, XFAIL, XPASS...; do
    if a test's state in every sumfile is $state; then
      it is not racy
    else
      it is racy

(The algorithm is actually a bit more complex than that, because it
takes into account other things in order to decide whether the test
should be ignored or not).

IOW, a test must have the same state in every sumfile.

After processing everything, the script prints the racy tests it could
identify on stdout.  I am redirecting this to a file named racy.sum.

Something else that I wasn't sure how to deal with was non-unique
messages in our testsuite.  I decided to do the same thing I do in our
BuildBot: include a unique identifier in the end of message, like:

  gdb.base/xyz.exp: non-unique message
  gdb.base/xyz.exp: non-unique message <<2>>

This means that you will have to be careful about them when you use
the racy.sum file.

I ran the script several times here, and it did a good job catching
some well-known racy tests.  Overall, I am satisfied with this
approach and I think it will be helpful to have it upstream'ed.  I
also intend to extend our BuildBot and create new, specialized
builders that will be responsible for detecting the racy tests every X
number of days.

2016-03-05  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (DEFAULT_RACY_ITER): New variable.
	(CHECK_TARGET_TMP): Likewise.
	(check-single-racy): New rule.
	(check-parallel-racy): Likewise.
	(TEST_TARGETS): Adjust rule to account for RACY_ITER.
	(do-check-parallel-racy): New rule.
	(check-racy/%.exp): Likewise.
	* README (Racy testcases): New section.
	* analyze-racy-logs.py: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix argument passing for call
@ 2016-03-05 12:31 sergiodj+buildbot
  2016-03-05 12:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-05 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb86f3880e61c79e59b9225e79c3544a1fcd8005 ***

Author: Denis Chertykov <chertykov@gmail.com>
Branch: master
Commit: cb86f3880e61c79e59b9225e79c3544a1fcd8005

Fix argument passing for call

When calling function with argument of size more than 8 bytes fails with
an error "That operation is not available on integers of more than 8 bytes.".
avr-gdb considers only 8 bytes (sizeof(long long)) in case of passing the
argument in registers. When the argument is of size more than 8 byte
then the utility function to extract bytes failed with the above error.

    gdb/
	* avr-tdep.c (AVR_LAST_ARG_REGNUM): Define.
        (avr_push_dummy_call): Correct last needed argument register.
        Write MSB of argument into register and subsequent bytes into
        other registers in decreasing order.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add missing ChangeLog entries for commit 82838
@ 2016-03-04 16:41 sergiodj+buildbot
  2016-03-04 20:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f1f41f55f2fa5d390e57074477b6407302c8c46 ***

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

Add missing ChangeLog entries for commit 82838

Fix gold/testsuite/plugin_layout_with_alignment.sh permission.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Tweak ARM process record
@ 2016-03-04 16:10 sergiodj+buildbot
  2016-03-04 17:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca92db2d5885c03d3e0ed23c96b5c6ab336d908d ***

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

Tweak ARM process record

This patch removes the printing "Process record does not support",
and do the print by calling arm_record_unsupported_insn in the
caller.  Also, call arm_record_extension_space only when condition
is 0xf.

gdb:

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

	* arm-tdep.c (arm_record_extension_space): Remove code
	printing "Process record does not support".
	(arm_record_data_proc_misc_ld_str): Likewise.
	(decode_insn): Call arm_record_extension_space if condition
	is 0xf.  Call arm_record_unsupported_insn if ret isn't
	ARM_RECORD_SUCCESS.  Use 'ret' instead of 'insn_id' to hold
	the value of thumb2_record_decode_insn_handler.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] feature_to_c.sh: Print help when passing no arguments
@ 2016-03-04 15:16 sergiodj+buildbot
  2016-03-04 16:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 15:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73519cce7cbe31609a2aa9c27955555237a0c51f ***

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

feature_to_c.sh: Print help when passing no arguments

I found that odd that passing no arguments to feature_to_c.sh produces
this:

$ ./feature_to_c.sh
./feature_to_c.sh: 23: shift: can't shift that many

but passing one argument shows the help:

$ ./feature_to_c.sh hello
Usage: ./feature_to_c.sh OUTPUTFILE INPUTFILE...

This patch changes the script to show the help in both cases.

gdb/ChangeLog:

	* features/feature_to_c.sh: Print the help when passing no
	argument.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Treat common symbol in executable as definition
@ 2016-03-04 14:50 sergiodj+buildbot
  2016-03-04 15:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-04 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07492f668d2173da7a2bda3707ff0985e0f460b6 ***

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

Treat common symbol in executable as definition

Common symbol in executable is a definition, which overrides definition
from shared objects.  When linker sees a new definition from a shared
object, the new dynamic definition should be overridden by the previous
common symbol in executable.

bfd/

	PR ld/19579
	* elflink.c (_bfd_elf_merge_symbol): Treat common symbol in
	executable as definition if the new definition comes from a
	shared library.

ld/

	PR ld/19579
	* testsuite/ld-elf/pr19579a.c: New file.
	* testsuite/ld-elf/pr19579b.c: Likewise.
	* testsuite/ld-elf/shared.exp: Run PR ld/19579 test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb.base/skip.exp: Use with_test_prefix.
@ 2016-03-03 19:03 sergiodj+buildbot
  2016-03-03 23:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdf7e23048b68171c01f2498cc46670a76e68c4d ***

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

gdb.base/skip.exp: Use with_test_prefix.

gdb/testsuite/ChangeLog:

	* gdb.base/skip.exp: Use with_test_prefix.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.
@ 2016-03-03 15:34 sergiodj+buildbot
  2016-03-03 21:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57aa17424380be1c3e362a5601071f1f3a6f74f6 ***

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

Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions.

	* simulator.c (set_flags_for_sub32): Correct type of signbit.
	(CondCompare): Swap interpretation of bit 30.
	(DO_ADDP): Delete macro.
	(do_vec_ADDP): Copy source registers before starting to update
	destination register.
	(do_vec_FADDP): Likewise.
	(do_vec_load_store): Fix computation of sizeof_operation.
	(rbit64): Fix type of constant.
	(aarch64_step): When displaying insn value, display all 32 bits.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] New test about step over clone syscall
@ 2016-03-03 10:27 sergiodj+buildbot
  2016-03-03 18:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4719d415b9908d3c7981163b47be5096d03656f9 ***

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

New test about step over clone syscall

This patch adds a new test for stepping over clone syscall.

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

	* gdb.base/step-over-syscall.exp (step_over_syscall): Kfail.
	Invoke step_over_syscall "clone" and break_cond_on_syscall
	"clone".
	* gdb.base/step-over-clone.c: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Reformat gdb.base/step-over-syscall.exp
@ 2016-03-03 10:20 sergiodj+buildbot
  2016-03-03 16:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ea50786226737509a8f4c2734699a5fc15cc63c4 ***

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

Reformat gdb.base/step-over-syscall.exp

gdb/testsuite:

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

	* gdb.base/step-over-syscall.exp (disp_step_cross_syscall): Fix
	code format.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Rename disp-step-syscall.exp to step-over-syscall.exp
@ 2016-03-03 10:09 sergiodj+buildbot
  2016-03-03 15:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8fc8cbdaf698ed042d859d5749cff66937bbb57c ***

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

Rename disp-step-syscall.exp to step-over-syscall.exp

disp-step-syscall.exp is extended for stepping over syscall instruction
in different cases, with or without displaced stepping, and stepping
over by GDBserver.

This patch rename disp-step-syscall.exp to step-over-syscall.exp to
reflect this.

gdb/testsuite:

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

	* gdb.base/disp-step-fork.c: Rename to ...
	* gdb.base/step-over-fork.c: ... it.  New file.
	* gdb.base/disp-step-vfork.c: Rename to ...
	* gdb.base/step-over-vfork.c: ... it.  New file.
	* gdb.base/disp-step-syscall.exp: Rename to ...
	* gdb.base/step-over-syscall.exp: ... it.  New file.
	(disp_step_cross_syscall): Rename to ...
	(step_over_syscall): ... it.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Step over fork/vfork syscall insn in gdbserver
@ 2016-03-03 10:00 sergiodj+buildbot
  2016-03-03 14:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03 10:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92fa70b0bd8690d979357ebcdb501a9e4aa42ea6 ***

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

Step over fork/vfork syscall insn in gdbserver

We can also extend disp-step-syscall.exp to test GDBserver step over
breakpoint on syscall instruction.  That is, we set a breakpoint
with a false condition on syscall instruction, so that GDBserver will
step over it.

This test triggers a GDBserver internal error, which can be fixed by
this series.

(gdb) PASS: gdb.base/disp-step-syscall.exp: fork: break cond on target: break on syscall insns
continue^M
Continuing.^M
Remote connection closed^M
(gdb) FAIL: gdb.base/disp-step-syscall.exp: fork: break cond on target: continue to fork again

In GDBserver, there is an internal error,

/home/yao/SourceCode/gnu/gdb/git/gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
unsuspend LWP 25554, suspended=-1

the simplified reproducer is like,

$ ./gdb ./testsuite/outputs/gdb.base/disp-step-syscall/disp-step-fork
(gdb) b main
(gdb) c
(gdb) disassemble fork // in order to find the address of insn 'syscall'
....
   0x00007ffff7ad6023 <+179>:	syscall
(gdb) b *0x00007ffff7ad6023 if main == 0
(gdb) c

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (break_cond_on_syscall): New.
	If target supports condition evaluation on target, invoke
	break_cond_on_syscall for fork and vfork.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [GDBserver] Leave child suspended when step over parent
@ 2016-03-03  9:31 sergiodj+buildbot
  2016-03-03  9:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-03  9:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f8288ae82bf5bdb33d46d7447cd3132393a1bd2 ***

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

[GDBserver] Leave child suspended when step over parent

I see the following GDBserver internal error in two cases,

 gdb/gdbserver/linux-low.c:1922: A problem internal to GDBserver has been detected.
 unsuspend LWP 17200, suspended=-1

 1. step over a breakpoint on fork/vfork syscall instruction,
 2. step over a breakpoint on clone syscall instruction and child
    threads hits a breakpoint,

the stack backtrace is

 #0  internal_error (file=file@entry=0x44c4c0 "gdb/gdbserver/linux-low.c", line=line@entry=1922,
    fmt=fmt@entry=0x44c7d0 "unsuspend LWP %ld, suspended=%d\n") at gdb/gdbserver/../common/errors.c:51
 #1  0x0000000000424014 in lwp_suspended_decr (lwp=<optimised out>, lwp=<optimised out>) at gdb/gdbserver/linux-low.c:1922
 #2  0x000000000042403a in unsuspend_one_lwp (entry=<optimised out>, except=0x66e8c0) at gdb/gdbserver/linux-low.c:2885
 #3  0x0000000000405f45 in find_inferior (list=<optimised out>, func=func@entry=0x424020 <unsuspend_one_lwp>, arg=arg@entry=0x66e8c0)
    at gdb/gdbserver/inferiors.c:243
 #4  0x00000000004297de in unsuspend_all_lwps (except=0x66e8c0) at gdb/gdbserver/linux-low.c:2895
 #5  linux_wait_1 (ptid=..., ourstatus=ourstatus@entry=0x665ec0 <last_status>, target_options=target_options@entry=0)
    at gdb/gdbserver/linux-low.c:3632
 #6  0x000000000042a764 in linux_wait (ptid=..., ourstatus=0x665ec0 <last_status>, target_options=0)
    at gdb/gdbserver/linux-low.c:3770
 #7  0x0000000000411163 in mywait (ptid=..., ourstatus=ourstatus@entry=0x665ec0 <last_status>, options=options@entry=0, connected_wait=connected_wait@entry=1)
    at gdb/gdbserver/target.c:214
 #8  0x000000000040b1f2 in resume (actions=0x66f800, num_actions=1) at gdb/gdbserver/server.c:2757
 #9  0x000000000040f660 in handle_v_cont (own_buf=0x66a630 "vCont;c:p45e9.-1") at gdb/gdbserver/server.c:2719

when GDBserver steps over a thread, other threads have been suspended,
the "stepping" thread may create new thread, but GDBserver doesn't set
it suspend count to 1.  When GDBserver unsuspend threads, the child's
suspend count goes to -1, and the assert is triggered.  In fact, GDBserver
has already taken care of suspend count of new thread when GDBserver is
suspending all threads except the one GDBserver wants to step over by
https://sourceware.org/ml/gdb-patches/2015-07/msg00946.html

+	  /* If we're suspending all threads, leave this one suspended
+	     too.  */
+	  if (stopping_threads == STOPPING_AND_SUSPENDING_THREADS)
+	    {
+	      if (debug_threads)
+		debug_printf ("HEW: leaving child suspended\n");
+	      child_lwp->suspended = 1;
+	    }

but that is not enough, because new thread is still can be spawned in
the thread which is being stepped over.  This patch extends the
condition that GDBserver set child's suspend count to one if it is
suspending threads or stepping over the thread.

gdb/gdbserver:

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

	PR server/19736
	* linux-low.c (handle_extended_wait): Set child suspended
	if event_lwp->bp_reinsert isn't zero.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays.
@ 2016-03-02 17:06 sergiodj+buildbot
  2016-03-02 23:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07e448ade17bc8fb52469a5b2184017f94669bd6 ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 07e448ade17bc8fb52469a5b2184017f94669bd6

testsuite: Fix timeout issues during print of vla-arrays.

Printing and resolving of dynamic array's causes sporadic timeout issues on loaded systems.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.fortran/vla-history.exp: Lookup array elements and printing exceeds timeout.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.
@ 2016-03-02 16:31 sergiodj+buildbot
  2016-03-03  7:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 16:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6896a8fa1e1d24a8fcc9b30efc0b195246b46029 ***

Author: Marcin Kocielnicki <koriakin@0x04.net>
Branch: master
Commit: 6896a8fa1e1d24a8fcc9b30efc0b195246b46029

[OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded.

Fixes rather embarassing gdb.trace regressions.

gdb/gdbserver/ChangeLog:

	* tracepoint.c (cmd_qtstart): Only set ipa_tdesc_idx if agent
	is actually loaded.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Fix run to main issue introduced by GCC 5.x.
@ 2016-03-02 15:53 sergiodj+buildbot
  2016-03-02 21:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ac2d526d9ae70272bf7fc436f2e3ad11a84d58b ***

Author: bernhard.heckel <bernhard.heckel@intel.com>
Branch: master
Commit: 9ac2d526d9ae70272bf7fc436f2e3ad11a84d58b

testsuite: Fix run to main issue introduced by GCC 5.x.

Adding a dummy assignment as a new breakpoint anchor because
breakpoint on return statement doesn't work for GCC 5.x.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.cp/vla-cxx.cc: Insert dummy assignment as anchor for an breakpoint.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Nullify pointers before first usage.
@ 2016-03-02 15:43 sergiodj+buildbot
  2016-03-02 19:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 178073690aec73fdb5f4452b49f108407edde700 ***

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

testsuite: Nullify pointers before first usage.

Nullify pointers to avoid an undefined association status.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/testsuite/Changelog:

     * gdb.mi/vla.f90: Nullify pointer after declaration.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add new maintainer to Write After Approval.
@ 2016-03-02 15:30 sergiodj+buildbot
  2016-03-02 17:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 15:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 650beae39d31e5ce2680649e2fb697e0e4a9e3eb ***

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

Add new maintainer to Write After Approval.

Add new maintainer to Write After Approval.

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

    * MAINTAINERS (Write After Approval): Add Bernhard Heckel.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix detection of gfortran compilers.
@ 2016-03-02 14:37 sergiodj+buildbot
  2016-03-02 16:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 14:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 285866651cd0d404087438668012289d278e4179 ***

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

Fix detection of gfortran compilers.

Newer gfortran compilers changed naming convention in DW_AT_producer tag.
For example "GNU Fortran 4.6.3" vs "GNU Fortran2008 5.3.0"

2016-03-02  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:

     * dwarf2read.c (new_symbol_full): Fix detection of gfortran compilers.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Regenerate or1k opcodes file
@ 2016-03-02 14:03 sergiodj+buildbot
  2016-03-02 14:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d11698cd0d9bb22b51598ee37af0aaf1d44ec5c7 ***

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

Regenerate or1k opcodes file

CGEN patch now committed upstream to use hex numbers for large enums.

	* or1k-desc.h: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Regenerate bfd files.
@ 2016-03-02  4:03 sergiodj+buildbot
  2016-03-02  6:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-02  4:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70a5df4fe30fd37166c3b62071fd816e49082d2e ***

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

Regenerate bfd files.

	* Makefile.in: Regenerate.
	* po/SRC-POTFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation
@ 2016-03-01 18:47 sergiodj+buildbot
  2016-03-01 22:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86e501afd46d7f0d31738bd62457593401d79bad ***

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

Fix gdb.trace/ftrace-lock.c compilation

Fixes, on F23:

 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c: In function 'gdb_agent_gdb_collect':
 .../src/gdb/testsuite/gdb.trace/ftrace-lock.c:50:3: warning: implicit declaration of function 'sleep' [-Wimplicit-function-declaration]
    sleep (1);
    ^

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

	* gdb.trace/ftrace-lock.c: Include <unistd.h>.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation
@ 2016-03-01 17:53 sergiodj+buildbot
  2016-03-01 21:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e903e320352db86233e1dd2d10fd140f5d4a887 ***

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

Fix gdb.threads/watchpoint-fork*.c compilation

This testcase currently fails to compile on Fedora 23:

 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c: In function 'start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70:11: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaration]
	i = pthread_yield ();
	    ^
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c: In function 'forkoff':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-child.c:114:8: warning: implicit declaration of function 'pthread_yield' [-Wimplicit-function-declaratio
 n]
     i = pthread_yield ();
	 ^
 /tmp/ccUkNIsI.o: In function `start':
 .../src/gdb/testsuite/gdb.threads/watchpoint-fork-mt.c:70: undefined reference to `pthread_yield'
 (...)
 collect2: error: ld returned 1 exit status

 UNSUPPORTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: Couldn't compile watchpoint-fork-child.c: unrecognized error
 UNTESTED: gdb.threads/watchpoint-fork.exp: child: multithreaded: watchpoint-fork.exp
 testcase .../src/gdb/testsuite/gdb.threads/watchpoint-fork.exp completed i

The glibc manual says, on _GNU_SOURCE:

 "You should define these macros by using #define preprocessor
 directives at the top of your source code files. These directives must
 come before any #include of a system header file."

I instead put it in the header all the .c files of the testcase must
include anyway.

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

	* gdb.threads/watchpoint-fork-child.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork-mt.c: Likewise.  Don't define
	_GNU_SOURCE here.
	* gdb.threads/watchpoint-fork-st.c: Include "watchpoint-fork.h"
	before anything else.
	* gdb.threads/watchpoint-fork.h: Define _GNU_SOURCE.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.base/catch-fork-kill.c compilation
@ 2016-03-01 17:26 sergiodj+buildbot
  2016-03-01 19:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ccb54e2a82ca934f6d430b87ab015b7bfecc413 ***

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

Fix gdb.base/catch-fork-kill.c compilation

Fixes:

 Running .../src/gdb/testsuite/gdb.base/catch-fork-kill.exp ...
 gdb compile failed, .../src/gdb/testsuite/gdb.base/catch-fork-kill.c: In function 'main':
 .../src/gdb/testsuite/gdb.base/catch-fork-kill.c:81:4: warning: implicit declaration of function 'wait' [-Wimplicit-function-declaration]
     wait (NULL);
     ^

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

	* gdb.base/catch-fork-kill.c: Include <sys/wait.h>.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix output path for arm-disp-step.exp
@ 2016-03-01 15:41 sergiodj+buildbot
  2016-03-01 17:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30ca9da1193ec4c82cc67a2ec2e6fb6adac7ab84 ***

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

Fix output path for arm-disp-step.exp

This patch fixes the following error,

ERROR: (/scratch/yao/gdb/build-git/arm-linux-gnueabihf/gdb/testsuite/outputs/gdb.arch/arm-disp-step/arm-disp-step) No such file or directory
FAIL: gdb.arch/arm-disp-step.exp: Can't run to main

gdb/testsuite:

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

	* gdb.arch/arm-disp-step.exp: Use standard_testfile and
	prepare_for_testing.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Fix output path for s390-tdbregs test case
@ 2016-03-01 12:05 sergiodj+buildbot
  2016-03-01 14:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9321595003d86dd4794d0edab071f91989808e ***

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

S390: Fix output path for s390-tdbregs test case

Since test artifacts are always organized in a directory hierarchy, the
s390-tdbregs test case is not executed correctly any more.  This is
because it uses an obsolete way of constructing the executable's path.

This change invokes prepare_for_testing instead.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-tdbregs.exp: Use prepare_for_testing instead of
	manually constructing the output path.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] S390: Fix internal error with stackless inferior
@ 2016-03-01 11:55 sergiodj+buildbot
  2016-03-01 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-03-01 11:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f24894771e384b1bc60dc0f2c104d7e7fad3c865 ***

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

S390: Fix internal error with stackless inferior

This fixes a GDB internal error that may occur when the inferior has no
valid stack pointer in r15.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-stackless.S: New.
	* gdb.arch/s390-stackless.exp: New.

gdb/ChangeLog:

	* s390-linux-tdep.c (s390_backchain_frame_unwind_cache): Avoid
	exception when attempting to access the inferior's backchain.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] aarch64-linux process record: more syscalls
@ 2016-02-29 17:29 sergiodj+buildbot
  2016-02-29 20:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d521906965b3e94648a723a13576236aaba301d0 ***

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

aarch64-linux process record: more syscalls

The last patch supports several syscalls in linux-record.c, so now
GDB aarch64-linux backend can return these canonicalized syscall numbers
per aarch64 syscall number.

This patch fixes the following fails,

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/pipe-reverse.exp: continue to breakpoint: marker2

Process record and replay target doesn't support syscall number 59^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M
(gdb) FAIL: gdb.reverse/readv-reverse.exp: continue to breakpoint: marker2

gdb:

2016-02-29  Yao Qi  <yao.qi@linaro.org>

	* aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Support
	eventfd2, eventfd2, dup3, inotify_init1, fallocate and pipe2.
	Return gdb_sys_epoll_create1 instead of gdb_sys_epoll_create
	for aarch64_sys_epoll_create1.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1
@ 2016-02-29 16:58 sergiodj+buildbot
  2016-02-29 19:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 253b4d3a09e9edbb72d21127fbc85934ab1b7c07 ***

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

Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1

This patch adds more syscalls in linux-record.

gdb:

2016-02-29  Yao Qi  <yao.qi@linaro.org>

	* linux-record.h (enum gdb_syscall) <gdb_sys_fallocate>: New.
	<gdb_sys_eventfd2, gdb_sys_epoll_create1, gdb_sys_dup3>: New.
	<gdb_sys_pipe2, gdb_sys_inotify_init1>: New.
	* linux-record.c (record_linux_system_call): Handle them.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] Local symbols relocation cleanup
@ 2016-02-29 16:04 sergiodj+buildbot
  2016-02-29 17:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 841fdfcdd9caa69f3ad7560a2806d421e23f598a ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 841fdfcdd9caa69f3ad7560a2806d421e23f598a

[ARC] Local symbols relocation cleanup

bfd/
2016-02-29  Cupertino Miranda  <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_relocate_section): Added rules to fix the
	relocation addend when sections get merged.

gas/
2016-02-29  Cupertino Miranda  <cmiranda@synopsys.com>
	    Claudiu Zissulescu  <Claudiu.Zissulescu@synopsys.com>

        * config/tc-arc.c (arc_extra_reloc): Change size to 0.
        (tc_arc_fix_adjustable): Changed default return value to 1.
        * testsuite/gas/arc/j.d: Updated expected symbol
        * testsuite/gas/arc/jl.d: Likewise
        * testsuite/gas/arc/relax-avoid1.d: Likewise
        * testsuite/gas/arc/st.d: Likewise

ld/
2016-02-29 Cupertino Miranda  <cmiranda@synopsys.com>

	* testsuite/ld-elf/merge.d: Removed xfail for ARC.
	* testsuite/ld-elf/merge2.d: Likewise.
	* testsuite/ld-elf/merge3.d: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARC] General fixes.
@ 2016-02-29 15:24 sergiodj+buildbot
  2016-02-29 15:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-29 15:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e4588997ebdddefc48d8be2d51a715822817c0e ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 7e4588997ebdddefc48d8be2d51a715822817c0e

[ARC] General fixes.

bfd/
2016-02-29  Cupertino Miranda <Cupertino.Miranda@synopsys.com>

	* elf32-arc.c (arc_elf_final_write_processing): Add condition to
	the flag change.
        (elf_arc_relocate_section): Fixes and conditions to support PIE.
	Assert for code sections dynamic relocs.

gas/
2016-02-29  Claudiu Zissulescu  <Claudiu.Zissulescu@synopsys.com>

	* config/tc-arc.c: Enable code density instructions for ARC EM.

ld/
2016-02-29  Cupertino Miranda  <Cupertino.Miranda@synopsys.com>

	* scripttempl/arclinux.sc: Force .tdata and .tbss to always be
	generated.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't recursively look for a symbol in all imports of imported modules.
@ 2016-02-28 15:25 sergiodj+buildbot
  2016-02-28 15:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-28 15:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38899f16e1560ce3020bab8a6a0b3a0c017d7925 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 38899f16e1560ce3020bab8a6a0b3a0c017d7925

Don't recursively look for a symbol in all imports of imported modules.

Given two or more modules that import each other's scope, the current symbol
lookup routines would go round in circles looking through each import from
each module, possibly checking the same module twice or more until all possible
paths are marked as "searched".

Given enough modules, this causes an exponential slowdown in time taken to find
symbols that do exist, and infinite recursion when they don't.

gdb/ChangeLog:
	* d-namespace.c (d_lookup_symbol_imports): Avoid recursive lookups from
	cyclic imports.

gdb/testsuite/ChangeLog:
	* gdb.dlang/circular.c: New file.
	* gdb.dlang/circular.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <1ed0c2a4bbe8ad5f5404014a6351b2b74db75577@gdb-build>]
* [binutils-gdb] Add aarch64-*-rtems* target
@ 2016-02-26 20:30 sergiodj+buildbot
  2016-02-27 12:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12a132db164ea95e9e457427c2c97005f94c5a70 ***

Author: Joel Sherrill <joel@rtems.org>
Branch: master
Commit: 12a132db164ea95e9e457427c2c97005f94c5a70

Add aarch64-*-rtems* target


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check.
@ 2016-02-26 18:19 sergiodj+buildbot
  2016-02-27  9:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5e3a3641ea9d6ed2918021fd77925825d24e9be ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: c5e3a3641ea9d6ed2918021fd77925825d24e9be

[BFD][AARCH64]Fix MOVW_SABS_G(0,1,2) relocation overflow check.

For these three relocations, 17 bit signed value should be used, instead of
16 bit. The bitsize field is changed from 16 to 17, this field in aarch64
backend is used for overflow check only.

bfd/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * elfnn-aarch64.c (elfNN_aarch64_howto_table): Fix signed overflow
    check for MOVW_SABS_G0, MOVW_SABS_G1, MOVW_SABS_G2.

ld/

2016-02-26  Renlin Li  <renlin.li@arm.com>

    * testsuite/ld-aarch64/aarch64-elf.exp: Run new testcases.
    * testsuite/ld-aarch64/emit-relocs-270.d: Update to use new boundary.
    * testsuite/ld-aarch64/emit-relocs-271.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-272.d: Likewise.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-270-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-271-overflow.s: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.d: New.
    * testsuite/ld-aarch64/emit-relocs-272-overflow.s: New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Rename gdb.reverse/aarch64.{exp, c} to gdb.reverse/insn-reverse.{exp, c}
@ 2016-02-26 16:01 sergiodj+buildbot
  2016-02-26 20:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce90fefec908ee50ae5a3b22b03447df638a54c1 ***

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

Rename gdb.reverse/aarch64.{exp,c} to gdb.reverse/insn-reverse.{exp,c}

gdb/testsuite:

2016-02-26  Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/aarch64.c: Rename to ...
	* gdb.reverse/insn-reverse.c: ... it.
	* gdb.reverse/aarch64.exp: Rename to ...
	* gdb.reverse/insn-reverse.exp: ... it.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix various bugs in arm_record_exreg_ld_st_insn
@ 2016-02-26 16:00 sergiodj+buildbot
  2016-02-27  0:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fde51ed303ea3ecbaa7c0084ea417e775a5db29 ***

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

Fix various bugs in arm_record_exreg_ld_st_insn

This patch fixes various bugs in arm_record_exreg_ld_st_insn, and use
gdb.reverse/insn-reverse.c to test more arm instructions.

 - Set flag SINGLE_REG correctly.  In the arch reference manual,
   SING_REG is true when the bit 8 of instruction is zero.
 - Record the right D registers for instructions changing S registers.
 - Fix the order of length and address in record_buf_mem array.
 - Shift the offset by 2 instead of by 24.

This patch also fixes one internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/utils.c:1072: internal-error: virtual memory exhausted.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

2016-02-26  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_record_exreg_ld_st_insn): Set 'single_reg'
	per bit 8.  Check bit 20 instead of bit 4 for VMOV
	instruction.  Record D registers for instructions changing
	S registers.  Change of the order of length and address
	in record_buf_mem array.

gdb/testsuite:

2016-02-26  Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/insn-reverse.c [__arm__] (ext_reg_load): New.
	[__arm__] (ext_reg_mov, ext_reg_push_pop): New.
	(testcases): Update.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Record right reg num of thumb special data instructions
@ 2016-02-26 15:51 sergiodj+buildbot
  2016-02-26 22:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f33efec7c6d1357d7e867176cfb88942fc513a8 ***

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

Record right reg num of thumb special data instructions

When GDB decodes these thumb special data instructions, such as 'mov sp, r7'
the Rd is got incorrectly.  According to the arch reference manual, the Rd
is DN:Rdn, in which DN is bit 7 and Rdn is bits 0 to 2.  This patch fixes it.

gdb:

2016-02-26  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (thumb_record_ld_st_reg_offset): Fix the register
	number of Rd.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Generalize gdb.reverse/aarch64.exp
@ 2016-02-26 15:15 sergiodj+buildbot
  2016-02-26 18:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 15:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3263bceb4f76b783a44aeea417a9fb69dab26ee5 ***

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

Generalize gdb.reverse/aarch64.exp

I said we can generialize gdb.reverse/aarch64.exp for other
architectures https://sourceware.org/ml/gdb-patches/2015-05/msg00482.html
and here is the patch to change aarch64.exp so that it can be used to
test for other architectures as well.

gdb/testsuite:

2016-02-26  Yao Qi  <yao.qi@linaro.org>

	* gdb.reverse/aarch64.c: [__aarch64__] Include arm_neon.h.
	(testcase_ftype): New.
	(testcases): New array.
	(n_testcases): New.
	(main): Call each element in testcases.
	* gdb.reverse/aarch64.exp: Remove is_aarch64_target check.
	(read_testcase): New.
	Do the tests in a loop.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Properly implement STT_COMMON
@ 2016-02-26 14:51 sergiodj+buildbot
  2016-02-26 17:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 14:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8871f357fdfa9c0c06d2d3e5600391d8c994f37 ***

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

Properly implement STT_COMMON

The BFD configure option, --enable-elf-stt-common, can't be to used to
verify STT_COMMON implementation with the normal binutils build.  Instead,
this patch removes it from BFD.  It adds --elf-stt-common=[no|yes] to ELF
assembler/objcopy and adds -z common/-z nocommon to ld.

A configure option, --enable-elf-stt-common, is added to gas to specify
whether ELF assembler should generate common symbols with the STT_COMMON
type by default.

Since BSF_KEEP_G is never used, it is renamed to BSF_ELF_COMMON for ELF
common symbols.

bfd/

	PR ld/19645
	* bfd.c (bfd): Change flags to 20 bits.
	(BFD_CONVERT_ELF_COMMON): New.
	(BFD_USE_ELF_STT_COMMON): Likewise.
	(BFD_FLAGS_SAVED): Add BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.
	(BFD_FLAGS_FOR_BFD_USE_MASK): Likewise.
	* configure.ac: Remove --enable-elf-stt-common.
	* elf.c (swap_out_syms): Choose STT_COMMON or STT_OBJECT for
	common symbol depending on BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.
	* elfcode.h (elf_slurp_symbol_table): Set BSF_ELF_COMMON for
	STT_COMMON.
	* elflink.c (bfd_elf_link_mark_dynamic_symbol): Also check
	STT_COMMON.
	(elf_link_convert_common_type): New function.
	(elf_link_output_extsym): Choose STT_COMMON or STT_OBJECT for
	common symbol depending on BFD_CONVERT_ELF_COMMON and
	BFD_USE_ELF_STT_COMMON.  Set sym.st_info after sym.st_shndx.
	* elfxx-target.h (TARGET_BIG_SYM): Add BFD_CONVERT_ELF_COMMON
	and BFD_USE_ELF_STT_COMMON to object_flags.
	(TARGET_LITTLE_SYM): Likewise.
	* syms.c (BSF_KEEP_G): Renamed to ...
	(BSF_ELF_COMMON): This.
	* bfd-in2.h: Regenerated.
	* config.in: Likewise.
	* configure: Likewise.

binutils/

	PR ld/19645
	* NEWS: Mention --elf-stt-common= for objcopy.
	* doc/binutils.texi: Document --elf-stt-common= for objcopy.
	* objcopy.c (do_elf_stt_common): New.
	(command_line_switch): Add OPTION_ELF_STT_COMMON.
	(copy_options): Add --elf-stt-common=.
	(copy_usage): Add --elf-stt-common=.
	(copy_object): Also check do_elf_stt_common for ELF targets.
	(copy_file): Handle do_elf_stt_common.
	(copy_main): Handle OPTION_ELF_STT_COMMON.
	* readelf.c (apply_relocations): Support STT_COMMON.
	* testsuite/binutils-all/common-1.s: New file.
	* testsuite/binutils-all/common-1a.d: Likewise.
	* testsuite/binutils-all/common-1b.d: Likewise.
	* testsuite/binutils-all/common-1c.d: Likewise.
	* testsuite/binutils-all/common-1d.d: Likewise.
	* testsuite/binutils-all/common-1e.d: Likewise.
	* testsuite/binutils-all/common-1f.d: Likewise.
	* testsuite/binutils-all/common-2.s: Likewise.
	* testsuite/binutils-all/common-2a.d: Likewise.
	* testsuite/binutils-all/common-2b.d: Likewise.
	* testsuite/binutils-all/common-2c.d: Likewise.
	* testsuite/binutils-all/common-2d.d: Likewise.
	* testsuite/binutils-all/common-2e.d: Likewise.
	* testsuite/binutils-all/common-2f.d: Likewise.
	* testsuite/binutils-all/objcopy.exp
	(objcopy_test_elf_common_symbols): New proc.
	Run objcopy_test_elf_common_symbols for ELF targets

gas/

	PR ld/19645
	* NEWS: Mention --enable-elf-stt-common and --elf-stt-common=
	for ELF assemblers.
	* as.c (flag_use_elf_stt_common): New.
	(show_usage): Add --elf-stt-common=.
	(option_values): Add OPTION_ELF_STT_COMMON.
	(std_longopts): Add --elf-stt-common=.
	(parse_args): Handle --elf-stt-common=.
	* as.h (flag_use_elf_stt_common): New.
	* config.in: Regenerated.
	* configure: Likewise.
	* configure.ac: Add --enable-elf-stt-common and define
	DEFAULT_GENERATE_ELF_STT_COMMON.
	* gas/write.c (write_object_file): Set BFD_CONVERT_ELF_COMMON
	and BFD_USE_ELF_STT_COMMON if flag_use_elf_stt_common is set.
	* doc/as.texinfo: Document --elf-stt-common=.
	* testsuite/gas/elf/common3.s: New file.
	* testsuite/gas/elf/common3a.d: Likewise.
	* testsuite/gas/elf/common3b.d: Likewise.
	* testsuite/gas/elf/common4.s: Likewise.
	* testsuite/gas/elf/common4a.d: Likewise.
	* testsuite/gas/elf/common4b.d: Likewise.
	* testsuite/gas/i386/dw2-compress-3b.d: Likewise.
	* testsuite/gas/i386/dw2-compressed-3b.d: Likewise.
	* testsuite/gas/elf/elf.exp: Run common3a, common3b, common4a
	and common4b.
	* testsuite/gas/i386/dw2-compress-3.d: Renamed to ...
	* testsuite/gas/i386/dw2-compress-3a.d: This.  Pass
	--elf-stt-common=no to as.
	* testsuite/gas/i386/dw2-compressed-3.d: Renamed to ...
	* testsuite/gas/i386/dw2-compressed-3a.d: This.  Pass
	--elf-stt-common=no to as.
	* testsuite/gas/i386/i386.exp: Run dw2-compress-3a,
	dw2-compress-3b, dw2-compressed-3a and dw2-compressed-3b instead
	of dw2-compress-3 and dw2-compressed-3.

include/

	PR ld/19645
	* bfdlink.h (bfd_link_elf_stt_common): New enum.
	(bfd_link_info): Add elf_stt_common.

ld/

	PR ld/19645
	* NEWS: Mention -z common/-z nocommon for ELF targets.
	* emultempl/elf32.em (gld${EMULATION_NAME}_handle_option): Handle
	-z common and -z nocommon.
	* ld.texinfo: Document -z common/-z nocommon.
	* lexsup.c (elf_shlib_list_options): Add -z common/-z nocommon.
	* testsuite/ld-elf/tls_common.exp: Test --elf-stt-common=no and
	--elf-stt-common=yes with assembler.
	* testsuite/ld-elfcomm/common-1.s: New file.
	* testsuite/ld-elfcomm/common-1a.d: Likewise.
	* testsuite/ld-elfcomm/common-1b.d: Likewise.
	* testsuite/ld-elfcomm/common-1c.d: Likewise.
	* testsuite/ld-elfcomm/common-1d.d: Likewise.
	* testsuite/ld-elfcomm/common-1e.d: Likewise.
	* testsuite/ld-elfcomm/common-1f.d: Likewise.
	* testsuite/ld-elfcomm/common-2.s: Likewise.
	* testsuite/ld-elfcomm/common-2a.d: Likewise.
	* testsuite/ld-elfcomm/common-2b.d: Likewise.
	* testsuite/ld-elfcomm/common-2c.d: Likewise.
	* testsuite/ld-elfcomm/common-2d.d: Likewise.
	* testsuite/ld-elfcomm/common-2e.d: Likewise.
	* testsuite/ld-elfcomm/common-2f.d: Likewise.
	* testsuite/ld-elfcomm/common-3a.rd: Likewise.
	* testsuite/ld-elfcomm/common-3b.rd: Likewise.
	* testsuite/ld-i386/pr19645.d: Likewise.
	* testsuite/ld-i386/pr19645.s: Likewise.
	* testsuite/ld-x86-64/largecomm-1.s: Likewise.
	* testsuite/ld-x86-64/largecomm-1a.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1b.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1c.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1d.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1e.d: Likewise.
	* testsuite/ld-x86-64/largecomm-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19645.d: Likewise.
	* testsuite/ld-x86-64/pr19645.s: Likewise.
	* testsuite/ld-elfcomm/elfcomm.exp: Test --elf-stt-common=yes
	with assembler.
	(assembler_generates_commons): Removed.
	Run -z common/-z nocommon tests.  Run *.d tests.
	* testsuite/ld-i386/i386.exp: Run pr19645.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-x86-64/dwarfreloc.exp: Test --elf-stt-common with
	assembler.  Test STT_COMMON with readelf.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [x86] Resolve non-PIC undefweak symbols in executable
@ 2016-02-26 13:10 sergiodj+buildbot
  2016-02-26 15:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aec6b87e0b66d707ead62ca40d220ee78b4cf5a5 ***

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

[x86] Resolve non-PIC undefweak symbols in executable

For i386 and x86-64, non-PIC references to undefined weak symbols are
resolved without dynamic relocation when creating executable.  Resolved
undefined weak symbols are removed from the dynamic symbol table in
executable.  One exception is on i386, we need resolved undefined weak
symbols in the dynamic symbol table in PIE if input relocatable files
contain branchs without PLT so that we can branch to 0 with dynamic
relocation in text section.

This makes behaviors of dynamic executable and position independent
executable predictable with mixed PIC and non-PIC references to undefined
weak symbols.  If all references to undefined weak symbols are PIC,
dynamic relocations against undefined weak symbols will be generated
in executable unless -z nodynamic-undefined-weak is passed to linker.

bfd/

	PR ld/19636
	PR ld/19704
	PR ld/19719
	* elf32-i386.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): New.
	(elf_i386_link_hash_entry): Add has_got_reloc and
	has_non_got_reloc.
	(elf_i386_link_hash_table): Add interp.
	(elf_i386_link_hash_newfunc): Initialize has_got_reloc and
	has_non_got_reloc.
	(elf_i386_copy_indirect_symbol): Copy has_got_reloc and
	has_non_got_reloc.
	(elf_i386_check_relocs): Set has_got_reloc and has_non_got_reloc.
	(elf_i386_fixup_symbol): New function.
	(elf_i386_pie_finish_undefweak_symbol): Likewise.
	(elf_i386_allocate_dynrelocs): Don't allocate space for dynamic
	relocations and discard relocations against resolved undefined
	weak symbols in executable.  Don't make resolved undefined weak
	symbols in executable dynamic.  Keep dynamic non-GOT/non-PLT
	relocation against undefined weak symbols in PIE.
	(elf_i386_size_dynamic_sections): Set interp to .interp section.
	(elf_i386_relocate_section): Don't generate dynamic relocations
	against resolved undefined weak symbols in PIE, except for
	R_386_PC32.
	(elf_i386_finish_dynamic_symbol): Keep PLT/GOT entries without
	dynamic PLT/GOT relocations for resolved undefined weak symbols.
	Don't generate dynamic relocation against resolved undefined weak
	symbol in executable.
	(elf_i386_finish_dynamic_sections): Call
	elf_i386_pie_finish_undefweak_symbol on all symbols in PIE.
	(elf_backend_fixup_symbol): New.
	* elf64-x86-64.c (UNDEFINED_WEAK_RESOLVED_TO_ZERO): New.
	(elf_x86_64_link_hash_entry): Add has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_link_hash_table): Add interp.
	(elf_x86_64_link_hash_newfunc): Initialize has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_copy_indirect_symbol): Copy has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_check_relocs): Set has_got_reloc and
	has_non_got_reloc.
	(elf_x86_64_fixup_symbol): New function.
	(elf_x86_64_pie_finish_undefweak_symbol): Likewise.
	(elf_x86_64_allocate_dynrelocs): Don't allocate space for dynamic
	relocations and discard relocations against resolved undefined
	weak symbols in executable.  Don't make resolved undefined weak
	symbols in executable dynamic.
	(elf_x86_64_size_dynamic_sections): Set interp to .interp section.
	(elf_x86_64_relocate_section): Check relocation overflow for
	dynamic relocations against unresolved weak undefined symbols.
	Don't generate dynamic relocations against resolved weak
	undefined symbols in PIE.
	(elf_x86_64_finish_dynamic_symbol): Keep PLT/GOT entries without
	dynamic PLT/GOT relocations for resolved undefined weak symbols.
	Don't generate dynamic relocation against resolved undefined weak
	symbol in executable.
	(elf_x86_64_finish_dynamic_sections): Call
	elf_x86_64_pie_finish_undefweak_symbol on all symbols in PIE.
	(elf_backend_fixup_symbol): New.

include/

	PR ld/19636
	PR ld/19704
	PR ld/19719
	* bfdlink.h (bfd_link_info): Add dynamic_undefined_weak.

ld/

	PR ld/19636
	PR ld/19704
	PR ld/19719
	* Makefile.am (ELF_X86_DEPS): Add dynamic_undefined_weak.sh.
	* Makefile.in: Regenerated.
	* NEWS: Mention -z nodynamic-undefined-weak.
	* ld.texinfo: Document -z nodynamic-undefined-weak.
	* ldmain.c (main): Initialize dynamic_undefined_weak to -1.
	* emulparams/dynamic_undefined_weak.sh: New file.
	* emulparams/elf32_x86_64.sh: Source dynamic_undefined_weak.sh.
	* emulparams/elf_i386.sh: Likewise.
	* emulparams/elf_i386_be.sh: Likewise.
	* emulparams/elf_i386_chaos.sh: Likewise.
	* emulparams/elf_i386_ldso.sh: Likewise.
	* emulparams/elf_i386_vxworks.sh: Likewise.
	* emulparams/elf_iamcu.sh: Likewise.
	* emulparams/elf_k1om.sh: Likewise.
	* emulparams/elf_l1om.sh: Likewise.
	* emulparams/elf_x86_64.sh: Likewise.
	* emulparams/extern_protected_data.sh (PARSE_AND_LIST_OPTIONS):
	Append.
	(PARSE_AND_LIST_ARGS_CASE_Z): Likewise.
	* testsuite/ld-elf/pr19719a.c: New file.
	* testsuite/ld-elf/pr19719b.c: Likewise.
	* testsuite/ld-elf/pr19719c.c: Likewise.
	* testsuite/ld-elf/pr19719d.c: Likewise.
	* testsuite/ld-i386/pr19636-1.s: Likewise.
	* testsuite/ld-i386/pr19636-1a.d: Likewise.
	* testsuite/ld-i386/pr19636-1b.d: Likewise.
	* testsuite/ld-i386/pr19636-1c.d: Likewise.
	* testsuite/ld-i386/pr19636-1d-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-1d.d: Likewise.
	* testsuite/ld-i386/pr19636-1e.d: Likewise.
	* testsuite/ld-i386/pr19636-1f.d: Likewise.
	* testsuite/ld-i386/pr19636-1g.d: Likewise.
	* testsuite/ld-i386/pr19636-1h.d: Likewise.
	* testsuite/ld-i386/pr19636-1i.d: Likewise.
	* testsuite/ld-i386/pr19636-2.s: Likewise.
	* testsuite/ld-i386/pr19636-2a.d: Likewise.
	* testsuite/ld-i386/pr19636-2b.d: Likewise.
	* testsuite/ld-i386/pr19636-2c-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-2c.d: Likewise.
	* testsuite/ld-i386/pr19636-2d-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-2d.d: Likewise.
	* testsuite/ld-i386/pr19636-2e-nacl.d: Likewise.
	* testsuite/ld-i386/pr19636-2e.d: Likewise.
	* testsuite/ld-i386/pr19636-3.s: Likewise.
	* testsuite/ld-i386/pr19636-3a.d: Likewise.
	* testsuite/ld-i386/pr19636-3b.d: Likewise.
	* testsuite/ld-i386/pr19636-3c.d: Likewise.
	* testsuite/ld-i386/pr19636-3d.d: Likewise.
	* testsuite/ld-i386/pr19636-3e.d: Likewise.
	* testsuite/ld-i386/pr19636-3f.d: Likewise.
	* testsuite/ld-i386/pr19636-3g.d: Likewise.
	* testsuite/ld-i386/pr19636-4.s: Likewise.
	* testsuite/ld-i386/pr19636-4a.d: Likewise.
	* testsuite/ld-i386/pr19636-4b.d: Likewise.
	* testsuite/ld-i386/pr19636-4c.d: Likewise.
	* testsuite/ld-i386/pr19636-4d.d: Likewise.
	* testsuite/ld-i386/pr19704.out: Likewise.
	* testsuite/ld-i386/pr19704a.c: Likewise.
	* testsuite/ld-i386/pr19704b.c: Likewise.
	* testsuite/ld-x86-64/pr19636-1.s: Likewise.
	* testsuite/ld-x86-64/pr19636-1a.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1b.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1c.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1d.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1e.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1f.d: Likewise.
	* testsuite/ld-x86-64/pr19636-1g.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2.s: Likewise.
	* testsuite/ld-x86-64/pr19636-2a.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2b.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2c.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2d-nacl.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2d.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2e.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2f.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2g.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2h.d: Likewise.
	* testsuite/ld-x86-64/pr19636-2i.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3.s: Likewise.
	* testsuite/ld-x86-64/pr19636-3a.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3b.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3c.d: Likewise.
	* testsuite/ld-x86-64/pr19636-3d.d: Likewise.
	* testsuite/ld-x86-64/pr19704.out: Likewise.
	* testsuite/ld-x86-64/pr19704a.c: Likewise.
	* testsuite/ld-x86-64/pr19704b.c: Likewise.
	* testsuite/ld-elf/shared.exp (mix_pic_and_non_pic): New.
	Run mix_pic_and_non_pic.
	* testsuite/ld-i386/i386.exp (undefined_weak): New.
	Run undefined_weak and PR ld/19636 tests.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-x86-64/pr13082-3b.d: Updated.
	* testsuite/ld-x86-64/pr13082-4b.d: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix powerpc64 -r --save-restore-funcs
@ 2016-02-26 13:00 sergiodj+buildbot
  2016-02-26 13:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-26 13:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b32547cd11bec3baf53e0dedf3c733cd3e0839f6 ***

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

Fix powerpc64 -r --save-restore-funcs

	* elf64-ppc.c (create_linkage_sections): Create sfpr when
	save_restore_funcs, rest of sections when not relocatable.
	(ppc64_elf_init_stub_bfd): Always call create_linkage_sections.
	(sfpr_define): Define all symbols on emitted code.
	(ppc64_elf_func_desc_adjust): Adjust for sfpr now being created
	when relocatable.  Move sfpr_define loop earlier.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>]
[parent not found: <ae91f6253926e4dadebcae90772f4f5a5bd06056@gdb-build>]
[parent not found: <678b48b7cf0bd518ebc234bda98229cc602c2a45@gdb-build>]
* [binutils-gdb] Remove gdb.base/branches.c
@ 2016-02-25 17:22 sergiodj+buildbot
  2016-02-25 21:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cb59ff1111c1d5e955ca0eeddab6f03db0fbfb7 ***

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

Remove gdb.base/branches.c

This patch removes gdb.base/branches.c which was added by the following
commit, but it is not used at all.

commit ea8122af1432abdeb256b2c669eb3d0cf8cb97bf
Author: John Metzler <jmetzler@cygnus>
Date:   Thu Apr 16 17:56:11 1998 +0000

    Thu Apr 16 10:52:34 1998  John Metzler  <jmetzler@cygnus.com>

        * gdb.base/branches.c: Code with lots of loops and
        subroutines. Used to test gdbs ability to single step through PC
        changes, especially to test mips-tdep.c:mips_next_pc

gdb/testsuite:

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

	* gdb.base/branches.c: Remove.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation
@ 2016-02-25 14:46 sergiodj+buildbot
  2016-02-25 15:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1eb7c2d886c0faac42d2b68862b0e6b0d3182d98 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 1eb7c2d886c0faac42d2b68862b0e6b0d3182d98

Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation

When encoding the agent expression operation ax_reg or ax_reg_mask, the
register number used is internal to GDB. However GDBServer expects a tdesc
based number.

This usually does not cause a problem since at the moment, for raw
registers GDBServer R trace action ignores the register mask and just
collects all registers.

It can be a problem, however with pseudo registers on some platforms if the
tdesc number doesn't match the GDB internal register number.

This is the case with ARM, the upcoming ARM tracepoint support, fails
these test cases without this patch:

gdb.trace/collection.exp: collect register locals collectively:*

GDBSever would exit with: unhandled register size
Since the register number is not mapped.

This patch fixes these issues by calling gdbarch_remote_register_number
before encoding the register number in the ax_reg or ax_reg_mask operation.

Tested on x86 native-gdbserver no regressions observed.

gdb/ChangeLog:

	* ax-general.c (ax_reg): Call gdbarch_remote_register_number.
	(ax_reg_mask): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add elf_x86_64_need_pic
@ 2016-02-25 12:24 sergiodj+buildbot
  2016-02-25 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-25 12:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef77d6af7cade17c566e4d1ecff098b841972f17 ***

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

Add elf_x86_64_need_pic

Add elf_x86_64_need_pic and replace x86_64_elf_howto_table[r_type].name
with howto->name.

	* elf64-x86-64.c (elf_x86_64_need_pic): New function.
	(elf_x86_64_relocate_section): Use it.  Replace
	x86_64_elf_howto_table[r_type] with howto.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Update symbol version for symbol from linker script
@ 2016-02-24 23:37 sergiodj+buildbot
  2016-02-25  1:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 23:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f550b3df1d4ae31d12505cf93981313c9c6dd25 ***

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

Update symbol version for symbol from linker script

We need to update symbol version for symbols from linker script.

bfd/

	PR ld/19698
	* elflink.c (bfd_elf_record_link_assignment): Set versioned if
	symbol version is unknown.

ld/

	PR ld/19698
	* testsuite/ld-elf/pr19698.d: New file.
	* testsuite/ld-elf/pr19698.s: Likewise.
	* testsuite/ld-elf/pr19698.t: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <338435ef105ff51e967571ad073830ec1eb5a4ab@gdb-build>]
* [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp
@ 2016-02-24 19:30 sergiodj+buildbot
  2016-02-24 19:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 861ca91fc65b9a53b807f6d5c5253fc33f92e7d8

Move tfile-avx.exp to tracefile-pseudo-reg.exp

As it is planned to add more architectures to this test, rename to a more
generic name.

gdb/testsuite/ChangeLog:

	* gdb.trace/tfile-avx.c: Move to...
	* gdb.trace/tracefile-pseudo-reg.c: Here.
	* gdb.trace/tfile-avx.exp: Move to...
	* gdb.trace/tracefile-pseudo-reg.exp: Here.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Move new skip features to proper section (post 7.11).
@ 2016-02-24 18:24 sergiodj+buildbot
  2016-02-24 18:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2dffb8d3be366d4d02de06e92c24c9abdb0adfc ***

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

Move new skip features to proper section (post 7.11).


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] powerpc: Support z-point type in gdbserver.
@ 2016-02-24 17:45 sergiodj+buildbot
  2016-02-24 17:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 17:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 657f9cde9d531c9929bef9e02a8064101d568f50 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 657f9cde9d531c9929bef9e02a8064101d568f50

powerpc: Support z-point type in gdbserver.

Support z-point, so tracepoints and breakpoints can be inserted at the same
location.

gdb/gdbserver/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* linux-ppc-low.c (ppc_supports_z_point_type): New function:
	(ppc_insert_point, ppc_remove_point): Insert/remove z-packet breakpoints.
	(ppc64_emit_ops_vector): Add target ops - ppc_supports_z_point_type,
	ppc_insert_point, ppc_remove_point.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Revert "ABS32"
@ 2016-02-24 15:09 sergiodj+buildbot
  2016-02-24 16:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 15:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92d77487b3dbfd934c5565bab09e0f3051e0b08d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 92d77487b3dbfd934c5565bab09e0f3051e0b08d

Revert "ABS32"

This reverts commit 30bdf5c82e5734ac9f0b18eb7af631806d419270.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.
@ 2016-02-24 14:22 sergiodj+buildbot
  2016-02-24 15:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0c11777665276f8e9b590bbe4832a7c66f5093d ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: b0c11777665276f8e9b590bbe4832a7c66f5093d

[OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Add fp16 instruction entries.
	(print_insn_coprocessor): Support fp16 instruction.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.d: Adjust output.
	* testsuite/gas/arm/copro.s: Adjust co-processor num.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [OPCODES][ARM]Fix mask for a few coprocessor opcodes.
@ 2016-02-24 14:12 sergiodj+buildbot
  2016-02-24 15:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e309328e8d91e37f2f3cea15f8a686d3bdfa700 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 3e309328e8d91e37f2f3cea15f8a686d3bdfa700

[OPCODES][ARM]Fix mask for a few coprocessor opcodes.

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (coprocessor_opcodes): Fix mask for vsel, vmaxnm, vminnm,
	vrint(mpna).

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/mask_1.d: New.
	* testsuite/gas/arm/mask_1.s: New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2
@ 2016-02-24 14:09 sergiodj+buildbot
  2016-02-24 15:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8afc7bea4018bf535902503c9a25dd4a96dfa3ca ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 8afc7bea4018bf535902503c9a25dd4a96dfa3ca

[OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2

opcodes/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* arm-dis.c (print_insn_coprocessor): Check co-processor number for
	cpd/cpd2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2.

gas/

2016-02-24  Renlin Li  <renlin.li@arm.com>

	* testsuite/gas/arm/copro.s: Use coprocessor other than 10, 11.
	* testsuite/gas/arm/copro.d: Update.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ABS32
@ 2016-02-24 14:07 sergiodj+buildbot
  2016-02-24 14:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 14:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30bdf5c82e5734ac9f0b18eb7af631806d419270 ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: 30bdf5c82e5734ac9f0b18eb7af631806d419270

ABS32


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Set plt_got.offset to (bfd_vma) -1
@ 2016-02-24 13:54 sergiodj+buildbot
  2016-02-24 14:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13f422778ff5307dad1f66d25a1d211bb8f76a8b ***

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

Set plt_got.offset to (bfd_vma) -1

Since plt_got.offset may be updated in x86 allocate_dynrelocs, set
plt_got.offset to (bfd_vma) -1 when setting needs_plt to 0.

	* elf32-i386.c (elf_i386_allocate_dynrelocs): Set plt_got.offset
	to (bfd_vma) -1 when setting needs_plt to 0.
	* elf64-x86-64.c (elf_x86_64_allocate_dynrelocs): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix logic in exec_file_locate_attach
@ 2016-02-24 12:00 sergiodj+buildbot
  2016-02-24 12:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24 12:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf74e428bca61022bd5cdf6bf28789a184748b4d ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: bf74e428bca61022bd5cdf6bf28789a184748b4d

Fix logic in exec_file_locate_attach

This commit fixes an error in exec_file_locate_attach where
the main executable could be loaded from outside the sysroot
if a nonempty, non-"target:" sysroot was set but the discovered
executable filename did not exist in that sysroot and did exist
on the main filesystem.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Do not attempt to
	locate main executable locally if not found in sysroot.

gdb/testsuite/ChangeLog:

	* gdb.base/attach-pie-noexec.exp: Do not expect an error
	message on attach.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Build unavailable-stack frames for tracepoint.
@ 2016-02-24  3:22 sergiodj+buildbot
  2016-02-24  3:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-24  3:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50ae56ec464580492a5f987f658acc6ad82131b6 ***

Author: Wei-cheng Wang <cole945@gmail.com>
Branch: master
Commit: 50ae56ec464580492a5f987f658acc6ad82131b6

Build unavailable-stack frames for tracepoint.

gdb/ChangeLog:

2016-02-24  Wei-cheng Wang  <cole945@gmail.com>

	* rs6000-tdep.c (rs6000_frame_cache, rs6000_frame_this_id): Handle
	unavailable PC/SP to build unavailable frame.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction.
@ 2016-02-23 21:37 sergiodj+buildbot
  2016-02-23 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cce0e92333b872cfe036aae611b6b5d61cf58186 ***

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

Extend "skip" command to support -file, -gfile, -function, -rfunction.

gdb/ChangeLog:

	Extend "skip" command to support -file, -gfile, -function, -rfunction.
	* NEWS: Document new features.
	* skip.c: #include "fnmatch.h", "gdb_regex.h".
	(skiplist_entry) <file>: Renamed from filename.
	<function>: Renamed from function_name.
	<file_is_glob, function_is_regexp>: New members.
	<compiled_function_regexp, compiled_function_regexp_is_valid>:
	New members.
	(make_skip_entry): New function.
	(free_skiplist_entry, free_skiplist_entry_cleanup): New functions.
	(make_free_skiplist_entry_cleanup): New function.
	(skip_file_command): Update.
	(skip_function, skip_function_command): Update.
	(compile_skip_regexp): New functions.
	(skip_command): Add support for new options.
	(skip_info): Update.
	(skip_file_p, skip_gfile_p): New functions.
	(skip_function_p, skip_rfunction_p): New functions.
	(function_name_is_marked_for_skip): Update and simplify.
	(_initialize_step_skip): Update.
	* symtab.c: #include "fnmatch.h".
	(compare_glob_filenames_for_search): New function.
	* symtab.h (compare_glob_filenames_for_search): Declare.
	* utils.c (count_path_elements): New function.
	(strip_leading_path_elements): New function.
	* utils.h (count_path_elements): Declare.
	(strip_leading_path_elements): Declare.

gdb/doc/ChangeLog:

	* gdb.texinfo (Skipping Over Functions and Files): Document new
	options to "skip" command.  Update docs of output of "info skip".

gdb/testsuite/ChangeLog:

	* gdb.base/skip.c (test_skip): New function.
	(end_test_skip_file_and_function): New function.
	(test_skip_file_and_function): New function.
	* gdb.base/skip1.c (test_skip): New function.
	(skip1_test_skip_file_and_function): New function.
	* gdb.base/skip.exp: Add tests for new skip options.
	* gdb.base/skip-solib.exp: Update expected output.
	* gdb.perf/skip-command.cc: New file.
	* gdb.perf/skip-command.exp: New file.
	* gdb.perf/skip-command.py: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] arm-tdep.c: Remove unused "to" parameters
@ 2016-02-23 18:34 sergiodj+buildbot
  2016-02-23 18:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1254566561957d2202d61e12881b0eb40d33a64c ***

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

arm-tdep.c: Remove unused "to" parameters

gdb/ChangeLog:

	* arm-tdep.c (arm_decode_svc_copro): Remove "to" parameter.
	(thumb_process_displaced_insn): Likewise.
	(arm_process_displaced_insn): Adjust calls.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks.
@ 2016-02-23 13:10 sergiodj+buildbot
  2016-02-23 13:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-23 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17733f5be961baa7a47fdf1471aa6948372293d6 ***

Author: Faraz Shahbazker <faraz.shahbazker@imgtec.com>
Branch: master
Commit: 17733f5be961baa7a47fdf1471aa6948372293d6

Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks.

	* bfd/elfxx-mips.c (_bfd_mips_post_process_headers): Increment
	ABIVERSION for non-executable stack.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Always create dynsym section with dynamic sections
@ 2016-02-23  0:43 sergiodj+buildbot
  2016-02-23  4:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-23  0:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a6e6083b69dcb695e175b5dc02342391da6ba22 ***

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

Always create dynsym section with dynamic sections

We should always create the dynsym section, even if it is empty, with
dynamic sections.

	* elflink.c (_bfd_elf_link_renumber_dynsyms): Always create the
	dynsym section, even if it is empty, with dynamic sections.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <4000e47e2f3860a85a9023f3fe5950c8cc6fa507@gdb-build>]
* [binutils-gdb] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'
@ 2016-02-22 16:37 sergiodj+buildbot
  2016-02-22 18:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 16:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac46107c5c781894e013b10cd9fb5c98a8393d26 ***

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

gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'

After building GDB
	--with-python=/usr/bin/python3
and for example stripping ./gdb and running:
	./gdb -data-directory data-directory/ -iex "add-auto-load-safe-path $PWD/gdb-gdb.gdb" -iex "add-auto-load-safe-path $PWD/gdb-gdb.
py" ./gdb
I get:
	Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
	  File "/home/jkratoch/redhat/gdb-test-python3/gdb/gdb-gdb.py", line 91
	    print "Warning: Cannot find enum type_flag_value type."
								  ^
	SyntaxError: Missing parentheses in call to 'print'
	(top-gdb) q

gdb/ChangeLog
2016-02-22  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb-gdb.py (class TypeFlagsPrinter): Use parentheses for print.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix arm process record code format
@ 2016-02-22 12:26 sergiodj+buildbot
  2016-02-22 12:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-22 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01e57735b0e8e6a613c58c271350dac2c416bb03 ***

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

Fix arm process record code format

This patch fixes the various code format issues in arm process record
in arm-tdep.c, such as using tab instead of spaces.

gdb:

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

	* arm-tdep.c: Fix code format issues.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Also update recursive call to d_lookup_symbol_imports.
@ 2016-02-21 21:15 sergiodj+buildbot
  2016-02-21 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 21:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: e08db6db1dd514f1c99f94bb6a9c1cfe02a1ab90

Also update recursive call to d_lookup_symbol_imports.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports.
@ 2016-02-21 20:46 sergiodj+buildbot
  2016-02-21 20:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-21 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 30a6a7f035026d05b52c92c26d4cb7ea3c6d6e5c

Remove search_parents parameter from d_lookup_symbol_imports.

gdb/ChangeLog:

	* d-namespace.c (d_lookup_symbol_imports): Remove argument
	'search_parents'.  All callers updated.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.
@ 2016-02-19 16:10 sergiodj+buildbot
  2016-02-19 17:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e517df3dbf7556ddb389228d713a804594ee3c1f ***

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

Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary.

	PR ld/19629
	* aoutx.h (aout_link_add_symbols): Check for out of range string
	table offsets.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Add FP16 feature extension for ARMv8.2 architecture
@ 2016-02-19 14:40 sergiodj+buildbot
  2016-02-19 15:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-19 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8ec4e871ef7650b852df9956841ee414766de59 ***

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

[ARM] Add FP16 feature extension for ARMv8.2 architecture

include/
  * opcode/arm.h (ARM_EXT2_FP16_INSN): New.

gas/
  * config/tc-arm.c (arm_ext_fp16): New.
  (arm_extensions): New entry for "fp16".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add D support to gdb_default_target_compile.
@ 2016-02-18 21:14 sergiodj+buildbot
  2016-02-18 22:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24f75eadabc519563ed119932c77874a016a799a ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 24f75eadabc519563ed119932c77874a016a799a

Add D support to gdb_default_target_compile.

gdb/testsuite/ChangeLog:

	* lib/future.exp: Add D support.
	(gdb_find_gdc): New proc.
	(gdb_default_target_compile): Add D support.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>]
[parent not found: <5f034a78b986d30a90030b2409c61a8660b9b48c@gdb-build>]
* [binutils-gdb] Intel MPX bound violation handling
@ 2016-02-18 16:46 sergiodj+buildbot
  2016-02-18 18:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 012b3a217a60cc74b802b059029c72a25d77808c ***

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

Intel MPX bound violation handling

With Intel Memory Protection Extensions it was introduced the concept of
boundary violation.  A boundary violations is presented to the inferior as
a segmentation fault having SIGCODE 3.  This patch adds a
handler for a boundary violation extending the information displayed
when a bound violation is presented to the inferior.  In the stop mode
case the debugger will also display the kind of violation: "upper" or
"lower", bounds and the address accessed.
On no stop mode the information will still remain unchanged.  Additional
information about bound violations are not meaningful in that case user
does not know the line in which violation occurred as well.

When the segmentation fault handler is stop mode the out puts will be
changed as exemplified below.

The usual output of a segfault is:
Program received signal SIGSEGV, Segmentation fault
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68        value = *(p + len);

In case it is a bound violation it will be presented as:
Program received signal SIGSEGV, Segmentation fault
Upper bound violation while accessing address 0x7fffffffc3b3
Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3]
0x0000000000400d7c in upper (p=0x603010, a=0x603030, b=0x603050,
c=0x603070, d=0x603090, len=7) at i386-mpx-sigsegv.c:68
68        value = *(p + len);

In mi mode the output of a segfault is:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault", frame={addr="0x0000000000400d7c",
func="upper",args=[{name="p", value="0x603010"},{name="a",value="0x603030"}
,{name="b",value="0x603050"}, {name="c",value="0x603070"},
{name="d",value="0x603090"},{name="len",value="7"}],
file="i386-mpx-sigsegv.c",fullname="i386-mpx-sigsegv.c",line="68"},
thread-id="1",stopped-threads="all",core="6"

in the case of a bound violation:
*stopped,reason="signal-received",signal-name="SIGSEGV",
signal-meaning="Segmentation fault",
sigcode-meaning="Upper bound violation",
lower-bound="0x603010",upper-bound="0x603023",bound-access="0x60302f",
frame={addr="0x0000000000400d7c",func="upper",args=[{name="p",
value="0x603010"},{name="a",value="0x603030"},{name="b",value="0x603050"},
{name="c",value="0x603070"},{name="d",value="0x603090"},
{name="len",value="7"}],file="i386-mpx-sigsegv.c",
fullname="i386-mpx-sigsegv.c",line="68"},thread-id="1",
stopped-threads="all",core="6"

2016-02-18  Walfred Tedeschi  <walfred.tedeschi@intel.com>

gdb/ChangeLog:

	* NEWS: Add entry for bound violation.
	* amd64-linux-tdep.c (amd64_linux_init_abi_common):
	Add handler for segmentation fault.
	* gdbarch.sh (handle_segmentation_fault): New.
	* gdbarch.c: Regenerate.
	* gdbarch.h: Regenerate.
	* i386-linux-tdep.c (i386_linux_handle_segmentation_fault): New.
	(SIG_CODE_BONDARY_FAULT): New define.
	(i386_linux_init_abi): Use i386_mpx_bound_violation_handler.
	* i386-linux-tdep.h (i386_linux_handle_segmentation_fault) New.
	* i386-tdep.c (i386_mpx_enabled): Add as external.
	* i386-tdep.c (i386_mpx_enabled): Add as external.
	* infrun.c (handle_segmentation_fault): New function.
	(print_signal_received_reason): Use handle_segmentation_fault.

gdb/testsuite/ChangeLog:

	* gdb.arch/i386-mpx-sigsegv.c: New file.
	* gdb.arch/i386-mpx-sigsegv.exp: New file.
	* gdb.arch/i386-mpx-simple_segv.c: New file.
	* gdb.arch/i386-mpx-simple_segv.exp: New file.

gdb/doc/ChangeLog:

	* gdb.texinfo (Signals): Add bound violation display hints for
	a SIGSEGV.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove setup_kfail server/13796 in disp-step-syscall.exp
@ 2016-02-18 13:17 sergiodj+buildbot
  2016-02-18 14:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d5189bd3a6e2014b9b42a4bcb0df410eff1c2e1 ***

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

Remove setup_kfail server/13796 in disp-step-syscall.exp

This patch series add fork support in target remote,

  [PATCH v2 0/3] Target remote mode fork and exec support
  https://sourceware.org/ml/gdb-patches/2015-12/msg00144.html

so GDB can be informed about the child, and adjust child correctly in
displaced stepping.  The PR server/13796 was fixed by this patch
series actually.  Test results on buildbot show this KFAIL->KPASS
change https://sourceware.org/ml/gdb-testers/2015-q4/msg10128.html

gdb/testsuite:

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

	* gdb.base/disp-step-syscall.exp (disp_step_cross_syscall):
	Don't call setup_kfail.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp
@ 2016-02-18 12:18 sergiodj+buildbot
  2016-02-18 12:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-18 12:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 40fb20d037581bc9d4b17b6ab64ee98825cfacab ***

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

Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp

Proc do_test in forking-threads-plus-breakpoint.exp has an argument
cond_bp_target, but the test doesn't use it to set
"breakpoint condition-evaluation", which is an oversight in the test.

This patch fixes it by setting "breakpoint condition-evaluation" per
$cond_bp_target.

gdb/testsuite:

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

	* gdb.threads/forking-threads-plus-breakpoint.exp (do_test):
	Set "set breakpoint condition-evaluation" per $cond_bp_target.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add missing cleanup in exec_file_locate_attach
@ 2016-02-17 17:04 sergiodj+buildbot
  2016-02-17 17:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-17 17:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88178e828a0d1af133c19d6165e4d5ee59304adf ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 88178e828a0d1af133c19d6165e4d5ee59304adf

Add missing cleanup in exec_file_locate_attach

exec_file_locate_attach allocates memory for full_exec_path (using
either exec_file_find, source_full_path_of or xstrdup) but this
memory is never freed.  This commit adds the necessary cleanup.

gdb/ChangeLog:

	* exec.c (exec_file_locate_attach): Add missing cleanup.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR remote/19496, internal err forking-threads-plus-bkpt
@ 2016-02-16 17:09 sergiodj+buildbot
  2016-02-17  1:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4041ed778095ed74f7cb9cdaac4115597f35147c ***

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

PR remote/19496, internal err forking-threads-plus-bkpt

This patch fixes an internal error that occurs in
gdb.threads/forking-threads-plus-breakpoint.exp:

/blah/binutils-gdb/gdb/target.c:2723: internal-error: Can't determine the
current address space of thread Thread 3170.3170

In default_thread_address_space, find_inferior_ptid couldn't find 3170.3170
because it had been overwritten in inferior_appeared, called as follows:

inferior_appeared
  remote_add_inferior
    remote_notice_new_inferior
      remote_update_thread_list

The cause of the problem was the following sequence of events:

* GDB knows only about the main thread

* the first fork event is reported to GDB, saved as pending_event

* qXfer:threads:read gets the threads from the remote.
  remove_new_fork_children id's the fork child from the pending event
  and removes it from the list reported to GDB.  All the rest of the
  threads, including the fork parent, are added to the GDB thread list.

* GDB stops all the threads.  All the stop events are pushed onto the
  stop reply queue behind the pending fork event.  The fork waitstatus
  is saved in the fork parent thread's pending status field
  thread_info.suspend.

* remote_wait_ns calls queued_stop_reply and process_stop_reply to
  remove the fork event from the front of the stop reply queue and save
  event information in the thread_info structure for the fork parent
  thread.  Unfortunately, none of the information saved in this way is
  the fork-specific information.

* A subsequent qXfer:threads:read packet gets the thread list including
  the fork parent and fork child.  remove_new_fork_children checks the
  thread list to see if there is a fork parent, doesn't find one, checks
  the stop reply queue for a pending fork event, doesn't find one, and
  allows the fork child thread to be reported to GDB before the fork
  event has been handled.  remote_update_thread_list calls
  remote_notice_new_thread and overwrites the current (main) thread in
  inferior_appeared.

So the fork event has been reported out of target_wait but it was left
pending on the infrun side (infrun.c:save_waitstatus).  IOW, the fork
event hasn't been processed by handle_inferior_event yet, so it hasn't
made it to tp->pending_follow yet.

The fix is to check thread_info.suspend along with the
thread_info.pending_follow in remote.c:remove_new_fork_children, to
prevent premature reporting of the fork child thread creation.

gdb/ChangeLog:

	PR remote/19496
	* remote.c (remove_new_fork_children): Check for pending
	fork status in thread_info.suspend.

gdb/testsuite/ChangeLog:

	PR remote/19496
	* gdb.threads/forking-threads-plus-breakpoint.exp (do_test):
	Remove kfail for PR remote/19496.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix cleanup in arm_linux_software_single_step
@ 2016-02-16 14:26 sergiodj+buildbot
  2016-02-16 19:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-16 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b442c911ee0e7444ee63edcc7da26089f6023cb6 ***

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

Fix cleanup in arm_linux_software_single_step

I see the following error in testing aarch64 GDB debugging arm
program.

(gdb) PASS: gdb.reverse/readv-reverse.exp: set breakpoint at marker2
continue
Continuing.
=================================================================
==32273==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x000000ce4c00 in thread T0
    #0 0x2ba5615645c7 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.1+0x545c7)^M
    #1 0x4be8b5 in VEC_CORE_ADDR_cleanup /home/yao/SourceCode/gnu/gdb/git/gdb/common/gdb_vecs.h:34^M
    #2 0x5e6d95 in do_my_cleanups /home/yao/SourceCode/gnu/gdb/git/gdb/common/cleanups.c:154^M
    #3 0x64c99a in fetch_inferior_event /home/yao/SourceCode/gnu/gdb/git/gdb/infrun.c:3975^M
    #4 0x678437 in inferior_event_handler /home/yao/SourceCode/gnu/gdb/git/gdb/inf-loop.c:44^M
    #5 0x5078f6 in remote_async_serial_handler /home/yao/SourceCode/gnu/gdb/git/gdb/remote.c:13223^M
    #6 0x4cecfd in run_async_handler_and_reschedule /home/yao/SourceCode/gnu/gdb/git/gdb/ser-base.c:137^M
    #7 0x676864 in gdb_wait_for_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:834^M
    #8 0x676a27 in gdb_do_one_event /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:323^M
    #9 0x676aed in start_event_loop /home/yao/SourceCode/gnu/gdb/git/gdb/event-loop.c:347^M
    #10 0x6706d2 in captured_command_loop /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:318^M
    #11 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #12 0x6716dd in captured_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1157^M
    #13 0x66db8c in catch_errors /home/yao/SourceCode/gnu/gdb/git/gdb/exceptions.c:240^M
    #14 0x671b7a in gdb_main /home/yao/SourceCode/gnu/gdb/git/gdb/main.c:1165^M
    #15 0x467684 in main /home/yao/SourceCode/gnu/gdb/git/gdb/gdb.c:32^M
    #16 0x2ba563ed7ec4 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)^M
    #17 0x4676b2 (/scratch/yao/gdb/build-git/aarch64-linux-gnu/gdb/gdb+0x4676b2)

looks we should discard cleanup if function
arm_linux_software_single_step returns early, or create cleanup when
it is needed.

gdb:

2016-02-16  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_software_single_step): Assign
	'old_chain' later.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add parentheses to prevent truncated addresses
@ 2016-02-16  0:16 sergiodj+buildbot
  2016-02-16 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-16  0:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd7268abff6f99dbbb78505f095bf1f54064db7 ***

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

Add parentheses to prevent truncated addresses

	* i386-dis.c (print_insn): Parenthesize expression to prevent
	truncated addresses.
	(OP_J): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't print 0x for core_addr_to_string_nz
@ 2016-02-15 10:19 sergiodj+buildbot
  2016-02-15 10:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-15 10:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a0da55626b632a8b8beb6c7878b866861e5daee ***

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

Don't print 0x for core_addr_to_string_nz

core_addr_to_string_nz returns string which has "0x" prefix, so don't
need to print "0x" again.  This patch is to remove the "0x".

gdb:

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

	* aarch64-tdep.c (aarch64_analyze_prologue): Remove "0x".


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Fix false Fortran regressions with recent gcc
@ 2016-02-14  8:44 sergiodj+buildbot
  2016-02-14 11:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-14  8:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba881f505ba211ffee59e68617cd1a02a7b4737b ***

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

testsuite: Fix false Fortran regressions with recent gcc

gcc-4.9.2-6.fc21.x86_64 -> gcc-5.3.1-2.fc23.x86_64

-PASS: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
+FAIL: gdb.fortran/vla-ptype.exp: ptype pvla not initialized
-PASS: gdb.fortran/vla-history.exp: print vla1 allocated
+FAIL: gdb.fortran/vla-history.exp: print vla1 allocated
-PASS: gdb.fortran/vla-history.exp: print $2
+FAIL: gdb.fortran/vla-history.exp: print $2
-PASS: gdb.fortran/vla-value.exp: print undefined pvla
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla
-PASS: gdb.fortran/vla-value.exp: print non-associated &pvla
+FAIL: gdb.fortran/vla-value.exp: print non-associated &pvla
-PASS: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)
+FAIL: gdb.fortran/vla-value.exp: print undefined pvla(1,3,8)

These issues get fixed (or removed if no longer applicable) by attached patch.

It is based on Googled:
	http://www.cs.rpi.edu/~szymansk/OOF90/bugs.html#5
	When a pointer is declared its status is undefined, and cannot be
	safely queried with the associated intrinsic.
	-> nullify(VARNAME)
+
	https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268786
	ALLOCATE is not supposed to initialize the array.
	-> Remove checks like an initial print is: \\( *0, *0, *0...\\)

These regressions remain:
	-PASS: gdb.fortran/library-module.exp: print var_i in lib
	+FAIL: gdb.fortran/library-module.exp: print var_i in lib
	-PASS: gdb.fortran/library-module.exp: print var_i in main
	+FAIL: gdb.fortran/library-module.exp: print var_i in main
I believe it is more a GDB bug (in a code contributed by me), filed:
	gdb.fortran/library-module.exp false regression on GCC upgrade
	https://sourceware.org/bugzilla/show_bug.cgi?id=19635

gdb/testsuite/ChangeLog
2016-02-14  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Fix compatibility with recent gfortran-5.3.1.
	* gdb.fortran/vla-history.exp (print vla1 allocated)
	(print vla2 allocated, print $2, print $3): Remove
	(print $4): Rename to ...
	(print $2): ... here.
	(print $9): Rename to ...
	(print $5): ... here.
	(print $10): Rename to ...
	(print $6): ... here.
	* gdb.fortran/vla.f90: Add pvla initialization.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <e44e00ffffe358d91df0ec4a11563eef0c14beb4@gdb-build>]
* [binutils-gdb] [ARM] Software single step cross kernel helpers
@ 2016-02-12 16:22 sergiodj+buildbot
  2016-02-12 17:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 16:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01113bc1c50ff1202517377afd7162861e66846f ***

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

[ARM] Software single step cross kernel helpers

GDB step cross kernel helpers only works if the kernel helpers are tail
called, which is the case how it is used in glibc.  See __aeabi_read_tp
in sysdeps/unix/sysv/linux/arm/aeabi_read_tp.S.  In __aeabi_read_tp,
branch/jump to the kernel helper is the last instruction, and the next
instruction address is in LR, which is in caller function.  GDB can
handle this correctly.  For example, glibc function __GI___ctype_init
calls __aeabi_read_tp

   0xb6e19b30 <__GI___ctype_init+4>:	ldr	r3, [pc, #80]	;
   0xb6e19b34 <__GI___ctype_init+8>:	bl	0xb6e0a6e0 <__aeabi_read_tp>
   0xb6e19b38 <__GI___ctype_init+12>:	ldr	r3, [pc, r3]

and __aeabi_read_tp calls kernel helper,

(gdb) disassemble __aeabi_read_tp
   0xb6fef5d0 <+0>:	mvn	r0, #61440	; 0xf000
   0xb6fef5d4 <+4>:	sub	pc, r0, #31

once GDB or GDBserver single step instruction on 0xb6fef5d4, LR is
0xb6e19b38, which is right address of next instruction to set breakpoint
on.

However, if the kernel helpers are not tail-called, the LR is still the
address in the caller function of kernel helper's caller, which isn't
the right address of next instruction to set breakpoint on.  For example,
we use kernel helper in main,

(gdb) disassemble main
....
   0x00008624 <+32>:    mov     r3, #4064       ; 0xfe0^M
   0x00008628 <+36>:    movt    r3, #65535      ; 0xffff^M
   0x0000862c <+40>:    blx     r3
   0x00008630 <+44>:    ldr     r3, [r11, #-8]

kernel helper is called on 0x0000862c and the expected next instruction
address is 0x00008630, but the LR now is the return address of main.
The problem here is LR may not have the right address because when we
single step the instruction, it isn't executed yet, so the LR isn't
updated.  This patch fix this problem by decoding instruction, if the
instruction updates LR (BL and BLX), the next instruction address is
PC + INSN_SIZE, otherwise, get the address of next instruction from LR.

gdb:

2016-02-12  Yao Qi  <yao.qi@linaro.org>

	* arch/arm-linux.c (arm_linux_get_next_pcs_fixup): Calculate
	nextpc according to instruction.

gdb/testsuite:

2016-02-12  Yao Qi  <yao.qi@linaro.org>

	* gdb.arch/arm-single-step-kernel-helper.c: New.
	* gdb.arch/arm-single-step-kernel-helper.exp: New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Fixup PC in software single step
@ 2016-02-12 16:11 sergiodj+buildbot
  2016-02-12 16:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-12 16:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed443b61e1f6e4eb7919fe9122dd947d1e87e767 ***

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

[ARM] Fixup PC in software single step

When I exercise GDBserver software single step, I see the following
error, which has been already handled by GDB properly.

In GDBserver log, we can see, GDBserver tries to single step instruction
on 0xb6e0a6e4, and destination address is 0xffff0fe0,

 stop pc is 0xb6e0a6e4
 Writing f001f0e7 to 0xffff0fe0 in process 7132
 Failed to insert breakpoint at 0xffff0fe0 (Input/output error).
 Failed to insert breakpoint at 0xffff0fe0 (-1).

(gdb) disassemble __aeabi_read_tp,+8
Dump of assembler code from 0xb6e0a6e0 to 0xb6e0a6e8:
   0xb6e0a6e0 <__aeabi_read_tp+0>:	mvn	r0, #61440	; 0xf000
   0xb6e0a6e4 <__aeabi_read_tp+4>:	sub	pc, r0, #31

however, it fails inserting breakpoint there.  This problem has already
fixed by GDB, see comments in arm-linux-tdep.c:arm_linux_software_single_step

      /* The Linux kernel offers some user-mode helpers in a high page.  We can
	 not read this page (as of 2.6.23), and even if we could then we
	 couldn't set breakpoints in it, and even if we could then the atomic
	 operations would fail when interrupted.  They are all called as
	 functions and return to the address in LR, so step to there
	 instead.  */

so we need to do the same thing in GDB side as well.  This patch adds
a new field fixup in arm_get_next_pcs_ops, so that we can fix up PC
for arm-linux target.  In this way, both GDB and GDBserver can single
step instructions going to kernel helpers.

gdb:

2016-02-12  Yao Qi  <yao.qi@linaro.org>

	* arch/arm-get-next-pcs.c (arm_get_next_pcs): Call
	self->ops->fixup if it isn't NULL.
	* arch/arm-get-next-pcs.h: Include gdb_vecs.h.
	(struct arm_get_next_pcs_ops) <fixup>: New field.
	* arch/arm-linux.c: Include common-regcache.h and
	arch/arm-get-next-pcs.h.
	(arm_linux_get_next_pcs_fixup): New function.
	* arch/arm-linux.h (arm_linux_get_next_pcs_fixup): Declare.
	* arm-linux-tdep.c (arm_linux_get_next_pcs_ops): Initialize
	it with arm_linux_get_next_pcs_fixup.
	(arm_linux_software_single_step): Move code to
	arm_linux_get_next_pcs_fixup.
	* arm-tdep.c (arm_get_next_pcs_ops): Initialize it.

gdb/gdbserver:

2016-02-12  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (get_next_pcs_ops): Initialize it with
	arm_linux_get_next_pcs_fixup.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <020ecd38e74681cb14987baf1a4d3c3ee3be0006@gdb-build>]
* [binutils-gdb] stack: check frame_unwind_caller_id
@ 2016-02-12  9:10 sergiodj+buildbot
  2016-02-12 12:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a038fa3e14a477d4d72a26c2e139fa47d2774be2 ***

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

stack: check frame_unwind_caller_id

Callers of frame_unwind_caller_* functions are supposed to check
frame_unwind_caller_id.

Add such a check to frame_info and treat an invalid caller ID as if the caller
PC were not available.

gdb/
	* stack.c (frame_info): Check frame_unwind_caller_id.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] frame: add skip_tailcall_frames
@ 2016-02-12  9:01 sergiodj+buildbot
  2016-02-12 10:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-12  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f3ef606b91298855e9ea13ae0e0316c23f06c9b ***

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

frame: add skip_tailcall_frames

Add a new function skip_tailcall_frames to skip TAILCALL_FRAME frames.

gdb/
	* frame.h (skip_tailcall_frames): New.
	* frame.c (skip_tailcall_frames): New.
	(frame_pop): Call skip_tailcall_frames.
	* infcmd.c (finish_command): Call skip_tailcall_frames.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add missing quotes to gdb/testsuite/README
@ 2016-02-11 20:15 sergiodj+buildbot
  2016-02-12  8:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT acc23c113ab9602707574e7df120f96170a9731c ***

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

Add missing quotes to gdb/testsuite/README

gdb/testsuite/ChangeLog:
2016-02-11  Pedro Alves  <palves@redhat.com>

	* README (Parallel testing): Add missing double quotes.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] arm-tdep.c: Change type of insn parameters
@ 2016-02-11 18:30 sergiodj+buildbot
  2016-02-12  3:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 615234c107e5dcdefff78596971266e9346b3f76 ***

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

arm-tdep.c: Change type of insn parameters

Almost obvious... change the type of some insn parameters, so that it
matches the rest of the code.

gdb/ChangeLog:

	* arm-tdep.c (thumb_copy_unmodified_16bit): Change type of insn.
	(thumb_copy_b): Likewise.
	(arm_decode_b_bl_ldmstm): Likewise.
	(thumb_copy_16bit_ldr_literal): Likewise.
	(thumb_copy_pop_pc_16bit): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use the target architecture when encoding tracepoint actions
@ 2016-02-11 13:31 sergiodj+buildbot
  2016-02-11 22:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-11 13:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82e9becd8afe1d7c9971096592bf312637d9437f ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 82e9becd8afe1d7c9971096592bf312637d9437f

Use the target architecture when encoding tracepoint actions

This patch uses the target architecture rather then the objfile
architecture when encoding tracepoint actions.

The target architecture may contain additional registers. E.g. ARM VFP
registers. This information is needed to allow their collection. Since we
can never know whether the registers numbers in the target match the
binary's we have to use tdesc here.

One note about combined debuggers / multi-inferior from Pedro Alves:

In the combined debugger case taking Cell as the practical example that
gdb supports currently:

In that case, the main target_gdbarch() will be powerpc, but you may have set a
tracepoint on _spu_ code, which has a different gdbarch.  so for that case,
target_gdbarch would be wrong.  I think that in that case, we'd need to
find __the_ target/tdesc gdbarch that is (bfd) compatible with the
objfile's gdbarch.

I think cell/spu gdbserver doesn't support tracepoints, so we can ignore
this for now.

The multi-inferior/process case is somewhat related, but its simpler.
each inferior has its own gdbarch.

That is, target_gdbarch depends on the current inferior selected.
In fact, that just returns inferior->gdbarch nowaways.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* tracepoint.c (encode_actions_1): Use target_gdbarch () rather
	than loc->gdbarch.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <e909d859f5635d66e79fef467da70d6090bfae1b@gdb-build>]
[parent not found: <473b99e5721ad623cc5826e03a73e2cf6cef4eb5@gdb-build>]
* [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned
@ 2016-02-10 17:06 sergiodj+buildbot
  2016-02-11 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f6a71b4bfdad8fa2fe33e86f799fa0d362973dc ***

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

Clear *VAL in regcache_raw_read_unsigned

We have function regcache_raw_read_unsigned defined in both GDB and
GDBserver, so that it is used in common like this,

  ULONGEST value;
  status = regcache_raw_read_unsigned (regcache, regnum, &value);

'value' is correctly set in GDB side, but may not be correctly set
in GDBserver, because &value is passed in regcache_raw_read_unsigned
but collect_register may only set part of the whole variable.  In my
test, I see the top half of 'value' is garbage.  This patch fixes this
problem by clearing *VAL before calling collect_register.

gdb/gdbserver:

2016-02-10  Yao Qi  <yao.qi@linaro.org>

	* regcache.c (regcache_raw_read_unsigned): Clear *VAL.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add support for ARC instruction relaxation in the assembler.
@ 2016-02-10 12:21 sergiodj+buildbot
  2016-02-11 10:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-10 12:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4670103e86f59a80259fd593a6949d693382e536 ***

Author: Claudiu Zissulescu <claziss@synopsys.com>
Branch: master
Commit: 4670103e86f59a80259fd593a6949d693382e536

Add support for ARC instruction relaxation in the assembler.

gas/
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>
	    Janek van Oirschot <jvanoirs@synopsys.com>

        * config/tc-arc.h (TC_FRAG_TYPE, TC_PCREL_ADJUST, MAX_INSN_ARGS)
        (MAX_INSN_FLGS, MAX_FLAG_NAME_LENGHT, TC_GENERIC_RELAX_TABLE):
        Define.
        (arc_flags, arc_relax_type): New structure.
        * config/tc-arc.c (FRAG_MAX_GROWTH, RELAX_TABLE_ENTRY)
	(RELAX_TABLE_ENTRY_MAX): New define.
        (relaxation_state, md_relax_table, arc_relaxable_insns)
	(arc_num_relaxable_ins): New variable.
	(rlx_operand_type, arc_rlx_types): New enums.
	(arc_relaxable_ins): New structure.
        (OPTION_RELAX): New option.
        (arc_insn): New relax member.
        (arc_flags): Remove.
        (relax_insn_p): New function.
        (apply_fixups): Likewise.
        (relaxable_operand): Likewise.
        (may_relax_expr): Likewise.
        (relaxable_flag): Likewise.
        (arc_pcrel_adjust): Likewise.
        (md_estimate_size_before_relax): Implement.
        (md_convert_frag): Likewise.
        (md_parse_option): Handle new mrelax option.
        (md_show_usage): Likewise.
        (assemble_insn): Set relax member.
        (emit_insn0): New function.
        (emit_insn1): Likewise.
        (emit_insn): Handle relaxation case.
	* NEWS: Mention the new relaxation option.
	* doc/c-arc.texi (ARC Options): Document new mrelax option.

gas/testsuite
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>

        * gas/arc/relax-avoid1.d: New file.
        * gas/arc/relax-avoid1.s: Likewise.
        * gas/arc/relax-avoid2.d: Likewise.
        * gas/arc/relax-avoid2.s: Likewise.
        * gas/arc/relax-avoid3.d: Likewise.
        * gas/arc/relax-avoid3.s: Likewise.
	* gas/arc/relax-b.d: Likewise.
        * gas/arc/relax-b.s: Likewise.

include/opcode/
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>
	    Janek van Oirschot  <jvanoirs@synopsys.com>

        * arc.h (arc_opcode arc_relax_opcodes, arc_num_relax_opcodes):
        Declare.

opcodes/
2016-01-26  Claudiu Zissulescu  <claziss@synopsys.com>
	    Janek van Oirschot  <jvanoirs@synopsys.com>

        * arc-opc.c (arc_relax_opcodes, arc_num_relax_opcodes): New
        variable.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Update NEWS post GDB 7.11 branch creation.
@ 2016-02-10  4:06 sergiodj+buildbot
  2016-02-10 16:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  4:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1233c0bae644451922bda07d03f1a66f3439dd20 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 1233c0bae644451922bda07d03f1a66f3439dd20

Update NEWS post GDB 7.11 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] 1903+ messages in thread
* [binutils-gdb] breakpoints/19546: Fix crash after updating breakpoints
@ 2016-02-10  0:25 sergiodj+buildbot
  2016-02-10 11:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-10  0:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 9ef9e6a6a0dd8f948708cb67c9afcfd0be40cb0a

breakpoints/19546: Fix crash after updating breakpoints

One of the last checks update_breakpoints_after_exec does while looping
over the list of breakpoints is check that the breakpoint has a valid
location spec. It uses event_location_empty_p to check if the location spec
is "empty", and if it is, the breakpoint is deleted.

momentary_breakpoint types rely on setting the breakpoint structure's
location spec to NULL, thereby causing an update to delete the breakpoint.
However, event_location_empty_p assumed that locations were never NULL.
As a result, GDB would crash dereferencing a NULL pointer whenever
update_breakpoints_after_exec would encounter a momentary_breakpoint.

This patch creates a new wrapper/helper function which tests that the given
breakpoint's location spec is non-NULL and if it is not "empty"
or "unspecified."

gdb/ChangeLog

	PR breakpoints/19546
	* breakpoint.c (breakpoint_event_location_empty_p): New function.
	(update_breakpoints_after_exec, bkpt_re_set): Use this new function
	instead of event_location_empty_p.

gdb/testsuite/ChangeLog

	PR breakpoints/19546
	* gdb.base/infcall-exec.c: New file.
	* gdb.base/infcall-exec2.c: New file.
	* gdb.base/infcall-exec.exp: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] python/19506 -- gdb.Breakpoint address location regression
@ 2016-02-09 22:56 sergiodj+buildbot
  2016-02-10  0:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 22:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f61929fd82fb632ee7c3be883d7086afc5c65d0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 9f61929fd82fb632ee7c3be883d7086afc5c65d0

python/19506 -- gdb.Breakpoint address location regression

Now that "legacy" linespecs benefit from consolidated support in
string_to_event_location_basic, python's Breakpoint command should use this
function to turn strings into event locations.

As a result, this patch fixes python/19506. Before:

(gdb) python gdb.Breakpoint("*main")
Traceback (most recent call last):
  File "<string>", line 1, in <module>
RuntimeError: Function "*main" not defined.
Error while executing Python code.

After:

(gdb) python gdb.Breakpoint("*main")
Breakpoint 1 at 0x4005fb: file ../../../src/gdb/testsuite/gdb.python/py-breakpoint.c, line 32.

gdb/ChangeLog

	PR python/19506
	* python/py-breakpoint.c (bppy_init): Use
	string_to_event_location_basic instead of new_linespec_location.

gdb/testsuite/ChangeLog

	PR python/19506
	* gdb.python/py-breakpoint.exp (test_bkpt_address): New procedure.
	(toplevel): Call test_bkpt_address.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Modernize configure.ac's
@ 2016-02-09 14:16 sergiodj+buildbot
  2016-02-09 20:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e94266c4db633f7defaf4bb68c74fd09a9cf9e2 ***

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

Modernize configure.ac's

Using AC_OUTPUT with arguments has been deprecated for some time in
autoconf, even in version 2.64, which we are using.  This change should
not affect functionality.

I also removed the "exit 0"'s, they shouldn't be necessary.

gdb/ChangeLog:

	* configure.ac: Use AC_CONFIG_FILES instead of passing arguments
	to AC_OUTPUT.  Remove "exit 0" at the end.
	* configure: Regenerate.

gdb/testsuite/ChangeLog:

	* configure.ac: Use AC_CONFIG_FILES instead of passing arguments
	to AC_OUTPUT.
	* configure: Regenerate.

gdb/gdbserver/ChangeLog:

	* configure.ac: Use AC_CONFIG_FILES instead of passing arguments
	to AC_OUTPUT.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't
@ 2016-02-09 12:41 sergiodj+buildbot
  2016-02-09 18:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 12:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a7f3dffced7a20c992e1488d9f05fed8b8001fd ***

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

Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't

PR19548 shows that we still have problems related to 13fd3ff34329:

 [PR17431: following execs with "breakpoint always-inserted on"]
 https://sourceware.org/ml/gdb-patches/2014-09/msg00733.html

The problem this time is that we currently update the global location
list and try to insert breakpoint locations after re-setting _each_
breakpoint in turn.

Say:

 - We have _more_ than one breakpoint set.  Let's assume 2.

 - There's a breakpoint with a pre-exec address that ends up being an
   unmapped address after the exec.

 - That breakpoint is NOT the first in the breakpoint list.

Then when handling an exec, and we re-set the first breakpoint in the
breakpoint list, we mistakently try to install the old pre-exec /
un-re-set locations of the other breakpoint, which fails:

 (gdb) continue
 Continuing.
 process 28295 is executing new program: (...)/execl-update-breakpoints2
 Error in re-setting breakpoint 1: Warning:
 Cannot insert breakpoint 2.
 Cannot access memory at address 0x1000764

 Breakpoint 1, main (argc=1, argv=0x7fffffffd368) at /home/pedro/gdb/mygit/src/gdb/testsuite/gdb.base/execl-update-breakpoints.c:34
 34        len = strlen (argv[0]);
 (gdb)

Fix this by deferring the global location list update till after all
breakpoints are re-set.

Tested on x86_64 Fedora 20, native and gdbserver.

gdb/ChangeLog:
2016-02-09  Pedro Alves  <palves@redhat.com>

	PR breakpoints/19548
	* breakpoint.c (create_overlay_event_breakpoint): Don't update
	global location list here.
	(create_longjmp_master_breakpoint)
	(create_std_terminate_master_breakpoint)
	(create_exception_master_breakpoint, create_jit_event_breakpoint)
	(update_breakpoint_locations):
	(breakpoint_re_set): Update global location list after all
	breakpoints are re-set.

gdb/testsuite/ChangeLog:
2016-02-09  Pedro Alves  <palves@redhat.com>

	PR breakpoints/19548
	* gdb.base/execl-update-breakpoints.c (some_function): New
	function.
	(main): Call it.
	* gdb.base/execl-update-breakpoints.exp: Add a second breakpoint.
	Tighten expected GDB output.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 11:06 sergiodj+buildbot
  2016-02-09 15:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e9c750c20fe8031a2b6d6272cd57bbf445df5 ***

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

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Revert "Fix build breakage"
@ 2016-02-09 10:57 sergiodj+buildbot
  2016-02-09 14:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c23bbc1cdae6149de4175a75aa9bf9bcbc936fa4 ***

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

Revert "Fix build breakage"

This reverts commit 222cab58b7ed37df6e01dacb0932f400a2588137.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow.
@ 2016-02-09 10:10 sergiodj+buildbot
  2016-02-09 10:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-09 10:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ea53e003163338a403d5afbb2046cafb8f3abe9 ***

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

Add a more helpful warning message to explain why some AArch64 relocations can overflow.

bfd	* elfnn-aarch64.c (elfNN_aarch64_relocate_section): Add a more
	helpful warning message to explain why certain AArch64 relocs
	might overflow.

ld	* testsuite/ld-aarch64/reloc-overflow-bad.d: New test.
	* testsuite/ld-aarch64/reloc-overflow-1.s: New source file.
	* testsuite/ld-aarch64/reloc-overflow-2.s: New source file.
	* testsuite/ld-aarch64/aarch64-elf.exp: Run the new test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix in-tree, parallel running of Ada tests
@ 2016-02-08 19:12 sergiodj+buildbot
  2016-02-08 20:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-08 19:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 437277d47a15711f29e02e5265ce8bbb8c8ef4f5 ***

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

Fix in-tree, parallel running of Ada tests

While testing the following patch,

  [PATCH] Always organize test artifacts in a directory hierarchy
  https://sourceware.org/ml/gdb-patches/2016-01/msg00133.html

I noticed that it broke Ada testing.  This lead me to think that
parallel testing when building in-tree didn't work previously in Ada.
It is confirmed by this test:

$ make check TESTS="gdb.ada/fun_addr.exp" -j 2
...
Running ./gdb.ada/fun_addr.exp ...
FAIL: gdb.ada/fun_addr.exp: compilation foo.adb
...

This patch fixes in-tree parallel testing for Ada, and consequently
serial and parallel testing when the aforementioned patch is applied.

The problem originates from the fact that Ada support code cd's to the
builddir before compiling.  In itself it's not a problem, it allows to
place intermediate auto-generated files in that directory.  The Ada
compilation refers to the source file, which is in another directory,
only by its base name (e.g. foo.adb).  In serial mode, that worked
because builddir was the same as the source directory (e.g.
gdb.ada/fun_addr/).  In an out-of-tree build, it works because the
source directory is added as an include directory (note: this is not the
same $srcdir as autoconf's):

  set srcdir [file dirname $source]
  additional_flags=-I$srcdir

which becomes:

  additional_flags=-I/home/emaisin/build/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr

However, when building in-tree, srcdir is relative: ./gdb.ada/fun_addr.
When using parallel or always-in-outputs-directory mode, we are cd'ed in
the outputs directory.  So -I$srcdir is relative to the current
directory, which is wrong.

To fix it, I made the TCL variable srcdir (set in site.exp, from which
everything else is derived) always absolute.  It is done by assigning
autoconf's abs_srcdir instead of autoconf's srcdir.  This way -I$srcdir
will always be good, regardless of where we cd'ed to.  A small apparent
change is that when running tests, DejaGnu will say:

  Running /tmp/binutils-gdb/gdb/testsuite/gdb.ada/fun_addr.exp ...

instead of

  Running ./gdb.ada/fun_addr.exp ...

I hope it's not too much of an annoyance.  I think that it should make
the testsuite a tiny bit more robust against other bugs of the same
class.

Regtested in & out of tree, only with native target.

gdb/testsuite/ChangeLog:

	* Makefile.in (abs_srcdir): Assign @abs_srcdir@.
	(site.exp): Assign abs_srcdir to tcl's srcdir.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: mips: fix prog_bfd usage
@ 2016-02-06  1:39 sergiodj+buildbot
  2016-02-07 10:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-06  1:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1554f758410c4307103120424d35050e88433d85 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 1554f758410c4307103120424d35050e88433d85

sim: mips: fix prog_bfd usage

We do not want to reference the "base" member directly.  We have the
STATE_PROG_BFD macro instead to look up the prog_bfd member.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [testsuite] Remove BASEDIR
@ 2016-02-04 15:57 sergiodj+buildbot
  2016-02-04 16:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31d913c7e4e84edf88b4324c3a9a8fb31c8206ec ***

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

[testsuite] Remove BASEDIR

BASEDIR was added by https://sourceware.org/ml/gdb-patches/2013-10/msg00587.html
in order to handle the different directory layout in serial testing
and parallel testing.  BASEDIR is "gdb.base" in serial testing and is
"outputs/gdb.base/TESTNAME" in parallel testing.  However, it doesn't
work if the GDBserver is in remote target, like this,

$ make check RUNTESTFLAGS='--target_board=remote-gdbserver-on-localhost foll-vfork.exp foll-exec.exp'
FAIL: gdb.base/foll-exec.exp: continue to first exec catchpoint (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork and exec child follow, to main bp: continue to bp (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: finish (the program exited)
FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: continue to bp (the program exited)

these tests fail because the executable can't be found.  With target
board native-gdbserver, the program is spawned this way,

 spawn ../gdbserver/gdbserver --once :2347 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.base/foll-vfork

so BASEDIR is correct.  However, with target board
remote-gdbserver-on-localhost, the program is spawned

  spawn /usr/bin/ssh -l yao localhost /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/../gdbserver/gdbserver --once :2346 /scratch/yao/gdb/build-git/x86_64/gdb/testsuite/gdb.base/foll-vfork

so BASEDIR (either "gdb.base" or "outputs/gdb.base/TESTNAME") makes no
sense.

I had a fix that pass absolute directory to BASEDIR, but it assumes
that directory structure is the same on build and target, and it
doesn't work in remote host case.  The current fix in this patch is
to get the directory from argv[0].  In any case, the program to be
exec'ed is at the same directory with the main program.

Note that these tests do "next N" to let program stop at the desired
line, but it is fragile, because GDB for different targets may skip
function prologue slightly differently, so I replace some of them by
"tbreak on LINE NUMBER and continue".

gdb/testsuite:

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

	* gdb.base/foll-exec-mode.c: Include limits.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.base/foll-exec-mode.exp: Don't pass -DBASEDIR in
	compilation.
	* gdb.base/foll-exec.c: Include limits.h.
	(main): Add parameters argc and argv.
	Get directory from argv[0].
	* gdb.base/foll-exec.exp: Don't pass -DBASEDIR in compilation.
	Adjust tests on the number of lines as source code changed.
	* gdb.base/foll-vfork-exit.c: Include limits.h.
	(main): Add one line of statement before vfork.
	* gdb.base/foll-vfork.c: Include limits.h and string.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.base/foll-vfork.exp: Don't pass -DBASEDIR in compilation.
	(setup_gdb): Set tbreak to skip some source lines.
	* gdb.multi/bkpt-multi-exec.c: Include limits.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.multi/bkpt-multi-exec.exp: Don't pass -DBASEDIR in
	compilation.
	* gdb.multi/multi-arch-exec.c: Include limits.h and string.h.
	(main): Add parameters argc and argv.  Get directory from
	argv[0].
	* gdb.multi/multi-arch-exec.exp: Don't pass -DBASEDIR in
	compilation.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix the encoding of the MSP430's RRUX instruction.
@ 2016-02-04 10:06 sergiodj+buildbot
  2016-02-04 10:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-04 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1d9289fef41b82aa22f63f74aa8e730ec898d3c ***

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

Fix the encoding of the MSP430's RRUX instruction.

	PR target/19561
opcdoe	* msp430-dis.c (print_insn_msp430): Add a special case for
	decoding an RRC instruction with the ZC bit set in the extension
	word.

include	* opcode/msp430.h (IGNORE_CARRY_BIT): New define.
	(RRUX): Synthesise using case 2 rather than 7.

gas	* config/tc-msp430.c (msp430_operands): Remove case 7.  Use case 2
	to handle encoding of RRUX instruction.
	* testsuite/gas/msp430/msp430x.s: Add more tests of the extended
	shift instructions.
	* testsuite/gas/msp430/msp430x.d: Update expected disassembly.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PowerPC64 ELFv2 entry code
@ 2016-02-02 13:44 sergiodj+buildbot
  2016-02-02 20:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85fabe715c441e1c90fe913e2a6d65f0e487e5e8 ***

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

PowerPC64 ELFv2 entry code

This tightens the condition under which ld optimizes PIC entry code
to non-PIC.

bfd/
	* elf64-ppc.c (ppc64_elf_relocate_section): Further restrict
	ELFv2 entry optimization.
gold/
	* powerpc.cc (relocate): Further restrict ELFv2 entry optimization.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Clear HAS_RELOC if there are no relocations
@ 2016-02-02 12:31 sergiodj+buildbot
  2016-02-02 19:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14f2c699ddca1e2f706342dffc59a6c7e23e844c ***

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

Clear HAS_RELOC if there are no relocations

The HAS_RELOC bit should be cleared when relocations are removed from
relocatable files.

bfd/

	PR binutils/19547
	* elf.c (assign_section_numbers): Clear HAS_RELOC if there are
	no relocations in relocatable files.

binutils/

	PR binutils/19547
	* testsuite/binutils-all/objcopy.exp
	(objcopy_test_without_global_symbol): New proc.
	Run objcopy_test_without_global_symbol.
	* testsuite/binutils-all/pr19547.c: New file.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] epiphany/disassembler: Improve alignment of output.
@ 2016-02-02 11:38 sergiodj+buildbot
  2016-02-02 16:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b89807c67baf4f31125d151f2dc3532b3420964d ***

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

epiphany/disassembler: Improve alignment of output.

Always set the bytes_per_line field (of struct disassemble_info) to the
same constant value, this is inline with the advice contained within
include/dis-asm.h.

Setting this field to a constant value will cause the disassembler
output to be better aligned.

cpu/ChangeLog:

	* epiphany.opc (epiphany_print_insn): Set info->bytes_per_line to
	a constant to better align disassembler output.

opcodes/ChangeLog:

	* epiphany-dis.c: Regenerated from latest cpu files.

gas/ChangeLog:

	* testsuite/gas/epiphany/sample.d: Update expected output.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add bound related fields to the siginfo structure
@ 2016-02-02 11:21 sergiodj+buildbot
  2016-02-02 14:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-02 11:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96b5c49fb18ba7ad070b0c3ad36388d56c5897fb ***

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

Add bound related fields to the siginfo structure

Both Linux and glibc have introduced bound related fields in the
segmentation fault fields of the siginfo_t type. Add the new fields
to our x86's siginfo_t type too.

Kernel patch:
http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=ee1b58d36aa1b5a79eaba11f5c3633c88231da83

Glibc patch:
http://repo.or.cz/w/glibc.git/commit/d4358b51c26a634eb885955aea06cad26af6f696

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

gdb/ChangeLog:

	* linux-tdep.c (linux_get_siginfo_type): Add the _addr_bnd
	structure to the siginfo if extra_fields contains
	LINUX_SIGINFO_FIELD_ADDR_BND.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't add DT_NEEDED for unmatched symbol
@ 2016-02-01 23:59 sergiodj+buildbot
  2016-02-02  7:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 23:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aef28989904e92e391fee905e51abc6bb2fd4de0 ***

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

Don't add DT_NEEDED for unmatched symbol

Don't add DT_NEEDED if a symbol from a library loaded via DT_NEEDED
doesn't match the symbol referenced by regular object.

bfd/

	PR ld/19553
	* elflink.c (elf_link_add_object_symbols): Don't add DT_NEEDED
	if a symbol from a library loaded via DT_NEEDED doesn't match
	the symbol referenced by regular object.

ld/testsuite/

	PR ld/19553
	* testsuite/ld-elf/indirect.exp: Run tests for PR ld/19553.
	* testsuite/ld-elf/pr19553.map: New file.
	* testsuite/ld-elf/pr19553.map: Likewise.
	* testsuite/ld-elf/pr19553a.c: Likewise.
	* testsuite/ld-elf/pr19553b.c: Likewise.
	* testsuite/ld-elf/pr19553b.out: Likewise.
	* testsuite/ld-elf/pr19553c.c: Likewise.
	* testsuite/ld-elf/pr19553c.out: Likewise.
	* testsuite/ld-elf/pr19553d.c: Likewise.
	* testsuite/ld-elf/pr19553d.out: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Guard against undefined behaviour in mi-vla-fortran.exp
@ 2016-02-01 18:40 sergiodj+buildbot
  2016-02-01 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37a8db1a336ce78a46bf7f303e47e17b2a1bf694 ***

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

gdb: Guard against undefined behaviour in mi-vla-fortran.exp

The test gdb.mi/mi-vla-fortran.exp reveals an issue with the DWARF
generated by gfortran.

In the test a pointer variable 'pvla2' is created:
    real, pointer :: pvla2 (:, :)

Initially this variable will be unassociated, so something like this:
    l = associated(pvla2)

should return false.

In the test gdb stops at a point _before_ pvla2 is associated with
anything, and we then try to print pvla2, the expectation is that gdb
should reply <not associated>.

The problem is that the data the DWARF directs gdb to read (to identify
if the variable is associated or not) is not initialised until the first
time pvla2 is accessed.

As a result gdb ends up reading uninitialised memory, sometimes this
uninitialised memory indicates the variable is associated (when it's
not).  This first mistake can lead to a cascade of errors, reading
uninitialised memory, with the result that gdb builds an invalid type to
associate with the variable pvla2.

In some cases, this invalid type can be very large, which when we try to
print pvla2 causes gdb to allocate a large amount of memory.

A recent commit added a new gdb variable 'max-value-size', which
prevents gdb from allocating values of extreme size.  As a result
directly trying to print pvla2 will now now error rather than allocate a
large amount of memory.

However, some of the later tests create a varobj for pvla2, and then
ask for the children of that varobj to be displayed.  In the case where
an invalid type has been computed for pvla2 then the number of children
can be wrong, and very big, in which case trying to display all of these
children can cause gdb to consume an excessive amount of memory.

This commit first detects if printing pvla2 triggers the max-value-size
error, if it does then we avoid all the follow on tests relating to the
unassociated pvla2, which avoids the second error printing the varobj
children.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-vla-fortran.exp: Add XFAIL for accessing unassociated
	pointer.  Don't perform further tests on the unassociated pointer
	if the first test fails.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: New set/show max-value-size command.
@ 2016-02-01 18:23 sergiodj+buildbot
  2016-02-01 18:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fdf6324fafd60f967e2e8323fdacf84b1bfcea3 ***

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

gdb: New set/show max-value-size command.

For languages with dynamic types, an incorrect program, or uninitialised
variables within a program, could result in an incorrect, overly large
type being associated with a value.  Currently, attempting to print such
a variable will result in gdb trying to allocate an overly large buffer.

If this large memory allocation fails then the result can be gdb either
terminating, or (due to memory contention) becoming unresponsive for the
user.

A new user visible variable in gdb helps guard against such problems,
two new commands are available:

   set max-value-size
   show max-value-size

The 'max-value-size' is the maximum size of memory in bytes that gdb
will allocate for the contents of a value.  Any attempt to allocate a
value with a size greater than this will result in an error.  The
initial default for this limit is set at 64k, this is based on a similar
limit that exists within the ada specific code.

It is possible for the user to set max-value-size to unlimited, in which
case the old behaviour is restored.

gdb/ChangeLog:

	* value.c (max_value_size): New variable.
	(MIN_VALUE_FOR_MAX_VALUE_SIZE): New define.
	(show_max_value_size): New function.
	(check_type_length_before_alloc): New function.
	(allocate_value_contents): Call check_type_length_before_alloc.
	(set_value_enclosing_type): Likewise.
	(_initialize_values): Add set/show handler for max-value-size.
	* NEWS: Mention new set/show command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Value Sizes): New section.
	(Data): Add the 'Value Sizes' node to the menu.

gdb/testsuite/ChangeLog:

	* gdb.base/max-value-size.c: New file.
	* gdb.base/max-value-size.exp: New file.
	* gdb.base/huge.exp: Disable max-value-size for this test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add support for importing data from ILF images.
@ 2016-02-01 13:53 sergiodj+buildbot
  2016-02-01 14:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 655ed9ea1703173cb796070ed9843ea90bb74e58 ***

Author: Nathaniel Smith <njs@pobox.com>
Branch: master
Commit: 655ed9ea1703173cb796070ed9843ea90bb74e58

Add support for importing data from ILF images.

	* peicode.h (pe_ILF_build_a_bfd): Create an import symbol for both
	CODE and DATA.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] x86 synthetic plt symbols
@ 2016-02-01 11:43 sergiodj+buildbot
  2016-02-01 13:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-01 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec1f73bb0be7482f2dffd9bbca2f93fc74eca172 ***

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

x86 synthetic plt symbols

Changing "pushq $1" in the following to "pushq $too_big" results in an
abort.  BFD shouldn't abort on (deliberately) bad user input.

 400480:       ff 25 9a 0b 20 00       jmpq   *0x200b9a(%rip)
 400486:       68 01 00 00 00          pushq  $0x1
 40048b:       e9 d0 ff ff ff          jmpq   400460 <_init+0x20>

	* elf64-x86-64.c (elf_x86_64_get_plt_sym_val): Don't abort on
	an out of range reloc_index.
	* elf32-i386.c (elf_i386_get_plt_sym_val): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix some comments in varobj.{c,h}
@ 2016-02-01  3:36 sergiodj+buildbot
  2016-02-01  4:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-02-01  3:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fa1307022c1278575846faba5f3391b70d64b16 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 5fa1307022c1278575846faba5f3391b70d64b16

Fix some comments in varobj.{c,h}

A few typos.  The comment about varobj_create has been misplaced since
the dawn of time.

gdb/ChangeLog:

	* varobj.h (struct varobj): Fix typos in comments.
	(struct lang_varobj_ops): Likewise.
	* varobj.c (VAROBJ_TABLE_SIZE): Likewise.
	(varobj_create): Move misplaced comment.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa.
@ 2016-01-31 20:38 sergiodj+buildbot
  2016-01-31 20:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-31 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d4b2867f8441c7bf75dfef6b3c95a10241f9709 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: 6d4b2867f8441c7bf75dfef6b3c95a10241f9709

Fix /usr/bin/ld: final link failed: File truncated error on hppa.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Set BFD_DECOMPRESS to decompress debug sections
@ 2016-01-28 21:41 sergiodj+buildbot
  2016-01-29  0:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf150a0bad8d3fcfa17f5d6b5a5ca75efae855ed ***

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

Set BFD_DECOMPRESS to decompress debug sections

We should set BFD_DECOMPRESS to decompress debug sections when reading in
DWARF debug sections.

bfd/

	PR binutils/19523
	* dwarf2.c (_bfd_dwarf2_slurp_debug_info): Set BFD_DECOMPRESS to
	decompress debug sections.

binutils/

	PR binutils/19523
	* Makefile.am (check-DEJAGNU): Pass CC and CC_FOR_BUILD to
	runtest.
	* Makefile.in: Regenerated.
	* testsuite/binutils-all/compress.exp (test_gnu_debuglink): New
	proc.
	Run test_gnu_debuglink for native ELF build.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Sync libiberty with GCC.
@ 2016-01-28 21:00 sergiodj+buildbot
  2016-01-28 21:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d98de835cb018419e0ef97db37fcf9061247750 ***

Author: Iain Buclaw <ibuclaw@gdcproject.org>
Branch: master
Commit: 9d98de835cb018419e0ef97db37fcf9061247750

Sync libiberty with GCC.

libiberty/ChangeLog:
	* d-demangle.c (dlang_call_convention): Handle extern Objective-C
	function calling convention.
	(dlang_call_convention_p): Likewise.
	(dlang_type): Likewise.
	* testsuite/d-demangle-expected: Add coverage tests.

	* d-demangle.c (dlang_function_args): Append ',' for variadic functions
	only if parameters were seen before the elipsis symbol.
	* testsuite/d-demangle-expected: Add coverage test for parameter-less
	variadic functions.

	* d-demangle.c (dlang_type): Handle function types only in the context
	of seeing a pointer type symbol.
	* testsuite/d-demangle-expected: Update function pointer tests.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp
@ 2016-01-28 14:39 sergiodj+buildbot
  2016-01-28 15:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-28 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fe8399de97e50f631ce28ceb42515862a927556 ***

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

[testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp

In vla.f90, this single line of source is compiled to many instructions,

  vla2(:, :, :) = 1311                ! vla2-allocated

it is quite slow (about several minutes in my testing) to step over this
source line without range stepping.  This patch is to increase the timeout
value by 15 times, which is a magic number to make sure timeout disappears
in my testing with a slow arm-linux board.

gdb/testsuite:

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

	* gdb.fortran/vla-value.exp: Wrap test with with_timeout_factor.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add Keith Seitz as Linespec Maintainer
@ 2016-01-27 11:38 sergiodj+buildbot
  2016-01-27 11:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-27 11:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c07af0ab296efebf868a153e6c98cb65c5c23d04 ***

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

Add Keith Seitz as Linespec Maintainer

gdb/ChangeLog:

        * MAINTAINERS (Responsible Maintainers): Add Keith Seitz as
        Linespec Maintainers.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <a579cd9aa8c57c8a54833f26452a1afef38e5d20@gdb-build>]
* [binutils-gdb] ARC/BFD: Fix a build error from `index' shadowing a global declaration
@ 2016-01-25 16:18 sergiodj+buildbot
  2016-01-25 18:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 16:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 840855c5edfb840a97fb063fd8f44a7e9e537b87 ***

Author: Maciej W. Rozycki <macro@imgtec.com>
Branch: master
Commit: 840855c5edfb840a97fb063fd8f44a7e9e537b87

ARC/BFD: Fix a build error from `index' shadowing a global declaration

	bfd/
	* elf32-arc.c (elf_arc_finish_dynamic_symbol): Rename `index' to
	`dynindx'.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp
@ 2016-01-25 13:32 sergiodj+buildbot
  2016-01-25 13:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-25 13:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1da4b11eef6dba04a1cfa579c6ba313718105b8 ***

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

Move foreach_with_prefix to lib/gdb.exp

gdb/testsuite/ChangeLog:
2016-01-25  Pedro Alves  <palves@redhat.com>

	* gdb.base/step-sw-breakpoint-adjust-pc.exp (foreach_with_prefix):
	Delete, moved to lib/gdb.exp.
	* gdb.threads/forking-threads-plus-breakpoint.exp
	(foreach_with_prefix): Likewise.
	* gdb.threads/process-dies-while-handling-bp.exp
	(foreach_with_prefix): Likewise.
	* lib/gdb.exp (foreach_with_prefix): New procedure.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!)
@ 2016-01-25  9:54 sergiodj+buildbot
  2016-01-25 10:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c244074cb684302be1378a072b33cdb8dd0dff1f ***

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

Add missing end-of-comment marker to previous delta.  (Doh!)


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up.
@ 2016-01-25  9:41 sergiodj+buildbot
  2016-01-25  9:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-25  9:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf466c2ac5ac55bb9b30b96fbdcad564e8c1ccc8 ***

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

Fix memory corruption on Mach-O systems by suppressing a memory tidy up.

	PR target/19435
	* mach-o.c (bfd_mach_o_close_and_cleanup): Suppress code to free
	dsym filename buffer.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number
@ 2016-01-22 21:00 sergiodj+buildbot
  2016-01-22 22:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-22 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 092127d743462e370fd1156cb746f814a7b46593 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 092127d743462e370fd1156cb746f814a7b46593

testsuite: gdb.gdb/selftest.exp: Drop expected Thread number

Pedro Alves:
Looks like you forgot to amend before pushing though -- the version
checked in still had "Thread 1".

gdb/testsuite/ChangeLog
2016-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	Fix testsuite compatibility with Guile.
	* gdb.gdb/selftest.exp (send ^C to child process): Drop expected Thread
	number.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <99e8eb11cfcdde8cba6755ed4613c3cb079dfaa4@gdb-build>]
* [binutils-gdb] * breakpoint.c (init_breakpoint_sal): Add comment.
@ 2016-01-22  1:15 sergiodj+buildbot
  2016-01-22  9:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-22  1:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b35a8b2f1f44c6ea48aeb6f7a74de01f6f5016fb ***

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

* breakpoint.c (init_breakpoint_sal): Add comment.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <f906b857015513af81f94db8e11b1e334c767def@gdb-build>]
* [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host.
@ 2016-01-21 14:04 sergiodj+buildbot
  2016-01-21 22:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23a42089156e63bbd2228675e78cdf1ffae63c51 ***

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

Fix compile time errors building ARC target on a 32-bit host.

	* elf32-arc.c (ADD_RELA): Fix compile time warning errors by
	changing the type of _loc to be bfd_byte *.
	(elf_arc_finish_dynamic_symbol): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler
@ 2016-01-21 11:45 sergiodj+buildbot
  2016-01-21 19:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a994041db36c9a6058fe591c7ccd018ed7affc76 ***

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

gdb: Respect CXXFLAGS when building with C++ compiler

Currently, even when built with --enable-build-with-cxx, gdb uses
CFLAGS instead of CXXFLAGS.  This commit fixes it.

CXXFLAGS set in the environment when configure was run is now honored
in the generated gdb/Makefile, and you can also override CXXFLAGS in
the command like at make time, with the usual 'make CXXFLAGS="..."'

Objects built with a C compiler (e.g., gnulib) still honor CFLAGS
instead.

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

	* Makefile.in (COMPILER_CFLAGS): New.
	(CXXFLAGS): Get it from configure.
	(INTERNAL_CFLAGS_BASE, INTERNAL_LDFLAGS): Use COMPILER_CFLAGS
	instead of CFLAGS.
	* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Set and AC_SUBST
	COMPILER_CFLAGS.
	* configure: Regenerate.

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

	* Makefile.in (COMPILER_CFLAGS, CXXFLAGS): New.
	(INTERNAL_CFLAGS_BASE): Use COMPILER_CFLAGS instead of CFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix unexpected failures in the linker testsuite for ARM VxWorks targets.
@ 2016-01-21 11:03 sergiodj+buildbot
  2016-01-21 18:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aebf9be7089c1903581740851ae9ae67ffee2f4b ***

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

Fix unexpected failures in the linker testsuite for ARM VxWorks targets.

	PR ld/19455
	* elf32-arm.c (elf32_arm_create_dynamic_sections): Set the ELF
	class of the linker stub bfd.
	(elf32_arm_check_relocs): Skip check for pic format after
	processing a vxWorks R_ARM_ABS12 reloc.
	* elflink.c (bfd_elf_final_link): Check for ELFCLASSNONE when
	reporting a class mismatch.

	* testsuite/ld-arm/vxworks1-lib.dd: Update for current
	disassmebler output.
	* testsuite/ld-arm/vxworks1-lib.rd: Likewise.
	* testsuite/ld-arm/vxworks1.dd: Likewise.
	* testsuite/ld-arm/vxworks1.rd: Likewise.
	* testsuite/ld-arm/vxworks1.ld: Set the output format.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Rename elf-linux-psinfo.h to elf-linux-core.h
@ 2016-01-21 10:09 sergiodj+buildbot
  2016-01-21 14:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-21 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de64ce13a78669f094d6909fce51d210e2f9d2c0 ***

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

Rename elf-linux-psinfo.h to elf-linux-core.h

Since it will sometime have more than just prpsinfo.  Also,
elf32-ppc.c needlessly includes this header.

	* elf-linux-core.h: Rename from elf-linux-psinfo.h.
	* elf.c: Adjust #include.
	* elf32-ppc.c: Don't #include elf-linux-psinfo.h
	* Makefile.am (SOURCE_HFILES): Update.
	* Makefile.in: Regenerate.
	* po/SRC-PORFILES.in: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Convert macros in elf-linux-core.h to inline functions
@ 2016-01-21  9:57 sergiodj+buildbot
  2016-01-21 15:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aeb7056972f1b383578204b9151b0ae6d8c1df81 ***

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

Convert macros in elf-linux-core.h to inline functions

Besides changing some macros into inline functions, this removes
redundant memsets and uses bfd_put_* rather than H_PUT_*.

	* elf-linux-core.h (swap_linux_prpsinfo32_out): New function.
	(swap_linux_prpsinfo64_out): New function.
	(LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(LINUX_PRPSINFO64_SWAP_FIELDS): Delete.
	* elf.c (elfcore_write_linux_prpsinfo32): Adjust.  Don't memset.
	(elfcore_write_linux_prpsinfo64): Likewise.
	* elf32-ppc.c (swap_ppc_linux_prpsinfo32_out): New function.
	(PPC_LINUX_PRPSINFO32_SWAP_FIELDS): Delete.
	(elfcore_write_ppc_linux_prpsinfo32): Adjust.  Don't memset.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to
@ 2016-01-21  8:17 sergiodj+buildbot
  2016-01-21 11:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-21  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7a6a40dbc279f0a54bdf947077cbad8ad52564c ***

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

Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to

This patch fixes the following regression introduced by commit d0e59a68

step^M
39      } /* handler */^M
1: x/i $pc^M
=> 0x8740 <handler+80>: sub     sp, r11, #0^M
(gdb) step^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
setitimer () at ../sysdeps/unix/syscall-template.S:81^M
81      ../sysdeps/unix/syscall-template.S: No such file or directory.^M
1: x/i $pc^M
=> 0xb6eff9c0 <setitimer>:      push    {r7}^M
(gdb) FAIL: gdb.base/sigstep.exp: continue to handler, si+advance in handler, step from handler: leave handler

in my test setting, program is compiled in arm mode, but the glibc
is built in thumb mode, so when we do 'step' to step over syscall
instruction svc for SIGRETURN, GDB should set breakpoint for arm mode
in the program, even though the current program in glibc is in thumb
mode.  Current GDB doesn't consider the case that the mode of program
SIGRETURN goes to can be different from current program mode.

In fact, GDB has taken care of this arm/thumb mode changes already,
see

/* Copy the value of next pc of sigreturn and rt_sigrturn into PC,
   return 1.  In addition, set IS_THUMB depending on whether we
   will return to ARM or Thumb code.  Return 0 if it is not a
   rt_sigreturn/sigreturn syscall.  */
static int
arm_linux_sigreturn_return_addr (struct frame_info *frame,
				 unsigned long svc_number,
				 CORE_ADDR *pc, int *is_thumb)

but in the commit d0e59a68

> -  arm_linux_sigreturn_return_addr (frame, svc_number, &return_addr, &is_thumb);
> +  if (svc_number == ARM_SIGRETURN || svc_number == ARM_RT_SIGRETURN)
> +    next_pc = arm_linux_sigreturn_next_pc (regcache, svc_number);

the IS_THUMB setting is lost, so it is a regression.

gdb:

2016-01-21  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_sigreturn_next_pc): Add parameter
	is_thumb and set it according to CPSR saved on the stack.
	(arm_linux_get_next_pcs_syscall_next_pc): Pass is_thumb to
	arm_linux_sigreturn_next_pc.

gdb/gdbserver:

2016-01-21  Yao Qi  <yao.qi@linaro.org>

	* linux-arm-low.c (arm_sigreturn_next_pc): Add parameter
	is_thumb and set it according to CPSR saved on the stack.
	(get_next_pcs_syscall_next_pc): Pass is_thumb to
	arm_sigreturn_next_pc.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549
@ 2016-01-20 18:53 sergiodj+buildbot
  2016-01-21  9:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 18:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd356fa28834fa3a9f22f9157a568264ad045010 ***

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

gnu_vector.exp: Respect `should_kfail' for PR 8549

The gnu_vector test case yields a new FAIL on s390x:

  FAIL: gdb.base/gnu_vector.exp: verify vector return value

It was introduced by commit 77ae9c1933b50 "gdb.base/gnu_vector.exp:
Don't test output from the inferior".  That commit dropped the special
handling for GDB's inability (on some targets) to set the return value.

This change re-establishes the logic from before, converting the above
FAIL to a KFAIL (PRMS gdb/8549).

gdb/testsuite/ChangeLog:

	* gdb.base/gnu_vector.exp: Re-establish handling for should_kfail
	when GDB can not set the vector return value.  Add more comments
	for clarification.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO
@ 2016-01-20 14:43 sergiodj+buildbot
  2016-01-21  4:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 14:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0bff6e2d6942690d81ce1f33728de07835b0f5b7 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 0bff6e2d6942690d81ce1f33728de07835b0f5b7

[AArch64] Reject invalid immediate operands to MSR UAO

In the instruction to write to the ARMv8.2 PSTATE field UAO,
MSR UAO, #<imm>, the immediate should be either 0 or 1 but GAS accepts
any unsigned 4-bit integer.

This patch implements the constraint on the immediate, generating an
error if the immediate operand is invalid, and adds tests for the
illegal forms.

opcodes/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Check validity
	of MSR UAO immediate operand.

gas/
2016-01-20  Matthew Wahab  <matthew.wahab@arm.com>

	* testsuite/gas/aarch64/armv8_2-a-illegal.d: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.l: New.
	* testsuite/gas/aarch64/armv8_2-a-illegal.s: New.

Change-Id: Ibdec4967c00b1ef3be9dbc43d23b2c70d1a0b28c


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.
@ 2016-01-20 13:05 sergiodj+buildbot
  2016-01-20 22:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-20 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91f68a68f992e3f6c3da26c616b5257230bd1eec ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 91f68a68f992e3f6c3da26c616b5257230bd1eec

Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD.

bfd/ChangeLog:
      * elf32-arm.c ((elf32_arm_special_sections): Remove catch of noread
      section using '.text.noread' pattern.

gas/ChangeLog:
      * config/obj-elf.c (obj_elf_change_section) : Allow arm section with
      SHF_ARM_NOREAD section flag.
      * config/tc-arm.h (md_elf_section_letter) : Implement this hook to
      handle letter 'y'.
     (arm_elf_section_letter) : Declare it.
      * config/tc-arm.c (arm_elf_section_letter): Handle letter 'y' to set
      SHF_ARM_NOREAD section flag.
      * doc/c-arm.texi (ARM section attribute 'y'): Document it.

gas/testsuite/ChangeLog:
      * gas/arm/section-execute-only.s: New test case.
      * gas/arm/section-execute-only.d: Expected output.

ld/testsuite/ChangeLog:
      * ld-arm/thumb1-noread-not-present-mixing-two-section.s: Add 'y'
      attribute usage.
      * ld-arm/thumb1-noread-present-one-section.s: Likewise.
      * ld-arm/thumb1-noread-present-two-section.s: Likewise.
      * ld-arm/thumb1-input-section-flag-match.s: Likewise.

binutils/ChangeLog:
      * readelf.c (get_elf_section_flags): Display y letter for section
      with SHF_ARM_NOREAD section flag in readelf section output.
      (process_section_headers): Add y letter in readelf section output
      key mapping for ARM architecture.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted
@ 2016-01-20  4:14 sergiodj+buildbot
  2016-01-20 18:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-20  4:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be56871ee8f65c51b9eee611532ed036a71a72e0 ***

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

minor reformatting in printcmd.c::print_scalar_formatted

(GNU Coding Standard...)

gdb/ChangeLog:

        * printcmd.c (print_scalar_formatted): move binary operator from
        end of line to beginning of next line.  Adjust formatting
        accordingly.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes.
@ 2016-01-19 17:09 sergiodj+buildbot
  2016-01-19 22:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4ddf30f1108b2c0b3eee5677c912383ac903256 ***

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

Add support to readelf for reading FreeBSD ELF core notes.

binutils/ChangeLog:

	* readelf.c (get_freebsd_elfcore_note_type): New
	(process_note): Add support for FreeBSD core notes.

include/ChangeLog:

	* elf/common.h (NT_FREEBSD_THRMISC): Define.
	(NT_FREEBSD_PROCSTAT_PROC): Define.
	(NT_FREEBSD_PROCSTAT_FILES): Define.
	(NT_FREEBSD_PROCSTAT_VMMAP): Define.
	(NT_FREEBSD_PROCSTAT_GROUPS): Define.
	(NT_FREEBSD_PROCSTAT_UMASK): Define.
	(NT_FREEBSD_PROCSTAT_RLIMIT): Define.
	(NT_FREEBSD_PROCSTAT_OSREL): Define.
	(NT_FREEBSD_PROCSTAT_PSSTRINGS): Define.
	(NT_FREEBSD_PROCSTAT_AUXV): Define.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Factor out --status in DO_RUNTEST
@ 2016-01-19 16:35 sergiodj+buildbot
  2016-01-19 20:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41d1845edace3cf5dabd0aa7fa376b801fd5f675 ***

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

testsuite: Factor out --status in DO_RUNTEST

gdb/testsuite/ChangeLog:

	* Makefile.in (DO_RUNTEST): Add --status and update usages.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add PIC and TLS support to the ARC target.
@ 2016-01-19 15:37 sergiodj+buildbot
  2016-01-19 15:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-19 15:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 34e967a5f3ac5fd0353731a259e358d462823290 ***

Author: Miranda Cupertino <Cupertino.Miranda@synopsys.com>
Branch: master
Commit: 34e967a5f3ac5fd0353731a259e358d462823290

Add PIC and TLS support to the ARC target.

bfd/ChangeLog:
	* arc-plt.def: New file.
	* arc-plt.h: Likewise.
	* elf32-arc.c (elf_arc_abs_plt0_entry, elf_arc_abs_pltn_entry,
		       elf_arcV2_abs_plt0_entry, elf_arcV2_abs_pltn_entry,
		       elf_arc_pic_plt0_entry, elf_arc_pic_pltn_entry,
		       elf_arcV2_pic_plt0_entry, elf_arcV2_pic_pltn_entry): Remove.
	(name_for_global_symbol): Added.
	(ADD_RELA): Helper to create dynamic relocs.
	(new_got_entry_to_list): Create a new got entry in linked list.
	(symbol_has_entry_of_type): Search for specific type of entry in
	list.
	(is_reloc_for_GOT): return FALSE for any TLS related relocs.
	(is_reloc_for_TLS, arc_elf_set_private_flags)
	(arc_elf_print_private_bfd_data, arc_elf_copy_private_bfd_data)
	(arc_elf_merge_private_bfd_data): New functions.
	(debug_arc_reloc): Cleaned debug info printing.
	(PDATA reloc): Changed not to perform address alignment.
	(reverse_me): Added. Fix for ARC_32 relocs.
	(arc_do_relocation): Return bfd_reloc_of when no relocation should
	occur.
	(arc_get_local_got_ents): Renamed from arc_get_local_got_offsets.
	Changed function to access an array of list of GOT entries instead
	of just an array of offsets.
	(elf_arc_relocate_section): Added support for PIC and TLS related relocations.
	(elf_arc_check_relocs): Likewise.
	(elf_arc_adjust_dynamic_symbol, elf_arc_finish_dynamic_symbol,
	(elf_arc_finish_dynamic_sections): Likewise
	(arc_create_dynamic_sections): Modified conditions to create
	dynamic sections.
	(ADD_SYMBOL_REF_SEC_AND_RELOC): New macro.
	(plt_do_relocs_for_symbol, relocate_plt_for_symbol)
	(relocate_plt_for_entry): Changed to support new way to define PLT
	related code.
	(add_symbol_to_plt): Likewise.
	(arc_elf_link_hash_table_create): New function.

include/ChangeLog:
	* elf/arc-reloc.def (ARC_32, ARC_GOTPC, ARC_TLS_GD_GOT)
	(ARC_TLS_IE_GOT, ARC_TLS_DTPOFF, ARC_TLS_DTPOFF_S9, ARC_TLS_LE_S9)
	(ARC_TLS_LE_32): Fixed formula.
	(ARC_TLS_GD_LD): Use new special function.
	* opcode/arc-func.h: Changed all the replacement
	functions to clear the patching bits before doing an or it with the value
	argument.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>]
* [binutils-gdb] testsuite: Remove unused global references in gdb_test
@ 2016-01-18 17:08 sergiodj+buildbot
  2016-01-18 20:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8bcbad33671aa67a0079fe4f8f448458de8cc05f ***

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

testsuite: Remove unused global references in gdb_test

Those are unused since gdb_test_multiple was added, factoring out most
of the content of gdb_test.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_test): Remove unused global references.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix PR threads/19422 - show which thread caused stop
@ 2016-01-18 16:03 sergiodj+buildbot
  2016-01-18 18:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 16:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f303dbd60d9c7984832446eeb9d4e4d89703c615 ***

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

Fix PR threads/19422 - show which thread caused stop

This commit changes GDB like this:

 - Program received signal SIGINT, Interrupt.
 + Thread 1 "main" received signal SIGINT, Interrupt.

 - Breakpoint 1 at 0x40087a: file threads.c, line 87.
 + Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file threads.c, line 87.

 ... once the program goes multi-threaded.  Until GDB sees a second
thread spawn, the output is still the same as before, per the
discussion back in 2012:

  https://www.sourceware.org/ml/gdb/2012-11/msg00010.html

This helps non-stop mode, where you can't easily tell which thread hit
a breakpoint or received a signal:

 (gdb) info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fc1740 (LWP 19362) "main" (running)
   2    Thread 0x7ffff7fc0700 (LWP 19366) "foo" (running)
   3    Thread 0x7ffff77bf700 (LWP 19367) "bar" (running)
 (gdb)
 Program received signal SIGUSR1, User defined signal 1.
 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
 92          lll_wait_tid (pd->tid);
 (gdb) b threads.c:87
 Breakpoint 1 at 0x40087a: file threads.c, line 87.
 (gdb)
 Breakpoint 1, thread_function1 (arg=0x1) at threads.c:87
 87              usleep (1);  /* Loop increment.  */

The best the user can do is run "info threads" and try to figure
things out.

It actually also affects all-stop mode, in case of "handle SIG print
nostop":

...
  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.

  Program received signal SIGUSR1, User defined signal 1.
...

The above doesn't give any clue that these were different threads
getting the SIGUSR1 signal.

I initially thought of lowercasing "breakpoint" in

  "Thread 3 hit Breakpoint 1"

but then after trying it I realized that leaving "Breakpoint"
uppercase helps the eye quickly find the relevant information.  It's
also easier to implement not showing anything about threads until the
program goes multi-threaded this way.

Here's a larger example session in non-stop mode:

  (gdb) c -a&
  Continuing.
  (gdb) interrupt -a
  (gdb)
  Thread 1 "main" stopped.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);

  Thread 2 "foo" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

  Thread 3 "bar" stopped.
  0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
  b threads.c:87
  Breakpoint 4 at 0x40087a: file threads.c, line 87.
  (gdb) b threads.c:67
  Breakpoint 5 at 0x400811: file threads.c, line 67.
  (gdb) c -a&
  Continuing.
  (gdb)
  Thread 3 "bar" hit Breakpoint 4, thread_function1 (arg=0x1) at threads.c:87
  87              usleep (1);  /* Loop increment.  */

  Thread 2 "foo" hit Breakpoint 5, thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" (running)
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) shell kill -SIGINT 31957
  (gdb)
  Thread 1 "main" received signal SIGINT, Interrupt.
  0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
  92          lll_wait_tid (pd->tid);
  info threads
    Id   Target Id         Frame
  * 1  Thread 0x7ffff7fc1740 (LWP 31957) "main" 0x0000003616a09237 in pthread_join (threadid=140737353877248, thread_return=0x7fffffffd5b8) at pthread_join.c:92
    2  Thread 0x7ffff7fc0700 (LWP 31961) "foo" thread_function0 (arg=0x0) at threads.c:68
    3  Thread 0x7ffff77bf700 (LWP 31962) "bar" thread_function1 (arg=0x1) at threads.c:87
  (gdb) t 2
  [Switching to thread 2, Thread 0x7ffff7fc0700 (LWP 31961)]
  #0  thread_function0 (arg=0x0) at threads.c:68
  68              (*myp) ++;
  (gdb) catch syscall
  Catchpoint 6 (any syscall)
  (gdb) c&
  Continuing.
  (gdb)
  Thread 2 "foo" hit Catchpoint 6 (call to syscall nanosleep), 0x0000003615ebc6ed in nanosleep () at ../sysdeps/unix/syscall-template.S:81
  81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)

I'll work on documentation next if this looks agreeable.

This patch applies on top of the star wildcards thread IDs series:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00291.html

For convenience, I've pushed this to the
users/palves/show-which-thread-caused-stop branch.

gdb/doc/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Threads): Mention that GDB displays the ID and name
	of the thread that hit a breakpoint or received a signal.

gdb/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that GDB now displays the ID and name of the
	thread that hit a breakpoint or received a signal.
	* break-catch-sig.c (signal_catchpoint_print_it): Use
	maybe_print_thread_hit_breakpoint.
	* break-catch-syscall.c (print_it_catch_syscall): Likewise.
	* break-catch-throw.c (print_it_exception_catchpoint): Likewise.
	* breakpoint.c (maybe_print_thread_hit_breakpoint): New function.
	(print_it_catch_fork, print_it_catch_vfork, print_it_catch_solib)
	(print_it_catch_exec, print_it_ranged_breakpoint)
	(print_it_watchpoint, print_it_masked_watchpoint, bkpt_print_it):
	Use maybe_print_thread_hit_breakpoint.
	* breakpoint.h (maybe_print_thread_hit_breakpoint): Declare.
	* gdbthread.h (show_thread_that_caused_stop): Declare.
	* infrun.c (print_signal_received_reason): Print which thread
	received signal.
	* thread.c (show_thread_that_caused_stop): New function.

gdb/testsuite/ChangeLog:
2016-01-18  Pedro Alves  <palves@redhat.com>

	* gdb.base/async-shell.exp: Adjust expected output.
	* gdb.base/dprintf-non-stop.exp: Adjust expected output.
	* gdb.base/siginfo-thread.exp: Adjust expected output.
	* gdb.base/watchpoint-hw-hit-once.exp: Adjust expected output.
	* gdb.java/jnpe.exp: Adjust expected output.
	* gdb.threads/clone-new-thread-event.exp: Adjust expected output.
	* gdb.threads/continue-pending-status.exp: Adjust expected output.
	* gdb.threads/leader-exit.exp: Adjust expected output.
	* gdb.threads/manythreads.exp: Adjust expected output.
	* gdb.threads/pthreads.exp: Adjust expected output.
	* gdb.threads/schedlock.exp: Adjust expected output.
	* gdb.threads/siginfo-threads.exp: Adjust expected output.
	* gdb.threads/signal-command-multiple-signals-pending.exp: Adjust
	expected output.
	* gdb.threads/signal-delivered-right-thread.exp: Adjust expected
	output.
	* gdb.threads/sigthread.exp: Adjust expected output.
	* gdb.threads/watchpoint-fork.exp: Adjust expected output.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit
@ 2016-01-18 15:19 sergiodj+buildbot
  2016-01-18 17:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-18 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f69e520676f5f434cf43c250865036b3d516429 ***

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

Replace some $ARCH_{get,set}_pc with linux_{get,set}_pc_64bit

This patch is the follow-up of
https://sourceware.org/ml/gdb-patches/2016-01/msg00164.html to provide
linux_{get,set}_pc_64bit functions.

Rebuild GDBserver with tilegx-linux-gcc.  Not tested.

I think about pc in Tile-GX a little bit.  Looks current Tile-GX
supports debugging 32-bit program (multi-arch), but PC is always
64-bit.  See this thread
https://sourceware.org/ml/gdb-patches/2013-02/msg00113.html
and GDBserver reads PC as 64-bit through ptrace.  However, if
the inferior is 32-bit, the PC in the target description and
regcache is 32-bit, so only 32-bit contents are sent back GDB.
Anyway, Tile-GX GDBserver may have some problems here, but this
patch doesn't change anything.

gdb/gdbserver:

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

	* linux-low.c (linux_set_pc_64bit): New function.
	(linux_get_pc_64bit): New function.
	* linux-low.h (linux_set_pc_64bit, linux_get_pc_64bit):
	Declare.
	* linux-sparc-low.c (debug_threads): Remove declaration.
	(sparc_get_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit instead of
	sparc_get_pc.
	* linux-tile-low.c (tile_get_pc, tile_set_pc): Remove.
	(the_low_target): Use linux_get_pc_64bit and
	linux_set_pc_64bit.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] GDB SIGSEGV opening a Fortran program compiled with ifort
@ 2016-01-17  7:04 sergiodj+buildbot
  2016-01-17  9:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  7:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dc365182240722969f044918ecd3cab00da55502 ***

Author: Jonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>
Branch: master
Commit: dc365182240722969f044918ecd3cab00da55502

GDB SIGSEGV opening a Fortran program compiled with ifort

This patch fixes a SIGSEGV when trying to open a Fortran program
compiled with ifort (reproduced using version using version 16.0.1.150).
The error can be reproduce with most, if not any program. For instance,
a single file only containing "end", compiled with no additional flag,
suffices.

gdb/ChangeLog:

       PR gdb/19208
       * dwarf2read.c (read_partial_die): Do not call set_objfile_main_name
       if the function has no name.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] fix gdb version parsing in src-release.sh
@ 2016-01-17  6:17 sergiodj+buildbot
  2016-01-17  8:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b677098d4e086c093554a064076e021fec0399e8 ***

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

fix gdb version parsing in src-release.sh

Small change required after we switched the gdb version scheme to
using a -git suffix rather than a -cvs one.

ChangeLog:

        * src-release.sh: Compute the gdb tarball name by stripping
        '-git' rather than '-cvs'.

Tested by running "src-release.sh gdb" and verifying the tarball
name as well as its contents.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] minor reformatting in sim/common/sim-fpu.c.
@ 2016-01-17  5:43 sergiodj+buildbot
  2016-01-17  6:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-17  5:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c8e93b7fab5b9d8ddb786772ab00d65ec127159 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 3c8e93b7fab5b9d8ddb786772ab00d65ec127159

minor reformatting in sim/common/sim-fpu.c.

This patch just makes a copy of formatting changes to better conform
with the GNU Coding Style.

sim/common/ChangeLog:

        * sim-fpu.c (print_bits): Minor reformatting (no code change).
        (sim_fpu_map): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Star wildcard ranges (e.g., "info thread 2.*")
@ 2016-01-15 22:25 sergiodj+buildbot
  2016-01-15 23:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71ef29a86b252a4780517fc9b2bf9f7d3dd2d991 ***

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

Star wildcard ranges (e.g., "info thread 2.*")

Add support for specifying "all threads of inferior N", by writing "*"
as thread number/range in thread ID lists.

E.g., "info threads 2.*" or "thread apply 2.* bt".

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

	* NEWS: Mention star wildcard ranges.
	* cli/cli-utils.c (get_number_or_range): Check state->in_range first.
	(number_range_setup_range): New function.
	* cli/cli-utils.h (number_range_setup_range): New declaration.
	* thread.c (thread_apply_command): Support star TID ranges.
	* tid-parse.c (tid_range_parser_finished)
	(tid_range_parser_string, tid_range_parser_skip)
	(get_tid_or_range, get_tid_or_range): Handle
	TID_RANGE_STATE_STAR_RANGE.
	(tid_range_parser_star_range): New function.
	* tid-parse.h (enum tid_range_state) <TID_RANGE_STATE_STAR_RANGE>:
	New value.
	(tid_range_parser_star_range): New declaration.

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

	* gdb.texinfo (Threads) <thread ID lists>: Document star ranges.

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

	* gdb.multi/tids.exp: Test star wildcard ranges.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix "thread apply $conv_var" and misc other related problems
@ 2016-01-15 21:59 sergiodj+buildbot
  2016-01-15 22:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-15 21:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f5b7598805c8253c43c989a540a2408c8b685ad ***

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

Fix "thread apply $conv_var" and misc other related problems

This fixes a few bugs in "thread apply".

While this works:

 (gdb) thread apply 1 p 1234

 Thread 1 (Thread 0x7ffff7fc1740 (LWP 14048)):
 $1 = 1234

This doesn't:

 (gdb) thread apply $thr p 1234

 Thread 1 (Thread 0x7ffff7fc1740 (LWP 12039)):
 Invalid thread ID: p 1234
 (gdb)

~~~~

Also, while this works:
 (gdb) thread apply 1
 Please specify a command following the thread ID list

This doesn't:
 (gdb) thread apply $thr
 Thread 1 (Thread 0x7ffff7fc1740 (LWP 12039)):
 [Current thread is 1 (Thread 0x7ffff7fc1740 (LWP 12039))]
 (gdb)

~~~~

And, while this works:
 (gdb) thread apply
 Please specify a thread ID list

This obviously bogus invocation is just silent:
 (gdb) thread apply bt
 (gdb)

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

	* thread.c (thread_apply_command): Use the tid range parser to
	advance past the thread ID list.
	* tid-parse.c (get_positive_number_trailer): New function.
	(parse_thread_id): Use it.
	(get_tid_or_range): Use it.  Return 0 instead of throwing invalid
	thread ID error.
	(get_tid_or_range): Detect negative values.  Return 0 instead of
	throwing invalid thread ID error.

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

	* gdb.multi/tids.exp (thr_apply_info_thr_error): Remove "p 1234"
	command from "thread apply" invocation.
	(thr_apply_info_thr_invalid): Default the expected output to the
	input tid list.
	(top level): Add tests that use convenience variables.  Add tests
	for "thread apply" with a valid TID list, but missing the command.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Remove field syscall_next_pc in struct gdbarch_tdep
@ 2016-01-14 14:57 sergiodj+buildbot
  2016-01-14 15:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-14 14:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7cf25a8ab54cd02b48e7443ef25764475f02315 ***

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

[ARM] Remove field syscall_next_pc in struct gdbarch_tdep

Field syscall_next_pc in struct gdbarch_tdep was to calculate the
next pc of syscall instruction.  On linux target, syscall_next_pc
is set to arm_linux_syscall_next_pc, to do linux specific things.
However, after we have struct arm_get_next_pcs_ops, we can do the
same thing in struct arm_get_next_pcs_ops field syscall_next_pc,
so syscall_next_pc in struct gdbarch_tdep is not needed any more.

gdb:

2016-01-14  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_get_next_pcs_syscall_next_pc):
	Declare.
	(arm_linux_get_next_pcs_ops): Install
	arm_linux_get_next_pcs_syscall_next_pc.
	(arm_linux_syscall_next_pc): Change to ...
	(arm_linux_get_next_pcs_syscall_next_pc): ... it.
	(arm_linux_init_abi): Don't set tdep->syscall_next_pc.
	* arm-tdep.c (arm_get_next_pcs_syscall_next_pc): Declare.
	(arm_get_next_pcs_syscall_next_pc): Make it static.  Don't
	call tdep->syscall_next_pc.
	* arm-tdep.h (struct gdbarch_tdep) <syscall_next_pc>: Remove.
	(arm_get_next_pcs_syscall_next_pc): Remove.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add $_gthread convenience variable
@ 2016-01-13 11:42 sergiodj+buildbot
  2016-01-13 18:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-13 11:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 663f6d42f47265d2deaa86c8a976e658fb13f820 ***

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

Add $_gthread convenience variable

This commit adds a new $_gthread convenience variable, that is like
$_thread, but holds the current thread's global thread id.

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

	* NEWS: Mention $_gthread.
	* gdbthread.h (struct thread_info) <global_num>: Mention
	$_gthread.
	* thread.c (thread_num_make_value_helper): New function.
	(thread_id_make_value): Delete.
	(thread_id_per_inf_num_make_value, global_thread_id_make_value):
	New.
	(thread_funcs): Adjust.
	(gthread_funcs): New.
	(_initialize_thread): Register $_gthread variable.

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

	* gdb.base/default.exp: Expect $_gthread as well.
	* gdb.multi/tids.exp: Test $_gthread.
	* gdb.threads/thread-specific.exp: Test $_gthread.

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

	* gdb.texinfo (Threads): Document the $_gthread convenience
	variable.
	(Convenience Vars): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Implement 'catch syscall' for gdbserver
@ 2016-01-12 20:34 sergiodj+buildbot
  2016-01-13  2:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d ***

Author: Josh Stone <jistone@redhat.com>
Branch: master
Commit: 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d

Implement 'catch syscall' for gdbserver

This adds a new QCatchSyscalls packet to enable 'catch syscall', and new
stop reasons "syscall_entry" and "syscall_return" for those events.  It
is currently only supported on Linux x86 and x86_64.

gdb/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* NEWS (Changes since GDB 7.10): Mention QCatchSyscalls and the
	syscall_entry and syscall_return stop reasons.  Mention GDB
	support for remote catch syscall.
	* remote.c (PACKET_QCatchSyscalls): New enum.
	(remote_set_syscall_catchpoint): New function.
	(remote_protocol_features): New element for QCatchSyscalls.
	(remote_parse_stop_reply): Parse syscall_entry/return stops.
	(init_remote_ops): Install remote_set_syscall_catchpoint.
	(_initialize_remote): Config QCatchSyscalls.
	* linux-nat.h (struct lwp_info) <syscall_state>: Comment typo.

gdb/doc/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.texinfo (Remote Configuration): List the QCatchSyscalls packet.
	(Stop Reply Packets): List the syscall entry and return stop reasons.
	(General Query Packets): Describe QCatchSyscalls, and add it to the
	table and the detailed list of stub features.

gdb/gdbserver/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* inferiors.h: Include "gdb_vecs.h".
	(struct process_info): Add syscalls_to_catch.
	* inferiors.c (remove_process): Free syscalls_to_catch.
	* remote-utils.c (prepare_resume_reply): Report syscall_entry and
	syscall_return stops.
	* server.h (UNKNOWN_SYSCALL, ANY_SYSCALL): Define.
	* server.c (handle_general_set): Handle QCatchSyscalls.
	(handle_query): Report support for QCatchSyscalls.
	* target.h (struct target_ops): Add supports_catch_syscall.
	(target_supports_catch_syscall): New macro.
	* linux-low.h (struct linux_target_ops): Add get_syscall_trapinfo.
	(struct lwp_info): Add syscall_state.
	* linux-low.c (handle_extended_wait): Mark syscall_state as an entry.
	Maintain syscall_state and syscalls_to_catch across exec.
	(get_syscall_trapinfo): New function, proxy to the_low_target.
	(linux_low_ptrace_options): Enable PTRACE_O_TRACESYSGOOD.
	(linux_low_filter_event): Toggle syscall_state entry/return for
	syscall traps, and set it ignored for all others.
	(gdb_catching_syscalls_p): New function.
	(gdb_catch_this_syscall_p): New function.
	(linux_wait_1): Handle SYSCALL_SIGTRAP.
	(linux_resume_one_lwp_throw): Add PTRACE_SYSCALL possibility.
	(linux_supports_catch_syscall): New function.
	(linux_target_ops): Install it.
	* linux-x86-low.c (x86_get_syscall_trapinfo): New function.
	(the_low_target): Install it.

gdb/testsuite/ChangeLog:

2016-01-12  Josh Stone  <jistone@redhat.com>
	    Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/catch-syscall.c (do_execve): New variable.
	(main): Conditionally trigger an execve.
	* gdb.base/catch-syscall.exp: Enable testing for remote targets.
	(test_catch_syscall_execve): New, check entry/return across execve.
	(do_syscall_tests): Call test_catch_syscall_execve.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Support ARMv8.2 RAS extension.
@ 2016-01-12 16:46 sergiodj+buildbot
  2016-01-12 23:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 105bde5771c1c1b26b69e3623c88f3caafa3a480 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 105bde5771c1c1b26b69e3623c88f3caafa3a480

[ARM] Support ARMv8.2 RAS extension.

The ARMv8.2 architecture includes the RAS extension which adds an
instruction, ESB, and a number of coprocessor registers. This patch adds
the instruction to binutils, making it available when -march=armv8.2-a
is selected. It also adds tests for the instruction and for the
coprocessor registers.

gas/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-arm.c (arm_ext_v8_2): New.
	(insns): Add "esb".
	* testsuite/gas/arm/armv8_2-a.d: New.
	* testsuite/gas/arm/armv8_2-a.s: New.

opcodes/
2016-01-12  Matthew Wahab  <matthew.wahab@arm.com>

	* arm-dis.c (arm_opcodes): Add "esb".
	(thumb_opcodes): Likewise.

Change-Id: I67f3d70789db78d1c66a56c4994675f99ac15e34


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix invalid conversion from void * to gdb_byte *
@ 2016-01-12 16:34 sergiodj+buildbot
  2016-01-12 19:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d18547d8b08615a58db18ad3e43f721dc92ae298 ***

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

Fix invalid conversion from void * to gdb_byte *

This patch fixes the following GDB build error in C++ mode.

gdb/nat/linux-ptrace.c: In function 'int linux_child_function(void*)':
gdb/nat/linux-ptrace.c:323:65: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
   linux_fork_to_function (child_stack, linux_grandchild_function);
                                                                 ^

gdb:

2016-01-12  Yao Qi  <yao.qi@linaro.org>

	* nat/linux-ptrace.c (linux_child_function): Cast child_stack
	to gdb_byte * and pass to linux_fork_to_function.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver: use the new gdb warning helpers
@ 2016-01-12 15:45 sergiodj+buildbot
  2016-01-12 18:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8f13a3ce8afc1144169a14c7704689e263316e70 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8f13a3ce8afc1144169a14c7704689e263316e70

gdbserver: use the new gdb warning helpers

We need to use -Wno-missing-prototypes for now as much of the code
sticks externs in local files and not in common headers.

2016-01-11  Mike Frysinger  <vapier@gentoo.org>

	* acinclude.m4: Include new ../warning.m4 file.
	* configure: Regenerated.
	* configure.ac: Replace all warning logic with AM_GDB_WARNINGS.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Change function signature passed to clone
@ 2016-01-12 15:22 sergiodj+buildbot
  2016-01-12 16:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 15:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba4dd7c4a1d99c62a1c2edd68f511a82f8fe041e ***

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

Change function signature passed to clone

I see the following compile error with an old bfin-uclinux gcc to
build GDBserver,

 cc1: warnings being treated as errors
 gdb/gdbserver/../nat/linux-ptrace.c: In function 'linux_fork_to_function':
 gdb/gdbserver/../nat/linux-ptrace.c:283: error: passing argument 1 of 'clone' from incompatible pointer type

in glibc, clone's prototype is like this, and in uClibc, it is the same,

       int clone(int (*fn)(void *), void *child_stack,
                 int flags, void *arg, ...
                 /* pid_t *ptid, struct user_desc *tls, pid_t *ctid */ );

so this patch changes function signature from 'void (*function) (gdb_byte *)'
to 'int (*function) (void *)'.

Note that I find Pedro advised to change argument type from 'void *'
to 'gdb_byte *' during the patch review
https://sourceware.org/ml/gdb-patches/2013-08/msg00611.html  however,
I think fix compile error can justify the change back to 'void *'.

gdb:

2016-01-12  Yao Qi  <yao.qi@linaro.org>

	* nat/linux-ptrace.c (linux_fork_to_function): Change type
	of argument 'function'.
	(linux_grandchild_function): Change return type to 'int'.
	Change child_stack's type to 'void *'.
	(linux_child_function): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk"
@ 2016-01-12 12:01 sergiodj+buildbot
  2016-01-12 12:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5eddd57823971bdb54f957d10c11ff3fc9f97b1e ***

Author: Thomas Schwinge <thomas@codesourcery.com>
Branch: master
Commit: 5eddd57823971bdb54f957d10c11ff3fc9f97b1e

Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk"

The "mawk" AWK implementation did't like that regular expression:

    mawk: [...]/gdb/reply_mig_hack.awk: line 98: regular expression compile failed (missing operand)

	gdb/
	* reply_mig_hack.awk: Rewrite one regular expression.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Reapply: List inferiors/threads/pspaces in ascending order
@ 2016-01-12  1:37 sergiodj+buildbot
  2016-01-12  7:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-12  1:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b05b120205e697db6291abb95a8cd2be054f99e9 ***

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

Reapply: List inferiors/threads/pspaces in ascending order

[This reapplies a change that was accidentally reverted with c0ecb95f3d.]

Before:
  (gdb) info threads
    Id   Target Id         Frame
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92

After:
  (gdb) info threads
    Id   Target Id         Frame
  * 1    Thread 0x7ffff7fc5740 (LWP 29030) 0x0000003b37209237 in pthread_join (threadid=140737353893632, thread_return=0x0) at pthread_join.c:92
    2    Thread 0x7ffff7fc4700 (LWP 29034) 0x000000000040087b in child_function_2 (arg=0x0) at foo.c:60
    3    Thread 0x7ffff77c3700 (LWP 29035) callme () at foo.c:30

gdb/doc/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.texinfo (Inferiors and Programs): Adjust "maint info
	program-spaces" example to ascending order listing.
	(Threads): Adjust "info threads" example to ascending order
	listing.
	(Forks): Adjust "info inferiors" example to ascending order
	listing.

gdb/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* inferior.c (add_inferior_silent): Append the new inferior to the
	end of the list.
	* progspace.c (add_program_space): Append the new pspace to the
	end of the list.
	* thread.c (new_thread): Append the new thread to the end of the
	list.

gdb/testsuite/ChangeLog:
2015-11-24  Pedro Alves  <palves@redhat.com>

	PR 17539
	* gdb.base/foll-exec-mode.exp: Adjust to GDB listing inferiors and
	threads in ascending order.
	* gdb.base/foll-fork.exp: Likewise.
	* gdb.base/foll-vfork.exp: Likewise.
	* gdb.base/multi-forks.exp: Likewise.
	* gdb.mi/mi-nonstop.exp: Likewise.
	* gdb.mi/mi-nsintrall.exp: Likewise.
	* gdb.multi/base.exp: Likewise.
	* gdb.multi/multi-arch.exp: Likewise.
	* gdb.python/py-inferior.exp: Likewise.
	* gdb.threads/break-while-running.exp: Likewise.
	* gdb.threads/execl.exp: Likewise.
	* gdb.threads/gcore-thread.exp: Likewise.
	* gdb.threads/info-threads-cur-sal.exp: Likewise.
	* gdb.threads/kill.exp: Likewise.
	* gdb.threads/linux-dp.exp: Likewise.
	* gdb.threads/multiple-step-overs.exp: Likewise.
	* gdb.threads/next-bp-other-thread.exp: Likewise.
	* gdb.threads/step-bg-decr-pc-switch-thread.exp: Likewise.
	* gdb.threads/step-over-lands-on-breakpoint.exp: Likewise.
	* gdb.threads/step-over-trips-on-watchpoint.exp: Likewise.
	* gdb.threads/thread-find.exp: Likewise.
	* gdb.threads/tls.exp: Likewise.
	* lib/mi-support.exp (mi_reverse_list): Delete.
	(mi_check_thread_states): No longer reverse list.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: i386 regression for funcargs.exp
@ 2016-01-11 21:31 sergiodj+buildbot
  2016-01-12  0:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01d8c27e4f77375c0e157d115266129b76ff6734 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 01d8c27e4f77375c0e157d115266129b76ff6734

testsuite: i386 regression for funcargs.exp

3ca22649a6dfeb71058c33be4d0542b98f1f0ff5 is the first bad commit
commit 3ca22649a6dfeb71058c33be4d0542b98f1f0ff5
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Mon Dec 21 12:51:54 2015 -0500
    Remove HP-UX references fom testsuite
@@ -1013,13 +1013,6 @@ proc localvars_in_indirect_call { } {
     #

     gdb_test_multiple "finish" "finish from indirectly called function" {
-       -re "\\(\\*pointer_to_call0a\\) \\(c, s, i, l\\);.*First.*$gdb_prompt $" {
-           #On hppa2.0w-hp-hpux11.00, gdb finishes at one line earlier than
-           #hppa1.1-hp-hpux11.00. Therefore, an extra "step" is necessary
-           #to continue the test.
-           send_gdb "step\n"
-           exp_continue
-	}
        -re ".*\\(\\*pointer_to_call0a\\) \\(c, s, i, l\\);.*Second.*$gdb_prompt $" {
            pass "finish from indirectly called function"
       	}

->

 finish^M
 Run till exit from #0  call0a (c=97 'a', s=1, i=2, l=3) at ./gdb.base/funcargs.c:82^M
 0x0804a189 in main () at ./gdb.base/funcargs.c:583^M
 583	  (*pointer_to_call0a) (c, s, i, l);    /* First step into call0a.  */^M
-(gdb) step^M
-584	  (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */^M
-(gdb) PASS: gdb.base/funcargs.exp: finish from indirectly called function
+(gdb) FAIL: gdb.base/funcargs.exp: finish from indirectly called function
 step^M
-call0a (c=97 'a', s=1, i=2, l=3) at ./gdb.base/funcargs.c:82^M
-82	  c = 'a';^M
-(gdb) PASS: gdb.base/funcargs.exp: stepping into indirectly called function
+584	  (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */^M
+(gdb) FAIL: gdb.base/funcargs.exp: stepping into indirectly called function

At least on x86_64 with testsuite in -m32 (expecting native i386 would be the
same).

Pedro Alves:

The difference is that with newer GCC there's an extra instruction
after the call which is still assigned to line 583:

$ diff -up /tmp/4.8.3 /tmp/6.0.0 -U 1000
--- /tmp/4.8.3  2016-01-11 12:37:39.611089156 +0000
+++ /tmp/6.0.0  2016-01-11 13:21:00.021127976 +0000
@@ -1,27 +1,30 @@
 583       (*pointer_to_call0a) (c, s, i, l);    /* First step into call0a.  */
    mov    0x804d060,%ebx
    mov    0x804d050,%ecx
    movzwl 0x804d040,%eax
    movswl %ax,%edx
    movzbl 0x804d030,%eax
    movsbl %al,%eax
-   mov    %ebx,0xc(%esp)
-   mov    %ecx,0x8(%esp)
-   mov    %edx,0x4(%esp)
-   mov    %eax,(%esp)
-   mov    0x7c(%esp),%eax
+   push   %ebx
+   push   %ecx
+   push   %edx
+   push   %eax
+   mov    -0x1c(%ebp),%eax
    call   *%eax
+   add    $0x10,%esp

 584	   (*pointer_to_call0a) (c, s, i, l);    /* Second step into call0a.  */
    mov    0x804d060,%ebx
    mov    0x804d050,%ecx
    movzwl 0x804d040,%eax
    movswl %ax,%edx
    movzbl 0x804d030,%eax
    movsbl %al,%eax
-   mov    %ebx,0xc(%esp)
-   mov    %ecx,0x8(%esp)
-   mov    %edx,0x4(%esp)
-   mov    %eax,(%esp)
-   mov    0x7c(%esp),%eax
+   push   %ebx
+   push   %ecx
+   push   %edx
+   push   %eax
+   mov    -0x1c(%ebp),%eax
    call   *%eax
+   add    $0x10,%esp
+

I don't know why -m32 changed to push/add instead of mov while 64-bit hasn't.

This is most likely needed on non-x86 ports as well.

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.base/funcargs.exp (finish from indirectly called function):
	Reintroduce the case for 'First'.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] testsuite: Fix false FAILs on too long base directory
@ 2016-01-11 21:16 sergiodj+buildbot
  2016-01-11 21:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0ecb95f3dc0c3e8d1545f0a37c0c3e537e1ea96 ***

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

testsuite: Fix false FAILs on too long base directory

I was getting

gu (print arg0)^M
= 0x7fffffffdafb
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.guile/scm-value/scm-"...^M
(gdb) FAIL: gdb.guile/scm-value.exp: verify dereferenced value
python print (arg0)^M
0x7fffffffdafd
"/unsafebuild-x86_64-redhat-linux-gnu/gdb/testsuite.unix.-m64/outputs/gdb.python/py-value/py-v"...^M
(gdb) FAIL: gdb.python/py-value.exp: verify dereferenced value

and also:

(gdb) p argv[0]^M
$2 = 0x7fffffffd832 "/home/jkratoch/redhat/gdb-test-", 'x' <repeats 169
times>...^M
(gdb) FAIL: gdb.guile/scm-value.exp: argv[0] should be available on this
target

gdb/testsuite/ChangeLog
2016-01-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.guile/scm-value.exp (test_value_in_inferior): Set print elements
	and repeats to unlimited.
	* gdb.python/py-value.exp: Likewise.
	* lib/gdb.exp (gdb_has_argv0): Save and temporarily set print elements
	and repeats to unlimited.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: split out warnings helpers
@ 2016-01-11 19:13 sergiodj+buildbot
  2016-01-11 19:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b835bb5265d614fd8a4759f284b987b365292c36 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b835bb5265d614fd8a4759f284b987b365292c36

gdb: split out warnings helpers

This will allow the sim tree to use the same set of warnings.
The new code in warning.m4 is exactly the same (other than the
AC_DEFUN wrapping).


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Import changes made to files shared with the FSF GCC project.
@ 2016-01-11 11:18 sergiodj+buildbot
  2016-01-11 11:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-11 11:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4849dfd8f454b9c595e6ee7477f6b7b25c31a499 ***

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

Import changes made to files shared with the FSF GCC project.

	Import the following changes from the GCC mainline:

	2015-11-13  Tsvetkova Alexandra  <aleksandra.tsvetkova@intel.com>

	* configure.ac: Enable libmpx by default.
	* configure: Regenerated.

	2015-11-19  Martin Liska  <mliska@suse.cz>

	* .gitignore: Add .clang-format to ignored files.
	* Makefile.tpl: Add clang-format.
	* Makefile.in: Regenerate.

	2015-12-01  Andreas Tobler  <andreast@gcc.gnu.org>

	PR libffi/65726
	* Makefile.def (lang_env_dependencies): Make libffi depend
	on cxx.
	* Makefile.in: Regenerate.

	2015-12-02  Ian Lance Taylor  <iant@google.com>

	PR go/66147
	* Makefile.tpl (HOST_EXPORTS): Add XGCC_FLAGS_FOR_TARGET.
	* Makefile.in: Regenerate.

	2015-12-17  Nathan Sidwell  <nathan@acm.org>

	* config/isl.m4 (ISL_CHECK_VERSION): Add gmp libs.
	* configure: Regenerate.

	2015-12-17  Sebastian Pop  <s.pop@samsung.com>

	* Makefile.in: Replace ISL with isl.
	* Makefile.tpl: Same.
	* config/isl.m4: Same.
	* configure.ac: Same.
	* contrib/download_prerequisites: Same.
	* configure: Regenerate.

	2016-01-01  Ben Elliston  <bje@gnu.org>

	* config.guess: Import version 2016-01-01.
	* config.sub: Likewise.

include	2016-01-07  Mike Frysinger  <vapier@gentoo.org>

	* longlong.h: Change !__SHMEDIA__ to
	(!defined (__SHMEDIA__) || !__SHMEDIA__).
	Change __SHMEDIA__ to defined (__SHMEDIA__) && __SHMEDIA__.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: drop unused SIM_AC_OPTION_PACKAGES
@ 2016-01-10 23:15 sergiodj+buildbot
  2016-01-11  1:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 23:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e19418e02e25ae4c62eb95547220897fa6aaf2e0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e19418e02e25ae4c62eb95547220897fa6aaf2e0

sim: drop unused SIM_AC_OPTION_PACKAGES

This was imported from the ppc sim, but that was only used to control
a single file, and that is already governed by the hw models.  There's
no need to have a sep configure option here, especially since none of
the other sims are using it.  Even when the code is enabled, there's
no runtime overhead.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: allow the assert configure option everywhere
@ 2016-01-10 22:20 sergiodj+buildbot
  2016-01-10 22:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-10 22:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35656e95217a20309c0a0f16bf0c89a49a549177 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 35656e95217a20309c0a0f16bf0c89a49a549177

sim: allow the assert configure option everywhere

Currently ports have to call SIM_AC_OPTION_ASSERT explicitly in order
to make the configure flag available, which none of them do.  There's
no real reason to not allow this flag for all ports, so move it to the
common sim macro.  This way we get standard behavior across all ports.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: drop targ-vals.def->nltvals.def indirection
@ 2016-01-10  9:12 sergiodj+buildbot
  2016-01-10 12:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  9:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99d8e879938c947588332a9cc579d378ccc2a855 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 99d8e879938c947588332a9cc579d378ccc2a855

sim: drop targ-vals.def->nltvals.def indirection

We don't have alternative nltvals.def files, so always symlinking
the targ-vals.def file to it doesn't gain us anything.  It does
make the build more complicated though and a pain to convert to
something newer (like automake).  Drop the symlinking entirely.

In the future, we'll want to explode this file anyways into the
respective arch dirs so things can be selected dynamically at
runtime, so it's not like we'll be bringing this back.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: drop --enable-sim-{regparm,stdcall} options
@ 2016-01-10  8:33 sergiodj+buildbot
  2016-01-10  9:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-10  8:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0dc73ef7c304e6ffc9ce43b2131c77553a74e1d4 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0dc73ef7c304e6ffc9ce43b2131c77553a74e1d4

sim: drop --enable-sim-{regparm,stdcall} options

These options were never exposed for most sims (just the ppc one),
and they are really only useful on 32-bit x86 systems.  Considering
modern systems tend to be 64-bit x86_64 and how well modern compilers
are at optimizing code, these have outlived their usefulness.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h
@ 2016-01-09  9:01 sergiodj+buildbot
  2016-01-09  9:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-09  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 936df7568a0e47547285a0dd57b81643264fef38 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 936df7568a0e47547285a0dd57b81643264fef38

sim: drop common/cconfig.h in favor of a single config.h

The common subdir sets up a cconfig.h file to hold checks for the common
code.  In practice, most files still end up using config.h instead which
just leads to confusion.

Merge all the configure checks that went into cconfig.h into SIM_AC_COMMON
so we can drop the cconfig.h file altogether.  Now there is only a single
config.h file like normal.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.multi/base.exp testsuite regression
@ 2016-01-08 19:16 sergiodj+buildbot
  2016-01-08 19:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 19:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cfc1fcb515d1ecd8445905b4749b81b3ca69552 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 6cfc1fcb515d1ecd8445905b4749b81b3ca69552

Fix gdb.multi/base.exp testsuite regression

Regressed by:

commit 762f774785f4ef878ac4c831e1f4733dc957234d
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Dec 10 16:21:06 2015 +0000
    Stop using nowarnings in gdb/testsuite/gdb.multi/

+gdb compile failed, gdb/testsuite/gdb.multi/hello.c: In function 'commonfun':
+gdb/testsuite/gdb.multi/hello.c:24:19: warning: implicit declaration of function 'bar' [-Wimplicit-function-declaration]
+ int commonfun() { bar(); } /* from hello */
+                   ^
+gdb/testsuite/gdb.multi/hello.c: At top level:
+gdb/testsuite/gdb.multi/hello.c:26:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ bar()
+ ^
+gdb/testsuite/gdb.multi/hello.c:32:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ hello(int x)
+ ^
+gdb/testsuite/gdb.multi/hello.c:38:1: warning: return type defaults to 'int' [-Wimplicit-int]
+ main()
+ ^
+UNTESTED: gdb.multi/base.exp: base.exp

gdb/testsuite/ChangeLog
2016-01-08  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* gdb.multi/goodbye.c: Fix compilation warnings by adding return types
	and reordering the functions.
	* gdb.multi/hangout.c: Likewise.
	* gdb.multi/hello.c: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] perf testsuite: python 3 fixes
@ 2016-01-08 15:34 sergiodj+buildbot
  2016-01-08 15:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 582a1b0064b14cb12b18f48678876d32c59c11c8 ***

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

perf testsuite: python 3 fixes

There are a few errors when trying to run the performance testsuite with
Python 3.  This commit fixes them.

In Python 2, it was possible to use relative imports (importing a module
relative to the current one).  In Python 3 it isn't.  So I use
absolute_import from the __future__ module, which allows Python 2 to
behave like Python 3, and use the Python 3 syntax.

In Python 3, dict.iterkeys doesn't exist anymore.  Using dict.keys is a
good compromise in this case.

gdb/testsuite/ChangeLog:

	* gdb.perf/lib/perftest/perftest.py: Change relative imports to
	absolute.
	(SingleStatisticTestResult.report): Use dict.keys instead of
	dict.iterkeys.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Change SIGINT handler for extension languages only when target terminal is ours
@ 2016-01-08 11:25 sergiodj+buildbot
  2016-01-08 14:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f99e8fc9cb84ca80cfca6c119f1f22bbfd2a314 ***

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

Change SIGINT handler for extension languages only when target terminal is ours

I see a timeout in gdb.base/random-signal.exp,

 Continuing.^M
 PASS: gdb.base/random-signal.exp: continue
 ^CPython Exception <type 'exceptions.KeyboardInterrupt'> <type
 exceptions.KeyboardInterrupt'>: ^M
 FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)

it can be reproduced by running random-signal.exp with native-gdbserver
in a loop, like this, and the fail will be shown in about 20 runs,

$ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver random-signal.exp"; done)

In the test, the program is being single-stepped for software watchpoint,
and in each internal stop, python unwinder sniffer is used,

 #0  pyuw_sniffer (self=<optimised out>, this_frame=<optimised out>, cache_ptr=0xd554f8) at /home/yao/SourceCode/gnu/gdb/git/gdb/python/py-unwind.c:608
 #1  0x00000000006a10ae in frame_unwind_try_unwinder (this_frame=this_frame@entry=0xd554e0, this_cache=this_cache@entry=0xd554f8, unwinder=0xecd540)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/frame-unwind.c:107
 #2  0x00000000006a143f in frame_unwind_find_by_frame (this_frame=this_frame@entry=0xd554e0, this_cache=this_cache@entry=0xd554f8)
     at /home/yao/SourceCode/gnu/gdb/git/gdb/frame-unwind.c:163
 #3  0x000000000069dc6b in compute_frame_id (fi=0xd554e0) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:454
 #4  get_prev_frame_if_no_cycle (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1781
 #5  0x000000000069fdb9 in get_prev_frame_always_1 (this_frame=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1955
 #6  get_prev_frame_always (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:1971
 #7  0x00000000006a04b1 in get_prev_frame (this_frame=this_frame@entry=0xd55410) at /home/yao/SourceCode/gnu/gdb/git/gdb/frame.c:2213

when GDB goes to python extension, or other language extension, the
SIGINT handler is changed, and is restored when GDB leaves extension
language.  GDB only stays in extension language for a very short period
in this case, but if ctrl-c is pressed at that moment, python extension
will handle the SIGINT, and exceptions.KeyboardInterrupt is shown.

Language extension is used in GDB side rather than inferior side,
so GDB should only change SIGINT handler for extension language when
the terminal is ours (not inferior's).  This is what this patch does.
With this patch applied, I run random-signal.exp in a loop for 18
hours, and no fail is shown.

gdb:

2016-01-08  Yao Qi  <yao.qi@linaro.org>

	* extension.c: Include target.h.
	(set_active_ext_lang): Only call install_gdb_sigint_handler,
	check_quit_flag, and set_quit_flag if target_terminal_is_ours
	returns false.
	(restore_active_ext_lang): Likewise.
	* target.c (target_terminal_is_ours): New function.
	* target.h (target_terminal_is_ours): Declare.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Check input interrupt first when reading packet
@ 2016-01-08 11:16 sergiodj+buildbot
  2016-01-08 12:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-08 11:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a0dd67a459338efb77f8d82bb3650d801ff0dd5 ***

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

Check input interrupt first when reading packet

Hi,
I see timeout in one of several runs of random-signal.exp like this,

 $ (set -e; while true; do make check RUNTESTFLAGS="--target_board=native-gdbserver random-signal.exp"; done)

In about every five runs, we can see a fail,

PASS: gdb.base/random-signal.exp: continue
^CFAIL: gdb.base/random-signal.exp: stop with control-c (timeout)

after some investigation, I find '\003' may be discarded by GDBserver when
it is expecting '$'.  In GDB side, both normal packets and '\003' are sent
via function send, but GDBserver may receive them at any time, that is to
say, in the receive buffer in GDBserver, '\003' may appear before or after
normal packet.  However, current GDBserver doesn't handle this case.

With this patch applied, I don't see this fail in multiple runs.
Although there is still timeout fail, that is a different problem, the
next patch will fix it.

gdb/gdbserver:

2016-01-08  Yao Qi  <yao.qi@linaro.org>

	* remote-utils.c (getpkt): If c is '\003', call target hook
	request_interrupt.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE
@ 2016-01-08  9:58 sergiodj+buildbot
  2016-01-08 10:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-08  9:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 109575d7ebac21a0eb67980001ecd4173d696f88 ***

Author: Jiong Wang <jiong.wang@arm.com>
Branch: master
Commit: 109575d7ebac21a0eb67980001ecd4173d696f88

[ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE

2016-01-08  Richard Sandiford  <richard.sandiford@arm.com>
	    Jiong Wang  <jiong.wang@arm.com>

	PR ld/19368
	bfd/
	* elf32-arm.c (elf32_arm_reloc_type_class): Map R_ARM_IRELATIVE to
	reloc_class_ifunc.

	ld/
	* testsuite/ld-arm/ifunc-3.rd: Update expected result.
	* testsuite/ld-arm/ifunc-4.rd: Likewise.
	* testsuite/ld-arm/ifunc-9.rd: Likewise.
	* testsuite/ld-arm/ifunc-10.rd: Likewise.
	* testsuite/ld-arm/ifunc-12.rd: Likewise.
	* testsuite/ld-arm/ifunc-13.rd: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: config: drop use of __DATE__/__TIME__
@ 2016-01-07  3:07 sergiodj+buildbot
  2016-01-07  4:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-07  3:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b900245c3b92fc460a3f7fa17d14eb08f9ab4c76 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b900245c3b92fc460a3f7fa17d14eb08f9ab4c76

sim: config: drop use of __DATE__/__TIME__

These don't add a whole lot of useful info, and people don't like them as
it makes builds unreproducible, so just drop them.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes
@ 2016-01-06 18:52 sergiodj+buildbot
  2016-01-06 19:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b31e4803316aa0635a6f9beaeceea3e18dbbe459 ***

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

MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes

	include/
	* opcode/mips.h: Add a summary of MIPS16 operand codes.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix gdb.python/py-infthread.exp test message typo
@ 2016-01-06 11:46 sergiodj+buildbot
  2016-01-06 12:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-06 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79bc59cb349fdbb8d3fa81804eb121af3c340c22 ***

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

Fix gdb.python/py-infthread.exp test message typo

gdb/testsuite/ChangeLog:
2016-01-06  Pedro Alves  <palves@redhat.com>

	* gdb.python/py-infthread.exp: Fix typo.  Expect t0.num to be 1.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly
@ 2016-01-05 23:03 sergiodj+buildbot
  2016-01-06  3:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 23:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b36c1ccb1feb678f7279b4a8d66c0125d4295078 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b36c1ccb1feb678f7279b4a8d66c0125d4295078

libiberty: {count,dup,write}argv: constify argv input slightly

Would be more useful if we could use "const char * const *", but there's
a long standing bug where gcc warns about incompatible pointers when you
try to pass in "char **".  We can at least constify the array itself as
gcc will not warn in that case.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function
@ 2016-01-05 22:29 sergiodj+buildbot
  2016-01-06  0:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-05 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bec0ef03e91506caf60d8842786b29c2d2ff049 ***

Author: Patrick Palka <patrick@parcs.ath.cx>
Branch: master
Commit: 4bec0ef03e91506caf60d8842786b29c2d2ff049

libiberty: Tweak the documentation of libiberty's xcrc32 function

In some places the xcrc32 documentation refers to GDB's own crc32
implementation, but GDB no longer has its own crc32 implementation.
It now uses libiberty's xcrc32 throughout.  So this patch removes
these references to GDB's now-nonexistent crc32 implementation.

Also, there appears to be a bug in the table-generation program embedded
within the documentation.  When the variable "int i" is >= 128, the
computation "i << 24" shifts a one bit into the sign bit (assuming a
32-bit int), which is UB.  To avoid this UB, I think it is sufficient to
make the induction variables i and j have type unsigned int.  This bug
seems latent, however.  I ran the program before and after this change
and the table output is the same.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: parse_args: polish getopt error message
@ 2016-01-04 11:04 sergiodj+buildbot
  2016-01-04 12:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-04 11:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d7d784e23b5b2f8c7e28ece1bdb73b58199f16f ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8d7d784e23b5b2f8c7e28ece1bdb73b58199f16f

sim: parse_args: polish getopt error message

The cris sim hit a few failures after the recent getopt logic, and the
expected output showed a few ways we can improve things to better match
other utils.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] btrace: do not return out of TRY/CATCH
@ 2016-01-04  8:52 sergiodj+buildbot
  2016-01-04  9:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43368e1d9ab8437079001f7a5f6ae2241acaece3 ***

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

btrace: do not return out of TRY/CATCH

In btrace_pt_readmem_callback, we read memory inside TRY/CATCH and return in
case of an error return value.  This corrupts the cleanup chain, which
eventually results in a SEGV when doing or discarding cleanups later on.

gdb/
	* btrace.c (btrace_pt_readmem_callback): Do not return in TRY/CATCH.

testsuite/
	* gdb.btrace/dlopen.exp: New.
	* gdb.btrace/dlopen.c: New.
	* gdb.btrace/dlopen-dso.c: New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: parse_args: display getopt error ourselves
@ 2016-01-04  3:17 sergiodj+buildbot
  2016-01-04  4:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77cf2ef5dc9099501529151921a73be904757466 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 77cf2ef5dc9099501529151921a73be904757466

sim: parse_args: display getopt error ourselves

Fix a long standing todo where we let getopt write directly to stderr
when an invalid option is passed.  Use the sim io funcs instead as they
go through the filtered callbacks that gdb wants.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: TODO: move to wiki
@ 2016-01-04  1:04 sergiodj+buildbot
  2016-01-04  2:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-04  1:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3726f72c654ab357be5b79c78f238da7a869f9a3 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3726f72c654ab357be5b79c78f238da7a869f9a3

sim: TODO: move to wiki

We're maintaining development docs in the wiki now:
	https://sourceware.org/gdb/wiki/Sim/TODO


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: clean up some more device detritus
@ 2016-01-03  9:56 sergiodj+buildbot
  2016-01-03 11:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-03  9:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61971b86bb897dc333fccffb7518056c83b99f45 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 61971b86bb897dc333fccffb7518056c83b99f45

sim: clean up some more device detritus

Clean up some more remains of WITH_DEVICES that escaped notice.

We also clean up GETTWI/SETTWI defines in a few ports where they
were copied & pasted and are unused as they happen to be near the
device code.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: cris: use standard output helpers
@ 2016-01-02 19:11 sergiodj+buildbot
  2016-01-02 19:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-02 19:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3fbb288afd9071523b61b3222869cfed0f95ab8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: b3fbb288afd9071523b61b3222869cfed0f95ab8

sim: cris: use standard output helpers

The sim-io module provides output helpers, so no need to define local
ones anymore.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: iq2000/m32r/lm32/sh64: delete dead option code
@ 2016-01-02 16:02 sergiodj+buildbot
  2016-01-02 16:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-02 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027e73b217ec5ed334015b5484ff8d281258b6bb ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 027e73b217ec5ed334015b5484ff8d281258b6bb

sim: iq2000/m32r/lm32/sh64: delete dead option code

The iq2000/m32r/sh64 option parsing logic appears to have always been
dead.  At least iq2000/sh64 are simply copy & paste rot from m32r.

The lm32 option parsing hack here hasn't been needed for a while -- this
was fixed back in commit 11409fac6b95d71a92848a4499b02d60a4f4c5bb in the
common code.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Copyright update for binutils
@ 2016-01-01 12:44 sergiodj+buildbot
  2016-01-01 13:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-01 12:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f2750feaf2827ef8a1a0a5b2f90c1e9a6cabbd1 ***

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

Copyright update for binutils


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] GDB copyright headers update after running GDB's copyright.py script.
@ 2016-01-01  4:56 sergiodj+buildbot
  2016-01-01  6:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2016-01-01  4:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 618f726fcb851883a0094aa7fa17003889b7189f ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 618f726fcb851883a0094aa7fa17003889b7189f

GDB copyright headers update after running GDB's copyright.py script.

gdb/ChangeLog:

        Update year range in copyright notice of all files.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: m68hc11: fix default endian
@ 2015-12-31  4:59 sergiodj+buildbot
  2015-12-31  5:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-31  4:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e26d677a240d3b495b7c565006d75646a15ed53 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8e26d677a240d3b495b7c565006d75646a15ed53

sim: m68hc11: fix default endian

The previous commit here set the default to little instead of big.
A typo lost when reviewing the different targets in parallel.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: cris/m68hc11: move default endian/alignment to configure
@ 2015-12-31  2:11 sergiodj+buildbot
  2015-12-31  2:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-31  2:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eca4255a1a6c3603e05c4f3ca9c0849f529657c3 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: eca4255a1a6c3603e05c4f3ca9c0849f529657c3

sim: cris/m68hc11: move default endian/alignment to configure


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: h8300: simplify h8300_reg_{fetch,store} funcs
@ 2015-12-30 11:14 sergiodj+buildbot
  2015-12-30 15:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-30 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a2757ac7e849aa35fc519ddfcc8688a46b60448 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 2a2757ac7e849aa35fc519ddfcc8688a46b60448

sim: h8300: simplify h8300_reg_{fetch,store} funcs

We can leverage the cpu->regs array rather than going through the
function helpers to get nice compact code.

Further, fix up the return values: return -1 when we can't find a
register (and let the caller write out warnings), return 2/4 when
we actually write out that amount, and handle the zero reg.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: simplify STATE_MY_NAME setup
@ 2015-12-30  9:52 sergiodj+buildbot
  2015-12-30 12:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9950eccba15155dda9ef8025a5a1685dd9db53b7 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 9950eccba15155dda9ef8025a5a1685dd9db53b7

sim: simplify STATE_MY_NAME setup

No point in writing basename ourselves when libiberty provides one.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: arm/d10v/h8300/m68hc11/microblaze/mips/mn10300/moxie/sh/v850: convert to common sim_{fetch, store}_register
@ 2015-12-30  8:57 sergiodj+buildbot
  2015-12-30 11:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  8:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e1211e55062594679697d2175b7ea77dad173823 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: e1211e55062594679697d2175b7ea77dad173823

sim: arm/d10v/h8300/m68hc11/microblaze/mips/mn10300/moxie/sh/v850: convert to common sim_{fetch,store}_register


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: h8300: drop unused inst.h
@ 2015-12-30  8:41 sergiodj+buildbot
  2015-12-30  8:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-30  8:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2089a69c164c789bcfd06b5eb9e0878f5520e13 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: f2089a69c164c789bcfd06b5eb9e0878f5520e13

sim: h8300: drop unused inst.h

We can also drop the compile.o rule since the common dep generation
logic takes care of this for us.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: unify sim-hload
@ 2015-12-27  6:09 sergiodj+buildbot
  2015-12-27  6:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-27  6:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e744ef887c1e879052cb30783638807190275f8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 5e744ef887c1e879052cb30783638807190275f8

sim: unify sim-hload

Pretty much all targets are using this module already, so add it to the
common list of objects.  The only oddball out here is cris and that's
because it supports loading via an offset for all the phdrs.  We drop
support for that.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: bfin: push down mmr address/size checks
@ 2015-12-27  0:20 sergiodj+buildbot
  2015-12-27  2:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-27  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 466b619e95908dc073b78413f0d0d0b1cb97e4b5 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 466b619e95908dc073b78413f0d0d0b1cb97e4b5

sim: bfin: push down mmr address/size checks

The bfin port is using the WITH_DEVICES framework for two reasons:
- get access to the cpu making the request (if available)
- check the alignment & size for core & system MMRs

We addressed the first part with commit dea10706e9159ba6e94eab4c25010f3,
and we handle the second part with this commit.  Arguably this is more
correct too because trying to do bad reads/writes directly (when devices
support is disabled) often results in bad memory accesses.

As part of this clean up, we also adjust all of the existing logic that
would reject invalid accesses: the code was relying on the checks never
returning, but that's not the case when things like gdb (via the user's
commands) are making the requests.  Thus we'd still end up with bad mem
accesses, or sometimes gdb being hung due to while(1) loops.

Now we can connect (most of) these models into any address and have them
work correctly.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: sim-core: pass down cpu to hw accesses when available
@ 2015-12-26 19:56 sergiodj+buildbot
  2015-12-26 21:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 19:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dea10706e9159ba6e94eab4c25010f3006d033a0 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: dea10706e9159ba6e94eab4c25010f3006d033a0

sim: sim-core: pass down cpu to hw accesses when available

The bfin port has been using the device callback largely so it could be
passed the cpu when available.  Add this logic to the common core code
so all ports get access to the active cpu.

The semantics of these buffer functions are changed slightly in that
errors halt the engine synchronously rather than returning the length
to the caller.  We'll probably adjust this in a follow up commit.

The bfin code isn't updated just yet as it has a bit more logic in the
device layer that needs to be unwound at which point we can delete it
entirely.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: standardize sim_create_inferior handling of argv a bit more
@ 2015-12-26 12:29 sergiodj+buildbot
  2015-12-26 18:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-26 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e9672991e9346d5c2cb9cd33e30fb3e573f88b8 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 0e9672991e9346d5c2cb9cd33e30fb3e573f88b8

sim: standardize sim_create_inferior handling of argv a bit more

For targets that process argv in sim_create_inferior, improve the code:
- provide more details in the comment
- make the check for when to re-init more robust
- clean out legacy sim_copy_argv code

This will be cleaned up more in the future when we have a common inferior
creation function, but at least help new ports get it right until then.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: cris: clean up rvdummy a bit
@ 2015-12-25 11:46 sergiodj+buildbot
  2015-12-26 13:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13e49fd6364e94625985b9eb15da5b1decd6a196 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 13e49fd6364e94625985b9eb15da5b1decd6a196

sim: cris: clean up rvdummy a bit

This fixes a few warnings when compiling the rvdummy tool.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: drop WITH_ENGINE define
@ 2015-12-25 10:01 sergiodj+buildbot
  2015-12-26 10:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25 10:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf59f47ebeccf4ea82b6c529c882644e4c445323 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cf59f47ebeccf4ea82b6c529c882644e4c445323

sim: drop WITH_ENGINE define

We enable this everywhere already, and all new ports should use the
engine logic, so no point in making it an option to disable.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: move MACH/MODEL types into SIM_xxx namespace
@ 2015-12-25  9:35 sergiodj+buildbot
  2015-12-26  8:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  9:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a0ebee658862bec66191df192c1d3b09bf0c943 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8a0ebee658862bec66191df192c1d3b09bf0c943

sim: move MACH/MODEL types into SIM_xxx namespace

The "MACH" and "MODEL" names are a bit generic and collide with symbols
used by other sections of code (like h8300's opcodes).  Since these are
sim-specific types, they really should have a "SIM_" prefix.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: arm: delete unused code
@ 2015-12-25  8:19 sergiodj+buildbot
  2015-12-26  5:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  8:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 91d6df784db745df2b0a6827de8306246083bc94 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 91d6df784db745df2b0a6827de8306246083bc94

sim: arm: delete unused code

These vestiges of the 20 year old emulator are just getting in the way.
Punt all the dead code we either don't compile or don't use.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: move WITH_SCACHE_PBB to sim-main.h
@ 2015-12-25  7:53 sergiodj+buildbot
  2015-12-26  1:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  7:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0c1b768b4f42c631547643ec01b020108c0ef8e ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: f0c1b768b4f42c631547643ec01b020108c0ef8e

sim: move WITH_SCACHE_PBB to sim-main.h

This helps us break up tconfig.h more.  Any file using this define should
be pulling in sim-main.h already, so things should continue working.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: delete old breakpoint code
@ 2015-12-25  2:16 sergiodj+buildbot
  2015-12-25 17:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  2:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cec19744887931294e9d4a1dfa4fa8bd42e57ae5 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: cec19744887931294e9d4a1dfa4fa8bd42e57ae5

sim: delete old breakpoint code

This code relies on the old sim-break module, but that was deleted in 2003.
The module only existed for gdb to tell the sim to set breakpoints on its
behalf, but then that logic was abandoned in favor of gdb knowing all about
proper breakpoints (since it does already for non-sim targets).  Some dead
code lived on in the older ports though -- clean it up now.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_FLATMEM support
@ 2015-12-25  1:25 sergiodj+buildbot
  2015-12-25 14:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  1:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3cabaf66d6ec7343bd3badc5c44c2ddd06221913 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 3cabaf66d6ec7343bd3badc5c44c2ddd06221913

sim: delete SIM_HAVE_FLATMEM support

No target has used this, and it's a cheap hack in place in using the
common memory module.  We want everyone using that though, so drop
support for flatmem entirely.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] sim: delete SIM_HAVE_SIMCACHE
@ 2015-12-25  0:34 sergiodj+buildbot
  2015-12-25  1:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-25  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8abe6c668e9336418277e64983587f121c8534e6 ***

Author: Mike Frysinger <vapier@gentoo.org>
Branch: master
Commit: 8abe6c668e9336418277e64983587f121c8534e6

sim: delete SIM_HAVE_SIMCACHE

This was used by the old run interface, but we punted that awhile ago,
so drop this define too.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Consolidate Thumb-1/Thumb-2 ISA detection
@ 2015-12-24  9:44 sergiodj+buildbot
  2015-12-24 10:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  9:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc289b0a832c536a2ec324634cb420f39b212696 ***

Author: Thomas Preud'homme <thomas.preudhomme@arm.com>
Branch: master
Commit: fc289b0a832c536a2ec324634cb420f39b212696

Consolidate Thumb-1/Thumb-2 ISA detection

2015-12-24  Thomas Preud'homme  <thomas.preudhomme@arm.com>

gas/
    * config/tc-arm.c (move_or_literal_pool): Check mov.w, mvm and movw
    availability against arm_ext_v6t2 instead of checking arm_arch_t2,
    fixing comments along the way.
    (handle_it_state): Check arm_ext_v6t2 instead of arm_arch_t2 to
    generate IT instruction.
    (t1_isa_t32_only_insn): New function.
    (md_assemble): Use above new function to check for invalid wide
    instruction for CPU Thumb ISA and to determine what Thumb extension
    bit is necessary for that instruction.
    (md_apply_fix): Use arm_ext_v6t2 instead of arm_arch_t2 to decide if
    branch is out of range.

include/opcode/
    * arm.h (ARM_ARCH_THUMB2): Add comment explaining its meaning and
    remove extension bit not including any Thumb-2 instruction.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [testsuite/Ada] stop using project files when building test programs
@ 2015-12-24  5:38 sergiodj+buildbot
  2015-12-24  5:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-24  5:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab8314b3d99625c9a2125d39f4f3e74bf9e49cce ***

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

[testsuite/Ada] stop using project files when building test programs

The current approach when building Ada programs for testing is
based on the use of a project file (testsuite/gdb.ada/gnat_ada.gpr).
To do that, we pass a number of additional arguments to target_compile,
one of them being the project file (via "-P/path/to/gnat_ada.gpr").
This used to work well-enough, but AdaCore is currently working towards
removing project-file support from gnatmake (the prefered tool for
using project files is gprbuild). So, we need to either switch
the compilation to gprbuild, or stop using project files.

First, using gprbuild is not always what users will be using to
build their applications. So having the option of using gnatmake
provides more flexibility towards exactly reproducing past bugs.
If we ever need a testcase that requires the use of gprbuild, then
I believe support for a new target needs to be added to dejagnu's
target_compile.

Also, the only real reason behind using a project file in the first
place is that we wanted to make it easy to specify the directory
where all compilation artifacts get stored. This is a consequence
of the organization choice we made for gdb.ada to keep each testcase
well organized. It is very easy to achieve that goal without using
project files.

This is therefore what this patch does: It change gdb_compile_ada
to build any program using gnatmake without using a project file
(by temporarily changing the current working directory).

There is a small (beneficial) side-effect; in the situation where
GDB is built in-tree, gnatmake is called as...

        % gnatmake [...] unit.adb

... which means that the debugging info in unit.o will say contain
a filename whose name is 'unit.adb', rather than '/path/to/unit.adb'.
This also better matches what users might typically do. But the side-
effect is that the unit name in the GDB output is not always a full
path. This patch tweaks a couple of testcases to make the path part
optional.

gdb/testsuite:

        * lib/ada.exp (target_compile_ada_from_dir): New function.
        (gdb_compile_ada): Reimplement avoiding the use of project files.
        * gdb.ada/gnat_ada.gpr: Delete.
        * gdb.ada/cond_lang.exp: Adjust test to make path before
        filename optional.
        * gdb.ada/small_reg_param.exp: Likewise.

Tested on x86_64-linux, with both in-tree and out-of-tree builds.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove HP-UX reference in foll-vfork.exp
@ 2015-12-22 16:10 sergiodj+buildbot
  2015-12-22 21:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe33faff35a8ee19db823149e764e3373e603bb9 ***

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

Remove HP-UX reference in foll-vfork.exp

One more I just found.

Tested with native, native-gdbserver and native-extended-gdbserver on
Linux.

gdb/testsuite/ChangeLog:

	* gdb.base/foll-vork.exp: Remove HP-UX special case.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [lynxos] gdbserver hangs when killing inferior from GDB
@ 2015-12-22 15:50 sergiodj+buildbot
  2015-12-22 19:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4abd5ed2221c826bcb843794286777452de5c50b ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 4abd5ed2221c826bcb843794286777452de5c50b

[lynxos] gdbserver hangs when killing inferior from GDB

With any program under GDBserver control on LynxOS, killing
the program from the debugger (using the "kill" command) causes
GDBserver to properly kill the inferior but GDBserver then hangs.

This change of behavior occured after the following change was
applied:

    commit f0ea042932e6922c90df3fd0001497d287b97677
    Date:   Mon Nov 30 16:05:27 2015 +0000
    Subject: gdbserver: don't exit until GDB disconnects

One of the changes introduced by the commit above is that
process_serial_event no longer calls exit after handling
the vKill packet. Instead, what happens is that we wait
until captured_main finds that we no longer have any inferior
to debug, at which point it throws_quit. This (normal) exception
is then expected to propagate all the way to the exception handle
in function "main", which calls exit.

However, before the exception gets propagated, the cleanups
are first executed, and one of the cleanups in question is
detach_or_kill_for_exit_cleanup, which was put in place by
captured_main. detach_or_kill_for_exit_cleanup is basically
a wrapper around detach_or_kill_for_exit, which iterates
over all inferiors, and kills them all.

In our case, we have only one inferior, which we have already
killed during the handling for the "vKill" packet. Unfortunately,
we did not properly clean our internal data for that inferior up,
and so detach_or_kill_for_exit thinks that we still have one inferior,
and therefore tries to kill it. This results in lynx_kill being
called, doing the following:

    lynx_ptrace (PTRACE_KILL, ptid, 0, 0, 0);
    lynx_wait (ptid, &status, 0);
    the_target->mourn (process);

The hang is caused by the call to lynx_wait, which waits for
an event from a process which does not exist...

This patch fixes the issue by enhancing lynx_mourn to clean
the threads and process list up.

gdb/gdbserver/ChangeLog:

        * lynx-low.c (lynx_delete_thread_callback): New function.
        (lynx_mourn): Properly delete our process and all of its
        threads.  Remove call to clear_inferiors.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [win32] cannot automatically find executable file [...] warning at GDB startup
@ 2015-12-22 15:35 sergiodj+buildbot
  2015-12-22 16:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-22 15:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aec47d1d54be415050bbd3ccb93c0157d60ed92d ***

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

[win32] cannot automatically find executable file [...] warning at GDB startup

The following change...

    commit 43499ea30db2a866412c86952c7e1d7b158d806f
    Date:   Tue Nov 17 15:17:44 2015 +0000
    Subject: [C++/mingw] windows-nat.c casts

... causes a small regression in GDB, where we get the following
warning at startup:

    % gdb
    C:\[...]\gdb.exe: warning: cannot automatically find executable file or library to read symbols.
    Use "file" or "dll" command to load executable/libraries directly.
    GNU gdb (GDB) 7.10.50.20151218-cvs (with AdaCore local changes)
    [...]
    (gdb)

The warning comes from _initialize_loadable which tries to dynamically
load some symbols from kernel32.dll and psapi.dll, and in particular:

  hm = LoadLibrary ("psapi.dll");
  if (hm)
    {
      GPA (hm, EnumProcessModules);
      GPA (hm, GetModuleInformation);
      GPA (hm, GetModuleFileNameEx);
    }

The problem is that the new GPA macro assumes that the name of
the variable we use to point to the function, and the name of
its associated symbol are the same. This is mostly the case,
except for GetModuleFileNameEx, where the name is provided by
the GetModuleFileNameEx_name macro (defined differently depending
on whether we are on cygwin or not). As a result, the dynamic
resolution for GetModuleFileNameEx returns NULL, and we trip
the following check which leads to the warning:

  if (!EnumProcessModules || !GetModuleInformation || !GetModuleFileNameEx)
    {
      [...]
      warning(_("[...]"));
    }

This patch fixes the problem by calling GetProcAddress directly,
rather than through the GPA macro, but in a way which hopefully
avoids the C++ compilation warning that the previous patch was
trying to get rid of.

gdb/ChangeLog:

	* windows-nat.c (_initialize_loadable): Fix computing of
	GetModuleFileNameEx.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove dead code in testsuite
@ 2015-12-21 19:50 sergiodj+buildbot
  2015-12-21 20:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 19:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10125099f09197b325c7e0e7f2af6d3c04f929a6 ***

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

Remove dead code in testsuite

This patch removes cases from the testsuite that are not posssibly used.  The
messages "Catch of * not yet implemented" were removed here:

https://www.sourceware.org/ml/gdb-patches/2004-01/msg00679.html

I changed the regexp at the same time to match the string more closely.

gdb/testsuite/ChangeLog:

	* gdb.base/break.exp: Remove dead code.
	* gdb.base/sepdebug.exp: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove references to HP CC/aCC compiler from testsuite
@ 2015-12-21 16:34 sergiodj+buildbot
  2015-12-21 16:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6304613bf0bb1c188bed30eb3df6e3e154b4196 ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: b6304613bf0bb1c188bed30eb3df6e3e154b4196

Remove references to HP CC/aCC compiler from testsuite

The HP CC/aCC compiler is exclusive to HP-UX, for which support has been
explicitly removed.  Therefore, It does not make sense to keep tests
for these compilers' quirks.

gdb/testsuite/ChangeLog:

	* gdb.base/break.exp: Remove references to HP CC/aCC compilers.
	* gdb.base/call-ar-st.exp: Likewise.
	* gdb.base/callfuncs.exp: Likewise.
	* gdb.base/condbreak.exp: Likewise.
	* gdb.base/constvars.exp: Likewise.
	* gdb.base/hbreak2.exp: Likewise.
	* gdb.base/langs.exp: Likewise.
	* gdb.base/list.exp: Likewise.
	* gdb.base/long_long.exp: Likewise.
	* gdb.base/ptype.exp: Likewise.
	* gdb.base/scope.exp: Likewise.
	* gdb.base/signals.exp: Likewise.
	* gdb.base/so-impl-ld.exp: Likewise.
	* gdb.base/varargs.exp: Likewise.
	* gdb.base/volatile.exp: Likewise.
	* gdb.base/whatis.exp: Likewise.
	* gdb.cp/cplusfuncs.exp: Likewise.
	* gdb.cp/inherit.exp: Likewise.
	* gdb.cp/local.exp: Likewise.
	* gdb.cp/member-ptr.exp: Likewise.
	* gdb.cp/method.exp: Likewise.
	* gdb.cp/overload.exp: Likewise.
	* gdb.cp/templates.exp: Likewise.
	* gdb.stabs/weird.exp: Likewise.
	* lib/compiler.c: Likewise.
	* lib/compiler.cc: Likewise.
	* lib/cp-support.exp: Likewise.
	* lib/gdb.exp: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Use arm_eabi_breakpoint on aarch32
@ 2015-12-21 14:08 sergiodj+buildbot
  2015-12-21 14:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-21 14:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35adc03f3787405297259a1706608bdeaab4fda9 ***

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

Use arm_eabi_breakpoint on aarch32

This patch is to get b37a6290 back again, which was removed by
d9311bfa by mistake.

gdb/gdbserver:

2015-12-21  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch32-low.h [__aarch64__]: Use arm_abi_breakpoint
	arm breakpoint.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix ARI warning in gdb/arch/arm-get-next-pcs.c
@ 2015-12-19  3:44 sergiodj+buildbot
  2015-12-20  8:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-19  3:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7826da33d884c21bd1a036e71fe1002fae76ce4 ***

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

Fix ARI warning in gdb/arch/arm-get-next-pcs.c

gdb/ChangeLog:

        * arch/arm-get-next-pcs.c (arm_get_next_pcs_raw): Remove trailing
        newline at end of error message.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add documentation to gdb_compile
@ 2015-12-18 18:50 sergiodj+buildbot
  2015-12-20  4:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aff9c0f8ab32e4f2f7ff9700afe84a61d23a08c6 ***

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

Add documentation to gdb_compile

This patch adds some documentation to gdb_compile.  It describes the
various options that can influence compilation.  Most of them are
handled by DejaGnu, but are not really documented anywhere, so I think
it's good to have a quick reference.  Not all possible options are
described, that would add way to much noise.  I chose those that I think
are relevant in the context of writing a test case.

gdb/testsuite/ChangeLog:

	* lib/gdb.exp (gdb_compile): Add function doc.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Share regcache function regcache_raw_read_unsigned
@ 2015-12-18 17:35 sergiodj+buildbot
  2015-12-20  0:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68ce205943e0821eacd8028881ced3607cc83c0d ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 68ce205943e0821eacd8028881ced3607cc83c0d

Share regcache function regcache_raw_read_unsigned

This patch is in preparation for software single step support on ARM in
GDBServer. It adds a new shared function regcache_raw_read_unsigned and
regcache_raw_get_unsigned so that GDB and GDBServer can use the same call
to fetch a raw register into an integer.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/ChangeLog:

	* Makefile.in (SFILES): Append common/common-regcache.c.
	(COMMON_OBS): Append common/common-regcache.o.
	(common-regcache.o): New rule.
	* common/common-regcache.h (register_status) New enum.
	(regcache_raw_read_unsigned): New declaration.
	* common/common-regcache.c: New file.
	* regcache.h (enum register_status): Move to common-regcache.h.
	(regcache_raw_read_unsigned): Likewise.
	(regcache_raw_get_unsigned): Likewise.

gdb/gdbserver/ChangeLog:

	* Makefile.in (SFILES): Append common/common-regcache.c.
	(OBS): Append common-regcache.o.
	(common-regcache.o): New rule.
	* regcache.c (init_register_cache): Initialize cache to
	REG_UNAVAILABLE.
	(regcache_raw_read_unsigned): New function.
	* regcache.h (REG_UNAVAILABLE, REG_VALID): Replaced by shared
	register_status enum.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Share some ARM target dependent code from GDB with GDBServer
@ 2015-12-18 17:01 sergiodj+buildbot
  2015-12-19 22:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-18 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cba7e83fda349cbf423fab274f5b8677d8148947 ***

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

Share some ARM target dependent code from GDB with GDBServer

This patch is in preparation for software single stepping support on ARM
it shares some functions and definitions that will be needed.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

Not tested: wince/bsd build.

gdb/ChangeLog:

	* arch/arm.c (bitcount): Move from arm-tdep.c.
	(condition_true): Likewise.
	* arch/arm.h (Instruction Definitions): Move form arm-tdep.h.
	(condition_true): Move defenition from arm-tdep.h.
	(bitcount): Likewise.
	* arm-tdep.c (condition_true): Move to arch/arm.c.
	(bitcount): Likewise.
	* arm-tdep.h (Instruction Definitions): Move to arch/arm.h.
	* arm-wince-tdep.c: Include arch/arm.h.
	* armnbsd-tdep.c: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Skip gdb.base/gdbinit-history.exp on remote hosts.
@ 2015-12-17 18:36 sergiodj+buildbot
  2015-12-19  3:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d978e177217d8e9da8648498f0592b5cd885e69 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 5d978e177217d8e9da8648498f0592b5cd885e69

Skip gdb.base/gdbinit-history.exp on remote hosts.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/gdbinit-history.exp: Skip for remote-host testing.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 11/14] Add support for the 2H vector type.
@ 2015-12-17 15:02 sergiodj+buildbot
  2015-12-18 15:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 15:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3067d3b96cfb88e86acf94d2aa1575cff0e0110f ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 3067d3b96cfb88e86acf94d2aa1575cff0e0110f

[AArch64][PATCH 11/14] Add support for the 2H vector type.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. The FP16 additions to the
scalar pairwise group introduce a new vector type, 2H. This patch adds
support for this vector type to binutils.

The patch adds a new operand qualifier to the enum
aarch64.h:aarch64_opnd_qualifier. This interferes with the calculation
used by aarch64-dis.c:get_vreg_qualifier_from_value, called when
decoding an instruction. Since the new vector type is only used in FP16
scalar pairwise instructions which do not require the function, this
patch adjusts the function to ignore the new qualifier.

gas/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (parse_neon_type_for_operand): Adjust to
	take into account new vector type 2H.
	(vectype_to_qualifier): Likewise.

include/opcode/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (enum aarch64_opnd_qualifier): Add
	AARCH64_OPND_QLF_V_2H.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.coM>

	* aarch64-dis.c (get_vreg_qualifier_from_value): Update comment
	and adjust calculation to ignore qualifier for type 2H.
	* aarch64-opc.c (aarch64_opnd_qualifier): Add "2H".

Change-Id: Idf9a3694732962c80fde04f08c7304de9164f126


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [Patch ARM] Fix build attributes for armv8-a in case of assembler files that contain no directives.
@ 2015-12-17 11:45 sergiodj+buildbot
  2015-12-19 15:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 11:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10c9892b66d56de0aab3fbaec3d59a0304dc0a21 ***

Author: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Branch: master
Commit: 10c9892b66d56de0aab3fbaec3d59a0304dc0a21

[Patch ARM] Fix build attributes for armv8-a in case of assembler files that contain no directives.

There is currently a problem in the way in which we produce
build attributes for simple assembler files that have armv8-a
instructions.

In these case we need to generate TAG_ISA_THUMB_Use to be Thumb-2
and set the architecture profile to be 'A' rather than not
setting architecture profile to be 'A' and setting TAG_ISA_THUMB_Use
to be Thumb-1.

This is a pre-requisite for any v8-m patches that have been posted.
arm-none-eabi gas testsuite run. no regressions.

2015-12-17  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

	* gas/config/tc-arm.c (aeabi_set_public_attributes): Adjust
	TAG_ARCH_profile for armv8-a.
	* gas/testsuite/gas/arm/armv8a-automatic-hlt.d: New test.
	* gas/testsuite/gas/arm/armv8a-automatic-hlt.s: New test.
	* gas/testsuite/gas/arm/armv8a-automatic-lda.d: New test.
	* gas/testsuite/gas/arm/armv8a-automatic-lda.s: New test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [ARM] Add support for thumb1 pcrop relocations.
@ 2015-12-17 10:05 sergiodj+buildbot
  2015-12-19 12:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17 10:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 72d98d16ed09584660d0cbb759d90f8dfeef2343 ***

Author: Mickael Guene <mickael.guene@st.com>
Branch: master
Commit: 72d98d16ed09584660d0cbb759d90f8dfeef2343

[ARM] Add support for thumb1 pcrop relocations.

To support thumb1 execute-only code we need to support four new
relocations (R_ARM_THM_ALU_ABS_G0_NC, R_ARM_THM_ALU_ABS_G1_NC,
R_ARM_THM_ALU_ABS_G2_NC and  R_ARM_THM_ALU_ABS_G3_NC).
These relocations allow the static linker to finalize construction
of symbol address.
Typical sequence of code to get address of the symbol foo is then
the following :
	movs	r3, #:upper8_15:#foo
	lsls	r3, #8
	adds	r3, #:upper0_7:#foo
	lsls	r3, #8
	adds	r3, #:lower8_15:#foo
	lsls	r3, #8
	adds	r3, #:lower0_7:#foo
This will give following sequence of text and relocations after
assembly :
   4:	2300      	movs	r3, #0
			4: R_ARM_THM_ALU_ABS_G3_NC	foo
   6:	021b      	lsls	r3, r3, #8
   8:	3300      	adds	r3, #0
			8: R_ARM_THM_ALU_ABS_G2_NC	foo
   a:	021b      	lsls	r3, r3, #8
   c:	3300      	adds	r3, #0
			c: R_ARM_THM_ALU_ABS_G1_NC	foo
   e:	021b      	lsls	r3, r3, #8
  10:	3300      	adds	r3, #0
			10: R_ARM_THM_ALU_ABS_G0_NC	foo


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Extend help text for 'list' command.
@ 2015-12-17  9:52 sergiodj+buildbot
  2015-12-18  0:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fdd372d502d241eb42032844836ae031830237a ***

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

gdb: Extend help text for 'list' command.

Reference the 'listsize' setting in the help text for the 'list' command
to help users find this setting.

gdb/ChangeLog:

	* cli/cli-cmds.c (_initialize_cli_cmds): Extend help text for
	'list' command.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Tweak gdb.trace/ftrace.exp for aarch64
@ 2015-12-17  9:14 sergiodj+buildbot
  2015-12-19 10:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  9:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a22279dd83da7a0dd2b496c92dc2522427f74e37 ***

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

Tweak gdb.trace/ftrace.exp for aarch64

Some tests are skipped on aarch64 unexpectedly because arg0exp isn't
set.  This patch is to set arg0exp to "$x0" for aarch64.

gdb/testsuite:

2015-12-15  Yao Qi  <yao.qi@linaro.org>

	* gdb.trace/ftrace.exp: Set arg0exp to "$x0" if target
	is aarch64*-*-*.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix invalid left shift of negative value
@ 2015-12-17  8:58 sergiodj+buildbot
  2015-12-19  8:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  8:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d19cae752a7b032b8253feb4fa3b9f1dc162823 ***

Author: Dominik Vogt <vogt@linux.vnet.ibm.com>
Branch: master
Commit: 1d19cae752a7b032b8253feb4fa3b9f1dc162823

Fix invalid left shift of negative value

Fix occurrences of left-shifting negative constants in C code.

sim/arm/ChangeLog:

	* thumbemu.c (handle_T2_insn): Fix left shift of negative value.
	* armemu.c (handle_v6_insn): Likewise.

sim/avr/ChangeLog:

	* interp.c (sign_ext): Fix left shift of negative value.

sim/mips/ChangeLog:

	* micromips.igen (process_isa_mode): Fix left shift of negative
	value.

sim/msp430/ChangeLog:

	* msp430-sim.c (get_op, put_op): Fix left shift of negative value.

sim/v850/ChangeLog:

	* simops.c (v850_bins): Fix left shift of negative value.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Skip gdb.base/gdbhistsize-history.exp on remote hosts.
@ 2015-12-17  7:16 sergiodj+buildbot
  2015-12-19  2:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e763b8690ff486d9783f43ce0f4bbb7c9e81b6c ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 7e763b8690ff486d9783f43ce0f4bbb7c9e81b6c

Skip gdb.base/gdbhistsize-history.exp on remote hosts.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/gdbhistsize-history.exp: Skip for remote-host testing.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Skip tests that send ctrl-c to GDB if nointerrupts target property is set.
@ 2015-12-17  7:08 sergiodj+buildbot
  2015-12-19  0:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  7:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87a3a92c46c770e6aa2ca1209f46af16eae2c4e9 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 87a3a92c46c770e6aa2ca1209f46af16eae2c4e9

Skip tests that send ctrl-c to GDB if nointerrupts target property is set.

2015-12-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/completion.exp: Skip tests that interrupt GDB with
	ctrl-C if nointerrupts target property is set.
	* gdb.base/double-prompt-target-event-error.exp: Likewise.
	* gdb.base/paginate-after-ctrl-c-running.exp: Likewise.
	* gdb.base/paginate-bg-execution.exp: Likewise.
	* gdb.base/paginate-execution-startup.exp: Likewise.
	* gdb.base/random-signal.exp: Likewise.
	* gdb.base/range-stepping.exp: Likewise.
	* gdb.cp/annota2.exp: Likewise.
	* gdb.cp/annota3.exp: Likewise.
	* gdb.gdb/selftest.exp: Likewise.
	* gdb.threads/continue-pending-status.exp: Likewise.
	* gdb.threads/leader-exit.exp: Likewise.
	* gdb.threads/manythreads.exp: Likewise.
	* gdb.threads/pthreads.exp: Likewise.
	* gdb.threads/schedlock.exp: Likewise.
	* gdb.threads/sigthread.exp: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Target remote mode fork and exec event support
@ 2015-12-17  6:17 sergiodj+buildbot
  2015-12-18 21:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  6:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8020350c5277e056e89b0ea5e14a8d09408f7fb3 ***

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

Target remote mode fork and exec event support

This patch implements support for fork and exec events with target remote
mode Linux targets.  For such targets with Linux kernels 2.5.46 and later,
this enables follow-fork-mode, detach-on-fork and fork and exec
catchpoints.

The changes required to implement this included:

 * Don't exit from gdbserver if there are still active inferiors.

 * Allow changing the active process in remote mode.

 * Enable fork and exec events in remote mode.

 * Print "Ending remote debugging" only when disconnecting.

 * Combine remote_kill and extended_remote_kill into a single function
   that can handle the multiple inferior case for target remote.  Also,
   the same thing for remote_mourn and extended_remote_mourn.

 * Enable process-style ptids in target remote.

 * Remove restriction on multiprocess mode in target remote.

gdb/gdbserver/ChangeLog:

	* server.c (process_serial_event): Don't exit from gdbserver
	in remote mode if there are still active inferiors.

gdb/ChangeLog:

	* inferior.c (number_of_live_inferiors): New function.
	(have_live_inferiors): Use number_of_live_inferiors in place
	of duplicate code.
	* inferior.h (number_of_live_inferiors): Declare new function.
	* remote.c (set_general_process): Remove restriction on target
	remote mode.
	(remote_query_supported): Likewise.
	(remote_detach_1): Exit in target remote mode only when there
	is just one live inferior left.
	(remote_disconnect): Unpush the target directly instead of
	calling remote_mourn.
	(remote_kill): Rewrite function to handle both target remote
	and extended-remote.  Call remote_kill_k.
	(remote_kill_k): New function.
	(extended_remote_kill): Delete function.
	(remote_mourn, extended_remote_mourn): Combine functions into
	one, remote_mourn, and enable extended functionality for target
	remote.
	(remote_pid_to_str): Enable "process" style ptid string for
	target remote.
	(remote_supports_multi_process): Remove restriction on target
	remote mode.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instructions.
@ 2015-12-17  6:02 sergiodj+buildbot
  2015-12-18 18:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  6:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4fd0a9fd005ea3affe8e61f6ec82817055a3bc2b ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 4fd0a9fd005ea3affe8e61f6ec82817055a3bc2b

[AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch extends
instructions in the group Adv.SIMD Scalar Shift By Immediate to support
FP16, making this support available when +simd+fp16 is enabled.

The extended instructions are: SCVTF, FCVTZS, UCVTF and FCVTZU.

The general form for these instructions is
   <OP> <Hd>, <Hs>, #<imm>

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16: Add tests for Adv.SIMD scalar shift
	by immediate instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_SSHIFT_H): New.
	(aarch64_opcode_table): Add fp16 versions of scvtf, fcvtzs, ucvtf
	and fcvtzu to the Adv.SIMD scalar shift by immediate group.

Change-Id: I40506496f52dd96909e7344f243b38a1870df7ff


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 12/14] Support FP16 Adv.SIMD Scalar Pairwise instructions.
@ 2015-12-17  5:45 sergiodj+buildbot
  2015-12-18 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b195470dd29e8a5c8810209fb2d22c30004fe6ab ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: b195470dd29e8a5c8810209fb2d22c30004fe6ab

[AArch64][PATCH 12/14] Support FP16 Adv.SIMD Scalar Pairwise instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Adv.SIMD Scalar Pairwise, making them
available when +simd+fp16 is enabled.

The instructions added are: FMAXNMP, FADDP, FMAXP, FMINNMP and FMINP

The general form for these instructions is
   <OP> <Hd>, <V>.<T>
   where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for Adv.SIMD Scalar
	Pairwise instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_SISD_PAIR_H): New.
	(aarch64_opcode_table): Add fp16 versions of fmaxnmp, faddp,
	fmaxp, fminnmp, fminp to the Adv.SIMD scalar pairwise group.

Change-Id: I19937ede3441b66dd0f940269ece895b17d3c345


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 9/14] Support FP16 Adv.SIMD Modified Immediate instructions.
@ 2015-12-17  5:29 sergiodj+buildbot
  2015-12-18 14:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b5fc357a17d59929cf39869d19fc4eabdb7ae81 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 4b5fc357a17d59929cf39869d19fc4eabdb7ae81

[AArch64][PATCH 9/14] Support FP16 Adv.SIMD Modified Immediate instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds an FP16
instruction to the group Adv.SIMD Modified Immediate, making it
available when +simd+fp16 is enabled.

The instruction added is: FMOV.

The form of this instructions is
    <OP> <Hd>, #<imm>

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for Adv.SIMD modified immediate
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_SIMD_IMM_H): New.
	(aarch64_opcode_table): Add fp16 version of fmov to the Adv.SIMD
	modified immediate group.

Change-Id: Ic66af44c494e6a53fb1cf01c372cdc62d12643e2


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 6/14] Support FP16 Vector Indexed Element instructions.
@ 2015-12-17  5:06 sergiodj+buildbot
  2015-12-18 11:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  5:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42f23f6218262ae8488caab214b7f272c6758941 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 42f23f6218262ae8488caab214b7f272c6758941

[AArch64][PATCH 6/14] Support FP16 Vector Indexed Element instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Vector Indexed Element, making them available
when +simd+fp16 is enabled.

The instructions added are: FMLA, FMLS, FMUL and FMULX.

The general form for these instructions is
  <OP> <V>.<T>, <V>.<T>, <V>.h[<idx>]
  where T is 4h or 8h

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for vector indexed element
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_ELEMENT_FP_H): New.
	(aarch64_opcode_table): Add fp16 versions of fmla, fmls, fmul and
	fmulx to the vector indexed element group.

Change-Id: Ib70cd4eaa6ea2938f84ac41f31d72644dbb0ceb4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 4/14] Support FP16 Vector Two Register Misc. instructions.
@ 2015-12-17  4:50 sergiodj+buildbot
  2015-12-18  8:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3aa142b8b04bfccef2cbc3233b565c2b3faa01a ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: f3aa142b8b04bfccef2cbc3233b565c2b3faa01a

[AArch64][PATCH 4/14] Support FP16 Vector Two Register Misc. instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Vector Two Register Misc, making them
available when +simd+fp16 is enabled.

The instructions added are: FCMGT, FCMGE, FCMEQ, FCMLE, FCMLT, FABS,
FNEG, FRINTN, FRINTA, FRINTP, FRINTM, FRINTX, FRINTZ, FRINTI, FCVTNS,
FCVTNU, FCVTPS, FCVTPU, FCVTMS, FCVTMU, FCVTZS, FCVTZU, FCVTAS, FCVTAU,
SCVTF, UCVTF, FRECPE, FRSQRTE and FSQRT.

The general form for these instructions is
  <OP> <Vd>.<T>, <Vs>.<T>
  where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: Update expected output.
	* gas/aarch64/advsimd-fp16.s: Add tests for vector two register misc.
	instructions.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_V2SAMEH): New.
	(aarch64_opcode_table): Add fp16 versions of frintn, frintm,
	fcvtns, fcvtms, fcvtas, scvtf, fcmgt, fcmeq, fcmlt, fabs, frintp,
	frintz, fcvtps, fcvtzs, frecpe, frinta, frintx, fcvtnu, fcvtmu,
	fcvtau, ucvtf, fcmge, fcmle, fneg, frinti, fcvtpu, fcvtzu, frsqrte
	and fsqrt to the vector register misc. group.

Change-Id: I0267511a7f7ea14247504d29fe4752e84c9af9ad


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 2/14] Support ARMv8.2 FP16 Vector Three Same instructions.
@ 2015-12-17  4:35 sergiodj+buildbot
  2015-12-18  6:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51d543ed936c9ea7d045ecf80030e6bc8ffff29f ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 51d543ed936c9ea7d045ecf80030e6bc8ffff29f

[AArch64][PATCH 2/14] Support ARMv8.2 FP16 Vector Three Same instructions.

ARMv8.2 adds 16-bit floating point operations as an optional extension
to floating point and Adv.SIMD support. This patch adds FP16
instructions to the group Vector Three Register Same, making them
available when +simd+fp16 is enabled.

The instructions added are: FMAXNM, FMAXNMP, FNMINNM, FMINNMP, FMLA,
FMLS, FADD, FADDP, FSUB, FABD, FMULX, FMUL, FCMEQ, FCMGE, FCMGT, FACGE,
FACGT, FMAX, FMAXP, FMIN, FMINP, FRECPS, FDIV and FRSQRTS.

The general form for these instructions is
  <OP> <Vd>.<T>, <Vs>.<T>, <Vm>.<T>
  where T is 4h or 8h.

gas/testsuite/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/advsimd-fp16.d: New.
	* gas/aarch64/advsimd-fp16.s: New.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_V3SAMEH): New.
	(aarch64_opcode_table): Add fp16 versions of fmaxnm, fmla, fadd,
	fmulx, fcmeq, fmax, frecps, fminnm, fmls, fsub, fmin, frsqrts,
	fmaxnmp, faddp, fmul, fcmge, facge, fmaxp, fdiv, fminnmp, fabd,
	fcmgt, facgt and fminp to the vector three same group.

Change-Id: I3f1c5fe82ca73f7a17fe5329cf2b0de03c94328c


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch
@ 2015-12-17  4:19 sergiodj+buildbot
  2015-12-18  4:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6351190792e586b5e80fe0efa0f254b4da0b6705 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 6351190792e586b5e80fe0efa0f254b4da0b6705

[AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch

A mistake with rebasing the ARMv8.2 AT instruction patch left this part

+  /* AT S1E1RP, AT S1E1WP.  Values are from aarch64_sys_regs_at.  */
+  if ((reg->value == CPENS (0, C7, C9, 0)
+       || reg->value == CPENS (0, C7, C9, 1))
+      && !AARCH64_CPU_HAS_FEATURE (features, AARCH64_FEATURE_V8_2))
+    return FALSE;

in aarch64_pstatefield_supported_p rather than in
aarch64_sys_ins_reg_supported_p, where it was supposed to be.

The patch adding support for id_aa64mmfr2_el1, also had the effect of
removing a conditional branch in aarch64_sys_reg_supported_p.

The effect of both of these is to suppress an error if some ARMv8.2
system registers are used with the wrong -march settings.

This patch fixes these mistakes.

opcodes/
2015-12-14  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (aarch64_sys_reg_supported_p): Add mistakenly
	removed statement.
	(aarch64_pstatefield_supported_p): Move feature checks for AT
	registers ..
	(aarch64_sys_ins_reg_supported_p): .. to here.

Change-Id: I48783d118eaaf0f3312e8b08a8340ef7af4e36a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Add an error when 'list -' reaches the start of a file.
@ 2015-12-17  3:46 sergiodj+buildbot
  2015-12-17 23:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b2464a8d39b8b787664438253b8fdf7625cac32 ***

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

gdb: Add an error when 'list -' reaches the start of a file.

When a a user uses 'list +' to list forward through a source file they
eventually reach the end of the source file.  Subsequent uses of 'list
+' result in an error message like this, that let the user know they are
at the end of the source file:

  Line number XXX out of range; FILENAME has YYY lines.

Compare this to the current behaviour of 'list -' which lists backwards
through a source file.  When the user reaches the beginning of the
source file, subsequent uses of 'list -' result in the command silently
returning.  This can be confusing if the previous uses of 'list -' have
scrolled off the users display, the user receives no reminder that the
have already seen the start of the file.

After this commit a use of 'list -' when the user has already seen the
start of a file will receive the following error:

   Already at the start of FILENAME.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Add an error when trying to use
	'-' to scan read off the start of the source file.

gdb/testsuite/ChangeLog:

	* gdb.base/list.exp (test_list_forward): Add end of file error
	test.
	(test_repeat_list_command): Add end of file error test.
	(test_list_backwards): Add beginning of file error test.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: 'list' command, tweak handling of +/- arguments.
@ 2015-12-17  3:37 sergiodj+buildbot
  2015-12-17 22:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0def019aaf79adf3add2a0559ab75bb84d72085 ***

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

gdb: 'list' command, tweak handling of +/- arguments.

There is an inconsistency with the handling of the special +/- arguments
to the list command.

For the very first time that list is used (after the inferior has
changed locations) then only the first character of the argument string
is checked, so 'list +BLAH' will operate as 'list +' and 'list -----FOO'
will operate as 'list -'.  This compares to each subsequent use of list,
where the whole argument string is checked, so 'list +BLAH' will try to
list lines of code around the function '+BLAH'.

This commit unifies the behaviour so that the whole argument string is
checked, in order to list the next 10, or previous 10 lines from a file
only 'list +' and 'list -' are now valid.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Check that the argument string is
	a single character, either '+' or '-'.

gdb/testsuite/ChangeLog:

	* gdb.base/list.exp (test_list_invalid_args): New function,
	defined, and called.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Small code restructure for list_command.
@ 2015-12-17  3:20 sergiodj+buildbot
  2015-12-17 19:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a48ce76774633e9e27dd245ba275a714b2b339f ***

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

gdb: Small code restructure for list_command.

Move handling of special +/- arguments to the list_command function
inside a single if block, this helps group all related functionality
together.  There should be no user visible changes after this commit.

gdb/ChangeLog:

	* cli/cli-cmds.c (list_command): Move all handling of +/-
	arguments into a single if block.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Make lines_to_list variable static.
@ 2015-12-17  3:07 sergiodj+buildbot
  2015-12-17 17:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  3:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f43f85715ac097b6ff4bfaed00879eb541428c1a ***

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

gdb: Make lines_to_list variable static.

Small clean up, make variable static.

gdb/ChangeLog:

	* source.c (lines_to_list): Make static.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ld -r doesn't need plugin for slim lto object
@ 2015-12-17  2:50 sergiodj+buildbot
  2015-12-17  8:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5847ba7267b6eedd4b750f5eeece3ec037a27fd ***

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

ld -r doesn't need plugin for slim lto object

Plugin isn't required on slim lto object for relocatable link.

bfd/

	PR ld/19317
	* linker.c (_bfd_generic_link_add_one_symbol): Don't complain
	plugin needed to handle slim lto object for relocatable link.

ld/testsuite/

	PR ld/19317
	* ld-plugin/lto.exp (lto_no_fat): New.
	(lto_link_tests): Add a test for PR ld/19317.
	(lto_run_tests): Likewise.
	(run_ld_link_tests): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][Patch 5/5] Add instruction PSB CSYNC
@ 2015-12-17  2:31 sergiodj+buildbot
  2015-12-17 13:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e6f4800fc01c7957d0688158385aba3bf5ce8de ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 1e6f4800fc01c7957d0688158385aba3bf5ce8de

[AArch64][Patch 5/5] Add instruction PSB CSYNC

The Statistical Profile Extension adds the instruction PSB CSYNC as an
alias for the HINT #17 instruction. This patch adds the instruction to
binutils as a HINT alias that takes an operand.

A new operand type, AARCH64_OPND_BARRIER_PSB, is added to represent the
operand to PSB. A parser for the operand type is added to the assembler
and a printer to the disassembler. The operand name "csync" is added to
the list of HINT options with HINT number #17. Encoding and decoding of
the operand is handled by the ins_hint/ext_hint functions added in the
preceding patches.

gas/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* config/tc-aarch64.c (aarch64_hint_opt_hsh): New.
	(parse_barrier_psb): New.
	(parse_operands): Add case for AARCH64_OPND_BARRIER_PSB.
	(md_begin): Set up aarch64_hint_opt_hsh.

gas/testsuite/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/system-2.d: Enable the statistical profiling
	extension.  Update the expected output.
	* gas/aarch64/system-2.s: Add tests for PSB CSYNC.
	* gas/aarch64/system.d: Update the expected output.

include/opcode/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64.h (aarch64_opnd): Add AARCH64_OPND_BARRIER_PSB.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-opc.c (aarch64_hint_options): Add "csync".
	(aarch64_print_operands): Handle AARCH64_OPND_BARRIER_PSB.
	* aarch64-tbl.h (aarch64_feature_stat_profile): New.
	(STAT_PROFILE): New.
	(aarch64_opcode_table): Add "psb".
	(AARCH64_OPERANDS): Add "BARRIER_PSB".

Change-Id: I5ffb672d26a8b15b48785478d359350a9b70ca09


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][Patch 3/5] Adjust maximum number of instruction aliases.
@ 2015-12-17  2:14 sergiodj+buildbot
  2015-12-17 11:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  2:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0f7013add6b1737e9a5e5d63cdf41ab2ebca0bf ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: a0f7013add6b1737e9a5e5d63cdf41ab2ebca0bf

[AArch64][Patch 3/5] Adjust maximum number of instruction aliases.

The Statistical Profile Extension adds the instruction PSB CSYNC as an
alias for the HINT #17 instruction. The HINT instruction currently has 8
aliases, which is the maximum number allowed. This patch raises to 16
the limit on the number of aliases an instruction can have.

opcodes/
2015-12-11  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-gen.c (find_alias_opcode): Set max_num_aliases to 16.

Change-Id: I131044bf6e0fe0940a9e7478d9bf52137748907d


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove "spaces" references from gdb.multi/base.exp
@ 2015-12-17  1:05 sergiodj+buildbot
  2015-12-17  4:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-17  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36d6fc0a3cbda55b9eb07a351c1312e369d4743f ***

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

Remove "spaces" references from gdb.multi/base.exp

I think these references to "spaces" came from the original multi-exec
submission that exposed "symbol spaces" to the user and had a
different UI, and then survived a global find/replace.

gdb/testsuite/ChangeLog:
2015-12-10  Pedro Alves  <palves@redhat.com>

	* gdb.multi/base.exp: Remove stale "spaces" references.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB
@ 2015-12-10 16:00 sergiodj+buildbot
  2015-12-10 18:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 16:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2c2a31fdb228d41ce3db62b268efea04bd39c18 ***

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

Remove support for thread events without PTRACE_EVENT_CLONE in GDB

Before, on systems that did not support PTRACE_EVENT_CLONE, both GDB and
GDBServer coordinated with libthread_db.so to insert breakpoints at magic
locations in libpthread.so, in order to break at thread creation and
thread death.

Support for thread events was removed from GDBServer as patch:
https://sourceware.org/ml/gdb-patches/2015-11/msg00466.html

This patch removes support for thread events in GDB.

No regressions found on Ubuntu 14.04 x86_64.

gdb/ChangeLog:

	* breakpoint.c (remove_thread_event_breakpoints): Remove.
	* breakpoint.h (remove_thread_event_breakpoints): Remove
	declaration.
	* linux-nat.c (in_pid_list_p): Remove.
	(lin_lwp_attach_lwp): Remove.
	* linux-nat.h (lin_lwp_attach_lwp): Remove declaration.
	* linux-thread-db.c (thread_db_use_events): Remove.
	(struct thread_db_info) <td_create_bp_addr>: Remove.
	<td_death_bp_addr>: Likewise.
	<td_ta_event_addr_p>: Likewise.
	<td_ta_set_event_p>: Likewise.
	<td_ta_clear_event_p>: Likewise.
	<td_ta_event_getmsg_p>: Likewise.
	<td_thr_event_enable_p>: Likewise.
	(attach_thread): Likewise.
	(detach_thread): Likewise.
	(have_threads_callback): Likewise.
	(have_threads): Likewise.
	(enable_thread_event): Likewise.
	(enable_thread_event_reporting): Likewise.
	(try_thread_db_load_1): Remove td_ta_event_addr, td_ta_set_event,
	td_ta_clear_event, td_ta_event_getmsg, td_thr_event_enable
	initializations.
	(try_thread_db_load_1): Remove enable_thread_event_reporting call.
	(disable_thread_event_reporting): Remove.
	(record_thread): Adapt to thread_db_use_event removal.
	(detach_thread): Remove.
	(thread_db_detach): Adapt to thread_db_use_event removal.
	(check_event): Remove.
	(thread_db_wait): Adapt to thread events support removal.
	(thread_db_mourn_inferior): Likewise.
	(find_new_threads_callback): Likewise.
	(find_new_threads_once): Likewise.
	(thread_db_update_thread_list): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdb: Handle multiple base address in debug_ranges data.
@ 2015-12-10 10:15 sergiodj+buildbot
  2015-12-10 10:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-10 10:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 28d2bfb9c3e519a3b7619bbe5d061ebe520750ef ***

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

gdb: Handle multiple base address in debug_ranges data.

It is possible to use multiple base addresses within a single address
range series, within the .debug_ranges section.  The following is a
simplified example for 32-bit addresses:

  .section ".debug_ranges"
  .4byte	0xffffffff
  .4byte	BASE_1
  .4byte	START_OFFSET_1
  .4byte	END_OFFSET_1
  .4byte	START_OFFSET_2
  .4byte	END_OFFSET_2
  .4byte	0xffffffff
  .4byte	BASE_2
  .4byte	START_OFFSET_3
  .4byte	END_OFFSET_3
  .4byte	0
  .4byte	0

In this example START/END 1 and 2 are relative to BASE_1, while
START/END 3 are relative to BASE_2.

Currently gdb does not correctly parse this DWARF, resulting in
corrupted address range information.  This commit fixes this issue, and
adds a new test to cover this case.

In order to support testing of this feature extensions were made to the
testsuite dwarf assembler, additional functionality was added to the
.debug_line generation function, and a new function for generating the
.debug_ranges section was added.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_ranges_read): Unify and fix base address
	reading code.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-ranges-base.c: New file.
	* gdb.dwarf2/dw2-ranges-base.exp: New file.
	* lib/dwarf.exp (namespace eval Dwarf): Add new variables to
	support additional line table, and debug ranges generation.
	(Dwarf::ranges): New function, generate .debug_ranges.
	(Dwarf::lines): Support generating simple line table programs.
	(Dwarf::assemble): Initialise new namespace variables.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
[parent not found: <8eab413676a0222a863f45ff606f3db69bb7afc4@gdb-build>]
* [binutils-gdb] varobj zero-padded hexadecimal format
@ 2015-12-09 13:15 sergiodj+buildbot
  2015-12-09 14:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-09 13:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c35a88f1d8399902c08a8334d3e3303df833538 ***

Author: Luis Machado <lgustavo@codesourcery.com>
Branch: master
Commit: 1c35a88f1d8399902c08a8334d3e3303df833538

varobj zero-padded hexadecimal format

This set of patches add support for the zero-padded hexadecimal format for
varobj's, defined as "zero-hexadecimal".  We currently only support regular
non-zero-padded hexadecimal.

Talking with IDE developers, they would like to have this option that is
already available to GDB's print/x commands, in the CLI, as 'z'.

gdb/ChangeLog:

2015-12-09  Luis Machado  <lgustavo@codesourcery.com>

	* gdb/mi/mi-cmd-var.c (mi_parse_format): Handle new "zero-hexadecimal"
	format.
	* gdb/varobj.c (varobj_format_string): Add "zero-hexadecimal" entry.
	(format_code): Add 'z' entry.
	(varobj_set_display_format): Handle FORMAT_ZHEXADECIMAL.
	* gdb/varobj.h (varobj_display_formats) <FORMAT_ZHEXADECIMAL>: New enum
	field.
	* NEWS: Add new note to MI changes citing the new zero-hexadecimal
	format for -var-set-format.

gdb/doc/ChangeLog:

2015-12-09  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.texinfo (GDB/MI Variable Objects): Update text to mention
	-var-set-format's new zero-hexadecimal format.

gdb/testsuite/ChangeLog:

2015-12-09  Luis Machado  <lgustavo@codesourcery.com>

	* gdb.mi/mi-var-display.exp: Add new checks for the zero-hexadecimal
	  format and change test names to make them unique.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix wrong output of x87 registers due to truncation to double on amd64
@ 2015-12-09 12:32 sergiodj+buildbot
  2015-12-09 12:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-09 12:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b593e3d9b00b09af43abf1e95d68e68200e3c2a5 ***

Author: Ruslan Kabatsayev <b7.10110111@gmail.com>
Branch: master
Commit: b593e3d9b00b09af43abf1e95d68e68200e3c2a5

Fix wrong output of x87 registers due to truncation to double on amd64

When `info float` is used on an AMD64 system, GDB prints
floating-point values of x87 registers with raw contents like
0x361a867a8e0527397ce0 or 0xc4f988454a1ddd3cfdab wrongly.

This happens due to truncation to double, after which the former
becomes 0.0, and the latter becomes negative infinity.  This is caused
by failed detection of x86-64 host, which results in setting
gdb_host_{float,double,long_double}_format to zeros.

This commit fixes this misdetection, and adds a test to make sure
future commits don't introduce a regression here.

gdb/ChangeLog:
2015-12-09  Ruslan Kabatsayev  <b7.10110111@gmail.com>

	PR gdb/18702
	* configure.host: Fix detection of x86_64 host when setting
	floatformats.

gdb/testsuite/ChangeLog:
2015-12-09  Ruslan Kabatsayev  <b7.10110111@gmail.com>
	    Pedro Alves  <pedro@redhat.com>

	PR gdb/18702
	Add checking of floatformats setup on x86_64 hosts.
	* gdb.arch/i386-float.S (main): Load bigval and smallval.
	(smallval, bigval): New labels/constants.
	* gdb.arch/i386-float.exp: Use with_test_prefix and test "info
	float" after loading bigval and smallval.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] DOCO: Enhance the menu to select function overloads with signatures
@ 2015-12-08  9:14 sergiodj+buildbot
  2015-12-08  9:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-08  9:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3685b09fb85dc279762e19df310dc2f30e64b044 ***

Author: Pierre-Marie de Rodat <derodat@adacore.com>
Branch: master
Commit: 3685b09fb85dc279762e19df310dc2f30e64b044

DOCO: Enhance the menu to select function overloads with signatures

gdb/ChangeLog:

	* NEWS: Announce this enhancement and the corresponding new
	option.

gdb/doc/ChangeLog:

	* gdb.texinfo (Ada Mode Into): Move overloading support
	description to its own node.
	(Overloading support for Ada): New node.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Support Z0 packet in AArch64 multi-arch debugging
@ 2015-12-07 16:13 sergiodj+buildbot
  2015-12-08  0:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 16:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17b1509aac6ff4205749c2626fddbb1c4d7255f4 ***

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

Support Z0 packet in AArch64 multi-arch debugging

In commit 6085d6f6, Z0 packet is disabled in aarch64 GDBserver if
the inferior is 32-bit or there may be multiple inferiors, because
Z0 packet isn't supported for arm then.  Recently, Z0 packet
is supported in arm target, so we don't have such limitation in
aarch64 GDBserver, that is to say, aarch64 GDBserver can use Z0
packet in multi-arch/multi-inferior debugging when the inferior's
arch is arm.

Part of this patch is to revert 6085d6f6, and the rest of the patch
is to move some breakpoint related arm_* functions into
linux-aarch32-low.c in order to share them between arm and aarch64.

This patch is regression tested on aarch64-linux for debugging both
aarch64 programs and arm programs respectively.

gdb/gdbserver:

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

	* configure.srv: Append arm.o to srv_tgtobj for
	aarch64*-*-linux* target.
	* linux-aarch32-low.c (arm_abi_breakpoint): New macro.  Moved
	from linux-arm-low.c.
	(arm_eabi_breakpoint, arm_breakpoint): Likewise.
	(arm_breakpoint_len, thumb_breakpoint): Likewise.
	(thumb_breakpoint_len, thumb2_breakpoint): Likewise.
	(thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode, arm_breakpoint_at): Likewise.
	(arm_breakpoint_kinds): Likewise.
	(arm_breakpoint_kind_from_pc): Likewise.
	(arm_sw_breakpoint_from_kind): Likewise.
	(arm_breakpoint_kind_from_current_state): Likewise.
	* linux-aarch32-low.h (arm_breakpoint_kind_from_pc): Declare.
	(arm_sw_breakpoint_from_kind): Declare.
	(arm_breakpoint_kind_from_current_state): Declare.
	(arm_breakpoint_at): Declare.
	* linux-aarch64-low.c (aarch64_sw_breakpoint_from_kind): Call
	arm_sw_breakpoint_from_kind if process is 32-bit.
	(aarch64_breakpoint_kind_from_pc): New function.
	(aarch64_breakpoint_kind_from_current_state): New function.
	(the_low_target): Initialize fields breakpoint_kind_from_pc
	and breakpoint_kind_from_current_state.
	* linux-arm-low.c (arm_breakpoint_kinds): Move to
	linux-aarch32-low.c.
	(arm_abi_breakpoint, arm_eabi_breakpoint): Likewise.
	(arm_breakpoint, arm_breakpoint_len): Likewise.
	(thumb_breakpoint, thumb_breakpoint_len): Likewise.
	(thumb2_breakpoint, thumb2_breakpoint_len): Likewise.
	(arm_is_thumb_mode): Likewise.
	(arm_breakpoint_at): Likewise.
	(arm_breakpoint_kind_from_pc): Likewise.
	(arm_sw_breakpoint_from_kind): Likewise.
	(arm_breakpoint_kind_from_current_state): Likewise.

	Revert:
	2015-08-04  Yao Qi  <yao.qi@linaro.org>

	* linux-aarch64-low.c (aarch64_supports_z_point_type): Return
	0 for Z_PACKET_SW_BP if it may be used in multi-arch debugging.
	* server.c (extended_protocol): Remove "static".
	* server.h (extended_protocol): Declare it.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Add myself as a write-after-approval GDB maintainer
@ 2015-12-07 12:11 sergiodj+buildbot
  2015-12-07 21:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-07 12:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b36b65787bcb905fb6a2c7b790b07dcaacbe1cb ***

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

Add myself as a write-after-approval GDB maintainer

gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add Andreas Arnez.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PowerPC ifunc with local symbols
@ 2015-12-07  4:29 sergiodj+buildbot
  2015-12-07 19:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-07  4:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbf959729423640e28a0d571338d3c8045cbb1e1 ***

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

PowerPC ifunc with local symbols

This fixes some cases where the linker would incorrectly error on plt
relocs to local ifunc symbols.  I've also tidied plt and ifunc
handling for ppc64, where check_relocs was allowing for the
possibility of plt calls via addr14/addr24 relocs but relocate_section
was not.

	* elf32-ppc.c (ppc_elf_check_relocs): Don't error on local ifunc
	plt call.  Wrap long lines.
	(ppc_elf_relocate_section): Wrap long lines.
	* elf64-ppc.c (ppc64_elf_check_relocs): Don't error on local ifunc
	plt calls.  Move __tls_get_addr checks later.  Don't create plt
	for addr14/addr24 relocs.
	(ppc64_elf_gc_sweep_hook): Adjust to suit check_relocs changes.
	(ppc64_elf_relocate_section): Correct local ifunc handling for
	PLT64, PLT32 and PLT16 relocs.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] R_PPC64_ENTRY
@ 2015-12-07  3:41 sergiodj+buildbot
  2015-12-07 16:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-07  3:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 006589cfa144fc1efeea1d114943c0bd1624e930 ***

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

R_PPC64_ENTRY

Add a new relocation that marks large-model entry code, for edit back
to medium-model.

include/elf/
	* ppc64.h (R_PPC64_ENTRY): Define.
bfd/
	* reloc.c (BFD_RELOC_PPC64_ENTRY): New.
	* elf64-ppc.c (reloc_howto_type ppc64_elf_howto_raw): Add
	entry for R_PPC64_ENTRY.
	(LD_R2_0R12, ADD_R2_R2_R12, LIS_R2, ADDIS_R2_R12): Define.
	(ppc64_elf_reloc_type_lookup): Handle R_PPC64_ENTRY.
	(ppc64_elf_relocate_section): Edit code at R_PPC64_ENTTY.  Use
	new insn defines.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Reorder some power9 insns
@ 2015-12-07  3:17 sergiodj+buildbot
  2015-12-07 15:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-07  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd2887fc3de48f6261d34208a0132122f05d7ef4 ***

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

Reorder some power9 insns

The idea being to put instructions that have the same encoding adjacent
to each other.

	* opcodes/ppc-opc.c (powerpc_opcodes): Sort power9 insns by
	major opcode/xop.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver: set ptrace flags after creating inferiors
@ 2015-12-05  2:39 sergiodj+buildbot
  2015-12-05  2:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-05  2:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ece66d651004eac0210217c4d48babf4e80d1f2e ***

Author: Josh Stone <jistone@redhat.com>
Branch: master
Commit: ece66d651004eac0210217c4d48babf4e80d1f2e

gdbserver: set ptrace flags after creating inferiors

Rename target_ops.arch_setup to .post_create_inferior.  In the Linux
hook, continue calling the low arch setup, then also set ptrace flags.
This corrects the possibility of running without flags, demonstrated by
a new test that would fail to catch a fork before.

gdb/gdbserver/ChangeLog:

2015-12-04  Josh Stone  <jistone@redhat.com>

	* target.h (struct target_ops) <arch_setup>: Rename to ...
	(struct target_ops) <post_create_inferior>: ... this.
	(target_arch_setup): Rename to ...
	(target_post_create_inferior): ... this, calling post_create_inferior.
	* server.c (start_inferior): Update target_arch_setup calls to
	target_post_create_inferior.
	* linux-low.c (linux_low_ptrace_options): Forward declare.
	(linux_arch_setup): Update its comment for general use.
	(linux_post_create_inferior): New, run arch_setup and setup ptrace.
	(struct linux_target_ops): Use linux_post_create_inferior.
	* lynx-low.c (struct lynx_target_ops): Update arch_setup stub comment
	to post_create_inferior.
	* nto-low.c (struct nto_target_ops): Likewise.
	* spu-low.c (struct spu_target_ops): Likewise.
	* win32-low.c (struct win32_target_ops): Likewise.

gdb/testsuite/ChangeLog:

2015-12-04  Josh Stone  <jistone@redhat.com>

	* gdb.base/catch-fork-static.exp: New.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Run gdb.base/sizeof.exp with board having gdb, noinferiorio
@ 2015-12-03 17:23 sergiodj+buildbot
  2015-12-03 17:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-03 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41d0efca578f03db2787246a4e0c7bf9b085007c ***

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

Run gdb.base/sizeof.exp with board having gdb,noinferiorio

In my remote cross testing (x86_64 host and aarch64 target), the test
gdb.base/sizeof.exp is skipped because gdb,noinferiorio is defined in
my gdbserver board file.  Tests are skipped because the test checks
the expected value from the program's output, but I don't see why must
do it this way.  With my patch applied, we can save the result in variable
in the program, and check the variable then.  Then, the test doesn't rely
on inferiorio.

gdb/testsuite:

2015-12-03  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/sizeof.c: Don't include stdio.h and
	../lib/unbuffer_output.c.
	(main): New variable 'size' and 'value'.  Remove printf and
	gdb_unbuffer_output.  Assign return value to size and value.
	* gdb.base/sizeof.exp: Remove the checking to gdb,noinferiorio
	at the beginning.
	(check_sizeof): Check the result by printing variable 'size'.
	(check_valueof): Check the result by printing variable 'value'.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] addr2line vs. inlined C functions called from C++
@ 2015-12-02 13:42 sergiodj+buildbot
  2015-12-02 14:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-02 13:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 923b198a8426f02866f33362b26ed8bbf7a5c5cd ***

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

addr2line vs. inlined C functions called from C++

In this case the inlined function doesn't have DW_AT_linkage_name in
.debug_info, but the language is C++ so find_nearest_line goes looking
in the symbol table.  Since the function is inlined the enclosing
non-inline function symbol is returned from _bfd_elf_find_function,
which is wrong.  This patch only uses a symbol if its address matches.

	PR binutils/19315
	* dwarf2.c (_bfd_elf_find_function): Return symbol matched.
	(_bfd_dwarf2_find_nearest_line): Check symbol returned above
	against dwarf range.
	* elf-bfd.h (_bfd_elf_find_function): Update prototype.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix powerpc64 segfault caused by zero r_symndx relocs.
@ 2015-12-02  9:02 sergiodj+buildbot
  2015-12-02 13:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-02  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c27b8c2aeb369972f4f9f98f390607694c56a127 ***

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

Fix powerpc64 segfault caused by zero r_symndx relocs.

Fixes a segfault in ppc64_elf_tls_optimize found when testing
R_PPC64_ENTRY, and potential for trouble in other places found by
code inspection.

	* elf64-ppc.c (ppc64_elf_tls_optimize): Don't segfault on NULL
	symbol section or output section.
	(ppc64_elf_edit_toc): Similarly for ld -R objects.
	(ppc64_elf_size_stubs): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Avoid "operation may be undefined" warning in remote.c
@ 2015-12-01 17:41 sergiodj+buildbot
  2015-12-02  9:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-01 17:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 974eac9d7694ca14dcdf6d1a74777a265fffdb95 ***

Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Branch: master
Commit: 974eac9d7694ca14dcdf6d1a74777a265fffdb95

Avoid "operation may be undefined" warning in remote.c

GCC 4.1 gives the following warning:
gdb/remote.c: In function 'remote_parse_stop_reply':
gdb/remote.c:6549: warning: operation on 'p' may be undefined
on this line of code:

	event->ptid = read_ptid (++p, &p);

Since p actually isn't used afterwards anyway, simply use NULL.

gdb/
	* remote.c (remote_parse_stop_reply): Avoid GCC 4.1 "operation
	may be undefined" warning.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Run gdb.base/disp-step-syscall.exp for aarch64-linux
@ 2015-12-01 12:47 sergiodj+buildbot
  2015-12-02  7:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-01 12:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99fd02d9fc9d6cc470d3b81c4cc3439b47bb9419 ***

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

Run gdb.base/disp-step-syscall.exp for aarch64-linux

This patch handles target aarch64*-*-linux* for syscall instruction.

gdb/testsuite:

2015-12-01  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/disp-step-syscall.exp: Define syscall instruction
	for aarch64*-*-linux* target.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] ARC port broken reloc processing
@ 2015-12-01  5:47 sergiodj+buildbot
  2015-12-01 22:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  5:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a5ff21b13783cef3b26680d1673b1ae37697aeb ***

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

ARC port broken reloc processing

This initialises howto.dst_mask so that relocations in debug sections
are applied by the generic reloc processing used by objdump to display
debug sections.

	* elf32-arc.c (arc_elf_howto_init): Init dst_mask.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Invoke aout N_* macros with pointer to struct internal_exec
@ 2015-12-01  3:43 sergiodj+buildbot
  2015-12-02  5:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  3:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbb1afc89b5cfa2f09b6a7c25fbfef745fbdd724 ***

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

Invoke aout N_* macros with pointer to struct internal_exec

No functional changes here.

BTW, some of these headers don't seem to be used anywhere:
include/aout/dynix3.h, include/aout/encap.h, include/aout/hp.h,
gas/config/aout_gnu.h

bfd/
	* aout-adobe.c: Invoke aout N_* macros with pointer to
	struct internal_exec.
	* aout-arm.c: Likewise.
	* aout-cris.c: Likewise.
	* aout-target.h: Likewise.
	* aout-tic30.c: Likewise.
	* aoutf1.h: Likewise.
	* aoutx.h: Likewise.
	* bout.c: Likewise.
	* freebsd.h: Likewise.
	* gen-aout.c: Likewise.
	* hp300hpux.c: Likewise.
	* i386aout.c: Likewise.
	* i386linux.c: Likewise.
	* i386lynx.c: Likewise.
	* i386mach3.c: Likewise.
	* i386os9k.c: Likewise.
	* libaout.h: Likewise.
	* m68klinux.c: Likewise.
	* m88kmach3.c: Likewise.
	* mipsbsd.c: Likewise.
	* netbsd.h: Likewise.
	* pc532-mach.c: Likewise.
	* pdp11.c: Likewise.
	* riscix.c: Likewise.
	* sparclinux.c: Likewise.
	* sparclynx.c: Likewise.
gas/
	* config/aout_gnu.h: Invoke aout N_* macros with pointer to
	struct internal_exec.
include/
	* bout.h: Invoke aout N_* macros with pointer to
	struct internal_exec.
	* os9k.h: Likewise.
include/aout/
	* adobe.h: Invoke aout N_* macros with pointer to
	struct internal_exec.
	* aout64.h: Likewise.
	* dynix3.h: Likewise.
	* encap.h: Likewise.
	* hp.h: Likewise.
	* hp300hpux.h: Likewise.
	* sun4.h: Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Don't use BFD_TRADITIONAL_FORMAT flag in COFF support
@ 2015-12-01  3:35 sergiodj+buildbot
  2015-12-02  3:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-12-01  3:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b560e2acdd41fe6b6228b11c2d82ad2a96188153 ***

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

Don't use BFD_TRADITIONAL_FORMAT flag in COFF support

info->traditional_format is available, or can be easily made
available.  This relegates BFD_TRADITIONAL_FORMAT to AOUT use only.

	* coff-rs6000.c (_bfd_xcoff_put_symbol_name): Replace abfd param
	with info param.  Test info->traditional_format rather than
	BFD_TRADITIONAL_FORMAT flag.
	* coff64-rs6000.c (_bfd_xcoff64_put_symbol_name): Likewise.
	* libxcoff.h (struct xcoff_backend_data_rec): Update
	_xcoff_put_symbol_name prototype.
	(bfd_xcoff_put_symbol_name): Add info param.
	* xcofflink.c (xcoff_find_tc0): Update bfd_xcoff_put_symbol_name call.
	(xcoff_write_global_symbol): Likewise.
	(xcoff_link_input_bfd): Test info->traditional_format rather than
	BFD_TRADITIONAL_FORMAT flag.
	* cofflink.c (_bfd_coff_final_link): Likewise.
	(_bfd_coff_link_input_bfd, _bfd_coff_write_global_sym): Likewise.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Refactor queries for hardware and software single stepping support in GDBServer.
@ 2015-11-30 22:31 sergiodj+buildbot
  2015-12-01 19:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d00775ece9e2364da5cfd65ebbfce515859667f ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 7d00775ece9e2364da5cfd65ebbfce515859667f

Refactor queries for hardware and software single stepping support in GDBServer.

Before this patch there was only one call: can_hardware_single_step. Its
implementation was a check on breakpoint_reinsert_addr if NULL it assumed
that the target could hardware single step.

This patch prepares for the case where this is not true anymore.

In order to improve software single stepping in GDBServer the
breakpoint_reinsert_addr operation of targets that had a very simple
software implementation used only for stepping over thread creation events
will be removed.

This will create a case where a target does not support hardware single
step and has the operation breakpoint_reinsert_addr set to NULL, thus
can_hardware_single_step needs to be implemented another way.

A new target operation supports_hardware_single_step is introduced and is
to return true if the target does support such a feature, support for the
feature is manually hardcoded.

Note that the hardware single step support was enabled as per the current
behavior, I did not check if tile for example really has ptrace singlestep
support but since the current implementation assumed it had, I kept it
that way.

No regressions on Ubuntu 14.04 on ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

Compilation tested on: aarch64,arm,bfind,crisv32,m32r,ppc,s390,tic6x,tile,
xtensa.
Not tested : sh.

gdb/gdbserver/ChangeLog:

	* linux-aarch64-low.c (aarch64_supports_hardware_single_step):
	New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-arm-low.c (arm_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-bfin-low.c (bfin_supports_hardware_single_step): New function.
	(struct linux_target_ops) <bfin_supports_hardware_single_step>:
	Initialize.
	* linux-crisv32-low.c (cris_supports_hardware_single_step):
	New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-low.c (can_hardware_single_step): Use
	supports_hardware_single_step.
	(can_software_single_step): New function.
	(start_step_over): Call can_software_single_step.
	(linux_supports_hardware_single_step): New function.
	(struct target_ops) <supports_software_single_step>: Initialize.
	* linux-low.h (struct linux_target_ops)
	<supports_hardware_single_step>: Initialize.
	* linux-m32r-low.c (m32r_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-ppc-low.c (ppc_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step> Initialize.
	* linux-s390-low.c (s390_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-sh-low.c (sh_supports_hardware_single_step): New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-tic6x-low.c (tic6x_supports_hardware_single_step): New function.
	(struct linux_target_ops) <tic6x_supports_hardware_single_step>:
	Initialize.
	* linux-tile-low.c (tile_supports_hardware_single_step): New function.
	(struct linux_target_ops) <tile_supports_hardware_single_step>:
	Initialize.
	* linux-x86-low.c (x86_supports_hardware_single_step) New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* linux-xtensa-low.c (xtensa_supports_hardware_single_step):
	New function.
	(struct linux_target_ops) <supports_hardware_single_step>: Initialize.
	* target.h (struct target_ops): <supports_software_single_step>:
	New field.
	(target_supports_software_single_step): New macro.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix breakpoint size when stepping over a permanent breakpoint in GDBServer.
@ 2015-11-30 22:15 sergiodj+buildbot
  2015-12-01 16:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 22:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 769ef81fec526f3c7513c88e82f98045f8971d14 ***

Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Branch: master
Commit: 769ef81fec526f3c7513c88e82f98045f8971d14

Fix breakpoint size when stepping over a permanent breakpoint in GDBServer.

When manually stepping over a permanent breakpoint on ARM we need to fetch the
right breakpoint size based on the current instruction set used.

Since this is not encoded in the stop_pc, the instruction mode needs to be
fetched from the CPSR register.

This is done by introducing a new target operation called :
breakpoint_kind_from_current_state.

For other targets that do not need this, breakpoint_kind_from_pc is used.

No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }

gdb/gdbserver/ChangeLog:

	* linux-arm-low.c (arm_is_thumb_mode): New function.
	(arm_breakpoint_at): Use arm_is_thumb_mode.
	(arm_breakpoint_kind_from_current_state): New function.
	(struct linux_target_ops) <breakpoint_kind_from_current_state>:
	Initialize.
	* linux-low.c (linux_wait_1): Call breakpoint_kind_from_current_state.
	(linux_breakpoint_kind_from_current_state): New function.
	(struct target_ops <breakpoint_kind_from_current_state>: Initialize.
	* linux-low.h (struct linux_target_ops)
	<breakpoint_kind_from_current_state>: New field.
	* target.h (struct target_ops): Likewise.
	(target_breakpoint_kind_from_current_state): New macro.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol
@ 2015-11-30 21:45 sergiodj+buildbot
  2015-12-01 12:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2faf941ae49653ff6e1485adfee299313d47c91 ***

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

Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol

Testing with "maint set target-non-stop on" causes regressions in
tests that rely on TARGET_WAITKIND_NO_RESUMED, which isn't modelled on
the RSP.  In real all-stop, gdbserver detects the situation and
reporst error to GDB, and so the tests (e.g.,
gdb.threads/no-unwaited-for-left.exp) at fail quickly.  But with
"maint set target-non-stop on", GDB instead hangs forever waiting for
a stop reply that never comes, and so the tests take longer to time
out.

This adds a new "N" stop reply packet that maps 1-1 to
TARGET_WAITKIND_NO_RESUMED.

gdb/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	PR 14618
	* NEWS (New remote packets): Mention the N stop reply.
	* remote.c (remote_protocol_features): Add "no-resumed" entry.
	(remote_query_supported): Report no-resumed+ support.
	(remote_parse_stop_reply): Handle 'N'.
	(process_stop_reply): Handle TARGET_WAITKIND_NO_RESUMED.
	(remote_wait_as): Handle 'N' / TARGET_WAITKIND_NO_RESUMED.
	(_initialize_remote): Register "set/show remote
	no-resumed-stop-reply" commands.

gdb/doc/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	PR 14618
	* gdb.texinfo (Stop Reply Packets): Document the N stop reply.
	(Remote Configuration): Add the "set/show remote
	no-resumed-stop-reply" to the available settings table.
	(General Query Packets): Document the "no-resumed" qSupported
	feature.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	PR 14618
	* linux-low.c (linux_wait_1): If the last resumed thread is gone,
	report TARGET_WAITKIND_NO_RESUMED.
	* remote-utils.c (prepare_resume_reply): Handle
	TARGET_WAITKIND_NO_RESUMED.
	* server.c (report_no_resumed): New global.
	(handle_query) <qSupported>: Handle "no-resumed+".  Report
	"no-resumed+" support.
	(resume): When the target reports TARGET_WAITKIND_NO_RESUMED, only
	return error if the client doesn't support no-resumed events.
	(push_stop_notification): New function.
	(handle_target_event): Use it.  Report TARGET_WAITKIND_NO_RESUMED
	events if the client supports them.

gdb/testsuite/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.threads/no-unwaited-for-left.exp: Remove setup_kfail calls.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver: fix killed-outside.exp
@ 2015-11-30 21:22 sergiodj+buildbot
  2015-12-01  9:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a681f9c91372d282229f6d58ba235ef0dd3644fb ***

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

gdbserver: fix killed-outside.exp

killed-outside.exp regresses with "maint set target-non-stop on".  The
logs show:

 (gdb) continue
 Continuing.
 infrun: clear_proceed_status_thread (Thread 9028.9028)
 infrun: proceed (addr=0xffffffffffffffff, signal=GDB_SIGNAL_DEFAULT)
 infrun: proceed: resuming Thread 9028.9028
 Sending packet: $Z0,3615a03966,1#4b...  Notification received: Stop:X9;process:2344
 Packet received: E01
 Sending packet: $Z0,3615a13970,1#47...Packet received: E01
 Sending packet: $Z0,3615a14891,1#4a...Packet received: E01
 infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current thread [Thread 9028.9028] at 0x4005e4
 Sending packet: $vCont;c:p2344.2344#1a...Packet received: E.target not running.
 Sending packet: $qXfer:threads:read::0,fff#03...Packet received: l<threads>\n</threads>\n
 Sending packet: $vStopped#55...Packet received: OK
 Unexpected vCont reply in non-stop mode: E.target not running.
 (gdb) remote_async_inferior_event_handler
 infrun: target_wait (-1.0.0, status) =
 infrun:   9028.0.0 [process 9028],
 infrun:   status->kind = signalled, signal = GDB_SIGNAL_KILL
 infrun: TARGET_WAITKIND_SIGNALLED

 Program terminated with signal SIGKILL, Killed.
 The program no longer exists.
 infrun: stop_waiting
 infrun: clear_step_over_info
 infrun: stop_all_threads
 remote_thread_exit_events(1)

Note the "Unexpected vCont reply" error.

I traced it to a problem in status_pending_p_callback.  It resumes an
LWP when it shouldn't.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* linux-low.c (thread_still_has_status_pending_p): Don't check
	vCont;t here.
	(lwp_resumed): New function.
	(status_pending_p_callback): Return early if the LWP is not
	supposed to be resumed.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remote thread create/exit events
@ 2015-11-30 21:14 sergiodj+buildbot
  2015-12-01  8:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65706a29bac50c2c971227a1945e46502845766b ***

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

Remote thread create/exit events

When testing with "maint set target-non-stop on", a few
threading-related tests expose an issue that requires new RSP packets.

Say there are 3 threads running, 1-3.  If GDB tries to stop thread 1,
2 and 3, and then waits for their stops, but meanwhile say, thread 2
exits, GDB hangs forever waiting for a stop for thread 2 that won't
ever happen.

This patch fixes the issue by adding support for thread exit events to
the protocol.  However, we don't want these always enabled, as they're
useless most of the time, and would slow down remote debugging.  So I
made it so that GDB can enable/disable them, and then made gdb do that
around the cases that need it, which currently is only
infrun.c:stop_all_threads.

In turn, if we have thread exit events, then the extra "thread x
exited" traffic slows down attach-many-short-lived-threads.exp enough
that gdb has trouble keeping up with new threads that are spawned
while gdb tries to stop existing ones.  To fix that I added support
for the counterpart thread created events too.  Enabling those when we
try to stop threads ensures that new threads never get a chance to
themselves start new threads, killing the race.

gdb/doc/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Remote Configuration): List "set/show remote
	thread-events" command in configuration table.
	(Stop Reply Packets): Document "T05 create" stop
	reason and 'w' stop reply.
	(General Query Packets): Document QThreadEvents packet.  Document
	QThreadEvents qSupported feature.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* linux-low.c (handle_extended_wait): Assert that the LWP's
	waitstatus is TARGET_WAITKIND_IGNORE.  If GDB wants to hear about
	thread create events, leave the new child's status pending.
	(linux_low_filter_event): If GDB wants to hear about thread exit
	events, leave the LWP marked dead and don't delete it.
	(linux_wait_for_event_filtered): Don't check for thread exit.
	(filter_exit_event): New function.
	(linux_wait_1): Use it, when returning an exit event.
	(linux_resume_one_lwp_throw): Assert that the LWP's
	waitstatus is TARGET_WAITKIND_IGNORE.
	* remote-utils.c (prepare_resume_reply): Handle
	TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
	* server.c (report_thread_events): New global.
	(handle_general_set): Handle QThreadEvents.
	(handle_query) <qSupported>: Handle and report QThreadEvents+;
	(handle_target_event): Handle TARGET_WAITKIND_THREAD_CREATED and
	TARGET_WAITKIND_THREAD_EXITED.
	* server.h (report_thread_events): Declare.

gdb/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* NEWS (New commands): Mention "set/show remote thread-events"
	commands.
	(New remote packets): Mention thread created/exited stop reasons
	and QThreadEvents packet.
	* infrun.c (disable_thread_events): New function.
	(stop_all_threads): Disable/enable thread create/exit events.
	Handle TARGET_WAITKIND_THREAD_EXITED.
	(handle_inferior_event_1): Handle TARGET_WAITKIND_THREAD_CREATED
	and TARGET_WAITKIND_THREAD_EXITED.
	* remote.c (remove_child_of_pending_fork): Also remove threads of
	threads that have TARGET_WAITKIND_THREAD_EXITED events.
	(remote_parse_stop_reply): Handle "create" magic register.  Handle
	'w' stop reply.
	(initialize_remote): Install remote_thread_events as
	to_thread_events target hook.
	(remote_thread_events): New function.
	* target-delegates.c: Regenerate.
	* target.c (target_thread_events): New function.
	* target.h (struct target_ops) <to_thread_events>: New field.
	(target_thread_events): Declare.
	* target/waitstatus.c (target_waitstatus_to_string): Handle
	TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
	* target/waitstatus.h (enum target_waitkind)
	<TARGET_WAITKIND_THREAD_CREATED, TARGET_WAITKIND_THREAD_EXITED):
	New values.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] gdbserver resume_stop handling bug
@ 2015-11-30 21:00 sergiodj+buildbot
  2015-12-01  6:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56cf4bed5354769d7352c5cf4e054a346d2553cd ***

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

gdbserver resume_stop handling bug

Running attach-many-short-lived-threads.exp with the extended-remote
board with "maint set target-non-stop on" times out -- the attach
never completes.  Enabling infrun debug logs, we see that GDB is stuck
stopping all threads:

 infrun: target_wait (-1.0.0, status) =
 infrun:   1639.22213.0 [Thread 1639.22213],
 infrun:   status->kind = stopped, signal = GDB_SIGNAL_0
 infrun:   Thread 1639.22260 not executing
 infrun:   Thread 1639.22256 not executing
 infrun:   Thread 1639.22258 not executing
 infrun:   Thread 1639.22257 not executing
 infrun:   Thread 1639.22259 not executing
 infrun:   Thread 1639.22255 not executing
 infrun:   Thread 1639.22253 executing, already stopping
 infrun:   Thread 1639.22251 executing, already stopping
 infrun:   Thread 1639.22252 executing, already stopping
 infrun:   Thread 1639.22250 executing, already stopping
 infrun:   Thread 1639.22254 executing, already stopping
 infrun:   Thread 1639.22247 executing, already stopping
 infrun:   Thread 1639.22213 not executing
 infrun:   Thread 1639.22207 not executing
 infrun:   Thread 1639.22201 not executing
 infrun:   Thread 1639.22219 not executing
 infrun:   Thread 1639.1639 not executing
 ** HANG HERE **

GDB is waiting for the stop replies of any of those "already stopping"
threads.  Take 22253 for example.  On the gdbserver logs we see:

 ...
 resume_stop request for LWP 22253
 stopping LWP 22253
 Sending sigstop to lwp 22253
 linux_resume done
 ...

and:

 my_waitpid (-1, 0x40000001)
 my_waitpid (-1, 0x80000001): status(3057f), 22253
 LWFE: waitpid(-1, ...) returned 22253, ERRNO-OK
 LLW: waitpid 22253 received Trace/breakpoint trap (stopped)
 pc is 0x3615ef4ce1
 HEW: Got clone event from LWP 22253, new child is LWP 22259

but from here on, we never see any other event for LWP 22253.  In
particular, we never see the expected SIGSTOP (from "Sending sigstop"
above).  The issue is that linux_resume_stopped_resumed_lwps never
re-resumes the 22253 after the clone event.

gdb/gdbserver/ChangeLog:
2015-11-30  Pedro Alves  <palves@redhat.com>

	* linux-low.c (resume_stopped_resumed_lwps): Don't check whether
	the thread's last_resume_kind was resume_stop.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] New vCtrlC packet, non-stop mode equivalent of \003
@ 2015-11-30 20:44 sergiodj+buildbot
  2015-12-01  4:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de979965d3f5de7e4bf2354871fe85b3f77c720e ***

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

New vCtrlC packet, non-stop mode equivalent of \003

There's currently no non-stop equivalent of the all-stop ^C (\003)
"packet" that GDB sends when a ctrl-c is pressed while a foreground
command is active.  There's vCont;t, but that's defined to cause a
"signal 0" stop.

This fixes many tests that type ^C, when testing with extended-remote
with "maint set target-non-stop on".  E.g.:

 Continuing.
 talk to me baby
 PASS: gdb.base/interrupt.exp: process is alive
 a
 a
 PASS: gdb.base/interrupt.exp: child process ate our char
 ^C
 [Thread 22730.22730] #1 stopped.
 0x0000003615ee6650 in __read_nocancel () at ../sysdeps/unix/syscall-template.S:81
 81      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
 (gdb) FAIL: gdb.base/interrupt.exp: send_gdb control C
 p func1 ()

gdb/
2015-11-30  Pedro Alves  <palves@redhat.com>

	* NEWS (New remote packets): Mention vCtrlC.
	* remote.c (PACKET_vCtrlC): New enum value.
	(async_remote_interrupt): Call target_interrupt instead of
	target_stop.
	(remote_interrupt_as): Remove 'ptid' parameter.
	(remote_interrupt_ns): New function.
	(remote_stop): Adjust.
	(remote_interrupt): If the target is in non-stop mode, try
	interrupting with vCtrlC.
	(initialize_remote): Install set remote ctrl-c packet.

gdb/doc/
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdb.texinfo (Bootstrapping): Add "interrupting remote targets"
	anchor.
	(Packets): Document vCtrlC.

gdb/gdbserver/
2015-11-30  Pedro Alves  <palves@redhat.com>

	* server.c (handle_v_requests): Handle vCtrlC.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Remote all-stop-on-top-of-non-stop
@ 2015-11-30 20:13 sergiodj+buildbot
  2015-11-30 21:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-30 20:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6efcd9a8b3dc6a01cd1f212a2d854e5f8896715e ***

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

Remote all-stop-on-top-of-non-stop

This is the first pass at implementing support for all-stop mode
running against the remote target using the non-stop variant of the
protocol.

The trickiest part here is the initial connection setup/synching.  We
need to fetch all inferiors' target descriptions etc. before stopping
threads, because stop_all_threads needs to read the threads' registers
(to record each thread's stop_pc).  But OTOH, the initial inferior
setup (target_post_attach, post_create_inferior, etc.), only works
correctly if the inferior is stopped...  So I've split that initial
setup part from attach_command_post_wait to a separate function, and
added a "still needs setup" flag to the inferior structure.  This is
similar to gdbserver/linux-low.c's handling of discovering the
process's target description).  Then if on connection all threads of
the remote inferior are running, when we go about stopping them, as
soon as they stop we call setup_inferior, from within
stop_all_threads.

Also, in all-stop, we need to process all the initial stop replies to
learn about all the pending signal the threads may already be stopped
for, and pick the one to report as current.  This is exposed by
gdb.threads/reconnect-signal.exp.

gdb/
2015-11-30  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (switch_to_thread_no_regs): Declare.
	* infcmd.c (setup_inferior): New function, factored out from ...
	(attach_command_post_wait): ... this.  Rename to ...
	(attach_post_wait): ... this.  Replace parameter async_exec with
	attach_post_wait_mode parameter.  Adjust.
	(enum attach_post_wait_mode): New enum.
	(struct attach_command_continuation_args): Replace 'async_exec'
	field with 'mode' field.
	(attach_command_continuation): Adjust.
	(attach_command): Add comment.  Mark the inferior as needing
	setup.  Adjust to use enum attach_post_wait_mode.
	(notice_new_inferior): Use switch_to_thread_no_regs.  Adjust to
	use enum attach_post_wait_mode.
	* inferior.h (setup_inferior): Declare.
	(struct inferior) <needs_setup>: New field.
	* infrun.c (set_last_target_status): Make extern.
	(stop_all_threads): Make extern.  Setup inferior, if necessary.
	* infrun.h (set_last_target_status, stop_all_threads): Declare.
	* remote-notif.c (remote_async_get_pending_events_handler)
	(handle_notification): Replace non_stop checks with
	target_is_non_stop_p() checks.
	* remote.c (remote_notice_new_inferior): Remove non_stop check.
	(remote_update_thread_list): Replace non_stop check with
	target_is_non_stop_p() check.
	(print_one_stopped_thread): New function.
	(process_initial_stop_replies): New 'from_tty' parameter.
	"Notice" all new live inferiors after storing initial stops as
	pending status in each corresponding thread.  If all-stop, stop
	all threads, try picking a signalled thread as current, and print
	the status of that one thread.  Record the last target status.
	(remote_start_remote): Replace non_stop checks with
	target_is_non_stop_p() checks.  Don't query for the remote current
	thread of use qOffsets here.  Pass from_tty to
	process_initial_stop_replies.
	(extended_remote_attach): Replace non_stop checks with
	target_is_non_stop_p() checks.
	(extended_remote_post_attach): Send qOffsets here.
	(remote_vcont_resume, remote_resume, remote_stop)
	(remote_interrupt, remote_parse_stop_reply, remote_wait): Replace
	non_stop checks with target_is_non_stop_p() checks.
	(remote_async): If target is non-stop, mark/clear the pending
	events token.
	* thread.c (switch_to_thread_no_regs): New function.


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] libiberty TAGS
@ 2015-11-28 19:24 sergiodj+buildbot
  2015-11-28 23:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 19:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f3363926de602b7590526740a01a64ca973ca78a ***

Author: Mike Stump <mikestump@comcast.net>
Branch: master
Commit: f3363926de602b7590526740a01a64ca973ca78a

libiberty TAGS

 	* Makefile.in (etags tags TAGS): Use && instead of ;.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@230270 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] libsanitizer merge from upstream r250806, compiler part.
@ 2015-11-28 18:08 sergiodj+buildbot
  2015-11-29  3:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 18:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b16c5514a2e01d47295e8d82cecd6b62db62955 ***

Author: Maxim Ostapenko <m.ostapenko@partner.samsung.com>
Branch: master
Commit: 3b16c5514a2e01d47295e8d82cecd6b62db62955

libsanitizer merge from upstream r250806, compiler part.

gcc/

	* asan.c (asan_emit_stack_protection): Don't pass local stack to
	asan_stack_malloc_[n] anymore. Check if asan_stack_malloc_[n] returned
	NULL and use local stack than.
	(asan_finish_file): Insert __asan_version_mismatch_check_v[n] call
	in addition to __asan_init.
	* sanitizer.def (BUILT_IN_ASAN_INIT): Rename to __asan_init.
	(BUILT_IN_ASAN_VERSION_MISMATCH_CHECK): Add new builtin call.
	* asan.h (asan_intercepted_p): Handle new string builtins.
	* ubsan.c (ubsan_use_new_style_p): New function.
	(ubsan_instrument_float_cast): If location is unknown, assign
	input_location to loc. Propagate loc to ubsan_create_data if
	ubsan_use_new_style_p returned true.

config/

	* bootstrap-asan.mk: Replace ASAN_OPTIONS=detect_leaks with
	LSAN_OPTIONS=detect_leaks.

gcc/testsuite/

	* c-c++-common/ubsan/float-cast-overflow-10.c: Adjust test.
	* c-c++-common/ubsan/float-cast-overflow-8.c: Likewise.
	* c-c++-common/ubsan/float-cast-overflow-9.c: Likewise.
	* g++.dg/asan/default-options-1.C: Likewise.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@229112 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters
@ 2015-11-28 17:44 sergiodj+buildbot
  2015-11-29  0:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4be264168ee2f6c38b6b9b3db0a166441be478b ***

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

PR other/61321 - demangler crash on casts in template parameters

The fix for bug 59195:

 [C++ demangler handles conversion operator incorrectly]
 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59195

unfortunately makes the demangler crash due to infinite recursion, in
case of casts in template parameters.

For example, with:

 template<int> struct A {};
 template <typename Y> void function_temp(A<sizeof ((Y)(999))>) {}
 template void function_temp<int>(A<sizeof (int)>);

The 'function_temp<int>' instantiation above mangles to:

  _Z13function_tempIiEv1AIXszcvT_Li999EEE

The demangler parses this as:

typed name
  template
    name 'function_temp'
    template argument list
      builtin type int
  function type
    builtin type void
    argument list
      template                          (*)
        name 'A'
        template argument list
          unary operator
            operator sizeof
            unary operator
              cast
                template parameter 0    (**)
              literal
                builtin type int
                name '999'

And after the fix for 59195, due to:

 static void
 d_print_cast (struct d_print_info *dpi, int options,
	       const struct demangle_component *dc)
 {
 ...
   /* For a cast operator, we need the template parameters from
      the enclosing template in scope for processing the type.  */
   if (dpi->current_template != NULL)
     {
       dpt.next = dpi->templates;
       dpi->templates = &dpt;
       dpt.template_decl = dpi->current_template;
     }

when printing the template argument list of A (what should be "<sizeof
(int)>"), the template parameter 0 (that is, "T_", the '**' above) now
refers to the first parameter of the the template argument list of the
'A' template (the '*' above), exactly what we were already trying to
print.  This leads to infinite recursion, and stack exaustion.  The
template parameter 0 should actually refer to the first parameter of
the 'function_temp' template.

Where it reads "for the cast operator" in the comment in d_print_cast
(above), it's really talking about a conversion operator, like:

  struct A { template <typename U> explicit operator U(); };

We don't want to inject the template parameters from the enclosing
template in scope when processing a cast _expression_, only when
handling a conversion operator.

The problem is that DEMANGLE_COMPONENT_CAST is currently ambiguous,
and means _both_ 'conversion operator' and 'cast expression'.

Fix this by adding a new DEMANGLE_COMPONENT_CONVERSION component type,
which does what DEMANGLE_COMPONENT_CAST does today, and making
DEMANGLE_COMPONENT_CAST just simply print its component subtree.

I think we could instead reuse DEMANGLE_COMPONENT_CAST and in
d_print_comp_inner still do:

 @@ -5001,9 +5013,9 @@ d_print_comp_inner (struct d_print_info *dpi, int options,
        d_print_comp (dpi, options, dc->u.s_extended_operator.name);
        return;

     case DEMANGLE_COMPONENT_CAST:
       d_append_string (dpi, "operator ");
 -     d_print_cast (dpi, options, dc);
 +     d_print_conversion (dpi, options, dc);
       return;

leaving the unary cast case below calling d_print_cast, but seems to
me that spliting the component types makes it easier to reason about
the code.

g++'s testsuite actually generates three symbols that crash the
demangler in the same way.  I've added those as tests in the demangler
testsuite as well.

And then this fixes PR other/61233 too, which happens to be a
demangler crash originally reported to GDB, at:
https://sourceware.org/bugzilla/show_bug.cgi?id=16957

Bootstrapped and regtested on x86_64 Fedora 20.

Also ran this through GDB's testsuite.  GDB will require a small
update to use DEMANGLE_COMPONENT_CONVERSION in one place it's using
DEMANGLE_COMPONENT_CAST in its sources.

libiberty/
2015-11-27  Pedro Alves  <palves@redhat.com>

        PR other/61321
        PR other/61233
        * demangle.h (enum demangle_component_type)
        <DEMANGLE_COMPONENT_CONVERSION>: New value.
        * cp-demangle.c (d_demangle_callback, d_make_comp): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (is_ctor_dtor_or_conversion): Handle DEMANGLE_COMPONENT_CONVERSION
        instead of DEMANGLE_COMPONENT_CAST.
        (d_operator_name): Return a DEMANGLE_COMPONENT_CONVERSION
        component if handling a conversion.
        (d_count_templates_scopes, d_print_comp_inner): Handle
        DEMANGLE_COMPONENT_CONVERSION.
        (d_print_comp_inner): Handle DEMANGLE_COMPONENT_CONVERSION instead
        of DEMANGLE_COMPONENT_CAST.
        (d_print_cast): Rename as ...
        (d_print_conversion): ... this.  Adjust comments.
        (d_print_cast): Rewrite - simply print the left subcomponent.
        * cp-demint.c (cplus_demangle_fill_component): Handle
        DEMANGLE_COMPONENT_CONVERSION.

        * testsuite/demangle-expected: Add tests.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@231020 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] (Makefiles): PATCH to include libcpp and libiberty in GCC etags
@ 2015-11-28 17:28 sergiodj+buildbot
  2015-11-28 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1e924157387421d45ccf2aafd33a886abda05420 ***

Author: Jason Merrill <jason@redhat.com>
Branch: master
Commit: 1e924157387421d45ccf2aafd33a886abda05420

(Makefiles): PATCH to include libcpp and libiberty in GCC etags

	gcc/c/
	* Make-lang.in (c.tags): Also include libcpp TAGS.
	gcc/cp/
	* Make-lang.in (c++.tags): Also include libcpp TAGS.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@229504 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Fix several crashes of C++ demangler on fuzzed input.
@ 2015-11-28 17:05 sergiodj+buildbot
  2015-11-28 19:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d81bf7ddc2ad497037fbfde5d15cfa8d81a9e959 ***

Author: Mikhail Maltsev <maltsevm@gmail.com>
Branch: master
Commit: d81bf7ddc2ad497037fbfde5d15cfa8d81a9e959

Fix several crashes of C++ demangler on fuzzed input.

libiberty/
	* cp-demangle.c (d_dump): Fix syntax error.
	(d_identifier): Adjust type of len to match d_source_name.
	(d_expression_1): Fix out-of-bounds access.  Check code variable for
	NULL before dereferencing it.
	(d_find_pack): Do not recurse for FIXED_TYPE, DEFAULT_ARG and NUMBER.
	(d_print_comp_inner): Add NULL pointer check.
	* cp-demangle.h (d_peek_next_char): Define as inline function when
	CHECK_DEMANGLER is defined.
	(d_advance): Likewise.
	* testsuite/demangle-expected: Add new testcases.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225727 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning
@ 2015-11-28 16:50 sergiodj+buildbot
  2015-11-28 17:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-28 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aaae08a7e4ac526975403ebb5f93b7f24ea16b90 ***

Author: Uros Bizjak <ubizjak@gmail.com>
Branch: master
Commit: aaae08a7e4ac526975403ebb5f93b7f24ea16b90

Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning

 	* getruntime.c (get_run_time) [__USE_GNU]: Use RUSAGE_SELF as
 	argument 1 of getrusage call.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225534 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 3/3] Add floating-point FP16 instructions
@ 2015-11-27 16:50 sergiodj+buildbot
  2015-11-28 16:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 16:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 622b9eb1a6047bd3ad3e1a3f120cf7318ac25b57 ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: 622b9eb1a6047bd3ad3e1a3f120cf7318ac25b57

[AArch64][PATCH 3/3] Add floating-point FP16 instructions

ARMv8.2 adds 16-bit floating point operations as an optional extension
to the ARMv8 FP support. This patch adds the new FP16 instructions,
making them available when the architecture extension +fp+fp16 is
specified.

The instructions added are:

- Comparisons and conditionals: FCMP, FCCMPE, FCMP, FCMPE and FCSEL.
- Arithmetic: FABS, FNEG, FSQRT, FMUL, FDIV, FADD, FSUB, FMADD, FMSUB,
  FNMADD and FNMSUB.
- Rounding: FRINTN, FRINTP, FRINTM, FRINTZ, FRINTA, FRINTX and FRINTI.
- Conversions: SCVTF (fixed-point), SCVTF (integer), UCVTF (fixed-point)
  UCVTF (integer), FCVTZS (fixed-point), FCVTZS (integer), FCVTZU
  (fixed-point), FCVTZU (integer), FCVTNS, FCVTNU, FCVTAS, FCVTAU,
  FCVTPS, FCVTPU, FCVTMS and  FCVTMU.
- Scalar FMOV: immediate, general and register

gas/testsuite/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* gas/aarch64/float-fp16.d: New.
	* gas/aarch64/float-fp16.s: New.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.
	* aarch64-tbl.h (QL_FIX2FP_H, QL_FP2FIX_H): New.
	(QL_INT2FP_H, QL_FP2INT_H): New.
	(QL_FP2_H, QL_FP3_H, QL_FP4_H): New
	(QL_DST_H): New.
	(QL_FCCMP_H): New.
	(aarch64_opcode_table): Add 16-bit variants of scvt, ucvtf,
	fcvtzs, fcvtzu, fcvtns, fcvtnu, scvtf, ucvtf, fcvtas, fcvtau,
	fmov, fcvtpos, fcvtpu, fcvtms, fcvtmu, fcvtzs, fcvtzu, fccmp,
	fccmpe, fcmp, fcmpe, fabs, fneg, fsqrt, frintn, frintp, frintm,
	frintz, frinta, frintx, frinti, fmul, fdiv, fadd, fsub, fmax,
	fmin, fmaxnm, fminnm, fnmul, fmadd, fmsub, fnmadd, fnmsub and
	fcsel.

Change-Id: Ie6d40bd1b215a9bc024e12ba75e52afbe1675eb7


^ permalink raw reply	[flat|nested] 1903+ messages in thread
* [binutils-gdb] [AArch64][PATCH 2/3] Adjust a utility function for floating point values.
@ 2015-11-27 16:42 sergiodj+buildbot
  2015-11-28 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 1903+ messages in thread
From: sergiodj+buildbot @ 2015-11-27 16:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf86120bae8973340583a0613ad622f0ca013efd ***

Author: Matthew Wahab <matthew.wahab@arm.com>
Branch: master
Commit: cf86120bae8973340583a0613ad622f0ca013efd

[AArch64][PATCH 2/3] Adjust a utility function for floating point values.

ARMv8.2 adds 16-bit floating point operations as an optional
extension. This patch adjusts the utility function expand_fp_imm to
support 16-bit values.

The function is intended to convert an 8-bit immediate representing a
floating point value to a representation that can be passed to
fprintf. Because of the limited use of the results, the only change made
to the function is to treat a request for a 16-bit float as a request
for a 32-bit float.

opcodes/
2015-11-27  Matthew Wahab  <matthew.wahab@arm.com>

	* aarch64-opc.c (half_conv_t): New.
	(expand_fp_imm): Replace is_dp flag with the parameter size to
	specify the number of bytes for the required expansion.  Treat
	a 16-bit expansion like a 32-bit expansion.  Add check for an
	unsupported size request.  Update comment.
	(aarch64_print_operand): Update to support 16-bit floating point
	values.  Update for changes to expand_fp_imm.

Change-Id: I1ae3df3864be375d71925197ab03397ed1ad2d15


^ permalink raw reply	[flat|nested] 1903+ messages in thread
end of thread, other threads:[~2017-01-14 14:42 UTC | newest]

Thread overview: 1903+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-13 17:42 [binutils-gdb] S/390: Fix kmctr instruction type sergiodj+buildbot
2016-09-13 17:43 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2016-09-13 17:56 ` Failures on Debian-i686, " sergiodj+buildbot
2016-09-13 18:02 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:18 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:20 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:30 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:32 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:40 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-13 18:59 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-09-13 19:11 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-13 20:02 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-09-13 20:25 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
     [not found] <@gdb-build>
2016-12-13 17:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-12-13 18:45 ` sergiodj+buildbot
2016-12-14  6:58 ` sergiodj+buildbot
2016-12-14  7:22 ` sergiodj+buildbot
2016-12-14  8:03 ` sergiodj+buildbot
2016-12-14  8:19 ` sergiodj+buildbot
2016-12-14  8:55 ` sergiodj+buildbot
2016-12-14 23:16 ` sergiodj+buildbot
2016-12-14 23:55 ` sergiodj+buildbot
2016-12-15  0:23 ` sergiodj+buildbot
2016-12-15  1:04 ` sergiodj+buildbot
2016-12-15  4:09 ` sergiodj+buildbot
2016-12-15 15:47 ` sergiodj+buildbot
2016-12-16  5:37 ` sergiodj+buildbot
2016-12-16 12:02 ` sergiodj+buildbot
2016-12-16 15:01 ` sergiodj+buildbot
2016-12-19 12:48 ` sergiodj+buildbot
2016-12-19 13:05 ` sergiodj+buildbot
2016-12-19 14:14 ` sergiodj+buildbot
2016-12-19 16:49 ` sergiodj+buildbot
2016-12-20  2:39 ` sergiodj+buildbot
2016-12-20  2:43 ` sergiodj+buildbot
2016-12-20  2:45 ` sergiodj+buildbot
2016-12-20  2:48 ` sergiodj+buildbot
2016-12-20  2:50 ` sergiodj+buildbot
2016-12-20  3:42 ` sergiodj+buildbot
2016-12-20  4:44 ` sergiodj+buildbot
2016-12-20  5:00 ` sergiodj+buildbot
2016-12-23 13:51 ` sergiodj+buildbot
2016-12-23 14:30 ` sergiodj+buildbot
2016-12-23 14:31 ` sergiodj+buildbot
2016-12-23 15:11 ` sergiodj+buildbot
2016-12-23 15:50 ` sergiodj+buildbot
2016-12-23 16:31 ` sergiodj+buildbot
2016-12-23 17:11 ` sergiodj+buildbot
2016-12-23 17:59 ` sergiodj+buildbot
2016-12-23 18:32 ` sergiodj+buildbot
2016-12-23 19:07 ` sergiodj+buildbot
2016-12-23 20:43 ` sergiodj+buildbot
2016-12-23 20:55 ` sergiodj+buildbot
2016-12-23 21:10 ` sergiodj+buildbot
2016-12-23 21:30 ` sergiodj+buildbot
2016-12-23 22:16 ` sergiodj+buildbot
2016-12-23 22:50 ` sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2016-12-13  0:21 [binutils-gdb] Don't add PHDR for objcopy/strip or ld script specifying PHDRS sergiodj+buildbot
2016-12-20  2:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-23 13:19 ` sergiodj+buildbot
2016-12-12 23:39 [binutils-gdb] Don't fudge p_vaddr when PHDR in segment sergiodj+buildbot
2017-01-14 14:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-12 18:30 [binutils-gdb] Port c++/78252 from GCC sergiodj+buildbot
2016-12-12 19:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-12 10:51 [binutils-gdb] Remove assert on exec_bfd in cris_delayed_get_disassembler sergiodj+buildbot
2016-12-12 14:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-12 10:38 [binutils-gdb] Handle memory error in print_insn_rx sergiodj+buildbot
2016-12-12 12:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-12  9:28 [binutils-gdb] Handle memory error in print_insn_rl78_common sergiodj+buildbot
2016-12-12 11:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-09 17:14 [binutils-gdb] Create tdep->rx_psw_type and tdep->rx_fpsw_type lazily sergiodj+buildbot
2016-12-10  0:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-09 11:10 [binutils-gdb] Use code cache in arm prologue analyzer sergiodj+buildbot
2016-12-09 20:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 17:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-09  0:14 [binutils-gdb] AArch64/opcodes: Correct another `index' global shadowing error sergiodj+buildbot
2016-12-09  1:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-08 11:25 [binutils-gdb] Hurd, C++: Mach/Hurd headers and MIG stubs are not yet fit for C++ sergiodj+buildbot
2016-12-08 13:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-08  9:00 [binutils-gdb] Hurd, C++: Avoid GNU C nested functions sergiodj+buildbot
2016-12-08 10:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-08  8:11 [binutils-gdb] Hurd, C++: Explicitly cast "void *" sergiodj+buildbot
2016-12-08  9:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-07 14:36 [binutils-gdb] MIPS/opcodes: Correct an `interaction' comment typo sergiodj+buildbot
2016-12-07 18:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-05 16:45 [binutils-gdb] [ARM] Add ARMv8.3 VCMLA and VCADD instructions sergiodj+buildbot
2016-12-05 21:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-05 16:01 [binutils-gdb] [ARM] Add ARMv8.3 VJCVT instruction sergiodj+buildbot
2016-12-05 19:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-05 15:01 [binutils-gdb] bfd, ld: Continue after partially-successful relaxed call relocations in sparc sergiodj+buildbot
2016-12-05 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-05 14:06 [binutils-gdb] Fix seg-fault attempting to strip a corrupt binary sergiodj+buildbot
2016-12-05 15:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-05 12:47 [binutils-gdb] Fix assertion failure in linker triggered by corrupt input file sergiodj+buildbot
2016-12-05 13:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-03 13:02 [binutils-gdb] Tidy ppc64_elf_hide_symbol sergiodj+buildbot
2016-12-04  4:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02 20:34 [binutils-gdb] Test user-defined gdb commands and arguments stack sergiodj+buildbot
2016-12-03 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02 18:11 [binutils-gdb] Revert change to gdb.cp/ovldbreak.exp sergiodj+buildbot
2016-12-03 14:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02 17:12 [binutils-gdb] Fix seg-fault in the linker when examining a corrupt binary sergiodj+buildbot
2016-12-03 13:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02 16:48 [binutils-gdb] PR symtab/16264 - support DW_AT_main_subprogram sergiodj+buildbot
2016-12-03 12:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02 10:50 [binutils-gdb] [AArch64] Recognize STR instruction in prologue sergiodj+buildbot
2016-12-02 20:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02  6:01 [binutils-gdb] Don't handle timeout inside gdb_test_multiple sergiodj+buildbot
2016-12-02 17:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02  5:34 [binutils-gdb] Class-ify ui_out_table sergiodj+buildbot
2016-12-02 16:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02  4:41 [binutils-gdb] Simplify ui-out level code sergiodj+buildbot
2016-12-02 15:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02  3:57 [binutils-gdb] Class-ify ui_out_level sergiodj+buildbot
2016-12-02 13:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-02  2:49 [binutils-gdb] Class-ify ui_out_hdr sergiodj+buildbot
2016-12-02 11:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-01 22:09 [binutils-gdb] Fix test names starting with uppercase using gdb_test_no_output sergiodj+buildbot
2016-12-02  0:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-01 21:12 [binutils-gdb] Fix test names starting with uppercase output by basic functions sergiodj+buildbot
2016-12-01 22:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-12-01 14:12 [binutils-gdb] Fix accesses to the GOT for AARCH64 operating in 32-bit mode sergiodj+buildbot
2016-12-01 17:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-30 21:56 [binutils-gdb] Makefiles: Disable suffix rules and implicit rules sergiodj+buildbot
2016-12-01  0:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-30 12:39 [binutils-gdb] [ARM] Read memory as unsigned integer sergiodj+buildbot
2016-11-30 15:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-28 16:35 [binutils-gdb] Properly hide hidden versioned symbol in executable sergiodj+buildbot
2016-11-28 17:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-25 16:29 [binutils-gdb] Fix typo in comment sergiodj+buildbot
2016-11-25 16:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-25 15:36 [binutils-gdb] Fix typos in comment sergiodj+buildbot
2016-11-25 16:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-24 21:27 [binutils-gdb] Do not use std::move when assigning an anonymous object to a unique_ptr sergiodj+buildbot
2016-11-25  1:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-24 19:17 [binutils-gdb] Optimize byte-aligned copies in copy_bitwise() sergiodj+buildbot
2016-11-24 21:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-24 19:13 [binutils-gdb] Add unit test for copy_bitwise sergiodj+buildbot
2016-11-24 20:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-24 14:48 [binutils-gdb] [ARM] Bind defined symbol locally in PIE sergiodj+buildbot
2016-11-24 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-23 16:36 [binutils-gdb] Normalize names of some source files sergiodj+buildbot
2016-11-23 21:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-23 15:19 [binutils-gdb] Makefiles: Flatten and sort file lists sergiodj+buildbot
2016-11-23 20:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-23  8:40 [binutils-gdb] Delete duplicate target short-cuts to dynamic sections sergiodj+buildbot
2016-11-23 15:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-23  7:46 [binutils-gdb] Regen POTFILES.in sergiodj+buildbot
2016-11-23 14:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-22 20:47 [binutils-gdb] gdbarch software_single_step frame_info to regcache: s390 sergiodj+buildbot
2016-11-23  2:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-22 20:15 [binutils-gdb] gdbarch software_single_step frame_info to regcache: sparc sergiodj+buildbot
2016-11-23  0:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-22 18:47 [binutils-gdb] gdbarch software_single_step frame_info to regcache: moxie sergiodj+buildbot
2016-11-22 22:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-22 17:26 [binutils-gdb] gdbarch software_single_step frame_info to regcache: cris sergiodj+buildbot
2016-11-22 19:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-22 16:56 [binutils-gdb] gdbarch software_single_step frame_info to regcache: alpha sergiodj+buildbot
2016-11-22 18:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-22 10:39 [binutils-gdb] Use input_bfd in relocate_section sergiodj+buildbot
2016-11-22 11:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-21 21:38 [binutils-gdb] Add missing POSTCOMPILE step to mi/ file generation rules sergiodj+buildbot
2016-11-22  2:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-21 14:37 [binutils-gdb] Create subobject value in pretty printer sergiodj+buildbot
2016-11-21 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 12:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-18 11:23 [binutils-gdb] [AArch64] Add ARMv8.3 combined pointer authentication load instructions sergiodj+buildbot
2016-11-18 12:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 12:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-17 20:10 [binutils-gdb] Makefile: Replace explicit subdir rules with pattern rules sergiodj+buildbot
2016-11-17 23:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-17 19:35 [binutils-gdb] Makefile: Replace old suffix rules with pattern rules sergiodj+buildbot
2016-11-17 22:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-17 18:31 [binutils-gdb] Document new hard requirement on GNU make sergiodj+buildbot
2016-11-17 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-17 16:49 [binutils-gdb] gdb/c-exp.y: fprintf -> parser_fprintf sergiodj+buildbot
2016-11-17 17:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-16 22:04 [binutils-gdb] Change meaning of VALUE_FRAME_ID; rename to VALUE_NEXT_FRAME_ID sergiodj+buildbot
2016-11-17  1:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-16 21:50 [binutils-gdb] Distinguish sentinel frame from null frame sergiodj+buildbot
2016-11-17  0:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-16 20:03 [binutils-gdb] Extend test gdb.python/py-recurse-unwind.exp sergiodj+buildbot
2016-11-16 22:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-16 20:01 [binutils-gdb] Fix PR20789 - relaxation with negative valued diff relocs sergiodj+buildbot
2016-11-16 21:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-15 20:24 [binutils-gdb] bitfield-parent-optimized-out: Fix struct definition sergiodj+buildbot
2016-11-15 21:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-14 10:28 [binutils-gdb] btrace: read entire aux buffer sergiodj+buildbot
2016-11-14 13:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-14  9:18 [binutils-gdb] Fix typo "Faal through" should be "Fall through" sergiodj+buildbot
2016-11-14 10:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-11 15:42 [binutils-gdb] [AArch64] Add ARMv8.3 instructions which are in the NOP space sergiodj+buildbot
2016-11-11 17:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-11 13:30 [binutils-gdb] [AArch64] Add ARMv8.3 command line option and feature flag sergiodj+buildbot
2016-11-11 15:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-11 12:02 [binutils-gdb] Remove apply_val_pretty_printer parameter valaddr sergiodj+buildbot
2016-11-11 13:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-11 10:40 [binutils-gdb] Remove parameter valaddr from c print functions sergiodj+buildbot
2016-11-11 12:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-11 10:09 [binutils-gdb] sim: mips: fix dv-tx3904cpu build error sergiodj+buildbot
2016-11-11 11:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  9:30 [binutils-gdb] [AArch64] Bind defined symbol locally in PIE sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  8:07 [binutils-gdb] tui-disasm: Fix window content buffer overrun sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  7:49 [binutils-gdb] Use unique_xmalloc_ptr in Python code sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  7:48 [binutils-gdb] Further cleanup/modernization of gdb.base/commands.exp sergiodj+buildbot
2016-11-10 11:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  7:47 [binutils-gdb] X86: Merge AVX512F vmovq sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  7:47 [binutils-gdb] X86: Remove the .s suffix from EVEX vpextrw sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  7:45 [binutils-gdb] gdb/testsuite: Introduce "proc_with_prefix" sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  6:36 [binutils-gdb] tui-winsource: Remove failed-allocation logic sergiodj+buildbot
2016-11-10 12:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  5:47 [binutils-gdb] gdb: Use vector::emplace_back sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  4:19 [binutils-gdb] tui-disasm: Fix line buffer size calculation sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  3:59 [binutils-gdb] tui-winsource: Allocate for actual lines only sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-10  1:21 [binutils-gdb] darwin-nat.c: handle Darwin 16 (aka Sierra) sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09 23:50 [binutils-gdb] Fix py-value.exp failure on Python 3 sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09 23:16 [binutils-gdb] X86: Remove the THREE_BYTE_0F7A entry sergiodj+buildbot
2016-11-10 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09 20:30 [binutils-gdb] Remove parameter valaddr from la_val_print sergiodj+buildbot
2016-11-10 11:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09 17:48 [binutils-gdb] 'struct agent_expr *' -> unique_ptr<agent_expr> sergiodj+buildbot
2016-11-10 11:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  5:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09  9:53 [binutils-gdb] Use ui_file_as_string in gdb/cli/cli-setshow.c sergiodj+buildbot
2016-11-09 16:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09  8:18 [binutils-gdb] Use ui_file_as_string in gdb/remote.c sergiodj+buildbot
2016-11-09 15:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09  8:07 [binutils-gdb] Use ui_file_as_string in gdb/python/ sergiodj+buildbot
2016-11-09 13:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-09  6:37 [binutils-gdb] Use ui_file_as_string in gdb/printcmd.c sergiodj+buildbot
2016-11-09 12:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-08 14:21 [binutils-gdb] Fix PR breakpoints/20739: Badly formatted adress string in error message sergiodj+buildbot
2016-11-08 14:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-08 12:26 [binutils-gdb] Fix indentation sergiodj+buildbot
2016-11-08 12:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-08 11:14 [binutils-gdb] Check for truncated registers in process_g_packet sergiodj+buildbot
2016-11-08 12:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-07 21:48 [binutils-gdb] Sync config.sub,config.guess with upstream sergiodj+buildbot
2016-11-07 22:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-04 23:14 [binutils-gdb] arc/nps400: Validate address type operands correctly sergiodj+buildbot
2016-11-05  0:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-03 23:05 [binutils-gdb] Fix handling of discriminantless univariant enums in Rust; fix bug with encoded enums sergiodj+buildbot
2016-11-04 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-03 18:59 [binutils-gdb] arc: Implement NPS-400 dcmac instruction sergiodj+buildbot
2016-11-04 14:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-03 15:50 [binutils-gdb] Remove gdbarch_remote_breakpoint_from_pc sergiodj+buildbot
2016-11-03 22:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-11-01 23:28 [binutils-gdb] BFD: Fix double BFD_FAIL calls in `bfd_default_reloc_type_lookup' sergiodj+buildbot
2016-11-02 19:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-17 23:24 [binutils-gdb] Fix duplicate test message in mi-trace-save.exp sergiodj+buildbot
2016-10-17 23:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-17 21:50 [binutils-gdb] Fix comment in mi-trace-save.exp sergiodj+buildbot
2016-10-17 22:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-17 16:34 [binutils-gdb] gdb: Fix phony iconv build sergiodj+buildbot
2016-10-17 16:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-17 13:56 [binutils-gdb] Removed pseudo invalid instructions opcodes sergiodj+buildbot
2016-10-17 15:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-17 11:03 [binutils-gdb] Update list of ELF machine numbers sergiodj+buildbot
2016-10-17 12:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-17  9:46 [binutils-gdb] Sync libiberty sources with gcc mainline sergiodj+buildbot
2016-10-17 10:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-14 13:25 [binutils-gdb] Fix set sysroot command on AIX sergiodj+buildbot
2016-10-14 14:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-13 15:27 [binutils-gdb] Share proc get_var_address sergiodj+buildbot
2016-10-13 17:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  6:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-13  4:50 [binutils-gdb] Remove unnecessary null_cleanup sergiodj+buildbot
2016-10-13  5:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-13  2:59 [binutils-gdb] Turn wchar iterator into a class sergiodj+buildbot
2016-10-13  4:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-12 16:00 [binutils-gdb] arc: Add support for Newlib sergiodj+buildbot
2016-10-12 17:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-12 13:32 [binutils-gdb] arc: Add evaluation of long jump targets sergiodj+buildbot
2016-10-12 16:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-11 23:35 [binutils-gdb] BFD_FAKE_SECTION macro params sergiodj+buildbot
2016-10-12  0:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-11  7:59 [binutils-gdb] Always descend into output section statements in lang_do_assignments sergiodj+buildbot
2016-10-11  8:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-10 10:37 [binutils-gdb] Rename 'arch' by 'gdbarch' in m32c_gdbarch_init sergiodj+buildbot
2016-10-10 11:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-07  7:22 [binutils-gdb] python: accept address and explicit locations in gdb.decode_line sergiodj+buildbot
2016-10-07 13:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  8:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 12:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-06 23:29 [binutils-gdb] gdb: Remove some C compiler support leftovers sergiodj+buildbot
2016-10-07  9:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-06 21:27 [binutils-gdb] Remove Java support sergiodj+buildbot
2016-10-06 21:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-06 17:57 [binutils-gdb] mips-tdep: Make FCRs always 32-bit sergiodj+buildbot
2016-10-06 20:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-06  0:52 [binutils-gdb] -Wimplicit-fallthrough error fixes sergiodj+buildbot
2016-10-06  5:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-06  0:04 [binutils-gdb] Don't use boolean OR in arithmetic expressions sergiodj+buildbot
2016-10-06  4:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 21:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-05 13:07 [binutils-gdb] Allow DW_OP_GNU_uninit in dwarf_expr_require_composition sergiodj+buildbot
2016-10-05 16:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-05  9:34 [binutils-gdb] Regenerate some regformats/rs6000/*.dat files sergiodj+buildbot
2016-10-05 13:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-10-05  8:44 [binutils-gdb] Clean up the XML files for ARM sergiodj+buildbot
2016-10-05  9:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-30 17:36 [binutils-gdb] [AArch64] PR target/20553, fix opcode mask for SIMD multiply by element sergiodj+buildbot
2016-09-30 18:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-30 15:11 [binutils-gdb] Remove syntactic sugar sergiodj+buildbot
2016-09-30 16:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-30 14:26 [binutils-gdb] Make bfd_error_handler_type like vprintf sergiodj+buildbot
2016-09-30 15:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 13:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-30  9:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-29 17:39 [binutils-gdb] Disallow 3-operand cmp[l][i] for ppc64 sergiodj+buildbot
2016-09-29 19:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  2:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 22:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-27  2:10 [binutils-gdb] When building target binaries, ensure that the warning flags selected for the command line match the target compiler sergiodj+buildbot
2016-09-27  3:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-26 22:57 [binutils-gdb] Fix the calculation of AMD64_PCRQUAD relocations sergiodj+buildbot
2016-09-27  2:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-26 19:24 [binutils-gdb] [ARC] ISA alignment sergiodj+buildbot
2016-09-27  1:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-26 16:58 [binutils-gdb] PowerPC .gnu.attributes sergiodj+buildbot
2016-09-26 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-26 11:09 [binutils-gdb] Call debug_exit in linux_wait_1 sergiodj+buildbot
2016-09-26 16:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  9:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-24  7:30 [binutils-gdb] Use std::string rather than dyn-string sergiodj+buildbot
2016-09-24 21:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-24  4:16 [binutils-gdb] Use std::vector in objfiles.c sergiodj+buildbot
2016-09-24 19:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-23 20:08 [binutils-gdb] gdb: Replace operator new / operator new[] sergiodj+buildbot
2016-09-24  8:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-23 19:06 [binutils-gdb] Delete relocations associatesd with deleted exidx entries sergiodj+buildbot
2016-09-24  5:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-23  0:46 [binutils-gdb] Close gdbserver in mi_gdb_exit sergiodj+buildbot
2016-09-24  1:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 23:04 [binutils-gdb] Fix build breakage from commit 6ec2b2 sergiodj+buildbot
2016-09-23 23:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 21:20 [binutils-gdb] Use gdbserver-base in remote-gdbserver-on-localhost.exp sergiodj+buildbot
2016-09-23 21:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 20:53 [binutils-gdb] arc: Fix ARI warning for printf(%p) sergiodj+buildbot
2016-09-23 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 19:54 [binutils-gdb] Check the right proc name sergiodj+buildbot
2016-09-23 18:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 17:56 [binutils-gdb] Add myself as a write-after-approval GDB maintainer sergiodj+buildbot
2016-09-23 18:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 17:43 [binutils-gdb] arc: New Synopsys ARC port sergiodj+buildbot
2016-09-23 17:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 16:46 [binutils-gdb] ppc: Fix return of instruction handlers in ppc_process_record_op63 sergiodj+buildbot
2016-09-23 17:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 14:56 [binutils-gdb] PR gdb/20604 - fix "quit" when an invalid expression is used sergiodj+buildbot
2016-09-23 16:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 14:12 [binutils-gdb] Update and add .gitignore's sergiodj+buildbot
2016-09-23 16:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 13:27 [binutils-gdb] ppc: Add Power ISA 3.0/POWER9 instructions record support sergiodj+buildbot
2016-09-23 11:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 12:46 [binutils-gdb] [AArch64] Print spaces after commas in addresses sergiodj+buildbot
2016-09-23  8:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 11:51 [binutils-gdb] [AArch64] Add SVE condition codes sergiodj+buildbot
2016-09-23  6:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22 10:26 [binutils-gdb] [AArch64][SVE 31/32] Add SVE instructions sergiodj+buildbot
2016-09-23  4:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22  9:37 [binutils-gdb] [AArch64][SVE 29/32] Add new SVE core & FP register operands sergiodj+buildbot
2016-09-22 23:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22  9:31 [binutils-gdb] [AArch64][SVE 30/32] Add SVE instruction classes sergiodj+buildbot
2016-09-23  2:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 18:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22  6:53 [binutils-gdb] [AArch64][SVE 25/32] Add support for SVE addressing modes sergiodj+buildbot
2016-09-22 17:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 14:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-22  1:25 [binutils-gdb] [AArch64][SVE 19/32] Refactor address-printing code sergiodj+buildbot
2016-09-22  7:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  6:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  5:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-21 23:35 [binutils-gdb] [AArch64][SVE 16/32] Use specific insert/extract methods for fpimm sergiodj+buildbot
2016-09-22  3:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  1:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-22  0:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 22:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-21 17:21 [binutils-gdb] MIPS/testsuite: mips16-thunks: Use `standard_output_file' sergiodj+buildbot
2016-09-21 19:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-21 15:44 [binutils-gdb] Keep reserved bits in CPSR on write sergiodj+buildbot
2016-09-21 17:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-20 21:40 [binutils-gdb] Avoid -Wduplicated-cond warnings in gdb/python sergiodj+buildbot
2016-09-21 13:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 22:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 12:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-19 23:22 [binutils-gdb] bfd: allow negative offsets to _GLOBAL_OFFSET_TABLE_ in elf64 SPARC sergiodj+buildbot
2016-09-20  5:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-19 16:45 [binutils-gdb] Consolidate target_mourn_inferior between GDB and gdbserver sergiodj+buildbot
2016-09-19 22:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-18 23:24 [binutils-gdb] Improve MinGW support in Readline sergiodj+buildbot
2016-09-19  5:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-17  5:15 [binutils-gdb] Introduce cleanup to restore current_uiout sergiodj+buildbot
2016-09-19  4:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-17  3:34 [binutils-gdb] gdb: Use std::min and std::max throughout sergiodj+buildbot
2016-09-19  2:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-17  1:02 [binutils-gdb] S390: Hardware breakpoint support sergiodj+buildbot
2016-09-19  1:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-17  0:28 [binutils-gdb] linux-nat: Add function lwp_is_stepping sergiodj+buildbot
2016-09-19  0:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-16 23:32 [binutils-gdb] S390: Enable "maint set show-debug-regs" sergiodj+buildbot
2016-09-17 15:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-16 23:12 [binutils-gdb] S390: Multi-inferior watchpoint support sergiodj+buildbot
2016-09-17  3:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  1:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-16 21:38 [binutils-gdb] S390: Avoid direct access to lwp_info structure sergiodj+buildbot
2016-09-16 23:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 22:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-16 19:43 [binutils-gdb] [ARC] Disassemble correctly extension instructions sergiodj+buildbot
2016-09-16 20:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-16 14:17 [binutils-gdb] Update ISA 3.0 / POWER9 gdb tests to match GAS test cases sergiodj+buildbot
2016-09-16 17:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-15 23:31 [binutils-gdb] testsuite: Disable ccache sergiodj+buildbot
2016-09-16  2:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 13:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-15  3:38 [binutils-gdb] Fix seg-fault in objdump when run on a fuzzed PE binary sergiodj+buildbot
2016-09-15  5:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 21:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 14:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-13 18:36 [binutils-gdb] S/390: Add alternate processor names sergiodj+buildbot
2016-09-13 20:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 18:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-12 15:28 [binutils-gdb] Use target_sim_options for sim target sergiodj+buildbot
2016-09-12 16:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-10 23:25 [binutils-gdb] Pass HWCAP to ifunc resolver sergiodj+buildbot
2016-09-12  6:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-10 20:57 [binutils-gdb] Remove some unneeded casts from remote.c sergiodj+buildbot
2016-09-10 21:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-08  0:06 [binutils-gdb] X86: Allow additional ISAs for IAMCU in assembler sergiodj+buildbot
2016-09-08 21:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-08  6:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-07  5:56 [binutils-gdb] Introduce make_cleanup_restore_current_ui sergiodj+buildbot
2016-09-07 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-07  1:30 [binutils-gdb] Resolve size relocation with copy relocation sergiodj+buildbot
2016-09-07 17:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-07  0:07 [binutils-gdb] Add gdbarch callback to provide formats for debug info float types sergiodj+buildbot
2016-09-07 15:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 23:33 [binutils-gdb] Remove TYPE_NOSIGN "char" hack sergiodj+buildbot
2016-09-07  1:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 22:01 [binutils-gdb] Remove obsolete TYPE_FLAG_... values sergiodj+buildbot
2016-09-07  0:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 21:12 [binutils-gdb] Unify init_type and arch_type interface and helpers sergiodj+buildbot
2016-09-06 23:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 20:46 [binutils-gdb] Add some missing arch_..._type helpers sergiodj+buildbot
2016-09-06 22:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 21:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 18:54 [binutils-gdb] Fix typo in ada_language_arch_info sergiodj+buildbot
2016-09-06 19:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 18:00 [binutils-gdb] Fix PR ld/20545 - relaxation bugs in avr backend sergiodj+buildbot
2016-09-06 18:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-06 16:28 [binutils-gdb] gdb/: Require a C++ compiler sergiodj+buildbot
2016-09-06 17:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-05 19:41 [binutils-gdb] Removed redundant line remote-utils.c sergiodj+buildbot
2016-09-05 22:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-03 12:46 [binutils-gdb] Handle DW_OP_form_tls_address sergiodj+buildbot
2016-09-05 18:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-02 22:03 [binutils-gdb] [GDBserver] Replace "reinsert_breakpoint" with "single_step_breakpoint" sergiodj+buildbot
2016-09-03 12:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-09-01 20:40 [binutils-gdb] Don't treat .opd section specially when ELFv2 sergiodj+buildbot
2016-09-01 21:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-31 20:01 [binutils-gdb] Fix a typo in comment sergiodj+buildbot
2016-08-31 22:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-31 19:13 [binutils-gdb] PowerPC64, correct grouping of stubs for ld.bfd sergiodj+buildbot
2016-08-31 19:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-31 18:21 [binutils-gdb] PowerPC VLE sh_flags and p_flags sergiodj+buildbot
2016-08-31 18:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-30 18:41 [binutils-gdb] ppc apuinfo for spe parsed incorrectly sergiodj+buildbot
2016-08-30 19:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 14:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-27 12:09 [binutils-gdb] Fix commit 980aa3e6 sergiodj+buildbot
2016-08-29 14:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  3:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  7:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-26 17:28 [binutils-gdb] Add missing ARMv8-M special registers sergiodj+buildbot
2016-08-27  1:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-26 16:28 [binutils-gdb] Fixed -init, -fini linker options sergiodj+buildbot
2016-08-26 18:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-26 15:37 [binutils-gdb] Fixes to legacy ARC relocations sergiodj+buildbot
2016-08-26 15:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-26 12:23 [binutils-gdb] S390: Add support for core dump NOTE sections sergiodj+buildbot
2016-08-26 13:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-25 10:27 [binutils-gdb] Sync proc_service definition with GLIBC sergiodj+buildbot
2016-08-25 14:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-24 20:24 [binutils-gdb] Allow resetting an empty inferior-tty sergiodj+buildbot
2016-08-25  9:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-24 18:02 [binutils-gdb] [ARC] Parse NOTE section in core dump files sergiodj+buildbot
2016-08-25  8:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-24  0:00 [binutils-gdb] Fix typo in comment sergiodj+buildbot
2016-08-24  0:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-23 22:53 [binutils-gdb] Fix PR20494 - User input stops being echoed in CLI sergiodj+buildbot
2016-08-23 23:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-23 17:39 [binutils-gdb] gdbserver_spawn "" rather than gdbserver_spawn ${binfile} sergiodj+buildbot
2016-08-23 22:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  9:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-22 20:15 [binutils-gdb] Error on unsupported PowerPC ifuncs sergiodj+buildbot
2016-08-22 21:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  7:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-19 18:19 [binutils-gdb] x32: gdb: Fix 'call' insn relocation with qRelocInsn sergiodj+buildbot
2016-08-19 18:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 14:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-19 12:02 [binutils-gdb] PR 20472, PowerPC64 ifunc confusion sergiodj+buildbot
2016-08-19 13:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-19  5:31 [binutils-gdb] Add myself as write-after-approval GDB maintainer sergiodj+buildbot
2016-08-19  6:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-18 14:37 [binutils-gdb] Add remove-inferiors test sergiodj+buildbot
2016-08-18 15:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-17 21:25 [binutils-gdb] sim: m68hc11: use standard STATIC_INLINE helper sergiodj+buildbot
2016-08-17 21:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-15 12:44 [binutils-gdb] sim: m68hc11: fix up various prototype related warnings sergiodj+buildbot
2016-08-15 13:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-13 21:55 [binutils-gdb] Correct .dynsym sh_info sergiodj+buildbot
2016-08-13 22:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-12 13:46 [binutils-gdb] Fix warning in gdb.base/signals-state-child.c sergiodj+buildbot
2016-08-13 21:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-12 11:02 [binutils-gdb] Export the single step function from the AArch64 simulator sergiodj+buildbot
2016-08-13 20:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-11  1:27 [binutils-gdb] MIPS/BFD: Actually produce short microMIPS LA25 stubs sergiodj+buildbot
2016-08-11  9:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-11  0:35 [binutils-gdb] Support setting thread names (MS-Windows) sergiodj+buildbot
2016-08-11  0:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-10 21:20 [binutils-gdb] Quiet ARI gettext checks sergiodj+buildbot
2016-08-10 23:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 23:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-09 20:38 [binutils-gdb] Correct the calculation of the use_counts of merged .got entries sergiodj+buildbot
2016-08-09 21:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-09  7:29 [binutils-gdb] Regenerate some target description files sergiodj+buildbot
2016-08-09 12:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-08 16:36 [binutils-gdb] Fix memory leaks in chew program sergiodj+buildbot
2016-08-09 12:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-05 22:57 [binutils-gdb] Remove unused cli_command_loop declaration sergiodj+buildbot
2016-08-06  3:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-05 20:42 [binutils-gdb] Fix PR remote/20398: File-IO write always outputs "Quit" sergiodj+buildbot
2016-08-06  2:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 18:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 21:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-04 16:00 [binutils-gdb] 2016-08-04 Thomas Preud'homme <thomas.preudhomme@arm.com> sergiodj+buildbot
2016-08-04 18:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-03 16:11 [binutils-gdb] Add myself as Rust maintainer sergiodj+buildbot
2016-08-03 16:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 13:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-08-01 13:20 [binutils-gdb] Swap "single-process" and "multi-process" in process-dies-while-detaching.exp sergiodj+buildbot
2016-08-01 14:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <147d994bcdd36a177e49e7b6ac8d9c1f7b4cdcf5@gdb-build>
2016-07-28  6:28 ` sergiodj+buildbot
     [not found] <40c31709c6a51926fcb409611caa52b2da6515c0@gdb-build>
2016-07-27 16:41 ` sergiodj+buildbot
     [not found] <e0461dbb653dbb3c46ea7a15054fd2c98f879f31@gdb-build>
2016-07-27  1:25 ` sergiodj+buildbot
     [not found] <3a1518e4f3c467cfee2786b0af3388529f14d23b@gdb-build>
2016-07-25 19:01 ` sergiodj+buildbot
     [not found] <e34879080d8935792ef3942efa5f25b4c3169b5a@gdb-build>
2016-07-24  6:25 ` sergiodj+buildbot
2016-07-23 19:48 [binutils-gdb] Fix ARMv8.1/v8.2 for hw watchpoint and breakpoint sergiodj+buildbot
2016-07-23 20:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-22 21:05 [binutils-gdb] PR rust/20162 - fix gdb regressions caused by rust 1.10 sergiodj+buildbot
2016-07-23  0:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-22  3:02 [binutils-gdb] Allow empty struct expressions in Rust sergiodj+buildbot
2016-07-22  3:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21 20:40 [binutils-gdb] Fix djgpp gdb build sergiodj+buildbot
2016-07-22  1:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21 19:45 [binutils-gdb] Remove unused variable in windows-nat.c sergiodj+buildbot
2016-07-21 23:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21 15:58 [binutils-gdb] Enqueue signal even when resuming threads sergiodj+buildbot
2016-07-21 19:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21 14:36 [binutils-gdb] Make reinsert_breakpoint thread specific sergiodj+buildbot
2016-07-21 16:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21 13:37 [binutils-gdb] Refactor clone_all_breakpoints sergiodj+buildbot
2016-07-21 15:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21 13:09 [binutils-gdb] Pass breakpoint type in set_breakpoint_at sergiodj+buildbot
2016-07-21 13:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21  9:38 [binutils-gdb] Fix fail in gdb.server/solib-list.exp sergiodj+buildbot
2016-07-21 10:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-21  4:17 [binutils-gdb] Fix implib test failures sergiodj+buildbot
2016-07-21  9:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  2:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-20 20:22 [binutils-gdb] Enable ptrace events on new child processes sergiodj+buildbot
2016-07-21  2:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-20 18:55 [binutils-gdb] Add support to the ARC disassembler for selecting instruction classes sergiodj+buildbot
2016-07-20 21:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-20 18:21 [binutils-gdb] Handle version 1a of FreeBSD's NT_PRSINFO sergiodj+buildbot
2016-07-20 20:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-20 10:29 [binutils-gdb] Enable the configuration of GDB for the NDS32 target sergiodj+buildbot
2016-07-20 14:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-19 16:20 [binutils-gdb] MIPS: Convert cross-mode BAL to JALX sergiodj+buildbot
2016-07-19 17:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-19 10:01 [binutils-gdb] Use do_self_tests in selftest.exp sergiodj+buildbot
2016-07-19 11:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-15 18:48 [binutils-gdb] GDB testsuite: Escape paths used in regular expressions sergiodj+buildbot
2016-07-15 19:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-15 17:10 [binutils-gdb] Add support for creating ELF import libraries sergiodj+buildbot
2016-07-15 17:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-14 21:44 [binutils-gdb] BFD: Let targets handle relocations against absolute symbols sergiodj+buildbot
2016-07-15  2:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-14 18:10 [binutils-gdb] Use getcurx in curses code sergiodj+buildbot
2016-07-14 19:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-14  8:46 [binutils-gdb] [ARC] Fix/improve small data support sergiodj+buildbot
2016-07-14  9:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-13 21:51 [binutils-gdb] PR python/15620, PR python/18620 - breakpoint events in Python sergiodj+buildbot
2016-07-14  6:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-13 20:39 [binutils-gdb] use user_breakpoint_p in python code sergiodj+buildbot
2016-07-13 21:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-13 19:38 [binutils-gdb] Fix PR cli/18053 sergiodj+buildbot
2016-07-13 20:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-13 17:04 [binutils-gdb] MIPS/opcodes: Address issues with NAL disassembly sergiodj+buildbot
2016-07-13 17:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-12 15:23 [binutils-gdb] Second fix for grammar in error message sergiodj+buildbot
2016-07-12 16:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-12 14:56 [binutils-gdb] Match the selftest output when captured_main is inlined sergiodj+buildbot
2016-07-12 15:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-11 14:57 [binutils-gdb] Enable relocation overflow messages by default sergiodj+buildbot
2016-07-11 15:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-08 19:38 [binutils-gdb] FT32: Correct 32-bit reloc for BFD_RELOC_32 sergiodj+buildbot
2016-07-08 20:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-08 19:25 [binutils-gdb] FT32: adjust disassembly opcode match fields sergiodj+buildbot
2016-07-08 19:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-07 17:47 [binutils-gdb] [obv] Fix broken build on Fedora 23 sergiodj+buildbot
2016-07-07 18:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-07 15:52 [binutils-gdb] Fix of default lookup for "this" symbol sergiodj+buildbot
2016-07-07 16:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-06 15:43 [binutils-gdb] Remove extraneous parentheses sergiodj+buildbot
2016-07-06 17:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-06 13:14 [binutils-gdb] Use 'ptid_t' instead of 'ptid' for fbsd_next_vfork_done's return type sergiodj+buildbot
2016-07-06 13:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-06  7:38 [binutils-gdb] [ARM] Fix endless recursion on calculating CPRC candidate sergiodj+buildbot
2016-07-06  8:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 13:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-01 17:17 [binutils-gdb] Honor detach-on-fork on FreeBSD sergiodj+buildbot
2016-07-01 18:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-01 10:53 [binutils-gdb] Factor out "Detaching from program" message printing sergiodj+buildbot
2016-07-01 11:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-07-01  7:09 [binutils-gdb] x86/Intel: fix operand checking for MOVSD sergiodj+buildbot
2016-07-01  7:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-30 15:32 [binutils-gdb] Fix typo in comment sergiodj+buildbot
2016-06-30 16:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-30 11:28 [binutils-gdb] Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work sergiodj+buildbot
2016-06-30 11:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 18:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 17:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-28 17:17 [binutils-gdb] [AArch64] Use int64_t for address offset sergiodj+buildbot
2016-06-28 18:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-28 14:32 [binutils-gdb] Implement get_syscall_trapinfo for arm-linux sergiodj+buildbot
2016-06-28 15:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-28 13:31 [binutils-gdb] Implement get_syscall_trapinfo for aarch64-linux sergiodj+buildbot
2016-06-28 14:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 14:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  9:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-27 12:10 [binutils-gdb] PR 19264 looping in ppc64_elf_size_stubs sergiodj+buildbot
2016-06-27 12:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-25 15:10 [binutils-gdb] Fix formatting in rust-lang.c sergiodj+buildbot
2016-06-25 15:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-23 14:21 [binutils-gdb] PR gdb/16483 - simplify "info frame-filters" output sergiodj+buildbot
2016-06-24  3:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-22 17:38 [binutils-gdb] addmore extern C sergiodj+buildbot
2016-06-24  0:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 23:24 [binutils-gdb] Add "new-ui console" tests sergiodj+buildbot
2016-06-23 18:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 22:18 [binutils-gdb] Always switch fork child to the main UI sergiodj+buildbot
2016-06-23 16:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-23 12:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 19:51 [binutils-gdb] [DOC] Document support for running interpreters on separate UIs sergiodj+buildbot
2016-06-23 11:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 23:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 18:08 [binutils-gdb] Simplify starting the command event loop sergiodj+buildbot
2016-06-21 20:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 18:04 [binutils-gdb] Make stdin be per UI sergiodj+buildbot
2016-06-22 22:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 21:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 11:56 [binutils-gdb] Make current_ui_out be per UI sergiodj+buildbot
2016-06-21 13:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 11:28 [binutils-gdb] Make raw_stdout be per MI instance sergiodj+buildbot
2016-06-21 19:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 10:12 [binutils-gdb] Make target_terminal_inferior/ours almost nops on non-main UIs sergiodj+buildbot
2016-06-21 16:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21 10:04 [binutils-gdb] Make out and error streams be per UI sergiodj+buildbot
2016-06-21 11:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21  9:34 [binutils-gdb] Always process target events in the main UI sergiodj+buildbot
2016-06-21 15:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 14:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21  6:37 [binutils-gdb] Make input_fd be per UI sergiodj+buildbot
2016-06-21 10:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21  4:34 [binutils-gdb] Make the intepreters output to all UIs sergiodj+buildbot
2016-06-21  7:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21  2:22 [binutils-gdb] Make gdb_stdout&co be per UI sergiodj+buildbot
2016-06-21  4:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-21  1:57 [binutils-gdb] Introduce "struct ui" sergiodj+buildbot
2016-06-21  3:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  2:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-20 12:50 [binutils-gdb] Use the IR symbol table for the IR input object sergiodj+buildbot
2016-06-20 13:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  3:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-17 14:33 [binutils-gdb] Delete reinsert breakpoints from forked child sergiodj+buildbot
2016-06-17 18:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-17 12:52 [binutils-gdb] More assert checks on reinsert breakpoint sergiodj+buildbot
2016-06-17 15:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-17 11:35 [binutils-gdb] gdb: new AndesTech NDS32 port sergiodj+buildbot
2016-06-17 13:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-16  2:00 [binutils-gdb] Check SEC_ALLOC before allocating dynamic relocation sergiodj+buildbot
2016-06-16  3:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-15  0:47 [binutils-gdb] Remove unneeded checks on type lengths sergiodj+buildbot
2016-06-15  0:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-14 18:11 [binutils-gdb] Check R_*_IRELATIVE in x86 reloc_type_class sergiodj+buildbot
2016-06-14 21:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-14 17:03 [binutils-gdb] [ARC] Add ldbit for nps sergiodj+buildbot
2016-06-14 18:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-14 15:50 [binutils-gdb] [ARC] Add arithmetic and logic instructions for nps sergiodj+buildbot
2016-06-14 16:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-14 11:26 [binutils-gdb] Fix feature checks based on ARM architecture value sergiodj+buildbot
2016-06-14 12:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-13 17:17 [binutils-gdb] [ARC] Fix condition sergiodj+buildbot
2016-06-13 20:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-13 15:47 [binutils-gdb] [ARC] General bug fixes sergiodj+buildbot
2016-06-13 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-13 14:52 [binutils-gdb] [ARC] Generate DT_RELACOUNT sergiodj+buildbot
2016-06-13 15:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-12  4:48 [binutils-gdb] Subtract GOT base only with a base register sergiodj+buildbot
2016-06-12  5:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-10 16:24 [binutils-gdb] Constify arch_type and friends sergiodj+buildbot
2016-06-10 19:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-10 16:15 [binutils-gdb] Fix PR rust/20110 sergiodj+buildbot
2016-06-10 18:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-10 11:59 [binutils-gdb] S/390: Dump unknown instructions according to their length sergiodj+buildbot
2016-06-10 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-09 16:34 [binutils-gdb] Fix PR 20221 - adjust syms and relocs only if relax shrunk section sergiodj+buildbot
2016-06-09 18:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 17:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-09 12:08 [binutils-gdb] sparc: add missing comment about hyperprivileged register operands sergiodj+buildbot
2016-06-09 12:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-07 16:02 [binutils-gdb] mi/mi-interp.c: Add missing braces sergiodj+buildbot
2016-06-07 17:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-07 13:02 [binutils-gdb] PowerPC VLE sergiodj+buildbot
2016-06-07 13:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-07 11:49 [binutils-gdb] Frame static link: Handle null pointer sergiodj+buildbot
2016-06-07 12:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-06 21:21 [binutils-gdb] Add method/format information to =record-started sergiodj+buildbot
2016-06-06 22:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-03 23:15 [binutils-gdb] Handle indirect branches for AMD64 and Intel64 sergiodj+buildbot
2016-06-04  0:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-02 19:39 [binutils-gdb] Fix PR python/18984 sergiodj+buildbot
2016-06-02 20:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-02 14:30 [binutils-gdb] Replace data32 with data16 in comments sergiodj+buildbot
2016-06-02 15:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-06-01 16:03 [binutils-gdb] Add new Serbian translation for the bfd library sergiodj+buildbot
2016-06-02  1:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 21:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-28 13:19 [binutils-gdb] Add dependencies to configure rule sergiodj+buildbot
2016-05-29 15:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-27 17:19 [binutils-gdb] Update x86 CPU_XXX_FLAGS handling sergiodj+buildbot
2016-05-28 17:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-27 15:15 [binutils-gdb] Replace CpuAMD64/CpuIntel64 with AMD64/Intel64 sergiodj+buildbot
2016-05-28 15:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-27 14:08 [binutils-gdb] Correct CpuMax in i386-opc.h sergiodj+buildbot
2016-05-28  8:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-28  2:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-27 12:46 [binutils-gdb] gdb: Forward VALUE_LVAL when avoiding side effects for STRUCTOP_PTR sergiodj+buildbot
2016-05-27 19:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-25 20:20 [binutils-gdb] MIPS/BFD: Report `bfd_reloc_outofrange' errors as such sergiodj+buildbot
2016-05-25 23:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-25 17:39 [binutils-gdb] Reimplement .no87/.nommx/.nosse/.noavx directives sergiodj+buildbot
2016-05-25 18:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 10:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-24 16:24 [binutils-gdb] add nb_inplace_divide for python 2 sergiodj+buildbot
2016-05-24 22:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 17:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-24 14:06 [binutils-gdb] Linux native thread create/exit events support sergiodj+buildbot
2016-05-24 15:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-23 17:14 [binutils-gdb] Skip unwritable frames in command "finish" sergiodj+buildbot
2016-05-23 19:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-19 13:44 [binutils-gdb] Fix invalid implicit conversions from void * sergiodj+buildbot
2016-05-19 14:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-19 10:25 [binutils-gdb] Remove unsupported `am34-*-linux*' target triplet sergiodj+buildbot
2016-05-19 12:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-19  5:57 [binutils-gdb] Fix powerpc subis range sergiodj+buildbot
2016-05-19 10:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-19  5:14 [binutils-gdb] Fix ppc64le S-record test fail sergiodj+buildbot
2016-05-19  9:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-18 12:06 [binutils-gdb] Updated Swedish translations for bfd and binutils sergiodj+buildbot
2016-05-19  3:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-18  0:39 [binutils-gdb] Rename OP_F90_RANGE to OP_RANGE sergiodj+buildbot
2016-05-18 23:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-17 21:52 [binutils-gdb] Add self-test framework to gdb sergiodj+buildbot
2016-05-17 22:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-17 21:36 [binutils-gdb] Update gdb test suite for Rust sergiodj+buildbot
2016-05-18 13:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-17 11:40 [binutils-gdb] LD/ELF: Unify STB_GNU_UNIQUE handling sergiodj+buildbot
2016-05-17 12:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-13  5:36 [binutils-gdb] ld -z combreloc elf_link_sort_relocs sergiodj+buildbot
2016-05-13  5:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-12 16:48 [binutils-gdb] PR symtab/19999 gdb unable to resolve vars with fission+PIE sergiodj+buildbot
2016-05-12 17:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-12 15:11 [binutils-gdb] ld -z combreloc reloc sorting sergiodj+buildbot
2016-05-12 15:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  2:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-10 17:37 [binutils-gdb] Factor our stub creation in ARM backend sergiodj+buildbot
2016-05-10 19:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-09 11:17 [binutils-gdb] opcodes,gas: sparc: fix mnemonic of faligndatai sergiodj+buildbot
2016-05-09 11:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-09  8:38 [binutils-gdb] Regenerate configure sergiodj+buildbot
2016-05-09  9:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-06  9:55 [binutils-gdb] Add support for FMLA (by element) to AArch64 sim sergiodj+buildbot
2016-05-06 10:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-05  0:11 [binutils-gdb] [spu] Fix C++ build problems sergiodj+buildbot
2016-05-05  0:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 17:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-03 12:30 [binutils-gdb] Fix gdb/python/python.c use-after-free sergiodj+buildbot
2016-05-03 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-03  9:56 [binutils-gdb] Fix "-Wl,--dynamic-list" gdb/configure test sergiodj+buildbot
2016-05-03 12:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-05-02 17:09 [binutils-gdb] Fix startup on MS-Windows when 'gdb.ini' is found in $HOME sergiodj+buildbot
2016-05-02 17:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-29 16:02 [binutils-gdb] Set interpreter in x86 create_dynamic_sections sergiodj+buildbot
2016-04-29 17:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-27 22:52 [binutils-gdb] Rename gdb_load_shlibs to gdb_load_shlib sergiodj+buildbot
2016-04-27 23:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 19:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 18:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 13:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-26 15:16 [binutils-gdb] fort_dyn_array: Support evaluation of dynamic elements inside arrays sergiodj+buildbot
2016-04-26 15:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  9:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22 18:06 [binutils-gdb] Choose TARGET_OBJECT_STACK_MEMORY and TARGET_OBJECT_MEMORY in read_value_memory sergiodj+buildbot
2016-04-22 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 16:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22 15:39 [binutils-gdb] [ARM] Clear reserved bits in CPSR sergiodj+buildbot
2016-04-22 15:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22 14:40 [binutils-gdb] Joel Brobecker stepping down as AIX Maintainer sergiodj+buildbot
2016-04-22 14:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22 12:23 [binutils-gdb] Tweak gdb.reverse/step-precsave.exp and gdb.reverse/step-reverse.exp sergiodj+buildbot
2016-04-22 12:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22 11:21 [binutils-gdb] New test case gdb.trace/signal.exp sergiodj+buildbot
2016-04-22 11:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22  5:18 [binutils-gdb] Exclude linker created file from dynobj sergiodj+buildbot
2016-04-22  7:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-21 16:36 [binutils-gdb] Switch gdb's TRY/CATCH to sjlj again sergiodj+buildbot
2016-04-21 17:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-21 13:06 [binutils-gdb] Fix AIX gdb build with C++ compiler sergiodj+buildbot
2016-04-21 13:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-21 11:15 [binutils-gdb] Fix s390 GNU/Linux gdb and gdbserver builds sergiodj+buildbot
2016-04-21 11:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 22:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-20 22:27 [binutils-gdb] Build GDB as a C++ program by default sergiodj+buildbot
2016-04-20 23:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-20 14:26 [binutils-gdb] Include arch/arm-linux.h in aarch32-linux-nat.c sergiodj+buildbot
2016-04-20 14:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 13:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  5:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-19 22:36 [binutils-gdb] opcodes/arc: Add yet more nps instructions sergiodj+buildbot
2016-04-19 23:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-19 22:17 [binutils-gdb] opcodes/arc: Add more nps instructions sergiodj+buildbot
2016-04-19 22:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-19 15:07 [binutils-gdb] linux-record: Squash cases with identical handling sergiodj+buildbot
2016-04-19 15:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-19 14:47 [binutils-gdb] Re-factor (i386|amd64)mpx target descriptions sergiodj+buildbot
2016-04-19 14:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-19  8:50 [binutils-gdb] Sync Makefile.tpl with gcc sergiodj+buildbot
2016-04-19  8:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-16  2:42 [binutils-gdb] gdb/ada-exp.y: Remap yydefred sergiodj+buildbot
2016-04-16 14:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-16  2:10 [binutils-gdb] Fix gdb build with --enable-build-with-cxx --disable-nls sergiodj+buildbot
2016-04-16 13:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 11:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-14 12:49 [binutils-gdb] Avoid "format not a string literal" warnings sergiodj+buildbot
2016-04-14 14:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-14 12:27 [binutils-gdb] Avoid implicit float <-> integer conversion warnings sergiodj+buildbot
2016-04-14 12:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-14 11:19 [binutils-gdb] Fix copying Solaris binaries with objcopy sergiodj+buildbot
2016-04-14 11:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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  9:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-13 20:40 [binutils-gdb] Debugging without a binary (regression) sergiodj+buildbot
2016-04-14  9:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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-14  4:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-13  7:30 [binutils-gdb] Eliminate prepare_to_throw_exception sergiodj+buildbot
2016-04-13 23:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 20:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 15:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-13  5:01 [binutils-gdb] Use target_terminal_ours_for_output in MI sergiodj+buildbot
2016-04-13 18:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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 10:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 20:57 [binutils-gdb] Use target_terminal_ours_for_output in warning/internal_error sergiodj+buildbot
2016-04-13 16:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 20:26 [binutils-gdb] Remove unused struct serial::name field sergiodj+buildbot
2016-04-12 20:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 20:21 [binutils-gdb] Introduce interruptible_select sergiodj+buildbot
2016-04-12 23:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 18:29 [binutils-gdb] Don't set immediate_quit in prompt_for_continue sergiodj+buildbot
2016-04-12 19:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 18:20 [binutils-gdb] Stop remote-fileio.c from throwing from SIGINT handler sergiodj+buildbot
2016-04-12 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 16:23 [binutils-gdb] Don't rely on immediate_quit in command_line_input sergiodj+buildbot
2016-04-12 16:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12 10:00 [binutils-gdb] Add support for .extCondCode, .extCoreRegister and .extAuxRegister sergiodj+buildbot
2016-04-12 10:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-12  9:33 [binutils-gdb] Update ARC instruction data-base sergiodj+buildbot
2016-04-12  9:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-09 12:55 [binutils-gdb] gdb.python/py-mi-events-gdb.py: Add parentheses to print sergiodj+buildbot
2016-04-09 13:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-08 13:52 [binutils-gdb] testsuite: Fix for gcc-4.8: gdb.base/jit.exp gdb.base/jit-so.exp sergiodj+buildbot
2016-04-08 14:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-07 17:52 [binutils-gdb] gas/arc: Handle multiple arc_opcode chains for same mnemonic sergiodj+buildbot
2016-04-07 19:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-07 16:55 [binutils-gdb] Fix gdb.reverse/next-reverse-bkpt-over-sr.exp sergiodj+buildbot
2016-04-07 17:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-07 16:05 [binutils-gdb] Set bp_tgt->reqstd_address and bp_tgt->placed_size in record_full_insert_breakpoint sergiodj+buildbot
2016-04-07 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-06 21:44 [binutils-gdb] Optimized-out pointer: New test for error handling sergiodj+buildbot
2016-04-06 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-06 19:19 [binutils-gdb] Workaround gdbserver<7.7 for setfs sergiodj+buildbot
2016-04-06 19:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-06  8:42 [binutils-gdb] Fix memory leak in ld ARM backend sergiodj+buildbot
2016-04-06  8:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-06  1:00 [binutils-gdb] Fix IPA detection in ftrace-insn-reloc.exp sergiodj+buildbot
2016-04-06  1:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-05 19:25 [binutils-gdb] Make ftrace tests work with remote targets sergiodj+buildbot
2016-04-05 22:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-05 18:35 [binutils-gdb] Improve gdb_remote_download, remove gdb_download sergiodj+buildbot
2016-04-05 21:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-05 17:01 [binutils-gdb] [ARC] PLT content endianess awareness sergiodj+buildbot
2016-04-05 18:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-05 15:04 [binutils-gdb] [ARC] Dynamic relocs verification for dynindx == -1 sergiodj+buildbot
2016-04-05 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-05 14:39 [binutils-gdb] ELF/LD: Avoid producing hidden and internal dynamic symbols sergiodj+buildbot
2016-04-05 14:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-03 16:59 [binutils-gdb] IPA: Fix build problem on !HAVE_GETAUXVAL sergiodj+buildbot
2016-04-03 16:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-01 13:05 [binutils-gdb] PR19886, --as-needed regression sergiodj+buildbot
2016-04-01 13:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-31 19:22 [binutils-gdb] Add regression test for PR gdb/19858 (JIT code registration on attach) sergiodj+buildbot
2016-03-31 21:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-31 15:30 [binutils-gdb] gdbserver: Add emit_ops for powerpc sergiodj+buildbot
2016-03-31 17:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-31 14:33 [binutils-gdb] IPA: Add alloc_jump_pad_buffer target hook sergiodj+buildbot
2016-03-31 15:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-31 12:58 [binutils-gdb] python: Use console format for output of gdb.execute command sergiodj+buildbot
2016-03-31 13:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-30 17:59 [binutils-gdb] Check func against 0 rather than NULL sergiodj+buildbot
2016-03-30 19:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-30 14:57 [binutils-gdb] [ARC] Cleanup AUX register names sergiodj+buildbot
2016-03-30 15:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-30  0:32 [binutils-gdb] gdbserver: Handle 'v' packet while processing qSymbol sergiodj+buildbot
2016-03-30 10:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-29 22:02 [binutils-gdb] gdbserver/s390: Add fast tracepoint support sergiodj+buildbot
2016-03-29 23:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-29 21:56 [binutils-gdb] gdbserver/s390: Switch on tracepoint support sergiodj+buildbot
2016-03-29 22:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-29 17:29 [binutils-gdb] [ARC] Fix typo in extension instruction name sergiodj+buildbot
2016-03-29 17:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-29 14:25 [binutils-gdb] Compile gdb.arch/arm-neon.exp with debug info sergiodj+buildbot
2016-03-29 14:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-29 10:50 [binutils-gdb] Tidy up AArch64 simulator code sergiodj+buildbot
2016-03-29 11:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-29  5:59 [binutils-gdb] PE/COFF regression in base of code and data calculation sergiodj+buildbot
2016-03-29  6:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-24 10:29 [binutils-gdb] Add quotation mark in test message sergiodj+buildbot
2016-03-24 11:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-22 12:26 [binutils-gdb] Attribute with DW_FORM_flag_present sergiodj+buildbot
2016-03-22 12:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-22 11:38 [binutils-gdb] Restore v850-rh850 as a recognised v850 architecture name for backwards compatibility sergiodj+buildbot
2016-03-22 12:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-22  9:46 [binutils-gdb] Add -Wstack-usage to the gcc warning flags list, but only if using a sufficiently recent version of gcc sergiodj+buildbot
2016-03-22 10:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-18 15:45 [binutils-gdb] Make sparc_software_single_step static sergiodj+buildbot
2016-03-19 17:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-18 13:21 [binutils-gdb] Fix generation of as.1 manual page so that it can be converted to DocBook format sergiodj+buildbot
2016-03-18 23:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17 23:01 [binutils-gdb] Add mips and s390 build targets for gold sergiodj+buildbot
2016-03-18 12:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17 10:26 [binutils-gdb] S390: Add syscall info for syscalls up to 374 sergiodj+buildbot
2016-03-18  6:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17  9:47 [binutils-gdb] linux-record: Simplify with record_mem_at_reg() sergiodj+buildbot
2016-03-18  4:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-17  9:19 [binutils-gdb] linux-record: Fix bad fall-through for pipe/pipe2 sergiodj+buildbot
2016-03-18  2:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 19:42 [binutils-gdb] Process record: Fix arm-linux syscall arguments sergiodj+buildbot
2016-03-16 21:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 17:48 [binutils-gdb] xml-tdesc.c (tdesc_start_enum): Fix c++ build sergiodj+buildbot
2016-03-17 21:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-16 16:29 [binutils-gdb] [ARM] Support ARMv8.2 FP16 simd instructions sergiodj+buildbot
2016-03-17  1:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-15 16:47 [binutils-gdb] Fix PR gdb/19676: Disable displaced stepping if /proc not mounted sergiodj+buildbot
2016-03-15 17:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-14 20:28 [binutils-gdb] Regenerate bfd-in2.h sergiodj+buildbot
2016-03-14 20:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-14 16:56 [binutils-gdb] gdb.base/default.exp: Add missing $_as_string to "show convenience" test sergiodj+buildbot
2016-03-14 17:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-13 10:06 [binutils-gdb] gdb/s390: Fill gen_return_address hook sergiodj+buildbot
2016-03-13 10:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-11 10:15 [binutils-gdb] gdb/s390: Fill pseudo register agent expression hooks sergiodj+buildbot
2016-03-11 11:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-10 22:34 [binutils-gdb] Add $_as_string convenience function sergiodj+buildbot
2016-03-11  6:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-10  1:30 [binutils-gdb] gdb.trace/tfind.exp: Force call via global entry point on ppc64le sergiodj+buildbot
2016-03-10  6:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 22:03 [binutils-gdb] gdb.trace/change-loc.exp: Don't depend on tracepoint ordering sergiodj+buildbot
2016-03-10  5:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 21:46 [binutils-gdb] gdb: fix doc string of target_can_use_hardware_watchpoint sergiodj+buildbot
2016-03-11  2:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 21:19 [binutils-gdb] Command line input handling TLC sergiodj+buildbot
2016-03-11  0:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:57 [binutils-gdb] Use struct buffer in gdb_readline_no_editing_callback sergiodj+buildbot
2016-03-10 22:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:36 [binutils-gdb] gdb_readline -> gdb_readline_no_editing sergiodj+buildbot
2016-03-10 19:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:27 [binutils-gdb] Update prompt_for_continue comments sergiodj+buildbot
2016-03-10 17:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:15 [binutils-gdb] Eliminate async_annotation_suffix sergiodj+buildbot
2016-03-10 15:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 20:06 [binutils-gdb] gdb_readline2 -> gdb_readline_no_editing_callback sergiodj+buildbot
2016-03-10 14:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 19:54 [binutils-gdb] Garbage collect window_hook sergiodj+buildbot
2016-03-10 11:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 19:42 [binutils-gdb] Test issuing a command split in multiple lines with continuation chars sergiodj+buildbot
2016-03-10 10:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 19:21 [binutils-gdb] gdb.trace/entry-values.exp: Fixes for powerpc64 sergiodj+buildbot
2016-03-10  7:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 18:40 [binutils-gdb] gdb/rs6000: Read backchain as unsigned sergiodj+buildbot
2016-03-10  3:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 16:41 [binutils-gdb] S390: Recognize special jumps in prologue parser sergiodj+buildbot
2016-03-09 23:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 16:30 [binutils-gdb] S390: Add use of unavailable-stack frame ID sergiodj+buildbot
2016-03-09 22:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 16:19 [binutils-gdb] Avoid spaces in osabi names sergiodj+buildbot
2016-03-09 20:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 15:59 [binutils-gdb] Fix v850 bfd arch info printable names sergiodj+buildbot
2016-03-09 17:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09 15:43 [binutils-gdb] For COFF and COFF/PE targets, skip relocations against absolute symbols sergiodj+buildbot
2016-03-09 16:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  6:37 [binutils-gdb] Allow zero length archive elements sergiodj+buildbot
2016-03-09  9:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  3:39 [binutils-gdb] [CRIS] Don't internal error if forced big endian sergiodj+buildbot
2016-03-09  7:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  3:19 [binutils-gdb] Assert that a floating type's length is at least as long as its format sergiodj+buildbot
2016-03-09  4:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-09  2:37 [binutils-gdb] Fix HP/PA GNU/Linux "long double" format sergiodj+buildbot
2016-03-09  3:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-08 17:47 [binutils-gdb] Handle local IFUNC symbols in shared object sergiodj+buildbot
2016-03-08 18:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-08 13:50 [binutils-gdb] Group common symbol checking together sergiodj+buildbot
2016-03-08 15:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-07 16:52 [binutils-gdb] Fix "set architecture mips:10000" crash sergiodj+buildbot
2016-03-07 19:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-07 15:51 [binutils-gdb] [AArch64] Create .got section if _GLOBAL_OFFSET_TABLE_ referenced sergiodj+buildbot
2016-03-07 17:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-06 22:42 [binutils-gdb] Set executable bit on analyze-racy-logs.py sergiodj+buildbot
2016-03-06 23:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-06  1:57 [binutils-gdb] Improve analysis of racy testcases sergiodj+buildbot
2016-03-06  3:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-05 12:31 [binutils-gdb] Fix argument passing for call sergiodj+buildbot
2016-03-05 12:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 16:41 [binutils-gdb] Add missing ChangeLog entries for commit 82838 sergiodj+buildbot
2016-03-04 20:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 16:10 [binutils-gdb] Tweak ARM process record sergiodj+buildbot
2016-03-04 17:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 15:16 [binutils-gdb] feature_to_c.sh: Print help when passing no arguments sergiodj+buildbot
2016-03-04 16:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-04 14:50 [binutils-gdb] Treat common symbol in executable as definition sergiodj+buildbot
2016-03-04 15:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 19:03 [binutils-gdb] gdb.base/skip.exp: Use with_test_prefix sergiodj+buildbot
2016-03-03 23:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 15:34 [binutils-gdb] Fix bugs in the simulation of the AArch64's ADDP, FADDP, LD1, CCMP and CCMP instructions sergiodj+buildbot
2016-03-03 21:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:27 [binutils-gdb] New test about step over clone syscall sergiodj+buildbot
2016-03-03 18:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:20 [binutils-gdb] Reformat gdb.base/step-over-syscall.exp sergiodj+buildbot
2016-03-03 16:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:09 [binutils-gdb] Rename disp-step-syscall.exp to step-over-syscall.exp sergiodj+buildbot
2016-03-03 15:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03 10:00 [binutils-gdb] Step over fork/vfork syscall insn in gdbserver sergiodj+buildbot
2016-03-03 14:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-03  9:31 [binutils-gdb] [GDBserver] Leave child suspended when step over parent sergiodj+buildbot
2016-03-03  9:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 17:06 [binutils-gdb] testsuite: Fix timeout issues during print of vla-arrays sergiodj+buildbot
2016-03-02 23:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 16:31 [binutils-gdb] [OBV] gdbserver: Only write ipa_tdesc_idx if agent is actually loaded sergiodj+buildbot
2016-03-03  7:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 15:53 [binutils-gdb] testsuite: Fix run to main issue introduced by GCC 5.x sergiodj+buildbot
2016-03-02 21:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 15:43 [binutils-gdb] testsuite: Nullify pointers before first usage sergiodj+buildbot
2016-03-02 19:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 15:30 [binutils-gdb] Add new maintainer to Write After Approval sergiodj+buildbot
2016-03-02 17:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 14:37 [binutils-gdb] Fix detection of gfortran compilers sergiodj+buildbot
2016-03-02 16:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02 14:03 [binutils-gdb] Regenerate or1k opcodes file sergiodj+buildbot
2016-03-02 14:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-02  4:03 [binutils-gdb] Regenerate bfd files sergiodj+buildbot
2016-03-02  6:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 18:47 [binutils-gdb] Fix gdb.trace/ftrace-lock.c compilation sergiodj+buildbot
2016-03-01 22:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 17:53 [binutils-gdb] Fix gdb.threads/watchpoint-fork*.c compilation sergiodj+buildbot
2016-03-01 21:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 17:26 [binutils-gdb] Fix gdb.base/catch-fork-kill.c compilation sergiodj+buildbot
2016-03-01 19:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 15:41 [binutils-gdb] Fix output path for arm-disp-step.exp sergiodj+buildbot
2016-03-01 17:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 12:05 [binutils-gdb] S390: Fix output path for s390-tdbregs test case sergiodj+buildbot
2016-03-01 14:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-03-01 11:55 [binutils-gdb] S390: Fix internal error with stackless inferior sergiodj+buildbot
2016-03-01 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 17:29 [binutils-gdb] aarch64-linux process record: more syscalls sergiodj+buildbot
2016-02-29 20:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 16:58 [binutils-gdb] Support more syscalls in linux-record: pipe2 epoll_create1 eventfd2 fallocate dup3 and inotify_init1 sergiodj+buildbot
2016-02-29 19:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 16:04 [binutils-gdb] [ARC] Local symbols relocation cleanup sergiodj+buildbot
2016-02-29 17:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-29 15:24 [binutils-gdb] [ARC] General fixes sergiodj+buildbot
2016-02-29 15:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-28 15:25 [binutils-gdb] Don't recursively look for a symbol in all imports of imported modules sergiodj+buildbot
2016-02-28 15:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <1ed0c2a4bbe8ad5f5404014a6351b2b74db75577@gdb-build>
2016-02-27 14:35 ` sergiodj+buildbot
2016-02-26 20:30 [binutils-gdb] Add aarch64-*-rtems* target sergiodj+buildbot
2016-02-27 12:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 18:19 [binutils-gdb] [BFD][AARCH64]Fix MOVW_SABS_G(0, 1, 2) relocation overflow check sergiodj+buildbot
2016-02-27  9:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 16:01 [binutils-gdb] Rename gdb.reverse/aarch64.{exp, c} to gdb.reverse/insn-reverse.{exp, c} sergiodj+buildbot
2016-02-26 20:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 16:00 [binutils-gdb] Fix various bugs in arm_record_exreg_ld_st_insn sergiodj+buildbot
2016-02-27  0:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 15:51 [binutils-gdb] Record right reg num of thumb special data instructions sergiodj+buildbot
2016-02-26 22:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 15:15 [binutils-gdb] Generalize gdb.reverse/aarch64.exp sergiodj+buildbot
2016-02-26 18:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 14:51 [binutils-gdb] Properly implement STT_COMMON sergiodj+buildbot
2016-02-26 17:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 13:10 [binutils-gdb] [x86] Resolve non-PIC undefweak symbols in executable sergiodj+buildbot
2016-02-26 15:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-26 13:00 [binutils-gdb] Fix powerpc64 -r --save-restore-funcs sergiodj+buildbot
2016-02-26 13:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <ab50308758bfde9ab7b50e6def65e20f0b560702@gdb-build>
2016-02-26  1:04 ` sergiodj+buildbot
     [not found] <ae91f6253926e4dadebcae90772f4f5a5bd06056@gdb-build>
2016-02-25 20:06 ` sergiodj+buildbot
     [not found] <678b48b7cf0bd518ebc234bda98229cc602c2a45@gdb-build>
2016-02-25 17:32 ` sergiodj+buildbot
2016-02-25 17:22 [binutils-gdb] Remove gdb.base/branches.c sergiodj+buildbot
2016-02-25 21:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-25 14:46 [binutils-gdb] Map registers to remote numbers when encoding an ax_reg or ax_reg_mask operation sergiodj+buildbot
2016-02-25 15:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-25 12:24 [binutils-gdb] Add elf_x86_64_need_pic sergiodj+buildbot
2016-02-25 12:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 23:37 [binutils-gdb] Update symbol version for symbol from linker script sergiodj+buildbot
2016-02-25  1:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <338435ef105ff51e967571ad073830ec1eb5a4ab@gdb-build>
2016-02-24 21:38 ` sergiodj+buildbot
2016-02-24 19:30 [binutils-gdb] Move tfile-avx.exp to tracefile-pseudo-reg.exp sergiodj+buildbot
2016-02-24 19:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 18:24 [binutils-gdb] Move new skip features to proper section (post 7.11) sergiodj+buildbot
2016-02-24 18:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 17:45 [binutils-gdb] powerpc: Support z-point type in gdbserver sergiodj+buildbot
2016-02-24 17:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 15:09 [binutils-gdb] Revert "ABS32" sergiodj+buildbot
2016-02-24 16:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:22 [binutils-gdb] [OPCODES][ARM][1/3]Add armv8.2 fp16 instruction dissembler support sergiodj+buildbot
2016-02-24 15:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:12 [binutils-gdb] [OPCODES][ARM]Fix mask for a few coprocessor opcodes sergiodj+buildbot
2016-02-24 15:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:09 [binutils-gdb] [OPCODE][ARM]Correct disassembler for cdp/cdp2, mcr/mcr2, mrc/mrc2, ldc/ldc2, stc/stc2 sergiodj+buildbot
2016-02-24 15:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 14:07 [binutils-gdb] ABS32 sergiodj+buildbot
2016-02-24 14:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 13:54 [binutils-gdb] Set plt_got.offset to (bfd_vma) -1 sergiodj+buildbot
2016-02-24 14:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24 12:00 [binutils-gdb] Fix logic in exec_file_locate_attach sergiodj+buildbot
2016-02-24 12:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-24  3:22 [binutils-gdb] Build unavailable-stack frames for tracepoint sergiodj+buildbot
2016-02-24  3:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 21:37 [binutils-gdb] Extend "skip" command to support -file, -gfile, -function, -rfunction sergiodj+buildbot
2016-02-23 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 18:34 [binutils-gdb] arm-tdep.c: Remove unused "to" parameters sergiodj+buildbot
2016-02-23 18:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23 13:10 [binutils-gdb] Increment the ABIVERSION to 5 for MIPS objects with non-executable stacks sergiodj+buildbot
2016-02-23 13:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-23  0:43 [binutils-gdb] Always create dynsym section with dynamic sections sergiodj+buildbot
2016-02-23  4:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <4000e47e2f3860a85a9023f3fe5950c8cc6fa507@gdb-build>
2016-02-22 19:24 ` sergiodj+buildbot
2016-02-22 16:37 [binutils-gdb] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print' sergiodj+buildbot
2016-02-22 18:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-22 12:26 [binutils-gdb] Fix arm process record code format sergiodj+buildbot
2016-02-22 12:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-21 21:15 [binutils-gdb] Also update recursive call to d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-21 20:46 [binutils-gdb] Remove search_parents parameter from d_lookup_symbol_imports sergiodj+buildbot
2016-02-21 20:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-19 16:10 [binutils-gdb] Prevent a seg-fault in the linker when accessing a specially crafted, corrupt, aout binary sergiodj+buildbot
2016-02-19 17:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-19 14:40 [binutils-gdb] [ARM] Add FP16 feature extension for ARMv8.2 architecture sergiodj+buildbot
2016-02-19 15:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 21:14 [binutils-gdb] Add D support to gdb_default_target_compile sergiodj+buildbot
2016-02-18 22:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <f79a3bae8725dfe0e11b04ddfc6e6bc8f23e4e4e@gdb-build>
2016-02-18 19:20 ` sergiodj+buildbot
     [not found] <5f034a78b986d30a90030b2409c61a8660b9b48c@gdb-build>
2016-02-18 16:52 ` sergiodj+buildbot
2016-02-18 16:46 [binutils-gdb] Intel MPX bound violation handling sergiodj+buildbot
2016-02-18 18:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 13:17 [binutils-gdb] Remove setup_kfail server/13796 in disp-step-syscall.exp sergiodj+buildbot
2016-02-18 14:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-18 12:18 [binutils-gdb] Set breakpoint condition-evaluation in forking-threads-plus-breakpoint.exp sergiodj+buildbot
2016-02-18 12:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-17 17:04 [binutils-gdb] Add missing cleanup in exec_file_locate_attach sergiodj+buildbot
2016-02-17 17:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-16 17:09 [binutils-gdb] PR remote/19496, internal err forking-threads-plus-bkpt sergiodj+buildbot
2016-02-17  1:17 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-16 14:26 [binutils-gdb] Fix cleanup in arm_linux_software_single_step sergiodj+buildbot
2016-02-16 19:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-16  0:16 [binutils-gdb] Add parentheses to prevent truncated addresses sergiodj+buildbot
2016-02-16 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-15 10:19 [binutils-gdb] Don't print 0x for core_addr_to_string_nz sergiodj+buildbot
2016-02-15 10:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-14  8:44 [binutils-gdb] testsuite: Fix false Fortran regressions with recent gcc sergiodj+buildbot
2016-02-14 11:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <e44e00ffffe358d91df0ec4a11563eef0c14beb4@gdb-build>
2016-02-12 21:25 ` sergiodj+buildbot
2016-02-12 16:22 [binutils-gdb] [ARM] Software single step cross kernel helpers sergiodj+buildbot
2016-02-12 17:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-12 16:11 [binutils-gdb] [ARM] Fixup PC in software single step sergiodj+buildbot
2016-02-12 16:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <020ecd38e74681cb14987baf1a4d3c3ee3be0006@gdb-build>
2016-02-12 15:30 ` sergiodj+buildbot
2016-02-12  9:10 [binutils-gdb] stack: check frame_unwind_caller_id sergiodj+buildbot
2016-02-12 12:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-12  9:01 [binutils-gdb] frame: add skip_tailcall_frames sergiodj+buildbot
2016-02-12 10:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-11 20:15 [binutils-gdb] Add missing quotes to gdb/testsuite/README sergiodj+buildbot
2016-02-12  8:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-11 18:30 [binutils-gdb] arm-tdep.c: Change type of insn parameters sergiodj+buildbot
2016-02-12  3:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-11 13:31 [binutils-gdb] Use the target architecture when encoding tracepoint actions sergiodj+buildbot
2016-02-11 22:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <e909d859f5635d66e79fef467da70d6090bfae1b@gdb-build>
2016-02-11 13:12 ` sergiodj+buildbot
     [not found] <473b99e5721ad623cc5826e03a73e2cf6cef4eb5@gdb-build>
2016-02-11 12:03 ` sergiodj+buildbot
2016-02-10 17:06 [binutils-gdb] Clear *VAL in regcache_raw_read_unsigned sergiodj+buildbot
2016-02-11 18:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-10 12:21 [binutils-gdb] Add support for ARC instruction relaxation in the assembler sergiodj+buildbot
2016-02-11 10:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-10  4:06 [binutils-gdb] Update NEWS post GDB 7.11 branch creation sergiodj+buildbot
2016-02-10 16:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-10  0:25 [binutils-gdb] breakpoints/19546: Fix crash after updating breakpoints sergiodj+buildbot
2016-02-10 11:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 22:56 [binutils-gdb] python/19506 -- gdb.Breakpoint address location regression sergiodj+buildbot
2016-02-10  0:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 14:16 [binutils-gdb] Modernize configure.ac's sergiodj+buildbot
2016-02-09 20:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 12:41 [binutils-gdb] Fix PR19548: Breakpoint re-set inserts breakpoints when it shouldn't sergiodj+buildbot
2016-02-09 18:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 11:06 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 15:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 10:57 [binutils-gdb] Revert "Fix build breakage" sergiodj+buildbot
2016-02-09 14:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-09 10:10 [binutils-gdb] Add a more helpful warning message to explain why some AArch64 relocations can overflow sergiodj+buildbot
2016-02-09 10:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-08 19:12 [binutils-gdb] Fix in-tree, parallel running of Ada tests sergiodj+buildbot
2016-02-08 20:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-06  1:39 [binutils-gdb] sim: mips: fix prog_bfd usage sergiodj+buildbot
2016-02-07 10:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-04 15:57 [binutils-gdb] [testsuite] Remove BASEDIR sergiodj+buildbot
2016-02-04 16:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-04 10:06 [binutils-gdb] Fix the encoding of the MSP430's RRUX instruction sergiodj+buildbot
2016-02-04 10:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-02 13:44 [binutils-gdb] PowerPC64 ELFv2 entry code sergiodj+buildbot
2016-02-02 20:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-02 12:31 [binutils-gdb] Clear HAS_RELOC if there are no relocations sergiodj+buildbot
2016-02-02 19:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-02 11:38 [binutils-gdb] epiphany/disassembler: Improve alignment of output sergiodj+buildbot
2016-02-02 16:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-02 11:21 [binutils-gdb] Add bound related fields to the siginfo structure sergiodj+buildbot
2016-02-02 14:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 23:59 [binutils-gdb] Don't add DT_NEEDED for unmatched symbol sergiodj+buildbot
2016-02-02  7:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 18:40 [binutils-gdb] gdb: Guard against undefined behaviour in mi-vla-fortran.exp sergiodj+buildbot
2016-02-01 19:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 18:23 [binutils-gdb] gdb: New set/show max-value-size command sergiodj+buildbot
2016-02-01 18:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 13:53 [binutils-gdb] Add support for importing data from ILF images sergiodj+buildbot
2016-02-01 14:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01 11:43 [binutils-gdb] x86 synthetic plt symbols sergiodj+buildbot
2016-02-01 13:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-02-01  3:36 [binutils-gdb] Fix some comments in varobj.{c,h} sergiodj+buildbot
2016-02-01  4:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-31 20:38 [binutils-gdb] Fix /usr/bin/ld: final link failed: File truncated error on hppa sergiodj+buildbot
2016-01-31 20:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-28 21:41 [binutils-gdb] Set BFD_DECOMPRESS to decompress debug sections sergiodj+buildbot
2016-01-29  0:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-28 21:00 [binutils-gdb] Sync libiberty with GCC sergiodj+buildbot
2016-01-28 21:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-28 14:39 [binutils-gdb] [testsuite] Fix tiemout fail in gdb.fortran/vla-value.exp sergiodj+buildbot
2016-01-28 15:51 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-27 11:38 [binutils-gdb] Add Keith Seitz as Linespec Maintainer sergiodj+buildbot
2016-01-27 11:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <a579cd9aa8c57c8a54833f26452a1afef38e5d20@gdb-build>
2016-01-25 23:48 ` sergiodj+buildbot
2016-01-25 16:18 [binutils-gdb] ARC/BFD: Fix a build error from `index' shadowing a global declaration sergiodj+buildbot
2016-01-25 18:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25 13:32 [binutils-gdb] Move foreach_with_prefix to lib/gdb.exp sergiodj+buildbot
2016-01-25 13:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25  9:54 [binutils-gdb] Add missing end-of-comment marker to previous delta. (Doh!) sergiodj+buildbot
2016-01-25 10:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-25  9:41 [binutils-gdb] Fix memory corruption on Mach-O systems by suppressing a memory tidy up sergiodj+buildbot
2016-01-25  9:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-22 21:00 [binutils-gdb] testsuite: gdb.gdb/selftest.exp: Drop expected Thread number sergiodj+buildbot
2016-01-22 22:12 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <99e8eb11cfcdde8cba6755ed4613c3cb079dfaa4@gdb-build>
2016-01-22 14:33 ` sergiodj+buildbot
2016-01-22  1:15 [binutils-gdb] * breakpoint.c (init_breakpoint_sal): Add comment sergiodj+buildbot
2016-01-22  9:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <f906b857015513af81f94db8e11b1e334c767def@gdb-build>
2016-01-21 23:22 ` sergiodj+buildbot
2016-01-21 14:04 [binutils-gdb] Fix compile time errors building ARC target on a 32-bit host sergiodj+buildbot
2016-01-21 22:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21 11:45 [binutils-gdb] gdb: Respect CXXFLAGS when building with C++ compiler sergiodj+buildbot
2016-01-21 19:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21 11:03 [binutils-gdb] Fix unexpected failures in the linker testsuite for ARM VxWorks targets sergiodj+buildbot
2016-01-21 18:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21 10:09 [binutils-gdb] Rename elf-linux-psinfo.h to elf-linux-core.h sergiodj+buildbot
2016-01-21 14:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21  9:57 [binutils-gdb] Convert macros in elf-linux-core.h to inline functions sergiodj+buildbot
2016-01-21 15:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-21  8:17 [binutils-gdb] Detect the arm/thumb mode of code SIGRETURN or RT_SIGRETURN returns to sergiodj+buildbot
2016-01-21 11:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20 18:53 [binutils-gdb] gnu_vector.exp: Respect `should_kfail' for PR 8549 sergiodj+buildbot
2016-01-21  9:13 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20 14:43 [binutils-gdb] [AArch64] Reject invalid immediate operands to MSR UAO sergiodj+buildbot
2016-01-21  4:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20 13:05 [binutils-gdb] Add support for an ARM specific 'y' section attribute flag to mark the section as NOREAD sergiodj+buildbot
2016-01-20 22:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-20  4:14 [binutils-gdb] minor reformatting in printcmd.c::print_scalar_formatted sergiodj+buildbot
2016-01-20 18:59 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-19 17:09 [binutils-gdb] Add support to readelf for reading FreeBSD ELF core notes sergiodj+buildbot
2016-01-19 22:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-19 16:35 [binutils-gdb] testsuite: Factor out --status in DO_RUNTEST sergiodj+buildbot
2016-01-19 20:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-19 15:37 [binutils-gdb] Add PIC and TLS support to the ARC target sergiodj+buildbot
2016-01-19 15:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <bd0a71fa16f668341a9361c695bc3ca44d27b322@gdb-build>
2016-01-19 12:35 ` sergiodj+buildbot
2016-01-18 17:08 [binutils-gdb] testsuite: Remove unused global references in gdb_test sergiodj+buildbot
2016-01-18 20:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-18 16:03 [binutils-gdb] Fix PR threads/19422 - show which thread caused stop sergiodj+buildbot
2016-01-18 18:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-18 15:19 [binutils-gdb] Replace some $ARCH_{get, set}_pc with linux_{get, set}_pc_64bit sergiodj+buildbot
2016-01-18 17:03 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-17  7:04 [binutils-gdb] GDB SIGSEGV opening a Fortran program compiled with ifort sergiodj+buildbot
2016-01-17  9:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-17  6:17 [binutils-gdb] fix gdb version parsing in src-release.sh sergiodj+buildbot
2016-01-17  8:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-17  5:43 [binutils-gdb] minor reformatting in sim/common/sim-fpu.c sergiodj+buildbot
2016-01-17  6:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-15 22:25 [binutils-gdb] Star wildcard ranges (e.g., "info thread 2.*") sergiodj+buildbot
2016-01-15 23:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-15 21:59 [binutils-gdb] Fix "thread apply $conv_var" and misc other related problems sergiodj+buildbot
2016-01-15 22:16 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-14 14:57 [binutils-gdb] [ARM] Remove field syscall_next_pc in struct gdbarch_tdep sergiodj+buildbot
2016-01-14 15:23 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-13 11:42 [binutils-gdb] Add $_gthread convenience variable sergiodj+buildbot
2016-01-13 18:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 20:34 [binutils-gdb] Implement 'catch syscall' for gdbserver sergiodj+buildbot
2016-01-13  2:53 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 16:46 [binutils-gdb] [ARM] Support ARMv8.2 RAS extension sergiodj+buildbot
2016-01-12 23:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 16:34 [binutils-gdb] Fix invalid conversion from void * to gdb_byte * sergiodj+buildbot
2016-01-12 19:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 15:45 [binutils-gdb] gdbserver: use the new gdb warning helpers sergiodj+buildbot
2016-01-12 18:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 15:22 [binutils-gdb] Change function signature passed to clone sergiodj+buildbot
2016-01-12 16:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12 12:01 [binutils-gdb] Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk" sergiodj+buildbot
2016-01-12 12:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-12  1:37 [binutils-gdb] Reapply: List inferiors/threads/pspaces in ascending order sergiodj+buildbot
2016-01-12  7:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-11 21:31 [binutils-gdb] testsuite: i386 regression for funcargs.exp sergiodj+buildbot
2016-01-12  0:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-11 21:16 [binutils-gdb] testsuite: Fix false FAILs on too long base directory sergiodj+buildbot
2016-01-11 21:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-11 19:13 [binutils-gdb] gdb: split out warnings helpers sergiodj+buildbot
2016-01-11 19:46 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-11 11:18 [binutils-gdb] Import changes made to files shared with the FSF GCC project sergiodj+buildbot
2016-01-11 11:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-10 23:15 [binutils-gdb] sim: drop unused SIM_AC_OPTION_PACKAGES sergiodj+buildbot
2016-01-11  1:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-10 22:20 [binutils-gdb] sim: allow the assert configure option everywhere sergiodj+buildbot
2016-01-10 22:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-10  9:12 [binutils-gdb] sim: drop targ-vals.def->nltvals.def indirection sergiodj+buildbot
2016-01-10 12:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-10  8:33 [binutils-gdb] sim: drop --enable-sim-{regparm,stdcall} options sergiodj+buildbot
2016-01-10  9:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-09  9:01 [binutils-gdb] sim: drop common/cconfig.h in favor of a single config.h sergiodj+buildbot
2016-01-09  9:18 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08 19:16 [binutils-gdb] Fix gdb.multi/base.exp testsuite regression sergiodj+buildbot
2016-01-08 19:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08 15:34 [binutils-gdb] perf testsuite: python 3 fixes sergiodj+buildbot
2016-01-08 15:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08 11:25 [binutils-gdb] Change SIGINT handler for extension languages only when target terminal is ours sergiodj+buildbot
2016-01-08 14:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08 11:16 [binutils-gdb] Check input interrupt first when reading packet sergiodj+buildbot
2016-01-08 12:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-08  9:58 [binutils-gdb] [ARM] PR ld/19368: Add missing relocation type class for R_ARM_IRELATIVE sergiodj+buildbot
2016-01-08 10:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-07  3:07 [binutils-gdb] sim: config: drop use of __DATE__/__TIME__ sergiodj+buildbot
2016-01-07  4:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-06 18:52 [binutils-gdb] MIPS/include: opcode/mips.h: Add a summary of MIPS16 operand codes sergiodj+buildbot
2016-01-06 19:09 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-06 11:46 [binutils-gdb] Fix gdb.python/py-infthread.exp test message typo sergiodj+buildbot
2016-01-06 12:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-05 23:03 [binutils-gdb] libiberty: {count, dup, write}argv: constify argv input slightly sergiodj+buildbot
2016-01-06  3:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-05 22:29 [binutils-gdb] libiberty: Tweak the documentation of libiberty's xcrc32 function sergiodj+buildbot
2016-01-06  0:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-04 11:04 [binutils-gdb] sim: parse_args: polish getopt error message sergiodj+buildbot
2016-01-04 12:37 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-04  8:52 [binutils-gdb] btrace: do not return out of TRY/CATCH sergiodj+buildbot
2016-01-04  9:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-04  3:17 [binutils-gdb] sim: parse_args: display getopt error ourselves sergiodj+buildbot
2016-01-04  4:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-04  1:04 [binutils-gdb] sim: TODO: move to wiki sergiodj+buildbot
2016-01-04  2:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-03  9:56 [binutils-gdb] sim: clean up some more device detritus sergiodj+buildbot
2016-01-03 11:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-02 19:11 [binutils-gdb] sim: cris: use standard output helpers sergiodj+buildbot
2016-01-02 19:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-02 16:02 [binutils-gdb] sim: iq2000/m32r/lm32/sh64: delete dead option code sergiodj+buildbot
2016-01-02 16:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-01 12:44 [binutils-gdb] Copyright update for binutils sergiodj+buildbot
2016-01-01 13:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-01-01  4:56 [binutils-gdb] GDB copyright headers update after running GDB's copyright.py script sergiodj+buildbot
2016-01-01  6:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-31  4:59 [binutils-gdb] sim: m68hc11: fix default endian sergiodj+buildbot
2015-12-31  5:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-31  2:11 [binutils-gdb] sim: cris/m68hc11: move default endian/alignment to configure sergiodj+buildbot
2015-12-31  2:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30 11:14 [binutils-gdb] sim: h8300: simplify h8300_reg_{fetch,store} funcs sergiodj+buildbot
2015-12-30 15:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30  9:52 [binutils-gdb] sim: simplify STATE_MY_NAME setup sergiodj+buildbot
2015-12-30 12:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30  8:57 [binutils-gdb] sim: arm/d10v/h8300/m68hc11/microblaze/mips/mn10300/moxie/sh/v850: convert to common sim_{fetch, store}_register sergiodj+buildbot
2015-12-30 11:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-30  8:41 [binutils-gdb] sim: h8300: drop unused inst.h sergiodj+buildbot
2015-12-30  8:57 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-27  6:09 [binutils-gdb] sim: unify sim-hload sergiodj+buildbot
2015-12-27  6:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-27  0:20 [binutils-gdb] sim: bfin: push down mmr address/size checks sergiodj+buildbot
2015-12-27  2:22 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-26 19:56 [binutils-gdb] sim: sim-core: pass down cpu to hw accesses when available sergiodj+buildbot
2015-12-26 21:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-26 12:29 [binutils-gdb] sim: standardize sim_create_inferior handling of argv a bit more sergiodj+buildbot
2015-12-26 18:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25 11:46 [binutils-gdb] sim: cris: clean up rvdummy a bit sergiodj+buildbot
2015-12-26 13:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25 10:01 [binutils-gdb] sim: drop WITH_ENGINE define sergiodj+buildbot
2015-12-26 10:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  9:35 [binutils-gdb] sim: move MACH/MODEL types into SIM_xxx namespace sergiodj+buildbot
2015-12-26  8:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  8:19 [binutils-gdb] sim: arm: delete unused code sergiodj+buildbot
2015-12-26  5:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  7:53 [binutils-gdb] sim: move WITH_SCACHE_PBB to sim-main.h sergiodj+buildbot
2015-12-26  1:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  2:16 [binutils-gdb] sim: delete old breakpoint code sergiodj+buildbot
2015-12-25 17:35 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  1:25 [binutils-gdb] sim: delete SIM_HAVE_FLATMEM support sergiodj+buildbot
2015-12-25 14:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-25  0:34 [binutils-gdb] sim: delete SIM_HAVE_SIMCACHE sergiodj+buildbot
2015-12-25  1:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-24  9:44 [binutils-gdb] Consolidate Thumb-1/Thumb-2 ISA detection sergiodj+buildbot
2015-12-24 10:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-24  5:38 [binutils-gdb] [testsuite/Ada] stop using project files when building test programs sergiodj+buildbot
2015-12-24  5:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-22 16:10 [binutils-gdb] Remove HP-UX reference in foll-vfork.exp sergiodj+buildbot
2015-12-22 21:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-22 15:50 [binutils-gdb] [lynxos] gdbserver hangs when killing inferior from GDB sergiodj+buildbot
2015-12-22 19:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-22 15:35 [binutils-gdb] [win32] cannot automatically find executable file [...] warning at GDB startup sergiodj+buildbot
2015-12-22 16:45 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-21 19:50 [binutils-gdb] Remove dead code in testsuite sergiodj+buildbot
2015-12-21 20:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-21 16:34 [binutils-gdb] Remove references to HP CC/aCC compiler from testsuite sergiodj+buildbot
2015-12-21 16:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-21 14:08 [binutils-gdb] Use arm_eabi_breakpoint on aarch32 sergiodj+buildbot
2015-12-21 14:25 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-19  3:44 [binutils-gdb] Fix ARI warning in gdb/arch/arm-get-next-pcs.c sergiodj+buildbot
2015-12-20  8:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-18 18:50 [binutils-gdb] Add documentation to gdb_compile sergiodj+buildbot
2015-12-20  4:55 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-18 17:35 [binutils-gdb] Share regcache function regcache_raw_read_unsigned sergiodj+buildbot
2015-12-20  0:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-18 17:01 [binutils-gdb] Share some ARM target dependent code from GDB with GDBServer sergiodj+buildbot
2015-12-19 22:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 18:36 [binutils-gdb] Skip gdb.base/gdbinit-history.exp on remote hosts sergiodj+buildbot
2015-12-19  3:40 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 15:02 [binutils-gdb] [AArch64][PATCH 11/14] Add support for the 2H vector type sergiodj+buildbot
2015-12-18 15:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 11:45 [binutils-gdb] [Patch ARM] Fix build attributes for armv8-a in case of assembler files that contain no directives sergiodj+buildbot
2015-12-19 15:33 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17 10:05 [binutils-gdb] [ARM] Add support for thumb1 pcrop relocations sergiodj+buildbot
2015-12-19 12:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  9:52 [binutils-gdb] gdb: Extend help text for 'list' command sergiodj+buildbot
2015-12-18  0:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  9:14 [binutils-gdb] Tweak gdb.trace/ftrace.exp for aarch64 sergiodj+buildbot
2015-12-19 10:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  8:58 [binutils-gdb] Fix invalid left shift of negative value sergiodj+buildbot
2015-12-19  8:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  7:16 [binutils-gdb] Skip gdb.base/gdbhistsize-history.exp on remote hosts sergiodj+buildbot
2015-12-19  2:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  7:08 [binutils-gdb] Skip tests that send ctrl-c to GDB if nointerrupts target property is set sergiodj+buildbot
2015-12-19  0:00 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  6:17 [binutils-gdb] Target remote mode fork and exec event support sergiodj+buildbot
2015-12-18 21:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  6:02 [binutils-gdb] [AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instructions sergiodj+buildbot
2015-12-18 18:58 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  5:45 [binutils-gdb] [AArch64][PATCH 12/14] Support FP16 Adv.SIMD Scalar Pairwise instructions sergiodj+buildbot
2015-12-18 16:24 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  5:29 [binutils-gdb] [AArch64][PATCH 9/14] Support FP16 Adv.SIMD Modified Immediate instructions sergiodj+buildbot
2015-12-18 14:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  5:06 [binutils-gdb] [AArch64][PATCH 6/14] Support FP16 Vector Indexed Element instructions sergiodj+buildbot
2015-12-18 11:04 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:50 [binutils-gdb] [AArch64][PATCH 4/14] Support FP16 Vector Two Register Misc. instructions sergiodj+buildbot
2015-12-18  8:47 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:35 [binutils-gdb] [AArch64][PATCH 2/14] Support ARMv8.2 FP16 Vector Three Same instructions sergiodj+buildbot
2015-12-18  6:44 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  4:19 [binutils-gdb] [AArch64] Fix errors rebasing the ARMv8.2 AT and system registers patch sergiodj+buildbot
2015-12-18  4:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:46 [binutils-gdb] gdb: Add an error when 'list -' reaches the start of a file sergiodj+buildbot
2015-12-17 23:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:37 [binutils-gdb] gdb: 'list' command, tweak handling of +/- arguments sergiodj+buildbot
2015-12-17 22:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:20 [binutils-gdb] gdb: Small code restructure for list_command sergiodj+buildbot
2015-12-17 19:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  3:07 [binutils-gdb] gdb: Make lines_to_list variable static sergiodj+buildbot
2015-12-17 17:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  2:50 [binutils-gdb] ld -r doesn't need plugin for slim lto object sergiodj+buildbot
2015-12-17  8:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  2:31 [binutils-gdb] [AArch64][Patch 5/5] Add instruction PSB CSYNC sergiodj+buildbot
2015-12-17 13:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  2:14 [binutils-gdb] [AArch64][Patch 3/5] Adjust maximum number of instruction aliases sergiodj+buildbot
2015-12-17 11:10 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-17  1:05 [binutils-gdb] Remove "spaces" references from gdb.multi/base.exp sergiodj+buildbot
2015-12-17  4:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-10 16:00 [binutils-gdb] Remove support for thread events without PTRACE_EVENT_CLONE in GDB sergiodj+buildbot
2015-12-10 18:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-10 10:15 [binutils-gdb] gdb: Handle multiple base address in debug_ranges data sergiodj+buildbot
2015-12-10 10:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
     [not found] <8eab413676a0222a863f45ff606f3db69bb7afc4@gdb-build>
2015-12-09 16:33 ` sergiodj+buildbot
2015-12-09 13:15 [binutils-gdb] varobj zero-padded hexadecimal format sergiodj+buildbot
2015-12-09 14:02 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-09 12:32 [binutils-gdb] Fix wrong output of x87 registers due to truncation to double on amd64 sergiodj+buildbot
2015-12-09 12:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-08  9:14 [binutils-gdb] DOCO: Enhance the menu to select function overloads with signatures sergiodj+buildbot
2015-12-08  9:30 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07 16:13 [binutils-gdb] Support Z0 packet in AArch64 multi-arch debugging sergiodj+buildbot
2015-12-08  0:52 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07 12:11 [binutils-gdb] Add myself as a write-after-approval GDB maintainer sergiodj+buildbot
2015-12-07 21:27 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07  4:29 [binutils-gdb] PowerPC ifunc with local symbols sergiodj+buildbot
2015-12-07 19:07 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07  3:41 [binutils-gdb] R_PPC64_ENTRY sergiodj+buildbot
2015-12-07 16:49 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-07  3:17 [binutils-gdb] Reorder some power9 insns sergiodj+buildbot
2015-12-07 15:48 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-05  2:39 [binutils-gdb] gdbserver: set ptrace flags after creating inferiors sergiodj+buildbot
2015-12-05  2:56 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-03 17:23 [binutils-gdb] Run gdb.base/sizeof.exp with board having gdb, noinferiorio sergiodj+buildbot
2015-12-03 17:50 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-02 13:42 [binutils-gdb] addr2line vs. inlined C functions called from C++ sergiodj+buildbot
2015-12-02 14:20 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-02  9:02 [binutils-gdb] Fix powerpc64 segfault caused by zero r_symndx relocs sergiodj+buildbot
2015-12-02 13:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01 17:41 [binutils-gdb] Avoid "operation may be undefined" warning in remote.c sergiodj+buildbot
2015-12-02  9:19 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01 12:47 [binutils-gdb] Run gdb.base/disp-step-syscall.exp for aarch64-linux sergiodj+buildbot
2015-12-02  7:32 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  5:47 [binutils-gdb] ARC port broken reloc processing sergiodj+buildbot
2015-12-01 22:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  3:43 [binutils-gdb] Invoke aout N_* macros with pointer to struct internal_exec sergiodj+buildbot
2015-12-02  5:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-12-01  3:35 [binutils-gdb] Don't use BFD_TRADITIONAL_FORMAT flag in COFF support sergiodj+buildbot
2015-12-02  3:15 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 22:31 [binutils-gdb] Refactor queries for hardware and software single stepping support in GDBServer sergiodj+buildbot
2015-12-01 19:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 22:15 [binutils-gdb] Fix breakpoint size when stepping over a permanent breakpoint in GDBServer sergiodj+buildbot
2015-12-01 16:39 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 21:45 [binutils-gdb] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol sergiodj+buildbot
2015-12-01 12:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 21:22 [binutils-gdb] gdbserver: fix killed-outside.exp sergiodj+buildbot
2015-12-01  9:26 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 21:14 [binutils-gdb] Remote thread create/exit events sergiodj+buildbot
2015-12-01  8:29 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 21:00 [binutils-gdb] gdbserver resume_stop handling bug sergiodj+buildbot
2015-12-01  6:28 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 20:44 [binutils-gdb] New vCtrlC packet, non-stop mode equivalent of \003 sergiodj+buildbot
2015-12-01  4:31 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-30 20:13 [binutils-gdb] Remote all-stop-on-top-of-non-stop sergiodj+buildbot
2015-11-30 21:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 19:24 [binutils-gdb] libiberty TAGS sergiodj+buildbot
2015-11-28 23:11 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 18:08 [binutils-gdb] libsanitizer merge from upstream r250806, compiler part sergiodj+buildbot
2015-11-29  3:21 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 17:44 [binutils-gdb] PR other/61321 - demangler crash on casts in template parameters sergiodj+buildbot
2015-11-29  0:01 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 17:28 [binutils-gdb] (Makefiles): PATCH to include libcpp and libiberty in GCC etags sergiodj+buildbot
2015-11-28 22:06 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 17:05 [binutils-gdb] Fix several crashes of C++ demangler on fuzzed input sergiodj+buildbot
2015-11-28 19:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-28 16:50 [binutils-gdb] Avoid "enum conversion when passing argument 1 of 'getrusage' is invalid in C++" warning sergiodj+buildbot
2015-11-28 17:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-27 16:50 [binutils-gdb] [AArch64][PATCH 3/3] Add floating-point FP16 instructions sergiodj+buildbot
2015-11-28 16:41 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2015-11-27 16:42 [binutils-gdb] [AArch64][PATCH 2/3] Adjust a utility function for floating point values sergiodj+buildbot
2015-11-28 15:36 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, 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).