public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] arch-utils: Make the last endianness actually chosen sticky
@ 2018-05-31 15:14 sergiodj+buildbot
  2018-05-31 14:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
                   ` (7 more replies)
  0 siblings, 8 replies; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b2dfa9d877a919e05817e6bfa4eda3addaf1b34 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 4b2dfa9d877a919e05817e6bfa4eda3addaf1b34

arch-utils: Make the last endianness actually chosen sticky

Use the last endianness explicitly selected, either by choosing a binary
file or with the `set endian' command, for future automatic selection.

As observed with the `gdb.base/step-over-no-symbols.exp' test case when
discarding the binary file even while connected to a live target the
endianness automatically selected is reset to the GDB target's default,
even if it does not match the endianness of the target being talked to.

For example with a little-endian MIPS target and the default endianness
being big we get this:

(gdb) file .../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols
Reading symbols from .../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols...done.
(gdb) delete breakpoints
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 1 at 0x400840: file .../gdb/testsuite/gdb.base/start.c, line 34.
[...]
(gdb) continue
Continuing.

Breakpoint 1, main () at .../gdb/testsuite/gdb.base/start.c:34
34	  foo();
(gdb) delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) file
A program is being debugged already.
Are you sure you want to change the file? (y or n) y
No executable file now.
Discard symbol table from `.../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols'? (y or n) y
No symbol file now.
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: purging symbols
p /x $pc
$1 = 0x40084000
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get before PC
break *$pc
Breakpoint 2 at 0x40084000
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: break *$pc
set displaced-stepping off
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: set displaced-stepping off
stepi
Warning:
Cannot insert breakpoint 2.
Cannot access memory at address 0x40084000

Command aborted.
(gdb) FAIL: gdb.base/step-over-no-symbols.exp: displaced=off: stepi
p /x $pc
$2 = 0x40084000
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get after PC
FAIL: gdb.base/step-over-no-symbols.exp: displaced=off: advanced
Remote debugging from host ...
monitor exit
(gdb) Killing process(es): ...
testcase .../gdb/testsuite/gdb.base/step-over-no-symbols.exp completed in 2 seconds

which shows that with the removal of the executable debugged the
endianness of $pc still at `main' gets swapped and the value in that
register is now incorrectly interpreted as 0x40084000 rather than
0x400840 as shown earlier on with the `break' command.  Consequently the
debug session no longer works as expected, until the endianness is
overridden with an explicit `set endian little' command.

This will happen while working with any target hardware whose endianness
does not match the default GDB target's endianness guessed and recorded
for a later use in `initialize_current_architecture'.

Given that within a single run of GDB it is more likely that consecutive
target connections will use the same endianness than that the endianness
will be swapped between connections, it makes sense to preserve the last
endianness explicitly selected as the automatic default.  It will make a
session like above, where an executable is removed, work correctly and
will retain the endianness for a further reconnection to the target.

And the new automatic default will still be overridden by subsequently
choosing a binary to debug, or with an explicit `set endian' command.

With the change in place the test case above completes successfully:

(gdb) continue
Continuing.

Breakpoint 1, main () at .../gdb/testsuite/gdb.base/start.c:34
34	  foo();
(gdb) delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) file
A program is being debugged already.
Are you sure you want to change the file? (y or n) y
No executable file now.
Discard symbol table from `.../gdb/testsuite/outputs/gdb.base/step-over-no-symbols/step-over-no-symbols'? (y or n) y
No symbol file now.
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: purging symbols
p /x $pc
warning: GDB can't find the start of the function at 0x400840.

    GDB is unable to find the start of the function at 0x400840
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x400840 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
$1 = 0x400840
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get before PC
break *$pc
Breakpoint 2 at 0x400840
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: break *$pc
set displaced-stepping off
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: set displaced-stepping off
stepi
warning: GDB can't find the start of the function at 0x4007f8.
0x004007f8 in ?? ()
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: stepi
p /x $pc
$2 = 0x4007f8
(gdb) PASS: gdb.base/step-over-no-symbols.exp: displaced=off: get after PC
PASS: gdb.base/step-over-no-symbols.exp: displaced=off: advanced
Remote debugging from host ...
monitor exit
(gdb) Killing process(es): ...
testcase .../gdb/testsuite/gdb.base/step-over-no-symbols.exp completed in 2 seconds

	gdb/
	* arch-utils.c (gdbarch_info_fill): Set `default_byte_order' to
	the endianness selected.
	* NEWS: Document `set endian auto' mode operation update.

	gdb/doc/
	* gdb.texinfo (Choosing Target Byte Order): Document endianness
	selection details with the `set endian auto' mode.

	gdb/testsuite
	* gdb.base/endian.exp: New test.
	* gdb.base/endian.c: New test source.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23937, powerpc64le local ifunc IRELATIVE relocs are wrong
@ 2018-11-30  7:11 sergiodj+buildbot
  2018-11-30 10:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-30  7:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba85c15dabe144e4bcee5a1b388b32bee10729e1 ***

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

PR23937, powerpc64le local ifunc IRELATIVE relocs are wrong

IFUNC resolvers must always be called via their global entry point.
They will be called from ld.so rather than from the local executable.

	PR 23937
bfd/
	* elf64-ppc.c (write_plt_relocs_for_local_syms): Don't add local
	entry offset for ifuncs.
ld/
	* testsuite/ld-powerpc/pr23937.d,
	* testsuite/ld-powerpc/pr23937.s: New test.
	* testsuite/ld-powerpc/powerpc.exp: Run it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix leak in forward-search
@ 2018-11-29 23:31 sergiodj+buildbot
  2018-11-30  1:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-29 23:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95b1f9ac6b7de84b09580bdf2456955bcff86da1 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 95b1f9ac6b7de84b09580bdf2456955bcff86da1

Fix leak in forward-search

Valgrind reports the below leak.
Fix the leak by using xrealloc, even for the first allocation,
as buf is static.

==29158== 5,888 bytes in 23 blocks are definitely lost in loss record 3,028 of 3,149
==29158==    at 0x4C2BE2D: malloc (vg_replace_malloc.c:299)
==29158==    by 0x41B557: xmalloc (common-utils.c:44)
==29158==    by 0x60B7D9: forward_search_command(char const*, int) (source.c:1563)
==29158==    by 0x40BA68: cmd_func(cmd_list_element*, char const*, int) (cli-decode.c:1888)
==29158==    by 0x665300: execute_command(char const*, int) (top.c:630)
...

gdb/ChangeLog
2018-11-29  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* source.c (forward_search_command): Fix leak by using
	xrealloc even for the first allocation in the loop, as buf
	is static.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Implement the "gdb_signal_to/from_target" gdbarch methods for FreeBSD.
@ 2018-11-29 22:18 sergiodj+buildbot
  2018-11-30  1:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-29 22:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e61667ef1413b9fba1bb9dc78744329f8215de74 ***

Author: Rajendra SY <rajendra.sy@gmail.com>
Branch: master
Commit: e61667ef1413b9fba1bb9dc78744329f8215de74

Implement the "gdb_signal_to/from_target" gdbarch methods for FreeBSD.

This fixes failures in the gdb.base/exitsignal.exp test.

gdb/ChangeLog:

	PR gdb/23093
	* gdb/fbsd-tdep.c (fbsd_gdb_signal_from_target)
	(fbsd_gdb_signal_to_target): New.
	(fbsd_init_abi): Install gdbarch "signal_from_target" and
	"signal_to_target" methods.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add missing c.unimp instruction.
@ 2018-11-29 21:41 sergiodj+buildbot
  2018-11-29 22:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-29 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12951a2f080abfd23d0aae0a9a5b2c322fd25c9e ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 12951a2f080abfd23d0aae0a9a5b2c322fd25c9e

RISC-V: Add missing c.unimp instruction.

	opcodes/
	* riscv-opc.c (unimp): Mark compressed unimp as INSN_ALIAS.
	(c.unimp): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid buffer overflow in value_x_unop
@ 2018-11-29 18:55 sergiodj+buildbot
  2018-11-29 20:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-29 18:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d5500e9580ec0f3cffeb1f1373834cbc1d2101d ***

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

Avoid buffer overflow in value_x_unop

Commit 6b1747cd1 ("invoke_xmethod & array_view") contains this change:

-  argvec = (struct value **) alloca (sizeof (struct value *) * 4);
+  value *argvec_storage[3];
+  gdb::array_view<value *> argvec = argvec_storage;

However, value_x_unop still does:

      argvec[2] = value_from_longest (builtin_type (gdbarch)->builtin_int, 0);
      argvec[3] = 0;

This triggers an error with -fsanitize=address from userdef.exp:

ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffdcf185068 at pc 0x000000e4f912 bp 0x7ffdcf184d80 sp 0x7ffdcf184d70
WRITE of size 8 at 0x7ffdcf185068 thread T0
    #0 0xe4f911 in value_x_unop(value*, exp_opcode, noside) ../../binutils-gdb/gdb/valarith.c:557
[...]

I think the two assignments to argvec[3] should just be removed, and
that this was intended in the earlier patch but just missed.

This passes userdef.exp with -fsanitize=address.

gdb/ChangeLog
2018-11-29  Tom Tromey  <tom@tromey.com>

	* valarith.c (value_x_unop): Don't set argvec[3].


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix use-after-free in gdbserver
@ 2018-11-29 18:14 sergiodj+buildbot
  2018-11-29 19:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-29 18:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d105de22fc385da878e8db44c9503a7f30419322 ***

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

Fix use-after-free in gdbserver

-fsanitize=address pointed out a use-after-free in gdbserver.  In
particular, handle_detach could reference "process" after it was
deleted by detach_inferior.  Avoiding this also necessitated changing
target_ops::join to take a pid rather than a process_info*.

Tested by the buildbot using a few of the gdbserver builders.

gdb/gdbserver/ChangeLog
2018-11-29  Tom Tromey  <tom@tromey.com>

	* win32-low.c (win32_join): Take pid, not process.
	* target.h (struct target_ops) <join>: Change argument type.
	(join_inferior): Change argument name.
	* spu-low.c (spu_join): Take pid, not process.
	* server.c (handle_detach): Preserve pid before destroying
	process.
	* lynx-low.c (lynx_join): Take pid, not process.
	* linux-low.c (linux_join): Take pid, not process.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] elf: Don't merge .note.gnu.property section in IR
@ 2018-11-29 13:41 sergiodj+buildbot
  2018-11-29 14:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-29 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ffd9e4d0225d45d1603d09e06151c388589e063f ***

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

elf: Don't merge .note.gnu.property section in IR

.note.gnu.property section in IR inputs should be ignored.  Don't
merge them.

	PR ld/23929
	* elf-properties.c (_bfd_elf_link_setup_gnu_properties): Don't
	merge .note.gnu.property section in IR inputs.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add .insn CA support.
@ 2018-11-27 20:10 sergiodj+buildbot
  2018-11-27 21:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-27 20:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4765cd611992862c844e8f152c5dbaadaecc25ce ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 4765cd611992862c844e8f152c5dbaadaecc25ce

RISC-V: Add .insn CA support.

	gas/
	* config/tc-riscv.c (validate_riscv_insn) <'F'>: Add support for CF6
	and CF2 operands.
	(riscv_ip) <'F'>: Likewise.
	* doc/c-riscv.texi (RISC-V-Formats): Add func6 abbreviation.  Use rs2
	instead of rs1 in CR description.  Add CA docs.
	* gas/testsuite/riscv/insn.s: Add use of .insn ca.
	* gas/testsuite/riscv/insn.d: Update to match.
	include/
	* opcode/riscv.h (OP_MASK_CFUNCT6, OP_SH_CFUNCT6): New.
	(OP_MASK_CFUNCT2, OP_SH_CFUNCT2): New.
	opcodes/
	* riscv-opc.c (ciw): Fix whitespace to align columns.
	(ca): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARM] Update knowledge of bfd architectures
@ 2018-11-27 19:07 sergiodj+buildbot
  2018-11-27 20:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-27 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5ab31636d36e1252791cec179aa11ab9d9b87e9 ***

Author: Thomas Preud'homme <thomas.preudhomme@linaro.org>
Branch: master
Commit: b5ab31636d36e1252791cec179aa11ab9d9b87e9

[ARM] Update knowledge of bfd architectures

Commit c0c468d562649df0f695737262b6230b7a56a4bb updated bfd's knowledge
of Arm architectures to Armv5TEJ and later but missed the list of CPUs
recognized by objdump -d -m<cpu>.

.note.gnu.arm.ident related code is intentionally not updated as build
attributes are a better mechanism to express the ISA in a file. However
this patch adds tests for the existing code since no existing testcase
cover those codepaths. Since I've only ever managed for
bfd_arm_get_mach_from_notes () to have an effect by using objcopy on
a file with a note but no Arm build attribute, the tests make use of
both objcopy actions supported by run_dump_test which requires to have a
ld line as well.

Note that the CPU list in bfd/cpu-arm.c was simply copied over from
GAS' CPU list but sorted alphabetically as already done for existing
entries.

2018-11-27  Thomas Preud'homme  <thomas.preudhomme@linaro.org>

bfd/
	* cpu-arm.c (processors): Add processors known to GAS but missing here
	and reindent.
	(bfd_arm_update_notes): Add comment explaining why the list of
	architectures in the switch should not be updated.
	(architectures): Likewise.

gas/
	* testsuite/gas/arm/cpu-arm1020.d: New testcase.
	* testsuite/gas/arm/cpu-arm1020e.d: Likewise.
	* testsuite/gas/arm/cpu-arm1020t.d: Likewise.
	* testsuite/gas/arm/cpu-arm1022e.d: Likewise.
	* testsuite/gas/arm/cpu-arm1026ej-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm1026ejs.d: Likewise.
	* testsuite/gas/arm/cpu-arm10e.d: Likewise.
	* testsuite/gas/arm/cpu-arm10t.d: Likewise.
	* testsuite/gas/arm/cpu-arm10tdmi.d: Likewise.
	* testsuite/gas/arm/cpu-arm1136j-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm1136jf-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm1136jfs.d: Likewise.
	* testsuite/gas/arm/cpu-arm1136js.d: Likewise.
	* testsuite/gas/arm/cpu-arm1156t2-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm1156t2f-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm1176jz-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm1176jzf-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm2.d: Likewise.
	* testsuite/gas/arm/cpu-arm250.d: Likewise.
	* testsuite/gas/arm/cpu-arm3.d: Likewise.
	* testsuite/gas/arm/cpu-arm6.d: Likewise.
	* testsuite/gas/arm/cpu-arm60.d: Likewise.
	* testsuite/gas/arm/cpu-arm600.d: Likewise.
	* testsuite/gas/arm/cpu-arm610.d: Likewise.
	* testsuite/gas/arm/cpu-arm620.d: Likewise.
	* testsuite/gas/arm/cpu-arm7.d: Likewise.
	* testsuite/gas/arm/cpu-arm70.d: Likewise.
	* testsuite/gas/arm/cpu-arm700.d: Likewise.
	* testsuite/gas/arm/cpu-arm700i.d: Likewise.
	* testsuite/gas/arm/cpu-arm710.d: Likewise.
	* testsuite/gas/arm/cpu-arm7100.d: Likewise.
	* testsuite/gas/arm/cpu-arm710c.d: Likewise.
	* testsuite/gas/arm/cpu-arm710t.d: Likewise.
	* testsuite/gas/arm/cpu-arm720.d: Likewise.
	* testsuite/gas/arm/cpu-arm720t.d: Likewise.
	* testsuite/gas/arm/cpu-arm740t.d: Likewise.
	* testsuite/gas/arm/cpu-arm7500.d: Likewise.
	* testsuite/gas/arm/cpu-arm7500fe.d: Likewise.
	* testsuite/gas/arm/cpu-arm7d.d: Likewise.
	* testsuite/gas/arm/cpu-arm7di.d: Likewise.
	* testsuite/gas/arm/cpu-arm7dm.d: Likewise.
	* testsuite/gas/arm/cpu-arm7dmi.d: Likewise.
	* testsuite/gas/arm/cpu-arm7m.d: Likewise.
	* testsuite/gas/arm/cpu-arm7t.d: Likewise.
	* testsuite/gas/arm/cpu-arm7tdmi-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm7tdmi.d: Likewise.
	* testsuite/gas/arm/cpu-arm8.d: Likewise.
	* testsuite/gas/arm/cpu-arm810.d: Likewise.
	* testsuite/gas/arm/cpu-arm9.d: Likewise.
	* testsuite/gas/arm/cpu-arm920.d: Likewise.
	* testsuite/gas/arm/cpu-arm920t.d: Likewise.
	* testsuite/gas/arm/cpu-arm922t.d: Likewise.
	* testsuite/gas/arm/cpu-arm926ej-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm926ej.d: Likewise.
	* testsuite/gas/arm/cpu-arm926ejs.d: Likewise.
	* testsuite/gas/arm/cpu-arm940t.d: Likewise.
	* testsuite/gas/arm/cpu-arm946e-r0.d: Likewise.
	* testsuite/gas/arm/cpu-arm946e-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm946e.d: Likewise.
	* testsuite/gas/arm/cpu-arm966e-r0.d: Likewise.
	* testsuite/gas/arm/cpu-arm966e-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm966e.d: Likewise.
	* testsuite/gas/arm/cpu-arm968e-s.d: Likewise.
	* testsuite/gas/arm/cpu-arm9e-r0.d: Likewise.
	* testsuite/gas/arm/cpu-arm9e.d: Likewise.
	* testsuite/gas/arm/cpu-arm9tdmi.d: Likewise.
	* testsuite/gas/arm/cpu-arm_any.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a12.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a15.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a17.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a32.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a35.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a5.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a53.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a55.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a57.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a7.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a72.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a73.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a75.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a76.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a8.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-a9.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m0.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m0plus.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m1.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m23.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m3.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m33.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m4.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-m7.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-r4.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-r4f.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-r5.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-r52.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-r7.d: Likewise.
	* testsuite/gas/arm/cpu-cortex-r8.d: Likewise.
	* testsuite/gas/arm/cpu-ep9312.d: Likewise.
	* testsuite/gas/arm/cpu-exynos-m1.d: Likewise.
	* testsuite/gas/arm/cpu-fa526.d: Likewise.
	* testsuite/gas/arm/cpu-fa606te.d: Likewise.
	* testsuite/gas/arm/cpu-fa616te.d: Likewise.
	* testsuite/gas/arm/cpu-fa626.d: Likewise.
	* testsuite/gas/arm/cpu-fa626te.d: Likewise.
	* testsuite/gas/arm/cpu-fa726te.d: Likewise.
	* testsuite/gas/arm/cpu-fmp626.d: Likewise.
	* testsuite/gas/arm/cpu-i80200.d: Likewise.
	* testsuite/gas/arm/cpu-iwmmxt.d: Likewise.
	* testsuite/gas/arm/cpu-iwmmxt2.d: Likewise.
	* testsuite/gas/arm/cpu-marvell-pj4.d: Likewise.
	* testsuite/gas/arm/cpu-marvell-whitney.d: Likewise.
	* testsuite/gas/arm/cpu-mpcore.d: Likewise.
	* testsuite/gas/arm/cpu-mpcorenovfp.d: Likewise.
	* testsuite/gas/arm/cpu-sa1.d: Likewise.
	* testsuite/gas/arm/cpu-strongarm.d: Likewise.
	* testsuite/gas/arm/cpu-strongarm1.d: Likewise.
	* testsuite/gas/arm/cpu-strongarm110.d: Likewise.
	* testsuite/gas/arm/cpu-strongarm1100.d: Likewise.
	* testsuite/gas/arm/cpu-strongarm1110.d: Likewise.
	* testsuite/gas/arm/cpu-xgene1.d: Likewise.
	* testsuite/gas/arm/cpu-xgene2.d: Likewise.
	* testsuite/gas/arm/cpu-xscale.d: Likewise.
	* testsuite/gas/arm/nop-asm.s: Likewise.
	* testsuite/gas/arm/note-march-armv2.d: Likewise.
	* testsuite/gas/arm/note-march-armv2.s: Likewise.
	* testsuite/gas/arm/note-march-armv2a.d: Likewise.
	* testsuite/gas/arm/note-march-armv2a.s: Likewise.
	* testsuite/gas/arm/note-march-armv3.d: Likewise.
	* testsuite/gas/arm/note-march-armv3.s: Likewise.
	* testsuite/gas/arm/note-march-armv3m.d: Likewise.
	* testsuite/gas/arm/note-march-armv3m.s: Likewise.
	* testsuite/gas/arm/note-march-armv4.d: Likewise.
	* testsuite/gas/arm/note-march-armv4.s: Likewise.
	* testsuite/gas/arm/note-march-armv4t.d: Likewise.
	* testsuite/gas/arm/note-march-armv4t.s: Likewise.
	* testsuite/gas/arm/note-march-armv5.d: Likewise.
	* testsuite/gas/arm/note-march-armv5.s: Likewise.
	* testsuite/gas/arm/note-march-armv5t.d: Likewise.
	* testsuite/gas/arm/note-march-armv5t.s: Likewise.
	* testsuite/gas/arm/note-march-armv5te.d: Likewise.
	* testsuite/gas/arm/note-march-armv5te.d: Likewise.
	* testsuite/gas/arm/note-march-ep9312.d: Likewise.
	* testsuite/gas/arm/note-march-ep9312.s: Likewise.
	* testsuite/gas/arm/note-march-iwmmxt.d: Likewise.
	* testsuite/gas/arm/note-march-iwmmxt.s: Likewise.
	* testsuite/gas/arm/note-march-iwmmxt2.d: Likewise.
	* testsuite/gas/arm/note-march-iwmmxt2.s: Likewise.
	* testsuite/gas/arm/note-march-xscale.d: Likewise.
	* testsuite/gas/arm/note-march-xscale.s: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/LD: Accept high-part relocations in PIC code with absolute symbols
@ 2018-11-27 17:58 sergiodj+buildbot
  2018-11-27 19:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-27 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c7687b9cdacc243f7e23cd9b144e72b88d58817 ***

Author: Maciej W. Rozycki <macro@linux-mips.org>
Branch: master
Commit: 3c7687b9cdacc243f7e23cd9b144e72b88d58817

MIPS/LD: Accept high-part relocations in PIC code with absolute symbols

Accept R_MIPS_HI16, R_MIPS_HIGHER and R_MIPS_HIGHEST relocations and
their compressed counterparts in PIC code where the symbol referred is
absolute.  Such an operation is meaningful, because an absolute symbol
effectively is a constant the calculation of the value of which has been
deferred to the static link time, and which is not going to change any
further at the dynamic load time.  Therefore there is no need ever to
refuse the use of these relocations with such symbols, as the resulting
run-time value observed by the program will be correct even in PIC code.

This is not the case with R_MIPS_26 and its compressed counterparts,
because the run-time value calculated by the instructions these
relocations are used with depends on the address of the instruction
itself, and that can change according to the base address used by the
dynamic loader.  Therefore these relocations have to continue being
rejected in PIC code even with absolute symbols.

This allows successful linking of code that relies on previous linker
behavior up to commit 861fb55ab50a ("Defer allocation of R_MIPS_REL32
GOT slots"), <https://sourceware.org/ml/binutils/2008-08/msg00096.html>,
which introduced the problematic check missing this special exception
for absolute symbols.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_check_relocs) <R_MIPS16_HI16>
	<R_MIPS_HI16, R_MIPS_HIGHER, R_MIPS_HIGHEST, R_MICROMIPS_HI16>
	<R_MICROMIPS_HIGHER, R_MICROMIPS_HIGHEST>: Also accept an
	absolute symbol in PIC code.

	ld/
	* testsuite/ld-mips-elf/pic-reloc-0.d: New test.
	* testsuite/ld-mips-elf/pic-reloc-1.d: New test.
	* testsuite/ld-mips-elf/pic-reloc-2.d: New test.
	* testsuite/ld-mips-elf/pic-reloc-3.d: New test.
	* testsuite/ld-mips-elf/pic-reloc-4.d: New test.
	* testsuite/ld-mips-elf/pic-reloc-absolute-hi.ld: New test
	linker script.
	* testsuite/ld-mips-elf/pic-reloc-absolute-lo.ld: New test
	linker script.
	* testsuite/ld-mips-elf/pic-reloc-ordinary.ld: New test linker
	script.
	* testsuite/ld-mips-elf/pic-reloc-j.s: New test source.
	* testsuite/ld-mips-elf/pic-reloc-lui.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/LD: Continue processing with refused relocations in PIC code
@ 2018-11-27 17:21 sergiodj+buildbot
  2018-11-27 18:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-27 17:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aff68bd0415c6f834cf1717865b5b44dea6b9ef5 ***

Author: Maciej W. Rozycki <macro@linux-mips.org>
Branch: master
Commit: aff68bd0415c6f834cf1717865b5b44dea6b9ef5

MIPS/LD: Continue processing with refused relocations in PIC code

Switch from `_bfd_error_handler' to `info->callbacks->einfo' with error
reporting concerning the use of position-dependent relocations such as
R_MIPS_HI16 or R_MIPS_26 in PIC code and continue processing so that any
subsequent link errors are also shown rather than the linker terminating
right away.  This can reduce user frustration where correcting one error
only reveals another one; instead all are shown together making them all
possible to investigate at once.  The use of the `%X' specifier causes
the linker to terminate unsuccessfully at the end of processing.

Also fix the message to say `cannot' rather than `can not'.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_check_relocs) <R_MIPS16_26>
	<R_MIPS_26, R_MICROMIPS_26_S1>: Use `info->callbacks->einfo'
	rather than `_bfd_error_handler' to report refused relocations
	in PIC code and continue processing.  Fix error message: `can
	not' -> `cannot'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Initialize *uncompressed_align_pow_p to 0
@ 2018-11-27 15:46 sergiodj+buildbot
  2018-11-27 16:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-27 15:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 131a5a648d314cd15811158150573cb40eb3abd0 ***

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

Initialize *uncompressed_align_pow_p to 0

Initialize *uncompressed_align_pow_p to 0 since *uncompressed_align_pow_p
is passed to bfd_is_section_compressed_with_header as uninitialized,

	PR binutils/23919
	* compress.c (bfd_is_section_compressed_with_header): Initialize
	*uncompressed_align_pow_p to 0.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Fix regression in Cortex A53 erratum when PIE. (PR ld/23904)
@ 2018-11-27 13:47 sergiodj+buildbot
  2018-11-27 14:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-27 13:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fca35fc3486283562a7fcd9eb0ff845b0152d98 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 9fca35fc3486283562a7fcd9eb0ff845b0152d98

AArch64: Fix regression in Cortex A53 erratum when PIE. (PR ld/23904)

The fix for PR ld/22263 causes TLS relocations using ADRP to be relaxed
into MOVZ, however this causes issues for the erratum code.

The erratum code scans the input sections looking for ADRP instructions
and notes their location in the stream.

It then later tries to find them again in order to generate the linker
stubs.  Due to the relaxation it instead finds a MOVZ and hard aborts.

Since this relaxation is a valid one, and in which case the erratum no
longer applies, it shouldn't abort but instead just continue.

This changes the TLS relaxation code such that when it finds an ADRP and
it relaxes it, it removes the erratum entry from the work list by changing
the stub type into none so the stub is ignored.

The entry is not actually removed as removal is a more expensive operation
and we have already allocated the memory anyway.

The clearing is done for IE->LE and GD->LE relaxations, and a testcase is
added for the IE case. The GD case I believe to be impossible to get together
with the erratum sequence due to the required BL which would break the sequence.
However to cover all basis I have added the guard there as well.

build on native hardware and regtested on
  aarch64-none-elf, aarch64-none-elf (32 bit host),
  aarch64-none-linux-gnu, aarch64-none-linux-gnu (32 bit host)

Cross-compiled and regtested on
  aarch64-none-linux-gnu, aarch64_be-none-linux-gnu

Testcase in PR23940 tested and works as expected now and benchmarks ran on A53
showing no regressions and no issues.

bfd/ChangeLog:

	PR ld/23904
	* elfnn-aarch64.c (_bfd_aarch64_adrp_p): Use existing constants.
	(_bfd_aarch64_erratum_843419_branch_to_stub): Use _bfd_aarch64_adrp_p.
	(struct erratum_835769_branch_to_stub_clear_data): New.
	(_bfd_aarch64_erratum_843419_clear_stub): New.
	(clear_erratum_843419_entry): New.
	(elfNN_aarch64_tls_relax): Use it.
	(elfNN_aarch64_relocate_section): Pass input_section.
	(aarch64_map_one_stub): Handle branch type none as valid.

ld/ChangeLog:

	PR ld/23904
	* testsuite/ld-aarch64/aarch64-elf.exp: Add erratum843419_tls_ie.
	* testsuite/ld-aarch64/erratum843419_tls_ie.d: New test.
	* testsuite/ld-aarch64/erratum843419_tls_ie.s: New test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix spurious semicolon in sparc-linux-nat.c
@ 2018-11-26 22:26 sergiodj+buildbot
  2018-11-26 23:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-26 22:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed2df75c51551cf9b44f7d94179849565ab5bdda ***

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

Fix spurious semicolon in sparc-linux-nat.c

Remove a semicolon that should not be there, as reported in PR 23917:

  CXX    sparc-linux-nat.o
/home/emaisin/src/binutils-gdb/gdb/sparc-linux-nat.c:39:3: error: expected unqualified-id before { token
   { sparc_store_inferior_registers (regcache, regnum); }
   ^

Tested by rebuilding the file manually (make sparc-linux-nat.o) in a
sparc64-linux-gnu build.

gdb/ChangeLog:

	PR gdb/23917
	* sparc-linux-nat.c (sparc_linux_nat_target): Remove extraneous
	semicolon.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix Solaris build
@ 2018-11-26 14:27 sergiodj+buildbot
  2018-11-26 14:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-26 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 24bce9bbe510c9efa36c0f85fb2f8a93ec8b623e ***

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

Fix Solaris build

The recent commit 080363310650 ("Per-inferior thread list, thread
ranges/iterators, down with ALL_THREADS, etc.") removed the
definitions of is_running/is_stopped/is_exited but missed updating a
couple uses of is_exited in Solaris-specific code.

Tested by Rainer Orth on amd64-pc-solaris2.11.

gdb/ChangeLog:
2018-11-26  Pedro Alves  <palves@redhat.com>

	* procfs.c (procfs_notice_thread): Replace uses of
	in_thread_list/is_exited with find_thread_ptid/THREAD_EXITED.
	* sol-thread.c (sol_thread_target::wait)
	(sol_update_thread_list_callback): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Implement timestamp'ed output on "make check"
@ 2018-11-25 23:41 sergiodj+buildbot
  2018-11-26  1:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-25 23:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f63c03b470036353c8c6c657e15f5ebd62ab67dd ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: f63c03b470036353c8c6c657e15f5ebd62ab67dd

Implement timestamp'ed output on "make check"

It is unfortunately not uncommon to have tests hanging on some of the
BuildBot workers.  For example, the ppc64be/ppc64le+gdbserver builders
are especially in a bad state when it comes to testing GDB/gdbserver,
and we can have builds that take an absurd amount of time to
finish (almost 1 week for one single build, for example).

It may be hard to diagnose these failures, because sometimes we don't
have access to the faulty systems, and other times we're just too busy
to wait and check which test is actually hanging.  During one of our
conversations about the topic, someone proposed that it would be a
good idea to have a timestamp put together with stdout output, so that
we can come back later and examine which tests are taking too long to
complete.

Here's my proposal to do this.  The very first thing I tried to do was
to use "ts(1)" to achieve this feature, and it obviously worked, but
the problem is that I'm afraid "ts(1)" may not be widely available on
every system we support.  Therefore, I decided to implement a *very*
simple version of "ts(1)", in Python 3, which basically does the same
thing: iterate over the stdin lines, and prepend a timestamp onto
them.

As for testsuite/Makefile.in, the user can now specify two new
variables to enable timestamp'ed output: TS (which enables the
output), and TS_FORMAT (optional, used to specify another timestamp
format according to "strftime").

Here's an example of how the output looks like:

  ...
  [Nov 22 17:07:19] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/call-strs.exp ...
  [Nov 22 17:07:19] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/step-over-no-symbols.exp ...
  [Nov 22 17:07:20] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/all-architectures-6.exp ...
  [Nov 22 17:07:20] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/hashline3.exp ...
  [Nov 22 17:07:20] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/max-value-size.exp ...
  [Nov 22 17:07:20] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/quit-live.exp ...
  [Nov 22 17:07:46] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/paginate-bg-execution.exp ...
  [Nov 22 17:07:56] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/gcore-buffer-overflow.exp ...
  [Nov 22 17:07:56] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/gcore-relro.exp ...
  [Nov 22 17:07:56] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/watchpoint-delete.exp ...
  [Nov 22 17:07:56] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/breakpoint-in-ro-region.exp ...
  [Nov 22 17:07:56] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/vla-sideeffect.exp ...
  [Nov 22 17:07:57] [1234] Running binutils-gdb/gdb/testsuite/gdb.base/unload.exp ...
  ...

(What, gdb.base/quit-live.exp is taking 26 seconds to complete?!)

Output to stderr is not timestamp'ed, but I don't think that will be a
problem for us.  If it is, we can revisit the solution and extend it.

gdb/testsuite/ChangeLog:
2018-11-25  Sergio Durigan Junior  <sergiodj@redhat.com>

	* Makefile.in (TIMESTAMP): New variable.
	(check-single): Add $(TIMESTAMP) to the end of $(DO_RUNTEST)
	command.
	(check-single-racy): Likewise.
	(check/%.exp): Likewise.
	(check-racy/%.exp): Likewise.
	(workers/%.worker): Likewise.
	(build-perf): Likewise.
	(check-perf): Likewise.
	* README: Describe new "TS" and "TS_FORMAT" variables.
	* print-ts.py: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove obsolete comments from field_fmt
@ 2018-11-25 23:04 sergiodj+buildbot
  2018-11-26  0:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-25 23:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5b12e1dbe0f2739624f91621828df73ef55e900 ***

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

Remove obsolete comments from field_fmt

This removes some comments that I believe were made obsolete by the
recent change to cli_ui_out::do_field_fmt.  The comment in mi_ui_out
probably was just copy/paste, because I think aligning never made
sense in an MI context.

gdb/ChangeLog
2018-11-25  Tom Tromey  <tom@tromey.com>

	* ui-out.c (ui_out::field_fmt): Remove comment.
	* tui/tui-out.c (tui_ui_out::do_field_fmt): Remove comment.
	* mi/mi-out.c (mi_ui_out::do_field_fmt): Remove comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Re-fix leak in source.c (open_source_file).
@ 2018-11-24 12:23 sergiodj+buildbot
  2018-11-24 13:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-24 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5446094655df842abb4ababac39f34c6342e8da3 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 5446094655df842abb4ababac39f34c6342e8da3

Re-fix leak in source.c (open_source_file).

Leak fixed in '8e6a5953e1d Fix 4K leak in open_source_file' has been partially
undone by '2179fbc36d23 Return scoped_fd from open_source_file'. Re-add the
transfer of current s->fullname to the unique_xmalloc_ptr fullname given to
find_and_open_source.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdbserver: AArch64: Remove cannot_fetch/store_register
@ 2018-11-23 14:34 sergiodj+buildbot
  2018-11-23 16:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-23 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5013824590f59374106007d4c9724d5767911d75 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 5013824590f59374106007d4c9724d5767911d75

gdbserver: AArch64: Remove cannot_fetch/store_register

The cannot store/fetch register functions are only used for checking
if a register can be accessed using PEEKUSER/POKEUSER.
The AArch64 port doesn't support this method of access, so remove the
unused functions.

gdb/gdbserver:
	* linux-aarch64-low.c (aarch64_cannot_store_register): Remove.
	(aarch64_cannot_fetch_register): Likewise.
	(struct linux_target_ops): Update references.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix follow_exec latent problem
@ 2018-11-22 18:39 sergiodj+buildbot
  2018-11-22 18:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-22 18:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4c17fb0f5879d3f58c733a4139fa59817e8155e ***

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

Fix follow_exec latent problem

A following commit to make each inferior have its own thread list
exposes a problem with bf93d7ba99 ("Add thread after updating gdbarch
when exec'ing"), which is that we can't defer adding the thread
because that breaks try_open_exec_file which deep inside ends up
calling inferior_thread():

 #5  0x0000000000637c78 in internal_error(char const*, int, char const*, ...) (file=0xc151f8 "src/gdb/thread.c", line=165, fmt=0xc15180 "%s: Assertion `%s' failed.") at src/gdb/common/errors.c:55
 #6  0x00000000008a3d80 in inferior_thread() () at src/gdb/thread.c:165
 #7  0x0000000000456f91 in try_thread_db_load_1(thread_db_info*) (info=0x277eb00) at src/gdb/linux-thread-db.c:830
 #8  0x0000000000457554 in try_thread_db_load(char const*, int) (library=0xb01a4f "libthread_db.so.1", check_auto_load_safe=0)
     at src/gdb/linux-thread-db.c:1002
 #9  0x0000000000457861 in try_thread_db_load_from_sdir() () at src/gdb/linux-thread-db.c:1079
 #10 0x0000000000457b72 in thread_db_load_search() () at src/gdb/linux-thread-db.c:1134
 #11 0x0000000000457d29 in thread_db_load() () at src/gdb/linux-thread-db.c:1192
 #12 0x0000000000457e51 in check_for_thread_db() () at src/gdb/linux-thread-db.c:1244
 #13 0x0000000000457ed2 in thread_db_new_objfile(objfile*) (objfile=0x270ff60) at src/gdb/linux-thread-db.c:1273
 #14 0x000000000045a92e in std::_Function_handler<void (objfile*), void (*)(objfile*)>::_M_invoke(std::_Any_data const&, objfile*&&) (__functor=..., __args#0=@0x7ffef3efe140: 0x270ff60) at /usr/include/c++/7/bits/std_function.h:316
 #15 0x00000000007bbebf in std::function<void (objfile*)>::operator()(objfile*) const (this=0x24e1d18, __args#0=0x270ff60)
     at /usr/include/c++/7/bits/std_function.h:706
 #16 0x00000000007bba86 in gdb::observers::observable<objfile*>::notify(objfile*) const (this=0x117ce80 <gdb::observers::new_objfile>, args#0=0x270ff60) at src/gdb/common/observable.h:106
 #17 0x0000000000856000 in symbol_file_add_with_addrs(bfd*, char const*, symfile_add_flags, section_addr_info*, objfile_flags, objfile*) (abfd=0x1d7dae0, name=0x254bfc0 "/ho

The problem is latent currently because inferior_thread() at that
point manages to return a thread, even though it's the wrong one (of
the old inferior).

The problem originally fixed by bf93d7ba99 was:

    (...) we should avoid doing register reads
    after a process does an exec and before we've updated that inferior's
    gdbarch.  Otherwise, we may interpret the registers using the wrong
    architecture.

    (...) The call to "add_thread" done just after adding the inferior is
    problematic, because it ends up reading the registers (because the ptid
    is re-used, we end up doing a switch_to_thread to it, which tries to
    update stop_pc). (...)

The register-reading issue is no longer a problem nowadays, ever since
switch_to_thread stopped reading the stop_pc in git commit
f2ffa92bbce9 ("gdb: Eliminate the 'stop_pc' global").

So this commit basically reverts bf93d7ba99.

gdb/ChangeLog:
2018-11-22  Pedro Alves  <palves@redhat.com>

	* infrun.c (follow_exec) <set follow-exec new>: Add thread and
	switch to it before calling into try_open_exec_file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Per-inferior thread list, thread ranges/iterators, down with ALL_THREADS, etc.
@ 2018-11-22 16:58 sergiodj+buildbot
  2018-11-22 20:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-22 16:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 080363310650c93ad8e93018bcb6760ba5d32d1c ***

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

Per-inferior thread list, thread ranges/iterators, down with ALL_THREADS, etc.

As preparation for multi-target, this patch makes each inferior have
its own thread list.

This isn't absolutely necessary for multi-target, but simplifies
things.  It originally stemmed from the desire to eliminate the
init_thread_list calls sprinkled around, plus it makes it more
efficient to iterate over threads of a given inferior (no need to
always iterate over threads of all inferiors).

We still need to iterate over threads of all inferiors in a number of
places, which means we'd need adjust the ALL_THREADS /
ALL_NON_EXITED_THREADS macros.  However, naively tweaking those macros
to have an extra for loop, like:

     #define ALL_THREADS (thr, inf) \
       for (inf = inferior_list; inf; inf = inf->next) \
	 for (thr = inf->thread_list; thr; thr = thr->next)

causes problems with code that does "break" or "continue" within the
ALL_THREADS loop body.  Plus, we need to declare the extra "inf" local
variable in order to pass it as temporary variable to ALL_THREADS
(etc.)

It gets even trickier when we consider extending the macros to filter
out threads matching a ptid_t and a target.  The macros become tricker
to read/write.  Been there.

An alternative (which was my next attempt), is to replace the
ALL_THREADS etc. iteration style with for_each_all_threads,
for_each_non_exited_threads, etc. functions which would take a
callback as parameter, which would usually be passed a lambda.
However, I did not find that satisfactory at all, because the
resulting code ends up a little less natural / more noisy to read,
write and debug/step-through (due to use of lambdas), and in many
places where we use "continue;" to skip to the next thread now need to
use "return;".  (I ran into hard to debug bugs caused by a
continue/return confusion.)

I.e., before:

    ALL_NON_EXITED_THREADS (tp)
      {
	if (tp->not_what_I_want)
	  continue;
	// do something
      }

would turn into:

    for_each_non_exited_thread ([&] (thread_info *tp)
      {
	if (tp->not_what_I_want)
	  return;
	// do something
      });

Lastly, the solution I settled with was to replace the ALL_THREADS /
ALL_NON_EXITED_THREADS / ALL_INFERIORS macros with (C++20-like) ranges
and iterators, such that you can instead naturaly iterate over
threads/inferiors using range-for, like e.g,.:

   // all threads, including THREAD_EXITED threads.
   for (thread_info *tp : all_threads ())
     { .... }

   // all non-exited threads.
   for (thread_info *tp : all_non_exited_threads ())
     { .... }

   // all non-exited threads of INF inferior.
   for (thread_info *tp : inf->non_exited_threads ())
     { .... }

The all_non_exited_threads() function takes an optional filter ptid_t as
parameter, which is quite convenient when we need to iterate over
threads matching that filter.  See e.g., how the
set_executing/set_stop_requested/finish_thread_state etc. functions in
thread.c end up being simplified.

Most of the patch thus is about adding the infrustructure for allowing
the above.  Later on when we get to actual multi-target, these
functions/ranges/iterators will gain a "target_ops *" parameter so
that e.g., we can iterate over all threads of a given target that
match a given filter ptid_t.

The only entry points users needs to be aware of are the
all_threads/all_non_exited_threads etc. functions seen above.  Thus,
those functions are declared in gdbthread.h/inferior.h.  The actual
iterators/ranges are mainly "internals" and thus are put out of view
in the new thread-iter.h/thread-iter.c/inferior-iter.h files.  That
keeps the gdbthread.h/inferior.h headers quite a bit more readable.

A common/safe-iterator.h header is added which adds a template that
can be used to build "safe" iterators, which are forward iterators
that can be used to replace the ALL_THREADS_SAFE macro and other
instances of the same idiom in future.

There's a little bit of shuffling of code between
gdbthread.h/thread.c/inferior.h in the patch.  That is necessary in
order to avoid circular dependencies between the
gdbthread.h/inferior.h headers.

As for the init_thread_list calls sprinkled around, they're all
eliminated by this patch, and a new, central call is added to
inferior_appeared.  Note how also related to that, there's a call to
init_wait_for_inferior in remote.c that is eliminated.
init_wait_for_inferior is currently responsible for discarding skipped
inline frames, which had to be moved elsewhere.  Given that nowadays
we always have a thread even for single-threaded processes, the
natural place is to delete a frame's inline frame info when we delete
the thread.  I.e., from clear_thread_inferior_resources.

gdb/ChangeLog:
2018-11-22  Pedro Alves  <palves@redhat.com>

	* Makefile.in (COMMON_SFILES): Add thread-iter.c.
	* breakpoint.c (breakpoints_should_be_inserted_now): Replace
	ALL_NON_EXITED_THREADS with all_non_exited_threads.
	(print_one_breakpoint_location): Replace ALL_INFERIORS with
	all_inferiors.
	* bsd-kvm.c: Include inferior.h.
	* btrace.c (btrace_free_objfile): Replace ALL_NON_EXITED_THREADS
	with all_non_exited_threads.
	* common/filtered-iterator.h: New.
	* common/safe-iterator.h: New.
	* corelow.c (core_target_open): Don't call init_thread_list here.
	* darwin-nat.c (thread_info_from_private_thread_info): Replace
	ALL_THREADS with all_threads.
	* fbsd-nat.c (fbsd_nat_target::resume): Replace
	ALL_NON_EXITED_THREADS with inf->non_exited_threads.
	* fbsd-tdep.c (fbsd_make_corefile_notes): Replace
	ALL_NON_EXITED_THREADS with inf->non_exited_threads.
	* fork-child.c (postfork_hook): Don't call init_thread_list here.
	* gdbarch-selftests.c (register_to_value_test): Adjust.
	* gdbthread.h: Don't include "inferior.h" here.
	(struct inferior): Forward declare.
	(enum step_over_calls_kind): Moved here from inferior.h.
	(thread_info::deletable): Definition moved to thread.c.
	(find_thread_ptid (inferior *, ptid_t)): Declare.
	(ALL_THREADS, ALL_THREADS_BY_INFERIOR, ALL_THREADS_SAFE): Delete.
	Include "thread-iter.h".
	(all_threads, all_non_exited_threads, all_threads_safe): New.
	(any_thread_p): Declare.
	(thread_list): Delete.
	* infcmd.c (signal_command): Replace ALL_NON_EXITED_THREADS with
	all_non_exited_threads.
	(proceed_after_attach_callback): Delete.
	(proceed_after_attach): Take an inferior pointer instead of an
	integer PID.  Adjust to use range-for.
	(attach_post_wait): Pass down inferior pointer instead of pid.
	Use range-for instead of ALL_NON_EXITED_THREADS.
	(detach_command): Remove init_thread_list call.
	* inferior-iter.h: New.
	* inferior.c (struct delete_thread_of_inferior_arg): Delete.
	(delete_thread_of_inferior): Delete.
	(delete_inferior, exit_inferior_1): Use range-for with
	inf->threads_safe() instead of iterate_over_threads.
	(inferior_appeared): Call init_thread_list here.
	(discard_all_inferiors): Use all_non_exited_inferiors.
	(find_inferior_id, find_inferior_pid): Use all_inferiors.
	(iterate_over_inferiors): Use all_inferiors_safe.
	(have_inferiors, number_of_live_inferiors): Use
	all_non_exited_inferiors.
	(number_of_inferiors): Use all_inferiors and std::distance.
	(print_inferior): Use all_inferiors.
	* inferior.h: Include gdbthread.h.
	(enum step_over_calls_kind): Moved to gdbthread.h.
	(struct inferior) <thread_list>: New field.
	<threads, non_exited_threads, threads_safe>: New methods.
	(ALL_INFERIORS): Delete.
	Include "inferior-iter.h".
	(ALL_NON_EXITED_INFERIORS): Delete.
	(all_inferiors_safe, all_inferiors, all_non_exited_inferiors): New
	functions.
	* inflow.c (child_interrupt, child_pass_ctrlc): Replace
	ALL_NON_EXITED_THREADS with all_non_exited_threads.
	* infrun.c (follow_exec): Use all_threads_safe.
	(clear_proceed_status, proceed): Use all_non_exited_threads.
	(init_wait_for_inferior): Don't clear inline frame state here.
	(infrun_thread_stop_requested, for_each_just_stopped_thread): Use
	all_threads instead of ALL_NON_EXITED_THREADS.
	(random_pending_event_thread): Use all_non_exited_threads instead
	of ALL_NON_EXITED_THREADS.  Use a lambda for repeated code.
	(clean_up_just_stopped_threads_fsms): Use all_non_exited_threads
	instead of ALL_NON_EXITED_THREADS.
	(handle_no_resumed): Use all_non_exited_threads instead of
	ALL_NON_EXITED_THREADS.  Use all_inferiors instead of
	ALL_INFERIORS.
	(restart_threads, switch_back_to_stepped_thread): Use
	all_non_exited_threads instead of ALL_NON_EXITED_THREADS.
	* linux-nat.c (check_zombie_leaders): Replace ALL_INFERIORS with
	all_inferiors.
	(kill_unfollowed_fork_children): Use inf->non_exited_threads
	instead of ALL_NON_EXITED_THREADS.
	* linux-tdep.c (linux_make_corefile_notes): Use
	inf->non_exited_threads instead of ALL_NON_EXITED_THREADS.
	* linux-thread-db.c (thread_db_target::update_thread_list):
	Replace ALL_INFERIORS with all_inferiors.
	(thread_db_target::thread_handle_to_thread_info): Use
	inf->non_exited_threads instead of ALL_NON_EXITED_THREADS.
	* mi/mi-interp.c (multiple_inferiors_p): New.
	(mi_on_resume_1): Simplify using all_non_exited_threads and
	multiple_inferiors_p.
	* mi/mi-main.c (mi_cmd_thread_list_ids): Use all_non_exited_threads
	instead of ALL_NON_EXITED_THREADS.
	* nto-procfs.c (nto_procfs_target::open): Don't call
	init_thread_list here.
	* record-btrace.c (record_btrace_target_open)
	(record_btrace_target::stop_recording)
	(record_btrace_target::close)
	(record_btrace_target::record_is_replaying)
	(record_btrace_target::resume, record_btrace_target::wait)
	(record_btrace_target::record_stop_replaying): Use
	all_non_exited_threads instead of ALL_NON_EXITED_THREADS.
	* record-full.c (record_full_wait_1): Use all_non_exited_threads
	instead of ALL_NON_EXITED_THREADS.
	* regcache.c (cooked_read_test): Remove reference to global
	thread_list.
	* remote-sim.c (gdbsim_target::create_inferior): Don't call
	init_thread_list here.
	* remote.c (remote_target::update_thread_list): Use
	all_threads_safe instead of ALL_NON_EXITED_THREADS.
	(remote_target::process_initial_stop_replies): Replace
	ALL_INFERIORS with all_non_exited_inferiors and use
	all_non_exited_threads instead of ALL_NON_EXITED_THREADS.
	(remote_target::open_1): Don't call init_thread_list here.
	(remote_target::append_pending_thread_resumptions)
	(remote_target::remote_resume_with_hc): Use all_non_exited_threads
	instead of ALL_NON_EXITED_THREADS.
	(remote_target::commit_resume)
	(remote_target::remove_new_fork_children): Replace ALL_INFERIORS
	with all_non_exited_inferiors and use all_non_exited_threads
	instead of ALL_NON_EXITED_THREADS.
	(remote_target::kill_new_fork_children): Use
	all_non_exited_threads instead of ALL_NON_EXITED_THREADS.  Remove
	init_thread_list and init_wait_for_inferior calls.
	(remote_target::remote_btrace_maybe_reopen)
	(remote_target::thread_handle_to_thread_info): Use
	all_non_exited_threads instead of ALL_NON_EXITED_THREADS.
	* target.c (target_terminal::restore_inferior)
	(target_terminal_is_ours_kind): Replace ALL_INFERIORS with
	all_non_exited_inferiors.
	* thread-iter.c: New file.
	* thread-iter.h: New file.
	* thread.c: Include "inline-frame.h".
	(thread_list): Delete.
	(clear_thread_inferior_resources): Call clear_inline_frame_state.
	(init_thread_list): Use all_threads_safe instead of
	ALL_THREADS_SAFE.  Adjust to per-inferior thread lists.
	(new_thread): Adjust to per-inferior thread lists.
	(add_thread_silent): Pass inferior to find_thread_ptid.
	(thread_info::deletable): New, moved from the header.
	(delete_thread_1): Adjust to per-inferior thread lists.
	(find_thread_global_id): Use inf->threads().
	(find_thread_ptid): Use find_inferior_ptid and pass inferior to
	find_thread_ptid.
	(find_thread_ptid(inferior*, ptid_t)): New overload.
	(iterate_over_threads): Use all_threads_safe.
	(any_thread_p): New.
	(thread_count): Use all_threads and std::distance.
	(live_threads_count): Use all_non_exited_threads and
	std::distance.
	(valid_global_thread_id): Use all_threads.
	(in_thread_list): Use find_thread_ptid.
	(first_thread_of_inferior): Adjust to per-inferior thread lists.
	(any_thread_of_inferior, any_live_thread_of_inferior): Use
	inf->non_exited_threads().
	(prune_threads, delete_exited_threads): Use all_threads_safe.
	(thread_change_ptid): Pass inferior pointer to find_thread_ptid.
	(set_resumed, set_running): Use all_non_exited_threads.
	(is_thread_state, is_stopped, is_exited, is_running)
	(is_executing): Delete.
	(set_executing, set_stop_requested, finish_thread_state): Use
	all_non_exited_threads.
	(print_thread_info_1): Use all_inferiors and all_threads.
	(thread_apply_all_command): Use all_non_exited_threads.
	(thread_find_command): Use all_threads.
	(update_threads_executing): Use all_non_exited_threads.
	* tid-parse.c (parse_thread_id): Use inf->threads.
	* x86-bsd-nat.c (x86bsd_dr_set): Use inf->non_exited_threads ().


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid find_thread_ptid with null_ptid
@ 2018-11-22 16:44 sergiodj+buildbot
  2018-11-22 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-22 16:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 151bb4a5059e73934f7bc61318efaaffe0c91b81 ***

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

Avoid find_thread_ptid with null_ptid

With a following patch, find_thread_ptid will first find the inferior
for the passed-in ptid, using find_inferior_pid, and then look for the
thread in that inferior's thread list.  If we pass down null_ptid to
find_thread_ptid then that means we'll end up passing 0 to
find_inferior_pid, which hits this assertion:

>   struct inferior *
>   find_inferior_pid (int pid)
>   {
>     struct inferior *inf;
>
>     /* Looking for inferior pid == 0 is always wrong, and indicative of
>	a bug somewhere else.  There may be more than one with pid == 0,
>	for instance.  */
>     gdb_assert (pid != 0);

This patch prepares for the change, by avoiding passing down null_ptid
to find_thread_ptid or to functions that naturally use it, such as the
target_pid_to_str call in inferior.c:add_inferior.  In that latter
case, the patch changes GDB output,

from:
 (gdb) add-inferior
 [New inferior 2 (process 0)]

to:
 (gdb) add-inferior
 [New inferior 2]

which seems like a good change to me.  It might not even make sense to
talk about "process" for the current target, for example.

The python_on_normal_stop change ends up avoiding looking up the
same thread twice (inferior_thread also does a look up).

gdb/ChangeLog:
2018-11-22  Pedro Alves  <palves@redhat.com>

	* cli/cli-interp.c (cli_on_user_selected_context_changed): Use
	inferior_thread instead of find_thread_ptid, and only when
	inferior_ptid is not null_ptid.
	* inferior.c (add_inferior): Don't include target_pid_to_str
	output when the inferior is not started.
	* python/py-inferior.c (python_on_normal_stop): Don't use
	find_thread_ptid.
	(tui_on_user_selected_context_changed): Use inferior_thread
	instead of find_thread_ptid, and only when inferior_ptid is not
	null_ptid.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z opcodes: Fix bug disassembling certain shift instructions.
@ 2018-11-21 21:16 sergiodj+buildbot
  2018-11-22  2:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27f42a4ddb28514fde3d01083120674fc8c0c107 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 27f42a4ddb28514fde3d01083120674fc8c0c107

S12Z opcodes: Fix bug disassembling certain shift instructions.

Shift and rotate instructions when the number of bit positions
was an immediate value greater than 1 were incorrectly disassembled.
This change fixes that problem and extends the test to check for
it.

gas/ChangeLog:

  testsuite/gas/s12z/shift.s: Add new test case.
  testsuite/gas/s12z/shift.d: Add expected result.

opcodes/ChangeLog:

  s12z-dis.c (print_insn_shift) [SB_REG_REG_N]: Enter special case
  if the postbyte matches the appropriate pattern.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make command-repeat work after gdb.execute
@ 2018-11-21 17:41 sergiodj+buildbot
  2018-11-22  0:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 17:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c97054b87495b008c6028d697deff61c9fb0b6e ***

Author: Benno Fnfstck <benno.fuenfstueck@gmail.com>
Branch: master
Commit: 1c97054b87495b008c6028d697deff61c9fb0b6e

Make command-repeat work after gdb.execute

Since commit

  56bcdbea2bed ("Let gdb.execute handle multi-line commands")

command repetition after using the `gdb.execute` Python function
fails (the previous command is not repeated anymore). This happens
because read_command_lines_1 sets dont_repeat, but the call to
prevent_dont_repeat in execute_gdb_command is later.

The fix is to move the call to prevent_dont_repeat to the beginning of
the function.

Tested on my laptop (ArchLinux-x86_64).

gdb/ChangeLog:

	PR python/23714
	* gdb/python/python.c (execute_gdb_command): Call
	prevent_dont_repeat earlier to avoid affecting dont_repeat.

gdb/testuite/ChangeLog:

	PR python/23714
	* gdb.python/python.exp: Test command repetition after
	gdb.execute.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] C++ify badness_vector, fix leaks
@ 2018-11-21 17:24 sergiodj+buildbot
  2018-11-21 17:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 17:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82ceee50146563a61ed19f4ad585d39636a6dfa8 ***

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

C++ify badness_vector, fix leaks

badness_vector is currently an open coded vector.  This reimplements
it as a std::vector.

This fixes a few leaks as well:

 - find_oload_champ is leaking every badness vector calculated bar the
   one returned.

 - bv->rank is always leaked, since callers of rank_function only
   xfree the badness_vector pointer, not bv->rank.

gdb/ChangeLog:
2018-11-21  Pedro Alves  <palves@redhat.com>

	* gdbtypes.c (compare_badness): Change type of parameters to const
	reference.  Adjust to badness_vector being a std::vector now.
	(rank_function): Adjust to badness_vector being a std::vector now.
	* gdbtypes.h (badness_vector): Now a typedef to std::vector.
	(LENGTH_MATCH): Delete.
	(compare_badness): Change type of parameters to const reference.
	(rank_function): Return a badness_vector by value now.
	(find_overload_match): Adjust to badness_vector being a
	std::vector now.  Remove cleanups.
	(find_oload_champ_namespace): 'oload_champ_bv' parameter now a
	badness_vector pointer.
	(find_oload_champ_namespace_loop): 'oload_champ_bv' parameter now
	a badness_vector pointer.  Adjust to badness_vector being a
	std::vector now.  Remove cleanups.
	(find_oload_champ): 'oload_champ_bv' parameter now
	a badness_vector pointer.  Adjust to badness_vector being a
	std::vector now.  Remove cleanups.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix linking MSP430 files created by gcc's LTO optimizer.
@ 2018-11-21 17:05 sergiodj+buildbot
  2018-11-21 23:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca94519e70c39fca1d6ea93b8604349111522a8b ***

Author: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Branch: master
Commit: ca94519e70c39fca1d6ea93b8604349111522a8b

Fix linking MSP430 files created by gcc's LTO optimizer.

When invoking GCC with "-g -flto", the compiler will create LTO objects
with debug information. The objects created are "simple ELF" objects (see
libiberty/simple-object-elf.c) and do not have target-specific sections.

When the MSP430 linker sees one of these objects without a .MSP430.attributes
section it errors:

> error: /tmp/cc4LhbEI.ltrans0.ltrans.o uses MSP430X instructions but /tmp/ccynqIwudebugobj uses unknown
> error: /tmp/cc4LhbEI.ltrans0.ltrans.o uses the small code model whereas /tmp/ccynqIwudebugobj uses the unknown code model
> error: /tmp/cc4LhbEI.ltrans0.ltrans.o uses the small data model whereas /tmp/ccynqIwudebugobj uses the unknown data model
> error: /tmp/cc4LhbEI.ltrans0.ltrans.o uses the small code model but /tmp/ccynqIwudebugobj uses the unknown data model
> failed to merge target specific data of file /tmp/cc4LhbEI.ltrans0.ltrans.o

The following patch allows these debug LTO objects to be linked with other
MSP430 objects even if they do not have a .MSP430.attributes section.

bfd	* elf32-msp430.c (elf32_msp430_merge_mspabi_attributes): Do not
	error when .MSP430.attributes section is missing from objects
	created by LTO.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Add target description support
@ 2018-11-21 14:40 sergiodj+buildbot
  2018-11-21 22:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 14:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5ffee3181d157a4d964f62344ac827142e37bde ***

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

gdb/riscv: Add target description support

This commit adds target description support for riscv.

I've used the split feature approach for specifying the architectural
features, and the CSR feature is auto-generated from the riscv-opc.h
header file.

If the target doesn't provide a suitable target description then GDB
will build one by looking at the bfd headers.

This commit does not implement target description creation for the
Linux or FreeBSD native targets, both of these will need to add
read_description methods into their respective target classes, which
probe the target features, and then call
riscv_create_target_description to build a suitable target
description.  Until this is done Linux and FreeBSD will get the same
default target description based on the bfd that bare-metal targets
get.

I've only added feature descriptions for 32 and 64 bit registers, 128
bit registers (for RISC-V) are not supported in the reset of GDB yet.

This commit removes the special reading of the MISA register in order
to establish the target features, this was only used for figuring out
the f-register size, and even that wasn't done consistently.  We now
rely on the target to tell us what size of registers it has (or look
in the BFD as a last resort).  The result of this is that we should
now support RV64 targets with 32-bit float, though I have not
extensively tested this combination yet.

	* Makefile.in (ALL_TARGET_OBS): Add arch/riscv.o.
	(HFILES_NO_SRCDIR): Add arch/riscv.h.
	* arch/riscv.c: New file.
	* arch/riscv.h: New file.
	* configure.tgt: Add cpu_obs list of riscv, move riscv-tdep.o into
	this list, and add arch/riscv.o.
	* features/Makefile: Add riscv features.
	* features/riscv/32bit-cpu.c: New file.
	* features/riscv/32bit-cpu.xml: New file.
	* features/riscv/32bit-csr.c: New file.
	* features/riscv/32bit-csr.xml: New file.
	* features/riscv/32bit-fpu.c: New file.
	* features/riscv/32bit-fpu.xml: New file.
	* features/riscv/64bit-cpu.c: New file.
	* features/riscv/64bit-cpu.xml: New file.
	* features/riscv/64bit-csr.c: New file.
	* features/riscv/64bit-csr.xml: New file.
	* features/riscv/64bit-fpu.c: New file.
	* features/riscv/64bit-fpu.xml: New file.
	* features/riscv/rebuild-csr-xml.sh: New file.
	* riscv-tdep.c: Add 'arch/riscv.h' include.
	(riscv_gdb_reg_names): Delete.
	(csr_reggroup): New global.
	(struct riscv_register_alias): Delete.
	(struct riscv_register_feature): New structure.
	(riscv_register_aliases): Delete.
	(riscv_xreg_feature): New global.
	(riscv_freg_feature): New global.
	(riscv_virtual_feature): New global.
	(riscv_csr_feature): New global.
	(riscv_create_csr_aliases): New function.
	(riscv_read_misa_reg): Delete.
	(riscv_has_feature): Delete.
	(riscv_isa_xlen): Simplify, just return cached xlen.
	(riscv_isa_flen): Simplify, just return cached flen.
	(riscv_has_fp_abi): Update for changes in struct gdbarch_tdep.
	(riscv_register_name): Update to make use of tdesc_register_name.
	Look up xreg and freg names in the new globals riscv_xreg_feature
	and riscv_freg_feature.  Don't supply csr aliases here.
	(riscv_fpreg_q_type): Delete.
	(riscv_register_type): Use tdesc_register_type in almost all
	cases, override the returned type in a few specific cases only.
	(riscv_print_one_register_info): Handle errors reading registers.
	(riscv_register_reggroup_p): Use tdesc_register_in_reggroup_p for
	registers that are otherwise unknown to GDB.  Also check the
	csr_reggroup.
	(riscv_print_registers_info): Remove assert about upper register
	number, and use gdbarch_register_reggroup_p instead of
	short-cutting.
	(riscv_find_default_target_description): New function.
	(riscv_check_tdesc_feature): New function.
	(riscv_add_reggroups): New function.
	(riscv_setup_register_aliases): New function.
	(riscv_init_reggroups): New function.
	(_initialize_riscv_tdep): Add calls to setup CSR aliases, and
	setup register groups.  Register new riscv debug variable.
	* riscv-tdep.h: Add 'arch/riscv.h' include.
	(struct gdbarch_tdep): Remove abi union, and add
	riscv_gdbarch_features field.  Remove cached quad floating point
	type, and provide initialisation for double type field.
	* target-descriptions.c (maint_print_c_tdesc_cmd): Add riscv to
	the list of targets using the feature based target descriptions.
	* NEWS: Mention target description support.

gdb/doc/ChangeLog:

	* gdb.texinfo (Standard Target Features): Add RISC-V Features
	sub-section.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] valops.c: Overload resolution code: Rename parameters/locals
@ 2018-11-21 14:05 sergiodj+buildbot
  2018-11-21 20:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 14:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38139a9681a32e92f5c5b8437875d2726c009841 ***

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

valops.c: Overload resolution code: Rename parameters/locals

While looking over this code, I thought the names of the parameters to
find_oload_champ and related functions and locals were a bit too
cryptic.  For example, FN_LIST holds methods, not free functions.
Free-functions are in OLOAD_SYMS.

This patch renames parameters/variables to the more obvious
methods/xmethods/functions instead.

gdb/ChangeLog:
2018-11-21  Pedro Alves  <palves@redhat.com>

	* valops.c (find_method_list, value_find_oload_method_list)
	(find_overload_match, find_oload_champ): Rename parameters and
	locals.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] valops.c: Some more gdb::array_view
@ 2018-11-21 13:51 sergiodj+buildbot
  2018-11-21 20:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 13:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 85cca2bcbc7833b33d4b61d7b7e0e75b9afa063b ***

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

valops.c: Some more gdb::array_view

This commit replaces some more use of pointer+length pairs in the
overload resolution code with gdb::array_view.

find_oload_champ's interface is simplified/normalized: the xmethods
parameter is converted from std::vector to array pointer, and then the
num_fns parameter is always passed in, no matter the array which is
non-NULL.  I tweaked the formatting of callers a little bit here and
there so that the 3 optional parameters are all in the same line.  (I
tried making the 3 optional array parameters be array_views, but the
resulting code didn't look as nice.)

gdb/ChangeLog:
2018-11-21  Pedro Alves  <palves@redhat.com>

	* valops.c (find_method_list): Replace pointer and length
	parameters with an gdb::array_view.  Adjust.
	(value_find_oload_method_list): Likewise.
	(find_overload_match): Use gdb::array_view for methods list.
	Adjust to find_oload_champ interface change.
	(find_oload_champ): 'xm_worker_vec' parameter now a pointer/array.
	'num_fns' parameter now a size_t.  Eliminate 'fn_count' local.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Eliminate make_symbol_overload_list-related globals & cleanup
@ 2018-11-21 13:48 sergiodj+buildbot
  2018-11-21 16:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0891c3cc132495ad7b323896efae4f91eca87c6c ***

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

Eliminate make_symbol_overload_list-related globals & cleanup

This gets rid of a few globals and a cleanup.

make_symbol_overload_list & friends currently maintain a global
open-coded vector.  Reimplement that with a std::vector, trickled down
through the functions.  Rename a few functions from "make_" to "add_"
for clarity.

gdb/ChangeLog:
2018-11-21  Pedro Alves  <palves@redhat.com>

	* cp-support.c (sym_return_val_size, sym_return_val_index)
	(sym_return_val): Delete.
	(overload_list_add_symbol): Add std::vector parameter.  Adjust to
	add to the vector.
	(make_symbol_overload_list): Adjust to return a std::vector
	instead of maintaining a global open coded vector.
	(make_symbol_overload_list_block): Add std::vector parameter.
	(make_symbol_overload_list_block): Rename to ...
	(add_symbol_overload_list_block): ... this and add std::vector
	parameter.
	(make_symbol_overload_list_namespace): Rename to ...
	(add_symbol_overload_list_namespace): ... this and add std::vector
	parameter.
	(make_symbol_overload_list_adl_namespace): Rename to ...
	(add_symbol_overload_list_adl_namespace): ... this and add
	std::vector parameter.
	(make_symbol_overload_list_adl): Delete.
	(add_symbol_overload_list_adl): New.
	(make_symbol_overload_list_using): Rename to ...
	(add_symbol_overload_list_using): ... this and add std::vector
	parameter.
	(make_symbol_overload_list_qualified): Rename to ...
	(add_symbol_overload_list_qualified): ... this and add std::vector
	parameter.
	* cp-support.h: Include "common/array-view.h" and <vector>.
	(make_symbol_overload_list): Change return type to std::vector.
	(make_symbol_overload_list_adl): Delete declaration.
	(add_symbol_overload_list_adl): New declaration.
	* valops.c (find_overload_match): Local 'oload_syms' now a
	std::vector.
	(find_oload_champ_namespace): 'oload_syms' parameter now a
	std::vector pointer.
	(find_oload_champ_namespace_loop): 'oload_syms' parameter now a
	std::vector pointer.  Adjust to new make_symbol_overload_list
	interface.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use gdb:array_view in call_function_by_hand & friends
@ 2018-11-21 13:16 sergiodj+buildbot
  2018-11-21 14:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21 13:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e71585ffe2e1394858f0fcf809e86f1b324fe4e6 ***

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

Use gdb:array_view in call_function_by_hand & friends

This replaces a few uses of pointer+length with gdb::array_view, in
call_function_by_hand and related code.

Unfortunately, due to -Wnarrowing, there are places where we can't
brace-initialize an gdb::array_view without an ugly-ish cast.  To
avoid the cast, this patch introduces a gdb::make_array_view function.
Unit tests included.

This patch in isolation may not look so interesting, due to
gdb::make_array_view uses, but I think it's still worth it.  Some of
the gdb::make_array_view calls disappear down the series, and others
could be eliminated with more (non-trivial) gdb::array_view
detangling/conversion (e.g. code around eval_call).  See this as a "we
have to start somewhere" patch.

gdb/ChangeLog:
2018-11-21  Pedro Alves  <palves@redhat.com>

	* ada-lang.c (ada_evaluate_subexp): Adjust to pass an array_view.
	* common/array-view.h (make_array_view): New.
	* compile/compile-object-run.c (compile_object_run): Adjust to
	pass an array_view.
	* elfread.c (elf_gnu_ifunc_resolve_addr): Adjust.
	* eval.c (eval_call): Adjust to pass an array_view.
	(evaluate_subexp_standard): Adjust to pass an array_view.
	* gcore.c (call_target_sbrk): Adjust to pass an array_view.
	* guile/scm-value.c (gdbscm_value_call): Likewise.
	* infcall.c (push_dummy_code): Replace pointer + size parameters
	with an array_view parameter.
	(call_function_by_hand, call_function_by_hand_dummy): Likewise and
	adjust.
	* infcall.h: Include "common/array-view.h".
	(call_function_by_hand, call_function_by_hand_dummy): Replace
	pointer + size parameters with an array_view parameter.
	* linux-fork.c (inferior_call_waitpid): Adjust to use array_view.
	* linux-tdep.c (linux_infcall_mmap): Likewise.
	* objc-lang.c (lookup_objc_class, lookup_child_selector)
	(value_nsstring, print_object_command): Likewise.
	* python/py-value.c (valpy_call): Likewise.
	* rust-lang.c (rust_evaluate_funcall): Likewise.
	* spu-tdep.c (flush_ea_cache): Likewise.
	* valarith.c (value_x_binop, value_x_unop): Likewise.
	* valops.c (value_allocate_space_in_inferior): Likewise.
	* unittests/array-view-selftests.c (run_tests): Add
	gdb::make_array_view test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Use string_printf to format int fields instead of a fixed size buffer
@ 2018-11-21  7:58 sergiodj+buildbot
  2018-11-21  7:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21  7:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d63095c426f704f75d943a7481189628403ed58f ***

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

gdb: Use string_printf to format int fields instead of a fixed size buffer

This patch removes a FIXME comment from cli-out.c, now instead of
formatting integers into a fixed size buffer we build a std::string
and extract the formatted integer from that.

The old code using a fixed size buffer was probably fine (the integer
was not going to overflow it) and probably slightly more efficient
(avoids building a std::string) however, given we already have utility
code in GDB that will allow the 'FIXME' comment to be removed, it
seems like an easy improvement.

gdb/ChangeLog:

	* cli-out.c (cli_ui_out::do_field_int): Use string_printf rather
	than a fixed size buffer.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Respect field width and alignment for 'fmt' fields in CLI output
@ 2018-11-21  6:21 sergiodj+buildbot
  2018-11-21  6:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-21  6:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1871a62daf0561da0880ba1ad39e8191bc3cf1ac ***

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

gdb: Respect field width and alignment for 'fmt' fields in CLI output

Currently the method 'cli_ui_out::do_field_fmt' has this comment:

  /* This is the only field function that does not align.  */

The reality is even slightly worse, the 'fmt' field type doesn't
respect either the field alignment or the field width.  In at least
one place in GDB we attempt to work around this lack of respect for
field width by adding additional padding manually.  But, as is often
the case, this is leading to knock on problems.

Conside the output for 'info breakpoints' when a breakpoint has
multiple locations.  This example is taken from the testsuite, from
test gdb.opt/inline-break.exp:

  (gdb) info breakpoints
  Num     Type           Disp Enb Address            What
  1       breakpoint     keep y   <MULTIPLE>
  1.1                     y     0x00000000004004ae in func4b at /src/gdb/testsuite/gdb.opt/inline-break.c:64
  1.2                     y     0x0000000000400682 in func4b at /src/gdb/testsuite/gdb.opt/inline-break.c:64

The miss-alignment of the fields shown here is exactly as GDB
currently produces.

With this patch 'fmt' style fields are now first written into a
temporary buffer, and then written out as a 'string' field.  The
result is that the field width, and alignment should now be respected.
With this patch in place the output from GDB now looks like this:

  (gdb) info breakpoints
  Num     Type           Disp Enb Address            What
  1       breakpoint     keep y   <MULTIPLE>
  1.1                         y   0x00000000004004ae in func4b at /src/gdb/testsuite/gdb.opt/inline-break.c:64
  1.2                         y   0x0000000000400682 in func4b at /src/gdb/testsuite/gdb.opt/inline-break.c:64

This patch has been tested on x86-64/Linux with no regressions,
however, the testsuite doesn't always spot broken output formatting or
alignment.  I have also audited all uses of 'fmt' fields that I could
find, and I don't think there are any other places that specifically
try to work around the lack of width/alignment, however, I could have
missed something.

gdb/ChangeLog:

	* breakpoint.c (print_one_breakpoint_location): Reduce whitespace,
	and remove insertion of extra spaces in GDB's output.
	* cli-out.c (cli_ui_out::do_field_fmt): Update header comment.
	Layout field into a temporary buffer, and then output it as a
	string field.

gdb/testsuite/ChangeLog:

	* gdb.opt/inline-break.exp: Add test that info breakpoint output
	is correctly aligned.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add a test to verify info [functions|variables|types]|rbreak respect language_mode.
@ 2018-11-20 23:25 sergiodj+buildbot
  2018-11-21  4:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-20 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb5e1ed910730334c713c0834d3d66503511ef92 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: fb5e1ed910730334c713c0834d3d66503511ef92

Add a test to verify info [functions|variables|types]|rbreak respect language_mode.

2018-11-20  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.ada/info_auto_lang.exp: New testcase.
	* gdb.ada/info_auto_lang/global_pack.ads: New file.
	* gdb.ada/info_auto_lang/proc_in_ada.adb: New file.
	* gdb.ada/info_auto_lang/some_c.c: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix regression 'info variables' does not show minimal symbols.
@ 2018-11-20 22:22 sergiodj+buildbot
  2018-11-20 22:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-20 22:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8462bbf0bb1c2ef55c87d32bfde6d0a962de87c ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: a8462bbf0bb1c2ef55c87d32bfde6d0a962de87c

Fix regression 'info variables' does not show minimal symbols.

12615cba8411c8 Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables]
introduced a regression that minimal symbols were not listed anymore, due to a wrong
condition checking the absence of a type regexp in the loop scanning the minimal symbols.

Instead, before entering the loop scanning the minimal symbols, check that we
do not have a type regexp, as we will never match a minimal symbol with
this type regexp.

With the fix in this patch, for this part of the code, we basically go back
to the GDB 8.2 logic, with just the addition of
  && !treg.has_value ())
to 'enter' in the minsym case.
This should ensure that at least there is no regression compared to 8.2,
when not using the new type matching argument, as there was no treg in 8.2.

2018-11-20  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* symtab.c (search_symbols): Properly check absence of type regexp
	before entering the loop scanning the minimal symbols.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Test case for 'info variables|functions' with minimal symbols.
@ 2018-11-20 21:54 sergiodj+buildbot
  2018-11-21  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-20 21:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT beddd67132d5f8240613fd89b21ae0d2a1c7bd0f ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: beddd67132d5f8240613fd89b21ae0d2a1c7bd0f

Test case for 'info variables|functions' with minimal symbols.

2018-11-20  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/info_minsym.c: New file.
	* gdb.base/info_minsym.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB: S12Z: new function s12z_extract_return_value
@ 2018-11-20 18:31 sergiodj+buildbot
  2018-11-20 19:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-20 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c3247a98cd2bf9dfcf733e6968273cce90850807 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: c3247a98cd2bf9dfcf733e6968273cce90850807

GDB: S12Z: new function s12z_extract_return_value

Make gdb aware of the return values of functions which
return in registers.

gdb/ChangeLog:
* s12z-tdep.c (s12z_extract_return_value): New function.
  (inv_reg_perm) New array.
  (s12z_return_value): Populate readbuf if non-null.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB: S12Z: Add assertion
@ 2018-11-20  8:31 sergiodj+buildbot
  2018-11-20 10:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-20  8:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b5227d1323e6ee2833f9ba44dea36f3c1c49179 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 7b5227d1323e6ee2833f9ba44dea36f3c1c49179

GDB: S12Z: Add assertion

gdb/ChangeLog:

	* s12z-tdep.c (s12z_frame_cache): Add an assertion.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change get_filename_and_charpos to return void
@ 2018-11-19 23:28 sergiodj+buildbot
  2018-11-20  1:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-19 23:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0614ef69be074fcfb2dc4e7b0e3b9c715a9b44ee ***

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

Change get_filename_and_charpos to return void

The return value from get_filename_and_charpos is never used, so this
patch changes it to return void.

gdb/ChangeLog
2018-11-19  Tom Tromey  <tom@tromey.com>

	* source.c (get_filename_and_charpos): Return void.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix inaccuracies in "info skip" help
@ 2018-11-19 22:58 sergiodj+buildbot
  2018-11-20  0:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-19 22:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 261f6f7962e3fab7cad813a8821f00cd0173f88f ***

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

Fix inaccuracies in "info skip" help

"help info skip" uses "skip info" in its examples, which is not the same
(it ends up creating new skips).  Also, the Type column that is referred
to doesn't exist today.

gdb/ChangeLog:

	* skip.c (_initialize_step_skip): Fix "info skip" help.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use std::forward_list for displaced_step_inferior_states
@ 2018-11-19 17:31 sergiodj+buildbot
  2018-11-19 18:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-19 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39a36629f68e9796d950d9204012fe8272e2d0ef ***

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

Use std::forward_list for displaced_step_inferior_states

Use std::forward_list instead of manually implemented list.  This
simplifies a bit the code, especially around removal.

Regtested on the buildbot.  There are some failures as always, but I
think they are unrelated.

gdb/ChangeLog:

	* infrun.c (displaced_step_inferior_states): Change type to
	std::forward_list.
	(get_displaced_stepping_state): Adjust.
	(displaced_step_in_progress_any_inferior): Adjust.
	(add_displaced_stepping_state): Adjust.
	(remove_displaced_stepping_state): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb.base/warning.exp tweaks
@ 2018-11-19 16:20 sergiodj+buildbot
  2018-11-19 18:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-19 16:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6769f2765db0d94eeb8437b41a925e2bd871f514 ***

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

gdb.base/warning.exp tweaks

#1- Check that the warning is emitted.

#2- Avoid overriding INTERNAL_GDBFLAGS, as per documentated in
    gdb/testsuite/README:

 ~~~
 The testsuite does not override a value provided by the user.
 ~~~

We don't actually need to tweak INTERNAL_GDBFLAGS, we just need to
append out -data-directory to GDBFLAGS, because each passed
-data-directory option leads to a call to the warning:

 $ ./gdb -data-directory=foo -data-directory=bar
 Warning: foo: No such file or directory.
 Warning: bar: No such file or directory.
 [...]

gdb/ChangeLog
2018-11-19  Pedro Alves  <palves@redhat.com>

	* gdb.base/warning.exp: Don't override INTERNAL_FLAGS.  Use
	gdb_spawn_with_cmdline_opts instead of gdb_start.  Check that we
	see the expected warning.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix ia64-linux-nat.c
@ 2018-11-18 17:46 sergiodj+buildbot
  2018-11-19 15:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-18 17:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2a6c5da37c0135acdb859ca819870980db69b77 ***

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

Fix ia64-linux-nat.c

PR build/23814 points out that ia64-linux-nat.c will not compile any
more.  This patch fixes the problem.  Thanks to Andreas Schwab for
trying the patch.

gdb/ChangeLog
2018-11-18  Tom Tromey  <tom@tromey.com>

	PR build/23814:
	* target-delegates.c: Rebuild.
	* ia64-linux-nat.c (class ia64_linux_nat_target)
	<have_steppable_watchpoint>: Use override.  Return true, not 1.
	(ia64_linux_nat_target::can_use_hw_breakpoint): Rename.  Remove
	"self" argument.
	(ia64_linux_nat_target::low_new_thread): Rename.
	(class ia64_linux_nat_target) <read_description>: Don't declare.
	* target.h (struct target_ops) <have_steppable_watchpoint>: Return
	bool.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64: Fix segfault when casting dummy calls
@ 2018-11-16 15:13 sergiodj+buildbot
  2018-11-16 18:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-16 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38a72da0f1d968432ae6a2a9697ba55932dc075e ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 38a72da0f1d968432ae6a2a9697ba55932dc075e

Aarch64: Fix segfault when casting dummy calls

The following will segfault on aarch64 if foo is in another object,
was compiled as c++ and has no debug symbols:
(gdb) p (int)foo()

This is because aarch64_push_dummy_call determines the return type
of the function and then does not check for null pointer.

A null pointer for the return type means the call has no debug
information.  For the code to get here, then the call must have
been cast, otherwise we'd error out sooner.  In the case of a
no-debug-info call cast, the return type is the type the user
had cast the call to, but we do not have that information
available here.

However, aarch64_push_dummy_call only requires the return type in
order to calculate lang_struct_return. This information is available
in the return_method enum. The fix is to simply use this instead.

Adds testcase to check calls across objects, with all combinations
of c, c++, debug and no debug.

gdb/ChangeLog:

	PR gdb/22736:
	* aarch64-tdep.c (aarch64_push_dummy_call): Remove
	lang_struct_return code.

gdb/testsuite/ChangeLog:

	PR gdb/22736:
	* gdb.cp/infcall-nodebug-lib.c: New test.
	* gdb.cp/infcall-nodebug-main.c: New test.
	* gdb.cp/infcall-nodebug.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use enum for return method for dummy calls
@ 2018-11-16 14:16 sergiodj+buildbot
  2018-11-16 15:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-16 14:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c5ac5cbb5be91d43bd31ac0068917bdb7ab9b439 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: c5ac5cbb5be91d43bd31ac0068917bdb7ab9b439

Use enum for return method for dummy calls

In call_function_by_hand_dummy, struct_return and hidden_first_param_p
are used to represent a single concept. Replace with an enum.

gdb/ChangeLog:

	* gdbarch.sh (enum function_call_return_method): Add enum.
	* gdbarch.h: Regenerate.
	* infcall.c (call_function_by_hand_dummy): Replace vars with enum.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Handle vector type alignment.
@ 2018-11-15  1:08 sergiodj+buildbot
  2018-11-15  1:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-15  1:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ef2de9e7eb19cf6f56c8378df82cab30ff741fe0 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: ef2de9e7eb19cf6f56c8378df82cab30ff741fe0

RISC-V: Handle vector type alignment.

For riscv64-linux target, first half of fix for
FAIL: gdb.base/gnu_vector.exp: call add_various_floatvecs

GCC gives vectors natural aligment based on total size, not element size,
bounded by the maximum supported type alignment.

	gdb/
	* riscv-tdep.c (BIGGEST_ALIGNMENT): New.
	(riscv_type_alignment) <TYPE_CODE_ARRAY>: If TYPE_VECTOR, return min
	of TYPE_LENGTH and BIGGEST_ALIGNMENT.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Fix unnamed arg alignment in registers.
@ 2018-11-14 23:47 sergiodj+buildbot
  2018-11-15  3:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-14 23:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b2d40cbba8fbf98d6e031c7d8c7e2ac1baae2d9 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 8b2d40cbba8fbf98d6e031c7d8c7e2ac1baae2d9

RISC-V: Fix unnamed arg alignment in registers.

For riscv64-linux target, second half of fix for
FAIL: gdb.base/gnu_vector.exp: call add_various_floatvecs

Unnamed arguments with 2*XLEN alignment are passed in aligned register pairs.

	gdb/
	* riscv-tdep.c (struct riscv_arg_info): New field is_unnamed.
	(riscv_call_arg_scalar_int): If unnamed arg with twice xlen alignment,
	then increment next_regnum if odd.
	(riscv_arg_location): New arg is_unnamed.  Set ainfo->is_unnamed.
	(riscv_push_dummy_call): New local ftype.  Call check_typedef to set
	function type.  Pass new arg to riscv_arg_location based on function
	type.
	(riscv_return_value): Pass new arg to riscv_arg_location.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Give stack slots same align as XLEN.
@ 2018-11-14 23:34 sergiodj+buildbot
  2018-11-15  0:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-14 23:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 174f8ac8d49021137f98884fc22a7d233e2f89b2 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 174f8ac8d49021137f98884fc22a7d233e2f89b2

RISC-V: Give stack slots same align as XLEN.

For riscv64-linux target, fixes
FAIL: gdb.base/gnu_vector.exp: call add_many_charvecs

Ensure that stack slots are always the same alignment as XLEN by rounding
up arg align to xlen.

	gdb/
	* riscv-tdep.c (riscv_call_arg_scalar_int): Use std::min when
	setting len.  New local align, set to max of arg align and xlen,
	and pass to first riscv_assign_stack_location call.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Improve linker error for FP mismatch.
@ 2018-11-14  0:45 sergiodj+buildbot
  2018-11-14  1:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-14  0:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0242af401093907f6f2bf49d90c1e5d1e23b4453 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 0242af401093907f6f2bf49d90c1e5d1e23b4453

RISC-V: Improve linker error for FP mismatch.

	bfd/
	* elfnn-riscv.c (riscv_float_abi_string): New.
	(_bfd_riscv_elf_merge_private_bfd_data): Use it for error message.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] opcodes/nfp: Fix disassembly of crc[] with swapped operands.
@ 2018-11-13 14:26 sergiodj+buildbot
  2018-11-14  0:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-13 14:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97b3f39201efc9029a9a27d65f13674964c51503 ***

Author: Francois H. Theron <francois.theron@netronome.com>
Branch: master
Commit: 97b3f39201efc9029a9a27d65f13674964c51503

opcodes/nfp: Fix disassembly of crc[] with swapped operands.

The decoding of the CRC operation in alu instructions was using bits
from the instruction word directly, instead of srcA which would be
different if the swap bit was set.

Signed-off-by: Francois H. Theron <francois.theron@netronome.com>


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARM] Improve indentation of ARM architecture declarations
@ 2018-11-13 13:15 sergiodj+buildbot
  2018-11-13 14:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-13 13:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 497d849d28d933016ae0ad388c86b08bb16dd504 ***

Author: Thomas Preud'homme <thomas.preudhomme@linaro.org>
Branch: master
Commit: 497d849d28d933016ae0ad388c86b08bb16dd504

[ARM] Improve indentation of ARM architecture declarations

This commit cleans up indentation of ARM architecture declaration,
namely entries of arm_archs and definition of macros ARM_EXT_*,
ARM_AEXT_*, ARM_AEXT2_*, FPU_EXT_*, FPU_ARCH_* and ARM_ARCH_*. It also
gets rid of unused ARM_ARCH_V6M-ONLY and merge AEM_AEXT_V6M_ONLY in
ARM_AEXT_V6M now sole user.

gas/
2018-11-13  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* config/tc-arm.c (arm_archs): Reindent.

include/
2018-11-13  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* opcode/arm.h (ARM_AEXT_V6M_ONLY): Merge into its use in ARM_AEXT_V6M.
	(ARM_ARCH_V6M_ONLY): Remove.
	(ARM_EXT_V1, ARM_EXT_V2, ARM_EXT_V2S, ARM_EXT_V3, ARM_EXT_V3M,
	ARM_EXT_V4, ARM_EXT_V4T, ARM_EXT_V5, ARM_EXT_V5T, ARM_EXT_V5ExP,
	ARM_EXT_V5E, ARM_EXT_V5J, ARM_EXT_V6, ARM_EXT_V6K, ARM_EXT_V8,
	ARM_EXT_V6T2, ARM_EXT_DIV, ARM_EXT_V5E_NOTM, ARM_EXT_V6_NOTM,
	ARM_EXT_V7, ARM_EXT_V7A, ARM_EXT_V7R, ARM_EXT_V7M, ARM_EXT_V6M,
	ARM_EXT_BARRIER, ARM_EXT_THUMB_MSR, ARM_EXT_V6_DSP, ARM_EXT_MP,
	ARM_EXT_SEC, ARM_EXT_OS, ARM_EXT_ADIV, ARM_EXT_VIRT, ARM_EXT2_PAN,
	ARM_EXT2_V8_2A, ARM_EXT2_V8M, ARM_EXT2_ATOMICS, ARM_EXT2_V6T2_V8M,
	ARM_EXT2_FP16_INST, ARM_EXT2_V8M_MAIN, ARM_EXT2_RAS, ARM_EXT2_V8_3A,
	ARM_EXT2_V8A, ARM_EXT2_V8_4A, ARM_EXT2_FP16_FML, ARM_EXT2_V8_5A,
	ARM_EXT2_SB, ARM_EXT2_PREDRES, ARM_CEXT_XSCALE, ARM_CEXT_MAVERICK,
	ARM_CEXT_IWMMXT, ARM_CEXT_IWMMXT2, FPU_ENDIAN_PURE, FPU_ENDIAN_BIG,
	FPU_FPA_EXT_V1, FPU_FPA_EXT_V2, FPU_MAVERICK, FPU_VFP_EXT_V1xD,
	FPU_VFP_EXT_V1, FPU_VFP_EXT_V2, FPU_VFP_EXT_V3xD, FPU_VFP_EXT_V3,
	FPU_NEON_EXT_V1, FPU_VFP_EXT_D32, FPU_VFP_EXT_FP16, FPU_NEON_EXT_FMA,
	FPU_VFP_EXT_FMA, FPU_VFP_EXT_ARMV8, FPU_NEON_EXT_ARMV8,
	FPU_CRYPTO_EXT_ARMV8, CRC_EXT_ARMV8, FPU_VFP_EXT_ARMV8xD,
	FPU_NEON_EXT_RDMA, FPU_NEON_EXT_DOTPROD, ARM_AEXT_V1, ARM_AEXT_V2,
	ARM_AEXT_V2S, ARM_AEXT_V3, ARM_AEXT_V3M, ARM_AEXT_V4xM, ARM_AEXT_V4,
	ARM_AEXT_V4TxM, ARM_AEXT_V4T, ARM_AEXT_V5xM, ARM_AEXT_V5,
	ARM_AEXT_V5TxM, ARM_AEXT_V5T, ARM_AEXT_V5TExP, ARM_AEXT_V5TE,
	ARM_AEXT_V5TEJ, ARM_AEXT_V6, ARM_AEXT_V6K, ARM_AEXT_V6Z, ARM_AEXT_V6KZ,
	ARM_AEXT_V6T2, ARM_AEXT_V6KT2, ARM_AEXT_V6ZT2, ARM_AEXT_V6KZT2,
	ARM_AEXT_V7_ARM, ARM_AEXT_V7A, ARM_AEXT_V7VE, ARM_AEXT_V7R,
	ARM_AEXT_NOTM, ARM_AEXT_V6M_ONLY, ARM_AEXT_V6M, ARM_AEXT_V6SM,
	ARM_AEXT_V7M, ARM_AEXT_V7, ARM_AEXT_V7EM, ARM_AEXT_V8A, ARM_AEXT2_V8A,
	ARM_AEXT2_V8_1A, ARM_AEXT2_V8_2A, ARM_AEXT2_V8_3A, ARM_AEXT2_V8_4A,
	ARM_AEXT2_V8_5A, ARM_AEXT_V8M_BASE, ARM_AEXT_V8M_MAIN,
	ARM_AEXT_V8M_MAIN_DSP, ARM_AEXT2_V8M, ARM_AEXT2_V8M_BASE,
	ARM_AEXT2_V8M_MAIN, ARM_AEXT2_V8M_MAIN_DSP, ARM_AEXT_V8R,
	ARM_AEXT2_V8R, FPU_VFP_V1xD, FPU_VFP_V1, FPU_VFP_V2, FPU_VFP_V3D16,
	FPU_VFP_V3, FPU_VFP_V3xD, FPU_VFP_V4D16, FPU_VFP_V4, FPU_VFP_V4_SP_D16,
	FPU_VFP_V5D16, FPU_VFP_ARMV8, FPU_NEON_ARMV8, FPU_CRYPTO_ARMV8,
	FPU_VFP_HARD, FPU_FPA, FPU_ARCH_VFP, FPU_ARCH_FPE, FPU_ARCH_FPA,
	FPU_ARCH_VFP_V1xD, FPU_ARCH_VFP_V1, FPU_ARCH_VFP_V2,
	FPU_ARCH_VFP_V3D16_FP16, FPU_ARCH_VFP_V3, FPU_ARCH_VFP_V3_FP16,
	FPU_ARCH_VFP_V3xD_FP16, FPU_ARCH_NEON_V1, FPU_ARCH_VFP_V3_PLUS_NEON_V1,
	FPU_ARCH_NEON_FP16, FPU_ARCH_VFP_HARD, FPU_ARCH_VFP_V4,
	FPU_ARCH_VFP_V4D16, FPU_ARCH_VFP_V4_SP_D16, FPU_ARCH_VFP_V5D16,
	FPU_ARCH_VFP_V5_SP_D16, FPU_ARCH_NEON_VFP_V4, FPU_ARCH_VFP_ARMV8,
	FPU_ARCH_NEON_VFP_ARMV8, FPU_ARCH_CRYPTO_NEON_VFP_ARMV8,
	FPU_ARCH_CRYPTO_NEON_VFP_ARMV8_DOTPROD, ARCH_CRC_ARMV8,
	FPU_ARCH_NEON_VFP_ARMV8_1, FPU_ARCH_CRYPTO_NEON_VFP_ARMV8_1,
	FPU_ARCH_DOTPROD_NEON_VFP_ARMV8, ARM_ARCH_V1, ARM_ARCH_V2,
	ARM_ARCH_V2S, ARM_ARCH_V3, ARM_ARCH_V3M, ARM_ARCH_V4xM, ARM_ARCH_V4,
	ARM_ARCH_V4TxM, ARM_ARCH_V4T, ARM_ARCH_V5xM, ARM_ARCH_V5,
	ARM_ARCH_V5TxM, ARM_ARCH_V5T, ARM_ARCH_V5TExP, ARM_ARCH_V5TE,
	ARM_ARCH_V5TEJ, ARM_ARCH_V6, ARM_ARCH_V6K, ARM_ARCH_V6Z, ARM_ARCH_V6KZ,
	ARM_ARCH_V6T2, ARM_ARCH_V6KT2, ARM_ARCH_V6ZT2, ARM_ARCH_V6KZT2,
	ARM_ARCH_V6M, ARM_ARCH_V6SM, ARM_ARCH_V7, ARM_ARCH_V7A, ARM_ARCH_V7VE,
	ARM_ARCH_V7R, ARM_ARCH_V7M, ARM_ARCH_V7EM, ARM_ARCH_V8A,
	ARM_ARCH_V8A_CRC, ARM_ARCH_V8_1A, ARM_ARCH_V8_2A, ARM_ARCH_V8_3A,
	ARM_ARCH_V8_4A, ARM_ARCH_V8_5A, ARM_ARCH_V8M_BASE, ARM_ARCH_V8M_MAIN,
	ARM_ARCH_V8M_MAIN_DSP, ARM_ARCH_V8R): Reindent.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [BINUTILS, AARCH64, 5/8] Add Tag getting instruction in Memory Tagging Extension
@ 2018-11-12 13:38 sergiodj+buildbot
  2018-11-12 21:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-12 13:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6025b546c21b280ef05201b065f07335ee10e2e ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: e6025b546c21b280ef05201b065f07335ee10e2e

[BINUTILS, AARCH64, 5/8] Add Tag getting instruction in Memory Tagging Extension

This patch is part of the patch series to add support for ARMv8.5-A
Memory Tagging Extensions which is an optional extension to
ARMv8.5-A and is enabled using the +memtag command line option.

This patch add support to the Tag Getting instruction from Memory Tagging
Extension.
- LDG <Xt>, [<Xn|SP>, #<simm>]

where
<Xt> : Is the 64-bit destination GPR.
<Xn|SP> : Is the 64-bit first source GPR or Stack pointer.
<simm> : Is the optional signed immediate offset, a multiple of 16
in the range of -4096 and 4080, defaulting to 0.

*** opcodes/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-tbl.h (QL_LDG): New.
	(aarch64_opcode_table): Add ldg.
	* aarch64-asm-2.c: Regenerated.
	* aarch64-dis-2.c: Regenerated.
	* aarch64-opc-2.c: Regenerated.

*** gas/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* testsuite/gas/aarch64/armv8_5-a-memtag.s: Add tests for ldg.
	* testsuite/gas/aarch64/armv8_5-a-memtag.d: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.s: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.l: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [BINUTILS, AARCH64, 4/8] Add Tag setting instructions in Memory Tagging Extension
@ 2018-11-12 13:37 sergiodj+buildbot
  2018-11-12 20:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-12 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb3265b371a141c4ffc97dcf8cc66e090c516dc8 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: fb3265b371a141c4ffc97dcf8cc66e090c516dc8

[BINUTILS, AARCH64, 4/8] Add Tag setting instructions in Memory Tagging Extension

This patch is part of the patch series to add support for ARMv8.5-A
Memory Tagging Extensions which is an optional extension to
ARMv8.5-A and is enabled using the +memtag command line option.

This patch add support to the Tag setting instructions from
MTE which consists of the following instructions:
- STG [<Xn|SP>, #<simm>]
- STG [<Xn|SP>, #<simm>]!
- STG [<Xn|SP>], #<simm>
- STZG [<Xn|SP>, #<simm>]
- STZG [<Xn|SP>, #<simm>]!
- STZG [<Xn|SP>], #<simm>
- ST2G [<Xn|SP>, #<simm>]
- ST2G [<Xn|SP>, #<simm>]!
- ST2G [<Xn|SP>], #<simm>
- STZ2G [<Xn|SP>, #<simm>]
- STZ2G [<Xn|SP>, #<simm>]!
- STZ2G [<Xn|SP>], #<simm>
- STGP <Xt>, <Xt2>, [<Xn|SP>, #<imm>]
- STGP <Xt>, <Xt2>, [<Xn|SP>, #<imm>]!
- STGP <Xt>, <Xt2>, [<Xn|SP>], #<imm>

where
<Xn|SP> : Is the 64-bit GPR or Stack pointer.
<simm> : Is the optional signed immediate offset, a multiple of 16
in the range -4096 to 4080, defaulting to 0.

*** include/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (aarch64_opnd): Add AARCH64_OPND_ADDR_SIMM11
	and AARCH64_OPND_ADDR_SIMM13.
	(aarch64_opnd_qualifier): Add new AARCH64_OPND_QLF_imm_tag.

*** opcodes/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-opc.c (aarch64_opnd_qualifiers): Add new data
	for AARCH64_OPND_QLF_imm_tag.
	(operand_general_constraint_met_p): Add case for
	AARCH64_OPND_ADDR_SIMM11 and AARCH64_OPND_ADDR_SIMM13.
	(aarch64_print_operand): Likewise.
	* aarch64-tbl.h (QL_LDST_AT, QL_STGP): New.
	(aarch64_opcode_table): Add stg, stzg, st2g, stz2g and stgp
	for both offset and pre/post indexed versions.
	(AARCH64_OPERANDS): Define ADDR_SIMM11 and ADDR_SIMM13.
	* aarch64-asm-2.c: Regenerated.
	* aarch64-dis-2.c: Regenerated.
	* aarch64-opc-2.c: Regenerated.

*** gas/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-aarch64.c (parse_operands): Add switch case for
	AARCH64_OPND_ADDR_SIMM11 and AARCH64_OPND_ADDR_SIMM13.
	(fix_insn): Likewise.
	(warn_unpredictable_ldst): Exempt STGP.
	* testsuite/gas/aarch64/armv8_5-a-memtag.s: Add tests for stg, st2g,
	stzg, stz2g and stgp.
	* testsuite/gas/aarch64/armv8_5-a-memtag.d: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.s: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.l: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [BINUTILS, AARCH64, 3/8] Add Pointer Arithmetic instructions in Memory Tagging Extension
@ 2018-11-12 13:37 sergiodj+buildbot
  2018-11-12 17:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-12 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b731bc3b1bd122872a6aff68aafba1eda64a98d1 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: b731bc3b1bd122872a6aff68aafba1eda64a98d1

[BINUTILS, AARCH64, 3/8] Add Pointer Arithmetic instructions in Memory Tagging Extension

This patch is part of the patch series to add support for ARMv8.5-A
Memory Tagging Extensions which is an optional extension to
ARMv8.5-A and is enabled using the +memtag command line option.

This patch add support to the Pointer Arithmetic instructions from
MTE. These are the following instructions added in this patch:
- SUBP <Xd>, <Xn|SP>, <Xm|SP>
- SUBPS <Xd>, <Xn|SP>, <Xm|SP>
- CMPP <Xn|SP>, <Xm|SP>
where CMPP is an alias to SUBPS XZR, <Xn|SP>, <Xm|SP>

where
<Xd> : Is the 64-bit destination GPR.
<Xn|SP> : Is the 64-bit first source GPR or Stack pointer.
<Xm|SP> : Is the 64-bit second source GPR or Stack pointer.

*** opcodes/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-tbl.h (aarch64_opcode_table): Add subp, subps and cmpp.
	* aarch64-asm-2.c: Regenerated.
	* aarch64-dis-2.c: Regenerated.
	* aarch64-opc-2.c: Regenerated.

*** gas/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* testsuite/gas/aarch64/armv8_5-a-memtag.s: Add tests for subp,
	subps and cmpp.
	* testsuite/gas/aarch64/armv8_5-a-memtag.d: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.s: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.l: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [BINUTILS, AARCH64, 2/8] Add Tag generation instructions in Memory Tagging Extension
@ 2018-11-12 13:36 sergiodj+buildbot
  2018-11-12 15:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-12 13:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 193614f2b908c2b55c188cb14c3ef78993ff85b0 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 193614f2b908c2b55c188cb14c3ef78993ff85b0

[BINUTILS, AARCH64, 2/8] Add Tag generation instructions in Memory Tagging Extension

This patch is part of the patch series to add support for ARMv8.5-A
Memory Tagging Extensions which is an optional extension to
ARMv8.5-A and is enabled using the +memtag command line option.

This patch add support to the Tag generation instructions from
MTE. These are the following instructions added in this patch:
- IRG <Xd|SP>, <Xn|SP>{, Xm}
- ADDG <Xd|SP>, <Xn|SP>, #<uimm1>. #<uimm2>
- SUBG <Xd|SP>, <Xn|SP>, #<uimm1>. #<uimm2>
- GMI <Xd>, <Xn|SP>, <Xm>

where
<Xd|SP> : Is the 64-bit destination GPR or Stack pointer.
<Xn|SP> : Is the 64-bit source GPR or Stack pointer.
<uimm6> : Is the unsigned immediate, a multiple of 16
in the range 0 to 1008.
<uimm4> : Is the unsigned immediate, in the range 0 to 15.

*** include/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (aarch64_opnd): Add
	AARCH64_OPND_UIMM4_ADDG and AARCH64_OPND_UIMM10 as new enums.

*** opcodes/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-opc.h (aarch64_field_kind): New FLD_imm4_3.
	(OPD_F_SHIFT_BY_4, operand_need_shift_by_four): New.
	* aarch64-opc.c (fields): Add entry for imm4_3.
	(operand_general_constraint_met_p): Add cases for
	AARCH64_OPND_UIMM4_ADDG and AARCH64_OPND_UIMM10.
	(aarch64_print_operand): Likewise.
	* aarch64-tbl.h (QL_ADDG): New.
	(aarch64_opcode_table): Add addg, subg, irg and gmi.
	(AARCH64_OPERANDS): Define UIMM4_ADDG and UIMM10.
	* aarch64-asm.c (aarch64_ins_imm): Add case for
	operand_need_shift_by_four.
	* aarch64-asm-2.c: Regenerated.
	* aarch64-dis-2.c: Regenerated.
	* aarch64-opc-2.c: Regenerated.

*** gas/ChangeLog ***

2018-11-12  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-aarch64.c (parse_operands): Add switch case for
	AARCH64_OPND_UIMM4_ADDG and AARCH64_OPND_UIMM10.
	* testsuite/gas/aarch64/armv8_5-a-memtag.s: New.
	* testsuite/gas/aarch64/armv8_5-a-memtag.d: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.s: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.l: Likewise.
	* testsuite/gas/aarch64/illegal-memtag.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a VEC from remote.c
@ 2018-11-10  1:05 sergiodj+buildbot
  2018-11-10  3:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-10  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eefce37f62d87a65f63e12e421a3f727b2685e9d ***

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

Remove a VEC from remote.c

This removes the VEC from remote_g_packet_data, replacing it with a
std::vector.  This is a bit odd in that this object is never
destroyed, and is obstack-allocated.  I believe a gdbarch is never
destroyed, so this seemed ok.

Tested by the buildbot.

gdb/ChangeLog
2018-11-09  Tom Tromey  <tom@tromey.com>

	* remote.c (remote_g_packet_guess_s): Remove typedef and DEF_VEC.
	(struct remote_g_packet_data): Derive from allocate_on_obstack.
	<guesses>: Now a std::vector.
	(remote_g_packet_data_init, register_remote_g_packet_guess):
	Update.
	(remote_read_description_p): Update.  Return bool.
	(remote_target::read_description): Update.
	(struct remote_g_packet_guess): Add constructor.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return scoped_fd from open_source_file and find_and_open_source
@ 2018-11-09 23:41 sergiodj+buildbot
  2018-11-10  0:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09 23:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2179fbc36d23f29a83fb3dfcac0fc7d1fb31b8e8 ***

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

Return scoped_fd from open_source_file and find_and_open_source

This changes open_source_file and find_and_open_source to return
scoped_fd, then updates the callers as appropriate, including using
scoped_fd::to_file.

Tested by the buildbot.

gdb/ChangeLog
2018-11-09  Tom Tromey  <tom@tromey.com>

	* common/scoped_fd.h (class scoped_fd): Add move constructor and
	move assignment operator.
	* psymtab.c (psymtab_to_fullname): Update.
	* source.h (open_source_file): Return scoped_fd.
	(find_and_open_source): Likewise.
	* source.c (open_source_file): Return scoped_fd.
	(get_filename_and_charpos): Update.
	(print_source_lines_base): Update.  Use scoped_fd::to_file.
	(forward_search_command): Likewise.
	(reverse_search_command): Likewise.
	(find_and_open_source): Return scoped_fd.
	* tui/tui-source.c (tui_set_source_content): Update.  Use
	gdb_file_up.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix unsigned overflow in minsyms reader.
@ 2018-11-09 20:51 sergiodj+buildbot
  2018-11-09 22:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09 20:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c122c7f9c8260d2cceb1e8f29d69607531f43ba ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 9c122c7f9c8260d2cceb1e8f29d69607531f43ba

Fix unsigned overflow in minsyms reader.

Use a ssize_t helper variable for the number of bytes to shrink the
msymbols obstack rather than relying on unsigned overflow to shrink
the size of the obstack.

gdb/ChangeLog:

	* minsyms.c (minimal_symbol_reader::install): Fix unsigned
	overflow.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix a typo in iconv.m4.
@ 2018-11-09 17:09 sergiodj+buildbot
  2018-11-09 19:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d762de01cc537cec47d3c7bbae0424a33b33b04 ***

Author: Hafiz Abid Qadeer <abidh@codesourcery.com>
Branch: master
Commit: 5d762de01cc537cec47d3c7bbae0424a33b33b04

Fix a typo in iconv.m4.

config/
2018-11-09  Hafiz Abid Qadeer  <abidh@codesourcery.com>

	* iconv.m4 (AM_ICONV_LINK): Don't overwrite CPPFLAGS.
	Append $INCICONV to it.

gdb/
2018-11-09  Hafiz Abid Qadeer  <abidh@codesourcery.com>

	* configure: Regenerate.

binutils/
2018-11-09  Hafiz Abid Qadeer  <abidh@codesourcery.com>

	* configure: Regenerate.

intl/
2018-11-09  Hafiz Abid Qadeer  <abidh@codesourcery.com>

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Correct comment concerning PE timestamp insertion.
@ 2018-11-09 16:53 sergiodj+buildbot
  2018-11-09 18:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09 16:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dfbfec241aa0ec5359906dd9cdf89ff90750d7c5 ***

Author: Bernhard M. Wiedemann <bwiedemann@suse.de>
Branch: master
Commit: dfbfec241aa0ec5359906dd9cdf89ff90750d7c5

Correct comment concerning PE timestamp insertion.

	* peXXigen.c (_bfd_XXi_only_swap_filehdr_out): Correct comment
	concerning timestamp insertion.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fixed warning from previous patch. Added Changelog.
@ 2018-11-09 16:51 sergiodj+buildbot
  2018-11-09 17:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09 16:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20b233dc4872717a845066b0362582ea4f483df7 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 20b233dc4872717a845066b0362582ea4f483df7

Fixed warning from previous patch. Added Changelog.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Fix local got entry list.
@ 2018-11-09 11:50 sergiodj+buildbot
  2018-11-09 13:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09 11:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0f2064107ba373ddcffb30afc55ac08b40c0585e ***

Author: Claudiu Zissulescu <claziss@gmail.com>
Branch: master
Commit: 0f2064107ba373ddcffb30afc55ac08b40c0585e

[ARC] Fix local got entry list.

Fix a memory leak appearing when the local got entry list was constructed.

bfd/
xxxx-xx-xx  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-got.h (arc_get_local_got_ents): Revamp it; use
	elf_local_got_ents to store the local got list.
	(get_got_entry_list_for_symbo): Restructure it.
	* elf32-arc.c (elf_arc_relocate_section): Correct the call to
	get_got_entry_list_for_symbol.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Capitalize "<TAB>" in require_record_target error
@ 2018-11-09  2:36 sergiodj+buildbot
  2018-11-09  2:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09  2:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c710e1157caf7a2c3e4c816c72f88360f3e859c ***

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

Capitalize "<TAB>" in require_record_target error

This changes require_record_target to say "<TAB>" rather than "<tab>".
I think capitalizing here is a bit more GNU-ish, based on Emacs usage
and one other case in gdb.

gdb/ChangeLog
2018-11-08  Tom Tromey  <tom@tromey.com>

	* record.c (require_record_target): Upper-case "<TAB>".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid crash when calling warning too early
@ 2018-11-09  0:05 sergiodj+buildbot
  2018-11-09  1:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-09  0:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 20f0d60db4fb5083779c4c9182bbc692f7d2bac5 ***

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

Avoid crash when calling warning too early

I noticed that if you pass the name of an existing file (not a
directory) as the argument to --data-directory, gdb will crash:

    $ ./gdb -nx  --data-directory  ./gdb
    ../../binutils-gdb/gdb/target.c:590:56: runtime error: member call on null pointer of type 'struct target_ops'

This was later reported as PR gdb/23838.

This happens because warning ends up calling
target_supports_terminal_ours, which calls current_top_target, which
returns nullptr this early.

This fixes the problem by handling this case specially in
target_supports_terminal_ours.  I also changed
target_supports_terminal_ours to return bool.

gdb/ChangeLog
2018-11-08  Tom Tromey  <tom@tromey.com>

	PR gdb/23555:
	PR gdb/23838:
	* target.h (target_supports_terminal_ours): Return bool.
	* target.c (target_supports_terminal_ours): Handle case where
	current_top_target returns nullptr.  Return bool.

gdb/testsuite/ChangeLog
2018-11-08  Tom Tromey  <tom@tromey.com>

	PR gdb/23555:
	PR gdb/23838:
	* gdb.base/warning.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (AArch64) wrong value returned by "finish" for HFA
@ 2018-11-08 16:30 sergiodj+buildbot
  2018-11-08 17:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-08 16:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4718d5c9f9b5c41d88254429c61010c63139130 ***

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

(AArch64) wrong value returned by "finish" for HFA

Consider the gdb.ada/array_return.exp testcase, and in particular,
consider the following code...

   type Small_Float_Vector is array (1 .. 2) of Float;

   function Create_Small_Float_Vector return Small_Float_Vector is
   begin
      return (others => 4.25);
   end Create_Small_Float_Vector;

... which declares a type which is an array with 2 floats in it
(floats are 4 bytes on AArch64), trying to get GDB to print
the return value from that function does not work:

    (gdb) fin
    Run till exit from #0  pck.create_small_float_vector () at /[...]/pck.adb:15
    0x000000000000062c in p () at /[...]/p.adb:11
    11         Vector := Create_Small_Float_Vector;
    Value returned is $1 = (4.25, 0.0)
                                  ^^^
                                  |||

We expected the value shown to be:

    (gdb) fin
    Run till exit from #0  pck.create_small_float_vector () at /[...]/pck.adb:15
    0x000000000000062c in p () at /[...]/p.adb:11
    11         Vector := Create_Small_Float_Vector;
    Value returned is $1 = (4.25, 4.25)

Because the return type is an HFA, it is returned via the first two
SIMD registers. However, what happens is that the current implementation
fails to realize that this is an HFA, and therefore fetches the return
value from the wrong location. And the reason why it fails to realize
this is because it thinks that our array has 8 elements (HFAs have
a maximum of 4). Looking at aapcs_is_vfp_call_or_return_candidate_1,
where this is determined, we can easily see why (looks like a thinko):

        | case TYPE_CODE_ARRAY:
        | [...]
        |         struct type *target_type = TYPE_TARGET_TYPE (type);
        |         int count = aapcs_is_vfp_call_or_return_candidate_1
        |                       (target_type, fundamental_type);
        |
        |         if (count == -1)
        |           return count;
        |
  !! -> |         count *= TYPE_LENGTH (type);
        |           return count;

Here, we first determine the count for one element of our array,
and so we should then be multiplying that count by the number
of elements in our array (2 in our case). But instead, we multiply it
by the total size (8). As a result, we do not classify the return
type as an HFA, and thus pick the wrong location for fetching
the return value.

gdb/ChangeLog:

        * aarch64-tdep.c (aapcs_is_vfp_call_or_return_candidate_1):
        return the correct count for potential HFAs.

Tested on aarch64-linux, fixes:

    array_return.exp: value printed by finish of Create_Small_Float_Vector


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Update test to support targets without FP hardware
@ 2018-11-08 10:32 sergiodj+buildbot
  2018-11-08 12:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-08 10:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd115d615c6558175a56c3d0896b6f1c62864cd1 ***

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

gdb/riscv: Update test to support targets without FP hardware

Update gdb.arch/riscv-reg-aliases.exp test to support targets without
floating point registers.

gdb/testsuite/ChangeLog:

	* gdb.arch/riscv-reg-aliases.exp: Handle targets without floating
	point hardware.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada/tasking) fix array or string index out of range warning
@ 2018-11-08  1:36 sergiodj+buildbot
  2018-11-08  7:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-08  1:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 76136aeda5ca3f23ba2f86fb6a6938b381d37f61 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 76136aeda5ca3f23ba2f86fb6a6938b381d37f61

(Ada/tasking) fix array or string index out of range warning

A recent change in the compiler highlighted a small weakness in
the function reading the contents of the Ada Task Control Block
(ATCB -- the data that allows us to inspect Ada tasks). As a result,
anytime we read it, we started getting some warnings. For instance,
using the gdb.ada/tasks.exp testcase...

        $ gnatmake -g foo.adb
        $ gdb foo
        (gdb) b foo.adb:60
        Breakpoint 1 at 0x403e07: file foo.adb, line 60.
        (gdb) run
        [...]
        Thread 1 "foo" hit Breakpoint 1, foo () at foo.adb:60
        60         for J in Task_List'Range loop  -- STOP_HERE

... we can see that the "info tasks" command produces some warnings,
followed by the correct output.

        (gdb) info tasks
  !! ->  warning: array or string index out of range
  !! ->  warning: array or string index out of range
  !! ->  warning: array or string index out of range
  !! ->  warning: array or string index out of range
           ID       TID P-ID Pri State                  Name
        *   1    654050       48 Runnable               main_task
            2    654ef0    1  48 Accept or Select Term  task_list(1)
            3    658680    1  48 Accept or Select Term  task_list(2)
            4    65be10    1  48 Accept or Select Term  task_list(3)

The problem comes from the fact that read_atcb, the function responsible
for loading the contents of the ATCB, blindly tries to read some data
which is only relevant when a task is waiting for another task on
an entry call. A comment in that code's section gives a hint as to
how the information is meant to be decoded:

      /* Let My_ATCB be the Ada task control block of a task calling the
         entry of another task; then the Task_Id of the called task is
         in My_ATCB.Entry_Calls (My_ATCB.ATC_Nesting_Level).Called_Task.  */

What the comment shows is that, to get the Id of the task being called,
one has to go through the entry calls field, which is an array pointer.
Up to now, we were lucky that, for tasks that are _not_ waiting on an
entry call, its ATCB atc_nesting_level used to be set to 1, and so
we were able to silently read some irrelevant data. But a recent change
now causes this field to be zero instead, and this triggers the warning,
since we are now trying to read outside of the array's range (arrays
in Ada often start at index 1, as is the case here).

We avoid this issue by simply only reading that data when the data
is actually known to be relevant (state == Entry_Caller_Sleep).

This, in turn, allows us to simplify a bit the use of the task_info->state
field, where we no longer need to check task the task has a state equal
to Entry_Caller_Sleep before using this field. Indeed, with this new
approach, we now know that, unless task_info->state == Entry_Caller_Sleep,
the state is now guaranteed to be zero. In other words, we no longer set
task_info->called_task to some random value, forcing to check the task's
state first as a way to verify that the data is not random.

gdb/ChangeLog:

        * ada-lang.c (read_atcb): Only set task_info->called_task if
        task_info->state == Entry_Caller_Sleep.
        (print_ada_task_info): Do not check task_info->state before
        checking task_info->called_task.
        (info_task): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add updated French and Portuguese translations.
@ 2018-11-07 19:25 sergiodj+buildbot
  2018-11-07 20:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0661ae2e5324719f7850e81fc1da9f6505361ae4 ***

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

Add updated French and Portuguese translations.

gas	* po/fr.po: Updated French translation.
bfd	* po/fr.po: Updated French translation.
	* po/pt.po: Updated Portuguese translation.
binutils* po/pt.po: Updated Portuguese translation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for new load commands added by Apple to the MACH-O file format.
@ 2018-11-07 17:23 sergiodj+buildbot
  2018-11-07 18:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07 17:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc7b364aba41819a5d74ae0ac69f050af282d057 ***

Author: Roman Bolshakov <r.bolshakov@yadro.com>
Branch: master
Commit: fc7b364aba41819a5d74ae0ac69f050af282d057

Add support for new load commands added by Apple to the MACH-O file format.

bfd	* mach-o.h: Add new enums for BFD_MACH_O_PLATFORM_MACOS,
	BFD_MACH_O_PLATFORM_IOS, BFD_MACH_O_PLATFORM_TVOS,
	BFD_MACH_O_PLATFORM_WATCHOS, BFD_MACH_O_PLATFORM_BRIDGEOS,
	BFD_MACH_O_TOOL_CLANG, BFD_MACH_O_TOOL_SWIFT, BFD_MACH_O_TOOL_LD.
	(struct bfd_mach_o_note_command): New.
	(struct bfd_mach_o_build_version_tool): New.
	(struct bfd_mach_o_build_version_command): New.
	(bfd_mach_o_read_version_min): Don't split version into
	a few fields. Rename reserved to sdk.
	* mach-o.c (bfd_mach_o_read_version_min): Don't split version into a
	few fields. Rename reserved to sdk.
	(bfd_mach_o_read_command): Handle LC_VERSION_MIN_TVOS, LC_NOTE,
	LC_BUILD_VERSION.
	(bfd_mach_o_read_note): New.
	(bfd_mach_o_read_build_version): New.

	PR 23728
binutils* od-macho.c (printf_version): New.
	(dump_load_command): Use it to print version. Print sdk version. Print
	version info for watchOS and tvOS. Print LC_NOTE, LC_BUILD_VERSION.
	(dump_buld_version): New.
	(bfd_mach_o_platform_name): New
	(bfd_mach_o_tool_name): New

	* mach-o/external.h (mach_o_nversion_min_command_external): Rename
	reserved to sdk.
	(mach_o_note_command_external): New.
	(mach_o_build_version_command_external): New.
	* mach-o/loader.h (BFD_MACH_O_LC_VERSION_MIN_TVOS): Define.
	(BFD_MACH_O_LC_NOTE): Define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Guard against NULL dereference in dwarf2_init_integer_type
@ 2018-11-07 16:23 sergiodj+buildbot
  2018-11-07 16:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35ee2dc2e4de8b1ae73f420d5db3375f92300b70 ***

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

gdb: Guard against NULL dereference in dwarf2_init_integer_type

In this commit:

    commit eb77c9df9f6d2f7aa644a170280fe31ce080f887
    Date:   Thu Oct 18 14:04:27 2018 +0100

        gdb: Handle ICC's unexpected void return type

A potential dereference of a NULL pointer was introduced if a
DW_TAG_base_type is missing a DW_AT_name attribute.

I have taken this opportunity to fix a slight confusion that existed
in the test also added in the above commit, the test had two C
variables, declared like this:

    int var_a = 5;

    void *var_ptr = &var_a;

However, the fake DWARF in the test script declared them like this:

    void var_a = 5;

    void *var_ptr = &var_a;

This wasn't a problem as the test never uses 'var_a' directly, this
only exists so 'var_ptr' can be initialised.  However, it seemed worth
fixing.

I've also added a test for a DW_TAG_base_type with a missing
DW_AT_name, as clearly there's not test currently that covers this
(the original patch tested cleanly).  I can confirm that the new test
causes GDB to crash before this patch, and passes with this patch.

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_init_integer_type): Check for name being
	NULL before dereferencing it.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/void-type.exp: Rename types, and make var_a an 'int'.
	* gdb.dwarf2/missing-type-name.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] rx: Add target rx-*-linux.
@ 2018-11-07 11:08 sergiodj+buildbot
  2018-11-07 11:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07 11:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d3c78e473c2af54c8117808f2459a408f9f6327 ***

Author: Yoshinori Sato <ysato@users.sourceforge.jp>
Branch: master
Commit: 8d3c78e473c2af54c8117808f2459a408f9f6327

rx: Add target rx-*-linux.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb] Fix gdb crash when reading core file
@ 2018-11-07  6:42 sergiodj+buildbot
  2018-11-07  9:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07  6:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31aceee86308321c2ef299e50773d0043e458e7f ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 31aceee86308321c2ef299e50773d0043e458e7f

[gdb] Fix gdb crash when reading core file

Consider the test-case from this patch, compiled with O0.

The executable segfaults, and generates a core dump:
...
$ ./a.out
Segmentation fault (core dumped)
...

When loading the core file, limiting stack size to 4MB, gdb crashes:
...
$ ulimit -s 4096
$ gdb -batch ./a.out core.saved
[New LWP 19379]
Segmentation fault (core dumped)
...

The crash originates here in linux_vsyscall_range_raw, where we call alloca
with phdrs_size == 4194112 (roughly 4MB):
...
      phdrs = (Elf_Internal_Phdr *) alloca (phdrs_size);
...

While for this test-case gdb runs fine with the system default stack limit of
8MB, there are cases reported of 12MB phdrs_size where gdb also crashes with
the system default stack limit.

Fix this by using xmalloc instead of alloca, which prevents the crash provided
the stack limit is at least 112kb.

Build and reg-tested on x86_64-linux.

2018-11-06  Tom de Vries  <tdevries@suse.de>

	* linux-tdep.c (linux_vsyscall_range_raw): Use xmalloc to allocate
	program headers.

	* gdb.base/many-headers.c: New test.
	* gdb.base/many-headers.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Force variables to .data for code_elim.
@ 2018-11-07  5:39 sergiodj+buildbot
  2018-11-07  7:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07  5:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 109be305bb6acf7604f95411f333549f33a673bb ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 109be305bb6acf7604f95411f333549f33a673bb

RISC-V: Force variables to .data for code_elim.

RISC-V puts a global variable in .sdata by default, which causes the
add-symbol-file commands with -s .data to fail as there is no .data section.
This fixes 3 testsuite failures.

	gdb/testsuite/
	* gdb.base/code_elim.exp: For riscv, set additional_flags
	to include -msmall-data-limit=0.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Note that PT_GETREGS supplies SSTATUS for FreeBSD/riscv.
@ 2018-11-07  2:34 sergiodj+buildbot
  2018-11-07  4:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07  2:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bcecc11da243fe5c333f9d2d914663d09f4b868d ***

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

Note that PT_GETREGS supplies SSTATUS for FreeBSD/riscv.

This permits reading the value of the SSTATUS CSR returned by ptrace()
for live FreeBSD/riscv processes.

	* riscv-fbsd-nat.c (getregs_supplies): Return true for
	RISCV_CSR_SSTATUS_REGNUM.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for a couple of new Mach-O commands.
@ 2018-11-07  1:22 sergiodj+buildbot
  2018-11-07  3:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-07  1:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ddea148b3da27eb681504bf341f45abb7a74580b ***

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

Add support for a couple of new Mach-O commands.

	PR 23742
	* mach-o.c (bfd_mach_o_read_command): Accept and ignore
	BFD_MACH_O_LC_LINKER_OPTIONS and BFD_MACH_O_LC_BUILD_VERSION
	commands.

	* mach-o/loader.h: Add BFD_MACH_O_LC_BUILD_VERSION.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [BINUTILS, ARM] Add Armv8.5-A to select_arm_features and update macros.
@ 2018-11-06 23:52 sergiodj+buildbot
  2018-11-07  2:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0632eeea6eb1096fe7ddbd7f81bd74b360d1f511 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 0632eeea6eb1096fe7ddbd7f81bd74b360d1f511

[BINUTILS, ARM] Add Armv8.5-A to select_arm_features and update macros.

This patch addresses the following
1) Adding ARMv8.5-A in select_arm_features.
2) Updating the feature macro so that the new ARM_EXT2_* features for
Armv8.5-A are moved to ARM_AEXT2_V8_5A.

*** opcodes/ChangeLog ***

2018-11-06  Sudakshina Das  <sudi.das@arm.com>

	* arm-dis.c (select_arm_features): Update bfd_mach_arm_8
	with Armv8.5-A. Remove reduntant ARM_EXT2_FP16_FML.

*** include/ChangeLog ***

2018-11-06  Sudakshina Das  <sudi.das@arm.com>

	* opcode/arm.h (ARM_ARCH_V8_5A): Move ARM_EXT2_PREDRES and
	ARM_EXT2_SB to ...
	(ARM_AEXT2_V8_5A): Here.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: correctly handle VPBROADCASTD with EVEX.W set outside of 64-bit mode
@ 2018-11-06 21:18 sergiodj+buildbot
  2018-11-07  0:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 21:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dd4e6394509d58685daea52cc6947c45fd7ee9d ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 4dd4e6394509d58685daea52cc6947c45fd7ee9d

x86: correctly handle VPBROADCASTD with EVEX.W set outside of 64-bit mode

For the flavor having a GPR operand EVEX.W is ignored outside of 64-bit
mode. The mnemonic should therefore not be VPBROADCASTQ.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: correctly handle KMOVD with VEX.W set outside of 64-bit mode
@ 2018-11-06 18:07 sergiodj+buildbot
  2018-11-06 20:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 18:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58a211d2602df0a39779c84a344b1b4d12deb2d0 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 58a211d2602df0a39779c84a344b1b4d12deb2d0

x86: correctly handle KMOVD with VEX.W set outside of 64-bit mode

For the flavors having a GPR operand VEX.W is ignored outside of 64-bit
mode. The mnemonic should therefore not be KMOVQ.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: adjust {,E}VEX.W handling for PEXTR* / PINSR*
@ 2018-11-06 17:28 sergiodj+buildbot
  2018-11-06 18:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b50c9f31661be05bcd73fb1158e02f606e696948 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: b50c9f31661be05bcd73fb1158e02f606e696948

x86: adjust {,E}VEX.W handling for PEXTR* / PINSR*

PEXTR{B,W} and PINSR{B,W}, just like for AVX512BW, are WIG, no matter
that the SDM uses a nonstandard description of that fact.

PEXTRD, even with EVEX.W set, ignores that bit outside of 64-bit mode,
just like its AVX counterpart.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fix various non-LIG templates
@ 2018-11-06 14:45 sergiodj+buildbot
  2018-11-06 15:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd71a3756e2dd1eae116d77dc5ec58391c4840d8 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: fd71a3756e2dd1eae116d77dc5ec58391c4840d8

x86: fix various non-LIG templates

Quite a few templates were marked LIG while really the insns aren't.
Introduce descriptive shorthands once again, instead of continuing to
use the less legible original forms.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: allow {store} to select alternative {, }PEXTRW encoding
@ 2018-11-06 14:03 sergiodj+buildbot
  2018-11-06 14:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 563c7eef61a1835973b857eaa7372ec66fc91d64 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 563c7eef61a1835973b857eaa7372ec66fc91d64

x86: allow {store} to select alternative {,}PEXTRW encoding

The 0F C5 encoding is indeed a load type one (just that memory operands
are not permitted), while the 0F 3A 15 encoding is obviously a store.
Allow the pseudo prefixes to be used to select between them.

Also move (without any change) the secondary AVX512BW templates next to
the primary one.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: add more VexWIG
@ 2018-11-06 12:32 sergiodj+buildbot
  2018-11-06 13:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 12:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0aaca1d90a2f9f075852b2ea5907937cca037044 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 0aaca1d90a2f9f075852b2ea5907937cca037044

x86: add more VexWIG

Commits 6865c0435a ("x86: Support VEX/EVEX WIG encoding") and 6fa52824c3
("x86: Replace VexW=3 with VexWIG") omitted quite a few templates, oddly
enough in some cases despite testcases getting added (which then were
recorded with wrong expected output).

Also adjust VPMAXUB's attributes in the AVX512BW case to match ordering
of that of neighboring templates.

For the moment SSE2AVX templates are left alone, as it isn't clear
whether they were intentionally left untouched by the original commits
(the descriptions don't say either way).

In this context I question the decision in commit 0375113302 ("x86: Add
-mvexwig=[0|1] option to assembler") to move the logic to determine the
value of the W bit ahead of the decision whether to use 2-byte VEX:
While I can see this as one possible interpretation of -mvexwig=, the
other alternative (setting the value of the bit only if it actually
exists in the encoding) looks as reasonable to me, and perhaps even more
in line with us generally trying to pick the shortest encoding.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: XOP VPHADD* / VPHSUB* are VEX.W0
@ 2018-11-06 11:41 sergiodj+buildbot
  2018-11-06 12:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-06 11:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbae6b11eb3a3c4a4c2f589d6c2b30e3c6b97c04 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: bbae6b11eb3a3c4a4c2f589d6c2b30e3c6b97c04

x86: XOP VPHADD* / VPHSUB* are VEX.W0

Also avoid introducing further uses of VexW=1, by introducing and using
VexW0 at this occasion. Move the marker past all #define-s.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return gdbpy_ref from gdbpy_get_varobj_pretty_printer
@ 2018-11-04 18:25 sergiodj+buildbot
  2018-11-04 20:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-04 18:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a31abe80ea4c45b544f3ae04bc63ccaeba530e0f ***

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

Return gdbpy_ref from gdbpy_get_varobj_pretty_printer

This changes gdbpy_get_varobj_pretty_printer to return a gdbpy_ref.

gdb/ChangeLog
2018-11-04  Tom Tromey  <tom@tromey.com>

	* varobj.c (install_default_visualizer): Update.
	* python/python-internal.h (gdbpy_get_varobj_pretty_printer):
	Return gdbpy_ref.
	* python/py-prettyprint.c (search_pp_list): Return gdbpy_ref.
	(find_pretty_printer_from_progspace)
	(find_pretty_printer_from_gdb, find_pretty_printer)
	(gdbpy_get_varobj_pretty_printer): Return gdbpy_ref.
	(gdbpy_get_varobj_pretty_printer, gdbpy_default_visualizer):
	Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return gdbpy_ref from gdb_py_object_from_*longest
@ 2018-11-04 16:10 sergiodj+buildbot
  2018-11-04 16:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-04 16:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12dfa12a3cfd4552c0cc4d7b271ab3e9c439589a ***

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

Return gdbpy_ref from gdb_py_object_from_*longest

This changes gdb_py_object_from_longest and
gdb_py_object_from_ulongest to return a gdbpy_ref rather than a
PyObject*.

gdb/ChangeLog
2018-11-04  Tom Tromey  <tom@tromey.com>

	* python/python-internal.h (gdb_py_object_from_longest)
	(gdb_py_object_from_ulongest): Return gdbpy_ref.
	* python/py-value.c (valpy_int): Update.
	* python/py-utils.c (gdb_py_object_from_longest): Return
	gdbpy_ref.
	(gdb_py_object_from_ulongest): Likewise.
	* python/py-type.c (typy_get_alignof): Update.
	* python/py-linetable.c (ltpy_get_all_source_lines)
	(ltpy_entry_get_line, ltpy_entry_get_pc): Update.
	* python/py-block.c (blpy_get_start, blpy_get_end): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] OBVIOUS Fix a typo in ada-lang.c add_prefix_cmd for "set ada"
@ 2018-11-03 21:38 sergiodj+buildbot
  2018-11-03 21:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-03 21:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 470678d7c92df4c016c6b4d8dadbd5d5e86cb5ff ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 470678d7c92df4c016c6b4d8dadbd5d5e86cb5ff

OBVIOUS Fix a typo in ada-lang.c add_prefix_cmd for "set ada"

Correct typo in add_prefix_cmd doc arg for "set ada".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] OBVIOUS Remove a useless const char *type and its initialization.
@ 2018-11-03 19:46 sergiodj+buildbot
  2018-11-03 21:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-03 19:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 814fa4f632006dace09b131021b949021dfb58bf ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 814fa4f632006dace09b131021b949021dfb58bf

OBVIOUS Remove a useless const char *type and its initialization.

Valgrind detected a leak for the line:
  type = xstrdup ("auto");

as the compile probably dropped the type variable completely, as its
only usage was this initialization.

So, remove the useless variable.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] QUIET flag initialization missing in 2 places.
@ 2018-11-02 14:20 sergiodj+buildbot
  2018-11-02 17:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-02 14:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d54cfd762b060ad167bd8e947e4ea212c0eb9b83 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: d54cfd762b060ad167bd8e947e4ea212c0eb9b83

QUIET flag initialization missing in 2 places.

Fix by Matthew Malcomson  <matthew.malcomson@arm.com>

Pushed as obvious.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23850, strip should not discard/move .rela.plt in executable
@ 2018-11-02  5:31 sergiodj+buildbot
  2018-11-02  6:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-02  5:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4bcd733712abd892aa7fe0d79a3f999b461f119 ***

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

PR23850, strip should not discard/move .rela.plt in executable

strip/objcopy can't deal with alloc reloc sections, not .rela.dyn or
.rela.plt in a dynamic executable, or .rela.plt/.rela.iplt in a static
executable.  So, don't have BFD treat them as side-channel data
associated with the section they are relocating.

	PR 23850
	* elf.c (bfd_section_from_shdr): Treat SHF_ALLOC SHT_REL* sections
	in an executable or shared library as normal sections.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Don't allow unaligned breakpoints.
@ 2018-11-02  0:51 sergiodj+buildbot
  2018-11-02  4:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-02  0:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ba2ee38a648b7f52e77700325b26137f6332fe2 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 3ba2ee38a648b7f52e77700325b26137f6332fe2

RISC-V: Don't allow unaligned breakpoints.

Some hardware doesn't support unaligned accesses, and a bare metal target
may not have an unaligned access trap handler.  So if the PC is 2-byte
aligned, then use a 2-byte breakpoint to avoid unaligned accesses.

Tested on native RV64GC Linux with gdb testsuite and cross on spike
simulator and openocd with riscv-tests/debug.

	gdb/
	* riscv-tdep.c (riscv_breakpoint_kind_from_pc): New local unaligned_p.
	Set if pcptr if unaligned.  Return 2 if unaligned_p true.  Update
	debugging messages.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) fix "error in expression" when using watch -location command
@ 2018-11-01 23:19 sergiodj+buildbot
  2018-11-02  2:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-01 23:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2b7af7242c99e503747a43775d94beda90cb24e ***

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

(Ada) fix "error in expression" when using watch -location command

The "watch -l EXPR" command with the language set to Ada currently
fails with the following error:

     (gdb) watch -l global_var
     Error in expression, near ` 0x000000000062d2d8'.

The error occurs because GDB internally translate the request into
a watchpoint on a different expression: "* (TYPE *) ADDR" where
TYPE and ADDR are the type and the address of the object returned
by the expression's evaluation (resp.). So, in the example above,
global_var being an integer stored at 0x000000000062d2d8, GDB tries
to set a watchpoint on "* (integer *) 0x000000000062d2d8", which
fails, because we try to parse this expression with Ada, when
in fact it is not valid.

This patch fixes the issue by implementing the la_watch_location_expression
language method, using a syntax that the Ada parser recognizes
("{TYPE} ADDR").

gdb/ChangeLog:

	* ada-lang.c (ada_watch_location_expression): New function.
        (ada_language_defn): Set la_watch_location_expression to
        ada_watch_location_expression.

gdb/testsuite/ChangeLog:

        * gdb.ada/watch_minus_l: New testcase.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remove trailing spaces in print-utils.c ("int_string" function)
@ 2018-11-01 23:04 sergiodj+buildbot
  2018-11-02  1:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-01 23:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b578f9c7626f57f5adb9e4a52f5b0d6c8f6e0a0 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 8b578f9c7626f57f5adb9e4a52f5b0d6c8f6e0a0

remove trailing spaces in print-utils.c ("int_string" function)

gdb/ChangeLog:

        * print-utils.c (int_string): Remove unnecessary trailing spaces.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Import mkdtemp gnulib module, fix mingw build
@ 2018-11-01 20:59 sergiodj+buildbot
  2018-11-01 21:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-01 20:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e8d8cce69b34481a27562267d94a1aff19b05518 ***

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

Import mkdtemp gnulib module, fix mingw build

Building with mingw currently fails:

  CXX    unittests/mkdir-recursive-selftests.o
/home/emaisin/src/binutils-gdb/gdb/unittests/mkdir-recursive-selftests.c: In function void selftests::mkdir_recursive::test():
/home/emaisin/src/binutils-gdb/gdb/unittests/mkdir-recursive-selftests.c:49:20: error: mkdtemp was not declared in this scope
   if (mkdtemp (base) == NULL)
                    ^
Commit

    e418a61a67a ("Move mkdir_recursive to common/filestuff.c")

moved this code, but also removed the HAVE_MKDTEMP guard which prevented
the mkdtemp call to be compiled on mingw.

We can either put back the HAVE_MKDTEMP ifdef, or import the gnulib
mkdtemp module, which provides the function for mingw.  Since the
mkdir_recursive is susceptible to be used on mingw at some point, I
think it would be nice to have it tested on mingw, so I did the latter.

Once built, I tested it on Windows (copied the resulting gdb.exe on a
Windows machine, ran it, and ran "maint selftest mkdir_recursive").  It
failed, because the temporary directory is hardcoded to "/tmp/...".  I
therefore added and used a new get_standard_temp_dir function, which
returns an appropriate temporary directory for the host platform.

gdb/ChangeLog:

	* common/pathstuff.c (get_standard_temp_dir): New.
	* common/pathstuff.h (get_standard_temp_dir): New.
	* config.in: Re-generate.
	* configure: Re-generate.
	* configure.ac: Don't check for mkdtemp.
	* gnulib/aclocal-m4-deps.mk: Re-generate.
	* gnulib/aclocal.m4: Re-generate.
	* gnulib/config.in: Re-generate.
	* gnulib/configure: Re-generate.
	* gnulib/import/Makefile.am: Re-generate.
	* gnulib/import/Makefile.in: Re-generate.
	* gnulib/import/m4/gnulib-cache.m4: Re-generate.
	* gnulib/import/m4/gnulib-comp.m4: Re-generate.
	* gnulib/import/m4/mkdtemp.m4: New file.
	* gnulib/import/mkdtemp.c: New file.
	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES):
	Add mkdtemp module.
	* unittests/mkdir-recursive-selftests.c (test): Use
	get_standard_temp_dir.
	(_initialize_mkdir_recursive_selftests): Remove HAVE_MKDTEMP
	ifdef.
	* compile/compile.c (get_compile_file_tempdir): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Reading signal handler frame in AIX
@ 2018-11-01 11:34 sergiodj+buildbot
  2018-11-01 11:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-11-01 11:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cdcda965ea4c70c80b9f8c294597e991417ff9d5 ***

Author: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Branch: master
Commit: cdcda965ea4c70c80b9f8c294597e991417ff9d5

Reading signal handler frame in AIX

In AIX if gdb is debugging an application which has a signal handler
and reaches the signal handler frame, then we need to read the back
chain address from sigcontext saved on the stack, similarly the LR.

As backchain at an offset 0 will be 0, because we will have a
sigconext saved after the minimum stack size. So the correct
backchain will be at an offset after minimum stack and the LR at
an offset 8 will be of the signal millicode address.
If the back chain pointer is NULL and the LR field is in the kernel
segment(ex. 0x00004a14) then we can probably assume we are in a
signal  handler.

sample output

(gdb) bt
0  sig_handle_aix (signo=11) at aix-sighandle.c:7
1  0x0000000000004a94 in ?? ()
(gdb)

expected output

(gdb) bt
0  sig_handle_aix (signo=11) at aix-sighandle.c:7
1  <signal handler called>
2  0x0000000100000748 in foo () at aix-sighandle.c:14
3  0x000000010000079c in main () at aix-sighandle.c:19

gdb/ChangeLog:

2018-11-01  Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>

	* rs6000-aix-tdep.c: Include "trad-frame.h" and "frame-unwind.h".
	(SIG_FRAME_LR_OFFSET64): New define.
	(SIG_FRAME_FP_OFFSET64): New define.
	(aix_sighandle_frame_cache): New Function.
	(aix_sighandle_frame_this_id): New Function.
	(aix_sighandle_frame_prev_register): New Function.
	(aix_sighandle_frame_sniffer): New Function.
	(aix_sighandle_frame_unwind): New global variable.
	(rs6000_aix_init_osabi): Install new frame unwinder.

gdb/testsuite/ChangeLog:

2018-11-01  Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>

	* gdb.arch/aix-sighandle.c: New file.
	* gdb.arch/aix-sighandle.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Fix failures on rv64 in gdb.arch/riscv-reg-aliases.exp test
@ 2018-10-31 19:06 sergiodj+buildbot
  2018-11-01  1:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-31 19:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92dcebf3fa5ccc1cae8fcb93eaf08ffea52957e2 ***

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

gdb/riscv: Fix failures on rv64 in gdb.arch/riscv-reg-aliases.exp test

The gdb.arch/riscv-reg-aliases.exp test didn't take into account that
on RV64 (and RV128) the floating point registers are represented as a
union.  This patch updates the test to handle this.

Tested against RV32 and RV64.

gdb/testsuite/ChangeLog:

	* gdb.arch/riscv-reg-aliases.exp: Rewrite to take account of float
	registers being unions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Factor out lib/valgrind.exp
@ 2018-10-31 18:41 sergiodj+buildbot
  2018-11-01  0:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-31 18:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68b9ac18cf6ae8d76828357982c106d57c695ad4 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 68b9ac18cf6ae8d76828357982c106d57c695ad4

[gdb/testsuite] Factor out lib/valgrind.exp

Factor out common code related to vgdb setup and cleanup in valgrind-bt.exp,
valgrind-disp-step.exp and gdb.base/valgrind-infcall.exp.

Tested on x86_64-linux with and without --target_board=native-gdbserver.

2018-10-31  Tom de Vries  <tdevries@suse.de>

	* lib/valgrind.exp: New file.
	 (vgdb_start, vgdb_stop): New procs, factored out of ...
	* gdb.base/valgrind-bt.exp: ... here, ...
	* gdb.base/valgrind-disp-step.exp: ... here and ...
	* gdb.base/valgrind-infcall.exp: ... here.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] get_valueof: Don't output value in test name
@ 2018-10-31 17:26 sergiodj+buildbot
  2018-10-31 19:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-31 17:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1443936e967d4a0a49acb8756e3f808dc3628318 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 1443936e967d4a0a49acb8756e3f808dc3628318

[gdb/testsuite] get_valueof: Don't output value in test name

The get_valueof outputs the value it has read as part of the test name.  This
causes test names to vary from run to run, and adds some noise when diffing
test results.  e.g.:

-PASS: gdb.guile/scm-ports.exp: buffered: get valueof "$sp" (140737488343920)
+PASS: gdb.guile/scm-ports.exp: buffered: get valueof "$sp" (140737488343968)
-PASS: gdb.guile/scm-ports.exp: unbuffered: get valueof "$sp" (140737488343920)
+PASS: gdb.guile/scm-ports.exp: unbuffered: get valueof "$sp" (140737488343968)

This patch removes that, since it's probably not very useful.

Tested on x86_64-linux.

2018-10-31  Tom de Vries  <tdevries@suse.de>

	* lib/gdb.exp (get_valueof): Don't output read value in test name.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Include nat/linux-ptrace.h in native targets
@ 2018-10-31 16:07 sergiodj+buildbot
  2018-10-31 16:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-31 16:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64f57f3d7d7b8e7bf9f57caa1389ac5ee3ecfec7 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 64f57f3d7d7b8e7bf9f57caa1389ac5ee3ecfec7

[PowerPC] Include nat/linux-ptrace.h in native targets

Patch "[PowerPC] Add support for PPR and DSCR" used
PTRACE_GETREGSET/SETREGSET without including the fallback definitions
from "nat/linux-ptrace.h".  Include this header to avoid breaking
builds in systems that don't define them.

gdb/ChangeLog:
2018-10-31  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* ppc-linux-nat.c: Include nat/linux-ptrace.h.

gdb/gdbserver/ChangeLog:
2018-10-31  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* linux-ppc-low.c: Include nat/linux-ptrace.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Handle ICC's unexpected void return type
@ 2018-10-31 13:54 sergiodj+buildbot
  2018-10-31 14:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-31 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eb77c9df9f6d2f7aa644a170280fe31ce080f887 ***

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

gdb: Handle ICC's unexpected void return type

I encountered a binary compiled with Intel's C Compiler (ICC) version
14.0.5.212, which seemed to contain some non-standard DWARF.

The DWARF spec (V5 3.3.2) says:

    Debugging information entries for C void functions should not have
    an attribute for the return type.

However, what I observed in the DWARF from this ICC compiled binary
was this:

    ...
    <0><857>: Abbrev Number: 1 (DW_TAG_compile_unit)
       <858>   DW_AT_comp_dir    : (indirect string, offset: 0x48d): /tmp/
       <85c>   DW_AT_language    : 1       (ANSI C)
       <85d>   DW_AT_name        : (indirect string, offset: 0x77c): filename.c
       <861>   DW_AT_producer    : (indirect string, offset: 0x520): Intel(R) C Intel(R) 64 Compiler ...
       <865>   DW_AT_low_pc      : 0x4378d0
       <86d>   DW_AT_high_pc     : 0x4378f0
       <875>   DW_AT_stmt_list   : 0xa37
    ...
    <1><7ea>: Abbrev Number: 2 (DW_TAG_base_type)
       <7eb>   DW_AT_byte_size   : 0
       <7ec>   DW_AT_encoding    : 5       (signed)
       <7ed>   DW_AT_name        : (indirect string, offset: 0x58f): void
    ...
    <1><7f1>: Abbrev Number: 3 (DW_TAG_subprogram)
       <7f2>   DW_AT_decl_line   : 268
       <7f4>   DW_AT_decl_column : 30
       <7f5>   DW_AT_decl_file   : 1
       <7f6>   DW_AT_type        : <0x7ea>
       <7fa>   DW_AT_prototyped  : 1
       <7fb>   DW_AT_name        : (indirect string, offset: 0x761): function_foo
       <7ff>   DW_AT_MIPS_linkage_name: (indirect string, offset: 0x761): function_foo
       <803>   DW_AT_low_pc      : 0x4378a0
       <80b>   DW_AT_high_pc     : 0x4378d0
       <813>   DW_AT_external    : 1
    ...

So function 'function_foo' has void return type, but still has a
DW_AT_type attribute for a 0 sized type called void.

What was found was that when the 'finish' command was used to leave
'function_foo', GDB would crash.

The problem is that in infcmd.c:print_return_value GDB tries to filter
out void return types, by looking for the TYPE_CODE_VOID, this fails
for the 'void' type as it has code TYPE_CODE_INT and GDB then tries to
print the 'void' type.

This eventually ends in a call to valprint.c:maybe_negate_by_bytes,
however, the len (length) of the value being negated is 0, which is
not detected or expected by this code, and invalid memory accesses
occur, some of which might cause GDB to crash.

The above DWARF was seen on version 14.0.5.212 of ICC.

I have also tested ICC versions 18.0.2.199 and 17.0.7.259, on both of
these versions, the DW_AT_type on the DW_TAG_subprogram has been
removed, bringing ICC inline with the DWARF standard, and with the
DWARF produced by GCC.

I only have limited access to these specific versions of ICC so I am
unable to get more specific details for when the generated DWARF
became non-standard or when it was changed to be more inline with the
DWARF standard.

Further testing revealed additional places where ICC produced 'void'
related DWARF that GDB struggles with.  When I compiled code that
contained a function with this signature:

    void funcx (void *arg);

on ICC 17/18, I got the following DWARF (notice the void return type
is now gone):

    ...
    <1><32>: Abbrev Number: 2 (DW_TAG_subprogram)
       <33>   DW_AT_decl_line   : 2
       <34>   DW_AT_decl_file   : 1
       <35>   DW_AT_prototyped  : 1
       <36>   DW_AT_name        : (indirect string, offset: 0xc5): funcx
       <3a>   DW_AT_MIPS_linkage_name: (indirect string, offset: 0xc5): funcx
       <3e>   DW_AT_low_pc      : 0x6dc
       <46>   DW_AT_high_pc     : 0x703
       <4e>   DW_AT_external    : 1
    <2><4f>: Abbrev Number: 3 (DW_TAG_formal_parameter)
       <50>   DW_AT_decl_line   : 2
       <51>   DW_AT_decl_file   : 1
       <52>   DW_AT_type        : <0x6a>
       <56>   DW_AT_name        : arg
       <5a>   DW_AT_location    : 2 byte block: 76 70      (DW_OP_breg6 (rbp): -16)
    ...
    <1><6a>: Abbrev Number: 5 (DW_TAG_pointer_type)
       <6b>   DW_AT_type        : <0x6f>
    <1><6f>: Abbrev Number: 6 (DW_TAG_base_type)
       <70>   DW_AT_byte_size   : 0
       <71>   DW_AT_encoding    : 5        (signed)
       <72>   DW_AT_name        : (indirect string, offset: 0xcb): void
    ...

However, the function argument 'arg' does still reference a 'void'
type.  This case doesn't seem as obviously non-standard as the
previous one, but I think that the DWARF standard (V5 5.2) does
suggest that the above is not the recommended approach.  If we compare
to the DWARF generated by GCC 7.3.1:

    ...
    <1><68>: Abbrev Number: 5 (DW_TAG_subprogram)
       <69>   DW_AT_external    : 1
       <69>   DW_AT_name        : (indirect string, offset: 0x221): funcx
       <6d>   DW_AT_decl_file   : 1
       <6e>   DW_AT_decl_line   : 2
       <6f>   DW_AT_prototyped  : 1
       <6f>   DW_AT_low_pc      : 0x400487
       <77>   DW_AT_high_pc     : 0x22
       <7f>   DW_AT_frame_base  : 1 byte block: 9c         (DW_OP_call_frame_cfa)
       <81>   DW_AT_GNU_all_call_sites: 1
       <81>   DW_AT_sibling     : <0xa0>
    <2><85>: Abbrev Number: 6 (DW_TAG_formal_parameter)
       <86>   DW_AT_name        : arg
       <8a>   DW_AT_decl_file   : 1
       <8b>   DW_AT_decl_line   : 2
       <8c>   DW_AT_type        : <0xa0>
       <90>   DW_AT_location    : 2 byte block: 91 58      (DW_OP_fbreg: -40)
    ...
    <1><a0>: Abbrev Number: 7 (DW_TAG_pointer_type)
       <a1>   DW_AT_byte_size   : 8
    ...

Here we see that the DW_TAG_pointer_type doesn't reference any further
type.  This also seems out of line with the DWARF standard (which I
think recommends using a DW_TAG_unspecified_type entry), however GDB
does handle the GCC generated DWARF better.

If we look at how GDB handles the DWARF from GCC, then we see this:

    (gdb) print *arg
    Attempt to dereference a generic pointer.

While on the current HEAD of master dereferencing arg causes undefined
behaviour which will likely crash GDB (for the same reason as was
described above for the 'finish' case).  On earlier versions of GDB
the ICC DWARF would cause this:

    (gdb) print *arg
    $1 = 0

In this patch both the return type, and general variable/parameter
type handling is fixed by transforming the synthetic void entries in
the DWARF, the ones that look like this:

    <1><6f>: Abbrev Number: 6 (DW_TAG_base_type)
       <70>   DW_AT_byte_size   : 0
       <71>   DW_AT_encoding    : 5        (signed)
       <72>   DW_AT_name        : (indirect string, offset: 0xcb): void

into GDB's builtin void type.  My criteria for performing the fix are:

  1. Binary produced by any version of ICC,
  2. We're producing an integer type,
  3. The size is 0, and
  4. The name is "void".

I ignore the signed / unsigned nature of the integer.

Potentially we could drop the ICC detection too, this should be a
reasonably safe transformation to perform, however, I'm generally
pretty nervous when it comes to modifying how the DWARF is parsed so,
for now, I have restricted this to ICC only.

I also added an assertion to maybe_negate_by_bytes.  This is nothing
to do with the actual fix, but should detect incorrect use of this
function in the future, without relying on undefined behaviour to
crash GDB.

I added a new test that makes use the of the testsuite's DWARF
generator.  As it is tricky to create target independent tests that
pass function parameters using the DWARF generator (as specifying the
argument location is target specific) I have instead made use of a
global variable void*.  This still shows the issue.

We already have a predicate in the DWARF parser to detect versions of
ICC prior to 14, however, this issue was spotted on a later version.
As a result I've added a new predicate that is true for any version of
ICC.

gdb/ChangeLog:

	* dwarf2read.c (struct dwarf2_cu): Add producer_is_icc field.
	(producer_is_icc): New function.
	(check_producer): Set producer_is_icc field on dwarf2_cu.
	(dwarf2_init_integer_type): New function.
	(read_base_type): Call dwarf2_init_integer_type instead of
	init_integer_type in all cases.
	(dwarf2_cu::dwarf2_cu): Initialise producer_is_icc field.
	* valprint.c (maybe_negate_by_bytes): Add an assertion that the
	LEN is greater than 0.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/void-type.c: New file.
	* gdb.dwarf2/void-type.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [src/erc32] Use ncurses instead of termcap on Cygwin too
@ 2018-10-30 21:22 sergiodj+buildbot
  2018-10-30 22:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-30 21:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1230d1bab8e36e1aa40f3bbadcef9b5d9ddc041 ***

Author: Joel Sherrill <joel@rtems.org>
Branch: master
Commit: c1230d1bab8e36e1aa40f3bbadcef9b5d9ddc041

[src/erc32] Use ncurses instead of termcap on Cygwin too

This removes a Cygwin-specific libtermcap hack that was dependent on
the presence of one of the multiple alternative libraries.  The one it
was hard-coded to pick isn't included with Cygwin anymore.

According to Corinna, libtermcap was removed from Cygwin a long time
ago, and libncurses is used in Cygwin for a long time too.

The fix is to make Cygwin use the same autoconf code to figure out the
correct lib as any other target.

sim/erc32/Changelog:
2018-10-30  Joel Sherrill <joel@rtems.org>

	* configure.ac: Remove the Cygwin-specific libtermcap.a hack
	and use the standard logic to determine which library to use.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Check return value of bfd_init
@ 2018-10-30 18:01 sergiodj+buildbot
  2018-10-30 17:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-30 18:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d5d104997da3b7beaaf7920caee40dcff8a78d9 ***

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

Check return value of bfd_init

Alan recently added a way for BFD library users to check whether they
were in fact loading a compatible version of BFD:

https://sourceware.org/ml/binutils/2018-10/msg00198.html

It seemed reasonable to me that gdb should do this check as well, in
case someone is dynamically linking against BFD.

Simon pointed out that an earlier version of the patch would cause a
gdb crash if the test failed.  This version works around this by
lowering the call to bfd_init and adding a comment explaining where
'error' can safely be called in captured_main_1.

gdb/ChangeLog
2018-10-30  Tom Tromey  <tom@tromey.com>

	* main.c (captured_main_1): Check return value of bfd_init.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove relational operators from common/offset-type.h
@ 2018-10-30  7:55 sergiodj+buildbot
  2018-10-30 15:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-30  7:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd332753fa7050bb9d7c89147e32d285099fe402 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fd332753fa7050bb9d7c89147e32d285099fe402

Remove relational operators from common/offset-type.h

This patch is a follow-up of:

  https://sourceware.org/ml/gdb-patches/2018-10/msg00601.html

It removes the declaration of the relational operators for
common/offset-type.h.  As it turns out, these overloads are not being
used when a new offset type is declared, because, according to Pedro
Alves:

  I think the functions aren't called because they are templates, and
  thus the built-in (non-template) versions take precedence.  If you
  make them non-templates, then they should be called.  But, the
  built-ins are fine, so yeah, we can just remove the custom
  definitions.

The patch also adjusts the comments on the code.

No regressions introduced.

gdb/ChangeLog:
2018-10-29  Sergio Durigan Junior  <sergiodj@redhat.com>

	* common/offset-type.h (DEFINE_OFFSET_REL_OP): Delete.
	Adjust comments.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Revert "GDB: Remote target can now accept the form unix::/path/to/socket."
@ 2018-10-29 21:40 sergiodj+buildbot
  2018-10-29 22:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-29 21:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 431f22cc098a118a862412c1bac1a8aa1bc6ceb7 ***

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

Revert "GDB: Remote target can now accept the form unix::/path/to/socket."

This reverts commit 88f5cc8cf8606478832c7d0d7b74755f3f625015.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Revert "GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested."
@ 2018-10-29 19:37 sergiodj+buildbot
  2018-10-30  4:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-29 19:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80e24d09860dbeba7d435b4a4f0990f85dbc084e ***

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

Revert "GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested."

This reverts commit f19c7ff839d7a32ebb48482ae7d318fb46ca823d.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Revert "GDB: Only build for "unix:" connections if AF_LOCAL is supported."
@ 2018-10-29 19:19 sergiodj+buildbot
  2018-10-29 20:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-29 19:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f53228719a0111e41c66da6c9c3b2ed1fd2aab9 ***

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

Revert "GDB: Only build for "unix:" connections if AF_LOCAL is supported."

This reverts commit 98a17ece013cb94cd602496b9efb92b8816b3953.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Provide get_shell declaration in procfs.c
@ 2018-10-29 17:37 sergiodj+buildbot
  2018-10-29 18:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-29 17:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30a7953dbfe3659c7bdc5b9b4c96f46903cb0254 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 30a7953dbfe3659c7bdc5b9b4c96f46903cb0254

Provide get_shell declaration in procfs.c

The Solaris build is currently broken:

/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c: In member function virtual void procfs_target::create_inferior(const char*, const string&, char**, int):
/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c:3038:28: error: get_shell was not declared in this scope
   const char *shell_file = get_shell ();
                            ^~~~~~~~~
/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c:3038:28: note: suggested alternative: getusershell
   const char *shell_file = get_shell ();
                            ^~~~~~~~~
                            getusershell

The following patch fixes this.  Tested on amd64-pc-solaris2.11.


2018-10-29  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

	* procfs.c: Include common/pathstuff.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB: Only build for "unix:" connections if AF_LOCAL is supported.
@ 2018-10-29  8:20 sergiodj+buildbot
  2018-10-29 15:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-29  8:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98a17ece013cb94cd602496b9efb92b8816b3953 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 98a17ece013cb94cd602496b9efb92b8816b3953

GDB: Only build for "unix:" connections if AF_LOCAL is supported.

Commit f19c7ff839d7a32ebb48482ae7d318fb46ca823d added a new member to the
prefixes array which included a use of the symbol AF_LOCAL.   Unfortunately,
not all systems declare this symbol.    This change only compiles the "unix:"
member if the system knows about AF_LOCAL.

gdb/ChangeLog:

* configure.ac: New test HAVE_AF_LOCAL
* common/netstuff.c (parse_connection_spec) [prefixes]: Only compile "unix:"
   if HAVE_AF_LOCAL is true.
* configure: regenerate.
* config.in: regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Add back missing braces in riscv-linux-nat.c
@ 2018-10-28 11:12 sergiodj+buildbot
  2018-10-28 20:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-28 11:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3d7226832e5750211ec300c5929dc0f035a3661 ***

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

gdb/riscv: Add back missing braces in riscv-linux-nat.c

In this commit:

    commit ee67fd7f3f6ca78eede2862e309c0bcf266bbd7e
    Date:   Thu Oct 25 12:03:31 2018 +0100

        gdb/riscv: Use correct regnum in riscv_linux_nat_target::fetch_registers

I incorrectly removed a set of braces in violation of the GDB coding
standard.  This commit adds them back.

gdb/ChangeLog:

	* riscv-linux-nat.c (riscv_linux_nat_target::fetch_registers):
	Add missing braces.  No functional change.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] OBVIOUS Use report_unrecognized_option_error in 'demangle' and 'info macro' commands.
@ 2018-10-27 20:36 sergiodj+buildbot
  2018-10-28  7:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd948f5b2be612b784591dbe438dc518f6b80d61 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: cd948f5b2be612b784591dbe438dc518f6b80d61

OBVIOUS Use report_unrecognized_option_error in 'demangle' and 'info macro' commands.

Rather than have some local logic to throw an error for an unrecognized option,
use the new cli-utils.h function throwing an error.

At the same time, fix some wrong indentation in info_macro_command
and fix a small bug in 'demangle' error handling:

Without the patch:
  (gdb) demangle -L c++ abcd
  Unrecognized option 'c++' to demangle command.  Try "help demangle".
  (gdb)

With the patch:
  (gdb) demangle -L c++ abcd
  Unrecognized option '-L' to demangle command.  Try "help demangle".

2018-10-27  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* macrocmd.c (info_macro_command): Use report_unrecognized_option_error
	to report a bad option and fix indentation.
	* demangle.c (demangle_command): Use report_unrecognized_option_error
	to report a bad option and correctly report the bad option.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a bunch of usages of gdb_suppress_tests in 'runto_main'.
@ 2018-10-27 18:48 sergiodj+buildbot
  2018-10-27 18:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8ee3f04a66141d5fa930cd77bc53ac0bc17de32 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: c8ee3f04a66141d5fa930cd77bc53ac0bc17de32

Remove a bunch of usages of gdb_suppress_tests in 'runto_main'.

In the 'info -q -t' patch series, I started a new test from
gdb.threads/threadapply.exp, that uses an obsolete way to do
runto_main.

This patch changes all occurrences of runto_main using gdb_suppress_tests
to use instead fail+return.

Note that there are still about 220 occurrences of gdb_suppress_tests
but unclear (to me) if these can be similarly trivially be replaced by a
fail+return.  Further cleanup can be done in follow-up patches.

Tests run on Debian/x86_64.

gdb/testsuite/ChangeLog
2018-10-27  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.arch/altivec-regs.exp: Do not use gdb_suppress_tests in
	runto_main, use fail + return instead.
	gdb.arch/amd64-byte.exp: Likewise.
	gdb.arch/amd64-dword.exp: Likewise.
	gdb.arch/amd64-word.exp: Likewise.
	gdb.arch/e500-abi.exp: Likewise.
	gdb.arch/e500-regs.exp: Likewise.
	gdb.arch/gdb1291.exp: Likewise.
	gdb.arch/gdb1431.exp: Likewise.
	gdb.arch/i386-avx.exp: Likewise.
	gdb.arch/i386-byte.exp: Likewise.
	gdb.arch/i386-prologue.exp: Likewise.
	gdb.arch/i386-sse.exp: Likewise.
	gdb.arch/i386-word.exp: Likewise.
	gdb.arch/iwmmxt-regs.exp: Likewise.
	gdb.arch/pa-nullify.exp: Likewise.
	gdb.arch/powerpc-prologue.exp: Likewise.
	gdb.arch/s390-tdbregs.exp: Likewise.
	gdb.arch/vsx-regs.exp: Likewise.
	gdb.asm/asm-source.exp: Likewise.
	gdb.base/auxv.exp: Likewise.
	gdb.base/bigcore.exp: Likewise.
	gdb.base/overlays.exp: Likewise.
	gdb.base/savedregs.exp: Likewise.
	gdb.base/setshow.exp: Likewise.
	gdb.base/sigaltstack.exp: Likewise.
	gdb.base/sigbpt.exp: Likewise.
	gdb.base/siginfo-addr.exp: Likewise.
	gdb.base/siginfo-obj.exp: Likewise.
	gdb.base/siginfo-thread.exp: Likewise.
	gdb.base/siginfo.exp: Likewise.
	gdb.base/signull.exp: Likewise.
	gdb.base/sigrepeat.exp: Likewise.
	gdb.base/structs2.exp: Likewise.
	gdb.threads/threadapply.exp: Likewise.
	gdb.threads/watchthreads.exp: Likewise.
	gdb.threads/watchthreads2.exp: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Cache a copy of the user's shell on macOS
@ 2018-10-27 18:36 sergiodj+buildbot
  2018-10-28  5:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b50a8b9a916ea2fe1379bcd8f122feef8129a0e9 ***

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

Cache a copy of the user's shell on macOS

Recent versions of macOS have a feature called System Integrity
Protection.  Among other things, This feature prevents ptrace from
tracing certain programs --- for example, the programs in /bin, which
includes typical shells.

This means that startup-with-shell does not work properly.  This is PR
cli/23364.  Currently there is a workaround in gdb to disable
startup-with-shell when this feature might be in use.

This patch changes gdb to be a bit more precise about when
startup-with-shell will not work, by checking whether the shell
executable is restricted.

If the shell is restricted, then this patch will also cause gdb to
cache a copy of the shell in the gdb cache directory, and then reset
the SHELL environment variable to point to this copy.  This lets
startup-with-shell work again.

Tested on High Sierra by trying to start a program using redirection,
and by running startup-with-shell.exp.

gdb/ChangeLog
2018-10-27  Tom Tromey  <tom@tromey.com>

	PR cli/23364:
	* darwin-nat.c (copied_shell): New global.
	(may_have_sip): Rename from should_disable_startup_with_shell.
	(copy_shell_to_cache, maybe_cache_shell): New functions.
	(darwin_nat_target::create_inferior): Update.  Use
	copied_shell.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Do not reopen temporary files
@ 2018-10-27 18:30 sergiodj+buildbot
  2018-10-28  2:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36033ef57cd048588f9a3d5523712147066421f2 ***

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

Do not reopen temporary files

The current callers of mkostemp close the file descriptor and then
re-open it with fopen.  It seemed better to me to continue to use the
already-opened file descriptor, so this patch rearranges the code a
little in order to do so.  It takes care to ensure that the files are
only unlinked after the file descriptor in question is closed, as
before.

gdb/ChangeLog
2018-10-27  Tom Tromey  <tom@tromey.com>

	* unittests/scoped_fd-selftests.c (test_to_file): New function.
	(run_tests): Call test_to_file.
	* dwarf-index-write.c (write_psymtabs_to_index): Do not reopen
	temporary files.
	* common/scoped_fd.h (scoped_fd::to_file): New method.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use mkostemp, not mkstemp
@ 2018-10-27 18:24 sergiodj+buildbot
  2018-10-28  1:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b3279b601e67ce47263082ef86cfc86e25607c5e ***

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

Use mkostemp, not mkstemp

I noticed that gdb could leak file descriptors coming from mkstemp.
This patch fixes the problem by importing the gnulib mkostemp instead,
and then changing gdb to pass O_CLOEXEC.

A small gnulib patch was needed.  This has already been accepted
upstream.

gdb/ChangeLog
2018-10-27  Tom Tromey  <tom@tromey.com>

	* unittests/scoped_mmap-selftests.c (test_normal): Use
	gdb_mkostemp_cloexec.
	* unittests/scoped_fd-selftests.c (test_destroy, test_release):
	Use gdb_mkostemp_cloexec.
	* gnulib/aclocal-m4-deps.mk, gnulib/aclocal.m4,
	gnulib/config.in, gnulib/configure,
	gnulib/import/Makefile.am, gnulib/import/Makefile.in,
	gnulib/import/m4/gnulib-cache.m4,
	gnulib/import/m4/gnulib-comp.m4: Update.
	* gnulib/import/m4/mkostemp.m4: New file.
	* gnulib/import/m4/mkstemp.m4: Remove.
	* gnulib/import/mkostemp.c: New file.
	* gnulib/import/mkstemp.m4: Remove.
	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Remove
	mkstemp, add mkostemp.  Apply new patch.
	* gnulib/import/stdlib.in.h: Apply patch.
	* gnulib/patches/0002-mkostemp-mkostemps-Fix-compilation-error-in-C-mode-o.patch:
	New file.
	* dwarf-index-write.c (write_psymtabs_to_index): Use
	gdb_mkostemp_cloexec.
	* common/filestuff.h (gdb_mkostemp_cloexec): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move mkdir_recursive to common/filestuff.c
@ 2018-10-27 18:18 sergiodj+buildbot
  2018-10-28  0:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e418a61a67a3476826259163383e5deb661042cc ***

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

Move mkdir_recursive to common/filestuff.c

This moves mkdir_recursive from dwarf-index-cache.c to
common/filestuff.c, and also changes it to return a boolean that says
whether or not it worked.

gdb/ChangeLog
2018-10-27  Tom Tromey  <tom@tromey.com>

	* unittests/mkdir-recursive-selftests.c: New file.
	* Makefile.in (SUBDIR_UNITTESTS_SRCS): Add
	unittests/mkdir-recursive-selftests.c.
	* dwarf-index-cache.c (mkdir_recursive): Move to
	common/filestuff.c.
	(index_cache::store): Check return value of mkdir_recursive.
	(create_dir_and_check, test_mkdir_recursive): Move to new file.
	(_initialize_index_cache): Don't register test.
	* common/filestuff.h (mkdir_recursive): Declare.
	* common/filestuff.c (mkdir_recursive): Move from
	dwarf-index-cache.c.  Return bool.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move make_temp_filename to common/pathstuff.c
@ 2018-10-27 18:16 sergiodj+buildbot
  2018-10-27 22:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29be4d9dee1263b36e33421dd8ea69b9b7308391 ***

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

Move make_temp_filename to common/pathstuff.c

Currently make_temp_filename is a function local to
write_psymtabs_to_index.  This patch moves it to pathstuff.c so that
it can be used from other places in gdb.

gdb/ChangeLog
2018-10-27  Tom Tromey  <tom@tromey.com>

	* dwarf-index-write.c (write_psymtabs_to_index): Move
	make_temp_filename to common/pathstuff.c.
	* common/pathstuff.h (make_temp_filename): Declare.
	* common/pathstuff.c (make_temp_filename): New function, moved
	from dwarf-index-write.c.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Unify shell-finding logic
@ 2018-10-27 18:10 sergiodj+buildbot
  2018-10-27 21:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 18:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 974e68446388769f023c6c9bfb1e67ed75199618 ***

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

Unify shell-finding logic

I noticed several places in gdb that were using getenv("SHELL") and
then falling back to "/bin/sh" if it returned NULL.  This unifies
these into a single function.

gdb/ChangeLog
2018-10-27  Tom Tromey  <tom@tromey.com>

	* procfs.c (procfs_target::create_inferior): Use get_shell.
	* cli/cli-cmds.c (shell_escape): Use get_shell.
	* windows-nat.c (windows_nat_target::create_inferior): Use
	get_shell.
	* common/pathstuff.c (get_shell): New function.
	* nat/fork-inferior.c (SHELL_FILE, get_startup_shell): Remove.
	(fork_inferior): Use get_shell.
	* common/pathstuff.h (get_shell): Declare.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables]
@ 2018-10-27 17:44 sergiodj+buildbot
  2018-10-27 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 17:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12615cba8411c845b33b98cc616439c66a34f03a ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 12615cba8411c845b33b98cc616439c66a34f03a

Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables]

Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables]

Main changes are:
* stack.c: Add two regexp preg and treg to print_variable_and_value_data
  and used them inside do_print_variable_and_value to filter the
  variables to print.

* symtab.h: Add a new function bool treg_matches_sym_type_name, that
  factorises type matching logic.

* symtab.c: Add type/name matching logic to 'info functions|variables'.

* stack.c : Add type/name matching logic to 'info args|locals'.

gdb/ChangeLog
2018-10-27  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* stack.c (print_variable_and_value_data): Add preg and treg.
	(print_frame_local_vars): Add quiet, regexp and t_regexp arguments,
	and update callers.
	(print_frame_arg_vars): Likewise.
	(prepare_reg): New function.
	(info_locals_command): Extract info print args and use them.
	(info_args_command): Likewise.
	(_initialize_stack): Modify on-line help.
	* symtab.c (treg_matches_sym_type_name): New function.
	(search_symbols): New arg t_regexp.
	(symtab_symbol_info): New args quiet, regexp, t_regexp.
	(info_variables_command): Extract info print args and use them.
	(info_functions_command): Likewise.
	(info_types_command): Update call to symtab_symbol_info.
	(_initialize_symtab): Modify on-line help.
	* symtab.h (treg_matches_sym_type_name): New function.
	(search_symbols): New t_regexp arg.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP]
@ 2018-10-27 14:04 sergiodj+buildbot
  2018-10-27 18:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 14:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 82b5e646c22b25862debc68a30d44957a9e5e3d3 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 82b5e646c22b25862debc68a30d44957a9e5e3d3

Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP]

Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP]

gdb/testsuite/ChangeLog
2018-10-27  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/info_qt.c: New file.
	* gdb.base/info_qt.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] New cli-utils.h/.c function extract_info_print_args
@ 2018-10-27 13:37 sergiodj+buildbot
  2018-10-27 15:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d4cad90ca7c4394a1799efaa79c784f84a18161 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 0d4cad90ca7c4394a1799efaa79c784f84a18161

New cli-utils.h/.c function extract_info_print_args

New cli-utils.h/.c function extract_info_print_args factorizes
the extraction of the args '[-q] [-t TYPEREGEXP] [NAMEREGEXP]'.
New cli-utils.h/.c function report_unrecognized_option_error
factorizes reporting an unknown option for a command.

These functions will be used by the commands
  info [args|functions|locals|variables]

As extract_info_print_args will be used for 'info functions|variables' which
already have the NAMEREGEXP arg, it provides a backward compatible
behaviour.

cli-utils.c has a new static function extract_arg_maybe_quoted
that extracts an argument, possibly quoted.  The behaviour of this
function is similar to the parsing done by gdb_argv.

gdb/ChangeLog
2018-10-27  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* cli-utils.c (extract_arg_maybe_quoted): New function.
	(extract_info_print_args): New function.
	(info_print_args_help): New function.
	(report_unrecognized_option_error): New function.
	* cli-utils.h (extract_arg_maybe_quoted): New function.
	(extract_info_print_args): New function.
	(info_print_args_help): New function.
	(report_unrecognized_option_error): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Support AT_HWCAP2 on FreeBSD.
@ 2018-10-27 11:14 sergiodj+buildbot
  2018-10-27 12:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 11:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7ded98f4cf9891cf04fe6af5c90b6af6709dff8 ***

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

Support AT_HWCAP2 on FreeBSD.

include/ChangeLog:

	* elf/common.h (AT_FREEBSD_HWCAP2): Define.

gdb/ChangeLog:

	* fbsd-tdep.c (fbsd_print_auxv_entry): Handle AT_FREEBSD_HWCAP2.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Linux signal frame support.
@ 2018-10-27 10:13 sergiodj+buildbot
  2018-10-27 10:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27 10:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77c6f5fcdae65da0428ff75fa81059f1b5271cf0 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 77c6f5fcdae65da0428ff75fa81059f1b5271cf0

RISC-V: Linux signal frame support.

Add support for recognizing signal trampolines, parsing the signal frame,
and reading register values from it.

	gdb/
	* riscv-linux-tdep.c: Include tramp-frame.h and trad-frame.h.
	(riscv_linux_sigframe_init): Declare.
	(RISCV_INST_LI_A7_SIGRETURN, RISCV_INT_ECALL): New.
	(riscv_linux_sigframe): New.
	(SIGFRAME_SIGINFO_SIZE, UCONTEXT_MCONTEXT_OFFSET): New.
	(riscv_linux_sigframe_init): Define.
	(riscv_linux_init_abi): Call tramp_frame_prepend_unwinder.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Linux signal frame support.
@ 2018-10-27  8:57 sergiodj+buildbot
  2018-10-27  9:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27  8:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a61382623e271fe2df0fe8f7558ea545db8b561 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 8a61382623e271fe2df0fe8f7558ea545db8b561

RISC-V: Linux signal frame support.

Make riscv_isa_flen available to the linux native code, and clean up duplicate
comments.

	gdb/
	* riscv-tdep.c (riscv_isa_xlen): Refer to riscv-tdep.h comment.
	(riscv_isa_flen): Likewise.  Drop static.
	* riscv-tdep.h (riscv_isa_xlen): Move riscv-tdep.c comment to here.
	(riscv_isa_flen): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Add support for EBB and PMU registers
@ 2018-10-27  6:36 sergiodj+buildbot
  2018-10-27  5:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27  6:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 232bfb8644f0a083969d8359a37bc23764642611 ***

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

[PowerPC] Add support for EBB and PMU registers

This patch adds support for registers of the Event Based Branching and
Performance Monitoring Units for the powerpc linux native and core
file targets, and for the powerpc linux server stub.

All three EBB registers are accessible.  Only a subset of the PMU
registers can be accessed through ptrace.  Because of this, the PMU
registers are enumerated individually in gdbarch_tdep, as opposed to
having a single "have_pmu" flag.  This is intended to make it easier
to add additional PMU registers in the future, since checking a
"have_pmu" flag elsewhere in the code would no longer be correct.  The
tdesc feature is named org.gnu.gdb.power.linux.pmu because of this.

It's unclear if it makes sense to save and restore these registers
across function calls, since some of them can be modified
asynchronously.  They are also not tracked in record-replay mode.

The kernel can return ENODATA when ptrace is used to get the EBB
registers, unless a linux performance event that uses EBB is open in
the inferior.  For this reason, the "fill" functions in the server
stub for the ebb register sets is not implemented.

Since gdbserver writes all registers in one go before resuming the
inferior, this error would not be detected at the time the user tries
to write to one of the registers on the client side, and gdbserver
would print out warnings every time it resumes the inferior when no
ebb performance event is opened, so there is currently no
straightforward way to handle this case.  This means the ebb registers
in the client-side regcache can become dirty when the user tries to
write to them, until the inferior is resumed and stopped again.

A related issue is that 'G' packets used to write to unrelated
registers will include bad data for the EBB registers if they are
unavailable, since no register status information is included in the
'G' packet.  This data won't be written to the inferior by the
gdbserver stub because the "fill" functions are not implemented, and
currently the gdbserver stub doesn't change the status of the
registers in its own regcache in response to 'G' packets.

Another limitation for the ebb registers is that traceframes don't
record if registers are available or not, so if these registers are
collected when a tracepoint is hit and the inferior has no ebb event
opened, the user will see zero values for all of them, instead of the
usual <unavailable>.

Because these registers are often unavailable, trying to store them
with target_store_registers with -1 for the regno argument (all
registers) would almost always fail, so they are ignored in this case.

gdb/ChangeLog:
2018-10-26  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
	    Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* arch/ppc-linux-common.h (PPC_LINUX_SIZEOF_EBBREGSET)
	(PPC_LINUX_SIZEOF_PMUREGSET): Declare.
	* nat/ppc-linux.h (PPC_FEATURE2_EBB, NT_PPC_EBB, NT_PPC_PMU):
	Define if not already defined.
	* features/rs6000/power-ebb.xml: New file.
	* features/rs6000/power-linux-pmu.xml: New file.
	* features/rs6000/powerpc-isa207-vsx32l.xml: Include ebb and pmu
	features.
	* features/rs6000/powerpc-isa207-vsx64l.xml: Likewise.
	* features/rs6000/powerpc-isa207-vsx32l.c: Re-generate.
	* features/rs6000/powerpc-isa207-vsx64l.c: Re-generate.
	* regformats/rs6000/powerpc-isa207-vsx32l.dat: Re-generate.
	* regformats/rs6000/powerpc-isa207-vsx64l.dat: Re-generate.
	* ppc-linux-nat.c (fetch_register, fetch_ppc_registers): Call
	fetch_regset with ebb and pmu regsets.
	(store_register, store_ppc_registers): Call store_regset with ebb
	and pmu regsets.
	(ppc_linux_nat_target::read_description): Set isa207 field in the
	features struct if ebb and pmu are avaiable.
	* ppc-linux-tdep.c (ppc32_regmap_ebb, ppc32_regmap_pmu)
	(ppc32_linux_ebbregset, ppc32_linux_pmuregset): New globals.
	(ppc_linux_iterate_over_regset_sections): Call back with the ebb
	and pmu regsets.
	(ppc_linux_core_read_description): Check if the pmu section is
	present and set isa207 in the features struct.
	* ppc-linux-tdep.h (ppc32_linux_ebbregset)
	(ppc32_linux_pmuregset): Declare.
	* ppc-tdep.h (struct gdbarch_tdep) <ppc_mmcr0_regnum>: New field.
	<ppc_mmcr2_regnum, ppc_siar_regnum, ppc_sdar_regnum>: New fields.
	<ppc_sier_regnum>: New field.
	(enum): <PPC_BESCR_REGNUM, PPC_EBBHR_REGNUM, PPC_EBBRR_REGNUM>:
	New enum values.
	<PPC_MMCR0_REGNUM, PPC_MMCR2_REGNUM, PPC_SIAR_REGNUM>: New enum
	values.
	<PPC_SDAR_REGNUM, PPC_SIER_REGNUM>: New enum values.
	(PPC_IS_EBB_REGNUM, PPC_IS_PMU_REGNUM): Define.
	* rs6000-tdep.c (rs6000_gdbarch_init): Look for and validate the
	ebb and pmu features.

gdb/gdbserver/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* configure.srv (powerpc*-*-linux*): Add rs6000/power-ebb.xml and
	rs6000/power-linux-pmu.xml to srv_xmlfiles.
	* linux-ppc-low.c (ppc_store_ebbregset, ppc_fill_pmuregset)
	(ppc_store_pmuregset): New functions.
	(ppc_regsets): Add entries for ebb and pmu regsets.
	(ppc_arch_setup): Set isa207 in features struct if the ebb and
	pmu regsets are available.  Set sizes for these regsets.

gdb/doc/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.texinfo (PowerPC Features): Describe new features
	"org.gnu.gdb.power.ebb" and "org.gnu.gdb.power.linux.pmu".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove DEF_VECs from symtab.h
@ 2018-10-27  0:33 sergiodj+buildbot
  2018-10-27 13:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-27  0:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c39bc03545798694b4ed2a5cd5caedd7ce3cc50 ***

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

Remove DEF_VECs from symtab.h

This removes a couple of DEF_VECs from symtab.h, replacing them with
std::vector at the points of use.

gdb/ChangeLog
2018-10-26  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (recursively_compute_inclusions): Use std::vector.
	(compute_compunit_symtab_includes): Update.
	* symtab.h: (symtab_ptr): Remove typedef.  Don't define a VEC.
	(compunit_symtab_ptr): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Add support for HTM registers
@ 2018-10-26 22:08 sergiodj+buildbot
  2018-10-27  7:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 22:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d619c01db64c533df3ffc706b694f293347f0d8 ***

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

[PowerPC] Add support for HTM registers

This patch adds support for Hardware Transactional Memory registers
for the powerpc linux native and core file targets, and for the
pwoerpc linux server stub.

These registers include both the HTM special-purpose registers (TFHAR,
TEXASR and TFIAR) as well as the set of registers that are
checkpointed (saved) when a transaction is initiated, which the
processor restores in the event of a transaction failure.

The set of checkpointed general-purpose registers is returned by the
linux kernel in the same format as the regular general-purpose
registers, defined in struct pt_regs.  However, the architecture
specifies that only some of the registers present in pt_regs are
checkpointed (GPRs 0-31, CR, XER, LR and CTR).  The kernel fills the
slots for MSR and NIP with other info.  The other fields usually don't
have meaningful values.  GDB doesn't define registers that are not
checkpointed in the architecture, but when generating a core file, GDB
fills the slot for the checkpointed MSR with the regular MSR.  These
are usually similar, although some bits might be different, and in
some cases the checkpointed MSR will have a value of 0 in a
kernel-generated core-file.  The checkpointed NIP is filled with TFHAR
by GDB in the core-file, which is what the kernel does.  The other
fields are set to 0 by GDB.

Core files generated by the kernel have a note section for
checkpointed GPRs with the same size for both 32-bit and 64-bit
threads, and the values for the registers of a 32-bit thread are
squeezed in the first half, with no useful data in the second half.
GDB generates a smaller note section for 32-bit threads, but can read
both sizes.

The checkpointed XER is required to be 32-bit in the target
description documentation, even though the more recent ISAs define it
as 64-bit wide, since the high-order 32-bits are reserved, and because
in Linux there is no way to get a 64-bit checkpointed XER for 32-bit
threads.  If this changes in the future, the target description
feature requirement can be relaxed to allow for a 64-bit checkpointed
XER.

Access to the checkpointed CR (condition register) can be confusing.
The architecture only specifies that CR fields 1 to 7 (the 24 least
significant bits) are checkpointed, but the kernel provides all 8
fields (32 bits).  The value of field 0 is not masked by ptrace, so it
will sometimes show the result of some kernel operation, probably
treclaim., which sets this field.

The checkpointed registers are marked not to be saved and restored.
Inferior function calls during an active transaction don't work well,
and it's unclear what should be done in this case.  TEXASR and TFIAR
can be altered asynchronously, during transaction failure recording,
so they are also not saved and restored.  For consistency neither is
TFHAR.

Record and replay also doesn't work well when transactions are
involved.  This patch doesn't address this, so the values of the HTM
SPRs will sometimes be innacurate when the record/relay target is
enabled.  For instance, executing a "tbegin." alters TFHAR and TEXASR,
but these changes are not currently recorded.

Because the checkpointed registers are only available when a
transaction is active (or suspended), ptrace can return ENODATA when
gdb tries to read these registers and the inferior is not in a
transactional state.  The registers are set to the unavailable state
when this happens.  When gbd tries to write to one of these registers,
and it is unavailable, an error is raised.

The "fill" functions for checkpointed register sets in the server stub
are not implemented for the same reason as for the EBB register set,
since ptrace can also return ENODATA for checkpointed regsets.  The
same issues with 'G' packets apply here.

Just like for the EBB registers, tracepoints will not mark the
checkpointed registers as unavailable if the inferior was not in a
transaction, so their content will also show 0 instead of
<unavailable> when inspecting trace data.

The new tests record the values of the regular registers before
stepping the inferior through a "tbegin." instruction to start a
transaction, then the checkpointed registers are checked against the
recorded pre-transactional values.  New values are written to the
checkpointed registers and recorded, the inferior continues until the
transaction aborts (which is usually immediately when it is resumed),
and the regular registers are checked against the recorded values,
because the abort should have reverted the registers to these values.

Like for the EBB registers, target_store_registers will ignore the
checkpointed registers when called with -1 as the regno
argument (store all registers in one go).

gdb/ChangeLog:
2018-10-26  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
	    Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* arch/ppc-linux-tdesc.h (tdesc_powerpc_isa207_htm_vsx32l)
	(tdesc_powerpc_isa207_htm_vsx64l): Declare.
	* arch/ppc-linux-common.h (PPC_LINUX_SIZEOF_TM_SPRREGSET)
	(PPC32_LINUX_SIZEOF_CGPRREGSET, PPC64_LINUX_SIZEOF_CGPRREGSET)
	(PPC_LINUX_SIZEOF_CFPRREGSET, PPC_LINUX_SIZEOF_CVMXREGSET)
	(PPC_LINUX_SIZEOF_CVSXREGSET, PPC_LINUX_SIZEOF_CPPRREGSET)
	(PPC_LINUX_SIZEOF_CDSCRREGSET, PPC_LINUX_SIZEOF_CTARREGSET):
	Define.
	(struct ppc_linux_features) <htm>: New field.
	(ppc_linux_no_features): Add initializer for htm field.
	* arch/ppc-linux-common.c (ppc_linux_match_description): Return
	new tdescs.
	* nat/ppc-linux.h (PPC_FEATURE2_HTM, NT_PPC_TM_CGPR)
	(NT_PPC_TM_CFPR, NT_PPC_TM_CVMX, NT_PPC_TM_CVSX)
	(NT_PPC_TM_SPR, NT_PPC_TM_CTAR, NT_PPC_TM_CPPR, NT_PPC_TM_CDSCR):
	Define if not already defined.
	* features/Makefile (WHICH): Add rs6000/powerpc-isa207-htm-vsx32l
	and rs6000/powerpc-isa207-htm-vsx64l.
	(XMLTOC): Add rs6000/powerpc-isa207-htm-vsx32l.xml and
	rs6000/powerpc-isa207-htm-vsx64l.xml.
	* features/rs6000/power-htm-spr.xml: New file.
	* features/rs6000/power-htm-core.xml: New file.
	* features/rs6000/power64-htm-core.xml: New file.
	* features/rs6000/power-htm-fpu.xml: New file.
	* features/rs6000/power-htm-altivec.xml: New file.
	* features/rs6000/power-htm-vsx.xml: New file.
	* features/rs6000/power-htm-ppr.xml: New file.
	* features/rs6000/power-htm-dscr.xml: New file.
	* features/rs6000/power-htm-tar.xml: New file.
	* features/rs6000/powerpc-isa207-htm-vsx32l.xml: New file.
	* features/rs6000/powerpc-isa207-htm-vsx64l.xml: New file.
	* features/rs6000/powerpc-isa207-htm-vsx32l.c: Generate.
	* features/rs6000/powerpc-isa207-htm-vsx64l.c: Generate.
	* regformats/rs6000/powerpc-isa207-htm-vsx32l.dat: Generate.
	* regformats/rs6000/powerpc-isa207-htm-vsx64l.dat: Generate.
	* ppc-linux-nat.c (fetch_register, fetch_ppc_registers): Call
	fetch_regset with HTM regsets.
	(store_register, store_ppc_registers): Call store_regset with HTM
	regsets.
	(ppc_linux_nat_target::read_description): Set htm field in the
	features struct if needed.
	* ppc-linux-tdep.c: Include
	features/rs6000/powerpc-isa207-htm-vsx32l.c and
	features/rs6000/powerpc-isa207-htm-vsx64l.c.
	(ppc32_regmap_tm_spr, ppc32_regmap_cgpr, ppc64_le_regmap_cgpr)
	(ppc64_be_regmap_cgpr, ppc32_regmap_cfpr, ppc32_le_regmap_cvmx)
	(ppc32_be_regmap_cvmx, ppc32_regmap_cvsx, ppc32_regmap_cppr)
	(ppc32_regmap_cdscr, ppc32_regmap_ctar): New globals.
	(ppc32_linux_tm_sprregset, ppc32_linux_cgprregset)
	(ppc64_be_linux_cgprregset, ppc64_le_linux_cgprregset)
	(ppc32_linux_cfprregset, ppc32_le_linux_cvmxregset)
	(ppc32_be_linux_cvmxregset, ppc32_linux_cvsxregset)
	(ppc32_linux_cpprregset, ppc32_linux_cdscrregset)
	(ppc32_linux_ctarregset): New globals.
	(ppc_linux_cgprregset, ppc_linux_cvmxregset): New functions.
	(ppc_linux_collect_core_cpgrregset): New function.
	(ppc_linux_iterate_over_regset_sections): Call back with the htm
	regsets.
	(ppc_linux_core_read_description): Check if the tm spr section is
	present and set htm in the features struct.
	(_initialize_ppc_linux_tdep): Call
	initialize_tdesc_powerpc_isa207_htm_vsx32l and
	initialize_tdesc_powerpc_isa207_htm_vsx64l.
	* ppc-linux-tdep.h (ppc_linux_cgprregset, ppc_linux_cvmxregset):
	Declare.
	(ppc32_linux_tm_sprregset, ppc32_linux_cfprregset)
	(ppc32_linux_cvsxregset, ppc32_linux_cpprregset)
	(ppc32_linux_cdscrregset, ppc32_linux_ctarregset): Declare.
	* ppc-tdep.h (struct gdbarch_tdep) <have_htm_spr, have_htm_core>:
	New fields.
	<have_htm_fpu, have_htm_altivec, have_htm_vsx>:
	Likewise.
	<ppc_cppr_regnum, ppc_cdscr_regnum, ppc_ctar_regnum>: Likewise.
	<ppc_cdl0_regnum, ppc_cvsr0_regnum, ppc_cefpr0_regnum>: Likewise.
	(enum) <PPC_TFHAR_REGNUM, PPC_TEXASR_REGNUM, PPC_TFIAR_REGNUM>:
	New enum fields.
	<PPC_CR0_REGNUM, PPC_CCR_REGNUM, PPC_CXER_REGNUM>: Likewise.
	<PPC_CLR_REGNUM, PPC_CCTR_REGNUM, PPC_CF0_REGNUM>: Likewise.
	<PPC_CFPSCR_REGNUM, PPC_CVR0_REGNUM, PPC_CVSCR_REGNUM>: Likewise.
	<PPC_CVRSAVE_REGNUM, PPC_CVSR0_UPPER_REGNUM>: Likewise.
	<PPC_CPPR_REGNUM, PPC_CDSCR_REGNUM>: Likewise.
	<PPC_CTAR_REGNUM>: Likewise.
	(PPC_IS_TMSPR_REGNUM, PPC_IS_CKPTGP_REGNUM, PPC_IS_CKPTFP_REGNUM)
	(PPC_IS_CKPTVMX_REGNUM, PPC_IS_CKPTVSX_REGNUM): Define.
	* rs6000-tdep.c (IS_CDFP_PSEUDOREG, IS_CVSX_PSEUDOREG)
	(IS_CEFP_PSEUDOREG): Define.
	(rs6000_register_name): Hide the upper halves of checkpointed VSX
	registers.  Return names for the checkpointed DFP, VSX, and EFP
	pseudo registers.
	(rs6000_pseudo_register_type): Remove initial assert and raise an
	internal error in the else clause instead.  Return types for the
	checkpointed DFP, VSX, and EFP pseudo registers.
	(dfp_pseudo_register_read, dfp_pseudo_register_write): Handle
	checkpointed DFP pseudo registers.
	(vsx_pseudo_register_read, vsx_pseudo_register_write): Handle
	checkpointed VSX pseudo registers.
	(efp_pseudo_register_read, efp_pseudo_register_write): Rename
	from efpr_pseudo_register_read and
	efpr_pseudo_register_write.  Handle checkpointed EFP pseudo
	registers.
	(rs6000_pseudo_register_read, rs6000_pseudo_register_write):
	Handle checkpointed DFP, VSX, and EFP registers.
	(dfp_ax_pseudo_register_collect, vsx_ax_pseudo_register_collect)
	(efp_ax_pseudo_register_collect): New functions.
	(rs6000_ax_pseudo_register_collect): Move DFP, VSX and EFP pseudo
	register logic to new functions.  Handle checkpointed DFP, VSX,
	and EFP pseudo registers.
	(rs6000_gdbarch_init): Look for and validate the htm features.
	Include checkpointed DFP, VSX and EFP pseudo-registers.
	* NEWS: Mention access to PPR, DSCR, TAR, EBB/PMU registers and
	HTM registers.

gdb/gdbserver/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* configure.srv (ipa_ppc_linux_regobj): Add
	powerpc-isa207-htm-vsx32l-ipa.o and
	powerpc-isa207-htm-vsx64l-ipa.o.
	(powerpc*-*-linux*): Add powerpc-isa207-htm-vsx32l.o and
	powerpc-isa207-htm-vsx64l.o to srv_regobj.  Add
	rs6000/power-htm-spr.xml, rs6000/power-htm-core.xml,
	rs6000/power64-htm-core.xml, rs6000/power-htm-fpu.xml,
	rs6000/power-htm-altivec.xml, rs6000/power-htm-vsx.xml,
	rs6000/power-htm-ppr.xml, rs6000/power-htm-dscr.xml,
	rs6000/power-htm-tar.xml, rs6000/powerpc-isa207-htm-vsx32l.xml,
	and rs6000/powerpc-isa207-htm-vsx64l.xml to srv_xmlfiles.
	* linux-ppc-tdesc-init.h (enum ppc_linux_tdesc)
	<PPC_TDESC_ISA207_HTM_VSX>: New enum value.
	(init_registers_powerpc_isa207_htm_vsx32l)
	(init_registers_powerpc_isa207_htm_vsx64l): Declare.
	* linux-ppc-low.c (ppc_fill_tm_sprregset, ppc_store_tm_sprregset)
	(ppc_store_tm_cgprregset, ppc_store_tm_cfprregset)
	(ppc_store_tm_cvrregset, ppc_store_tm_cvsxregset)
	(ppc_store_tm_cpprregset, ppc_store_tm_cdscrregset)
	(ppc_store_tm_ctarregset): New functions.
	(ppc_regsets): Add entries for HTM regsets.
	(ppc_arch_setup): Set htm in features struct when needed.  Set
	sizes for the HTM regsets.
	(ppc_get_ipa_tdesc_idx): Return PPC_TDESC_ISA207_HTM_VSX.
	(initialize_low_arch): Call
	init_registers_powerpc_isa207_htm_vsx32l and
	init_registers_powerpc_isa207_htm_vsx64l.
	* linux-ppc-ipa.c (get_ipa_tdesc): Handle
	PPC_TDESC_ISA207_HTM_VSX.
	(initialize_low_tracepoint): Call
	init_registers_powerpc_isa207_htm_vsx32l and
	init_registers_powerpc_isa207_htm_vsx64l.

gdb/testsuite/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.arch/powerpc-htm-regs.c: New file.
	* gdb.arch/powerpc-htm-regs.exp: New file.

gdb/doc/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.texinfo (PowerPC Features): Describe new features
	"org.gnu.gdb.power.htm.spr", "org.gnu.gdb.power.htm.core",
	"org.gnu.gdb.power.htm.fpu", "org.gnu.gdb.power.htm.altivec",
	"org.gnu.gdb.power.htm.vsx", "org.gnu.gdb.power.htm.ppr",
	"org.gnu.gdb.power.htm.dscr", "org.gnu.gdb.power.htm.tar".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Reject tdescs with VSX and no FPU or Altivec
@ 2018-10-26 21:00 sergiodj+buildbot
  2018-10-27  7:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 21:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 81ab84fd6cdaab121988e0c424f8cdc0ae472e14 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 81ab84fd6cdaab121988e0c424f8cdc0ae472e14

[PowerPC] Reject tdescs with VSX and no FPU or Altivec

Currently rs6000_gdbarch_init will accept a tdesc with the
"org.gnu.gdb.power.vsx" feature but without the
"org.gnu.gdb.power.altivec" or "org.gnu.gdb.power.fpu".

It isn't clear from the standard features documentation that these are
requirements.  However, these tdescs would cause trouble in the VSX
pseudo-register functions, so this patch will cause them to be
rejected.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* rs6000-tdep.c (rs6000_gdbarch_init): Reject tdescs with vsx but
	without altivec or fpu.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Add support for TAR
@ 2018-10-26 20:29 sergiodj+buildbot
  2018-10-27  5:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 20:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2cf6173f33bbb562881c571bfecd129fe94b158 ***

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

[PowerPC] Add support for TAR

This patch adds support for the Target Address Register for powerpc
linux native and core file targets, and in the powerpc linux server
stub.

gdb/ChangeLog:
2018-10-26  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
	    Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* arch/ppc-linux-tdesc.h (tdesc_powerpc_isa207_vsx32l)
	(tdesc_powerpc_isa207_vsx64l): Declare.
	* arch/ppc-linux-common.h (PPC_LINUX_SIZEOF_TARREGSET): Define.
	(struct ppc_linux_features) <isa207>: New field.
	(ppc_linux_no_features): Add initializer for isa207 field.
	* arch/ppc-linux-common.c (ppc_linux_match_description): Return
	new tdescs.
	* nat/ppc-linux.h (PPC_FEATURE2_ARCH_2_07, PPC_FEATURE2_TAR)
	(NT_PPC_TAR): Define if not already defined.
	* features/Makefile (WHICH): Add rs6000/powerpc-isa207-vsx32l and
	rs6000/powerpc-isa207-vsx64l.
	(XMLTOC): Add rs6000/powerpc-isa207-vsx32l.xml and
	rs6000/powerpc-isa207-vsx64l.xml.
	* features/rs6000/power-tar.xml: New file.
	* features/rs6000/powerpc-isa207-vsx32l.xml: New file.
	* features/rs6000/powerpc-isa207-vsx64l.xml: New file.
	* features/rs6000/powerpc-isa207-vsx32l.c: Generate.
	* features/rs6000/powerpc-isa207-vsx64l.c: Generate.
	* regformats/rs6000/powerpc-isa207-vsx32l.dat: Generate.
	* regformats/rs6000/powerpc-isa207-vsx64l.dat: Generate.
	* ppc-linux-nat.c (fetch_register, fetch_ppc_registers): Call
	fetch_regset with the TAR regset.
	(store_register, store_ppc_registers): Call store_regset with the
	TAR regset.
	(ppc_linux_nat_target::read_description): Set isa207 field in the
	features struct if needed.
	* ppc-linux-tdep.c: Include
	features/rs6000/powerpc-isa207-vsx32l.c and
	features/rs6000/powerpc-isa207-vsx64l.c.
	(ppc32_regmap_tar, ppc32_linux_tarregset): New globals.
	(ppc_linux_iterate_over_regset_sections): Call back with the tar
	regset.
	(ppc_linux_core_read_description): Check if the tar section is
	present and set isa207 in the features struct.
	(_initialize_ppc_linux_tdep): Call
	initialize_tdesc_powerpc_isa207_vsx32l and
	initialize_tdesc_powerpc_isa207_vsx64l.
	* ppc-linux-tdep.h (ppc32_linux_tarregset): Declare.
	* ppc-tdep.h (gdbarch_tdep) <ppc_tar_regnum>: New field.
	(enum) <PPC_TAR_REGNUM>: New enum value.
	* rs6000-tdep.c (rs6000_gdbarch_init): Look for and validate tar
	feature.
	(ppc_process_record_op31): Record changes to TAR.

gdb/gdbserver/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* configure.srv (ipa_ppc_linux_regobj): Add
	powerpc-isa207-vsx64l-ipa.o and powerpc-isa207-vsx32l-ipa.o.
	(powerpc*-*-linux*): Add powerpc-isa207-vsx32l.o and
	powerpc-isa207-vsx64l.o to srv_regobj, add rs6000/power-tar.xml,
	rs6000/powerpc-isa207-vsx32l.xml, and
	rs6000/powerpc-isa207-vsx64l.xml to srv_xmlfiles.
	* linux-ppc-tdesc-init.h (enum ppc_linux_tdesc)
	<PPC_TDESC_ISA207_VSX>: New enum value.
	(init_registers_powerpc_isa207_vsx32l): Declare.
	(init_registers_powerpc_isa207_vsx64l): Declare.
	* linux-ppc-low.c (ppc_fill_tarregset): New function.
	(ppc_store_tarregset): New function.
	(ppc_regsets): Add entry for the TAR regset.
	(ppc_arch_setup): Set isa207 in features struct when needed.  Set
	size for the TAR regsets.
	(ppc_get_ipa_tdesc_idx): Return PPC_TDESC_ISA207_VSX.
	(initialize_low_arch): Call init_registers_powerpc_isa207_vsx32l
	and init_registers_powerpc_isa207_vsx64l.
	* linux-ppc-ipa.c (get_ipa_tdesc): Handle PPC_TDESC_ISA207_VSX.
	(initialize_low_tracepoint): Call
	init_registers_powerpc_isa207_vsx32l and
	init_registers_powerpc_isa207_vsx64l.

gdb/testsuite/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.arch/powerpc-tar.c: New file.
	* gdb.arch/powerpc-tar.exp: New file.

gdb/doc/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.texinfo (PowerPC Features): Describe new feature
	"org.gnu.gdb.power.tar".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Add support for PPR and DSCR
@ 2018-10-26 20:20 sergiodj+buildbot
  2018-10-27  1:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 20:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ca18ed6d22398dd3009ba72d3a1e7747e40753d ***

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

[PowerPC] Add support for PPR and DSCR

This patch adds gdb support for the Program Priorty Register and the
Data Stream Control Register, for the powerpc linux native and core
file targets, and for the powerpc linux server stub.

gdb/ChangeLog:
2018-10-26  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
	    Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* arch/ppc-linux-tdesc.h (tdesc_powerpc_isa205_ppr_dscr_vsx32l)
	(tdesc_powerpc_isa205_ppr_dscr_vsx64l): Declare.
	* arch/ppc-linux-common.h (PPC_LINUX_SIZEOF_PPRREGSET)
	(PPC_LINUX_SIZEOF_DSCRREGSET): Define.
	(struct ppc_linux_features) <ppr_dscr>: New field.
	(ppc_linux_no_features): Add initializer for ppr_dscr field.
	* arch/ppc-linux-common.c (ppc_linux_match_description): Return
	new tdescs.
	* nat/ppc-linux.h (PPC_FEATURE2_DSCR, NT_PPC_PPR, NT_PPC_DSCR):
	Define if not already defined.
	* features/Makefile (WHICH): Add
	rs6000/powerpc-isa205-ppr-dscr-vsx32l and
	rs6000/powerpc-isa205-ppr-dscr-vsx64l.
	(XMLTOC): Add rs6000/powerpc-isa205-ppr-dscr-vsx32l.xml and
	rs6000/powerpc-isa205-ppr-dscr-vsx64l.xml.
	* features/rs6000/power-dscr.xml: New file.
	* features/rs6000/power-ppr.xml: New file.
	* features/rs6000/powerpc-isa205-ppr-dscr-vsx32l.xml: New file.
	* features/rs6000/powerpc-isa205-ppr-dscr-vsx64l.xml: New file.
	* features/rs6000/powerpc-isa205-ppr-dscr-vsx32l.c: Generate.
	* features/rs6000/powerpc-isa205-ppr-dscr-vsx64l.c: Generate.
	* regformats/rs6000/powerpc-isa205-ppr-dscr-vsx32l.dat: Generate.
	* regformats/rs6000/powerpc-isa205-ppr-dscr-vsx64l.dat: Generate.
	* ppc-linux-nat.c: Include <sys/uio.h>.
	(fetch_regset, store_regset, check_regset): New functions.
	(fetch_register, fetch_ppc_registers): Call fetch_regset with
	DSCR and PPR regsets.
	(store_register, store_ppc_registers): Call store_regset with
	DSCR and PPR regsets.
	(ppc_linux_get_hwcap2): New function.
	(ppc_linux_nat_target::read_description): Call
	ppc_linux_get_hwcap2 and check_regset, set ppr_dscr field in the
	features struct if needed.
	* ppc-linux-tdep.c: Include
	features/rs6000/powerpc-isa205-ppr-dscr-vsx32l.c and
	features/rs6000/powerpc-isa205-ppr-dscr-vsx64l.c.
	(ppc32_regmap_ppr, ppc32_regmap_dscr, ppc32_linux_pprregset)
	(ppc32_linux_dscrregset): New globals.
	(ppc_linux_iterate_over_regset_sections): Call back with the ppr
	and dscr regsets.
	(ppc_linux_core_read_description): Check if the ppr and dscr
	sections are present and set ppr_dscr in the features struct.
	(_initialize_ppc_linux_tdep): Call
	initialize_tdesc_powerpc_isa205_ppr_dscr_vsx32l and
	initialize_tdesc_powerpc_isa205_ppr_dscr_vsx64l.
	* ppc-linux-tdep.h (ppc32_linux_pprregset)
	(ppc32_linux_dscrregset): Declare.
	* ppc-tdep.h (struct gdbarch_tdep) <ppc_ppr_regnum>: New field.
	<ppc_dscr_regnum>: New field.
	(enum) <PPC_PPR_REGNUM, PPC_DSCR_REGNUM>: New enum values.
	* rs6000-tdep.c (rs6000_gdbarch_init): Look for and validate ppr
	and dscr features.
	(ppc_process_record_op31): Record changes to PPR and DSCR.

gdb/gdbserver/ChangeLog:
2018-10-26  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
	    Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* configure.srv (ipa_ppc_linux_regobj): Add
	powerpc-isa205-ppr-dscr-vsx32l-ipa.o and
	powerpc-isa205-ppr-dscr-vsx64l-ipa.o.
	(powerpc*-*-linux*): Add powerpc-isa205-ppr-dscr-vsx32l.o and
	powerpc-isa205-ppr-dscr-vsx64l.o to srv_regobj, add
	rs6000/power-dscr.xml, rs6000/power-ppr.xml,
	rs6000/powerpc-isa205-ppr-dscr-vsx32l.xml and
	rs6000/powerpc-isa205-ppr-dscr-vsx64l.xml to srv_xmlfiles.
	* linux-ppc-tdesc-init.h (enum ppc_linux_tdesc)
	<PPC_TDESC_ISA205_PPR_DSCR_VSX>: New enum value.
	(init_registers_powerpc_isa205_ppr_dscr_vsx32l)
	(init_registers_powerpc_isa205_ppr_dscr_vsx64l): Declare.
	* linux-ppc-low.c: Include "elf/common.h" and <sys/uio.h>.
	(ppc_hwcap): Add comment.
	(ppc_hwcap2): New global.
	(ppc_check_regset, ppc_fill_pprregset, ppc_store_pprregset)
	(ppc_fill_dscrregset, ppc_store_dscrregset): New functions.
	(ppc_regsets): Add entries for the DSCR and PPR regsets.
	(ppc_arch_setup): Get AT_HWCAP2.  Set ppr_dscr in features struct
	when needed.  Set sizes for the the DSCR and PPR regsets.
	(ppc_get_ipa_tdesc_idx): Return PPC_TDESC_ISA205_PPR_DSCR_VSX.
	(initialize_low_arch): Call
	init_registers_powerpc_isa205_ppr_dscr_vsx32l and
	init_registers_powerpc_isa205_ppr_dscr_vsx64l.
	* linux-ppc-ipa.c (get_ipa_tdesc): Handle
	PPC_TDESC_ISA205_PPR_DSCR_VSX.
	(initialize_low_tracepoint): Call
	init_registers_powerpc_isa205_ppr_dscr_vsx32l and
	init_registers_powerpc_isa205_ppr_dscr_vsx64l.

gdb/testsuite/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.arch/powerpc-ppr-dscr.c: New file.
	* gdb.arch/powerpc-ppr-dscr.exp: New file.

gdb/doc/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* gdb.texinfo (PowerPC Features): Describe new features
	"org.gnu.gdb.power.ppr" and "org.gnu.gdb.power.dscr".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Refactor have_ initializers in rs6000-tdep.c
@ 2018-10-26 19:41 sergiodj+buildbot
  2018-10-27  0:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 19:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93b4691f0fe1f8249de3c3f9d2e271cb0ba3254e ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 93b4691f0fe1f8249de3c3f9d2e271cb0ba3254e

[PowerPC] Refactor have_ initializers in rs6000-tdep.c

This patch refactors a series of initializers in rs6000_gdbarch_init
for clarity.  The have_fpu initializer is also changed to set the
variable to 0, like the other similar variables.  This doesn't affect
program behavior.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* rs6000-tdep.c (rs6000_gdbarch_init): Replace line wrapping by a
	second initializer line for the have_* variables.  Initialize
	have_fpu to 0 instead of 1.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Fix indentation in arch/ppc-linux-common.c
@ 2018-10-26 19:41 sergiodj+buildbot
  2018-10-26 23:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 19:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71733a7bf696fd54b1c75a2c9c16fd61819c0ddb ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 71733a7bf696fd54b1c75a2c9c16fd61819c0ddb

[PowerPC] Fix indentation in arch/ppc-linux-common.c

This patch parenthesizes the tdesc selection expressions in
arch/ppc-linux-common.c so that they can be tab-indented.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* arch/ppc-linux-common.c (ppc_linux_match_description):
	Parenthesize tdesc assignements and indent them properly.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Fix two if statements in gdb/ppc-linux-nat.c
@ 2018-10-26 19:07 sergiodj+buildbot
  2018-10-26 22:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d907528ca584b522125ce4ac818f45dfe7a9a24 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 3d907528ca584b522125ce4ac818f45dfe7a9a24

[PowerPC] Fix two if statements in gdb/ppc-linux-nat.c

This patch changes two if statements to else if statements in
ppc-linux-nat.c:fetch_register for clarity.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* ppc-linux-nat.c (fetch_register): Change if statement to else
	if.
	(store_register): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Remove rs6000_pseudo_register_reggroup_p
@ 2018-10-26 18:45 sergiodj+buildbot
  2018-10-26 20:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 18:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 500f01a0e2f79d64cc08011ad70c6ffa1e1c7694 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 500f01a0e2f79d64cc08011ad70c6ffa1e1c7694

[PowerPC] Remove rs6000_pseudo_register_reggroup_p

This patch removes rs6000_pseudo_register_reggroup_p.

Group membership for the pseudoregisters can be detected through their
types in default_register_reggroup_p through
tdesc_register_reggroup_p.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* rs6000-tdep.c: Remove reggroups.h include.
	(rs6000_pseudo_register_reggroup_p): Remove.
	(rs6000_gdbarch_init): Remove call to
	set_tdesc_pseudo_register_reggroup_p.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add decfloat registers to float reggroup
@ 2018-10-26 18:31 sergiodj+buildbot
  2018-10-26 19:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ed29001c4a965520f6a243ec7ad41c156f96a20 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 7ed29001c4a965520f6a243ec7ad41c156f96a20

Add decfloat registers to float reggroup

This patch changes default_register_reggroup_p to return true when the
register type is decimal floating point and the reggroup is
float_reggroup.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* reggroups.c (default_register_reggroup_p): Return true for
	decfloat registers and float_reggroup.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Don't zero-initialize vector register buffers
@ 2018-10-26 17:52 sergiodj+buildbot
  2018-10-26 18:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c849b222b154cd5f481fee9d6f3971bd2eeddc2 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 5c849b222b154cd5f481fee9d6f3971bd2eeddc2

[PowerPC] Don't zero-initialize vector register buffers

Now that linux-tdep.c already zero-initializes the buffer used for
generating core file notes, there is no need to do this in the linux
collect functions for the vector regset.  The memsets in gdbserver were
not useful to begin with.

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* ppc-linux-tdep.c (ppc_linux_collect_vrregset): Remove.
	(ppc32_le_linux_vrregset, ppc32_be_linux_vrregset): Replace
	ppc_linux_collect_vrregset by regcache_collect_regset.

gdb/gdbserver/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* linux-ppc-low.c (ppc_fill_vrregset): Remove memset calls.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Zero-initialize linux note sections
@ 2018-10-26 17:28 sergiodj+buildbot
  2018-10-26 17:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT afde3032dde478a2bbb2e0c4b0cb4256b27eb949 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: afde3032dde478a2bbb2e0c4b0cb4256b27eb949

Zero-initialize linux note sections

This patches changes linux-tdep.c so that the buffer used to write
note sections when generating a core file is zero-initialized.  This
way, bytes that are not collected won't contain random
data (e.g. padding bytes).

gdb/ChangeLog:
2018-10-26  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* linux-tdep.c (linux_collect_regset_section_cb): Use
	std::vector<gdb_byte> instead of char * and malloc for buf.
	Remove xfree.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix SYMBOL_LANGUAGE assertion failure on AIX.
@ 2018-10-26 12:40 sergiodj+buildbot
  2018-10-26 16:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 12:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b971899198607b844f5a37e39dc561766c3b331a ***

Author: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Branch: master
Commit: b971899198607b844f5a37e39dc561766c3b331a

Fix SYMBOL_LANGUAGE assertion failure on AIX.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Remove redundant code, and catch more errors when accessing MISA
@ 2018-10-26 11:01 sergiodj+buildbot
  2018-10-26 11:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-26 11:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b0eff8b1d8b4fe51ad3a14f60816f98bc0e963a ***

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

gdb/riscv: Remove redundant code, and catch more errors when accessing MISA

When reading the MISA register, the RISC-V specification says that, if
MISA can't be found then a default value of 0 should be assumed.

As such, this patch ensures that GDB ignores errors when accessing
both the new and old locations for the MISA register.

Additionally, this patch removes an unneeded flag parameter which
didn't provide any additional functionality beyond checking the MISA
for the default value of 0.

gdb/ChangeLog:

	* riscv-tdep.c (riscv_read_misa_reg): Update comment, remove
	READ_P parameter, catch and ignore register access errors from
	either the old or new MISA location.
	(riscv_has_feature): Update call to riscv_read_misa_reg.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/python: Make convert_values_to_python return gdbpy_ref<>
@ 2018-10-25 16:08 sergiodj+buildbot
  2018-10-25 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-25 16:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b352ceb6b4fc9f026944d307704076d1e6894de9 ***

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

gdb/python: Make convert_values_to_python return gdbpy_ref<>

Make convert_values_to_python return a gdbpy_ref<> directly rather
than building a gdbpy_ref<>, releasing it, and then having a new
gdbpy_ref<> created to hold the result.

I also added a header comment to convert_values_to_python.

gdb/ChangeLog:

	* python/py-function.c (convert_values_to_python): Return
	gdbpy_ref<>. Add header comment.
	(fnpy_call): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Rewrite valgrind-db-attach.exp to use vgdb
@ 2018-10-25 15:12 sergiodj+buildbot
  2018-10-25 18:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-25 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfcc0eba9e66f3793feecc059f80e97d03dbdbef ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: bfcc0eba9e66f3793feecc059f80e97d03dbdbef

[gdb/testsuite] Rewrite valgrind-db-attach.exp to use vgdb

The valgrind option --db-attach has been deprecated in version 3.10.0, and
removed in version 3.11.0, so the valgrind-db-attach.exp testcase is
unsupported starting version 3.11.0.

Rewrite the test-case to use vgdb instead (making it supported starting
version 3.7.0).

Tested on x86_64-linux with and without --target_board=native-gdbserver.

2018-10-25  Tom de Vries  <tdevries@suse.de>

	* gdb.base/valgrind-db-attach.exp: Rewrite to use vgdb.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/python: Make cmdpy_completer_helper return gdbpy_ref<>
@ 2018-10-25 12:19 sergiodj+buildbot
  2018-10-25 15:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-25 12:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50db9ef4c014d28dd64b2d660b043a40224a1a27 ***

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

gdb/python: Make cmdpy_completer_helper return gdbpy_ref<>

Make cmdpy_completer_helper return a gdbpy_ref<> directly rather than
building a gdbpy_ref<>, releasing it, and then having a new
gdbpy_ref<> created to hold the result.

gdb/ChangeLog:

	* python/py-cmd.c (cmdpy_completer_helper): Return gdbpy_ref<>.
	(cmdpy_completer_handle_brkchars): Adjust.
	(cmdpy_completer): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Use correct regnum in riscv_linux_nat_target::fetch_registers
@ 2018-10-25 11:43 sergiodj+buildbot
  2018-10-25 14:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-25 11:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ee67fd7f3f6ca78eede2862e309c0bcf266bbd7e ***

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

gdb/riscv: Use correct regnum in riscv_linux_nat_target::fetch_registers

In riscv_linux_nat_target::fetch_registers, if we are asked to supply
all registers (regnum parameter is -1), then we currently end up
calling regcache::raw_supply_zeroed with the regnum -1, which is
invalid.  Instead we should be passing the regnum of the specific
register we wish to supply zeroed, in this case RISCV_CSR_MISA_REGNUM.

I removed the extra { ... } block in line with the coding standard
while editing this area.

gdb/ChangeLog:

	* riscv-linux-nat.c (riscv_linux_nat_target::fetch_registers):
	Pass correct regnum to raw_supply_zeroed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ELF: Hide symbols defined in discarded input sections
@ 2018-10-25  2:40 sergiodj+buildbot
  2018-10-25  3:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-25  2:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a640d719684f25bdb88ae60148c6978e6131701 ***

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

ELF: Hide symbols defined in discarded input sections

When assigning symbol version, we should hide debug symbols defined in
discarded sections from IR objects so that they can be removed later.

bfd/

	PR ld/23818
	* elflink.c (_bfd_elf_link_assign_sym_version): Hide symbols
	defined in discarded input sections.

ld/

	PR ld/23818
	* testsuite/ld-plugin/lto.exp: Run PR ld/23818 test.
	* testsuite/ld-plugin/pr23818.d: New file.
	* testsuite/ld-plugin/pr23818.t: Likewise.
	* testsuite/ld-plugin/pr23818a.c: Likewise.
	* testsuite/ld-plugin/pr23818b.c: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Log wait status on process no longer exists error
@ 2018-10-24 17:35 sergiodj+buildbot
  2018-10-24 16:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-24 17:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe1a5cad302b5535030cdf62895e79512713d738 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: fe1a5cad302b5535030cdf62895e79512713d738

[gdb/testsuite] Log wait status on process no longer exists error

Proc gdb_test_multiple can run into a process no longer exists error, but when
that happens it shows no details about the process:
...
ERROR: Process no longer exists
...

Fix this by showing the wait status of the process in the log:
...
ERROR: GDB process no longer exists
GDB process exited with wait status 8106 exp8 0 0 CHILDKILLED SIGSEGV \
  {segmentation violation}
...

In order to run the wait commmand we need an explicit pid, so we can't use
any_spawn_id, and duplicate the "-i any_spawn_id eof" pattern for gdb_spawn_id,
and add the wait status logging there.

Build and tested on x86_64-linux.

2018-10-24  Tom de Vries  <tdevries@suse.de>

	* lib/gdb.exp (gdb_test_multiple): Log wait status on process no
	longer exists error.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] cmse_scan segfault
@ 2018-10-24 15:12 sergiodj+buildbot
  2018-10-24 16:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-24 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c246a60c08d82066b16973bcd622e671300eb02 ***

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

cmse_scan segfault

elf_sym_hashes for as-needed libs will be zeroed if the library is
found to be not needed.  More than that, the local symbols for such a
library should not be considered by cmse_scan.

	* elf32-arm.c (elf32_arm_size_stubs): Ignore as-needed libs that
	were not needed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Rewrite catch-follow-exec.exp using gdb_test
@ 2018-10-24 13:40 sergiodj+buildbot
  2018-10-24 16:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-24 13:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a76dc3b7705c5c85efc00521ebfac49e80c3fedf ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: a76dc3b7705c5c85efc00521ebfac49e80c3fedf

[gdb/testsuite]	Rewrite catch-follow-exec.exp using gdb_test

The testcase catch-follow-exec.exp is written use gdb -batch in order to avoid
a GDB SIGTTOU.  After the commit of "Avoid GDB SIGTTOU on catch exec + set
follow-exec-mode new (PR 23368)", that no longer is necessary.

Rewrite the test using regular gdb_test commands.

Tested with x86_64-linux.

2018-10-24  Tom de Vries  <tdevries@suse.de>

	* gdb.base/catch-follow-exec.exp: Rewrite using gdb_test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Handle removed valgrind option --db-attach
@ 2018-10-24 13:14 sergiodj+buildbot
  2018-10-24 13:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-24 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4df46df7a4643c0f6f93a2739c4b7bc0e83bcdce ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 4df46df7a4643c0f6f93a2739c4b7bc0e83bcdce

[gdb/testsuite] Handle removed valgrind option --db-attach

When running valgrind-db-attach.exp with valgrind version 3.13.0, we get:
...
PASS: gdb.base/valgrind-db-attach.exp: spawn valgrind
valgrind: Unknown option: --db-attach=yes
valgrind: Use --help for more information or consult the user manual.
ERROR: Process no longer exists
UNRESOLVED: gdb.base/valgrind-db-attach.exp: valgrind started
...

The valgrind option --db-attach has been deprecated in version 3.10.0, and
removed in version 3.11.0.

Fix valgrind-db-attach.exp to replace the ERROR/UNRESOLVED with:
...
UNSUPPORTED: gdb.base/valgrind-db-attach.exp: valgrind started
...

Tested on x86_64-linux.

2018-10-24  Tom de Vries  <tdevries@suse.de>

	* gdb.base/valgrind-db-attach.exp: Handle removed support for
	--db-attach in valgrind.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid GDB SIGTTOU on catch exec + set follow-exec-mode new (PR 23368)
@ 2018-10-23 22:01 sergiodj+buildbot
  2018-10-24  2:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35ed81d4f45855b98ea0c517b396662c3ae2a8c5 ***

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

Avoid GDB SIGTTOU on catch exec + set follow-exec-mode new (PR 23368)

Here's a summary of PR 23368:

  #include <unistd.h>
  int main (void)
  {
    char *exec_args[] = { "/bin/ls", NULL };
    execve (exec_args[0], exec_args, NULL);
  }

$ gdb -nx t -ex "catch exec" -ex "set follow-exec-mode new" -ex run
...
[1]  + 13146 suspended (tty output)  gdb -q -nx t -ex "catch exec" -ex "set follow-exec-mode new" -ex run
$

Here's what happens: when the inferior execs with "follow-exec-mode
new", we first "mourn" it before creating the new one.  This ends up
calling inflow_inferior_exit, which sets the per-inferior terminal state
to "is_ours":

  inf->terminal_state = target_terminal_state::is_ours;

At this point, the inferior's terminal_state is is_ours, while the
"reality", tracked by gdb_tty_state, is is_inferior (GDB doesn't own the
terminal).

Later, we continue processing the exec inferior event and decide we want
to stop (because of the "catch exec") and call target_terminal::ours to
make sure we own the terminal.  However, we don't actually go to the
target backend to change the settings, because the core thinks that no
inferior owns the terminal (inf->terminal_state is
target_terminal_state::is_ours, as checked in
target_terminal_is_ours_kind, for both inferiors).  When something in
readline tries to mess with the terminal settings, it generates a
SIGTTOU.

This patch fixes this by tranferring the state of the terminal from the
old inferior to the new inferior.

gdb/ChangeLog:

	PR gdb/23368
	* infrun.c (follow_exec): In the follow_exec_mode_new case,
	transfer terminal state from old new new inferior.
	* terminal.h (swap_terminal_info): New function.
	* inflow.c (swap_terminal_info): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix use-after-free in record_btrace_start_replaying
@ 2018-10-23 21:06 sergiodj+buildbot
  2018-10-24  0:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 21:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79b8d3b090bcbfbcffa8bdd195476c6db172273b ***

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

Fix use-after-free in record_btrace_start_replaying

-fsanitize=address showed a use-after-free in
record_btrace_start_replaying.  The bug occurred because
get_thread_current_frame returned a frame_info, but this object was
then invalidated before the return by ~scoped_restore_current_thread.

This patch fixes the problem by renaming get_thread_current_frame and
having it return a frame id.

gdb/ChangeLog
2018-10-23  Tom Tromey  <tom@tromey.com>

	* record-btrace.c (get_thread_current_frame_id): Rename from
	get_thread_current_frame.  Return a frame_id.
	(record_btrace_start_replaying): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S/390: Support vector alignment hints
@ 2018-10-23 16:56 sergiodj+buildbot
  2018-10-24  0:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f47998d69f8d290564c022b010e63d5886a1fd7d ***

Author: Andreas Krebbel <krebbel@linux.ibm.com>
Branch: master
Commit: f47998d69f8d290564c022b010e63d5886a1fd7d

S/390: Support vector alignment hints

This patch adds the vector alignment hints to the vector load and
store instructions as documented in the IBM z14 Principles of
Operations manual:

http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr011.pdf

opcodes/ChangeLog:

2018-10-23  Andreas Krebbel  <krebbel@linux.ibm.com>

	* s390-opc.txt: Add vector load/store instructions with additional
	alignment parameter.

gas/ChangeLog:

2018-10-23  Andreas Krebbel  <krebbel@linux.ibm.com>

	* config/tc-s390.c (md_gather_operands): Fix for optional operands
	following memory addresses.
	* testsuite/gas/s390/zarch-arch12.d: Add regexp checks for new
	instruction variants.
	* testsuite/gas/s390/zarch-arch12.s: Emit new instruction
	variants.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB:  New target s12z
@ 2018-10-23 15:59 sergiodj+buildbot
  2018-10-23 22:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51d21d60b37f1e1a0aa6fd1f5439b22591fa6d5f ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 51d21d60b37f1e1a0aa6fd1f5439b22591fa6d5f

GDB:  New target s12z

gdb/
    * configure.tgt: Add configuration for s12z.
    * s12z-tdep.c:  New file.
    * NEWS: Mention new target.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB: Remote target can now accept the form unix::/path/to/socket.
@ 2018-10-23 15:43 sergiodj+buildbot
  2018-10-23 21:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 15:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88f5cc8cf8606478832c7d0d7b74755f3f625015 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 88f5cc8cf8606478832c7d0d7b74755f3f625015

GDB: Remote target can now accept the form unix::/path/to/socket.

Allow target remote to use the unix::/path/to/socket syntax as well as just
plain /path/to/socket

gdb/

  * ser-uds.c (uds_open): Use parse_connection_spec to deal with the
    comm form unix::/path/to/socket.

  * serial.c (serial_open): Consider the "unix:" prefix when deciding which
    interface to use.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested.
@ 2018-10-23 15:10 sergiodj+buildbot
  2018-10-23 20:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 15:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f19c7ff839d7a32ebb48482ae7d318fb46ca823d ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: f19c7ff839d7a32ebb48482ae7d318fb46ca823d

GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested.

When invoking gdbserver, if the COMM parameter takes the form "unix::/path/name"
then a local (unix) domain socket will be created with that name and gdbserver
will listen for connections on that.

    gdb/
    * NEWS: Mention new feature.

    gdb/gdbserver/
    * configure.ac (AC_CHECK_HEADERS): Add sys/un.h.
    * configure: Regenerate.
    * remote-utils.c (remote_prepare): Create a local socket if requested.
     (remote_open):  Don't attempt to open a file if it's a socket.
     (handle_accept_event): Display the name of the socket on connection.

   gdb/common/
   * netstuff.c (parse_connection_spec)[prefixes]: New member for local domain sockets.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23806, NULL pointer dereference in merge_strings
@ 2018-10-23 11:46 sergiodj+buildbot
  2018-10-23 16:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45a0eaf77022963d639d6d19871dbab7b79703fc ***

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

PR23806, NULL pointer dereference in merge_strings

	PR 23806
	* merge.c (_bfd_add_merge_section): Don't attempt to merge
	sections with ridiculously large alignments.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23805, NULL pointer dereference in elf_link_input_bfd
@ 2018-10-23 11:28 sergiodj+buildbot
  2018-10-23 15:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 102def4da826b3d9e169741421e5e67e8731909a ***

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

PR23805, NULL pointer dereference in elf_link_input_bfd

	PR 23805
	* elflink.c (elf_link_input_bfd): Don't segfault on finding
	STT_TLS symbols without any TLS sections.  Instead, change the
	symbol type to STT_NOTYPE.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: expect h/w watchpoints to trigger before the memory is written
@ 2018-10-23 10:54 sergiodj+buildbot
  2018-10-23 12:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 10:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a77b1b49f49cc5cfdb30727d8fc1bf456cad429 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 5a77b1b49f49cc5cfdb30727d8fc1bf456cad429

gdb/riscv: expect h/w watchpoints to trigger before the memory is written

When using QEMU as a RISCV simulator, hardware watchpoint events are
reported to GDB before the target memory gets written. GDB currently
expects the event to be reported after it is written. As a result of
this mismatch, upon receiving the event, GDB sees that the target
memory region has not changed, and therefore decides to ignore the
event. It therefore resumes the program's execution with a continue,
which is the start of an infinite loop between QEMU repeatedly
reporting the same watchpoint event over and over, and GDB repeatedly
ignoring it.

This patch fixes the issue by telling GDB to expect the watchpoint
event to be reported ahead of the memory region being modified.
Upon receiving the event, GDB then single-steps the program before
checking the watched memory value.

gdb/ChangeLog:

        * riscv-tdep.c (riscv_gdbarch_init): Set the gdbarch's
        have_nonsteppable_watchpoint attribute to 1.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Fix register access for register aliases
@ 2018-10-23 10:49 sergiodj+buildbot
  2018-10-23 11:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-23 10:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0dbfcfffe9abbc5198bce95eb8c66b6bc9b364be ***

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

gdb/riscv: Fix register access for register aliases

Some confusion over how the register names and aliases are setup in
riscv means that we currently can't access registers through their
architectural name.

This commit fixes this issue, and moves some of the csr register
handling out of the alias handling code and deals with it separately.
This has the benefit that we can now directly access some arrays
rather than having to iterate over them.

A new test is added to ensure that register aliases now work
correctly.

gdb/ChangeLog:

	* riscv-tdep.c (riscv_gdb_reg_names): Update comment, and all
	register names.
	(struct register_alias): Rename to...
	(struct riscv_register_alias): ...this, and update comment.
	(riscv_register_aliases): Update type, and alias names.  Remove
	CSR names from this list.
	(riscv_register_name): Use riscv_gdb_reg_names for int and float
	register names.  Add an extra assertion.
	(riscv_is_regnum_a_named_csr): New function.
	(riscv_register_reggroup_p): Use riscv_is_regnum_a_named_csr.

gdb/testsuite/ChangeLog:

	* gdb.arch/riscv-reg-aliases.c: New file.
	* gdb.arch/riscv-reg-aliases.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: NaN-box FP values smaller than an FP register.
@ 2018-10-22 22:02 sergiodj+buildbot
  2018-10-22 23:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-22 22:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3399f1b3030c3419859f1230bc66a981154d176d ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 3399f1b3030c3419859f1230bc66a981154d176d

RISC-V: NaN-box FP values smaller than an FP register.

The hardware requires that values in FP registers be NaN-boxed, so we must
extend them with 1's instead of 0's as we do for integer values.

	gdb/
	* riscv-tdep.c (riscv_push_dummy_call) <in_reg>: Check for value in
	FP reg smaller than FP reg size, and fill with -1 instead of 0.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Print FP regs as union of float types.
@ 2018-10-22 22:01 sergiodj+buildbot
  2018-10-22 22:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-22 22:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 270b9329b713fdc166f95dfa3a0a2f72f3a49608 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 270b9329b713fdc166f95dfa3a0a2f72f3a49608

RISC-V: Print FP regs as union of float types.

A 64-bit FP register can hold either a single or double float value, so
print it as both types by using a union type for FP registers.  Likewise
for 128-bit regs which can also hold long double.

	gdb/
	* riscv-tdep.c (riscv_fpreg_d_type, riscv_fpreg_q_type): New.
	(riscv_register_type): Use them.
	(riscv_print_one_register_info): Handle union of floats same as float.
	* riscv-tdep.h (struct gdbarch_tdep): Add riscv_fpreg_d_type and
	riscv_fpreg_q_type fields.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Disassembly: Fallback to show the address if the symbol table is empty.
@ 2018-10-22 19:45 sergiodj+buildbot
  2018-10-22 20:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-22 19:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 192c2bfbd7a6d4b2069f6b94b020d274a483c198 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 192c2bfbd7a6d4b2069f6b94b020d274a483c198

S12Z: Disassembly: Fallback to show the address if the symbol table is empty.

* opcodes/s12z-dis.c (decode_possible_symbol): Add fallback case.
  (rel_15_7): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allocate buffer with proper size in amd64_pseudo_register_{read_value, write}
@ 2018-10-22  2:44 sergiodj+buildbot
  2018-10-22  3:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-22  2:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 925047fed0d6ab86e6fe86d3e22e1aa9dde7b3eb ***

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

Allocate buffer with proper size in amd64_pseudo_register_{read_value,write}

Running "maintenance selftest" on an amd64 build with AddressSanitizer
enabled, I get this:

==18126==ERROR: AddressSanitizer: dynamic-stack-buffer-overflow on address 0x7ffdf72397c1 at pc 0x7fb5f437b011 bp 0x7ffdf7239740 sp 0x7ffdf7238ee8
WRITE of size 8 at 0x7ffdf72397c1 thread T0
    #0 0x7fb5f437b010 in __interceptor_memcpy /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:737
    #1 0x55a1f899c1b3 in readable_regcache::raw_read(int, unsigned char*) /home/simark/src/binutils-gdb/gdb/regcache.c:530
    #2 0x55a1f7db241b in amd64_pseudo_register_read_value /home/simark/src/binutils-gdb/gdb/amd64-tdep.c:384
    #3 0x55a1f8413a2e in gdbarch_pseudo_register_read_value(gdbarch*, readable_regcache*, int) /home/simark/src/binutils-gdb/gdb/gdbarch.c:1992
    #4 0x55a1f899c9d1 in readable_regcache::cooked_read(int, unsigned char*) /home/simark/src/binutils-gdb/gdb/regcache.c:636
    #5 0x55a1f89a2251 in cooked_read_test /home/simark/src/binutils-gdb/gdb/regcache.c:1649

In amd64_pseudo_register_read_value, when we try to read the al
register, for example, we need to read rax and extract al from it.  We
allocate a buffer of the size of al (1 byte):

  gdb_byte *raw_buf = (gdb_byte *) alloca (register_size (gdbarch, regnum));

but read in it the whole rax value (8 bytes):

  status = regcache->raw_read (gpnum, raw_buf);

Fix it by allocating a buffer correctly sized for the full register from
which the smaller register is extracted.  The
amd64_pseudo_register_write function had the same problem.

gdb/ChangeLog:

	* amd64-tdep.c (amd64_pseudo_register_read_value): Use
	correctly-sized buffer with raw_read.
	(amd64_pseudo_register_write): Use correctly-sized buffer for
	raw_read/raw_write.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PUSHED/OBVIOUS] ensure help set print type gives the correct help.
@ 2018-10-20 21:54 sergiodj+buildbot
  2018-10-20 23:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-20 21:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4051d2d65a73f02cfd2baebf8803fe2880dbd76c ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 4051d2d65a73f02cfd2baebf8803fe2880dbd76c

[PUSHED/OBVIOUS] ensure help set print type gives the correct help.

Without this patch:
  (gdb) help set print type
  Generic command for setting how types print.

  List of show print type subcommands:

  show print type methods -- Set printing of methods defined in classes
  ...

With this patch:
  (gdb) h set print type
  Generic command for setting how types print.

  List of set print type subcommands:

  set print type methods -- Set printing of methods defined in classes
  ...


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23788, objcopy: failed to find link section
@ 2018-10-20  9:57 sergiodj+buildbot
  2018-10-20 11:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-20  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac85e67c053f1555def2c111962f4e68740794f9 ***

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

PR23788, objcopy: failed to find link section

Symbol tables can change when a number of objcopy options are used.
I figure string tables are similarly changeable.

	PR 23788
	* elf.c (section_match): Don't require a size match for SHT_SYMTAB
	or SHT_STRTAB.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Minor cleanups in tui-io.c
@ 2018-10-20  0:14 sergiodj+buildbot
  2018-10-20  0:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-20  0:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 84371624ada07e6f107ee14c48a609466055fe0d ***

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

Minor cleanups in tui-io.c

I noticed that a couple of functions in tui-io.c could be static, and
that a couple more were unused and could be removed.

gdb/ChangeLog
2018-10-19  Tom Tromey  <tom@tromey.com>

	* tui/tui-io.h (key_is_start_sequence, key_is_end_sequence)
	(key_is_backspace, tui_getc): Don't declare.
	* tui/tui-io.c (key_is_start_sequence): Now static.
	(key_is_end_sequence, key_is_backspace): Remove.
	(tui_getc): Now static.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Clear static_links in reread_symbols
@ 2018-10-19 19:31 sergiodj+buildbot
  2018-10-19 19:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-19 19:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22ad8107d35d833db000e5a5050c0f53af7af51f ***

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

Clear static_links in reread_symbols

-fsanitize=address pointed out a use-after free in
objfile_register_static_link.  The bug turned out to be that
reread_symbols does not clear the static_links field; this leaves a
hash table that is filled with freed pointers.

Jan's (now quite old) idea of replacing reread_symbols with a simple
delete/new still seems good to me, and it's worth noting that it would
have avoided this bug.

Tested by the buildbot and by observing the change with
-fsanitize=address.

gdb/ChangeLog
2018-10-19  Tom Tromey  <tom@tromey.com>

	* symfile.c (reread_symbols): Clear "static_links".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S390: Fix crash when remote tdesc doesn't define vec128
@ 2018-10-19 17:09 sergiodj+buildbot
  2018-10-19 17:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-19 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0667c506823489f2fab1938d3fc8ee27f8a7c651 ***

Author: Andreas Arnez <arnez@linux.ibm.com>
Branch: master
Commit: 0667c506823489f2fab1938d3fc8ee27f8a7c651

S390: Fix crash when remote tdesc doesn't define vec128

I've encountered a GDB crash when trying to read registers from a remote
stub that provided a target.xml with vector registers, but without the
'vec128' data type.  The crash is caused by NULL register type entries for
the "concatenated" pseudo-registers v0-v15.  These NULL entries are
introduced by the logic in s390_pseudo_register_type(), where the tdesc
type 'vec128' is returned unconditionally -- even if it doesn't exist (is
NULL).

The fixed logic for determining a "concatenated" vector register's type
now returns the type of the raw register v16 instead.  This also makes
sure that all vector register have the same type.

gdb/ChangeLog:

	* s390-tdep.c (s390_pseudo_register_type): For v0-v15 don't yield
	the possibly non-existent tdesc type 'vec128', but the type of raw
	register v16 instead.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64: Better termination checks for sigcontext reading
@ 2018-10-19 13:10 sergiodj+buildbot
  2018-10-19 19:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-19 13:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74b3c713184abb8e07f92c4e069ebafde78c0a0e ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 74b3c713184abb8e07f92c4e069ebafde78c0a0e

Aarch64: Better termination checks for sigcontext reading

When reading the reserved section in the sigcontext ensure the
address is updated on an unknown section. Also add additional
checks to prevent reading past the end of the array.

Fixes gdb.base/savedregs.exp

	* aarch64-linux-tdep.c (AARCH64_SIGCONTEXT_RESERVED_SIZE): New
	define.
	(aarch64_linux_sigframe_init): Extra boundary checks.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Testsuite: vla-optimized-out.exp is too pessimistic
@ 2018-10-19 11:35 sergiodj+buildbot
  2018-10-19 13:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-19 11:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c6ac8d7ce6e018168c17b11d978b25dba721554 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 2c6ac8d7ce6e018168c17b11d978b25dba721554

Testsuite: vla-optimized-out.exp is too pessimistic

On aarch64 (and possibly other ports), for O3 the sizeof "a" can still be shown.

2018-10-19  Alan Hayward  <alan.hayward@arm.com>

	* gdb.base/vla-optimized-out.exp: Allow either optimized out or 6.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Testsuite: compile-cplus-print.exp: Start inferior before compiling
@ 2018-10-19 10:47 sergiodj+buildbot
  2018-10-19 11:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-19 10:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f1ae3a34faf8217bd253fa12b4d0abaaa42c2d2 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 1f1ae3a34faf8217bd253fa12b4d0abaaa42c2d2

Testsuite: compile-cplus-print.exp: Start inferior before compiling

skip_compile_feature_tests is only valid if the inferior has already
been started (see proc comments). Move the runto_main earlier.

2018-10-18  Alan Hayward  <alan.hayward@arm.com>

	* gdb.compile/compile-cplus-print.exp: Start inferior earlier.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Arm: Fix disassembler crashing on -b binary when thumb file and thumb not forced.
@ 2018-10-19 10:22 sergiodj+buildbot
  2018-10-19 10:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-19 10:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b347048e7e33070212a408dc2371075ee60b556 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 0b347048e7e33070212a408dc2371075ee60b556

Arm: Fix disassembler crashing on -b binary when thumb file and thumb not forced.

The disassembler for Arm has some aborts in it in places it assumes can never
be reached.  Under normal circumstances they indeed cannot be reached because
the right options are selected from the ARM attributes in the ELF file.

However when disassembling with -b binary then if you do not get the options
right the disassembler just aborts.  This changes it so it just prints how it
was trying to interpret the instruction and prints UNKNOWN instructions next to it.

This way the user has an idea of what's going.

gas/ChangeLog:

	* testsuite/gas/arm/undefined-insn-arm.d: New test.
	* testsuite/gas/arm/undefined-insn-thumb.d: New test.
	* testsuite/gas/arm/undefined-insn.s: New test.

opcodes/ChangeLog:

	* arm-dis.c (UNKNOWN_INSTRUCTION_32BIT): Format specifier for arm mode.
	(UNKNOWN_INSTRUCTION_16BIT): Format specifier for thumb mode.
	(print_insn_arm, print_insn_thumb16, print_insn_thumb32): Use them.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/ChangeLog:
@ 2018-10-18  0:19 sergiodj+buildbot
  2018-10-18  1:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-18  0:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 89eb3c547018af6a41ce9b3614cc2ab9a679168b ***

Author: Paul Koning <paul_koning@dell.com>
Branch: master
Commit: 89eb3c547018af6a41ce9b3614cc2ab9a679168b

gdb/ChangeLog:

        * charset.c (convert_between_encodings): Fix unsigned overflow.

    gdb/charset.c (convert_between_encodings): Fix unsigned overflow.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Share the code to format "info proc mappings" entries for FreeBSD.
@ 2018-10-17 19:13 sergiodj+buildbot
  2018-10-17 23:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-17 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f3b1098e820cef84709ef71c287c4b72e6c671b ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 6f3b1098e820cef84709ef71c287c4b72e6c671b

Share the code to format "info proc mappings" entries for FreeBSD.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_nat_target::info_proc) Use
	fbsd_info_proc_mappings_header and fbsd_info_proc_mappings_entry.
	* fbsd-tdep.c (fbsd_vm_map_entry_flags): Mark static.
	(fbsd_info_proc_mappings_header, fbsd_info_proc_mappings_entry):
	New functions.
	(fbsd_core_info_proc_mappings): Use fbsd_info_proc_mappings_header
	and fbsd_info_proc_mappings_header.
	* fbsd-tdep.h (fbsd_vm_map_entry_flags): Remove.
	(fbsd_info_proc_mappings_header, fbsd_info_proc_mappings_entry):
	New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/MAINTAINERS: Add Rainer Orth as Solaris maintainer for GDB
@ 2018-10-17 19:00 sergiodj+buildbot
  2018-10-17 20:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-17 19:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d500b4f23fc329f5c8cce6ee8fa3629c0f130038 ***

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

gdb/MAINTAINERS: Add Rainer Orth as Solaris maintainer for GDB

gdb/ChangeLog:

	* MAINTAINERS (Responsible Maintainers): Add Rainer Orth as
	Solaris Maintainer.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23653, ld SIGSEGVs when attempts to link sparc object with x86_64 library
@ 2018-10-17  5:34 sergiodj+buildbot
  2018-10-17  8:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-17  5:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4de5434b694fc260d02610e8e7fec21b2923600a ***

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

PR23653, ld SIGSEGVs when attempts to link sparc object with x86_64 library

This patch improves dynobj selection.  This allows the testcase in the
PR to proceed further before segfaulting due to other bugs in the
sparc backend.

../ld/ld-new --eh-frame-hdr -m elf_x86_64 -shared -o bug.so.5 bug.o ./libc.so.6 ./crtendS.o
../ld/ld-new: sparc architecture of input file `bug.o' is incompatible with i386:x86-64 output
../ld/ld-new: bug.o: in function `a':
bug.c:(.text+0x4): undefined reference to `_GLOBAL_OFFSET_TABLE_'
../ld/ld-new: bug.c:(.text+0x8): undefined reference to `_GLOBAL_OFFSET_TABLE_'
Segmentation fault

	PR 23653
	* elflink.c (_bfd_elf_link_create_dynstrtab): Match elf_object_id
	too when choosing dynobj.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Rewrite catch-follow-exec.exp
@ 2018-10-16 21:32 sergiodj+buildbot
  2018-10-17  4:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-16 21:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4b90788516fd431c86c22deac5001d6c4648227 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: c4b90788516fd431c86c22deac5001d6c4648227

[gdb/testsuite] Rewrite catch-follow-exec.exp

There are two problems with the current catch-follow-exec.exp:
- INTERNAL_GDBFLAGS (containing the datadir setting) is not used
- remote host testing doesn't work

Fix the former by using gdb_spawn_with_cmdline_opts.  Fix the latter by
requiring gdb-native.

Build on x86_64-linux with and without ubsan, and tested.

2018-10-16  Tom de Vries  <tdevries@suse.de>

	PR gdb/23730
	* gdb.base/catch-follow-exec.c: Add copyright notice.
	* gdb.base/catch-follow-exec.exp: Rewrite to use
	gdb_spawn_with_cmdline_opts.  Require gdb-native.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Fix error checking for SIMD udot (by element)
@ 2018-10-16 18:23 sergiodj+buildbot
  2018-10-16 21:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-16 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 66e6f0b760c2480e4ebdac8169adcee1fc31f689 ***

Author: Matthew Malcomson <matthew.malcomson@arm.com>
Branch: master
Commit: 66e6f0b760c2480e4ebdac8169adcee1fc31f689

AArch64: Fix error checking for SIMD udot (by element)

Committed on behalf of Matthew Malcomson:

The SIMD UDOT instruction assembly has an unusual operand that selects a single
32 bit element with the mnemonic 4B.
This unusual mnemonic is handled by a special operand qualifier and associated
qualifier data in `aarch64_opnd_qualifiers`.

The current qualifier data describes 4 1-byte elements with the structure
{1, 4, 0x0, "4b", OQK_OPD_VARIANT}
This makes sense, as the instruction does work on 4 1-byte elements, however
some logic in the `operand_general_constraint_met_p` makes assumptions about
the range of index allowed when selecting a SIMD_ELEMENT depending on element
size.
That function reasons that e.g. in order to select a byte-sized element in a 16
byte V register an index must allow selection of one of the 16 elements and
hence its range will be in [0,15].

This reasoning breaks with the above description of a 4 part selection of 1
byte elements and allows an index outside the valid [0,3] range, triggering an
assert later on in the program in `aarch64_ins_reglane`.

vshcmd: > echo 'udot v0.2s, v1.8b, v2.4b[4]' | ../src/binutils-build/gas/as-new -march=armv8.4-a
as-new: ../../binutils-gdb/opcodes/aarch64-asm.c:134: aarch64_ins_reglane: Assertion `reglane_index < 4' failed.
{standard input}: Assembler messages:
{standard input}:1: Internal error (Aborted).
Please report this bug.

This patch changes the operand qualifier data so that it describes a single
32 bit element.
{4, 1, 0x0, "4b", OQK_OPD_VARIANT}
Hence the calculation in `operand_general_constraint_met_p` provides the
correct answer and the usual error checking machinery is used.

vshcmd: > echo 'udot v0.2s, v1.8b, v2.4b[4]' | ../src/binutils-build/gas/as-new -march=armv8.4-a
{standard input}: Assembler messages:
{standard input}:1: Error: register element index out of range 0 to 3 at operand 3 -- `udot v0.2s,v1.8b,v2.4b[4]'


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Simplify PR23110 PE_DEBUG_DATA size checks
@ 2018-10-16  8:51 sergiodj+buildbot
  2018-10-16  9:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-16  8:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 48dcd4ea064ae86364dacbf4dd7f035fba56151c ***

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

Simplify PR23110 PE_DEBUG_DATA size checks

The negative size check can be rolled into the "exceeds space left in
section" check if that is done using an unsigned comparison.  We know
that "addr - section->vma" is never larger than section->size since
the section is found by find_section_by_vma.

	* peXXigen.c (_bfd_XX_bfd_copy_private_bfd_data_common): Simplify
	PE_DEBUG_DATA size checks.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23781, _bfd_pe_bfd_copy_private_bfd_data_common memory leak
@ 2018-10-16  6:35 sergiodj+buildbot
  2018-10-16  8:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-16  6:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8df73d5cc3a87101f3bd254f33820fcce61bc971 ***

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

PR23781, _bfd_pe_bfd_copy_private_bfd_data_common memory leak

	PR 23781
	* peXXigen.c (_bfd_XX_bfd_copy_private_bfd_data_common): Free data
	before returning.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unnecessary casts from TUI
@ 2018-10-16  5:56 sergiodj+buildbot
  2018-10-16  6:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-16  5:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63a33118e05a84fbae40cbe3ef955b52bad359a7 ***

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

Remove unnecessary casts from TUI

This removes a number of unnecessary casts from the TUI.  Some were
found with -Wuseless-cast (which, I think, can't easily be enabled for
gdb); and some were found by inspection.

Tested by rebuilding on x86-64 Fedora 28.
I'm checking this in.

gdb/ChangeLog
2018-10-15  Tom Tromey  <tom@tromey.com>

	* tui/tui.c (strcat_to_buf): Remove casts.
	* tui/tui-winsource.c (tui_show_source_line)
	(tui_set_is_exec_point_at, tui_line_is_displayed): Remove casts.
	* tui/tui-wingeneral.c (tui_refresh_win, box_win): Remove casts.
	* tui/tui-windata.c (tui_first_data_item_displayed)
	(tui_delete_data_content_windows, tui_erase_data_content)
	(tui_display_all_data, tui_display_data_from)
	(tui_refresh_data_win, tui_vertical_data_scroll): Remove casts.
	* tui/tui-win.c (tui_set_win_height)
	(make_invisible_and_set_new_height, parse_scrolling_args): Remove
	casts.
	* tui/tui-win.c (tui_resize_all): Remove casts.
	(tui_scroll_backward_command, tui_set_focus)
	(tui_set_tab_width_command): Likewise.
	* tui/tui-source.c (tui_vertical_source_scroll): Remove cast.
	* tui/tui-regs.c (tui_show_register_group): Remove cast.
	* tui/tui-layout.c (tui_set_layout_by_name): Remove cast.
	* tui/tui-disasm.c (tui_vertical_disassem_scroll): Remove cast.
	* tui/tui-data.c (tui_partial_win_by_name, tui_free_win_content):
	Remove casts.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add Alan Hayward as AArch64/ARM GDB maintainer
@ 2018-10-15 20:07 sergiodj+buildbot
  2018-10-15 20:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-15 20:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 933e62b1c17b1cf396f8bf8e17a066d03226533e ***

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

Add Alan Hayward as AArch64/ARM GDB maintainer

gdb/ChangeLog:

	* MAINTAINERS (Responsible Maintainers): Add Alan Hayward as
	AArch64/ARM maintainer.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] BFD_INIT_MAGIC
@ 2018-10-15 13:05 sergiodj+buildbot
  2018-10-15 14:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-15 13:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf2dd8d7cf4114b8a60dbb83b340f76b9b2474d1 ***

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

BFD_INIT_MAGIC

This patch performs a run-time test that a shared libbfd.so has been
compiled with the same size bfd_vma as that of apps using the library.
On a 32-bit host it is easily possible to have one libbfd.so compiled
to support 64-bit targets (or configured with --enable-64-bit-bfd)
while another only supports 32-bit targets.  The two libraries will
have differently sized bfd_vma types, and if the wrong one is loaded
all sorts of weird behaviour might be seen.

bfd/
	PR 23534
	* init.c (BFD_INIT_MAGIC): Define.
	(bfd_init): Return BFD_INIT_MAGIC.
	bfd-in2.h: Regenerate.
binutils/
	PR 23534
	* addr2line.c (main): Exit with fatal error if bfd_init
	returns an unexpected value.
	* ar.c (main): Likewise.
	* dlltool.c (identify_dll_for_implib): Likewise.
	* nm.c (main): Likewise.
	* objcopy.c (main): Likewise.
	* objdump.c (main): Likewise.
	* size.c (main): Likewise.
	* strings.c (main): Likewise.
	* windmc.c (main): Likewise.
	* windres.c (main): Likewise.
gas/
	PR 23534
	* as.c (main): Exit with fatal error if bfd_init returns an
	unexpected value.
ld/
	PR 23534
	* ldmain.c (main): Exit with fatal error if bfd_init returns
	an unexpected value.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] _bfd_clear_contents bounds checking
@ 2018-10-13 13:40 sergiodj+buildbot
  2018-10-13 14:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-13 13:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0930cb3021b8078b34cf216e79eb8608d017864f ***

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

_bfd_clear_contents bounds checking

This PR shows a fuzzed binary triggering a segfault via a bad
relocation in .debug_line.  It turns out that unlike normal
relocations applied to a section, the linker applies those with
symbols from discarded sections via _bfd_clear_contents without
checking that the relocation is within the section bounds.  The same
thing now happens when reading debug sections since commit
a4cd947aca23, the PR23425 fix.

	PR 23770
	PR 23425
	* reloc.c (_bfd_clear_contents): Replace "location" param with
	"buf" and "off".  Bounds check "off".  Return status.
	* cofflink.c (_bfd_coff_generic_relocate_section): Update
	_bfd_clear_contents call.
	* elf-bfd.h (RELOC_AGAINST_DISCARDED_SECTION): Likewise.
	* elf32-arc.c (elf_arc_relocate_section): Likewise.
	* elf32-i386.c (elf_i386_relocate_section): Likewise.
	* elf32-metag.c (metag_final_link_relocate): Likewise.
	* elf32-nds32.c (nds32_elf_get_relocated_section_contents): Likewise.
	* elf32-ppc.c (ppc_elf_relocate_section): Likewise.
	* elf32-visium.c (visium_elf_relocate_section): Likewise.
	* elf64-ppc.c (ppc64_elf_relocate_section): Likewise.
	* elf64-x86-64.c *(elf_x86_64_relocate_section): Likewise.
	* libbfd-in.h (_bfd_clear_contents): Update prototype.
	* libbfd.h: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix buglets in gdb.trace/tspeed.{exp,c}
@ 2018-10-12 20:49 sergiodj+buildbot
  2018-10-12 21:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-12 20:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f9c49bffe616013ba97f679afd3446a8c87d80a7 ***

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

Fix buglets in gdb.trace/tspeed.{exp,c}

When trying to run gdb.trace/tspeed.exp, I get:

ERROR: can't read "ipalib": no such variable
    while executing
"gdb_load_shlib $ipalib"
    (procedure "prepare_for_trace_test" line 5)

This problem seems to come from commit

    c708f4d256f ("gdb: Don't call gdb_load_shlib unless GDB is running")

which moved the gdb_load_shlib call in prepare_for_trace_test.  In order
to access the ipalib variable, we need to declare "global ipalib" first.

Then, this test uses nowarnings, for no good reason I could find.  We
can remove that and fix the two trivial warnings that appear:

/home/emaisin/src/binutils-gdb/gdb/testsuite/gdb.trace/tspeed.c: In function 'main':
/home/emaisin/src/binutils-gdb/gdb/testsuite/gdb.trace/tspeed.c:87:16: warning: too many arguments for format [-Wformat-extra-args]
        printf ("Negative times, giving up\n", max_iters);
                ^
/home/emaisin/src/binutils-gdb/gdb/testsuite/gdb.trace/tspeed.c:99:7: warning: implicit declaration of function 'sleep' [-Wimplicit-function-declaration]
       sleep (1);  /* set post-run breakpoint here */
       ^

gdb/testsuite/ChangeLog:

	* gdb.trace/tspeed.exp: Remove nowarnings.
	(prepare_for_trace_test): Declare "global ipalib".
	* gdb.trace/tspeed.c: Include unistd.h.
	(main): Remove superfluous printf argument.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix pathname regexp in gdb.base/solib-vanish.exp.
@ 2018-10-12  0:20 sergiodj+buildbot
  2018-10-12  0:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-12  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4330bde6891c74498cea8866ce9992181798861 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: d4330bde6891c74498cea8866ce9992181798861

Fix pathname regexp in gdb.base/solib-vanish.exp.

2018-10-11  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/solib-vanish.exp: Fix regexp not to require a POSIX
	directory prefix on the filename.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix interp::m_name resource leak found by Coverity
@ 2018-10-11  9:34 sergiodj+buildbot
  2018-10-11 10:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-11  9:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbe61a3661b083a666e6550b3b0c2de364e6d4a6 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: fbe61a3661b083a666e6550b3b0c2de364e6d4a6

Fix interp::m_name resource leak found by Coverity

This commit fixes a resource leak found by Coverity, where interp's
constructor allocated memory for m_name that interp's destructor did
not free.

gdb/ChangeLog:

	* interps.h (interp::m_name): Make private and mutable.
	* interps.c (interp::~interp): Free m_name.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add missing va_end found by Coverity
@ 2018-10-10 14:19 sergiodj+buildbot
  2018-10-10 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-10 14:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33b031ce7a9b8b1b7c729518af965b7cb70a1cd6 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 33b031ce7a9b8b1b7c729518af965b7cb70a1cd6

Add missing va_end found by Coverity

This commit adds a missing va_end found by Coverity.

gdb/ChangeLog:

	* remote.c (remote_target::remote_send_printf): Add
	missing va_end found by Coverity.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold Size{16,32,64} template attributes
@ 2018-10-10  7:45 sergiodj+buildbot
  2018-10-10  7:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-10  7:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 673fe0f0a7a0624819f1b4cdc289f43691567e91 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 673fe0f0a7a0624819f1b4cdc289f43691567e91

x86: fold Size{16,32,64} template attributes

Only one of them can be set at a time, which means they can be expressed
by a single 2-bit field instead of three 1-bit ones.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Disable the undefined behavior sanitizer by default
@ 2018-10-10  1:54 sergiodj+buildbot
  2018-10-10  4:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-10  1:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eff98030f90d3dab4c7d133ab0b0cb02d1921543 ***

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

Disable the undefined behavior sanitizer by default

There have been a few undefined behavior failures reported, and Pedro
suggested that the sanitizer be disabled by default.  This patch
implements this.

gdb/ChangeLog
2018-10-09  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.
	* sanitize.m4 (AM_GDB_UBSAN): Default to no.
	* NEWS: Update --enable-ubsan documentation.

gdb/doc/ChangeLog
2018-10-09  Tom Tromey  <tom@tromey.com>

	* gdb.texinfo (Configure Options): Update --enable-ubsan
	documentation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PATCH, BINUTULS, AARCH64, 9/9] Add SSBS to MSR/MRS
@ 2018-10-10  0:45 sergiodj+buildbot
  2018-10-10  2:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-10  0:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 104fefeebb544b7745bb353b63110afa46119647 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 104fefeebb544b7745bb353b63110afa46119647

[PATCH, BINUTULS, AARCH64, 9/9] Add SSBS to MSR/MRS

This patch is part of the patch series to add support for ARMv8.5-A
extensions.
(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/exploration-tools)
The encodings can be found in the System Register XML.

This patch adds support for the mitigation for Spectre Variant 4 by
adding the PSTATE bit SSBS which are accessible using MSR and MRS
instructions. Although this is a mandatory addition to the ARMv8.5-A,
it is permitted to be added to any version of the ARMv8 architecture.
This is enabled using the command line option of +ssbs for older
versions.

*** include/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_SSBS): New.
	(AARCH64_ARCH_V8_5): Add AARCH64_FEATURE_SSBS by default.

*** opcodes/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-opc.c (operand_general_constraint_met_p): Add
	SSBS in the check for one-bit immediate.
	(aarch64_sys_regs): New entry for SSBS.
	(aarch64_sys_reg_supported_p): New check for above.
	(aarch64_pstatefields): New entry for SSBS.
	(aarch64_pstatefield_supported_p): New check for above.

*** gas/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-aarch64.c (aarch64_features): Add new "ssbs".
	* doc/c-aarch64.texi: Document the same.
	* testsuite/gas/aarch64/ssbs-illegal1.d: New test.
	* testsuite/gas/aarch64/ssbs-illegal1.l: New test.
	* testsuite/gas/aarch64/ssbs-illegal2.d: New test.
	* testsuite/gas/aarch64/ssbs-illegal2.l: New test.
	* testsuite/gas/aarch64/ssbs.s: New test.
	* testsuite/gas/aarch64/ssbs1.d: Test with +ssbs
	* testsuite/gas/aarch64/ssbs2.d: Test with armv8.5-a.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PATCH, BINUTILS, AARCH64, 3/9] Add instruction SB for ARMv8.5-A
@ 2018-10-09 18:12 sergiodj+buildbot
  2018-10-09 19:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 18:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68dfbb92ef5f013a315d652c88ede2082c16a88e ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 68dfbb92ef5f013a315d652c88ede2082c16a88e

[PATCH, BINUTILS, AARCH64, 3/9] Add instruction SB for ARMv8.5-A

This patch is part of the patch series to add support for ARMv8.5-A
extensions.
(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/docs/ddi0596/a/a64-base-instructions-alphabetic-order)

This instruction is retrospectively made optional for all versions of
the architecture from ARMv8.0 to ARMv8.4 and is mandatory from
ARMv8.5.  Hence a new command line option of "+sb" is added for older
architectures.

*** include/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_SB): New.
	(AARCH64_ARCH_V8_5): Add AARCH64_FEATURE_SB by default.

*** opcodes/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-tbl.h (aarch64_feature_sb): New.
	(SB, SB_INSN): New.
	(aarch64_opcode_table): Add entry for sb.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

*** gas/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-aarch64.c (aarch64_features): Add new "sb" option
	for older architectures.
	* doc/c-aarch64.texi: Document the same.
	* testsuite/gas/aarch64/sb.s: New.
	* testsuite/gas/aarch64/sb.d: New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PATCH, BINUTILS, AARCH64, 2/9] Add Data procoessing instructions for ARMv8.5-A
@ 2018-10-09 16:52 sergiodj+buildbot
  2018-10-09 18:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13c60ad7e1211ee1dfbf6bfb5e35110a33e4eed5 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 13c60ad7e1211ee1dfbf6bfb5e35110a33e4eed5

[PATCH, BINUTILS, AARCH64, 2/9] Add Data procoessing instructions for ARMv8.5-A

This patch is part of the patch series to add support for ARMv8.5-A
extensions.
(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/docs/ddi0596/a/a64-base-instructions-alphabetic-order)

This patch adds the data processing instructions that are new to
ARMv8.5-A.

1) There are 2 instructions: xaflag, axflag, that are added to
manipulate the states of the flag and are used to convert between the
Arm representation and the fcmp representation.

2) The other instructions are rounding instructions which have 8
versions based on whether the floating-point number is a
Single-Precision or Double-Precision number, whether the target
integer is a 32-bit or 64-bit integer and whether the rounding mode is
the ambient rounding mode or to zero. Each of these instruction is
available in both Scalar and Vector forms.

Since both 1) and 2) have separate identification mechanism and it is
permissible that a ARMv8.4 compliant implementation may include any
arbitrary subset of the ARMv8.5 features unless otherwise specified,
new feature bits are added.

*** include/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_FLAGMANIP): New.
	(AARCH64_FEATURE_FRINTTS): New.
	(AARCH64_ARCH_V8_5): Add both by default.

*** opcodes/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-tbl.h (aarch64_feature_flagmanip): New.
	(aarch64_feature_frintts): New.
	(FLAGMANIP, FRINTTS): New.
	(aarch64_opcode_table): Add entries for xaflag, axflag
	and frint[32,64][x,z] instructions.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

*** gas/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* testsuite/gas/aarch64/armv8_5-a-dp.s: New.
	* testsuite/gas/aarch64/armv8_5-a-dp.d: New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PATCH, BINUTILS, AARCH64, 8/9] Add SCXTNUM_ELx and ID_PFR2_EL1 system registers
@ 2018-10-09 16:35 sergiodj+buildbot
  2018-10-10  1:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 16:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97330e723cf3c639a951329ac5fe2797528249b ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: a97330e723cf3c639a951329ac5fe2797528249b

[PATCH, BINUTILS, AARCH64, 8/9] Add SCXTNUM_ELx and ID_PFR2_EL1 system registers

This patch is part of the patch series to add support for ARMv8.5-A
extensions.
(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/exploration-tools)
The encodings can be found in the System Register XML.

This patch adds the new system registers SCXTNUM_ELx and ID_PFR2_EL1.

*** include/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_SCXTNUM): New.
	(AARCH64_FEATURE_ID_PFR2): New.
	(AARCH64_ARCH_V8_5): Add both by default.

*** opcodes/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-opc.c (aarch64_sys_regs): New entries for
	scxtnum_el[0,1,2,3,12] and id_pfr2_el1.
	(aarch64_sys_reg_supported_p): New checks for above.

*** gas/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* testsuite/gas/aarch64/sysreg-4.s: Test registers
	scxtnum_el[0,1,2,3,12] and id_pfr2_el1.
	* testsuite/gas/aarch64/sysreg-4.d: Likewise.
	* testsuite/gas/aarch64/illegal-sysreg-4.l: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PATCH, BINUTILS, AARCH64, 5/9] Add DC CVADP instruction
@ 2018-10-09 15:52 sergiodj+buildbot
  2018-10-09 22:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 15:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fd229a447cd28a70bfd921f617bc6c3553b8fdd ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 3fd229a447cd28a70bfd921f617bc6c3553b8fdd

[PATCH, BINUTILS, AARCH64, 5/9] Add DC CVADP instruction

This patch is part of the patch series to add support for ARMv8.5-A
extensions.
(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/docs/ddi0596/a/a64-base-instructions-alphabetic-order/dc-data-cache-operation-an-alias-of-sys)

This patch adds the DC CVADP instruction. Since this has a separate
identification mechanism a new feature bit is added.

*** include/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_CVADP): New.

*** opcodes/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-opc.c (aarch64_sys_regs_dc): New entry for cvadp.
	(aarch64_sys_ins_reg_supported_p): New check for above.

*** gas/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* testsuite/gas/aarch64/sysreg-4.s: Test instruction.
	* testsuite/gas/aarch64/sysreg-4.d: Likewise.
	* testsuite/gas/aarch64/illegal-sysreg-4.l: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PATCH, BINUTILS, AARCH64, 4/9] Add Execution and Data Restriction instructions
@ 2018-10-09 15:38 sergiodj+buildbot
  2018-10-09 20:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac435d46608be7ef90f80aaf9ff48443aea571e ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 2ac435d46608be7ef90f80aaf9ff48443aea571e

[PATCH, BINUTILS, AARCH64, 4/9] Add Execution and Data Restriction instructions

This patch is part of the patch series to add support for ARMv8.5-A
extensions.
(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/docs/ddi0596/a/a64-base-instructions-alphabetic-order)

This patch adds the prediction restriction instructions (that is, cfp,
dvp, cpp). These instructions are retrospectively made optional for
all versions of the architecture from ARMv8.0 to ARMv8.4 and is
mandatory from ARMv8.5. Hence adding a new +predres which can be used
by the older architectures.

*** include/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* opcode/aarch64.h (AARCH64_FEATURE_PREDRES): New.
	(AARCH64_ARCH_V8_5): Add AARCH64_FEATURE_PREDRES by default.
	(aarch64_opnd): Add AARCH64_OPND_SYSREG_SR.
	(aarch64_sys_regs_sr): Declare new table.

*** opcodes/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* aarch64-dis.c (aarch64_ext_sysins_op): Add case for
	AARCH64_OPND_SYSREG_SR.
	* aarch64-opc.c (aarch64_print_operand): Likewise.
	(aarch64_sys_regs_sr): Define table.
	(aarch64_sys_ins_reg_supported_p): Check for RCTX with
	AARCH64_FEATURE_PREDRES.
	* aarch64-tbl.h (aarch64_feature_predres): New.
	(PREDRES, PREDRES_INSN): New.
	(aarch64_opcode_table): Add entries for cfp, dvp and cpp.
	(AARCH64_OPERANDS): Add new description for SYSREG_SR.
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Regenerate.
	* aarch64-opc-2.c: Regenerate.

*** gas/ChangeLog ***

2018-10-09  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-aarch64.c (aarch64_sys_regs_sr_hsh): New.
	(parse_operands): Add entry for AARCH64_OPND_SYSREG_SR.
	(md_begin): Allocate and initialize aarch64_sys_regs_sr_hsh
	with aarch64_sys_regs_sr.
	(aarch64_features): Add new "predres" option for older
	architectures.
	* doc/c-aarch64.texi: Document the same.
	* testsuite/gas/aarch64/sysreg-4.s: New.
	* testsuite/gas/aarch64/sysreg-4.d: New.
	* testsuite/gas/aarch64/illegal-sysreg-4.d: New.
	* testsuite/gas/aarch64/illegal-sysreg-4.l: New.
	* testsuite/gas/aarch64/predres.s: New.
	* testsuite/gas/aarch64/predres.d: New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Fix target_supports_scheduler_locking raciness
@ 2018-10-09 14:06 sergiodj+buildbot
  2018-10-09 16:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58bbcd02dee8ba018b97706c068ed8ed7afac15d ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 58bbcd02dee8ba018b97706c068ed8ed7afac15d

[gdb/testsuite] Fix target_supports_scheduler_locking raciness

When calling gdb_start_cmd, it's the caller's responsibility to wait for gdb
to return to the prompt.  In target_supports_scheduler_locking, that's not the
case, and consequently, target_supports_scheduler_locking fails spuriously.

Fix by using runto_main instead.

Build and reg-tested on x86_64-linux.

2018-10-09  Tom de Vries  <tdevries@suse.de>

	* lib/gdb.exp (target_supports_scheduler_locking): Replace gdb_start_cmd
	with runto_main.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix buffer overrun found by Coverity
@ 2018-10-09 13:37 sergiodj+buildbot
  2018-10-09 14:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09 13:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04fd5eed91c0a960e1706fb627912ad6350ae391 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 04fd5eed91c0a960e1706fb627912ad6350ae391

Fix buffer overrun found by Coverity

This commit fixes a buffer overrun found by Coverity, where
36 bytes are written into a 24 byte buffer.

gdb/ChangeLog:

	* dwarf2read.c (create_dwp_hash_table): Fix buffer overrun
	found by Coverity.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Do not place symbols into a discarded .dynsym
@ 2018-10-09  7:39 sergiodj+buildbot
  2018-10-09  8:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-09  7:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c2649ed7481881cb963bb53251a79bfb8b1047e ***

Author: Egeyar Bagcioglu <egeyar.bagcioglu@oracle.com>
Branch: master
Commit: 1c2649ed7481881cb963bb53251a79bfb8b1047e

Do not place symbols into a discarded .dynsym

Prevents getting an error about dynamic symbols in sections indexed
64K+ when .dynsym is discarded.

	* elflink.c (elf_link_output_extsym): Do not place symbols into a
	discarded .dynsym.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused variables from riscv-fbsd-tdep.c
@ 2018-10-08 23:07 sergiodj+buildbot
  2018-10-08 23:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 23:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0c3048e3f397a595a14208e82e21399131f782b ***

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

Remove unused variables from riscv-fbsd-tdep.c

This removes a couple of unused variables from riscv-fbsd-tdep.c.
This allows a --enable-targets=all build to complete on
x86-64 Fedora 28.

gdb/ChangeLog
2018-10-08  Tom Tromey  <tom@tromey.com>

	* riscv-fbsd-tdep.c (riscv_fbsd_sigframe_init): Remove unused
	variable.
	(riscv_fbsd_init_abi): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use p_vaddr_offset to set p_vaddr on segments without sections
@ 2018-10-08 13:45 sergiodj+buildbot
  2018-10-08 14:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d695627883b32cf33adb529c8fc7271b46dcf55 ***

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

Use p_vaddr_offset to set p_vaddr on segments without sections

p_vaddr is currently set from the first section vma if a segment has
sections, and to zero if a segment has no sections.  This means we
lose p_vaddr when objcopy'ing executables if a segment without
sections has a non-zero p_vaddr.

This patch saves p_vaddr to p_vaddr_offset, and to make the use of
p_vaddr_offset consistent, inverts the sign.  (It's now added to
section vma to get segment vaddr, and added to zero when there are no
sections.)

	* elf.c (assign_file_positions_for_load_sections): Set p_vaddr
	from m->p_vaddr_offset for segments without sections.  Invert
	sign of p_vaddr_offset.
	(rewrite_elf_program_header, copy_elf_program_header): Save
	old segment p_vaddr to p_vaddr_offset.  Invert sign of
	p_vaddr_offset.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Replace C initializers with memset
@ 2018-10-08 13:17 sergiodj+buildbot
  2018-10-08 17:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 780f601cf3bfd2eb141c2ea32b673b5bd0956a33 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 780f601cf3bfd2eb141c2ea32b673b5bd0956a33

AArch64: Replace C initializers with memset

Clang doesn't accept {0} as a valid C struct initializer under their implementation
of -Wmissing-field-initializers.  This makes using C initializers a bit tricky.

Instead I'm changing the code to use memset instead, which at least GCC inlines and
generates the same code for.  This also seems to be the idiom used in binutils for
most targets.

opcodes/

	* aarch64-opc.c (verify_constraints): Use memset instead of {0}.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Don't add GNU_PROPERTY_X86_FEATURE_2_NEEDED for -z separate-code
@ 2018-10-08 12:28 sergiodj+buildbot
  2018-10-08 16:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 12:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80f3ac5d61a5d01d7cf951de0e24ecdc71c545cb ***

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

x86: Don't add GNU_PROPERTY_X86_FEATURE_2_NEEDED for -z separate-code

With

commit 64029e93683a266c38d19789e780f3748bd6a188
Author: Alan Modra <amodra@gmail.com>
Date:   Fri Oct 5 11:40:54 2018 +0930

    Separate header PT_LOAD for -z separate-code

there is no need to add a GNU_PROPERTY_X86_ISA_1_USED note to force
program header in in non-code PT_LOAD segment when -z separate-code
is used.

bfd/

	PR ld/23428
	* elfxx-x86.c (_bfd_x86_elf_link_setup_gnu_properties): Don't
	add GNU_PROPERTY_X86_FEATURE_2_NEEDED to force program header
	in non-code PT_LOAD segment.

ld/

	PR ld/23428
	* testsuite/ld-i386/property-x86-4a.d: Updated.
	* testsuite/ld-x86-64/property-x86-4a-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-4a.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Separate header PT_LOAD for -z separate-code
@ 2018-10-08 11:39 sergiodj+buildbot
  2018-10-08 15:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 11:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64029e93683a266c38d19789e780f3748bd6a188 ***

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

Separate header PT_LOAD for -z separate-code

This patch, along with previous patches in the series, supports
putting the ELF file header and program headers in a PT_LOAD without
sections.

Logic governing whether headers a loaded has changed a little:  The
primary reason to include headers is now the presence of
SIZEOF_HEADERS in a linker script.  However, to support scripts that
may have reserved space for headers by hand, we continue to add
headers whenever the first section address is past the end of headers
modulo page size.

include/
	* bfdlink.h (struct bfd_link_info): Add load_phdrs field.
bfd/
	* elf-nacl.c (nacl_modify_segment_map): Cope with header PT_LOAD
	lacking sections.
	* elf.c (_bfd_elf_map_sections_to_segments): Assume file and
	program headers are required when info->load_phdrs.  Reorganize
	code handling program headers.  Generate a mapping without
	sections just for file and program headers when -z separate-code
	would indicate they should be on a different page to the first
	section.
ld/
	* ldexp.c (fold_name <SIZEOF_HEADERS>): Set link_info.load_phdrs.
	* testsuite/ld-elf/loadaddr1.d: Pass -z noseparate-code.
	* testsuite/ld-elf/loadaddr2.d: Likewise.
	* testsuite/ld-i386/vxworks2.sd: Adjust expected output.
	* testsuite/ld-powerpc/vxworks2.sd: Likewise.
	* testsuite/ld-elf/overlay.d: Remove spu xfail.
	* testsuite/ld-spu/ovl.lnk: Don't use SIZEOF_HEADERS.
	* testsuite/ld-tic6x/dsbt-be.ld: Likewise.
	* testsuite/ld-tic6x/dsbt-inrange.ld: Likewise.
	* testsuite/ld-tic6x/dsbt-overflow.ld: Likewise.
	* testsuite/ld-tic6x/dsbt.ld: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] No PT_INTERP when .interp is zero size
@ 2018-10-08 11:10 sergiodj+buildbot
  2018-10-08 13:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 11:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b9e270b09c140464a7892c95c28eafa812c6b08 ***

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

No PT_INTERP when .interp is zero size

Some targets don't set a default interpreter, resulting in an empty
.interp section unless --dynamic-linker is passed to ld.  A PT_INTERP
without a path is rather useless.

The testsuite change fixes a failure on microblaze-linux.

bfd/
	* elf.c (get_program_header_size): Don't count PT_INTERP if
	.interp is empty.
	(_bfd_elf_map_sections_to_segments): Don't create PT_INTERP if
	.interp is empty.
ld/
	* testsuite/ld-elf/pr22423.d: Pass --dynamic-linker to ld.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Tidy elf_segment_map allocation
@ 2018-10-08 10:26 sergiodj+buildbot
  2018-10-08 11:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-08 10:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00bee008e9f7d0b3adf3278962450944653787f8 ***

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

Tidy elf_segment_map allocation

This cleans up elf_segment_map allocation when the section array is
empty.  "amt += (to - from - 1) * sizeof (asection *)", when "to" and
"from" are unsigned int results in an unsigned value inside the
parentheses.  When "to" and "from" are equal on a 64-bit host,
0xffffffff * 8 is added to "amt", not -8 as desired.

The patch also renames a variable for consistency with other functions
using a similar index.

	* elf.c (make_mapping): Cope with zero size array at end of
	struct elf_segment_map.
	(_bfd_elf_map_sections_to_segments): Likewise.
	(rewrite_elf_program_header, copy_elf_program_header): Likewise.
	(_bfd_elf_map_sections_to_segments): Rename phdr_index to hdr_index.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add Inferior.architecture method
@ 2018-10-07 10:25 sergiodj+buildbot
  2018-10-07 10:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-07 10:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT add5ded5e476918ef8b05823801531de2f51fa9c ***

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

Add Inferior.architecture method

I've written a couple of gdb unwinders in Python, and while doing so,
I wanted to find the architecture of the inferior.  (In an unwinder in
particular, one can't use the frame's architecture, because there is
no frame.)

This patch adds Inferior.architecture to allow this.  Normally I think
I would have chosen an attribute and not a method here, but seeing
that Frame.architecture is a method, I chose a method as well, for
consistency.

gdb/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR python/19399:
	* python/py-inferior.c: Add "architecture" entry.
	(infpy_architecture): New function.

gdb/doc/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR python/19399:
	* python.texi (Inferiors In Python): Document
	Inferior.Architecture.

gdb/testsuite/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR python/19399:
	* gdb.python/py-inferior.exp: Add architecture test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix Python gdb.Breakpoint.location crash
@ 2018-10-07  6:18 sergiodj+buildbot
  2018-10-07  6:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-07  6:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a8be20359dba9cc684fd3ffa222d985399f3b18 ***

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

Fix Python gdb.Breakpoint.location crash

I noticed today that gdb.Breakpoint.location will crash when applied
to a catchpoint made with "catch throw".

The bug is that "catch throw" makes a breakpoint that is of type
bp_breakpoint, but which does not have a location.

Regression tested on x86-64 Fedora 28.

gdb/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	* python/py-breakpoint.c (bppy_get_location): Handle a
	bp_breakpoint without a location.

gdb/testsuite/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-breakpoint.exp (check_last_event): Check location
	of a "throw" catchpoint.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update symbol domain and location values for Python
@ 2018-10-07  5:46 sergiodj+buildbot
  2018-10-07  9:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-07  5:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 51e78fc5fa21870d415c52f90b93e3c6ad57be46 ***

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

Update symbol domain and location values for Python

In the distant past, there was no distinction between domain_enum and
search_domain.  At that point, there were two sets of enumerators in a
single enum -- which is why these were eventually split.  This
confusion leaked out to the Python API as well, as noted in
PR python/21765.

This patch deprecates the constants that aren't useful to the Python
API.  They are left in place for now, but removed from the
documentation.  Also, their values are changed so that, if used, they
might work.  Finally, missing domains and location constants are
added.

gdb/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR python/21765:
	* python/py-symbol.c (gdbpy_initialize_symbols): Redefine
	SYMBOL_VARIABLES_DOMAIN, SYMBOL_FUNCTIONS_DOMAIN,
	SYMBOL_TYPES_DOMAIN.  Define SYMBOL_MODULE_DOMAIN,
	SYMBOL_COMMON_BLOCK_DOMAIN, SYMBOL_LOC_COMMON_BLOCK.

gdb/doc/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR python/21765:
	* python.texi (Symbols In Python): Document the module and
	common-block domains.  Remove documentation for incorrect
	domains.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Do not accidentally include in-tree readline headers
@ 2018-10-07  5:20 sergiodj+buildbot
  2018-10-07  7:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-07  5:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8a5dbcab8df0b3a9e04745d4fe8d64740acb323 ***

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

Do not accidentally include in-tree readline headers

PR build/17077 points out that when --with-system-readline is given,
gdb will still pick up the in-tree readline headers.  Normally this is
not a big problem, because readline is very stable and so the ABI does
not change much; but it is clearly a bug to do this, and could bite at
some point.

The basic problem is that OPCODES_CFLAGS uses -I$(OPCODES_SRC)/..  so
that #include "opcodes/..." works.  However, this also makes it so the

This patch fixes the problem in a mildly hacky way: remove the
offending -I option, and change gdb to use #include "../opcodes/..."
instead.  This continues to make it clear where the header comes from,
without allowing incorrect behavior.

Tested by rebuilding and then looking at the *.Po files.

gdb/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR build/17077:
	* Makefile.in (OPCODES_CFLAGS): Remove "-I$(OPCODES_SRC)/..".
	* arc-tdep.c, frv-tdep.c, lm32-tdep.c, mep-tdep.c,
	microblaze-tdep.c, or1k-tdep.h: Use ../opcodes, not opcodes, in
	#include.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Call nonl before wgetch in TUI
@ 2018-10-06 22:16 sergiodj+buildbot
  2018-10-06 23:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-06 22:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a9569281a63e472750e3b7b481e2cdf5c931ed8 ***

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

Call nonl before wgetch in TUI

PR tui/28819 points out that, in the TUI, the C-j and C-m keys cannot
be bound differently in one's ~/.inputrc.  However, this works in
other readline applications.

The bug is that the TUI uses curses' "nl" mode, which causes wgetch to
return the same value for both keys.  There is a "nonl" mode, but it
also affects output.

This patch fixes the bug by arranging to call nonl before reading a
key and then nl afterward.  This avoids any potential problem with
changing the output if gdb was to use nonl globally.

gdb/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	PR tui/28819:
	* tui/tui-io.c (gdb_wgetch): New function.
	(tui_mld_getc, tui_getc): Use it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update string expected from "help info proc" on gdb.base/info-proc.exp
@ 2018-10-06 16:25 sergiodj+buildbot
  2018-10-06 16:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-06 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e04caa70901ed44eb9537ccdbd286fe9b0a46ce2 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: e04caa70901ed44eb9537ccdbd286fe9b0a46ce2

Update string expected from "help info proc" on gdb.base/info-proc.exp

Commit 73f1bd769a5 ("Make the "info proc" documentation more
consistent.") updated the output from "help info proc", but forgot to
update the test on gdb.base/info-proc.exp.  This obvious patch does
that.

Checked-in as obvious.

gdb/testsuite/ChangeLog:
2018-10-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.base/info-proc.exp: Update string expected from "help info
	proc".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Set correct SHT_NOTE type for .note.spu_name
@ 2018-10-06  9:05 sergiodj+buildbot
  2018-10-06  9:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-06  9:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1c86cff1ecdd1027bd224d38f2161196e9955fa ***

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

Set correct SHT_NOTE type for .note.spu_name

	* elf32-spu.c (spu_elf_create_sections): Make .note.spu_name
	SHT_NOTE.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add -Wshadow=local
@ 2018-10-06  5:35 sergiodj+buildbot
  2018-10-06  5:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-06  5:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96643e35c077ed36c74b231ceefa4c30b3b02e28 ***

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

Add -Wshadow=local

This adds -Wshadow=local to configure.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.
	* warning.m4 (AM_GDB_WARNINGS): Add -Wshadow=local.

gdb/gdbserver/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Simple -Wshadow=local fixes
@ 2018-10-05 18:32 sergiodj+buildbot
  2018-10-05 19:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 18:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b926417afaea99ed17663e06d6654d0048536017 ***

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

Simple -Wshadow=local fixes

This fixes all the straightforward -Wshadow=local warnings in gdb.  A
few standard approaches are used here:

* Renaming an inner (or outer, but more commonly inner) variable;
* Lowering a declaration to avoid a clash;
* Moving a declaration into a more inner scope to avoid a clash,
  including the special case of moving a declaration into a loop header.

I did not consider any of the changes in this patch to be particularly
noteworthy, though of course they should all still be examined.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* ctf.c (SET_ARRAY_FIELD): Rename "u32".
	* p-valprint.c (pascal_val_print): Split inner "i" variable.
	* xtensa-tdep.c (xtensa_push_dummy_call): Declare "i" in loop
	header.
	* xstormy16-tdep.c (xstormy16_push_dummy_call): Declare "val" in
	more inner scope.
	* xcoffread.c (read_xcoff_symtab): Rename inner "symbol".
	* varobj.c (varobj_update): Rename inner "newobj",
	"type_changed".
	* valprint.c (generic_emit_char): Rename inner "buf".
	* valops.c (find_overload_match): Rename inner "temp".
	(value_struct_elt_for_reference): Declare "v" in more inner
	scope.
	* v850-tdep.c (v850_push_dummy_call): Rename "len".
	* unittests/array-view-selftests.c (run_tests): Rename inner
	"vec".
	* tui/tui-stack.c (tui_show_frame_info): Declare "i" in loop
	header.
	* tracepoint.c (merge_uploaded_trace_state_variables): Declare
	"tsv" in more inner scope.
	(print_one_static_tracepoint_marker): Rename inner
	"tuple_emitter".
	* tic6x-tdep.c (tic6x_analyze_prologue): Declare "inst" lower.
	(tic6x_push_dummy_call): Don't redeclare "addr".
	* target-float.c: Declare "dto" lower.
	* symtab.c (lookup_local_symbol): Rename inner "sym".
	(find_pc_sect_line): Rename inner "pc".
	* stack.c (print_frame): Don't redeclare "gdbarch".
	(return_command): Rename inner "gdbarch".
	* s390-tdep.c (s390_prologue_frame_unwind_cache): Renam inner
	"sp".
	* rust-lang.c (rust_internal_print_type): Declare "i" in loop
	header.
	* rs6000-tdep.c (ppc_process_record): Rename inner "addr".
	* riscv-tdep.c (riscv_push_dummy_call): Declare "info" in inner
	scope.
	* remote.c (remote_target::update_thread_list): Don't redeclare
	"tp".
	(remote_target::process_initial_stop_replies): Rename inner
	"thread".
	(remote_target::remote_parse_stop_reply): Don't redeclare "p".
	(remote_target::wait_as): Don't redeclare "stop_reply".
	(remote_target::get_thread_local_address): Rename inner
	"result".
	(remote_target::get_tib_address): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix undefined behavior, don't pass NULL to fwrite
@ 2018-10-05 17:22 sergiodj+buildbot
  2018-10-05 18:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 17:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f88d0c87c37d3a15fa6376335e8b0d1c79d85aa ***

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

Fix undefined behavior, don't pass NULL to fwrite

If a vector that we try to write using file_write is empty, we may end
up passing NULL to fwrite, which triggers UBSan:

  .../gdb/dwarf-index-write.c:73:14: runtime error: null pointer passed as argument 1, which is declared to never be null

Avoid it by skipping the write if the vector is empty.

gdb/ChangeLog:

	* dwarf-index-write.c (file_write): Don't write if the vector is
	empty.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix -Wshadow=local warning in sol_thread_target::wait
@ 2018-10-05 16:53 sergiodj+buildbot
  2018-10-06 10:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 16:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f8740dc531c006311ee9f7287180550fe46a94ab ***

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

Fix -Wshadow=local warning in sol_thread_target::wait

Rainer pointed out that -Wshadow=local broke the Solaris build.
This fixes it.

gdb/ChangeLog
2018-10-05  Tom Tromey  <tom@tromey.com>

	* sol-thread.c (sol_thread_target::wait): Rename inner
	"save_ptid".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] or1k: Add the l.adrp insn and supporting relocations
@ 2018-10-05 14:51 sergiodj+buildbot
  2018-10-05 16:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 14:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8e98e3692cec125b92c995d8f881d9bdf1fac00 ***

Author: Stafford Horne <shorne@gmail.com>
Branch: master
Commit: c8e98e3692cec125b92c995d8f881d9bdf1fac00

or1k: Add the l.adrp insn and supporting relocations

This patch adds the new instruction and relocation as per proposal:
   https://openrisc.io/proposals/ladrp

This is to be added to the spec in an upcoming revision.  The new instruction
l.adrp loads the page offset of the current instruction offset by
a 21-bit immediate shifted left 13-bits.  This is meant to be used with
a 13-bit lower bit page offset.  This allows us to free up the got
register r16.

  l.adrp  r3, foo
  l.ori   r4, r3, po(foo)
  l.lbz   r5, po(foo)(r3)
  l.sb    po(foo)(r3), r6

The relocations we add are:

 - BFD_RELOC_OR1K_PLTA26	For PLT jump relocation with PLT entry
   asm: plta()			implemented using l.ardp, meaning
				no need for r16 (the GOT reg)

 - BFD_RELOC_OR1K_GOT_PG21	Upper 21-bit Page offset got address
   asm: got()
 - BFD_RELOC_OR1K_TLS_GD_PG21	Upper 21-bit Page offset with TLS General
   asm: tlsgd()			Dynamic calculation
 - BFD_RELOC_OR1K_TLS_LDM_PG21	Upper 21-bit Page offset with TLS local
   asm: tlsldm()		dynamic calculation
 - BFD_RELOC_OR1K_TLS_IE_PG21	Upper 21-bit Page offset with TLS Initial
   asm: gottp() 		Executable calculation
 - BFD_RELOC_OR1K_PCREL_PG21	Default relocation for disp21 (l.adrp
				instructions)

 - BFD_RELOC_OR1K_LO13		low 13-bit page offset relocation
   asm: po()			i.e. mem loads, addi etc
 - BFD_RELOC_OR1K_SLO13		low 13-bit page offset relocation
   asm: po()			i.e. mem stores, with split immediate
 - BFD_RELOC_OR1K_GOT_LO13,	low 13-bit page offset with GOT calcs
   asm: gotpo()
 - BFD_RELOC_OR1K_TLS_GD_LO13	Lower 13-bit offset with TLS GD calcs
   asm: tlsgdpo()
 - BFD_RELOC_OR1K_TLS_LDM_LO13	Lower 13-bit offset with TLS LD calcs
   asm: tlsldmpo()
 - BFD_RELOC_OR1K_TLS_IE_LO13	Lower 13-bit offset with TLS IE calcs
   asm: gottppo()

bfd/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* bfd-in2.h: Regenerated.
	* elf32-or1k.c: (or1k_elf_howto_table): Fix formatting for
	R_OR1K_PLT26, Add R_OR1K_PCREL_PG21, R_OR1K_GOT_PG21,
	R_OR1K_TLS_GD_PG21, R_OR1K_TLS_LDM_PG21, R_OR1K_TLS_IE_PG21,
	R_OR1K_LO13, R_OR1K_GOT_LO13, R_OR1K_TLS_GD_LO13, R_OR1K_TLS_LDM_LO13,
	R_OR1K_TLS_IE_LO13, R_OR1K_SLO13, R_OR1K_PLTA26.
	(or1k_reloc_map): Add BFD_RELOC_OR1K_PCREL_PG21,
	BFD_RELOC_OR1K_GOT_PG21, BFD_RELOC_OR1K_TLS_GD_PG21,
	BFD_RELOC_OR1K_TLS_LDM_PG21, BFD_RELOC_OR1K_TLS_IE_PG21,
	BFD_RELOC_OR1K_LO13, BFD_RELOC_OR1K_GOT_LO13,
	BFD_RELOC_OR1K_TLS_GD_LO13, BFD_RELOC_OR1K_TLS_GD_LO13,
	BFD_RELOC_OR1K_TLS_LDM_LO13, BFD_RELOC_OR1K_TLS_IE_LO13,
	BFD_RELOC_OR1K_SLO13, BFD_RELOC_OR1K_PLTA26.
	(elf_or1k_link_hash_table): Add field saw_plta.
	(or1k_final_link_relocate): Add value calculations for new relocations.
	(or1k_elf_relocate_section): Add section relocations for new
	relocations.
	(or1k_write_plt_entry): New function.
	(or1k_elf_finish_dynamic_sections): Add support for PLTA relocations
	using new l.adrp instruction.  Cleanup PLT relocation code generation.
	* libbfd.h: Regenerated.
	* reloc.c: Add BFD_RELOC_OR1K_PCREL_PG21, BFD_RELOC_OR1K_LO13,
	BFD_RELOC_OR1K_SLO13, BFD_RELOC_OR1K_GOT_PG21, BFD_RELOC_OR1K_GOT_LO13,
	BFD_RELOC_OR1K_PLTA26, BFD_RELOC_OR1K_TLS_GD_PG21,
	BFD_RELOC_OR1K_TLS_GD_LO13, BFD_RELOC_OR1K_TLS_LDM_PG21,
	BFD_RELOC_OR1K_TLS_LDM_LO13, BFD_RELOC_OR1K_TLS_IE_PG21,
	BFD_RELOC_OR1K_TLS_IE_LO13.

cpu/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* or1k.opc (parse_disp26): Add support for plta() relocations.
	(parse_disp21): New function.
	(or1k_rclass): New enum.
	(or1k_rtype): New enum.
	(or1k_imm16_relocs): Define new PO and SPO relocation mappings.
	(parse_reloc): Add new po(), gotpo() and gottppo() for LO13 relocations.
	(parse_imm16): Add support for the new 21bit and 13bit relocations.
	* or1korbis.cpu (f-disp26): Don't assume SI.
	(f-disp21): New pc-relative 21-bit 13 shifted to right.
	(insn-opcode): Add ADRP.
	(l-adrp): New instruction.

gas/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* config/tc-or1k.c (or1k_apply_fix): Add BFD_RELOC_OR1K_TLS_GD_PG21,
	BFD_RELOC_OR1K_TLS_GD_LO13, BFD_RELOC_OR1K_TLS_LDM_PG21,
	BFD_RELOC_OR1K_TLS_LDM_LO13, BFD_RELOC_OR1K_TLS_IE_PG21,
	BFD_RELOC_OR1K_TLS_IE_LO13.
	* testsuite/gas/or1k/allinsn.s: Add test for l.adrp.
	* testsuite/gas/or1k/allinsn.d: Add test results for new
	instructions.
	* testsuite/gas/or1k/reloc-1.s: Add tests to generate
	R_OR1K_PLTA26, R_OR1K_GOT_PG21, R_OR1K_TLS_GD_PG21, R_OR1K_TLS_LDM_PG21,
	R_OR1K_TLS_IE_PG21, R_OR1K_LO13, R_OR1K_GOT_LO13, R_OR1K_TLS_GD_LO13,
	R_OR1K_TLD_LDM_LO13, R_OR1K_TLS_IE_LO13, R_OR1K_LO13, R_OR1K_SLO13
	relocations.
	* testsuite/gas/or1k/reloc-1.d: Add relocation results for
	tests.
	* testsuite/gas/or1k/reloc-2.s: Add negative tests for store to
	gotpo().
	* testsuite/gas/or1k/reloc-2.l: Add expected error test results.

ld/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* testsuite/ld-or1k/or1k.exp: Add test cases for plt generation.
	* testsuite/ld-or1k/plt1.dd: New file.
	* testsuite/ld-or1k/plt1.s: New file.
	* testsuite/ld-or1k/plt1.x.dd: New file.
	* testsuite/ld-or1k/plta1.dd: New file.
	* testsuite/ld-or1k/plta1.s: New file.
	* testsuite/ld-or1k/pltlib.s: New file.

include/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* elf/or1k.h (elf_or1k_reloc_type): Add R_OR1K_PCREL_PG21,
	R_OR1K_GOT_PG21, R_OR1K_TLS_GD_PG21, R_OR1K_TLS_LDM_PG21,
	R_OR1K_TLS_IE_PG21, R_OR1K_LO13, R_OR1K_GOT_LO13,
	R_OR1K_TLS_GD_LO13, R_OR1K_TLS_LDM_LO13, R_OR1K_TLS_IE_LO13,
	R_OR1K_SLO13, R_OR1K_PLTA26.

opcodes/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* or1k-asm.c: Regenerated.
	* or1k-desc.c: Regenerated.
	* or1k-desc.h: Regenerated.
	* or1k-dis.c: Regenerated.
	* or1k-ibld.c: Regenerated.
	* or1k-opc.c: Regenerated.
	* or1k-opc.h: Regenerated.
	* or1k-opinst.c: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] or1k: Fix messages for relocations in shared libraries
@ 2018-10-05 14:05 sergiodj+buildbot
  2018-10-05 15:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 14:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2c1801f6255a3f9f483ae2f07c7d7da0ddae4af ***

Author: Stafford Horne <shorne@gmail.com>
Branch: master
Commit: f2c1801f6255a3f9f483ae2f07c7d7da0ddae4af

or1k: Fix messages for relocations in shared libraries

Added checks include:

 - Do not allow relocations to global symbols using relocations which are
   meant for local symbol relocations.
 - Require the use of -fpic when compiling shared libraries.
 - Require zero addend for plt relocations.

bfd/ChangeLog:

yyyy-mm-dd  Richard Henderson  <rth@twiddle.net>

	* elf32-or1k.c (or1k_elf_relocate_section): Add error for unknown
	relocations.  Add error for non zero addend with plt and got
	relocations.  Add error for got and plt references against dynamic, non
	local, symbols.  Add error when linking non shared liraries with
	flag_pic.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [Arm, 3/3] Add Execution and Data Prediction instructions for AArch32
@ 2018-10-05 11:16 sergiodj+buildbot
  2018-10-06  8:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 11:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dad0c3bfb5e32ff3f2a03830dc189fe207c7ae00 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: dad0c3bfb5e32ff3f2a03830dc189fe207c7ae00

[Arm, 3/3] Add Execution and Data Prediction instructions for AArch32

This patch is part of the patch series to add support for ARMv8.5-A
extensions.

(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/exploration-tools)

This patch adds the Execution and Data Prediction Restriction
instructions (that is, cfprctx, dvprxtc, cpprctx). These are all
aliases to MCR and are disassembled as such.

This instruction is retrospectively made optional for all versions of
the architecture from ARMv8.0 to ARMv8.4 and is mandatory from
ARMv8.5.  Hence adding a new +predres for older versions of the
architecture.

*** include/ChangeLog ***

2018-10-05  Sudakshina Das  <sudi.das@arm.com>

	* opcode/arm.h (ARM_EXT2_PREDRES): New.
	(ARM_ARCH_V8_5A): Add ARM_EXT2_PREDRES by default.

*** gas/ChangeLog ***

2018-10-05  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-arm.c (arm_ext_predres): New.
	(insns): Add new cfprctx, dvprctx and cpprctx instructions.
	(arm_extensions): Add "predres".
	* doc/c-arm.texi: Document the above.
	* testsuite/gas/arm/predres-bad.d: New test.
	* testsuite/gas/arm/predres-bad.l: New test.
	* testsuite/gas/arm/predres.s: New test.
	* testsuite/gas/arm/predres1.d: New test.
	* testsuite/gas/arm/predres2.d: New test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [Arm, 2/3] Add instruction SB for AArch32
@ 2018-10-05 11:03 sergiodj+buildbot
  2018-10-06  7:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05 11:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7fadb25d6faf2665305016ceb4aeaeeb86015569 ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: 7fadb25d6faf2665305016ceb4aeaeeb86015569

[Arm, 2/3] Add instruction SB for AArch32

This patch is part of the patch series to add support for ARMv8.5-A
extensions.

(https://developer.arm.com/products/architecture/cpu-architecture/a-profile/exploration-tools)

This patch adds the instruction SB. This instruction is
retrospectively made optional for all versions of the architecture
from ARMv8.0 to ARMv8.4 and is mandatory from ARMv8.5. Hence adding a
new "+sb" for older archtectures.

*** include/ChangeLog ***

2018-10-05  Sudakshina Das  <sudi.das@arm.com>

	* opcode/arm.h (ARM_EXT2_SB): New.
	(ARM_ARCH_V8_5A): Add ARM_EXT2_SB by default.

*** opcodes/ChangeLog ***

2018-10-05  Sudakshina Das  <sudi.das@arm.com>

	* arm-dis.c (arm_opcodes): Add sb.
	(thumb32_opcodes): Likewise.

*** gas/ChangeLog ***

2018-10-05  Sudakshina Das  <sudi.das@arm.com>

	* config/tc-arm.c (arm_ext_sb): New.
	(insns): Add new sb instruction.
	(arm_extensions): Add "sb".
	* doc/c-arm.texi: Document the above.
	* testsuite/gas/arm/sb-bad.d: New test.
	* testsuite/gas/arm/sb-bad.l: New test.
	* testsuite/gas/arm/sb-thumb1.d: New test.
	* testsuite/gas/arm/sb-thumb2.d: New test.
	* testsuite/gas/arm/sb.s: New test.
	* testsuite/gas/arm/sb1.d: New test.
	* testsuite/gas/arm/sb2.d: New test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Shadowing fix in gdbscm_frame_read_var
@ 2018-10-05  6:49 sergiodj+buildbot
  2018-10-06  3:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  6:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d951f98b3c8bf202571327d8679ae30ca1da9fdc ***

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

Shadowing fix in gdbscm_frame_read_var

-Wshadow=local pointed out that the shadowing in gdbscm_frame_read_var
means that the ultimate call to read_var_value will always be passed
block==NULL.  The fix is to remove the inner declaration.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* guile/scm-frame.c (gdbscm_frame_read_var): Remove inner
	declaration of "block".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid shadowing in fdwalk
@ 2018-10-05  6:19 sergiodj+buildbot
  2018-10-06  2:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  6:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8c888478d517a39d8b0104857d573e47620a3d1 ***

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

Avoid shadowing in fdwalk

-Wshadow=local caught this buglet.  fdwalk redeclares "result" in the
inner scope, meaning that this function will always return 0, even on
error.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* common/filestuff.c (fdwalk): Remove inner declaration of
	"result".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid shadowing in linux-tdep.c
@ 2018-10-05  5:52 sergiodj+buildbot
  2018-10-05 23:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  5:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3fba72f7612c071f07fc7e65887bd1e8e056e272 ***

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

Avoid shadowing in linux-tdep.c

This is one of the uglier changes to avoid local shadowing.  Because
obstack.h uses statement expressions, in some cases a nested obstack
call will result in shadowing.  Rather than try to fix obstack.h, this
patch simply works around the one instance of this problem.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* linux-tdep.c (linux_make_mappings_corefile_notes): Introduce new
	variable "size".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use std::string in mdebugread.c
@ 2018-10-05  5:39 sergiodj+buildbot
  2018-10-05 21:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  5:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 795afcbbb4b6c9a47597b9da57221b1bf9fdc88f ***

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

Use std::string in mdebugread.c

This changes a couple of spots in mdebugread to use std::string rather
than manual management.  This is simpler, and also avoids shadowing by
renaming the variable in question.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* mdebugread.c (parse_partial_symbols): Use std::string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid shadowing in gdbserver
@ 2018-10-05  5:25 sergiodj+buildbot
  2018-10-05 20:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  5:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da4ae14a4d1614015f6e8d4a37df1b882806630a ***

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

Avoid shadowing in gdbserver

This fixes a few instances of shadowing in gdbserver.  These are all
simple fixes.

gdb/gdbserver/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* server.c (handle_status): Rename inner "thread".
	(process_serial_event): Declare "res" in 'm' case.
	* linux-low.c (last_thread_of_process_p, find_lwp_pid)
	(iterate_over_lwps): Rename inner "thread".
	(linux_qxfer_libraries_svr4): Rename inner "len".
	* gdbthread.h (find_thread_in_random): Rename inner "thread".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make complaint output prettier
@ 2018-10-05  2:29 sergiodj+buildbot
  2018-10-05  3:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  2:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6afcf761c2d8ffcb04ede75d1e670042e196bc5b ***

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

Make complaint output prettier

Currently complaints are not always printed with a newline.  For
example, when I run gdb on itself, I see output like:

    (gdb) set complaints 5
    (gdb) file ./gdb/gdb
    Reading symbols from ./gdb/gdb...DW_AT_low_pc 0x0 is zero for DIE at 0x437dd4 [in module /home/tromey/gdb/build/gdb/gdb]....debug_line address at offset 0x21bf9 is 0 [in module /home/tromey/gdb/build/gdb/gdb]...DW_AT_low_pc 0x0 is zero for DIE at 0x5a85dd [in module /home/tromey/gdb/build/gdb/gdb]....debug_line address at offset 0x2dc2d is 0 [in module /home/tromey/gdb/build/gdb/gdb]...DW_AT_low_pc 0x0 is zero for DIE at 0xab6033 [in module /home/tromey/gdb/build/gdb/gdb]....debug_line address at offset 0x4f683 is 0 [in module /home/tromey/gdb/build/gdb/gdb]...DW_AT_low_pc 0x0 is zero for DIE at 0x10028f0 [in module /home/tromey/gdb/build/gdb/gdb]....debug_line address at offset 0x75edf is 0 [in module /home/tromey/gdb/build/gdb/gdb]...DW_AT_low_pc 0x0 is zero for DIE at 0x1021364 [in module /home/tromey/gdb/build/gdb/gdb]....debug_line address at offset 0x76f62 is 0 [in module /home/tromey/gdb/build/gdb/gdb]...done.

That's one very long line.  I find it quite difficult to read that,
and I thought it would be better with some newlines, which is what
this patch does.  Now the output looks like:

    (gdb) file ./gdb
    Reading symbols from ./gdb...
    DW_AT_low_pc 0x0 is zero for DIE at 0x437dd4 [in module /home/tromey/gdb/build/gdb/gdb]
    .debug_line address at offset 0x21bf9 is 0 [in module /home/tromey/gdb/build/gdb/gdb]
    DW_AT_low_pc 0x0 is zero for DIE at 0x5a85dd [in module /home/tromey/gdb/build/gdb/gdb]
    .debug_line address at offset 0x2dc2d is 0 [in module /home/tromey/gdb/build/gdb/gdb]
    done.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	PR cli/22234:
	* complaints.c: Emit \n.

gdb/testsuite/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	PR cli/22234:
	* gdb.dwarf2/dw2-stack-boundary.exp: Update expected output.
	* gdb.gdb/complaints.exp (test_short_complaints): Update expected
	output.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use filtered printing when reading symbols
@ 2018-10-05  2:01 sergiodj+buildbot
  2018-10-05  2:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  2:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22068491adac735905948fd4c2e9aaacf9e22e06 ***

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

Use filtered printing when reading symbols

While working on this series, I found some unfiltered prints that
didn't make sense -- many things, like complaints, are filtered, while
their context (in this case the "Reading symbols ..."  messages) may
not be.

This patch changes some spots in symbol reading to use filtered
prints.  I think this is preferable overall; in fact I'd go farther
and say that unfiltered printing should just be removed.

One of these spots was not strictly related (the change to
dump_psymtab), but I left it in partly because it makes psymtab.c
"unfiltered-clean", and partly because it is an example of filtered
and unfiltered printing being mixed in the same function.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* symfile.c (symbol_file_add_with_addrs, symbol_file_clear)
	(separate_debug_file_exists, find_separate_debug_file)
	(add_symbol_file_command, reread_symbols, allocate_symtab)
	(allocate_compunit_symtab): Use filtered printing, not
	unfiltered.
	* psymtab.c (require_partial_symbols, dump_psymtab)
	(allocate_psymtab): Use filtered printing, not unfiltered.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix off-by-one error in complaint_internal
@ 2018-10-05  0:03 sergiodj+buildbot
  2018-10-05  1:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-05  0:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9fdd7193e7fd041e9ff311a69dc02aecef53070f ***

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

Fix off-by-one error in complaint_internal

complaint_internal had an off-by-one error, where it would allow one
extra complaint to be issued.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* complaints.c (complaint_internal): Correctly check complaint
	count.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/python] Fix cpychecker error in pspy_solib_name
@ 2018-10-04 22:49 sergiodj+buildbot
  2018-10-05 12:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 22:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c4481cc9bf9dfec3c35aaf5d95b08542ab8970b ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 5c4481cc9bf9dfec3c35aaf5d95b08542ab8970b

[gdb/python] Fix cpychecker error in pspy_solib_name

When using cpychecker, we run into:
...
gdb/python/py-progspace.c: \
  In function PyObject* pspy_solib_name(PyObject*, PyObject*):
gdb/python/py-progspace.c:370:25: error: Mismatching type in call to \
  PyArg_ParseTuple with format code "K" [-Werror]
   if (!PyArg_ParseTuple (args, GDB_PY_LLU_ARG, &pc))
  argument 3 ("&pc") had type
    "gdb_py_longest *" (pointing to 64 bits)
  but was expecting
    "long long unsigned int *" (pointing to 64 bits)
  for format code "K"
...

Fix this fixing the type of the variable.

Build and reg-tested on x86_64-linux.

2018-10-05  Tom de Vries  <tdevries@suse.de>

	* python/py-progspace.c (pspy_solib_name): Fix type mismatch in
	PyArg_ParseTuple call.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid pagination in attach.exp
@ 2018-10-04 22:09 sergiodj+buildbot
  2018-10-04 22:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fef1b2933d911476c52418ae7c207d94e13ebb97 ***

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

Avoid pagination in attach.exp

While re-testing the complaint series, I saw some unresolved tests in
attach.exp.  In particular, the tests were failing because the pager
was active.

This is partly a new problem, introduced because that series changes
some prints from unfiltered to filtered.  However, it is also a latent
bug, which you can see by shrinking your window very small and then
running the test.

This patch avoids the problem by passing -quiet to gdb and arranging
to set the window height and width in one other test.

Arguably instead of -quiet we should disable the pager during gdb's
welcome message.  I can do that if it seems desirable; but meanwhile
this patch is safe.

gdb/testsuite/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* gdb.base/attach.exp (test_command_line_attach_run): Use -quiet;
	set width and height to 0.
	(test_command_line_attach_run): Use -quiet.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Delete zero-size .tdata.dyn section.
@ 2018-10-04 21:49 sergiodj+buildbot
  2018-10-05  7:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 21:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e1b4df89cfa5171c52245d79434774f4b570ae1 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 3e1b4df89cfa5171c52245d79434774f4b570ae1

RISC-V: Delete zero-size .tdata.dyn section.

	bfd/
	* elfnn-riscv.c (riscv_elf_size_dynamic_sections): In dynobj->sections
	loop, handle htab->sdyntdata section.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Simplify complaints even more
@ 2018-10-04 21:36 sergiodj+buildbot
  2018-10-05  6:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 21:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ca8c39f059b30991b7090e7a662e4eb35d11133 ***

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

Simplify complaints even more

This removes the SHORT_FIRST_MESSAGE case from complaints, leaving
only a single case.  This allows for the removal of the last argument
to clear_complaints, and also simplifies complaint_internal, removing
an extra allocation in the process.

After this, the "./gdb -iex 'set complaint 1' -nx ./gdb" example will
show:

    Reading symbols from ./gdb...
    During symbol reading: .debug_ranges entry has start address of zero [in module /home/tromey/gdb/build/gdb/gdb]
    During symbol reading: DW_AT_low_pc 0x0 is zero for DIE at 0x17116c1 [in module /home/tromey/gdb/build/gdb/gdb]
    During symbol reading: .debug_line address at offset 0xa22f5 is 0 [in module /home/tromey/gdb/build/gdb/gdb]
    During symbol reading: unsupported tag: 'DW_TAG_unspecified_type'
    During symbol reading: const value length mismatch for 'std::ratio<1, 1000000000>::num', got 8, expected 0

This is a bit wordier but, I think, a bit more clear, as the form of
the message no longer depends on precisely when it was emitted.  In
particular if you compare to the output from the 'Clean up "Reading
symbols" output' patch, you can see that earlier gdb would switch from
the prefix-less form to the "During symbol reading" form at a point
that is meaningless to the user (specifically, after psymtab reading
is done and gdb tries to expand a CU).

2018-10-04  Tom Tromey  <tom@tromey.com>

	* symfile.c (syms_from_objfile_1, finish_new_objfile)
	(reread_symbols): Update.
	* complaints.h (clear_complaints): Remove argument.
	* complaints.c (enum complaint_series): Remove.
	(series): Remove global.
	(complaint_internal): Update.
	(clear_complaints): Remove argument.

gdb/testsuite/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	* gdb.cp/maint.exp (test_invalid_name): Update expected output.
	* gdb.gdb/complaints.exp (test_short_complaints): Remove.
	(test_initial_complaints, test_empty_complaints): Update.
	* gdb.dwarf2/dw2-stack-boundary.exp: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Only print "no debugging symbols" message once
@ 2018-10-04 21:23 sergiodj+buildbot
  2018-10-05  5:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 21:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e79497a160f38368688107520d7d1bd0aeafc1c7 ***

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

Only print "no debugging symbols" message once

The "no debugging symbols" message can be confusing in some cases, for
example when gdb finds separate debug info for an objfile, but the
separate debug info does not contain symbols.

For example:

    (gdb) file /bin/ls
    Reading symbols from /bin/ls...
    Reading symbols from .gnu_debugdata for /usr/bin/ls...
    (No debugging symbols found in .gnu_debugdata for /usr/bin/ls)
    (No debugging symbols found in /bin/ls)

Here, I think the second "no debugging symbols" message is redundant
and confusing.

This patch changes gdb to only emit this message when the objfile in
question does not have a separate debug file.  So, in the example
above, the output would now read:

    (gdb) file /bin/ls
    Reading symbols from /bin/ls...
    Reading symbols from .gnu_debugdata for /usr/bin/ls...
    (No debugging symbols found in .gnu_debugdata for /usr/bin/ls)

2018-10-04  Tom Tromey  <tom@tromey.com>

	* symfile.c (symbol_file_add_with_addrs): Do not print "no
	debugging symbols" message if there is a separate debug objfile.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Clean up "Reading symbols" output
@ 2018-10-04 21:11 sergiodj+buildbot
  2018-10-05  4:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 21:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3453e7e409f44a79ac6695589836edb8a49bfb08 ***

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

Clean up "Reading symbols" output

This patch is another attempt to fix PR cli/19551.  Unlike my previous
attempt, it doesn't print progress.  Instead, it just changes some
messages and adds newlines to make the output a bit nicer.

It also removes the "done." text that was previously emitted.  The
idea here is that it is obvious when gdb is done reading debug info,
as it starts then doing something else; and that while this message
did not provide much benefit to users, it did make it harder to make
the output clean.

After this change the output from "./gdb -iex 'set complaint 1' -nx ./gdb"
reads:

    Reading symbols from ./gdb...
    .debug_ranges entry has start address of zero [in module /home/tromey/gdb/build/gdb/gdb]
    DW_AT_low_pc 0x0 is zero for DIE at 0x17116c1 [in module /home/tromey/gdb/build/gdb/gdb]
    .debug_line address at offset 0xa22f5 is 0 [in module /home/tromey/gdb/build/gdb/gdb]
    During symbol reading, unsupported tag: 'DW_TAG_unspecified_type'.
    During symbol reading, const value length mismatch for 'std::ratio<1, 1000000000>::num', got 8, expected 0.

gdb/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	PR cli/19551:
	* symfile.c (symbol_file_add_with_addrs): Update output.
	* psymtab.c (require_partial_symbols): Update output.

gdb/testsuite/ChangeLog
2018-10-04  Tom Tromey  <tom@tromey.com>

	PR cli/19551:
	* lib/mi-support.exp (mi_gdb_file_cmd): Update.
	* lib/gdb.exp (gdb_file_cmd): Update.
	* gdb.stabs/weird.exp (print_weird_var): Update.
	* gdb.server/solib-list.exp: Update.
	* gdb.multi/remove-inferiors.exp (test_remove_inferiors): Update.
	* gdb.mi/mi-cli.exp: Update.
	* gdb.linespec/linespec.exp: Update.
	* gdb.dwarf2/dw2-stack-boundary.exp: Update.
	* gdb.dwarf2/dw2-objfile-overlap.exp: Update.
	* gdb.cp/cp-relocate.exp: Update.
	* gdb.base/sym-file.exp: Update.
	* gdb.base/relocate.exp: Update.
	* gdb.base/readnever.exp: Update.
	* gdb.base/print-symbol-loading.exp (test_load_core): Update.
	* gdb.base/kill-detach-inferiors-cmd.exp: Update.
	* gdb.base/dbx.exp (gdb_file_cmd): Update.
	* gdb.base/code_elim.exp: Update.
	* gdb.base/break-unload-file.exp (test_break): Update.
	* gdb.base/break-interp.exp (test_attach_gdb): Update.
	* gdb.base/break-idempotent.exp (force_breakpoint_re_set):
	Update.
	* gdb.base/attach.exp (do_attach_tests): Update.
	* gdb.base/sepdebug.exp: Update.
	* gdb.python/py-section-script.exp: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add self to gdb/MAINTAINERS
@ 2018-10-04 12:26 sergiodj+buildbot
  2018-10-04 21:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04 12:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f9bdf7fa52ba0d520647d0b69fe94e523fabf56 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 4f9bdf7fa52ba0d520647d0b69fe94e523fabf56

Add self to gdb/MAINTAINERS

Joel asked me to add myself to gdb/MAINTAINERS.  Done as follows, fixing two
incorrectly indented lines on the way.  Installed on master.

	* MAINTAINERS (Write After Approval): Add self.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid two uninitialized warnings from gcc
@ 2018-10-04  3:16 sergiodj+buildbot
  2018-10-04 19:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04  3:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 875e539851bb2702f3292f819e220545a8776242 ***

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

Avoid two uninitialized warnings from gcc

This avoids a couple of uninitialized warnings from gcc by
initializing the object in question.  The one in coffread.c seems like
it could be a latent bug.  The one in scm-value.c is harmless, but GCC
can't see that.

gdb/ChangeLog
2018-10-03  Tom Tromey  <tom@tromey.com>

	* guile/scm-value.c (gdbscm_value_to_string): Initialize
	"buffer_contents".
	* coffread.c (coff_symtab_read): Initialize "newobj".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Do not pass NULL to memcpy
@ 2018-10-04  3:01 sergiodj+buildbot
  2018-10-04  7:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04  3:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10657c047e4e0257440c80fda5f4e23a3452616c ***

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

Do not pass NULL to memcpy

-fsanitize=undefined pointed out a spot that passes NULL to memcpy,
which is undefined behavior according to the C standard.

gdb/ChangeLog
2018-10-03  Tom Tromey  <tom@tromey.com>

	* namespace.c (add_using_directive): Don't pass NULL to memcpy.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove struct keyword in range-based for
@ 2018-10-04  0:06 sergiodj+buildbot
  2018-10-04 18:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-04  0:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8634679f82df75cf482b0c0814c2b3865da91d22 ***

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

Remove struct keyword in range-based for

I get the following error with gcc 6.3.0:

/home/simark/src/binutils-gdb/gdb/dwarf2read.c: In function 'void read_func_scope(die_info*, dwarf2_cu*)':
/home/simark/src/binutils-gdb/gdb/dwarf2read.c:13838:12: error: types may not be defined in a for-range-declaration [-Werror]
       for (struct symbol *sym : template_args)
            ^~~~~~

Removing the struct keyword fixes it.

gdb/ChangeLog:

	* dwarf2read.c (read_func_scope): Remove struct keyword in
	range-based for.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Constraint disassembler and assembler changes.
@ 2018-10-03 23:50 sergiodj+buildbot
  2018-10-04  2:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 23:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bde90be2cddc06371ee80a258bf6855d0f346324 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: bde90be2cddc06371ee80a258bf6855d0f346324

AArch64: Constraint disassembler and assembler changes.

This patch wires in the new constraint verifiers into the assembler and
disassembler.  Because of this the MOVPRFX tests have to be split out from the
generic SVE tests into their own tests so warnings can be ignored.

These tests are only intended to test the encoding correctness and not the
constraints.

gas/

	* testsuite/gas/aarch64/sve-movprfx.d: New test.
	* testsuite/gas/aarch64/sve-movprfx.s: New test.
	* testsuite/gas/aarch64/sve.d: Refactor.
	* testsuite/gas/aarch64/sve.s: Refactor.
        * testsuite/gas/aarch64/sysreg-diagnostic.d: Update.

opcodes/

	* aarch64-asm.c (aarch64_opcode_encode): Apply constraint verifier.
	* aarch64-dis.c (print_operands): Refactor to take notes.
	(print_verifier_notes): New.
	(print_aarch64_insn): Apply constraint verifier.
	(print_insn_aarch64_word): Update call to print_aarch64_insn.
	* aarch64-opc.c (aarch64_print_operand): Remove attribute, update notes format.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid undefined behavior in ada_operator_length
@ 2018-10-03 23:29 sergiodj+buildbot
  2018-10-04 14:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 23:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e70ee0905a848701bb929a66f84ff2e212cfa81 ***

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

Avoid undefined behavior in ada_operator_length

-fsanitize=undefined pointed out this error:

    runtime error: load of value 2887952, which is not a valid value for type 'exp_opcode'

This happens in gdb.ada/complete.exp when processing "complete p
my_glob".  This does not parse, so the Ada parser throws an exception;
but then the code in parse_exp_in_context_1 accepts the expression
anyway.  However, as no elements have been written to the expression,
undefined behavior results.

The fix is to notice this case in parse_exp_in_context_1.  This patch
also adds an assertion to prefixify_expression to enforce this
pre-existing constraint.

gdb/ChangeLog
2018-10-03  Tom Tromey  <tom@tromey.com>

	* parse.c (prefixify_expression): Add assert.
	(parse_exp_in_context_1): Throw exception if the expression is
	empty.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid undefined behavior in read_signed_leb128
@ 2018-10-03 23:16 sergiodj+buildbot
  2018-10-04 13:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 23:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dd1b46077b2ae7331f274f7888733de5166445c ***

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

Avoid undefined behavior in read_signed_leb128

-fsanitize=undefined pointed out that read_signed_leb128 had an
undefined left-shift when processing the final byte of a 64-bit leb:

    runtime error: left shift of 127 by 63 places cannot be represented in type 'long int'

and an undefined negation:

    runtime error: negation of -9223372036854775808 cannot be represented in type 'long int'; cast to an unsigned type to negate this value to itself

Both of these problems are readily avoided by havinng
read_signed_leb128 work in an unsigned type, and then casting to the
signed type at the return.

gdb/ChangeLog
2018-10-03  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (read_signed_leb128): Work in ULONGEST.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid undefined behavior in extract_integer
@ 2018-10-03 22:40 sergiodj+buildbot
  2018-10-04 10:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 22:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0101665f864383147448c5871a67286a3f7a9a28 ***

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

Avoid undefined behavior in extract_integer

-fsanitize=undefined showed that extract_integer could left-shift a
negative value, which is undefined.  This patch fixes the problem by
doing all the work in an unsigned type.  This relies on
implementation-defined behavior, but I tend to think we are on safe
ground there.  (Also, if need be, violations of this could probably be
detected, either by configure or by a static_assert.)

gdb/ChangeLog
2018-10-03  Tom Tromey  <tom@tromey.com>

	* findvar.c (extract_integer): Do work in an unsigned type.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Add SVE constraints verifier.
@ 2018-10-03 22:39 sergiodj+buildbot
  2018-10-04  1:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 22:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a68f4cd235a36776d3d9fea7291163b8d8e35869 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: a68f4cd235a36776d3d9fea7291163b8d8e35869

AArch64: Add SVE constraints verifier.

This patch adds the verification rules for move prefix constraints.

The Arm SVE instruction MOVPRFX introduces[1] constraints on the instruction at
PC+4. Particularly the following constraints are handled by this patch

* MOVPRFX must be followed by an instruction.
* MOVPRFX can only be followed by non-layout altering directives.
* MOVPRFX destination register MUST be used as the destination register in the
  instruction at PC+4, and is not allowed to be used in any other position other than
  destructive input.  This includes registers that architecturally overlap. e.g. x1
  should be treated as z1.
* MOVPRFX must be followed by a restricted set of SVE instructions.
* The size of the destination register of MOVPRFX must be equal to that of
  the operation at PC+4.
* The predicate register and operation of MOVPRFX must match that of the instruction
  at PC+4
* The predicated instruction at PC+4 must use the merging predicate.
* Architectural aliases and pseudo-instructions need to be supported as well.
* MOVPRFX cannot be the last instruction in a sequence

Any failure to adhere to any of these constrains will emit an assembly warning
and a disassembly note.

[1] https://developer.arm.com/docs/ddi0584/latest/arm-architecture-reference-manual-supplement-the-scalable-vector-extension-sve-for-armv8-a

include/

	* opcode/aarch64.h (aarch64_inst): Remove.
	(enum err_type): Add ERR_VFI.
	(aarch64_is_destructive_by_operands): New.
	(init_insn_sequence): New.
	(aarch64_decode_insn): Remove param name.

opcodes/

	* aarch64-opc.c (init_insn_block): New.
	(verify_constraints, aarch64_is_destructive_by_operands): New.
	* aarch64-opc.h (verify_constraints): New.

gas/

        * config/tc-aarch64.c (output_operand_error_report): Order warnings.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ELF: Group PT_NOTE segments by section alignments
@ 2018-10-03 20:36 sergiodj+buildbot
  2018-10-04  4:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23e463ed7c0d289e2291aaefd576bf02efd98df8 ***

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

ELF: Group PT_NOTE segments by section alignments

Alignments of SHT_NOTE sections can be 8 bytes for 64-bit ELF files.  We
should put all adjacent SHT_NOTE sections with the same section alignment
into a single PT_NOTE segment even when the section alignment != 4 bytes.
Also check SHT_NOTE section type instead of section name.

	PR ld/23658
	* elf.c (get_program_header_size): Put all adjacent SHT_NOTE
	sections with the same section alignment into a single PT_NOTE
	segment.  Check SHT_NOTE section type instead of section name.
	(_bfd_elf_map_sections_to_segments): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Wire through instr_sequence
@ 2018-10-03 19:21 sergiodj+buildbot
  2018-10-03 21:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e84b55d8f973b011f55f604a76c2d1d989d0b6b ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 7e84b55d8f973b011f55f604a76c2d1d989d0b6b

AArch64: Wire through instr_sequence

This patch introduces aarch64_instr_sequence which is a structure similar to IT
blocks on Arm in order to track instructions that introduce a constraint or
dependency on instruction 1..N positions away from the instruction that opened
the block.

The struct is also wired through to the locations that require it.

gas/

	* config/tc-aarch64.c (now_instr_sequence):
	(*insn_sequence, now_instr_sequence): New.
	(output_operand_error_record, do_encode): Add insn_sequence.
	(md_assemble): Update insn_sequence.
	(try_to_encode_as_unscaled_ldst, fix_mov_imm_insn, fix_insn):
	Pass insn_sequence.
	* config/tc-aarch64.h (struct aarch64_segment_info_type):
	Add insn_sequence.

include/

	* opcode/aarch64.h (struct aarch64_instr_sequence): New.
	(aarch64_opcode_encode): Use it.

opcodes/

	* aarch64-asm.c (aarch64_opcode_encode): Add insn_sequence.
	* aarch64-dis.c (insn_sequence): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] AArch64: Mark sve instructions that require MOVPRFX constraints
@ 2018-10-03 18:22 sergiodj+buildbot
  2018-10-03 19:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eae424aef0b14e1765602088ac866b95d14d4a22 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: eae424aef0b14e1765602088ac866b95d14d4a22

AArch64: Mark sve instructions that require MOVPRFX constraints

This patch series is to allow certain instructions such as the SVE MOVPRFX
instruction to apply a constraint/dependency on the instruction at PC+4.

This patch starts this off by marking which instructions impose the constraint
and which instructions must adhere to the constraint.  This is done in a
generic way by extending the verifiers.

* The constraint F_SCAN indicates that an instruction opens a sequence and imposes
a constraint on an instructions following it.  The length of the sequence depends
on the instruction itself and it handled in the verifier code.

* The C_SCAN_MOVPRFX flag is used to indicate which constrain the instruction is
checked against.  An instruction with both F_SCAN and C_SCAN_MOVPRFX starts a
block for the C_SCAN_MOVPRFX instruction, and one with only C_SCAN_MOVPRFX must
adhere to a previous block constraint is applicable.

The SVE instructions in this list have been marked according to the SVE
specification[1].

[1] https://developer.arm.com/docs/ddi0584/latest/arm-architecture-reference-manual-supplement-the-scalable-vector-extension-sve-for-armv8-a

include/

	* opcode/aarch64.h (struct aarch64_opcode): Add constraints,
	extend flags field size.
	(F_SCAN, C_SCAN_MOVPRFX, C_MAX_ELEM): New.

opcodes/

	* aarch64-tbl.h (CORE_INSN, __FP_INSN, SIMD_INSN, CRYP_INSN, _CRC_INSN,
	_LSE_INSN, _LOR_INSN, RDMA_INSN, FF16_INSN, SF16_INSN, V8_2_INSN,
	_SVE_INSN, V8_3_INSN, CNUM_INSN, RCPC_INSN, SHA2_INSN, AES_INSN,
	V8_4_INSN, SHA3_INSN, SM4_INSN, FP16_V8_2_INSN, DOT_INSN): Initialize
	constraints.
	(_SVE_INSNC): New.
	(struct aarch64_opcode): (fjcvtzs, ldpsw, ldpsw, esb, psb): Initialize
	constraints.
	(movprfx): Change _SVE_INSN into _SVE_INSNC, add C_SCAN_MOVPRFX and
	F_SCAN flags.
	(msb, mul, neg, not, orr, rbit, revb, revh, revw, sabd, scvtf,
	sdiv, sdivr, sdot, smax, smin, smulh, splice, sqadd, sqdecd, sqdech,
	sqdecp, sqdecw, sqincd, sqinch, sqincp, sqincw, sqsub, sub, subr, sxtb,
	sxth, sxtw, uabd, ucvtf, udiv, udivr, udot, umax, umin, umulh, uqadd,
	uqdecd, uqdech, uqdecp, uqdecw, uqincd, uqinch, uqincp, uqincw, uqsub,
	uxtb, uxth, uxtw, bic, eon, orn, mov, fmov): Change _SVE_INSN into _SVE_INSNC and add
	C_SCAN_MOVPRFX and C_MAX_ELEM constraints.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Skip gdb ifunc tests on targets that don't support this feature.
@ 2018-10-03 16:44 sergiodj+buildbot
  2018-10-03 17:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 16:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ca98345e0b3fda08ae79e4cb07632eab84ef6ef2 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: ca98345e0b3fda08ae79e4cb07632eab84ef6ef2

Skip gdb ifunc tests on targets that don't support this feature.

2018-10-03  Sandra Loosemore  <sandra@codesourcery.com>

	* lib/gdb.exp (skip_ifunc_tests): New.
	* gdb.base/gnu-ifunc.exp: Skip if no ifunc support.  Handle
	other compile failures.
	* gdb.compile/compile-ifunc.exp: Skip if no ifunc support.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix the handling of inlined frames in DWARF debug info.
@ 2018-10-03 11:23 sergiodj+buildbot
  2018-10-03 12:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 11:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8d3f93237d77f76d14e09e44bc770ce9428b0e4 ***

Author: Millan Wolff <mail@milianw.de>
Branch: master
Commit: c8d3f93237d77f76d14e09e44bc770ce9428b0e4

Fix the handling of inlined frames in DWARF debug info.

	PR 23715
	* dwarf2.c (find_abstract_instance): Allow recursive invocations
	of find_abstract_instance to override the name variable.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Updated Portuguese translations for the bfd/ and binutils/ subdirectories.
@ 2018-10-03 10:16 sergiodj+buildbot
  2018-10-03 11:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03 10:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e90d6d2c2f84abf25efc669e10efa3ae29b1039 ***

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

Updated Portuguese translations for the bfd/ and binutils/ subdirectories.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make print_insn_s12z public.
@ 2018-10-03  9:01 sergiodj+buildbot
  2018-10-03 10:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03  9:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 007d2fe43e27fa38a0bc1e22c5f5fb4ee945830d ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 007d2fe43e27fa38a0bc1e22c5f5fb4ee945830d

Make print_insn_s12z public.

Gdb can use this function in its stack unwinder.

* include/dis-asm.h (print_insn_s12z): Add declaration.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use pulongest in aarch64-linux-tdep.c
@ 2018-10-03  1:47 sergiodj+buildbot
  2018-10-03  2:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-03  1:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2398abf8bca3563ddab4bd41c710af8027fe2919 ***

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

Use pulongest in aarch64-linux-tdep.c

I tried a build on macOS today and it failed due to a mismatch between
the printf format and the type in aarch64-linux-tdep.c.  This patch
fixes the problem by using pulongest and %s rather than %ld.

gdb/ChangeLog
2018-10-02  Tom Tromey  <tom@tromey.com>

	* aarch64-linux-tdep.c (aarch64_linux_sigframe_init): Use pulongest.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add fence.tso instruction
@ 2018-10-02 15:42 sergiodj+buildbot
  2018-10-02 17:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-02 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64a336ac134ebd7f9452a7088e90e29551465251 ***

Author: Palmer Dabbelt <palmer@sifive.com>
Branch: master
Commit: 64a336ac134ebd7f9452a7088e90e29551465251

RISC-V: Add fence.tso instruction

The RISC-V memory model has been ratified, and it includes an additional
fence: "fence.tso".  This pseudo instruction extends one of the
previously reserved full fence patterns to be less restrictive, and
therefor will execute correctly on all existing microarchitectures.
Thus there is no reason to allow this instruction to be disabled (or
unconverted to a full fence), so it's just unconditionally allowed.

I've added a test case for GAS to check that "fence.tso" correctly
assembles on rv32i-based targets.  I checked to see that "fence.tso"
appears in "gas.log", but that's the only testing I've done.

gas/ChangeLog

2018-10-02  Palmer Dabbelt  <palmer@sifive.com>

        * testsuite/gas/riscv/fence-tso.d: New file.
        * testsuite/gas/riscv/fence-tso.s: Likewise.

include/ChangeLog

2018-10-02  Palmer Dabbelt  <palmer@sifive.com>

        * opcode/riscv-opc.h (MATCH_FENCE_TSO): New define.
        (MASK_FENCE_TSO): Likewise.

opcodes/ChangeLog

2018-10-02  Palmer Dabbelt  <palmer@sifive.com>

        * riscv-opc.c (riscv_opcodes) <fence.tso>: New opcode.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allow remote debugging over a Unix local domain socket.
@ 2018-10-02 14:34 sergiodj+buildbot
  2018-10-02 16:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-02 14:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1168a2f66553cd4730931cf59e3be8378a1a03f ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: c1168a2f66553cd4730931cf59e3be8378a1a03f

Allow remote debugging over a Unix local domain socket.

Extend the "target remote" and "target extended-remote" commands
such that if the filename provided is a Unix local domain (AF_UNIX)
socket, then it'll be treated as such, instead of trying to open
it as if it were a character device.

gdb/ChangeLog:
	* NEWS: Mention changed commands.
	* ser-uds.c: New file.
	* configure.ac (SER_HARDWIRE): Add ser-uds.o.
	* configure: Regenerate.
	* Makefile.in: Add new file.
	* serial.c (serial_open): Check if filename is a socket
	  and lookup the appropriate interface accordingly.

gdb/doc/ChangeLog:
	* gdb.texinfo (Remote Connection Commands): Describe
	  the changes to target remote and target extended-remote
	  relating to Unix domain sockets.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64: Move pseudo defines to header
@ 2018-10-02  0:25 sergiodj+buildbot
  2018-10-02  3:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-02  0:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c74e7cb96ffc525b0218cd329c292aacb16f94f8 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: c74e7cb96ffc525b0218cd329c292aacb16f94f8

Aarch64: Move pseudo defines to header

gdb/
	* aarch64-tdep.c (AARCH64_Q0_REGNUM): Move to here.
	(AARCH64_D0_REGNUM): Likewise.
	(AARCH64_S0_REGNUM): Likewise.
	(AARCH64_H0_REGNUM): Likewise.
	(AARCH64_B0_REGNUM): Likewise.
	(AARCH64_SVE_V0_REGNUM): Likewise.
	* arch/aarch64.h (AARCH64_Q0_REGNUM): Move from here.
	(AARCH64_D0_REGNUM): Likewise.
	(AARCH64_S0_REGNUM): Likewise.
	(AARCH64_H0_REGNUM): Likewise.
	(AARCH64_B0_REGNUM): Likewise.
	(AARCH64_SVE_V0_REGNUM): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ancient workaround
@ 2018-10-01 16:56 sergiodj+buildbot
  2018-10-01 19:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12b164e9a96f75ffd030d04a7633dfbb64862806 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 12b164e9a96f75ffd030d04a7633dfbb64862806

Remove ancient workaround

This commit removes a workaround for a bug in glibc 2.1.3, which
was released 2000-02-24 and superseded 2000-11-09.

gdb/ChangeLog:

	* gdb_proc_service.h (gdb_prfpregset_t): Remove typedef.
	* proc-service.c (ps_lgetfpregs, ps_lsetfpregs): Use
	prfpregset_t instead of gdb_prfpregset_t.
	* configure.ac (PRFPREGSET_T_BROKEN): Remove check.
	* configure, config.in: Rebuild.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add aarch64-sighandler-regs.exp test
@ 2018-10-01 15:05 sergiodj+buildbot
  2018-10-02  6:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 15:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6bb8890e2ccf2b1ae7860fcb6fe4579c4aa9ebf6 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 6bb8890e2ccf2b1ae7860fcb6fe4579c4aa9ebf6

Add aarch64-sighandler-regs.exp test

Add Aarch64 test to check register values of a previous frame
can be shown correctly across a signal.

gdb/testsuite/ChangeLog:

	* gdb.arch/aarch64-sighandler-regs.c: New test.
	* gdb.arch/aarch64-sighandler-regs.exp: New file.
	* lib/gdb.exp (skip_aarch64_sve_tests): New proc.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Fixed issue with DTSOFF relocs.
@ 2018-10-01 13:46 sergiodj+buildbot
  2018-10-02  2:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 13:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 714e9a954a2e4123dcb26bb8da850e1344de4f5f ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 714e9a954a2e4123dcb26bb8da850e1344de4f5f

[ARC] Fixed issue with DTSOFF relocs.

Inserted offset in final section in the GOT entry of type DTSOFF soon to be
relocated by the dynamic loader.

bfd/
2018-09-06  Cupertino Miranda <cmiranda@synopsys.com>

	* arc-got.h (relocate_fix_got_relocs_for_got_info): Changed. Take TLS
	    section alignment in consideration for this relocation.
	* elf32-arc.c (FINAL_SECTSTART): Added this formula macro.
	  (ARC_TLS_DTPOFF) Updated reloc to use new created macro instead.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add workaround from gdbserver's gdb_proc_service.h to GDB
@ 2018-10-01 13:28 sergiodj+buildbot
  2018-10-01 15:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 13:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43b7e92b0c73d693d3b656b84b2a1181e40477ca ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 43b7e92b0c73d693d3b656b84b2a1181e40477ca

Add workaround from gdbserver's gdb_proc_service.h to GDB

This commit adds a workaround from gdbserver's gdb_proc_service.h
to GDB's.  It doesn't seem to have been needed on any glibc as far
back as 2001, but it's possibly required for other C libraries so
I've retained it.

gdb/ChangeLog:

	* configure.ac: Check if sys/procfs.h defines elf_fpregset_t.
	(AC_CHECK_HEADERS): Check for linux/elf.h.
	* configure, config.in: Rebuild.
	* gdb_proc_service.h: Include linux/elf.h if sys/procfs.h
	doesn't define elf_fpregset_t.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] PLT information was still being generated when symbol was forced_local.
@ 2018-10-01 13:03 sergiodj+buildbot
  2018-10-02  0:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 13:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab16fcd743b8fc963e736f7d00e3c2f039ce0d56 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: ab16fcd743b8fc963e736f7d00e3c2f039ce0d56

[ARC] PLT information was still being generated when symbol was forced_local.

A change upstream reveiled this issue, triggering an assert when linking glibc.

bfd/
2018-03-01  Cupertino Miranda <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_check_relocs): Changed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Make sure global symbol is not an indirect or warning.
@ 2018-10-01 12:31 sergiodj+buildbot
  2018-10-01 23:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 12:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2936af90155cf7f7647b4886dc5b9568d15ca298 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: 2936af90155cf7f7647b4886dc5b9568d15ca298

[ARC] Make sure global symbol is not an indirect or warning.

Problem identified in the context of glibc with latest upstream binutils.
Dynamic symbol space was being reserved but, no actual information for the
symbol was being set. Data for the symbol was kept initialized with -1.
No easy test case was possible to be created.

bfd/
2018-03-01  Cupertino Miranda <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_check_relocs): Changed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Improved robustness. Return FALSE in case of NULL pointer.
@ 2018-10-01 12:17 sergiodj+buildbot
  2018-10-01 21:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 12:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c834917fda58d9e4cd72b67f7793e2f429ccce57 ***

Author: Cupertino Miranda <cmiranda@synopsys.com>
Branch: master
Commit: c834917fda58d9e4cd72b67f7793e2f429ccce57

[ARC] Improved robustness. Return FALSE in case of NULL pointer.

bfd/
2018-03-01  Cupertino Miranda <cmiranda@synopsys.com>

	* elf32-arc.c (elf_arc_finish_dynamic_symbol) Return FALSE in case
	arc_htab is NULL.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move duplicated code to common/gdb_proc_service.h
@ 2018-10-01 11:02 sergiodj+buildbot
  2018-10-01 17:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01 11:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c619dbdae11bead6f85863b7ce25f8b8610c59d ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 7c619dbdae11bead6f85863b7ce25f8b8610c59d

Move duplicated code to common/gdb_proc_service.h

This commit moves now-identical code from gdb/gdb_proc_service.h
and gdb/gdbserver/gdb_proc_service.h into the new shared file
gdb/common/gdb_proc_service.h.

gdb/ChangeLog:

	* common/gdb_proc_service.h: New file, factored out from...
	* gdb_proc_service.h: Moved common code to the above file.
	* Makefile.in (HFILES_NO_SRCDIR): Add the above new file.

gdb/gdbserver/ChangeLog:

	* gdb_proc_service.h: Moved common code to
	common/gdb_proc_service.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Copy configure option documentation to gdb.texinfo
@ 2018-10-01  9:54 sergiodj+buildbot
  2018-10-01 10:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01  9:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a95746f91769c0f65e9393ff83aad0871d1a666b ***

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

Copy configure option documentation to gdb.texinfo

I realized that while I'd updated the README, I didn't update
gdb.texinfo to document the options to configure.

This patch copies the text from README into gdb.texinfo, adding
Texinfo markup.

gdb/ChangeLog
2018-10-01  Tom Tromey  <tom@tromey.com>

	* README: Minor change.

gdb/doc/ChangeLog
2018-10-01  Tom Tromey  <tom@tromey.com>

	* gdb.texinfo (Configure Options): Document configure options.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Don't check HAVE_UNISTD_H
@ 2018-10-01  9:23 sergiodj+buildbot
  2018-10-01 12:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-10-01  9:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4176f14d9c9e509425bffc01404c751e238b1f01 ***

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

Don't check HAVE_UNISTD_H

I noticed some spots that were checking HAVE_UNISTD_H.  There is no
need to do this, as <unistd.h> is unconditionally included in many
places in gdb.  This sort of cleanup was done once before, in 2013:

    2013-07-01  Pedro Alves  <palves@redhat.com>

	    * defs.h: Don't check HAVE_UNISTD_H before including <unistd.h>.
	    (STDIN_FILENO, STDOUT_FILENO, STDERR_FILENO): Delete.
	    * tracepoint.c: Don't check HAVE_UNISTD_H before including
	    <unistd.h>.

HAVE_UNISTD_H seems to come from gnulib, so there are still mentions
of it in the source.

gdb/ChangeLog
2018-10-01  Tom Tromey  <tom@tromey.com>

	* unittests/scoped_mmap-selftests.c: Don't check HAVE_UNISTD_H.
	* unittests/scoped_fd-selftests.c: Don't check HAVE_UNISTD_H.
	* common/scoped_fd.h: Don't check HAVE_UNISTD_H.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: For PCREL_LO12, fix addend handling in auipc lookup.
@ 2018-09-29 15:33 sergiodj+buildbot
  2018-09-30 17:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-29 15:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a05f27b68934c2ea3efa028a0af2cd968db1bd2d ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: a05f27b68934c2ea3efa028a0af2cd968db1bd2d

RISC-V: For PCREL_LO12, fix addend handling in auipc lookup.

	bfd/
	* elfnn-riscv.c (_bfd_riscv_relax_pc) <R_RISCV_PCREL_LO12_I>: New local
	hi_sec_off which is symbol address with addend subtracted.  Use in
	riscv_find_pcgp_hi_reloc and riscv_record_pcgp_lo_reloc calls.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Allow pcrel_lo addends, error on addend overflow.
@ 2018-09-29 14:35 sergiodj+buildbot
  2018-09-30 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-29 14:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 551703cfd409faca433626a0af077a43011381b7 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 551703cfd409faca433626a0af077a43011381b7

RISC-V: Allow pcrel_lo addends, error on addend overflow.

	bfd/
	* elfnn-riscv.c (riscv_resolve_pcrel_lo_relocs): Add check for reloc
	overflow with addend.  Use reloc_dangerous instead of reloc_overflow.
	Add strings for the two errors handled here.
	(riscv_elf_relocate_section) In case R_RISCV_PCREL_LO12_I, rewrite
	comment.  Only give error with addend when used with section symbol.
	In case bfd_reloc_dangerous, update error string.

	ld/
	* testsuite/ld-riscv-elf/ld-riscv-elf.exp: Run pcrel-lo-addend-2.
	* testsuite/ld-riscv/elf/ld-riscv-elf/pcrel-lo-addend-2.d: New.
	* testsuite/ld-riscv/elf/ld-riscv-elf/pcrel-lo-addend-2.s: New.
	* testsuite/ld-riscv/elf/ld-riscv-elf/pcrel-lo-addend.d: Update name
	and error string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add "const" to a few locals in gdb
@ 2018-09-28 22:16 sergiodj+buildbot
  2018-09-28 22:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-28 22:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5a9bfbebec0a42d3c5b4fe3b7a62bd31cecc440 ***

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

Add "const" to a few locals in gdb

I noticed that some code in gdb was doing:

    char *mumble = getenv (...)

However, using "const char *" here would be clearer.
This patch fixes the instances I could readily build.

Tested by rebuilding.

gdb/ChangeLog
2018-09-24  Tom Tromey  <tom@tromey.com>

	* common/pathstuff.c (get_standard_cache_dir): Make
	"xdg_cache_home" and "home" const.
	* top.c (init_history): Make "tmpenv" const.
	* main.c (get_init_files): Make "homedir" const.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix PR gdb/20948: --write option to GDB causes segmentation fault
@ 2018-09-28 12:23 sergiodj+buildbot
  2018-09-28 23:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-28 12:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db72737006fc383cb8838bf7f3dc8e641e60c38f ***

Author: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Branch: master
Commit: db72737006fc383cb8838bf7f3dc8e641e60c38f

Fix PR gdb/20948: --write option to GDB causes segmentation fault

When opening a BFD for update, as gdb --write does, modifications to
anything but the contents of sections is restricted.

Do not try to write back any ELF headers in this case.

bfd/ChangeLog
2018-09-24  Jozef Lawrynowicz  <jozef.l@mittosystems.com>

	PR gdb/20948
	* elf.c (_bfd_elf_write_object_contents): Return from function
	early if abfd->direction == both_direction.

gdb/testsuite/ChangeLog
2018-09-24  Jozef Lawrynowicz  <jozef.l@mittosystems.com>

	PR gdb/20948
	* gdb.base/write_mem.exp: New test.
	* gdb.base/write_mem.c: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Check for negative argument in Type.template_argument
@ 2018-09-28  0:31 sergiodj+buildbot
  2018-09-27 11:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-28  0:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fd3ba736db19d4c7cd928f3735329339a8c8ef47 ***

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

Check for negative argument in Type.template_argument

typy_template_argument did not check if the template argument was
non-negative.  A negative value could cause a gdb crash.

2018-09-23  Tom Tromey  <tom@tromey.com>

	PR python/17284:
	* python/py-type.c (typy_template_argument): Check for negative
	argument number.

gdb/testsuite/ChangeLog
2018-09-23  Tom Tromey  <tom@tromey.com>

	PR python/17284:
	* gdb.python/py-template.exp (test_template_arg): Add test for
	negative template argument number.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Report Python errors coming from gdb.post_event
@ 2018-09-26 16:59 sergiodj+buildbot
  2018-09-27 10:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-26 16:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39a24317ac65837663ce1e1b0adcf880758ddc8e ***

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

Report Python errors coming from gdb.post_event

PR python/14062 points out that errors coming from the gdb.post_event
callback are not reported.  This can make it hard to understand why
your Python code in gdb isn't working.

Because users have control over whether exceptions are printed at all,
it seems good to simply have post_event report errors in the usual
way.

2018-09-23  Tom Tromey  <tom@tromey.com>

	PR python/14062:
	* python/python.c (gdbpy_run_events): Do not ignore exceptions.

gdb/testsuite/ChangeLog
2018-09-23  Tom Tromey  <tom@tromey.com>

	PR python/14062:
	* gdb.python/python.exp: Add test for post_event error.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Preserve sign when converting gdb.Value to Python int
@ 2018-09-26 14:14 sergiodj+buildbot
  2018-09-26 17:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-26 14:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1c1e54f6b4b6de83aa3f31e6584f5bb4d6242930 ***

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

Preserve sign when converting gdb.Value to Python int

PR python/20126 points out that sometimes the conversion of a
gdb.Value can result in a negative Python integer.  This happens
because valpy_int does not examine the signedness of the value's type.

gdb/ChangeLog
2018-09-23  Tom Tromey  <tom@tromey.com>

	PR python/20126:
	* python/py-value.c (valpy_int): Respect type sign.

gdb/testsuite/ChangeLog
2018-09-23  Tom Tromey  <tom@tromey.com>

	PR python/20126:
	* gdb.python/py-value.exp (test_value_numeric_ops): Add
	signed-ness conversion tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix incorrect extraction of signed constants in nios2 disassembler.
@ 2018-09-26 12:49 sergiodj+buildbot
  2018-09-26 13:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-26 12:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6031ac352c05c5c9f44e24fa1c5a8222a7a7d02d ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 6031ac352c05c5c9f44e24fa1c5a8222a7a7d02d

Fix incorrect extraction of signed constants in nios2 disassembler.

2018-09-23  Sandra Loosemore  <sandra@codesourcery.com>

	opcodes/
	* nios2-dis.c (nios2_print_insn_arg): Make sure signed conversions
	are used when extracting signed fields and converting them to
	potentially 64-bit types.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Also recognize __sighndlr on Solaris/x86
@ 2018-09-25 21:14 sergiodj+buildbot
  2018-09-26 11:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-25 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1db88d2272a776200db950c2af46e64e98ef056b ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 1db88d2272a776200db950c2af46e64e98ef056b

Also recognize __sighndlr on Solaris/x86

Unlike Solaris/SPARC, the __sighndlr function isn't recognized as part
of a signal handler, causing a couple of testcases to fail.

The following patch fixes that.  A followup patch will move this to
common code to avoid such unnecessary discrepancies between
Solaris/SPARC and x86 in the future.

While this fixes a couple of backtraces to now correctly print

#1  <signal handler called>

they often fail later with

#2  0x0ff3ffffff00857f in ?? ()
Backtrace stopped: Cannot access memory at address 0xff3000002e0886f

which needs further investigation.

Tested on amd64-pc-solaris2.11 (running the tests with both -m64 and
-m32).

	* amd64-sol2-tdep.c (amd64_sol2_sigtramp_p): Also recognize
	__sighndlr.
	* i386-sol2-tdep.c (i386_sol2_sigtramp_p): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a spurious target_terminal::ours() from windows_nat_target::wait()
@ 2018-09-25 14:11 sergiodj+buildbot
  2018-09-25 21:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-25 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a44294f5ed9fe09fdfc9427f6f83677843590524 ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: a44294f5ed9fe09fdfc9427f6f83677843590524

Remove a spurious target_terminal::ours() from windows_nat_target::wait()

This causes the inferior to stop with SIGTTIN if it tries to read from the
terminal after it has been continued.

See https://cygwin.com/ml/cygwin/2016-09/msg00285.html for reproduction.

Since MinGW doesn't have a tcsetpgrp(), I don't think this problem would be
observed there, but Cygwin does so target_terminal::ours() will call it.

Calling target_terminal::ours() here seems to be is no longer appropriate
after the "Merge async and sync code paths" changes (as the inferior is now
in a separate process group even in sync mode(?), which is always used on
Windows targets)

This call was added in commit c44537cf (and see
https://sourceware.org/ml/gdb-patches/2007-02/msg00167.html for what it
fixed, which is not regressed by this change)

When windows_nat_target::wait() is entered, the inferior is running (either
it's been just been started or attached to, or windows_continue() was
called), so grabbing the controlling terminal away from it here seems to be
wrong, since infrun.c takes care of calling target_terminal::ours() when the
inferior stops.

gdb/ChangeLog:

2018-08-02  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (windows_nat_target::wait): Remove a spurious
	target_terminal::ours().


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] elf32-nds32: Don't define fls if it is provided by the system
@ 2018-09-24 17:58 sergiodj+buildbot
  2018-09-24 23:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a767a1c4d3c7c5dd2f32cc106a21c1e01eddebcc ***

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

elf32-nds32: Don't define fls if it is provided by the system

The fls function already exists on macOS and FreeBSD (and probably others),
leading to this error:

/Users/simark/src/binutils-gdb/bfd/elf32-nds32.c:5074:1: error: static declaration of 'fls' follows non-static declaration
fls (register unsigned int x)
^
/usr/include/strings.h:87:6: note: previous declaration is here
int      fls(int) __OSX_AVAILABLE_STARTING(__MAC_10_5, __IPHONE_2_0);
         ^

Add a configure-time check for it, and only define it if the system doesn't
provide it.

bfd/ChangeLog:

	* configure.ac: Check for fls.
	* elf32-nds32.c (fls): Only define if !HAVE_FLS.
	* config.in: Re-generate.
	* configure: Re-generate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] csky-opc.h: Initialize fields of last array elements
@ 2018-09-24 17:05 sergiodj+buildbot
  2018-09-24 23:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f24ff6e9b5adc7983c3ad7cf28375eb49921b3ed ***

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

csky-opc.h: Initialize fields of last array elements

clang gives these errors:

In file included from /Users/simark/src/binutils-gdb/opcodes/csky-dis.c:30:
/Users/simark/src/binutils-gdb/opcodes/csky-opc.h:2330:8: error: missing field 'transfer' initializer [-Werror,-Wmissing-field-initializers]
  {NULL}
       ^
/Users/simark/src/binutils-gdb/opcodes/csky-opc.h:8126:10: error: missing field 'transfer' initializer [-Werror,-Wmissing-field-initializers]
    {NULL}
         ^

They go away when we Initialize all fields.  I noticed there used to be some
files built with -Wno-missing-field-initializers, but it's not the case
anymore, since commit e7ae278d0474ab84ba3b1ee932a19e83616ddacc.  There is still
a NO_WMISSING_FIELD_INITIALIZERS variable defined in the Makefile, but it's
unused, so I removed it to avoid further confusion.

opcodes/ChangeLog:

	* Makefile.am: Remove NO_WMISSING_FIELD_INITIALIZERS.
	* Makefile.in: Re-generate.
	* aclocal.m4: Re-generate.
	* configure: Re-generate.
	* configure.ac: Remove check for -Wno-missing-field-initializers.
	* csky-opc.h (csky_v1_opcodes): Initialize all fields of last element.
	(csky_v2_opcodes): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove redundant test in update_inserted_breakpoint_locations
@ 2018-09-24 16:14 sergiodj+buildbot
  2018-09-24 21:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 16:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4daf19021fef36767e70845608a8a2c3b4d72f99 ***

Author: Yacov Simhony <ysimhony@gmail.com>
Branch: master
Commit: 4daf19021fef36767e70845608a8a2c3b4d72f99

Remove redundant test in update_inserted_breakpoint_locations

Remove a redundant test in update_inserted_breakpoint_locations.

gdb/ChangeLog
2018-09-21  Yacov Simhony  <ysimhony@gmail.com>

	* breakpoint.c (update_inserted_breakpoint_locations): Remove
	redundant condition.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ELF: Don't include zero size sections at start of PT_NOTE segment
@ 2018-09-24 15:38 sergiodj+buildbot
  2018-09-24 16:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95475e5d6b7529309ca804fdc2c2e04d654c3978 ***

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

ELF: Don't include zero size sections at start of PT_NOTE segment

We shouldn't include zero size sections at start of PT_NOTE segment,
similar to PT_DYNAMIC segment.

	PR binutils/23694
	* include/elf/internal.h (ELF_SECTION_IN_SEGMENT_1): Don't
	include zero size sections at start of PT_NOTE segment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add '_' in the match pattern.
@ 2018-09-24 12:44 sergiodj+buildbot
  2018-09-24 13:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 12:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a466edac5f9913e3373e59335607e9666a0ac8c7 ***

Author: Hafiz Abid Qadeer <abidh@codesourcery.com>
Branch: master
Commit: a466edac5f9913e3373e59335607e9666a0ac8c7

Add '_' in the match pattern.

I was looking at GDB testcase results for arm-eabi target with qemu and
noticed that register groups returned by the qemu can have '_' in the
name e.g. 'cp_regs'. The reggroups.exp fails to recognize that as group
name. Fixed by adding '_' in the pattern.

2018-09-20  Hafiz Abid Qadeer  <abidh@codesourcery.com>

	gdb.base/reggroups.exp (fetch_reggroups): Add '_' in match pattern.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RS6000/BFD: Remove dead duplicate `config.bfd' target matchers
@ 2018-09-24 10:35 sergiodj+buildbot
  2018-09-24 11:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 10:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed3162adc45291b3de496be25911ebfd39f43a36 ***

Author: Maciej W. Rozycki <macro@linux-mips.org>
Branch: master
Commit: ed3162adc45291b3de496be25911ebfd39f43a36

RS6000/BFD: Remove dead duplicate `config.bfd' target matchers

Remove duplicate `rs6000-*-aix5.[01]' and `rs6000-*-aix[5-9]*' target
configuration selectors meant to correspond to `powerpc64-*-aix5.[01]'
and `powerpc64-*-aix[5-9]*' respectively for the purpose of BFD target
vector selection in `config.bfd'.

These selectors were added with commit 9a9e2ca33263 ("rs6000 xcoff bfd
config"), <https://sourceware.org/ml/binutils/2010-12/msg00372.html>,
and have been dead right from the beginning, because they appear twice
each in the case statement, which means the earlier instance of each
takes precedence and the other one is ignored.  Here ones that alias to
`powerpc-*-aix5.[01]' and `powerpc-*-aix[5-9]*' respectively immediately
above are used instead.

	bfd/
	* config.bfd <rs6000-*-aix5.[01], rs6000-*-aix[5-9]*>: Remove
	duplicate `case' selectors.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ARC: Fix build errors with large constants and C89
@ 2018-09-24 10:24 sergiodj+buildbot
  2018-09-24 12:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24 10:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 53b6d6f5b2d8681cc4a061e05fe28ef896900908 ***

Author: Maciej W. Rozycki <macro@linux-mips.org>
Branch: master
Commit: 53b6d6f5b2d8681cc4a061e05fe28ef896900908

ARC: Fix build errors with large constants and C89

Fix build errors:

cc1: warnings being treated as errors
In file included from .../opcodes/arc-opc.c:2630:
.../opcodes/arc-nps400-tbl.h:38: warning: integer constant is too large for 'long' type
.../opcodes/arc-nps400-tbl.h:38: warning: integer constant is too large for 'long' type
.../opcodes/arc-nps400-tbl.h:41: warning: integer constant is too large for 'long' type
.../opcodes/arc-nps400-tbl.h:41: warning: integer constant is too large for 'long' type
[...]
.../opcodes/arc-nps400-tbl.h:712: warning: integer constant is too large for 'long' type
.../opcodes/arc-nps400-tbl.h:712: warning: integer constant is too large for 'long' type
.../opcodes/arc-nps400-tbl.h:715: warning: integer constant is too large for 'long' type
.../opcodes/arc-nps400-tbl.h:715: warning: integer constant is too large for 'long' type
make[4]: *** [arc-opc.lo] Error 1

and:

cc1: warnings being treated as errors
.../gas/config/tc-arc.c: In function 'md_number_to_chars_midend':
.../gas/config/tc-arc.c:802: warning: integer constant is too large for 'long' type
.../gas/config/tc-arc.c:810: warning: integer constant is too large for 'long' type
make[4]: *** [config/tc-arc.o] Error 1

observed with GCC 4.1.2 and presumably other C89 compilers with the
`arc-elf' and `arc-linux-gnu' targets, caused by the use of constants
the values of which are outside the range of the `int' type (or the
`long' type if it is of the same with).  In the C89 language standard
such constants are not implicitly converted to a wider type and an
explicit suffix is required for such constants.

Add a `ull' suffix then as with such constants used in other ports.

	gas/
	* config/tc-arc.c (md_number_to_chars_midend): Append `ull' to
	large constants.

	opcodes/
	* arc-nps400-tbl.h: Append `ull' to large constants throughout.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Andes Technology has good news for you, we plan to update the nds32 port of binutils on upstream!
@ 2018-09-24  6:58 sergiodj+buildbot
  2018-09-24 10:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24  6:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbaf61ad525eb2818598b699d44df32e46583925 ***

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

Andes Technology has good news for you, we plan to update the nds32 port of binutils on upstream!

We have not only removed all unsupported and obsolete code, but also supported lost of new features,
including better link-time relaxations and TLS implementations. Besides, the files generated by the
newly assembler and linker usually get higher performance and more optimized code size.

ld	* emultempl/nds32elf.em (hyper_relax): New variable.
	(nds32_elf_create_output_section_statements):
	the parameters of bfd_elf32_nds32_set_target_option
	(PARSE_AND_LIST_PROLOGUE, PARSE_AND_LIST_OPTIONS,
	PARSE_AND_LIST_ARGS_CASES): Add new option --mhyper-relax.
	* emultempl/nds32elf.em (nds32_elf_after_open): Updated.
	* emultempl/nds32elf.em (tls_desc_trampoline): New variable.
	* (nds32_elf_create_output_section_statements): Updated.
	* (nds32_elf_after_parse): Disable relaxations when PIC is enable.
	* (PARSE_AND_LIST_PROLOGUE, PARSE_AND_LIST_OPTIONS,
	PARSE_AND_LIST_ARGS_CASES): Add new option --m[no-]tlsdesc-trampoline.

include	* elf/nds32.h: Remove the unused target features.
	* dis-asm.h (disassemble_init_nds32): Declared.
	* elf/nds32.h (E_NDS32_NULL): Removed.
	(E_NDS32_HAS_DSP_INST, E_NDS32_HAS_ZOL): New.
	* opcode/nds32.h: Ident.
	(N32_SUB6, INSN_LW): New macros.
	(enum n32_opcodes): Updated.
	* elf/nds32.h: Doc fixes.
	* elf/nds32.h: Add R_NDS32_LSI.
	* elf/nds32.h: Add new relocations for TLS.

gas 	* config/tc-nds32.c: Remove the unused target features.
	(nds32_relax_relocs, md_pseudo_table, nds32_elf_record_fixup_exp,
	nds32_set_elf_flags_by_insn, nds32_insert_relax_entry,
	nds32_apply_fix): Likewise.
	(nds32_no_ex9_begin): Removed.
	* config/tc-nds32.c (add_mapping_symbol_for_align,
	make_mapping_symbol, add_mapping_symbol): New functions.
	* config/tc-nds32.h (enum mstate): New.
	(nds32_segment_info_type): Likewise.
	* configure.ac (--enable-dsp-ext, --enable-zol-ext): New options.
	* config.in: Regenerated.
	* configure: Regenerated.
	* config/tc-nds32.c (nds32_dx_regs):
	Set the value according to the configuration.
	(nds32_perf_ext, nds32_perf_ext2, nds32_string_ext, nds32_audio_ext):
	Likewise.
	(nds32_dsp_ext): New variable. Set the value according to the
	configuration.
	(nds32_zol_ext): Likewise.
	(asm_desc, nds32_pseudo_opcode_table): Make them static.
	(nds32_set_elf_flags_by_insn): Updated.
	(nds32_check_insn_available): Updated.
	(nds32_str_tolower): New function.
	* config/tc-nds32.c (relax_table): Updated.
	(md_begin): Updated.
	(md_assemble): Use XNEW macro to allocate space for `insn.info',
	and then remember to free it.
	(md_section_align): Cast (-1) to ValueT.
	(nds32_get_align): Cast (~0U) to addressT.
	(nds32_relax_branch_instructions): Updated.
	(md_convert_frag): Add new local variable `final_r_type'.
	(invalid_prev_frag): Add new bfd_boolean parameter `relax'.
	All callers changed.
	* config/tc-nds32.c (struct nds32_relocs_pattern): Add `insn' field.
	(struct nds32_hint_map): Add `option_list' field.
	(struct suffix_name, suffix_table): Remove the unused `pic' field.
	(do_pseudo_b, do_pseudo_bal): Remove the suffix checking.
	(do_pseudo_la_internal, do_pseudo_pushpopm): Indent.
	(relax_hint_bias, relax_hint_id_current): New static variables.
	(reset_bias, relax_hint_begin): New variables.
	(nds_itoa): New function.
	(CLEAN_REG, GET_OPCODE): New macros.
	(struct relax_hint_id): New.
	(nds32_relax_hint): For .relax_hint directive, we can use `begin'
	and `end' to mark the relax pattern without giving exactly id number.
	(nds32_elf_append_relax_relocs): Handle the case that the .relax_hint
	directives are attached to pseudo instruction.
	(nds32_elf_save_pseudo_pattern): Change the second parameter from
	instruction's opcode to byte code.
	(nds32_elf_build_relax_relation): Add new bfd_boolean parameter
	`pseudo_hint'.
	(nds32_lookup_pseudo_opcode): Fix the overflow issue.
	(enum nds32_insn_type): Add N32_RELAX_ALU1 and N32_RELAX_16BIT.
	(nds32_elf_record_fixup_exp, relax_ls_table, hint_map,
	nds32_find_reloc_table, nds32_match_hint_insn, nds32_parse_name):
	Updated.
	* config/tc-nds32.h (MAX_RELAX_NUM): Extend it to 6.
	(enum nds32_relax_hint_type): Merge NDS32_RELAX_HINT_LA and
	NDS32_RELAX_HINT_LS into NDS32_RELAX_HINT_LALS. Add
	NDS32_RELAX_HINT_LA_PLT, NDS32_RELAX_HINT_LA_GOT and
	NDS32_RELAX_HINT_LA_GOTOFF.
	* config/tc-nds32.h (relax_ls_table): Add floating load/store
	to gp relax pattern.
	(hint_map, nds32_find_reloc_table): Likewise.
	* configure.ac: Define NDS32_LINUX_TOOLCHAIN.
	* configure: Regenerated.
	* config.in: Regenerated.
	* config/tc-nds32.h (enum nds32_ramp): Updated.
	(enum nds32_relax_hint_type): Likewise.
	* config/tc-nds32.c: Include "errno.h" and "limits.h".
	(relax_ls_table): Add TLS relax patterns.
	(nds32_elf_append_relax_relocs): Attach BFD_RELOC_NDS32_GROUP on
	each instructions of TLS patterns.
	(nds32_elf_record_fixup_exp): Updated.
	(nds32_apply_fix): Likewise.
	(suffix_table): Add TLSDESC suffix.

binutils* testsuite/binutils-all/objcopy.exp: Set the unsupported reloc number
	from 215 to 255 for NDS32.

bfd	* elf32-nds32.c (nds32_elf_relax_loadstore):
	Remove the unused target features.
	(bfd_elf32_nds32_set_target_option): Remove the unused parameters.
	(nds32_elf_relax_piclo12, nds32_elf_relax_letlslo12,
	nds32_elf_relax_letlsadd, nds32_elf_relax_letlsls,
	nds32_elf_relax_pltgot_suff, nds32_elf_relax_got_suff
	nds32_elf_relax_gotoff_suff, calculate_plt_memory_address,
	calculate_plt_offset, calculate_got_memory_address,
	nds32_elf_check_dup_relocs): Removed.
	All callers changed.
	* elf32-nds32.h: Remove the unused macros and defines.
	(elf_nds32_link_hash_table): Remove the unused variable.
	(bfd_elf32_nds32_set_target_option): Update prototype.
	(nds32_elf_ex9_init): Removed.
	* elf32-nds32.c (nds32_convert_32_to_16): Updated.
	* elf32-nds32.c (HOWTO2, HOWTO3): Define new HOWTO macros
	to initialize array nds32_elf_howto_table in any order
	without lots of EMPTY_HOWTO.
	(nds32_reloc_map): Updated.
	* reloc.c: Add BFD_RELOC_NDS32_LSI.
	* bfd-in2.h: Regenerated.
	* bfd/libbfd.h: Regenerated.
	* elf32-nds32.c (nds32_elf_relax_howto_table): Add R_NDS32_LSI.
	(nds32_reloc_map): Likewise.
	(nds32_elf_relax_flsi): New function.
	(nds32_elf_relax_section): Support floating load/store relaxation.
	* elf32-nds32.c (NDS32_GUARD_SEC_P, elf32_nds32_local_gp_offset):
	New macro.
	(struct elf_nds32_link_hash_entry): New `offset_to_gp' field.
	(struct elf_nds32_obj_tdata): New `offset_to_gp' and `hdr_size' fields.
	(elf32_nds32_allocate_local_sym_info, nds32_elf_relax_guard,
	nds32_elf_is_target_special_symbol, nds32_elf_maybe_function_sym):
	New functions.
	(nds32_info_to_howto_rel): Add BFD_ASSERT.
	(bfd_elf32_bfd_reloc_type_table_lookup, nds32_elf_link_hash_newfunc,
	nds32_elf_link_hash_table_create, nds32_elf_relocate_section,
	nds32_elf_relax_loadstore, nds32_elf_relax_lo12, nds32_relax_adjust_label,
	bfd_elf32_nds32_set_target_option, nds32_fag_mark_relax): Updated.
	(nds32_elf_final_sda_base): Improve it to find the better gp value.
	(insert_nds32_elf_blank): Must consider `len' when inserting blanks.
	* elf32-nds32.h (bfd_elf32_nds32_set_target_option): Update prototype.
	(struct elf_nds32_link_hash_table): Add new variable `hyper_relax'.
	* elf32-nds32.c (elf32_nds32_allocate_dynrelocs): New function.
	(create_got_section): Likewise.
	(allocate_dynrelocs, nds32_elf_size_dynamic_sections,
	nds32_elf_relocate_section, nds32_elf_finish_dynamic_symbol): Updated.
	(nds32_elf_check_relocs): Fix the issue that the shared library may
	has TEXTREL entry in the dynamic section.
	(nds32_elf_create_dynamic_sections): Enable to call readonly_dynrelocs
	since the TEXTREL issue is fixed in the nds32_elf_check_relocs.
	(nds32_elf_finish_dynamic_sections): Update and add DT_RELASZ
	dynamic entry.
	(calculate_offset): Remove the unused parameter `pic_ext_target' and
	related codes.
	All callers changed.
	(elf_backend_dtrel_excludes_plt): Disable it temporarily since it
	will cause some errors for our test cases.
	* elf32-nds32.c (nds32_elf_merge_private_bfd_data): Allow to link the
	generic object.
	* reloc.c: Add TLS relocations.
	* libbfd.h: Regenerated.
	* bfd-in2.h: Regenerated.
	* elf32-nds32.h (struct section_id_list_t): New.
	(elf32_nds32_lookup_section_id, elf32_nds32_check_relax_group,
	elf32_nds32_unify_relax_group, nds32_elf_unify_tls_model):
	New prototypes.
	(elf32_nds32_compute_jump_table_size, elf32_nds32_local_tlsdesc_gotent):
	New macro.
	(nds32_insertion_sort, bfd_elf32_nds32_set_target_option,
	elf_nds32_link_hash_table): Updated.
	* elf32-nds32.c (enum elf_nds32_tls_type): New.
	(struct elf32_nds32_relax_group_t, struct relax_group_list_t): New.
	(elf32_nds32_add_dynreloc, patch_tls_desc_to_ie, get_tls_type,
	fls, ones32, list_insert, list_insert_sibling, dump_chain,
	elf32_nds32_check_relax_group, elf32_nds32_lookup_section_id,
	elf32_nds32_unify_relax_group, nds32_elf_unify_tls_model): New functions.
	(elf_nds32_obj_tdata): Add new fields.
	(elf32_nds32_relax_group_ptr, nds32_elf_local_tlsdesc_gotent): New macros.
	(nds32_elf_howto_table): Add TLS relocations.
	(nds32_reloc_map): Likewise.
	(nds32_elf_copy_indirect_symbol, nds32_elf_size_dynamic_sections,
	nds32_elf_finish_dynamic_symbol, elf32_nds32_allocate_local_sym_info,
	nds32_elf_relocate_section, bfd_elf32_nds32_set_target_option,
	nds32_elf_check_relocs, allocate_dynrelocs): Updated.
	(nds32_elf_relax_section): Call nds32_elf_unify_tls_model.
	(dtpoff_base): Rename it to `gottpof' and then update it.

opcodes	* nds32-asm.c (operand_fields): Remove the unused fields.
	(nds32_opcodes): Remove the unused instructions.
	* nds32-dis.c (nds32_ex9_info): Removed.
	(nds32_parse_opcode): Updated.
	(print_insn_nds32): Likewise.
	* nds32-asm.c (config.h, stdlib.h, string.h): New includes.
	(LEX_SET_FIELD, LEX_GET_FIELD): Update defines.
	(nds32_asm_init, build_operand_hash_table, build_keyword_hash_table,
	build_opcode_hash_table): New functions.
	(nds32_keyword_table, nds32_keyword_count_table, nds32_field_table,
	nds32_opcode_table): New.
	(hw_ktabs): Declare it to a pointer rather than an array.
	(build_hash_table): Removed.
	* nds32-asm.h (enum): Add SYN_INPUT, SYN_OUTPUT, SYN_LOPT,
	SYN_ROPT and upadte HW_GPR and HW_INT.
	* nds32-dis.c (keywords): Remove const.
	(match_field): New function.
	(nds32_parse_opcode): Updated.
	* disassemble.c (disassemble_init_for_target):
	Add disassemble_init_nds32.
	* nds32-dis.c (eum map_type): New.
	(nds32_private_data): Likewise.
	(get_mapping_symbol_type, is_mapping_symbol, nds32_symbol_is_valid,
	nds32_add_opcode_hash_table, disassemble_init_nds32): New functions.
	(print_insn_nds32): Updated.
	* nds32-asm.c (parse_aext_reg): Add new parameter.
	(parse_re, parse_re2, parse_aext_reg): Only reduced registers
	are allowed to use.
	All callers changed.
	* nds32-asm.c (keyword_usr, keyword_sr): Updated.
	(operand_fields): Add new fields.
	(nds32_opcodes): Add new instructions.
	(keyword_aridxi_mx): New keyword.
	* nds32-asm.h (enum): Add NASM_ATTR_DSP_ISAEXT, HW_AEXT_ARIDXI_MX
	and NASM_ATTR_ZOL.
	(ALU2_1, ALU2_2, ALU2_3): New macros.
	* nds32-dis.c (nds32_filter_unknown_insn): Updated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23685, buffer overflow
@ 2018-09-24  6:13 sergiodj+buildbot
  2018-09-24  9:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-24  6:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf93e9c2cf8f8b2566f8fc86e961592b51b5980d ***

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

PR23685, buffer overflow

	PR 23685
	* peXXigen.c (pe_print_edata): Correct export address table
	overflow checks.  Check dataoff against section size too.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Provide pid_to_exec_file on Solaris (PR tdep/17903)
@ 2018-09-23 18:47 sergiodj+buildbot
  2018-09-24  6:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-23 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4206c05ea1542c413a4a361c29cbbd206861946c ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 4206c05ea1542c413a4a361c29cbbd206861946c

Provide pid_to_exec_file on Solaris (PR tdep/17903)

While looking through gdb.log, I found that two tests FAIL like this:

warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x00400dc4 in ?? ()
(gdb) FAIL: gdb.base/attach.exp: attach2, with no file

The other is gdb.base/quit-live.exp.  I've implemented the following
patch that fixes both failures, only then detecting that I'd previously
reported the issue as PR tdep/17903.

Tested on amd64-pc-solaris2.10 and amd64-pc-solaris2.11.

	PR tdep/17903
	* procfs.c (procfs_target): Declare pid_to_exec_file.
	(procfs_target::pid_to_exec_file): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Handle missing Solaris auxv entries
@ 2018-09-23 16:28 sergiodj+buildbot
  2018-09-23 20:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-23 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3d282ac37064ec0105d3aa3f379f7fb8af98759c ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 3d282ac37064ec0105d3aa3f379f7fb8af98759c

Handle missing Solaris auxv entries

Currently, three tests FAIL on Solaris 11.4+ (amd64-pc-solaris2.11 and
sparcv9-sun-solaris2.11):

info auxv
[...]
2009 AT_SUN_HWCAP         Machine-dependent CPU capability hints 0x3f5ff7
2023 ???                                                 0x0
0    AT_NULL              End of vector                  0x0
(gdb) WARNING: Unrecognized tag value: 2023 ???  0x0

FAIL: gdb.base/auxv.exp: info auxv on live process

info auxv
4294969310 ???                                                 0x7fffbfffe410
9225589753816 ???                                                 0x7fffbfffe45c
[...]
WARNING: Unrecognized tag value: 4294969310 ???  0x7fffbfffe410

WARNING: Unrecognized tag value: 9225589753816 ???  0x7fffbfffe45c

WARNING: Unrecognized tag value: 140733193388037 ???  0x6
[...]
2009 AT_SUN_HWCAP         Machine-dependent CPU capability hints 0x3f5ff7
2023 ???                                                 0x0
0    AT_NULL              End of vector                  0x0
(gdb) WARNING: Unrecognized tag value: 2023 ???  0x0

UNRESOLVED: gdb.base/auxv.exp: info auxv on native core dump

info auxv
[...]
2009 AT_SUN_HWCAP         Machine-dependent CPU capability hints 0x3f5ff7
2023 ???                                                 0x0
0    AT_NULL              End of vector                  0x0
(gdb) WARNING: Unrecognized tag value: 2023 ???  0x0

FAIL: gdb.base/auxv.exp: info auxv on gcore-created dump

The following patch fixes this by introducing the missing AT_SUN_*
values from Solaris 11.4+ <sys/auxv.h>.  This lets the live and
gcore-created dump tests PASS.

I don't know yet what's the reason for those weird 'Unrecognized tag
value' warnings with native core dumps is; elfdump -n certainly doesn't
show them.  However, native core dumps still need quite some work
(mostly in bfd) in this and other areas.

Tested on amd64-pc-solaris2.11.

	gdb:
	* auxv.c (default_print_auxv_entry): Reflect AT_SUN_CAP_HW1
	renaming.
	Handle AT_SUN_EMULATOR, AT_SUN_BRANDNAME, AT_SUN_BRAND_AUX1,
	AT_SUN_BRAND_AUX2, AT_SUN_BRAND_AUX3, AT_SUN_CAP_HW2.

	include:
	* elf/common.h (AT_SUN_HWCAP): Rename to ...
	(AT_SUN_CAP_HW1): ... this.  Retain old name for backward
	compatibility.
	(AT_SUN_EMULATOR, AT_SUN_BRANDNAME, AT_SUN_BRAND_AUX1)
	(AT_SUN_BRAND_AUX2, AT_SUN_BRAND_AUX3, AT_SUN_CAP_HW2): Define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fold i386-v4-nat.c into i386-sol2-nat.c
@ 2018-09-23 16:12 sergiodj+buildbot
  2018-09-23 19:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-23 16:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8674be792462bc4469b04723484c63ab4c7ad895 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 8674be792462bc4469b04723484c63ab4c7ad895

Fold i386-v4-nat.c into i386-sol2-nat.c

I've been carrying around the following patch for some time.  I noticed
that both i386-sol2-nat.c and i386-v4-nat.c are Solaris-only now and it
seems confusing to carry both around.

So this patch merges i386-v4-nat.c into i386-sol2-nat.c, simplifying it
in a couple of places, like removing checks for macros that are always
defined.

Tested on 64-bit Solaris 11.5/x86 (amd64-pc-solaris2.11) and 32-bit
Solaris 11.3/x86 (i386-pc-solaris2.11) half a year ago.

	* i386-v4-nat.c (regmap, supply_gregset, fill_gregset)
	(supply_fpregset, fill_fpregset): Move ...
	* i386-sol2-nat.c [PR_MODEL_NATIVE != PR_MODEL_LP64]: ... here.
	Remove HAVE_GREGSET_T, HAVE_FPREGET_T guards.
	Remove references to ioctl-based procfs.
	Include <sys/reg.h>.
	Remove PR_MODEL_NATIVE guards.
	* configure.nat <sol2, i386> (NATDEPFILES): Remove i386-v4-nat.o.
	* Makefile.in (ALLDEPFILES): Remove i386-v4-nat.c.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Bug 23686, two segment faults in nm
@ 2018-09-23 15:49 sergiodj+buildbot
  2018-09-23 17:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-23 15:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30838132997e6a3cfe3ec11c58b32b22f6f6b102 ***

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

Bug 23686, two segment faults in nm

Fixes the bugs exposed by the testcases in the PR, plus two more bugs
I noticed when looking at _bfd_stab_section_find_nearest_line.

	PR 23686
	* dwarf2.c (read_section): Error when attempting to malloc
	"(bfd_size_type) -1".
	* syms.c (_bfd_stab_section_find_nearest_line): Bounds check
	function_name.  Bounds check reloc address.  Formatting.  Ensure
	.stabstr zero terminated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Skip GDB tab-completion tests if no readline.
@ 2018-09-23 14:31 sergiodj+buildbot
  2018-09-23 15:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-23 14:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4ee9b0c53a8055b869dfe424846bc00eb0cd0c8f ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: 4ee9b0c53a8055b869dfe424846bc00eb0cd0c8f

Skip GDB tab-completion tests if no readline.

2018-09-18  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.base/complete-empty.exp: Skip tab-completion tests if
	no readline.
	* gdb.base/utf8-identifiers.exp: Likewise.
	* gdb.cp/cpcompletion.exp: Likewise.
	* gdb.linespec/cpcompletion.exp: Likewise.
	* gdb.linespec/cpls-abi-tag.exp: Likewise.
	* gdb.linespec/cpls-ops.exp: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Darwin: Handle unrelocated dyld.
@ 2018-09-21 16:28 sergiodj+buildbot
  2018-09-21 18:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-21 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79b32f4a3a109321cb9a99014293b0ade57535ab ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: 79b32f4a3a109321cb9a99014293b0ade57535ab

Darwin: Handle unrelocated dyld.

On Darwin, debugging an helloworld program with GDB does
not work and ends with:

  (gdb) set startup-with-shell off
  (gdb) start
  Temporary breakpoint 1 at 0x100000fb4: file /tmp/helloworld.c, line 1.
  Starting program: /private/tmp/helloworld
  [New Thread 0x2703 of process 18906]
  [New Thread 0x2603 of process 18906]

  [1]+  Stopped                 ./gdb/gdb /tmp/helloworld

When debugging with lldb, instead of having the STOP signal, we can
see that a breakpoint is not set to a proper location:

  Warning:
  Cannot insert breakpoint -1.
  Cannot access memory at address 0xf726

  Command aborted.

The inserted breakpoint is the one used when GDB has to stop the target
when a shared library is loaded or unloaded. The notifier address used
for adding the breakpoint is wrong thus the above failure.
This notifier address is an offset relative to dyld base address, so
the value calculation has to be updated to reflect this.

This was tested on High Sierra by trying to run a simple "hello world"
program.

gdb/ChangeLog:

	PR gdb/20981:
        * solib-darwin.c (darwin_get_dyld_bfd): New function.
        (darwin_solib_get_all_image_info_addr_at_init): Update call.
        (darwin_handle_solib_event): New function.
        (darwin_solib_create_inferior_hook): Handle unrelocated dyld.

Change-Id: I7dde5008c9158f17b78dc89bd7f4bd8a12d4a6e1


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add missing spaces after inet_ntop invocations.
@ 2018-09-21 15:17 sergiodj+buildbot
  2018-09-21 15:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-21 15:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07147793e678dac92f6a16f140678f9a5aed21e7 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 07147793e678dac92f6a16f140678f9a5aed21e7

Add missing spaces after inet_ntop invocations.

gdb/ChangeLog:

	* fbsd-tdep.c (fbsd_print_sockaddr_in): Style fix.
	(fbsd_print_sockaddr_in6): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Logical short circuiting with argument lists
@ 2018-09-20 17:14 sergiodj+buildbot
  2018-09-20 18:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-20 17:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23be8da7396ffc4d5492d976e244daaa543eaac9 ***

Author: Richard Bunt <richard.bunt@arm.com>
Branch: master
Commit: 23be8da7396ffc4d5492d976e244daaa543eaac9

Logical short circuiting with argument lists

When evaluating Fortran expressions such as the following:

	print truth_table(1,1) .OR. truth_table(2,1)

where truth_table(1,1) evaluates to true, the debugger would report that
it could not perform substring operations on this type. This patch
addresses this issue.

Investigation revealed that EVAL_SKIP was not being handled correctly
for all types serviced by the OP_F77_UNDETERMINED_ARGLIST case in
evaluate_subexp_standard. While skipping an undetermined argument list
the type is resolved to be an integer (as this is what evaluate_subexp
returns when skipping) and so it was not possible to delegate to the
appropriate case (e.g. array, function call).

The solution implemented here updates OP_VAR_VALUE to return correct
type information when skipping. This way OP_F77_UNDETERMINED_ARGLIST
can delegate the skipping to the appropriate case or routine, which
should know how to skip/evaluate the type in question.

koenig.exp was updated to include a testcase which exercises the
modified skip logic in OP_VAR_VALUE, as it falls through from
OP_ADL_FUNC.

This patch has been tested for regressions with GCC 7.3 on aarch64,
ppc64le and x86_64.

gdb/ChangeLog:

	* eval.c (skip_undetermined_arglist): Skip argument list helper.
	(evaluate_subexp_standard): Return a dummy type when
	honoring EVAL_SKIP in OP_VAR_VALUE and handle skipping in the
	OP_F77_UNDETERMINED_ARGLIST case.
	* expression.h (enum noside): Update comment.

gdb/testsuite/ChangeLog:

	* gdb.cp/koenig.exp: Extend to test logical short circuiting.
	* gdb.fortran/short-circuit-argument-list.exp: New file.
	* gdb.fortran/short-circuit-argument-list.f90: New test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix /proc pathname sizes on Solaris
@ 2018-09-20 16:28 sergiodj+buildbot
  2018-09-20 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-20 16:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13db92d3f48cbd6784f50bbd0ce10220e0d48ee4 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 13db92d3f48cbd6784f50bbd0ce10220e0d48ee4

Fix /proc pathname sizes on Solaris

I'm slowly working my way through the gdb patches from the
solaris-userland repo

	https://github.com/oracle/solaris-userland/tree/master/components/gdb/patches

This one (001-fix-proc-name-size.patch) should be obvious given the
patches' comment:

# In Solaris, PID_MAX is 999999 (6 digit pid).
# In Solaris, lwpid_t is an unsigned int, so theoretically the lwp id
# could be 10 digits.

Tested on i386-pc-solaris2.11.

2018-09-19  Stefan Teleman <stefan.teleman@oracle.com>
	    April Chin <april.chin@oracle.com>
	    Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

	* procfs.c (MAX_PROC_NAME_SIZE): Allow for 6-digit PID_MAX and
	uint_t lwpid_t.
	(create_procinfo): Print pids in /proc without leading zeros.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Carry the gnulib getcwd backport as a patch
@ 2018-09-20 10:41 sergiodj+buildbot
  2018-09-20 15:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-20 10:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b567ca638c274e27969975403b885973af9ccae6 ***

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

Carry the gnulib getcwd backport as a patch

Commit

  e2fc52e7457 ("Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB")

backported some changes from a future gnulib version to our import.
However, this means that every time someone wants to change our gnulib
import (e.g. add a module), they must make sure not to include that
backported change.  It also means that someone running the
update-gnulib.sh script without changes will get some diffs and wonder
why.

Instead, I suggest we carry that backport as a patch applied by the
update-gnulib.sh script after running the import tool.  It will make it
clear what backport or local modification we have and should make
running update-gnulib.sh give a reproducible result.

There is a hunk in the configure file in this patch, this is because the
commit that backported the getcwd bits didn't include the re-generated
configure.

Note: you'll need this patch as well to get deterministic results:

  Generate aclocal-m4-deps.mk more deterministically and portably.
  https://sourceware.org/ml/gdb-patches/2018-09/msg00643.html

gdb/ChangeLog:

	* patches/0001-Fix-PR-gdb-23558-Use-system-s-getcwd-when-cross-comp.patch:
	New file.
	* update-gnulib.sh: Apply patch.
	* configure: Re-generate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for 'info proc files' on FreeBSD core dumps.
@ 2018-09-20 10:22 sergiodj+buildbot
  2018-09-20 12:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-20 10:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57c2a98a4c7e5ad4e62c876eb5cebe9d17a51ad0 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 57c2a98a4c7e5ad4e62c876eb5cebe9d17a51ad0

Add support for 'info proc files' on FreeBSD core dumps.

Walk the list of struct kinfo_file objects in the
NT_FREEBSD_PROCSTAT_FILES core dump note outputting a description of
each open file descriptor.  For sockets, the local and remote socket
addresses are displayed in place of the file name field.  For UNIX
local domain sockets, only a single address is displayed since most
UNIX sockets only have one valid address and printing both pathnames
could be quite long.  The output format was somewhat inspired by the
output of the "procstat -f" command on FreeBSD, but with a few less
details and some fields were condensed.

gdb/ChangeLog:

	* fbsd-tdep.c (KF_FLAGS, KF_OFFSET, KF_VNODE_TYPE, KF_SOCK_DOMAIN)
	(KF_SOCK_TYPE, KF_SOCK_PROTOCOL, KF_SA_LOCAL, KF_SA_PEER)
	(KINFO_FILE_TYPE_SOCKET, KINFO_FILE_TYPE_PIPE)
	(KINFO_FILE_TYPE_FIFO, KINFO_FILE_TYPE_KQUEUE)
	(KINFO_FILE_TYPE_CRYPTO, KINFO_FILE_TYPE_MQUEUE)
	(KINFO_FILE_TYPE_SHM, KINFO_FILE_TYPE_SEM, KINFO_FILE_TYPE_PTS)
	(KINFO_FILE_TYPE_PROCDESC, KINFO_FILE_FD_TYPE_ROOT)
	(KINFO_FILE_FD_TYPE_JAIL, KINFO_FILE_FD_TYPE_TRACE)
	(KINFO_FILE_FD_TYPE_CTTY, KINFO_FILE_FLAG_READ)
	(KINFO_FILE_FLAG_WRITE, KINFO_FILE_FLAG_APPEND)
	(KINFO_FILE_FLAG_ASYNC, KINFO_FILE_FLAG_FSYNC)
	(KINFO_FILE_FLAG_NONBLOCK, KINFO_FILE_FLAG_DIRECT)
	(KINFO_FILE_FLAG_HASLOCK, KINFO_FILE_FLAG_EXEC)
	(KINFO_FILE_VTYPE_VREG, KINFO_FILE_VTYPE_VDIR)
	(KINFO_FILE_VTYPE_VCHR, KINFO_FILE_VTYPE_VLNK)
	(KINFO_FILE_VTYPE_VSOCK, KINFO_FILE_VTYPE_VFIFO, FBSD_AF_UNIX)
	(FBSD_AF_INET, FBSD_AF_INET6, FBSD_SOCK_STREAM, FBSD_SOCK_DGRAM)
	(FBSD_SOCK_SEQPACKET, FBSD_IPPROTO_ICMP, FBSD_IPPROTO_TCP)
	(FBSD_IPPROTO_UDP, FBSD_IPPROTO_SCTP): New defines.
	(struct fbsd_sockaddr_in, struct fbsd_sockaddr_in6)
	(struct fbsd_sockaddr_un): New types.
	(fbsd_file_fd, fbsd_file_type, fbsd_file_flags, fbsd_ipproto)
	(fbsd_print_sockaddr_in, fbsd_print_sockaddr_in6)
	(fbsd_info_proc_files_header, fbsd_info_proc_files_entry)
	(fbsd_core_info_proc_files): New functions.
	(fbsd_core_info_proc): List open file descriptors for IP_FILES and
	IP_ALL.
	* fbsd-tdep.h (fbsd_info_proc_files_header)
	(fbsd_info_proc_files_entry): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Generate aclocal-m4-deps.mk more deterministically and portably.
@ 2018-09-20  3:28 sergiodj+buildbot
  2018-09-20  9:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-20  3:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2afffa7f629da4c07510014098294d1fd141f5c7 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 2afffa7f629da4c07510014098294d1fd141f5c7

Generate aclocal-m4-deps.mk more deterministically and portably.

Sort the list of files generated by find to make the order of the
entries deterministic.  When sorting, use explicit "C" collation.  Use
an explicit tab character instead of '\t' as some sed implementations
treat '\t' as an escaped 't' instead of a tab.

gdb/ChangeLog:

	* gnulib/aclocal-m4-deps.mk: New file.
	* gnulib/update-gnulib.sh: Generate "aclocal-m4-deps.mk"
	deterministically.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make the "info proc" documentation more consistent.
@ 2018-09-19 22:12 sergiodj+buildbot
  2018-09-20 15:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 22:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73f1bd769a5216b3debc1025faa62a466c5a1e68 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 73f1bd769a5216b3debc1025faa62a466c5a1e68

Make the "info proc" documentation more consistent.

Remove "running" in a few places since "info proc" can be used with
core dumps as well as running processes on both Linux and FreeBSD.

Use "the specified process" in the description of most "info proc"
subcommands.

Use "additional information" instead of "/proc process information" in
the "info proc" description to more closely match the language in the
manual.

gdb/ChangeLog:

	* infcmd.c (_initialize_infcmd): Remove "running" from "info proc"
	description.  Make "info proc" command descriptions more
	consistent.

gdb/doc/ChangeLog:

	* gdb.texinfo (info proc): Remove "running".
	(info proc mappings): Replace "program" with "process".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Document the 'info proc files' command.
@ 2018-09-19 21:37 sergiodj+buildbot
  2018-09-20 14:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b11311136c0acb5c4d3fbc9c1c92f259feb6beb ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 8b11311136c0acb5c4d3fbc9c1c92f259feb6beb

Document the 'info proc files' command.

gdb/ChangeLog:

	* NEWS: Mention 'info proc files' command.

gdb/doc/ChangeLog:

	* gdb.texinfo (Process Information): Document "info proc files"
	command.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Support 'info proc files' on live FreeBSD processes.
@ 2018-09-19 20:31 sergiodj+buildbot
  2018-09-20 12:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 20:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e69672e4dfa532607e4ecef99623680264a87b3 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 7e69672e4dfa532607e4ecef99623680264a87b3

Support 'info proc files' on live FreeBSD processes.

This walks the list of struct kinfo_file objects returned by a call to
kinfo_getfile outputting a description of each open file descriptor.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_nat_target::info_proc): List open file
	descriptors for IP_FILES and IP_ALL.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Expect optional "arch=" when executing "-stack-list-frames" on gdb.arch/amd64-invalid-stack-top.exp
@ 2018-09-19 20:08 sergiodj+buildbot
  2018-09-20  3:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 20:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5031d0ae0b9fb1a42eb8ff9d2b5098a56774cee1 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 5031d0ae0b9fb1a42eb8ff9d2b5098a56774cee1

Expect optional "arch=" when executing "-stack-list-frames" on gdb.arch/amd64-invalid-stack-top.exp

Another case of incomplete regexp.  The problem is very similar to the
one happening with gdb.arch/amd64-invalid-stack-middle.exp.

The output when GDB is compiled with "--enable-targets" is:

  (gdb) interpreter-exec mi "-stack-list-frames"
  ^done,stack=[frame={level="0",addr="0x00000000004005e7",func="func2",arch="i386:x86-64"}]

While the output when "--enable-targets" is not specified is:

  (gdb) interpreter-exec mi "-stack-list-frames"
  ^done,stack=[frame={level="0",addr="0x00000000004005e7",func="func2"}]

The fix is, again, to extend the current regexp and expect for the
optional "arch=" part.  With this patch, the test now passes on both
scenarios.

OK?

gdb/testsuite/ChangeLog:
2018-09-18  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.arch/amd64-invalid-stack-top.exp: Expect optional
	"arch=" keyword when executing "-stack-list-frames".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add a new 'info proc files' subcommand of 'info proc'.
@ 2018-09-19 19:48 sergiodj+buildbot
  2018-09-20 11:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 19:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e98ee8c458f3a8405eb93e71b00f801b4bbe3635 ***

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

Add a new 'info proc files' subcommand of 'info proc'.

This command displays a list of open file descriptors.

gdb/ChangeLog:

	* defs.h (enum info_proc_what) [IP_FILES]: New value.
	* infcmd.c (info_proc_cmd_files): New function.
	(_initialize_infcmd): Register 'info proc files' command.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Import gnulib's inet_ntop module.
@ 2018-09-19 18:52 sergiodj+buildbot
  2018-09-20 10:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 18:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 725e299974632e529be8b9c004a72118240da9f1 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 725e299974632e529be8b9c004a72118240da9f1

Import gnulib's inet_ntop module.

An upcoming patch to fbsd-tdep.c uses inet_ntop to format IP addresses.

gdb/ChangeLog:

	* gnulib/aclocal-m4-deps.mk: Re-generate.
	* gnulib/aclocal.m4: Re-generate.
	* gnulib/config.in: Re-generate.
	* gnulib/configure: Re-generate.
	* gnulib/import/Makefile.am: Re-generate.
	* gnulib/import/Makefile.in: Re-generate.
	* gnulib/import/m4/gnulib-cache.m4: Re-generate.
	* gnulib/import/m4/gnulib-comp.m4: Re-generate.
	* gnulib/import/arpa_inet.in.h: New file.
	* gnulib/import/inet_ntop.c: New file.
	* gnulib/import/m4/arpa_inet_h.m4: New file.
	* gnulib/import/m4/inet_ntop.m4: New file.
	* gnulib/import/m4/netinet_in_h.m4: New file.
	* gnulib/import/m4/socklen.m4: New file.
	* gnulib/import/m4/sockpfaf.m4: New file.
	* gnulib/import/m4/stdalign.m4: New file.
	* gnulib/import/m4/sys_uio_h.m4: New file.
	* gnulib/import/netinet_in.in.h: New file.
	* gnulib/import/stdalign.in.h: New file.
	* gnulib/import/sys_socket.c: New file.
	* gnulib/import/sys_socket.in.h: New file.
	* gnulib/import/sys_uio.in.h: New file.
	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add inet_ntop
	module.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use KF_PATH to verify the size of a struct kinfo_file.
@ 2018-09-19 17:19 sergiodj+buildbot
  2018-09-20  8:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9f235e09e4d3dc6820e2d667200fe09b3e73b623 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 9f235e09e4d3dc6820e2d667200fe09b3e73b623

Use KF_PATH to verify the size of a struct kinfo_file.

fbsd_core_vnode_path needs to use the offset of the kf_path member of
struct kinfo_file as the minimum size of a struct kinfo_file object.
However, it was using KVE_PATH instead due to a copy and paste bug.

While here, fix another copy and paste bug in the error message for a
truncated kinfo_file object.

gdb/ChangeLog:

	* fbsd-tdep.c (fbsd_core_vnode_path): Use KF_PATH instead of
	KVE_PATH.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Expect for "@" when doing "complete break ada" on gdb.ada/complete.exp
@ 2018-09-19 13:17 sergiodj+buildbot
  2018-09-19 17:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a6d2b458f95030f433a0dcdabd5cda7ee695a9b ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 7a6d2b458f95030f433a0dcdabd5cda7ee695a9b

Expect for "@" when doing "complete break ada" on gdb.ada/complete.exp

Currently, gdb.ada/complete.exp's "complete break ada" test fails
because the regexp used to match the command's output doesn't expect
"@", but we have an output like:

  ...
  complete break ada
  break ada.assertions.assert
  break ada.calendar.arithmetic.difference
  break ada.calendar.arithmetic_operations.add
  break ada.calendar.arithmetic_operations.add.cold
  break ada.calendar.arithmetic_operations.add@plt
  break ada.calendar.arithmetic_operations.difference
  break ada.calendar.arithmetic_operations.difference@plt
  ...

This patch adds "@" to the regexp, unbreaking the test.

OK?

gdb/testsuite/ChangeLog:
2018-09-18  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.ada/complete.exp: Expect for "@" when doing "complete
	break ada".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove munmap_listp_free_cleanup
@ 2018-09-19  9:40 sergiodj+buildbot
  2018-09-19 15:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19  9:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c9e0a7e333107ad140d9e15110f8820115921555 ***

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

Remove munmap_listp_free_cleanup

This removes munmap_listp_free_cleanup, replacing it with a
std::unique_ptr at one spot and an explicit delete in another.  It
seemed simplest to completely change this data structure.

gdb/ChangeLog
2018-09-18  Tom Tromey  <tom@tromey.com>

	* compile/compile-object-run.c (do_module_cleanup): Use delete.
	* compile/compile-object-load.c (struct munmap_list): Move to
	header file.
	(munmap_list::add): Rename from munmap_list_add; rewrite.
	(munmap_list::~munmap_list): Rename from munmap_list_free.
	(munmap_listp_free_cleanup): Remove.
	(compile_object_load): Update.
	* compile/compile-object-load.h (struct munmap_list): Move from
	compile-object-load.c.  Rewrite.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add a warning to the bfd library for when it encounters an ELF file with an invalid section size.
@ 2018-09-19  9:06 sergiodj+buildbot
  2018-09-19 11:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19  9:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ff71a9c80cfcf64c54d4ae938c644b1b1ea19fb ***

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

Add a warning to the bfd library for when it encounters an ELF file with an invalid section size.

	PR 23657
	* elfcode.h (elf_swap_shdr_in): Generate a warning message if an
	ELF section has contents and size larger than the file size.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64 SVE: Fix stack smashing when calling functions
@ 2018-09-19  8:21 sergiodj+buildbot
  2018-09-19 10:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-19  8:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3ff2c72e14b7f4381c785ee35608c2812ef8610e ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 3ff2c72e14b7f4381c785ee35608c2812ef8610e

Aarch64 SVE: Fix stack smashing when calling functions

Using "call" on a function that passes arguments via float registers can cause
gdb to overflow buffers.

Ensure enough memory is reserved to hold a full FP register.

This fixes gdb.base/callfuncs.exp for Aarch64 SVE.

2018-09-18  Alan Hayward  <alan.hayward@arm.com>

	* aarch64-tdep.c (pass_in_v): Use register size.
	(aarch64_extract_return_value): Likewise.
	(aarch64_store_return_value): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/Python] Eliminate find_inferior_object
@ 2018-09-18 20:10 sergiodj+buildbot
  2018-09-18 20:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 20:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d35da542a7a7f62b909cef636f69c9da928e7d9b ***

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

[gdb/Python] Eliminate find_inferior_object

Commit 00431a78b28f ("Use thread_info and inferior pointers more
throughout") removed the declaration of find_inferior_object, but
missed removing the definition.

gdb/ChangeLog:
2018-09-17  Pedro Alves  <palves@redhat.com>

	* python/py-inferior.c (find_inferior_object): Delete.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Do not pass -DNDEBUG to Python compilations in development mode
@ 2018-09-18 17:57 sergiodj+buildbot
  2018-09-18 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 17:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae292b3afc0fce65c12014d2cc4621d7a0e661fd ***

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

Do not pass -DNDEBUG to Python compilations in development mode

The Python CFLAGS include -DNDEBUG.  This was apparently done
intentionally -- setting the flags is done manually because, according
to a comment, python-config passes too many things to the compiler
(which is true).

Per PR python/20445, this patch changes configure so that -DNDEBUG is
only used by release builds.  This probably doesn't have very much
effect in practice, but I did see that some Python headers use assert,
so perhaps it will give some safety.

Tested by rebuilding and re-running gdb.python/*.exp on x86-64 Fedora 28.

gdb/ChangeLog
2018-09-17  Tom Tromey  <tom@tromey.com>

	PR python/20445:
	* configure: Rebuild.
	* configure.ac: Conditionally use -DNDEBUG for Python.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Check for gmp when checking for mpfr
@ 2018-09-18 17:40 sergiodj+buildbot
  2018-09-18 21:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da658607ed24bc5a4dcfcfb56b6e1440ccab33d2 ***

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

Check for gmp when checking for mpfr

There was a report on irc that the gdb check for mpfr failed when only
static libraries are available.  The issue is that mpfr depends on
gmp, but this is not handled explicitly by gdb.

Ideally upstream would switch to pkg-config.  Or even more ideally, we
would incorporate pkg-config into the compiler and not mess with any
of this.

Meanwhile, this changes gdb's configure to add gmp to the link line
when checking for mpfr.

gdb/ChangeLog
2018-09-17  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.
	* configure.ac: Use gmp as a library dependency when checking for
	mpfr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix use-after-move in compile/compile-cplus-types.c
@ 2018-09-18 17:08 sergiodj+buildbot
  2018-09-18 17:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 17:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 461464f22632163209937ba5128d1f9f32554ea3 ***

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

Fix use-after-move in compile/compile-cplus-types.c

Patch

  d82b3862f12 ("compile: Remove non-const reference parameters")

introduced a regression in compile/compile-cplus-types.c.  The new_scope
variable in compile_cplus_instance::enter_scope is used after it was
std::moved.  This patch fixes it by referring to the back of the vector
where it was moved instead.

gdb/ChangeLog:

	* compile/compile-cplus-types.c
	(compile_cplus_instance::enter_scope): Don't use new_scope after
	std::move.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Set EVex=2 on EVEX.128 only vmovd and vmovq
@ 2018-09-18 15:08 sergiodj+buildbot
  2018-09-18 15:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 04e2a1829ea137ac23ac96e98fd60f9d720dcdcb ***

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

x86: Set EVex=2 on EVEX.128 only vmovd and vmovq

EVEX "VMOVD xmm1, r32/m32", "VMOVD r32/m32, xmm2", "VMOVQ xmm1, r64/m64",
"VMOVD r64/m64, xmm2", "VMOVQ xmm1, xmm2/m64" and "VMOVQ xmm1/m64, xmm2"
can only be encoded with EVEX.128.  Set EVex=2 on EVEX.128 only vmovd and
vmovq.

gas/

	PR gas/23670
	* testsuite/gas/i386/evex-lig-2.d: New file.
	* testsuite/gas/i386/evex-lig-2.s: Likewise.
	* testsuite/gas/i386/x86-64-evex-lig-2.d: Likewise.
	* testsuite/gas/i386/x86-64-evex-lig-2.s: Likewise.
	* testsuite/gas/i386/i386.exp: Run evex-lig-2 and
	x86-64-evex-lig-2.

opcodes/

	PR gas/23670
	* i386-dis-evex.h (evex_table): Use EVEX_LEN_0F6E_P_2,
	EVEX_LEN_0F7E_P_1, EVEX_LEN_0F7E_P_2 and EVEX_LEN_0FD6_P_2.
	(EVEX_LEN_0F6E_P_2): New EVEX_LEN_TABLE entry.
	(EVEX_LEN_0F7E_P_1): Likewise.
	(EVEX_LEN_0F7E_P_2): Likewise.
	(EVEX_LEN_0FD6_P_2): Likewise.
	* i386-dis.c (USE_EVEX_LEN_TABLE): New.
	(EVEX_LEN_TABLE): Likewise.
	(EVEX_LEN_0F6E_P_2): New enum.
	(EVEX_LEN_0F7E_P_1): Likewise.
	(EVEX_LEN_0F7E_P_2): Likewise.
	(EVEX_LEN_0FD6_P_2): Likewise.
	(evex_len_table): New.
	(get_valid_dis386): Handle USE_EVEX_LEN_TABLE.
	* i386-opc.tbl: Set EVex=2 on EVEX.128 only vmovd and vmovq.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Update disassembler for VexWIG
@ 2018-09-18 14:47 sergiodj+buildbot
  2018-09-18 14:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 14:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec6f095abc396e60f46e1b4724d0eb2e4d18213d ***

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

x86: Update disassembler for VexWIG

The VEX.W bit is ignored by some VEX instructions, aka WIG instructions.
Update x86 disassembler to handle VEX WIG instructions.

	* i386-dis.c (VZERO_Fixup): Removed.
	(VZERO): Likewise.
	(VEX_LEN_0F10_P_1): Likewise.
	(VEX_LEN_0F10_P_3): Likewise.
	(VEX_LEN_0F11_P_1): Likewise.
	(VEX_LEN_0F11_P_3): Likewise.
	(VEX_LEN_0F2E_P_0): Likewise.
	(VEX_LEN_0F2E_P_2): Likewise.
	(VEX_LEN_0F2F_P_0): Likewise.
	(VEX_LEN_0F2F_P_2): Likewise.
	(VEX_LEN_0F51_P_1): Likewise.
	(VEX_LEN_0F51_P_3): Likewise.
	(VEX_LEN_0F52_P_1): Likewise.
	(VEX_LEN_0F53_P_1): Likewise.
	(VEX_LEN_0F58_P_1): Likewise.
	(VEX_LEN_0F58_P_3): Likewise.
	(VEX_LEN_0F59_P_1): Likewise.
	(VEX_LEN_0F59_P_3): Likewise.
	(VEX_LEN_0F5A_P_1): Likewise.
	(VEX_LEN_0F5A_P_3): Likewise.
	(VEX_LEN_0F5C_P_1): Likewise.
	(VEX_LEN_0F5C_P_3): Likewise.
	(VEX_LEN_0F5D_P_1): Likewise.
	(VEX_LEN_0F5D_P_3): Likewise.
	(VEX_LEN_0F5E_P_1): Likewise.
	(VEX_LEN_0F5E_P_3): Likewise.
	(VEX_LEN_0F5F_P_1): Likewise.
	(VEX_LEN_0F5F_P_3): Likewise.
	(VEX_LEN_0FC2_P_1): Likewise.
	(VEX_LEN_0FC2_P_3): Likewise.
	(VEX_LEN_0F3A0A_P_2): Likewise.
	(VEX_LEN_0F3A0B_P_2): Likewise.
	(VEX_W_0F10_P_0): Likewise.
	(VEX_W_0F10_P_1): Likewise.
	(VEX_W_0F10_P_2): Likewise.
	(VEX_W_0F10_P_3): Likewise.
	(VEX_W_0F11_P_0): Likewise.
	(VEX_W_0F11_P_1): Likewise.
	(VEX_W_0F11_P_2): Likewise.
	(VEX_W_0F11_P_3): Likewise.
	(VEX_W_0F12_P_0_M_0): Likewise.
	(VEX_W_0F12_P_0_M_1): Likewise.
	(VEX_W_0F12_P_1): Likewise.
	(VEX_W_0F12_P_2): Likewise.
	(VEX_W_0F12_P_3): Likewise.
	(VEX_W_0F13_M_0): Likewise.
	(VEX_W_0F14): Likewise.
	(VEX_W_0F15): Likewise.
	(VEX_W_0F16_P_0_M_0): Likewise.
	(VEX_W_0F16_P_0_M_1): Likewise.
	(VEX_W_0F16_P_1): Likewise.
	(VEX_W_0F16_P_2): Likewise.
	(VEX_W_0F17_M_0): Likewise.
	(VEX_W_0F28): Likewise.
	(VEX_W_0F29): Likewise.
	(VEX_W_0F2B_M_0): Likewise.
	(VEX_W_0F2E_P_0): Likewise.
	(VEX_W_0F2E_P_2): Likewise.
	(VEX_W_0F2F_P_0): Likewise.
	(VEX_W_0F2F_P_2): Likewise.
	(VEX_W_0F50_M_0): Likewise.
	(VEX_W_0F51_P_0): Likewise.
	(VEX_W_0F51_P_1): Likewise.
	(VEX_W_0F51_P_2): Likewise.
	(VEX_W_0F51_P_3): Likewise.
	(VEX_W_0F52_P_0): Likewise.
	(VEX_W_0F52_P_1): Likewise.
	(VEX_W_0F53_P_0): Likewise.
	(VEX_W_0F53_P_1): Likewise.
	(VEX_W_0F58_P_0): Likewise.
	(VEX_W_0F58_P_1): Likewise.
	(VEX_W_0F58_P_2): Likewise.
	(VEX_W_0F58_P_3): Likewise.
	(VEX_W_0F59_P_0): Likewise.
	(VEX_W_0F59_P_1): Likewise.
	(VEX_W_0F59_P_2): Likewise.
	(VEX_W_0F59_P_3): Likewise.
	(VEX_W_0F5A_P_0): Likewise.
	(VEX_W_0F5A_P_1): Likewise.
	(VEX_W_0F5A_P_3): Likewise.
	(VEX_W_0F5B_P_0): Likewise.
	(VEX_W_0F5B_P_1): Likewise.
	(VEX_W_0F5B_P_2): Likewise.
	(VEX_W_0F5C_P_0): Likewise.
	(VEX_W_0F5C_P_1): Likewise.
	(VEX_W_0F5C_P_2): Likewise.
	(VEX_W_0F5C_P_3): Likewise.
	(VEX_W_0F5D_P_0): Likewise.
	(VEX_W_0F5D_P_1): Likewise.
	(VEX_W_0F5D_P_2): Likewise.
	(VEX_W_0F5D_P_3): Likewise.
	(VEX_W_0F5E_P_0): Likewise.
	(VEX_W_0F5E_P_1): Likewise.
	(VEX_W_0F5E_P_2): Likewise.
	(VEX_W_0F5E_P_3): Likewise.
	(VEX_W_0F5F_P_0): Likewise.
	(VEX_W_0F5F_P_1): Likewise.
	(VEX_W_0F5F_P_2): Likewise.
	(VEX_W_0F5F_P_3): Likewise.
	(VEX_W_0F60_P_2): Likewise.
	(VEX_W_0F61_P_2): Likewise.
	(VEX_W_0F62_P_2): Likewise.
	(VEX_W_0F63_P_2): Likewise.
	(VEX_W_0F64_P_2): Likewise.
	(VEX_W_0F65_P_2): Likewise.
	(VEX_W_0F66_P_2): Likewise.
	(VEX_W_0F67_P_2): Likewise.
	(VEX_W_0F68_P_2): Likewise.
	(VEX_W_0F69_P_2): Likewise.
	(VEX_W_0F6A_P_2): Likewise.
	(VEX_W_0F6B_P_2): Likewise.
	(VEX_W_0F6C_P_2): Likewise.
	(VEX_W_0F6D_P_2): Likewise.
	(VEX_W_0F6F_P_1): Likewise.
	(VEX_W_0F6F_P_2): Likewise.
	(VEX_W_0F70_P_1): Likewise.
	(VEX_W_0F70_P_2): Likewise.
	(VEX_W_0F70_P_3): Likewise.
	(VEX_W_0F71_R_2_P_2): Likewise.
	(VEX_W_0F71_R_4_P_2): Likewise.
	(VEX_W_0F71_R_6_P_2): Likewise.
	(VEX_W_0F72_R_2_P_2): Likewise.
	(VEX_W_0F72_R_4_P_2): Likewise.
	(VEX_W_0F72_R_6_P_2): Likewise.
	(VEX_W_0F73_R_2_P_2): Likewise.
	(VEX_W_0F73_R_3_P_2): Likewise.
	(VEX_W_0F73_R_6_P_2): Likewise.
	(VEX_W_0F73_R_7_P_2): Likewise.
	(VEX_W_0F74_P_2): Likewise.
	(VEX_W_0F75_P_2): Likewise.
	(VEX_W_0F76_P_2): Likewise.
	(VEX_W_0F77_P_0): Likewise.
	(VEX_W_0F7C_P_2): Likewise.
	(VEX_W_0F7C_P_3): Likewise.
	(VEX_W_0F7D_P_2): Likewise.
	(VEX_W_0F7D_P_3): Likewise.
	(VEX_W_0F7E_P_1): Likewise.
	(VEX_W_0F7F_P_1): Likewise.
	(VEX_W_0F7F_P_2): Likewise.
	(VEX_W_0FAE_R_2_M_0): Likewise.
	(VEX_W_0FAE_R_3_M_0): Likewise.
	(VEX_W_0FC2_P_0): Likewise.
	(VEX_W_0FC2_P_1): Likewise.
	(VEX_W_0FC2_P_2): Likewise.
	(VEX_W_0FC2_P_3): Likewise.
	(VEX_W_0FD0_P_2): Likewise.
	(VEX_W_0FD0_P_3): Likewise.
	(VEX_W_0FD1_P_2): Likewise.
	(VEX_W_0FD2_P_2): Likewise.
	(VEX_W_0FD3_P_2): Likewise.
	(VEX_W_0FD4_P_2): Likewise.
	(VEX_W_0FD5_P_2): Likewise.
	(VEX_W_0FD6_P_2): Likewise.
	(VEX_W_0FD7_P_2_M_1): Likewise.
	(VEX_W_0FD8_P_2): Likewise.
	(VEX_W_0FD9_P_2): Likewise.
	(VEX_W_0FDA_P_2): Likewise.
	(VEX_W_0FDB_P_2): Likewise.
	(VEX_W_0FDC_P_2): Likewise.
	(VEX_W_0FDD_P_2): Likewise.
	(VEX_W_0FDE_P_2): Likewise.
	(VEX_W_0FDF_P_2): Likewise.
	(VEX_W_0FE0_P_2): Likewise.
	(VEX_W_0FE1_P_2): Likewise.
	(VEX_W_0FE2_P_2): Likewise.
	(VEX_W_0FE3_P_2): Likewise.
	(VEX_W_0FE4_P_2): Likewise.
	(VEX_W_0FE5_P_2): Likewise.
	(VEX_W_0FE6_P_1): Likewise.
	(VEX_W_0FE6_P_2): Likewise.
	(VEX_W_0FE6_P_3): Likewise.
	(VEX_W_0FE7_P_2_M_0): Likewise.
	(VEX_W_0FE8_P_2): Likewise.
	(VEX_W_0FE9_P_2): Likewise.
	(VEX_W_0FEA_P_2): Likewise.
	(VEX_W_0FEB_P_2): Likewise.
	(VEX_W_0FEC_P_2): Likewise.
	(VEX_W_0FED_P_2): Likewise.
	(VEX_W_0FEE_P_2): Likewise.
	(VEX_W_0FEF_P_2): Likewise.
	(VEX_W_0FF0_P_3_M_0): Likewise.
	(VEX_W_0FF1_P_2): Likewise.
	(VEX_W_0FF2_P_2): Likewise.
	(VEX_W_0FF3_P_2): Likewise.
	(VEX_W_0FF4_P_2): Likewise.
	(VEX_W_0FF5_P_2): Likewise.
	(VEX_W_0FF6_P_2): Likewise.
	(VEX_W_0FF7_P_2): Likewise.
	(VEX_W_0FF8_P_2): Likewise.
	(VEX_W_0FF9_P_2): Likewise.
	(VEX_W_0FFA_P_2): Likewise.
	(VEX_W_0FFB_P_2): Likewise.
	(VEX_W_0FFC_P_2): Likewise.
	(VEX_W_0FFD_P_2): Likewise.
	(VEX_W_0FFE_P_2): Likewise.
	(VEX_W_0F3800_P_2): Likewise.
	(VEX_W_0F3801_P_2): Likewise.
	(VEX_W_0F3802_P_2): Likewise.
	(VEX_W_0F3803_P_2): Likewise.
	(VEX_W_0F3804_P_2): Likewise.
	(VEX_W_0F3805_P_2): Likewise.
	(VEX_W_0F3806_P_2): Likewise.
	(VEX_W_0F3807_P_2): Likewise.
	(VEX_W_0F3808_P_2): Likewise.
	(VEX_W_0F3809_P_2): Likewise.
	(VEX_W_0F380A_P_2): Likewise.
	(VEX_W_0F380B_P_2): Likewise.
	(VEX_W_0F3817_P_2): Likewise.
	(VEX_W_0F381C_P_2): Likewise.
	(VEX_W_0F381D_P_2): Likewise.
	(VEX_W_0F381E_P_2): Likewise.
	(VEX_W_0F3820_P_2): Likewise.
	(VEX_W_0F3821_P_2): Likewise.
	(VEX_W_0F3822_P_2): Likewise.
	(VEX_W_0F3823_P_2): Likewise.
	(VEX_W_0F3824_P_2): Likewise.
	(VEX_W_0F3825_P_2): Likewise.
	(VEX_W_0F3828_P_2): Likewise.
	(VEX_W_0F3829_P_2): Likewise.
	(VEX_W_0F382A_P_2_M_0): Likewise.
	(VEX_W_0F382B_P_2): Likewise.
	(VEX_W_0F3830_P_2): Likewise.
	(VEX_W_0F3831_P_2): Likewise.
	(VEX_W_0F3832_P_2): Likewise.
	(VEX_W_0F3833_P_2): Likewise.
	(VEX_W_0F3834_P_2): Likewise.
	(VEX_W_0F3835_P_2): Likewise.
	(VEX_W_0F3837_P_2): Likewise.
	(VEX_W_0F3838_P_2): Likewise.
	(VEX_W_0F3839_P_2): Likewise.
	(VEX_W_0F383A_P_2): Likewise.
	(VEX_W_0F383B_P_2): Likewise.
	(VEX_W_0F383C_P_2): Likewise.
	(VEX_W_0F383D_P_2): Likewise.
	(VEX_W_0F383E_P_2): Likewise.
	(VEX_W_0F383F_P_2): Likewise.
	(VEX_W_0F3840_P_2): Likewise.
	(VEX_W_0F3841_P_2): Likewise.
	(VEX_W_0F38DB_P_2): Likewise.
	(VEX_W_0F3A08_P_2): Likewise.
	(VEX_W_0F3A09_P_2): Likewise.
	(VEX_W_0F3A0A_P_2): Likewise.
	(VEX_W_0F3A0B_P_2): Likewise.
	(VEX_W_0F3A0C_P_2): Likewise.
	(VEX_W_0F3A0D_P_2): Likewise.
	(VEX_W_0F3A0E_P_2): Likewise.
	(VEX_W_0F3A0F_P_2): Likewise.
	(VEX_W_0F3A21_P_2): Likewise.
	(VEX_W_0F3A40_P_2): Likewise.
	(VEX_W_0F3A41_P_2): Likewise.
	(VEX_W_0F3A42_P_2): Likewise.
	(VEX_W_0F3A62_P_2): Likewise.
	(VEX_W_0F3A63_P_2): Likewise.
	(VEX_W_0F3ADF_P_2): Likewise.
	(VEX_LEN_0F77_P_0): New.
	(prefix_table): Update PREFIX_VEX_0F10, PREFIX_VEX_0F11,
	PREFIX_VEX_0F12, PREFIX_VEX_0F16, PREFIX_VEX_0F2E,
	PREFIX_VEX_0F2F, PREFIX_VEX_0F51, PREFIX_VEX_0F52,
	PREFIX_VEX_0F53, PREFIX_VEX_0F58, PREFIX_VEX_0F59,
	PREFIX_VEX_0F5A, PREFIX_VEX_0F5B, PREFIX_VEX_0F5C,
	PREFIX_VEX_0F5D, PREFIX_VEX_0F5E, PREFIX_VEX_0F5F,
	PREFIX_VEX_0F60, PREFIX_VEX_0F61, PREFIX_VEX_0F62,
	PREFIX_VEX_0F63, PREFIX_VEX_0F64, PREFIX_VEX_0F65,
	PREFIX_VEX_0F66, PREFIX_VEX_0F67, PREFIX_VEX_0F68,
	PREFIX_VEX_0F69, PREFIX_VEX_0F6A, PREFIX_VEX_0F6B,
	PREFIX_VEX_0F6C, PREFIX_VEX_0F6D, PREFIX_VEX_0F6F,
	PREFIX_VEX_0F70, PREFIX_VEX_0F71_REG_2, PREFIX_VEX_0F71_REG_4,
	PREFIX_VEX_0F71_REG_6, PREFIX_VEX_0F72_REG_4,
	PREFIX_VEX_0F72_REG_6, PREFIX_VEX_0F73_REG_2,
	PREFIX_VEX_0F73_REG_3, PREFIX_VEX_0F73_REG_6,
	PREFIX_VEX_0F73_REG_7, PREFIX_VEX_0F74, PREFIX_VEX_0F75,
	PREFIX_VEX_0F76, PREFIX_VEX_0F77, PREFIX_VEX_0F7C,
	PREFIX_VEX_0F7D, PREFIX_VEX_0F7F, PREFIX_VEX_0FC2,
	PREFIX_VEX_0FD0, PREFIX_VEX_0FD1, PREFIX_VEX_0FD2,
	PREFIX_VEX_0FD3, PREFIX_VEX_0FD4, PREFIX_VEX_0FD5,
	PREFIX_VEX_0FD8, PREFIX_VEX_0FD9, PREFIX_VEX_0FDA,
	PREFIX_VEX_0FDC, PREFIX_VEX_0FDD, PREFIX_VEX_0FDE,
	PREFIX_VEX_0FDF, PREFIX_VEX_0FE0, PREFIX_VEX_0FE1,
	PREFIX_VEX_0FE2, PREFIX_VEX_0FE3, PREFIX_VEX_0FE4,
	PREFIX_VEX_0FE5, PREFIX_VEX_0FE6, PREFIX_VEX_0FE8,
	PREFIX_VEX_0FE9, PREFIX_VEX_0FEA, PREFIX_VEX_0FEB,
	PREFIX_VEX_0FEC, PREFIX_VEX_0FED, PREFIX_VEX_0FEE,
	PREFIX_VEX_0FEF, PREFIX_VEX_0FF1. PREFIX_VEX_0FF2,
	PREFIX_VEX_0FF3, PREFIX_VEX_0FF4, PREFIX_VEX_0FF5,
	PREFIX_VEX_0FF6, PREFIX_VEX_0FF8, PREFIX_VEX_0FF9,
	PREFIX_VEX_0FFA, PREFIX_VEX_0FFB, PREFIX_VEX_0FFC,
	PREFIX_VEX_0FFD, PREFIX_VEX_0FFE, PREFIX_VEX_0F3800,
	PREFIX_VEX_0F3801, PREFIX_VEX_0F3802, PREFIX_VEX_0F3803,
	PREFIX_VEX_0F3804, PREFIX_VEX_0F3805, PREFIX_VEX_0F3806,
	PREFIX_VEX_0F3807, PREFIX_VEX_0F3808, PREFIX_VEX_0F3809,
	PREFIX_VEX_0F380A, PREFIX_VEX_0F380B, PREFIX_VEX_0F3817,
	PREFIX_VEX_0F381C, PREFIX_VEX_0F381D, PREFIX_VEX_0F381E,
	PREFIX_VEX_0F3820, PREFIX_VEX_0F3821, PREFIX_VEX_0F3822,
	PREFIX_VEX_0F3823, PREFIX_VEX_0F3824, PREFIX_VEX_0F3825,
	PREFIX_VEX_0F3828, PREFIX_VEX_0F3829, PREFIX_VEX_0F382B,
	PREFIX_VEX_0F382C, PREFIX_VEX_0F3831, PREFIX_VEX_0F3832,
	PREFIX_VEX_0F3833, PREFIX_VEX_0F3834, PREFIX_VEX_0F3835,
	PREFIX_VEX_0F3837, PREFIX_VEX_0F3838, PREFIX_VEX_0F3839,
	PREFIX_VEX_0F383A, PREFIX_VEX_0F383B, PREFIX_VEX_0F383C,
	PREFIX_VEX_0F383D, PREFIX_VEX_0F383E, PREFIX_VEX_0F383F,
	PREFIX_VEX_0F3840, PREFIX_VEX_0F3A08, PREFIX_VEX_0F3A09,
	PREFIX_VEX_0F3A0A, PREFIX_VEX_0F3A0B, PREFIX_VEX_0F3A0C,
	PREFIX_VEX_0F3A0D, PREFIX_VEX_0F3A0E, PREFIX_VEX_0F3A0F,
	PREFIX_VEX_0F3A40 and PREFIX_VEX_0F3A42 entries.
	(vex_table): Update VEX 0F28 and 0F29 entries.
	(vex_len_table): Update VEX_LEN_0F10_P_1, VEX_LEN_0F10_P_3,
	VEX_LEN_0F11_P_1, VEX_LEN_0F11_P_3, VEX_LEN_0F2E_P_0,
	VEX_LEN_0F2E_P_2, VEX_LEN_0F2F_P_0, VEX_LEN_0F2F_P_2,
	VEX_LEN_0F51_P_1, VEX_LEN_0F51_P_3, VEX_LEN_0F52_P_1,
	VEX_LEN_0F53_P_1, VEX_LEN_0F58_P_1, VEX_LEN_0F58_P_3,
	VEX_LEN_0F59_P_1, VEX_LEN_0F59_P_3, VEX_LEN_0F5A_P_1,
	VEX_LEN_0F5A_P_3, VEX_LEN_0F5C_P_1, VEX_LEN_0F5C_P_3,
	VEX_LEN_0F5D_P_1, VEX_LEN_0F5D_P_3, VEX_LEN_0F5E_P_1,
	VEX_LEN_0F5E_P_3, VEX_LEN_0F5F_P_1, VEX_LEN_0F5F_P_3,
	VEX_LEN_0FC2_P_1, VEX_LEN_0FC2_P_3, VEX_LEN_0F3A0A_P_2 and
	VEX_LEN_0F3A0B_P_2 entries.
	(vex_w_table): Remove VEX_W_0F10_P_0, VEX_W_0F10_P_1,
	VEX_W_0F10_P_2, VEX_W_0F10_P_3, VEX_W_0F11_P_0, VEX_W_0F11_P_1,
	VEX_W_0F11_P_2, VEX_W_0F11_P_3, VEX_W_0F12_P_0_M_0,
	VEX_W_0F12_P_0_M_1, VEX_W_0F12_P_1, VEX_W_0F12_P_2,
	VEX_W_0F12_P_3, VEX_W_0F13_M_0, VEX_W_0F14, VEX_W_0F15,
	VEX_W_0F16_P_0_M_0, VEX_W_0F16_P_0_M_1, VEX_W_0F16_P_1,
	VEX_W_0F16_P_2, VEX_W_0F17_M_0, VEX_W_0F28, VEX_W_0F29,
	VEX_W_0F2B_M_0, VEX_W_0F2E_P_0, VEX_W_0F2E_P_2, VEX_W_0F2F_P_0,
	VEX_W_0F2F_P_2, VEX_W_0F50_M_0, VEX_W_0F51_P_0, VEX_W_0F51_P_1,
	VEX_W_0F51_P_2, VEX_W_0F51_P_3, VEX_W_0F52_P_0, VEX_W_0F52_P_1,
	VEX_W_0F53_P_0, VEX_W_0F53_P_1, VEX_W_0F58_P_0, VEX_W_0F58_P_1,
	VEX_W_0F58_P_2, VEX_W_0F58_P_3, VEX_W_0F59_P_0, VEX_W_0F59_P_1,
	VEX_W_0F59_P_2, VEX_W_0F59_P_3, VEX_W_0F5A_P_0, VEX_W_0F5A_P_1,
	VEX_W_0F5A_P_3, VEX_W_0F5B_P_0, VEX_W_0F5B_P_1, VEX_W_0F5B_P_2,
	VEX_W_0F5C_P_0, VEX_W_0F5C_P_1, VEX_W_0F5C_P_2, VEX_W_0F5C_P_3,
	VEX_W_0F5D_P_0, VEX_W_0F5D_P_1, VEX_W_0F5D_P_2, VEX_W_0F5D_P_3,
	VEX_W_0F5E_P_0, VEX_W_0F5E_P_1, VEX_W_0F5E_P_2, VEX_W_0F5E_P_3,
	VEX_W_0F5F_P_0, VEX_W_0F5F_P_1, VEX_W_0F5F_P_2, VEX_W_0F5F_P_3,
	VEX_W_0F60_P_2, VEX_W_0F61_P_2, VEX_W_0F62_P_2, VEX_W_0F63_P_2,
	VEX_W_0F64_P_2, VEX_W_0F65_P_2, VEX_W_0F66_P_2, VEX_W_0F67_P_2,
	VEX_W_0F68_P_2, VEX_W_0F69_P_2, VEX_W_0F6A_P_2, VEX_W_0F6B_P_2,
	VEX_W_0F6C_P_2, VEX_W_0F6D_P_2, VEX_W_0F6F_P_1, VEX_W_0F6F_P_2,
	VEX_W_0F70_P_1, VEX_W_0F70_P_2, VEX_W_0F70_P_3,
	VEX_W_0F71_R_2_P_2, VEX_W_0F71_R_4_P_2, VEX_W_0F71_R_6_P_2,
	VEX_W_0F72_R_2_P_2, VEX_W_0F72_R_4_P_2, VEX_W_0F72_R_6_P_2,
	VEX_W_0F73_R_2_P_2, VEX_W_0F73_R_3_P_2, VEX_W_0F73_R_6_P_2,
	VEX_W_0F73_R_7_P_2, VEX_W_0F74_P_2, VEX_W_0F75_P_2,
	VEX_W_0F76_P_2, VEX_W_0F77_P_0, VEX_W_0F7C_P_2, VEX_W_0F7C_P_3,
	VEX_W_0F7D_P_2, VEX_W_0F7D_P_3, VEX_W_0F7E_P_1, VEX_W_0F7F_P_1,
	VEX_W_0F7F_P_2, VEX_W_0FAE_R_2_M_0, VEX_W_0FAE_R_3_M_0,
	VEX_W_0FC2_P_0, VEX_W_0FC2_P_1, VEX_W_0FC2_P_2, VEX_W_0FC2_P_3,
	VEX_W_0FD0_P_2, VEX_W_0FD0_P_3, VEX_W_0FD1_P_2, VEX_W_0FD2_P_2,
	VEX_W_0FD3_P_2, VEX_W_0FD4_P_2, VEX_W_0FD5_P_2, VEX_W_0FD6_P_2,
	VEX_W_0FD7_P_2_M_1, VEX_W_0FD8_P_2, VEX_W_0FD9_P_2,
	VEX_W_0FDA_P_2, VEX_W_0FDB_P_2, VEX_W_0FDC_P_2, VEX_W_0FDD_P_2,
	VEX_W_0FDE_P_2, VEX_W_0FDF_P_2, VEX_W_0FE0_P_2, VEX_W_0FE1_P_2,
	VEX_W_0FE2_P_2, VEX_W_0FE3_P_2, VEX_W_0FE4_P_2, VEX_W_0FE5_P_2,
	VEX_W_0FE6_P_1, VEX_W_0FE6_P_2, VEX_W_0FE6_P_3,
	VEX_W_0FE7_P_2_M_0, VEX_W_0FE8_P_2, VEX_W_0FE9_P_2,
	VEX_W_0FEA_P_2, VEX_W_0FEB_P_2, VEX_W_0FEC_P_2, VEX_W_0FED_P_2,
	VEX_W_0FEE_P_2, VEX_W_0FEF_P_2, VEX_W_0FF0_P_3_M_0,
	VEX_W_0FF1_P_2, VEX_W_0FF2_P_2, VEX_W_0FF3_P_2, VEX_W_0FF4_P_2,
	VEX_W_0FF5_P_2, VEX_W_0FF6_P_2, VEX_W_0FF7_P_2, VEX_W_0FF8_P_2,
	VEX_W_0FF9_P_2, VEX_W_0FFA_P_2, VEX_W_0FFB_P_2, VEX_W_0FFC_P_2,
	VEX_W_0FFD_P_2, VEX_W_0FFE_P_2, VEX_W_0F3800_P_2,
	VEX_W_0F3801_P_2, VEX_W_0F3802_P_2, VEX_W_0F3803_P_2,
	VEX_W_0F3804_P_2, VEX_W_0F3805_P_2, VEX_W_0F3806_P_2,
	VEX_W_0F3807_P_2, VEX_W_0F3808_P_2, VEX_W_0F3809_P_2,
	VEX_W_0F380A_P_2, VEX_W_0F380B_P_2, VEX_W_0F3817_P_2,
	VEX_W_0F381C_P_2, VEX_W_0F381D_P_2, VEX_W_0F381E_P_2,
	VEX_W_0F3820_P_2, VEX_W_0F3821_P_2, VEX_W_0F3822_P_2,
	VEX_W_0F3823_P_2, VEX_W_0F3824_P_2, VEX_W_0F3825_P_2,
	VEX_W_0F3828_P_2, VEX_W_0F3829_P_2, VEX_W_0F382A_P_2_M_0,
	VEX_W_0F382B_P_2, VEX_W_0F3830_P_2, VEX_W_0F3831_P_2,
	VEX_W_0F3832_P_2, VEX_W_0F3833_P_2, VEX_W_0F3834_P_2,
	VEX_W_0F3835_P_2, VEX_W_0F3837_P_2, VEX_W_0F3838_P_2,
	VEX_W_0F3839_P_2, VEX_W_0F383A_P_2, VEX_W_0F383B_P_2,
	VEX_W_0F383C_P_2, VEX_W_0F383D_P_2, VEX_W_0F383E_P_2,
	VEX_W_0F383F_P_2, VEX_W_0F3840_P_2, VEX_W_0F3841_P_2,
	VEX_W_0F38DB_P_2, VEX_W_0F3A08_P_2, VEX_W_0F3A09_P_2,
	VEX_W_0F3A0A_P_2, VEX_W_0F3A0B_P_2, VEX_W_0F3A0C_P_2,
	VEX_W_0F3A0D_P_2, VEX_W_0F3A0E_P_2, VEX_W_0F3A0F_P_2,
	VEX_W_0F3A21_P_2, VEX_W_0F3A40_P_2, VEX_W_0F3A41_P_2,
	VEX_W_0F3A42_P_2, VEX_W_0F3A62_P_2, VEX_W_0F3A63_P_2 and
	VEX_W_0F3ADF_P_2 entries.
	(mod_table): Update MOD_VEX_0F2B, MOD_VEX_0F50,
	MOD_VEX_0FD7_PREFIX_2, MOD_VEX_0FE7_PREFIX_2,
	MOD_VEX_0FF0_PREFIX_3 and MOD_VEX_0F382A_PREFIX_2 entries.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Set Vex=1 on VEX.128 only vmovd and vmovq
@ 2018-09-18 13:14 sergiodj+buildbot
  2018-09-18 15:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5f787c2bc90793c1d781b7291758e77067daad5 ***

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

x86: Set Vex=1 on VEX.128 only vmovd and vmovq

AVX "VMOVD xmm1, r32/m32", "VMOVD r32/m32, xmm2", "VMOVQ xmm1, r64/m64"
and "VMOVD r64/m64, xmm2" can only be encoded with VEX.128.  Set Vex=1
on VEX.128 only vmovd and vmovq.

gas/

	PR gas/23665
	* testsuite/gas/i386/avx-scalar.s: Remove vmovq and vmovd tests.
	* testsuite/gas/i386/x86-64-avx-scalar.s: Likewise.
	* testsuite/gas/i386/avx-scalar-intel.d: Updated.
	* testsuite/gas/i386/avx-scalar.d: Likewise.
	* testsuite/gas/i386/x86-64-avx-scalar-intel.d: Likewise.
	* testsuite/gas/i386/x86-64-avx-scalar.d: Likewise.
	* testsuite/gas/i386/i386.exp: Run avx-scalar2 and
	x86-64-avx-scalar2.
	* testsuite/gas/i386/avx-scalar-2.d: New file.
	* testsuite/gas/i386/avx-scalar-2.s: Likewise.
	* testsuite/gas/i386/x86-64-avx-scalar-2.d: Likewise.
	* testsuite/gas/i386/x86-64-avx-scalar-2.s: Likewise.

opcodes/

	PR gas/23665
	* i386-dis.c (vex_len_table): Update VEX_LEN_0F6E_P_2 and
	VEX_LEN_0F7E_P_2 entries.
	* i386-opc.tbl: Set Vex=1 on VEX.128 only vmovd and vmovq.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update get_standard_cache_dir for macOS
@ 2018-09-18  9:20 sergiodj+buildbot
  2018-09-18  9:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18  9:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e6cd1dc1e6c0d081382ee21c156b205204efc75b ***

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

Update get_standard_cache_dir for macOS

On macOS the usual cache directory is ~/Library/Caches.  This patch
changes get_standard_cache_dir to use that instead of XDG.

gdb/ChangeLog
2018-09-17  Tom Tromey  <tom@tromey.com>

	* common/pathstuff.c (get_standard_cache_dir): Use
	~/Library/Caches on macOS.
	* common/pathstuff.h (get_standard_cache_dir): Update comment.

gdb/doc/ChangeLog
2018-09-17  Tom Tromey  <tom@tromey.com>

	* gdb.texinfo (Index Files): Update for cache directory change on
	macOS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Replace VexW=3 with VexWIG
@ 2018-09-18  7:31 sergiodj+buildbot
  2018-09-18  7:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18  7:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6fa52824c316091c2beb22fceed9ba96d17f37c4 ***

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

x86: Replace VexW=3 with VexWIG

	* i386-opc.tbl (VexWIG): New.
	Replace VexW=3 with VexWIG.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make save_infcall_*_state return unique pointers
@ 2018-09-18  4:08 sergiodj+buildbot
  2018-09-18  4:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18  4:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb5248409d7a5a10748c2aa70824ecddf2f913d5 ***

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

Make save_infcall_*_state return unique pointers

Simon pointed out that save_infcall_suspend_state and
save_infcall_control_state could return unique pointers.  This patch
implements this idea.

gdb/ChangeLog
2018-09-17  Tom Tromey  <tom@tromey.com>

	* infrun.c (save_infcall_suspend_state): Return
	infcall_suspend_state_up.
	(save_infcall_control_state): Return infcall_control_state_up.
	* inferior.h (save_infcall_suspend_state)
	(save_infcall_control_state): Declare later.  Return unique
	pointers.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanup from infrun.c
@ 2018-09-18  2:42 sergiodj+buildbot
  2018-09-18  2:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18  2:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 117f580a97f721465d62d0630594dafdcd89e4e8 ***

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

Remove cleanup from infrun.c

This removes a cleanup from infrun.c by taking advantage of the
previous patch to introduce a use of unique_xmalloc_ptr.

gdb/ChangeLog
2018-09-17  Tom Tromey  <tom@tromey.com>

	* infrun.c (struct infcall_suspend_state) <registers>: Now a
	unique_ptr.
	<siginfo_data>: Now a unique_xmalloc_ptr.
	(save_infcall_suspend_state, restore_infcall_suspend_state)
	(discard_infcall_suspend_state)
	(get_infcall_suspend_state_regcache): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Don't steal references in the gdb Python code
@ 2018-09-18  1:10 sergiodj+buildbot
  2018-09-18  2:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-18  1:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1a3389079dd5c93419846f44d42027a526ce19cf ***

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

Don't steal references in the gdb Python code

Some Python APIs steal references from their caller, and the refcount
checker supports this via an attribute.

However, in gdb with C++ we have a better idiom available: we can use
std::move on a gdbpy_ref<> instead.  This makes the semantics obvious
at the point of call, and is safer at runtime as well, because the
callee's gdbpy_ref<> will be emptied.

This patch changes the reference-stealing code in gdb to use rvalue
references instead.

Tested on x86-64 Fedora 28.

gdb/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* python/python-internal.h (CPYCHECKER_STEALS_REFERENCE_TO_ARG):
	Remove.
	* python/py-varobj.c (py_varobj_iter_ctor): Change pyiter to
	rvalue reference.  Remove CPYCHECKER_STEALS_REFERENCE_TO_ARG.
	(py_varobj_iter_new): Likewise.
	(py_varobj_get_iterator): Use gdbpy_ref.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Sort objects in gdb and gdbserver Makefiles
@ 2018-09-17 20:34 sergiodj+buildbot
  2018-09-17 20:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 20:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ff03f0bfbf0dc7d125f6ea0b844636c0aba74f6 ***

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

Sort objects in gdb and gdbserver Makefiles

Tom mentioned this a while ago, as a way to give you a cheap sense of
progression in your build, as all object files will be built
alphabetically (including the directory part).  I tried it and I think
it's nice.

gdb/ChangeLog:

	* Makefile.in (LIBGDB_OBS): Sort COMMON_OBS.

gdb/gdbserver/ChangeLog:

	* Makefile.in (gdbserver$(EXEEXT)): Sort OBS.
	(gdbreplay$(EXEEXT)): Sort GDBREPLAY_OBS.
	($(IPA_LIB)): Sort IPA_OBJS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Set the source mask value of all howtos to zero.
@ 2018-09-17 15:20 sergiodj+buildbot
  2018-09-17 15:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 15:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 808325d203f629208ed1988c8a90321c470ebcff ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 808325d203f629208ed1988c8a90321c470ebcff

S12Z: Set the source mask value of all howtos to zero.

Thanks to Alan Modra for this hint.

* bfd/elf32-s12z.c (elf_s12z_howto_table): set all src_mask members to zero.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove CPYCHECKER_RETURNS_BORROWED_REF
@ 2018-09-17 13:47 sergiodj+buildbot
  2018-09-17 15:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 13:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 94c8b7253a5e165ee92f7302f3247764d69b55e5 ***

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

Remove CPYCHECKER_RETURNS_BORROWED_REF

CPYCHECKER_RETURNS_BORROWED_REF is not used, and I think should never
be used.  This patch removes it.

gdb/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* python/python-internal.h (CPYCHECKER_RETURNS_BORROWED_REF):
	Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change thread_to_thread_object to return a new reference
@ 2018-09-17 13:40 sergiodj+buildbot
  2018-09-17 14:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 13:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db1337cc8300bb44f8ccf9dced3e122b6e50b4c9 ***

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

Change thread_to_thread_object to return a new reference

This changes thread_to_thread_object to return a new reference and
fixes up all the callers.

gdb/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* python/python-internal.h (thread_to_thread_object): Change
	return type.
	* python/py-inferior.c (thread_to_thread_object): Return a new
	reference.
	(infpy_thread_from_thread_handle): Update.
	* python/py-infthread.c (gdbpy_selected_thread): Update.
	* python/py-stopevent.c (create_stop_event_object): Update.
	* python/py-threadevent.c (py_get_event_thread): Return a new
	reference.
	(py_get_event_thread): Update.
	* python/py-event.h (py_get_event_thread): Change return type.
	* python/py-continueevent.c (create_continue_event_object):
	Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change pspace_to_pspace_object to return a new reference
@ 2018-09-17 12:57 sergiodj+buildbot
  2018-09-17 14:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 12:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c7aa30778a1615d88c13508c04138ef2499112d ***

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

Change pspace_to_pspace_object to return a new reference

This changes pspace_to_pspace_object to return a new reference and
fixes up all the callers.

gdb/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* python/py-inferior.c (infpy_get_progspace): Update.
	* python/python-internal.h (pspace_to_pspace_object): Change
	return type.
	* python/py-newobjfileevent.c
	(create_clear_objfiles_event_object): Update.
	* python/py-xmethods.c (gdbpy_get_matching_xmethod_workers):
	Update.
	* python/python.c (gdbpy_get_current_progspace): Update.
	(gdbpy_progspaces): Update.
	* python/py-progspace.c (pspace_to_pspace_object): Return a new
	reference.
	* python/py-objfile.c (objfpy_get_progspace): Update.
	* python/py-prettyprint.c (find_pretty_printer_from_progspace):
	Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use GNU style for metasyntactic variables in gdbserver
@ 2018-09-17 12:25 sergiodj+buildbot
  2018-09-17 13:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 12:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 752312ba4e53fea8e77ae240a35a7b508c6ca619 ***

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

Use GNU style for metasyntactic variables in gdbserver

This changes a couple of places in gdbserver to use the GNU style for
metasyntactic variables.

gdb/gdbserver/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* remote-utils.c (remote_open): Use GNU style for metasyntactic
	variables.
	* gdbreplay.c (gdbreplay_usage): Use GNU style for metasyntactic
	variables.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use GNU style for metasyntactic variables in gdb
@ 2018-09-17 12:03 sergiodj+buildbot
  2018-09-17 12:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 12:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65e65158c50dd7e7a5fbc9dcdad9da6df31e01c4 ***

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

Use GNU style for metasyntactic variables in gdb

I searched for other spots that did not use the GNU style for
metasyntactic syntactic variables.  This patch fixes most of the ones
I found in gdb proper.  There are a few remaining in MI, but I was
unsure whether those should be touched.

gdb/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* top.c (new_ui_command): Use GNU style for metasyntactic
	variables.
	* breakpoint.c (stopat_command): Use GNU style for metasyntactic
	variables.
	* maint.c (maintenance_translate_address): Remove "<>" around
	text.
	* interps.c (interpreter_exec_cmd): Use GNU style for
	metasyntactic variables.
	* nto-procfs.c (nto_procfs_target_info): Use GNU style for
	metasyntactic variables.
	* tracepoint.c (tfind_range_command): Use GNU style for
	metasyntactic variables.
	(tfind_outside_command): Likewise.
	(_initialize_tracepoint): Likewise.
	* remote.c (extended_remote_target::create_inferior): Use GNU
	style for metasyntactic variables.
	* sparc64-tdep.c (adi_examine_command): Use GNU style for
	metasyntactic variables.
	(adi_assign_command): Likewise.

gdb/testsuite/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* gdb.base/new-ui.exp (do_execution_tests): Update.
	* gdb.base/dbx.exp (test_breakpoints): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Expand "show disassembler-options" output
@ 2018-09-17 11:30 sergiodj+buildbot
  2018-09-17 12:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17 11:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4bab6ff22a0ddb799c1c492117a15fe0501ff1e ***

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

Expand "show disassembler-options" output

I typed this:

    (gdb) help set disassembler-options
    Set the disassembler options.
    Usage: set disassembler-options OPTION [,OPTION]...

    See: 'show disassembler-options' for valid option values.

... so I tried what it said and got:

    (gdb) show disassembler-options
    The current disassembler options are ''

This surprised me a little, so this patch adds some text to explain
the situation when an architecture does not have disassembler options.

While there I noticed one more spot where gdb was not using the GNU
style for metasyntactic variables.  This patch fixes this as well.

gdb/ChangeLog
2018-09-16  Tom Tromey  <tom@tromey.com>

	* disasm.c (show_disassembler_options_sfunc): Use GNU style for
	metasyntactic variables.  Print message if no disassembler options
	are available.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Set VexW=3 on AVX vrsqrtss
@ 2018-09-17  4:32 sergiodj+buildbot
  2018-09-17  4:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17  4:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db4cc66567397498a9e9eaedb8d0bb8889744ef7 ***

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

x86: Set VexW=3 on AVX vrsqrtss

AVX vrsqrtss is a VEX WIG instruction.

	* i386-opc.tbl: Set VexW=3 on AVX vrsqrtss.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change get_inferior_args to return const char *
@ 2018-09-17  2:36 sergiodj+buildbot
  2018-09-17  2:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17  2:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbaaa0cafcac0630c6f07f81663a1b10a4e197a0 ***

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

Change get_inferior_args to return const char *

I noticed that get_inferior_args should return const char *, because
it is just returning a reference to something owned by the inferior.

I'm checking this in.

gdb/ChangeLog
2018-09-15  Tom Tromey  <tom@tromey.com>

	* infcmd.c (get_inferior_args): Return const char *.
	* inferior.h (get_inferior_args): Return type now const.
	* linux-tdep.c (linux_fill_prpsinfo): Update.
	* procfs.c (procfs_target::make_corefile_notes): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Set Vex=1 on VEX.128 only vmovq
@ 2018-09-17  1:22 sergiodj+buildbot
  2018-09-17  1:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-17  1:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c3741435f315fba956bbace8c4991215e283510 ***

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

x86: Set Vex=1 on VEX.128 only vmovq

AVX "VMOVQ xmm1, xmm2/m64" and "VMOVQ xmm1/m64, xmm2" can only be
encoded with VEX.128.  Set Vex=1 on VEX.128 only vmovq and update
assembler tests.

gas/

	PR gas/23665
	* testsuite/gas/i386/avx-scalar-intel.d: Updated.
	* testsuite/gas/i386/avx-scalar.d: Likewise.
	* testsuite/gas/i386/x86-64-avx-scalar-intel.d: Likewise.
	* testsuite/gas/i386/x86-64-avx-scalar.d: Likewise.

opcodes/

	PR gas/23665
	* i386-dis.c (vex_len_table): Update VEX_LEN_0F7E_P_1 and
	VEX_LEN_0FD6_P_2 entries.
	* i386-opc.tbl: Set Vex=1 on VEX.128 only vmovq.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix possible exception leak in python.c
@ 2018-09-16  7:12 sergiodj+buildbot
  2018-09-16  7:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-16  7:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a3a6aef4090ca13d065d116f5d77f4e3f7bcbf9a ***

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

Fix possible exception leak in python.c

In the Python code, gdb exceptions may not leak into the Python core.
execute_gdb_command was calling bpstat_do_actions outside of a
TRY/CATCH; which seemed risky.  I don't have a test case for this, but
if bpstat_do_actions could ever throw, it could crash gdb.

This patch introduces a new scope in order to preserve the current
semantics, so it is looks a bit bigger than it really is.

Tested on x86-64 Fedora 28.

gdb/ChangeLog
2018-09-07  Tom Tromey  <tom@tromey.com>

	* python/python.c (execute_gdb_command): Call bpstat_do_actions
	inside the TRY.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Provide type_align gdbarch function for nios2.
@ 2018-09-16  6:00 sergiodj+buildbot
  2018-09-16  6:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-16  6:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f70e088ff4ebf79a4bea45e84a8b042706e6e083 ***

Author: Sandra Loosemore <sandra@codesourcery.com>
Branch: master
Commit: f70e088ff4ebf79a4bea45e84a8b042706e6e083

Provide type_align gdbarch function for nios2.

2018-09-14  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/
	* nios2-tdep.c (nios2_type_align): New.
	(nios2_gdb_arch_init): Install type_align hook.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR ld/21375: MIPS: Fix non-zero run-time value for undefined weaks
@ 2018-09-15 20:32 sergiodj+buildbot
  2018-09-15 20:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15 20:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47275900adcda29161e2853179c1fbde4da4c86a ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 47275900adcda29161e2853179c1fbde4da4c86a

PR ld/21375: MIPS: Fix non-zero run-time value for undefined weaks

We have an issue in the MIPS backend, with the handling of undefined
hidden and internal weak symbols.  References to such symbols are
supposed to resolve to 0 according to the ELF gABI[1]:

"Unresolved weak symbols have a zero value."

and the 64-bit MIPS psABI[2]:

"If a symbol with one of these [hidden or internal] attributes has no
definition within the executable/DSO being linked, then it must be
resolved to allocated space if common, resolved to zero if weak, or an
error reported otherwise."

however if a GOT relocation is used, then a local GOT entry is created
and used to satisfy the reference.  Such an entry is then (in DSO and
PIE binaries) subject to the usual load-time relocation, which means a
non-zero value will be returned if the base address is non-zero.  This
will defeat the usual run-time sequence like:

void a (void) __attribute__ ((visibility ("hidden"), weak));

void
x (void)
{
  if (a)
    a ();
}

This can be reproduced with this simple code:

$ cat libtest.c
extern int a __attribute__ ((visibility ("hidden"), weak));

int *
x (void)
{
  return &a;
}
$ cat test.c

int *x (void);

int
main (void)
{
  printf ("a: %p\n", x ());

  return 0;
}
$ gcc -shared -fPIC -o libtest.so libtest.c
$ gcc -o test test.c -Wl,-rpath,$(pwd) libtest.so
$ ./test
a: 0x77184000
$

The usual approach targets take is making all the steps required to
assign a GOT entry for the symbol referred, and then leave its contents
at zero with no dynamic relocation attached, therefore ensuring that the
value does not change at load time.  However this is not going to work
with the implicitly relocated GOT the MIPS psABI specifies[3]:

"The dynamic linker relocates the global offset table by first adding
the difference between the base where the shared object is loaded and
the value of the dynamic tag DT_MIPS_BASE_ADDRESS to all local global
offset table entries."

and we cannot therefore use the local GOT part.

And we cannot offhand use the global part either, as the symbol would
then have to be exported and possibly wrongly preempt symbols in other
modules involved in the dynamic load, because as per the ELF gABI[1] we
are not allowed to enter a hidden or internal symbol into the dynamic
symbol table (and then use its associated GOT entry):

"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."

and:

"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."

So we have to choose something else.

Our choice is further limited by the need for the reference associated
with the GOT relocation to stay within the signed 16-bit limit from the
GOT pointer base register, while being compliant with the ELF gABI and
the MIPS psABI.  However as Alan Modra has observed[4] one possibility
is to edit (relax) the code such that the GOT reference is removed
altogether.

Based on these observations then modify MIPS BFD linker backend code to:

1. Interpret code associated with GOT relocations and relax the usual LW
   or LD instructions into a corresponding immediate load operation that
   places the value of 0 in the intended register, while leaving the GOT
   entry allocated and initialized as usually.

2. Leave any other instructions associated with GOT relocations in place
   and instead redirect the reference to a global GOT entry associated
   with a special `__gnu_absolute_zero' symbol created for this purpose,
   whose value is 0, SHN_ABS section marks it absolute, binding is
   global and export class protected, ensuring that the locally provided
   value is always used at load time, and that the value is not
   relocated by the dynamic loader.

3. Adjust any high-part GOT relocation used, typically associated with
   a LUI instruction, accordingly, so that run-time consistency is
   maintained, either by resolving to the original entry if the
   instruction associated with the corresponding low-part GOT relocation
   has been relaxed to an immediate load (in which case the value loaded
   with LUI will be overwritten), or by also redirecting the reference
   to `__gnu_absolute_zero' to complete the GOT access sequence if that
   symbol has been used.

4. Add a target `elf_backend_hide_symbol' hook, for the three MIPS ABIs,
   which prevents the `__gnu_absolute_zero' symbol from being forced
   local, to ensure that the redirection works and the symbol remains
   global/protected with existing linker scripts unchanged.

5. Observing the issue with handling SHN_ABS symbols in the GNU dynamic
   loader, covered by glibc PR 19818, set the EI_ABIVERSION field in the
   ELF file header produced to 4 (ABI_ABSOLUTE) if `__gnu_absolute_zero'
   symbol has been produced and the target configured indicates the GNU
   operating system, so that broken versions of the GNU dynamic loader
   gracefully reject the file in loading rather than going astray.  Keep
   EI_ABIVERSION at the original value for other operating systems or if
   no `__gnu_absolute_zero' symbol has been made.

The name of the special `__gnu_absolute_zero' has no meaning other than
how a human reader can interpret it, as it is ignored in dynamic loading
in the handling of the scenarios concerned.  This is because the symbol
resolves locally, and it's only the symbol's attributes that matter so
that the associated GOT entry remains unchanged at load time.

Therefore the name is somewhat arbitrary, observing however the need to
use the name space reserved for the system so that it does not conflict
with a possible user symbol, and hence the leading underscore, and also
the `gnu' infix to denote a GNU feature.  Other implementations wishing
to address the problem in a similar way may choose a different name and
have the solution still work, possibly with a mixture of modules used in
a dynamic having symbols of different names provided, which will however
not interact with each other due to the protected export class.

The symbol can be referred explicitly, however the name is an internal
implementation detail rather than a part of the ABI, and therefore no
specific semantics is guaranteed.

One limitation of this change is that if `__gnu_absolute_zero' has been
already defined, then we do not wipe the old definition and all kinds of
odd behavior can result.  This is however like with other symbols we
internally define, such as `_GLOBAL_OFFSET_TABLE_' or `__rld_map', and
therefore left as a possible future enhancement.

As an optimization the relaxation of LW and LD instructions to a load of
immediate zero is always made, even SVR4 PIC code for code that will end
up in a regular (non-PIE) executable, because there is a cache advantage
with the avoidance of a load from the GOT, even if it is otherwise
guaranteed to remain zero.  It does not reliably happen though, due to a
symbol exportation issue affecting executables, covered by PR ld/21805.

One existing test case needs to be updated, as it triggers relaxation
introduced with this change and consequently linker output does not
match expectations anymore.  As we want to keep the original issue
covered with the test case modify it then to use the LWL instruction in
place of LW, and adjust the output expected accordingly.

References:

[1] "System V Application Binary Interface - DRAFT - 19 October 2010",
    The SCO Group, Section "Symbol Table",
    <http://www.sco.com/developers/gabi/2012-12-31/ch4.symtab.html>

[2] "64-bit ELF Object File Specification, Draft Version 2.5", MIPS
    Technologies / Silicon Graphics Computer Systems, Order Number
    007-4658-001, Section 2.5 "Symbol Table", p. 22,
    <http://techpubs.sgi.com/library/manuals/4000/007-4658-001/pdf/007-4658-001.pdf>

[3] "SYSTEM V APPLICATION BINARY INTERFACE, MIPS RISC Processor
    Supplement, 3rd Edition", Section "Global Offset Table", p. 5-10,
    <http://www.linux-mips.org/pub/linux/mips/doc/ABI/mipsabi.pdf>

[4] "Undo dynamic symbol state after regular object sym type mismatch",
    <https://sourceware.org/ml/binutils/2017-07/msg00265.html>

	bfd/
	PR ld/21375
	* elfxx-mips.h (_bfd_mips_elf_hide_symbol): New prototype.
	(_bfd_mips_elf_linker_flags): Update prototype.
	* elf32-mips.c (elf_backend_hide_symbol): New macro.
	* elf64-mips.c (elf_backend_hide_symbol): Likewise.
	* elfn32-mips.c (elf_backend_hide_symbol): Likewise.
	* elfxx-mips.c (mips_elf_link_hash_table): Add
	`use_absolute_zero' and `gnu_target' members.
	(mips_elf_record_global_got_symbol): Call
	`_bfd_mips_elf_hide_symbol' rather than
	`_bfd_elf_link_hash_hide_symbol'.
	(mips_use_local_got_p): Return FALSE if the symbol is absolute.
	(mips_elf_obtain_contents): Reorder function.
	(mips_elf_nullify_got_load): New function.
	(mips_elf_calculate_relocation): Add `contents' parameter.
	Nullify GOT loads or if it is not possible, then redirect GOT
	relocations to the `__gnu_absolute_zero' symbol, for references
	that are supposed to resolve to zero.
	(mips_elf_define_absolute_zero): New function.
	(_bfd_mips_elf_check_relocs): Prepare for arrangements made in
	`mips_elf_calculate_relocation' for references made via the GOT
	that are supposed to resolve to zero.
	(_bfd_mips_elf_hide_symbol): New function.
	(_bfd_mips_elf_linker_flags): Add the `gnu_target' parameter,
	set the `gnu_target' member of the MIPS hash table.
	(MIPS_LIBC_ABI_ABSOLUTE): New enumeration constant.
	(_bfd_mips_post_process_headers): Use it.

	ld/
	PR ld/21375
	* emultempl/mipself.em: Set `gnu_target' according to ${target}.
	(mips_create_output_section_statements): Update call to
	`_bfd_mips_elf_linker_flags'.
	* testsuite/ld-mips-elf/pr21334.s: Use LWL rather than LW.
	* testsuite/ld-mips-elf/pr21334.dd: Update accordingly.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Support VEX/EVEX WIG encoding
@ 2018-09-15 19:03 sergiodj+buildbot
  2018-09-15 19:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6865c0435a54e6d5f1fcc5cdcd56895e9a3c5484 ***

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

x86: Support VEX/EVEX WIG encoding

Add VEXWIG, defined as 3, to indicate that the VEX.W/EVEX.W bit is
ignored by such VEX/EVEX instructions, aka WIG instructions.  Set
VexW=3 on VEX/EVEX WIG instructions.  Update assembler to check
VEXWIG when setting the VEX.W bit.

gas/

	PR gas/23642
	* config/tc-i386.c (build_vex_prefix): Check VEXWIG when setting
	the VEX.W bit.
	(build_evex_prefix): Check VEXWIG when setting the EVEX.W bit.

opcodes/

	PR gas/23642
	* i386-opc.h (VEXWIG): New.
	* i386-opc.tbl: Set VexW=3 on VEX/EVEX WIG instructions.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Handle unsupported static rounding in vcvt[u]si2sd in 32-bit mode
@ 2018-09-15 17:16 sergiodj+buildbot
  2018-09-15 17:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15 17:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70df6fc9bc9e114f46532dbe58caa98e495b119c ***

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

x86: Handle unsupported static rounding in vcvt[u]si2sd in 32-bit mode

Update x86 disassembler to handle the unsupported static rounding in
vcvt[u]si2sd in 32-bit mode.

gas/

	PR binutils/23655
	* testsuite/gas/i386/evex.d: Updated.

opcodes/

	PR binutils/23655
	* i386-dis-evex.h: Replace EXxEVexR with EXxEVexR64 for
	vcvtsi2sd%LQ and vcvtusi2sd%LQ.
	* i386-dis.c (EXxEVexR64): New.
	(evex_rounding_64_mode): Likewise.
	(OP_Rounding): Handle evex_rounding_64_mode.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Properly decode EVEX.W in vcvt[u]si2s[sd] in 32-bit mode
@ 2018-09-15 16:19 sergiodj+buildbot
  2018-09-15 16:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15 16:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d20dee9efad3c23c9098f03ac785037572258483 ***

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

x86: Properly decode EVEX.W in vcvt[u]si2s[sd] in 32-bit mode

Update x86 disassembler to ignore the EVEX.W bit in EVEX vcvt[u]si2s[sd]
instructions in 32-bit mode.

gas/

	PR binutils/23655
	* testsuite/gas/i386/evex.d: New file.
	* testsuite/gas/i386/evex.s: Likewise.
	* testsuite/gas/i386/i386.exp: Run evex.

opcodes/

	PR binutils/23655
	* i386-dis-evex.h (evex_table): Replace Eq with Edqa for
	vcvtsi2ss%LQ, vcvtsi2sd%LQ, vcvtusi2ss%LQ and vcvtusi2sd%LQ.
	* i386-dis.c (Edqa): New.
	(dqa_mode): Likewise.
	(intel_operand_size): Handle dqa_mode as m_mode.
	(OP_E_register): Handle dqa_mode as dq_mode.
	(OP_E_memory): Set shift for dqa_mode based on address_mode.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] i386: Reformat OP_E_memory
@ 2018-09-15 11:06 sergiodj+buildbot
  2018-09-15 12:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15 11:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5074ad8a66ab2e955cf3ae4dba5773d5aa67b29b ***

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

i386: Reformat OP_E_memory

	* i386-dis.c (OP_E_memory): Reformat.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove an unnecessary block in call_function_by_hand_dummy
@ 2018-09-15  9:45 sergiodj+buildbot
  2018-09-15 11:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15  9:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4b08fa2aa25f245c77921ad2405c15d30e421ed ***

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

Remove an unnecessary block in call_function_by_hand_dummy

I noticed that call_function_by_hand_dummy has a block that only
exists to declare a variable, like:

    {
      int i;
      for (i = ...0)
	...
    }

This patch removes the unnecessary and the extra indentation by moving
the declaration into the "for".

gdb/ChangeLog
2018-09-14  Tom Tromey  <tom@tromey.com>

	* infcall.c (call_function_by_hand_dummy): Remove unnecessary
	block.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] csky: Support PC relative diff relocation
@ 2018-09-15  9:05 sergiodj+buildbot
  2018-09-15 10:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15  9:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fe75f42ee15944a0d14d3d42b242676fc2417352 ***

Author: Lifang Xia <lifang_xia@c-sky.com>
Branch: master
Commit: fe75f42ee15944a0d14d3d42b242676fc2417352

csky: Support PC relative diff relocation

Define DIFF_EXPR_OK to Support PC relative diff relocation,
and add CKCORE_PCREL32 relocation process

bfd/
        * elf32-csky.c (csky_elf_howto_table): Fill special_function of
        R_CKCORE_PCREL32.
        (csky_elf_relocate_section): Add R_CKCORE_PCREL32 process.
gas/
        * config/tc-csky.c (md_apply_fix): Transmit
        BFD_RELOC_32_PCREL to BFD_RELOC_CKCORE_PCREL32.
        (tc_gen_reloc): Trasmit BFD_RELOC_CKCORE_ADDR32 to
        BFD_RELOC_CKCORE_PCREL32 while pc-relative.
        * config/tc-csky.h (DIFF_EXPR_OK): Define to enable PC relative
        diff relocs.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23425, unresolved symbol diagnostic
@ 2018-09-15  4:21 sergiodj+buildbot
  2018-09-15  5:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15  4:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a4cd947aca23d58966ead843e120f4c19db01030 ***

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

PR23425, unresolved symbol diagnostic

dwarf2.c code reasonably assumes that debug info is local to a file,
an assumption now violated by gcc, resulting in "DWARF error: invalid
abstract instance DIE ref" or wrong details when attempting to print
linker error messages with file, function and line reported.

This is because find_abstract_instance is only prepared to handle
DW_FORM_ref_addr when the .debug_info section referenced is in the
current file.  When that isn't the case, relocations to access another
file's .debug_info will typically be against a symbol defined at the
start of that .debug_info section, plus an addend.  Since the dwarf2.c
code only considers the current file's debug info, that symbol will be
undefined, resolving to zero.  In effect the ref_addr will wrongly
resolve to the current file's .debug_info.

This patch avoids the problem by treating relocations in debug
sections against undefined symbols in a similar manner to the way
relocations against symbols defined in discarded sections are
resolved.  They result in a zero value (except in .debug_ranges)
regardless of the addend.

	PR 23425
	* reloc.c (bfd_generic_get_relocated_section_contents): Zero reloc
	fields in debug sections when reloc is against an undefined symbol
	and called from bfd_simple_get_relocated_section_contents or
	similar.
	* dwarf2.c (find_abstract_instance): Return true for zero offset
	DW_FORM_ref_addr without returning values.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold CRC32 templates
@ 2018-09-15  3:58 sergiodj+buildbot
  2018-09-15  4:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15  3:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 556059dd13a8a9a30b23eacbefbe7b85e74ce7b7 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 556059dd13a8a9a30b23eacbefbe7b85e74ce7b7

x86: fold CRC32 templates

Just like other insns having byte and word forms, these can also make
use of the W modifier, which at the same time allows simplifying some
other code a little bit.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanup from try_open_exec_file
@ 2018-09-15  1:00 sergiodj+buildbot
  2018-09-15  1:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97e67fc62045723db7af6d323ce9c428666ab6f5 ***

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

Remove cleanup from try_open_exec_file

This removes a cleanup from try_open_exec_file, using std::string to
manage the storage instead.

gdb/ChangeLog
2018-09-13  Tom Tromey  <tom@tromey.com>

	* exec.c (try_open_exec_file): Use std::string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Testsuite: Add gdb_simple_compile
@ 2018-09-15  0:20 sergiodj+buildbot
  2018-09-15  3:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-15  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf326452537c11deece2aabe16b6b9d62388a2d9 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: bf326452537c11deece2aabe16b6b9d62388a2d9

Testsuite: Add gdb_simple_compile

Simplfy gdb.exp by adding a function that will attempt to
compile a piece of code, then clean up, leaving the created
object.

gdb/testsuite

        * lib/gdb.exp (gdb_simple_compile): Add proc.
        (is_elf_target): Use gdb_simple_compile.
        (skip_altivec_tests): Likewise.
        (skip_vsx_tests): Likewise.
        (skip_tsx_tests): Likewise.
        (skip_btrace_tests): Likewise.
        (skip_btrace_pt_tests): Likewise.
        (gdb_can_simple_compile): Likewise.
        (gdb_has_argv0): Likewise.
        (gdb_target_symbol_prefix): Likewise.
        (target_supports_scheduler_locking): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] python: Add Progspace.objfiles method
@ 2018-09-14 22:10 sergiodj+buildbot
  2018-09-14 22:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 22:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ae1a3211adcb8e7518b0b656b2309ebbc45e9ae ***

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

python: Add Progspace.objfiles method

This patch adds an objfiles method to the Progspace object, which
returns a sequence of the objfiles associated to that program space.  I
chose a method rather than a property for symmetry with gdb.objfiles().

gdb/ChangeLog:

	* python/py-progspace.c (PSPY_REQUIRE_VALID): New macro.
	(pspy_get_objfiles): New function.
	(progspace_object_methods): New.
	(pspace_object_type): Add tp_methods callback.
	* python/python-internal.h (build_objfiles_list): New
	declaration.
	* python/python.c (build_objfiles_list): New function.
	(gdbpy_objfiles): Implement using build_objfiles_list.
	* NEWS: Mention the Progspace.objfiles method.

gdb/doc/ChangeLog:

	* python.texi (Program Spaces In Python): Document the
	Progspace.objfiles method.
	(Objfiles In Python): Mention that gdb.objfiles() is identical
	to gdb.selected_inferior().progspace.objfiles().

gdb/testsuite/ChangeLog:

	* gdb.python/py-progspace.exp: Test the Progspace.objfiles
	method.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] python: Add Inferior.progspace property
@ 2018-09-14 21:28 sergiodj+buildbot
  2018-09-14 21:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 21:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a40bf0c2e93daac4ae4ce7dd1c43ab6135e76720 ***

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

python: Add Inferior.progspace property

This patch adds a progspace property to the gdb.Inferior type, which
allows getting the gdb.Progspace object associated to that inferior.
In conjunction with the following patch, this will allow scripts iterate
on objfiles associated with a particular inferior.

gdb/ChangeLog:

	* python/py-inferior.c (infpy_get_progspace): New function.
	(inferior_object_getset): Add progspace property.
	* NEWS: Mention the new property.

gdb/doc/ChangeLog:

	* python.texi (Inferiors In Python): Document
	Inferior.progspace.
	(Program Spaces In Python): Document that
	gdb.current_progspace() is the same as
	gdb.selected_inferior().progspace.

gdb/testsuite/ChangeLog:

	* gdb.python/py-inferior.exp: Add tests for Inferior.progspace
	and a few other Inferior properties when the Inferior is no
	longer valid.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] python: Provide textual representation for Inferior and Objfile
@ 2018-09-14 18:27 sergiodj+buildbot
  2018-09-14 18:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 18:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1256af7d1afb123c15ae3935de4470becdf7c512 ***

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

python: Provide textual representation for Inferior and Objfile

Printing a GDB Python object is notoriously not helpful:

>>> print(gdb.selected_inferior())
<gdb.Inferior object at 0x7fea59aed198>
>>> print(gdb.objfiles())
[<gdb.Objfile object at 0x7fea59b57c90>]

This makes printing debug traces more difficult than it should be.  This
patch provides some repr() implementation for these two types (more to
come if people agree with the idea, but I want to test the water first).
Here's the same example as above, but with this patch:

>>> print(gdb.selected_inferior())
<gdb.Inferior num=1>
>>> print(gdb.objfiles())
[<gdb.Objfile filename=/home/emaisin/build/binutils-gdb-gcc-git/gdb/test>]

I implemented repr rather than str, because when printing a list (or
another container I suppose), Python calls the repr method of the
elements.  This is useful when printing a list of inferiors or objfiles.
The print(gdb.objfiles()) above would not have worked if I had
implemented str.

I found this post useful to understand the difference between repr and
str:

  https://stackoverflow.com/questions/1436703/difference-between-str-and-repr

gdb/ChangeLog:

	* python/py-inferior.c (infpy_repr): New.
	(inferior_object_type): Register infpy_repr.
	* python/py-objfile.c (objfpy_repr): New.
	(objfile_object_type): Register objfpy_repr.

gdb/testsuite/ChangeLog:

	* gdb.python/py-inferior.exp: Test repr() of gdb.Inferior.
	* gdb.python/py-objfile.exp: Test repr() of gdb.Objfile.
	* gdb.python/py-symtab.exp: Update test printing an objfile.

gdb/doc/ChangeLog:

	* python.texi (Basic Python): Mention the string representation
	of GDB Python objects.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Remove VexW=1 from WIG VEX movq and vmovq
@ 2018-09-14 17:56 sergiodj+buildbot
  2018-09-14 18:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5be12fc1ad9e47e82bd8902ad6a1f71946c58805 ***

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

x86: Remove VexW=1 from WIG VEX movq and vmovq

Put back changes lost in commit 41d1ab6a6d96937fd0db04e53746f93f53687807.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX512_4* insns
@ 2018-09-14 15:05 sergiodj+buildbot
  2018-09-14 15:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 15:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2589a7e59bdd0c3f9647bf79e5d0ab107216f976 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 2589a7e59bdd0c3f9647bf79e5d0ab107216f976

x86: drop bogus IgnoreSize from AVX512_4* insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Generate more tags in gdb/testsuite/Makefile
@ 2018-09-14 14:59 sergiodj+buildbot
  2018-09-15  2:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 14:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2361b0fb1d99e9c0b97f4c1f42f89f862d757128 ***

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

Generate more tags in gdb/testsuite/Makefile

I noticed that the TAGS target in gdb/testsuite/Makefile does not pick
up Tcl procs defined with proc_with_prefix or gdb_caching_proc.  This
patch fixes this by updating the regexp.

Tested in Emacs.

gdb/testsuite/ChangeLog
2018-09-13  Tom Tromey  <tom@tromey.com>

	* Makefile.in (TAGS): Recognize proc_with_prefix and
	gdb_caching_proc.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return std::string from gdb_bfd_errmsg
@ 2018-09-14 13:59 sergiodj+buildbot
  2018-09-14 23:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 13:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 803c08d083556154cd4d27368e58b359e9de8b93 ***

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

Return std::string from gdb_bfd_errmsg

This changes gdb_bfd_errmsg to return a std::string, removing a
cleanup.  This approach may be slightly less efficient than the
previous code, but I don't believe this is very important in this
situation.

gdb/ChangeLog
2018-09-13  Tom Tromey  <tom@tromey.com>

	* utils.h (gdb_bfd_errmsg): Return std::string.
	* exec.c (exec_file_attach): Update.
	* compile/compile-object-load.c (compile_object_load): Update.
	* utils.c (gdb_bfd_errmsg): Return std::string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanup from procfs.c
@ 2018-09-14 13:48 sergiodj+buildbot
  2018-09-14 22:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 13:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b4cbbe357aaf6462a68e1a15c9532dd3d01e06d ***

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

Remove cleanup from procfs.c

This removes the last remaining cleanup from procfs.c, replacing it
with a unique_ptr specialization.

gdb/ChangeLog
2018-09-13  Tom Tromey  <tom@tromey.com>

	* procfs.c (struct procinfo_deleter): New.
	(procinfo_up): New typedef.
	(do_destroy_procinfo_cleanup): Remove.
	(procfs_target::info_proc): Use procinfo_up.  Remove cleanups.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX512VL insns
@ 2018-09-14 13:04 sergiodj+buildbot
  2018-09-14 13:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 13:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9caa306f8020d5c9bfa84b88f4922f60763ea77a ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 9caa306f8020d5c9bfa84b88f4922f60763ea77a

x86: drop bogus IgnoreSize from AVX512VL insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX512F insns
@ 2018-09-14 12:05 sergiodj+buildbot
  2018-09-14 12:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a8da8866974e139642b4bb41d7c252d509fd2a0 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 6a8da8866974e139642b4bb41d7c252d509fd2a0

x86: drop bogus IgnoreSize from AVX512F insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix crash with empty Rust enum
@ 2018-09-14  8:17 sergiodj+buildbot
  2018-09-14 19:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 098b2108a2b61531c0bc8ea16854f773083a95d7 ***

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

Fix crash with empty Rust enum

While testing my Rust compiler patch to fix the DWARF representation
of Rust enums (https://github.com/rust-lang/rust/pull/54004), I found
a gdb crash coming from one of the Rust test cases.

The bug here is that the new variant support in gdb does not handle
the case where there are no variants in the enum.

This patch fixes the problem in a straightforward way.  Note that the
new tests are somewhat lax because I did not want to try to fully fix
this corner case for older compilers.  If you think that's
unacceptable, let meknow.

Tested on x86-64 Fedora 28 using several versions of the Rust
compiler.  I intend to push this to the 8.2 branch as well.

gdb/ChangeLog
2018-09-13  Tom Tromey  <tom@tromey.com>

	PR rust/23626:
	* rust-lang.c (rust_enum_variant): Now static.
	(rust_empty_enum_p): New function.
	(rust_print_enum, rust_evaluate_subexp, rust_print_struct_def):
	Handle empty enum.

gdb/testsuite/ChangeLog
2018-09-13  Tom Tromey  <tom@tromey.com>

	PR rust/23626:
	* gdb.rust/simple.rs (EmptyEnum): New type.
	(main): Use it.
	* gdb.rust/simple.exp (test_one_slice): Add empty enum test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add "contrib" to the list of GDB support dirs (on src-release.sh)
@ 2018-09-14  7:16 sergiodj+buildbot
  2018-09-14 19:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  7:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80ca5f98b86c9b209f392cb52dde8b8471856c5a ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 80ca5f98b86c9b209f392cb52dde8b8471856c5a

Add "contrib" to the list of GDB support dirs (on src-release.sh)

On commit:

  commit 5a6996172e6294ea37054b1a9caa3a923a8fe399
  Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
  Date:   Mon Aug 6 16:05:16 2018 +0200

      Update dg-extract-results.* from gcc

dg-extract-results.sh was moved from the "gdb/contrib/" directory to
the toplevel "contrib/" directory.  However, src-release.sh was not
updated in order to include "contrib/" in the tarball release of GDB.
This makes it very inconvenient to run and analyze the GDB testsuite
results.  This commit adds "contrib/" to the list of support
directories that are included in each GDB release.

ChangeLog:
2018-09-12  Sergio Durigan Junior  <sergiodj@redhat.com>

	* src-release.sh (GDB_SUPPORT_DIRS): Add "contrib".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from SSE4.2 insns
@ 2018-09-14  6:38 sergiodj+buildbot
  2018-09-14  6:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  6:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0001cfd00ce30c5a06c938eb0fb203451870ef85 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 0001cfd00ce30c5a06c938eb0fb203451870ef85

x86: drop bogus IgnoreSize from SSE4.2 insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from a few further insns
@ 2018-09-14  4:41 sergiodj+buildbot
  2018-09-14 16:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57f6375ec10415fc26bbfaf4fdc19effb313a06d ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 57f6375ec10415fc26bbfaf4fdc19effb313a06d

x86: drop bogus IgnoreSize from a few further insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX512DQ insns
@ 2018-09-14  3:57 sergiodj+buildbot
  2018-09-14 14:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  3:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a760eb41aac52948ac28f4a47563565396a7c37a ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: a760eb41aac52948ac28f4a47563565396a7c37a

x86: drop bogus IgnoreSize from AVX512DQ insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX512BW insns
@ 2018-09-14  3:49 sergiodj+buildbot
  2018-09-14 13:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  3:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e90426589d7c783b7e458162baaac1431fc33bd5 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: e90426589d7c783b7e458162baaac1431fc33bd5

x86: drop bogus IgnoreSize from AVX512BW insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from SHA insns
@ 2018-09-14  2:48 sergiodj+buildbot
  2018-09-14 11:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  2:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7f279191fd49f9e4e302cb65268e6df595f2761 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: c7f279191fd49f9e4e302cb65268e6df595f2761

x86: drop bogus IgnoreSize from SHA insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX2 insns
@ 2018-09-14  2:28 sergiodj+buildbot
  2018-09-14 10:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  2:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fbbbee5e78e590ecee718e8da4f229fb59fe9c5 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 2fbbbee5e78e590ecee718e8da4f229fb59fe9c5

x86: drop bogus IgnoreSize from AVX2 insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from AVX insns
@ 2018-09-14  2:04 sergiodj+buildbot
  2018-09-14  9:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  2:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b02b9a2abfc773ad3cce49ecc36c37a1a84bcc9 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 2b02b9a2abfc773ad3cce49ecc36c37a1a84bcc9

x86: drop bogus IgnoreSize from AVX insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from GNFI insns
@ 2018-09-14  1:46 sergiodj+buildbot
  2018-09-14  9:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  1:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 963c68aa4af4bf9448aa1d2ee03fc13cc88da0f5 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 963c68aa4af4bf9448aa1d2ee03fc13cc88da0f5

x86: drop bogus IgnoreSize from GNFI insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from PCLMUL/VPCLMUL insns
@ 2018-09-14  1:38 sergiodj+buildbot
  2018-09-14  7:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  1:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64e025c3a16d05c640d20192ac32728b05ee0415 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 64e025c3a16d05c640d20192ac32728b05ee0415

x86: drop bogus IgnoreSize from PCLMUL/VPCLMUL insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from SSE4.1 insns
@ 2018-09-14  0:04 sergiodj+buildbot
  2018-09-14  5:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-14  0:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be4b452e28df8a18cbb7f3af929512722b003ba1 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: be4b452e28df8a18cbb7f3af929512722b003ba1

x86: drop bogus IgnoreSize from SSE4.1 insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from SSE3 insns
@ 2018-09-13 23:42 sergiodj+buildbot
  2018-09-14  4:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 23:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07599e13ac3a65c5dfb692bf9891758463949cfc ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 07599e13ac3a65c5dfb692bf9891758463949cfc

x86: drop bogus IgnoreSize from SSE3 insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop bogus IgnoreSize from SSE2 insns
@ 2018-09-13 23:25 sergiodj+buildbot
  2018-09-14  2:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 23:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ee3e48715c188bab4db68476b54161535839d6a ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 1ee3e48715c188bab4db68476b54161535839d6a

x86: drop bogus IgnoreSize from SSE2 insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop unnecessary {,No}Rex64
@ 2018-09-13 23:12 sergiodj+buildbot
  2018-09-14  1:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 23:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49d5d12d0e5b80afc376c6bb9be4976efb53425c ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 49d5d12d0e5b80afc376c6bb9be4976efb53425c

x86: drop unnecessary {,No}Rex64


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: also allow D on 3-operand insns
@ 2018-09-13 22:57 sergiodj+buildbot
  2018-09-14  0:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f5eb1d70fb8ed38290413acae2617fe899a1663c ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: f5eb1d70fb8ed38290413acae2617fe899a1663c

x86: also allow D on 3-operand insns

For now this is just for VMOVS{D,S}.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86-64: bndmk, bndldx, and bndstx don't allow RIP-relative addressing
@ 2018-09-13 22:29 sergiodj+buildbot
  2018-09-13 22:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 22:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d276ec695e8954330e922807d6886b8212d6323b ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: d276ec695e8954330e922807d6886b8212d6323b

x86-64: bndmk, bndldx, and bndstx don't allow RIP-relative addressing


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused "tmp" variable.
@ 2018-09-13 20:29 sergiodj+buildbot
  2018-09-13 21:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 20:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f117a62c5debd8a46fb4f76eba784d433d1bb875 ***

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

Remove unused "tmp" variable.

gdb/ChangeLog:

	* fbsd-nat.c (fbsd_nat_target::info_proc): Remove unused variable.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix a typo in a comment.
@ 2018-09-13 19:20 sergiodj+buildbot
  2018-09-13 19:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 19:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 88f22c34d0f39ee4aca87940bff2cbf47e64b9d7 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 88f22c34d0f39ee4aca87940bff2cbf47e64b9d7

Fix a typo in a comment.

gdb/ChangeLog:

	* aarch64-fbsd-tdep.h (AARCH64_FBSD_SIZEOF_GREGSET): Fix comment
	typo.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] python: Add tests for trying to use an invalid Inferior object
@ 2018-09-13 18:38 sergiodj+buildbot
  2018-09-13 18:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 18:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4aa8e6c2387e796649279c2190cd499b579d028c ***

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

python: Add tests for trying to use an invalid Inferior object

This patch adds tests for trying to use property or methods on a
gdb.Inferior object that represents an inferior that does not exist
anymore.  We expect an exception to be thrown.

gdb/testsuite/ChangeLog:

	* gdb.python/py-inferior.exp: Test using an invalid gdb.Inferior
	object.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move 'is_regular_file' from common-utils.c to filestuff.c
@ 2018-09-13 17:42 sergiodj+buildbot
  2018-09-13 18:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 17:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c025cfe5efc44eb4dfb03b53dca28e75096dd1e ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 3c025cfe5efc44eb4dfb03b53dca28e75096dd1e

Move 'is_regular_file' from common-utils.c to filestuff.c

There is no reason for 'is_regular_file' to be in common-utils.c; it
belongs to 'filestuff.c'.  This commit moves the function definition
and its prototype to the appropriate files.

The motivation behind this move is a failure that happens on certain
cross-compilation environments when compiling the IPA library, due to
the way gnulib probes the need for a 'stat' call replacement.  Because
configure checks when cross-compiling are more limited, gnulib decides
that it needs to substitute the 'stat' calls its own 'rpl_stat';
however, the IPA library doesn't link with gnulib, which leads to an
error when compiling 'common-utils.c':

  ...
  /opt/x86-core2--musl--bleeding-edge-2018.09-1/bin/i686-buildroot-linux-musl-g++  -shared -fPIC -Wl,--soname=libinproctrace.so -Wl,--no-undefined -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os      -I. -I. -I./../common -I./../regformats -I./.. -I./../../include -I./../gnulib/import -Ibuild-gnulib-gdbserver/import -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-narrowing -Wno-error=maybe-uninitialized  -DGDBSERVER \
   -Wl,--dynamic-list=./proc-service.list -o libinproctrace.so ax-ipa.o common-utils-ipa.o errors-ipa.o format-ipa.o print-utils-ipa.o regcache-ipa.o remote-utils-ipa.o rsp-low-ipa.o tdesc-ipa.o tracepoint-ipa.o utils-ipa.o vec-ipa.o linux-i386-ipa.o linux-x86-tdesc-ipa.o arch/i386-ipa.o -ldl -pthread
  /opt/x86-core2--musl--bleeding-edge-2018.09-1/lib/gcc/i686-buildroot-linux-musl/8.2.0/../../../../i686-buildroot-linux-musl/bin/ld: common-utils-ipa.o: in function `is_regular_file(char const*, int*)':
  common-utils.c:(.text+0x695): undefined reference to `rpl_stat'
  collect2: error: ld returned 1 exit status
  Makefile:413: recipe for target 'libinproctrace.so' failed
  make[1]: *** [libinproctrace.so] Error 1
  ...

More details can also be found at:

  https://sourceware.org/ml/gdb-patches/2018-09/msg00304.html

The most simple fix for this problem is to move 'is_regular_file' to
'filestuff.c', which is not used by IPA.  This ends up making the
files more logically organized as well, since 'is_regular_file' is a
file operation.

No regressions found.

gdb/ChangeLog:
2018-09-12  Sergio Durigan Junior  <sergiodj@redhat.com>

	* common/common-utils.c: Don't include '<sys/stat.h>'.
	(is_regular_file): Move to...
	* common/filestuff.c (is_regular_file): ... here.
	* common/common-utils.h (is_regular_file): Move to...
	* common/filestuff.h (is_regular_file): ... here.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add debug output about skipping files and functions
@ 2018-09-13 16:49 sergiodj+buildbot
  2018-09-13 17:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e68067fb2d59ea93ea95d713a6c27b635332912 ***

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

Add debug output about skipping files and functions

While trying to create skips for libstdc++, I found myself debugging GDB
quite a bit, mostly to find out what the exact function name to match
is.  I thought it would make sense to have this information as debug
output.

This patch adds "set debug skip on|off".

gdb/ChangeLog:

	* skip.c (debug_skip): New variable.
	(skiplist_entry::do_skip_file_p): Add debug output.
	(skiplist_entry::do_skip_gfile_p): Likewise.
	(skiplist_entry::skip_function_p): Likewise.
	(_initialize_step_skip): Create debug command.
	* NEWS: Mention set/show debug skip.

gdb/doc/ChangeLog:

	* gdb.texinfo (Skipping Over Functions and Files): Document
	set/show debug skip.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Testsuite: Add gdb_can_simple_compile
@ 2018-09-13 15:36 sergiodj+buildbot
  2018-09-13 15:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 15:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c221b2f7708017593d572cf90560dc305bc3bf51 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: c221b2f7708017593d572cf90560dc305bc3bf51

Testsuite: Add gdb_can_simple_compile

Simplfy gdb.exp by adding a function that will attempt to
compile a piece of code, then clean up.

gdb/testsuite

	* lib/gdb.exp (gdb_can_simple_compile): Add proc.
	(support_complex_tests): Use gdb_can_simple_compile.
	(is_ilp32_target): Likewise.
	(is_lp64_target): Likewise.
	(is_64_target): Likewise.
	(is_amd64_regs_target): Likewise.
	(is_aarch32_target): Likewise.
	(gdb_int128_helper): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Darwin: set startup-with-shell to off on Sierra and later.
@ 2018-09-13 13:35 sergiodj+buildbot
  2018-09-13 13:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 13:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6be54ef73eacaaf5bf28bafc7dfebc80ebac832 ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: d6be54ef73eacaaf5bf28bafc7dfebc80ebac832

Darwin: set startup-with-shell to off on Sierra and later.

On Mac OS X Sierra and later, the shell is not allowed to be
debug so add a check and disable startup with shell in that
case. This disabling is done temporary before forking
inferior and restored after the fork.

gdb/ChangeLog:

        * darwin-nat.c (should_disable_startup_with_shell):
        New function.
        (darwin_nat_target::create_inferior): Add call.

Change-Id: Ie4d9090f65fdf2e83ecf7a0f9d0647fb1c27cdcc


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Darwin: fix SIGTRAP when debugging
@ 2018-09-13 12:56 sergiodj+buildbot
  2018-09-13 13:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 12:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de1ec836c8cc4eeb68e3e4eb8223eeff9840546e ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: de1ec836c8cc4eeb68e3e4eb8223eeff9840546e

Darwin: fix SIGTRAP when debugging

Debugging a program under Darwin does not work:

(gdb) start
Temporary breakpoint 1 at 0x100000fb4: file /tmp/helloworld.c, line 1.
Starting program: /private/tmp/helloworld
[New Thread 0x2903 of process 60326]
During startup program terminated with signal SIGTRAP, Trace/breakpoint
trap.

Field signaled from darwin_thread_info is not initialized thus signal
sent to the debuggee is considered as not sent by GDB whereas it should.

This patch fixes this problem and also updates (change type and/or
initialize) other fields in the same structure at the same time.

gdb/ChangeLog:

        * darwin-nat.h (struct darwin_thread_info) <gdb_port,
	inf_port, msg_state>: Initialize.
        (struct darwin_thread_info) <signaled, single_step>: Change
        type and initialize.
        (struct darwin_thread_info) <event>: Initialize.

Change-Id: I0fe2a6985df9d0dfcc8a2a258a3ef70cfa19b403


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [testsuite] Fix dg-extract-results.sh path
@ 2018-09-13 12:17 sergiodj+buildbot
  2018-09-13 12:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13 12:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f1107b59311300cb44379022f19af42db98b1e4 ***

Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: master
Commit: 6f1107b59311300cb44379022f19af42db98b1e4

[testsuite] Fix dg-extract-results.sh path

There was a typo in patch:
commit 5a6996172e6294ea37054b1a9caa3a923a8fe399
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Mon Aug 6 16:05:16 2018 +0200
    Update dg-extract-results.* from gcc

gdb/testsuite/ChangeLog
2018-09-11  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* Makefile.in (check-parallel-racy): Fix dg-extract-results.sh path.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB
@ 2018-09-13  0:34 sergiodj+buildbot
  2018-09-13 10:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13  0:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e2fc52e745757a11f7a4a256984cabbe5474f55a ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: e2fc52e745757a11f7a4a256984cabbe5474f55a

Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB

This is a backport of a gnulib fix for the following bug:

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

The problem reported there is about the replacement of 'getcwd' when
cross-compiling GDB.  With our current gnulib copy, the mechanism for
deciding whether to use the system's 'getcwd' or gnulib's version is
too simplistic and pessimistic, so when cross-compiling we always end
up using gnulib's version, which has a limitation: it cannot handle
the situation when the parent directory doesn't have read permissions.

The solution is to backport the following gnulib commit:

  commit a96d2e67052c879b1bcc5bc461722beac75fc372
  Author: Bruno Haible <bruno@clisp.org>
  Date:   Thu Aug 23 21:13:19 2018 +0200

      getcwd: Add cross-compilation guesses.

gdb/ChangeLog:
2018-09-10  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR gdb/23555
	PR gdb/23558
	* gnulib/import/m4/getcwd-path-max.m4: Add cross-compilation
	guesses.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Revert "Update gnulib to current upstream master"
@ 2018-09-13  0:01 sergiodj+buildbot
  2018-09-13  9:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-13  0:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5e8754f90abbbf832987477eea4ee91a9d2f694c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 5e8754f90abbbf832987477eea4ee91a9d2f694c

Revert "Update gnulib to current upstream master"

This reverts commit 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 ("Update
gnulib to current upstream master").  It is needed because the gnulib
update caused problems with people using old GCC compilers (version
4.8, for example), which support C99 but don't default to using it.
Unfortunately this broke GDB for these users.  A more detailed report
of what happened can be found at:

  https://lists.gnu.org/archive/html/bug-gnulib/2018-08/msg00157.html

The reason for updating our gnulib copy was to fix PR gdb/23558.
Reverting this patch reintroduces the bug, so in order to fix it I
will submit a subsequent patch which cherry-picks the fix from gnulib.

gdb/ChangeLog:
2018-09-10  Sergio Durigan Junior  <sergiodj@redhat.com>

	Revert:
	2018-08-29  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR gdb/23555
	PR gdb/23558
	* gnulib/aclocal.m4: Regenerate.
	* gnulib/config.in: Regenerate.
	* gnulib/configure: Regenerate.
	* gnulib/import/Makefile.am: Update.
	* gnulib/import/Makefile.in: Update.
	* gnulib/import/extra/snippet/_Noreturn.h: Rename to...
	* gnulib/import/_Noreturn.h: ... this.
	* gnulib/import/alloca.in.h: Update.
	* gnulib/import/extra/snippet/arg-nonnull.h: Rename to...
	* gnulib/import/arg-nonnull.h: ... this.
	* gnulib/import/assure.h: Update.
	* gnulib/import/at-func.c: Update.
	* gnulib/import/basename-lgpl.c: Update.
	* gnulib/import/extra/snippet/c++defs.h: Rename to...
	* gnulib/import/c++defs.h: ... this.
	* gnulib/import/canonicalize-lgpl.c: Update.
	* gnulib/import/cdefs.h: Update.
	* gnulib/import/chdir-long.c: Update.
	* gnulib/import/chdir-long.h: Update.
	* gnulib/import/cloexec.c: Update.
	* gnulib/import/cloexec.h: Update.
	* gnulib/import/close.c: Update.
	* gnulib/import/closedir.c: Update.
	* gnulib/import/config.charset: Update.
	* gnulib/import/dirent-private.h: Update.
	* gnulib/import/dirent.in.h: Update.
	* gnulib/import/dirfd.c: Update.
	* gnulib/import/dirname-lgpl.c: Update.
	* gnulib/import/dirname.h: Update.
	* gnulib/import/dosname.h: Update.
	* gnulib/import/dup-safer-flag.c: Update.
	* gnulib/import/dup-safer.c: Update.
	* gnulib/import/dup.c: Update.
	* gnulib/import/dup2.c: Update.
	* gnulib/import/errno.in.h: Update.
	* gnulib/import/error.c: Update.
	* gnulib/import/error.h: Update.
	* gnulib/import/exitfail.c: Update.
	* gnulib/import/exitfail.h: Update.
	* gnulib/import/extra/update-copyright: Update.
	* gnulib/import/fchdir.c: Update.
	* gnulib/import/fcntl.c: Update.
	* gnulib/import/fcntl.in.h: Update.
	* gnulib/import/fd-hook.c: Update.
	* gnulib/import/fd-hook.h: Update.
	* gnulib/import/fd-safer-flag.c: Update.
	* gnulib/import/fd-safer.c: Update.
	* gnulib/import/fdopendir.c: Update.
	* gnulib/import/filename.h: Update.
	* gnulib/import/filenamecat-lgpl.c: Update.
	* gnulib/import/filenamecat.h: Update.
	* gnulib/import/flexmember.h: Update.
	* gnulib/import/float+.h: Update.
	* gnulib/import/float.c: Update.
	* gnulib/import/float.in.h: Update.
	* gnulib/import/fnmatch.c: Update.
	* gnulib/import/fnmatch.in.h: Update.
	* gnulib/import/fnmatch_loop.c: Update.
	* gnulib/import/fpucw.h: Update.
	* gnulib/import/frexp.c: Update.
	* gnulib/import/frexpl.c: Update.
	* gnulib/import/fstat.c: Update.
	* gnulib/import/fstatat.c: Update.
	* gnulib/import/getcwd-lgpl.c: Update.
	* gnulib/import/getcwd.c: Update.
	* gnulib/import/getdtablesize.c: Update.
	* gnulib/import/getlogin_r.c: Update.
	* gnulib/import/getprogname.c: Update.
	* gnulib/import/getprogname.h: Update.
	* gnulib/import/gettext.h: Update.
	* gnulib/import/gettimeofday.c: Update.
	* gnulib/import/glob-libc.h: Update.
	* gnulib/import/glob.c: Update.
	* gnulib/import/glob.in.h: Update.
	* gnulib/import/glob_internal.h: Update.
	* gnulib/import/glob_pattern_p.c: Update.
	* gnulib/import/globfree.c: Update.
	* gnulib/import/hard-locale.c: Update.
	* gnulib/import/hard-locale.h: Update.
	* gnulib/import/intprops.h: Update.
	* gnulib/import/inttypes.in.h: Update.
	* gnulib/import/isnan.c: Update.
	* gnulib/import/isnand-nolibm.h: Update.
	* gnulib/import/isnand.c: Update.
	* gnulib/import/isnanl-nolibm.h: Update.
	* gnulib/import/isnanl.c: Update.
	* gnulib/import/itold.c: Update.
	* gnulib/import/libc-config.h: Update.
	* gnulib/import/limits.in.h: Update.
	* gnulib/import/localcharset.c: Update.
	* gnulib/import/localcharset.h: Update.
	* gnulib/import/localtime-buffer.c: Update.
	* gnulib/import/localtime-buffer.h: Update.
	* gnulib/import/lstat.c: Update.
	* gnulib/import/m4/00gnulib.m4: Update.
	* gnulib/import/m4/__inline.m4: Update.
	* gnulib/import/m4/absolute-header.m4: Update.
	* gnulib/import/m4/alloca.m4: Update.
	* gnulib/import/m4/builtin-expect.m4: Update.
	* gnulib/import/m4/canonicalize.m4: Update.
	* gnulib/import/m4/chdir-long.m4: Update.
	* gnulib/import/m4/close.m4: Update.
	* gnulib/import/m4/closedir.m4: Update.
	* gnulib/import/m4/configmake.m4: Update.
	* gnulib/import/m4/d-ino.m4: Update.
	* gnulib/import/m4/d-type.m4: Update.
	* gnulib/import/m4/dirent_h.m4: Update.
	* gnulib/import/m4/dirfd.m4: Update.
	* gnulib/import/m4/dirname.m4: Update.
	* gnulib/import/m4/double-slash-root.m4: Update.
	* gnulib/import/m4/dup.m4: Update.
	* gnulib/import/m4/dup2.m4: Update.
	* gnulib/import/m4/eealloc.m4: Update.
	* gnulib/import/m4/environ.m4: Update.
	* gnulib/import/m4/errno_h.m4: Update.
	* gnulib/import/m4/error.m4: Update.
	* gnulib/import/m4/exponentd.m4: Update.
	* gnulib/import/m4/exponentl.m4: Update.
	* gnulib/import/m4/extensions.m4: Update.
	* gnulib/import/m4/extern-inline.m4: Update.
	* gnulib/import/m4/fchdir.m4: Update.
	* gnulib/import/m4/fcntl-o.m4: Update.
	* gnulib/import/m4/fcntl.m4: Update.
	* gnulib/import/m4/fcntl_h.m4: Update.
	* gnulib/import/m4/fdopendir.m4: Update.
	* gnulib/import/m4/filenamecat.m4: Update.
	* gnulib/import/m4/flexmember.m4: Update.
	* gnulib/import/m4/float_h.m4: Update.
	* gnulib/import/m4/fnmatch.m4: Update.
	* gnulib/import/m4/fnmatch_h.m4: Update.
	* gnulib/import/m4/fpieee.m4: Update.
	* gnulib/import/m4/frexp.m4: Update.
	* gnulib/import/m4/frexpl.m4: Update.
	* gnulib/import/m4/fstat.m4: Update.
	* gnulib/import/m4/fstatat.m4: Update.
	* gnulib/import/m4/getcwd-abort-bug.m4: Update.
	* gnulib/import/m4/getcwd-path-max.m4: Update.
	* gnulib/import/m4/getcwd.m4: Update.
	* gnulib/import/m4/getdtablesize.m4: Update.
	* gnulib/import/m4/getlogin.m4: Update.
	* gnulib/import/m4/getlogin_r.m4: Update.
	* gnulib/import/m4/getpagesize.m4: Update.
	* gnulib/import/m4/getprogname.m4: Update.
	* gnulib/import/m4/gettimeofday.m4: Update.
	* gnulib/import/m4/glibc21.m4: Update.
	* gnulib/import/m4/glob.m4: Update.
	* gnulib/import/m4/glob_h.m4: Update.
	* gnulib/import/m4/gnulib-cache.m4: Update.
	* gnulib/import/m4/gnulib-common.m4: Update.
	* gnulib/import/m4/gnulib-comp.m4: Update.
	* gnulib/import/m4/gnulib-tool.m4: Update.
	* gnulib/import/m4/hard-locale.m4: Update.
	* gnulib/import/m4/include_next.m4: Update.
	* gnulib/import/m4/inttypes-pri.m4: Update.
	* gnulib/import/m4/inttypes.m4: Update.
	* gnulib/import/m4/isnand.m4: Update.
	* gnulib/import/m4/isnanl.m4: Update.
	* gnulib/import/m4/largefile.m4: Update.
	* gnulib/import/m4/limits-h.m4: Update.
	* gnulib/import/m4/localcharset.m4: Update.
	* gnulib/import/m4/locale-fr.m4: Update.
	* gnulib/import/m4/locale-ja.m4: Update.
	* gnulib/import/m4/locale-zh.m4: Update.
	* gnulib/import/m4/localtime-buffer.m4: Update.
	* gnulib/import/m4/longlong.m4: Update.
	* gnulib/import/m4/lstat.m4: Update.
	* gnulib/import/m4/malloc.m4: Update.
	* gnulib/import/m4/malloca.m4: Update.
	* gnulib/import/m4/math_h.m4: Update.
	* gnulib/import/m4/mbrtowc.m4: Update.
	* gnulib/import/m4/mbsinit.m4: Update.
	* gnulib/import/m4/mbsrtowcs.m4: Update.
	* gnulib/import/m4/mbstate_t.m4: Update.
	* gnulib/import/m4/memchr.m4: Update.
	* gnulib/import/m4/memmem.m4: Update.
	* gnulib/import/m4/mempcpy.m4: Update.
	* gnulib/import/m4/memrchr.m4: Update.
	* gnulib/import/m4/mkdir.m4: Update.
	* gnulib/import/m4/mkstemp.m4: Update.
	* gnulib/import/m4/mmap-anon.m4: Update.
	* gnulib/import/m4/mode_t.m4: Update.
	* gnulib/import/m4/msvc-inval.m4: Update.
	* gnulib/import/m4/msvc-nothrow.m4: Update.
	* gnulib/import/m4/multiarch.m4: Update.
	* gnulib/import/m4/nocrash.m4: Update.
	* gnulib/import/m4/off_t.m4: Update.
	* gnulib/import/m4/onceonly.m4: Update.
	* gnulib/import/m4/open-cloexec.m4: Update.
	* gnulib/import/m4/open.m4: Update.
	* gnulib/import/m4/openat.m4: Update.
	* gnulib/import/m4/opendir.m4: Update.
	* gnulib/import/m4/pathmax.m4: Update.
	* gnulib/import/m4/rawmemchr.m4: Update.
	* gnulib/import/m4/readdir.m4: Update.
	* gnulib/import/m4/readlink.m4: Update.
	* gnulib/import/m4/realloc.m4: Update.
	* gnulib/import/m4/rename.m4: Update.
	* gnulib/import/m4/rewinddir.m4: Update.
	* gnulib/import/m4/rmdir.m4: Update.
	* gnulib/import/m4/save-cwd.m4: Update.
	* gnulib/import/m4/secure_getenv.m4: Update.
	* gnulib/import/m4/setenv.m4: Update.
	* gnulib/import/m4/signal_h.m4: Update.
	* gnulib/import/m4/ssize_t.m4: Update.
	* gnulib/import/m4/stat-time.m4: Update.
	* gnulib/import/m4/stat.m4: Update.
	* gnulib/import/m4/std-gnu11.m4: Update.
	* gnulib/import/m4/stdbool.m4: Update.
	* gnulib/import/m4/stddef_h.m4: Update.
	* gnulib/import/m4/stdint.m4: Update.
	* gnulib/import/m4/stdio_h.m4: Update.
	* gnulib/import/m4/stdlib_h.m4: Update.
	* gnulib/import/m4/strchrnul.m4: Update.
	* gnulib/import/m4/strdup.m4: Update.
	* gnulib/import/m4/strerror.m4: Update.
	* gnulib/import/m4/string_h.m4: Update.
	* gnulib/import/m4/strstr.m4: Update.
	* gnulib/import/m4/strtok_r.m4: Update.
	* gnulib/import/m4/sys_socket_h.m4: Update.
	* gnulib/import/m4/sys_stat_h.m4: Update.
	* gnulib/import/m4/sys_time_h.m4: Update.
	* gnulib/import/m4/sys_types_h.m4: Update.
	* gnulib/import/m4/tempname.m4: Update.
	* gnulib/import/m4/time_h.m4: Update.
	* gnulib/import/m4/unistd-safer.m4: Update.
	* gnulib/import/m4/unistd_h.m4: Update.
	* gnulib/import/m4/warn-on-use.m4: Update.
	* gnulib/import/m4/wchar_h.m4: Update.
	* gnulib/import/m4/wchar_t.m4: Update.
	* gnulib/import/m4/wctype_h.m4: Update.
	* gnulib/import/m4/wint_t.m4: Update.
	* gnulib/import/malloc.c: Update.
	* gnulib/import/malloc/scratch_buffer.h: Update.
	* gnulib/import/malloc/scratch_buffer_grow.c: Update.
	* gnulib/import/malloc/scratch_buffer_grow_preserve.c: Update.
	* gnulib/import/malloc/scratch_buffer_set_array_size.c: Update.
	* gnulib/import/malloca.c: Update.
	* gnulib/import/malloca.h: Update.
	* gnulib/import/malloca.valgrind: Update.
	* gnulib/import/math.in.h: Update.
	* gnulib/import/mbrtowc.c: Update.
	* gnulib/import/mbsinit.c: Update.
	* gnulib/import/mbsrtowcs-impl.h: Update.
	* gnulib/import/mbsrtowcs-state.c: Update.
	* gnulib/import/mbsrtowcs.c: Update.
	* gnulib/import/memchr.c: Update.
	* gnulib/import/memmem.c: Update.
	* gnulib/import/mempcpy.c: Update.
	* gnulib/import/memrchr.c: Update.
	* gnulib/import/mkdir.c: Update.
	* gnulib/import/mkstemp.c: Update.
	* gnulib/import/msvc-inval.c: Update.
	* gnulib/import/msvc-inval.h: Update.
	* gnulib/import/msvc-nothrow.c: Update.
	* gnulib/import/msvc-nothrow.h: Update.
	* gnulib/import/open.c: Update.
	* gnulib/import/openat-die.c: Update.
	* gnulib/import/openat-priv.h: Update.
	* gnulib/import/openat-proc.c: Update.
	* gnulib/import/openat.c: Update.
	* gnulib/import/openat.h: Update.
	* gnulib/import/opendir.c: Update.
	* gnulib/import/pathmax.h: Update.
	* gnulib/import/pipe-safer.c: Update.
	* gnulib/import/rawmemchr.c: Update.
	* gnulib/import/readdir.c: Update.
	* gnulib/import/readlink.c: Update.
	* gnulib/import/realloc.c: Update.
	* gnulib/import/ref-add.sin: Update.
	* gnulib/import/ref-del.sin: Update.
	* gnulib/import/rename.c: Update.
	* gnulib/import/rewinddir.c: Update.
	* gnulib/import/rmdir.c: Update.
	* gnulib/import/same-inode.h: Update.
	* gnulib/import/save-cwd.c: Update.
	* gnulib/import/save-cwd.h: Update.
	* gnulib/import/scratch_buffer.h: Update.
	* gnulib/import/secure_getenv.c: Update.
	* gnulib/import/setenv.c: Update.
	* gnulib/import/signal.in.h: Update.
	* gnulib/import/stat-time.c: Update.
	* gnulib/import/stat-time.h: Update.
	* gnulib/import/stat-w32.c: Update.
	* gnulib/import/stat-w32.h: Update.
	* gnulib/import/stat.c: Update.
	* gnulib/import/stdbool.in.h: Update.
	* gnulib/import/stddef.in.h: Update.
	* gnulib/import/stdint.in.h: Update.
	* gnulib/import/stdio.in.h: Update.
	* gnulib/import/stdlib.in.h: Update.
	* gnulib/import/str-two-way.h: Update.
	* gnulib/import/strchrnul.c: Update.
	* gnulib/import/strdup.c: Update.
	* gnulib/import/streq.h: Update.
	* gnulib/import/strerror-override.c: Update.
	* gnulib/import/strerror-override.h: Update.
	* gnulib/import/strerror.c: Update.
	* gnulib/import/string.in.h: Update.
	* gnulib/import/stripslash.c: Update.
	* gnulib/import/strnlen1.c: Update.
	* gnulib/import/strnlen1.h: Update.
	* gnulib/import/strstr.c: Update.
	* gnulib/import/strtok_r.c: Update.
	* gnulib/import/sys_stat.in.h: Update.
	* gnulib/import/sys_time.in.h: Update.
	* gnulib/import/sys_types.in.h: Update.
	* gnulib/import/tempname.c: Update.
	* gnulib/import/tempname.h: Update.
	* gnulib/import/time.in.h: Update.
	* gnulib/import/unistd--.h: Update.
	* gnulib/import/unistd-safer.h: Update.
	* gnulib/import/unistd.in.h: Update.
	* gnulib/import/unsetenv.c: Update.
	* gnulib/import/verify.h: Update.
	* gnulib/import/extra/snippet/warn-on-use.h: Update.
	* gnulib/import/wchar.in.h: Update.
	* gnulib/import/wctype.in.h: Update.
	* gnulib/import/xalloc-oversized.h: Update.
	* gnulib/update-gnulib.sh (GNULIB_COMMIT_SHA1): Set to
	"53e2c179f26a890fa6685af4b6c1397ee370433b".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused variable in record-btrace.c
@ 2018-09-12 19:01 sergiodj+buildbot
  2018-09-13  9:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-12 19:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8ec235834d454a66a89fe16bc62e11497eb79078 ***

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

Remove unused variable in record-btrace.c

old_inferior_ptid is unused, this is caught by a gcc built from git
recently, not sure about previous versions:

/home/emaisin/src/binutils-gdb/gdb/record-btrace.c: In function frame_info* get_thread_current_frame(thread_info*):
/home/emaisin/src/binutils-gdb/gdb/record-btrace.c:1974:10: error: unused variable old_inferior_ptid [-Werror=unused-variable]
1974 |   ptid_t old_inferior_ptid;
     |          ^~~~~~~~~~~~~~~~~

gdb/ChangeLog:

	* record-btrace.c (get_thread_current_frame): Remove
	old_inferior_ptid.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) Fix resolving of homonym components in tagged types
@ 2018-09-12 14:53 sergiodj+buildbot
  2018-09-13  1:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-12 14:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1f5d1570c0eaadbb72d450211f70b24c4c23ac8e ***

Author: Jerome Guitton <guitton@adacore.com>
Branch: master
Commit: 1f5d1570c0eaadbb72d450211f70b24c4c23ac8e

(Ada) Fix resolving of homonym components in tagged types

ada_value_struct_elt is used when displaying a component (say, 'N') of
a record object (say, 'Obj') of type, say, 't1'. Now if Obj is tagged
(Ada parlance: "tagged types" are what other object-oriented languages
call "classes"), then 'N' may not be visible in the current view and
we need to look for it in its actual type. We do that at the same time
as resolving variable-length fields. This would typically be done by
the following call to ada_value_struct_elt, with the last parameter
check_tag set to 1:

      t1 = ada_to_fixed_type (ada_get_base_type (t1), NULL,
                              address, NULL, 1);

This is the general logic, but recently we introduced a special case
to handle homonyms. Different components may have the same name in a
tagged type.  For instance:

       type Top_T is tagged record
          N : Integer := 1;
       end record;

       type Middle_T is new Top.Top_T with record
          N : Character := 'a';
       end record;

Middle_T extends Top_T and both define a (different) component with
the same name ('N'). In such a case, using the actual type of a
Middle_T object would create a confusion, since we would have two
component 'N' in this actual type.

So, to handle homonyms, we convert t1 to the actual type *if
and only if* N cannot be found in the current view. For example, if Obj
has been created as a Middle_T but is seen as a Top_T'Class at our
point of execution, then "print Obj.N" will display the integer field
defined in Top_T's declaration.

Now, even if we find N in the current view, we still have to get a
fixed type: for instance, the record can be unconstrained and we still
need a fixed type to get the proper offset to each field. That is
to say, in this case:

   type Dyn_Top_T (Disc : Natural) is tagged record
      S : Integer_Array (1 .. Disc) := (others => Disc);
      N : Integer := 1;
   end record;

   type Dyn_Middle_T is new Dyn_Top.Dyn_Top_T with record
      N : Character := 'a';
      U : Integer := 42;
   end record;

If we have an object Obj of type Dyn_Middle_T and we want to display
U, we don't need to build, from its tag, a real type with all its real
fields. In other words, we don't need to add the parent components:
Disc, S, and the integer N. We only need to access U and it is
directly visible in Dyn_Middle_T. So no tag handling. However, we do
need to build a fixed-size type to have the proper offset to U (since
this offset to U depends on the size of Obj.S, which itself is dynamic
and depends on the value of Obj.Disc).

We accidentally lost some of this treatment when we introduced the
resolution of homonyms. This patch re-install this part by uncoupling
the tag resolution from the "fixing" of variable-length components.

This change also slightly simplifies the non-tagged case: in the
non-tagged case, no need to set check_tag to 1, since we already know
that there is no tag.

gdb/ChangeLog:

	* ada-lang.c (ada_value_struct_elt): Call ada_to_fixed_type
	with check_tag to 1 if and only if the type is tagged and the
	component being searched cannot been found in the current
	view. Otherwise, always call ada_to_fixed_type with
	check_tag to 0.

gdb/testsuite/ChangeLog:

	* gdb.ada/same_component_name: Add test for case of tagged record
	with variable-length fields.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) Cleanup code by using ada_is_access_to_unconstrained_array call.
@ 2018-09-12 12:16 sergiodj+buildbot
  2018-09-13  1:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-12 12:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d91e9ea81dce83259f2a7f32f43876373f3e7981 ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: d91e9ea81dce83259f2a7f32f43876373f3e7981

(Ada) Cleanup code by using ada_is_access_to_unconstrained_array call.

This patch just avoids code duplication by using a function we
introduced recently (ada_is_access_to_unconstrained_array).

gdb/ChangeLog:

    * ada-lang.c (ada_is_access_to_unconstrained_array): Remove static
    declaration.
    * ada-lang.h: add ada_is_access_to_unconstrained_array prototype.
    * ada-varobj.c (ada_varobj_get_number_of_children,
    ada_varobj_describe_child, ada_value_is_changeable_p): Cleanup code.

Tested on x86_64-linux.
No new testcase provided, as this is just a refactoring.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) Fix printing of access to unconstrained arrays
@ 2018-09-12 12:06 sergiodj+buildbot
  2018-09-13  0:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-12 12:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc330e39bc938cefd4cfc581639177ef4c6bcbe3 ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: cc330e39bc938cefd4cfc581639177ef4c6bcbe3

(Ada) Fix printing of access to unconstrained arrays

Using this Ada code:

    type String_Access is access String;
    type Array_Of_String is array (1 .. 2) of String_Access;
    Aos : Array_Of_String := (new String'("ab"), new String'("cd"));

When debugging with GDB, printing each Aos element displays:

    (gdb) print Aos(1)
    $2 = "ab"
    (gdb) print Aos(2)
    $3 = "cd"

Whereas it should display:

    (gdb) print Aos(1)
    $2 = (foo_r118_024.string_access) 0x635018
    (gdb) print Aos(2)
    $3 = (foo_r118_024.string_access) 0x635038

Notice that printing the entire array works:

(gdb) print Aos
$1 = (0x635018, 0x635038)

The problem was located in ada_value_print function and due to the fact
that the value_type used in this function was based on
value_enclosing_type rather than value_type itself.
In our example, the difference between the value_type and the
value_enclosing_type of the value is that the value_type contains an
additional typedef layer which is not present in the value_enclosing_type.
This typedef layer is GNAT's way to specify that the element is, at the
source level, an access to the unconstrained array, rather than the
unconstrained array.
Moreover, the value_enclosing_type is not really needed in that case and
the value_type can be used instead in this function, and this patch fixes
this.

gdb/ChangeLog:

    * ada-valprint.c (ada_value_print): Use type instead of
    enclosing type.

testsuite/ChangeLog:

    * gdb.ada/access_to_unbounded_array.exp: New testcase.
    * gdb.ada/access_to_unbounded_array/foo.adb: New file.
    * gdb.ada/access_to_unbounded_array/pack.adb: New file.
    * gdb.ada/access_to_unbounded_array/pack.ads: New file.

Tested: x86_64-linux


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) New function ada_is_access_to_unconstrained_array
@ 2018-09-12 11:28 sergiodj+buildbot
  2018-09-12 23:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-12 11:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 736ade86ea3dd3df31120b6c617d64c88bcc86c1 ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: 736ade86ea3dd3df31120b6c617d64c88bcc86c1

(Ada) New function ada_is_access_to_unconstrained_array

Add a new function to check if a given type is an access to an
unconstrained array. This function contains code that is present only
once in the current sources but will be used in a future patch.

gdb/ChangeLog:

        * ada-lang.c (ada_is_access_to_unconstrained_array): New function.
        (ada_check_typedef): Use it.

Tested on x86_64-linux.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix "make install-strip" failure to install gdb-add-index.sh
@ 2018-09-11 12:01 sergiodj+buildbot
  2018-09-11 14:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-11 12:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23c4651c060c123493de004ef61d8ed052d46113 ***

Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: 23c4651c060c123493de004ef61d8ed052d46113

Fix "make install-strip" failure to install gdb-add-index.sh

gdb/ChangeLog:
2018-09-10  Eli Zaretskii  <eliz@gnu.org>

	* Makefile.in (transformed_name): Use INSTALL_SCRIPT instead of
	INSTALL_PROGRAM to install gdb-add-index.sh.  Don't append
	$(EXEEXT) to the script, as it is not a program.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make py-prettyprint.exp test names unique
@ 2018-09-10 17:59 sergiodj+buildbot
  2018-09-11 11:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10 17:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1aac008f1c2f0a239b7ba26efe9d6b68044cddf8 ***

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

Make py-prettyprint.exp test names unique

I noticed that the py-prettyprint.exp test names were not unique.
This patch fixes the problem via with_test_prefix.

gdb/testsuite/ChangeLog
2018-09-08  Tom Tromey  <tom@tromey.com>

	* gdb.python/py-prettyprint.exp: Use with_test_prefix.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allow a pretty-printer without a to_string method
@ 2018-09-10 16:47 sergiodj+buildbot
  2018-09-11 11:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 332cf4c9251a31f0addc2ce2970c9a8bb0c16f96 ***

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

Allow a pretty-printer without a to_string method

PR python/16047 points out that, while the documentation says that the
to_string method is optional for a pretty-printer, the code disagrees
and throws an exception.  This patch fixes the problem.  varobj is
already ok here.

Tested on x86-64 Fedora 26.

gdb/ChangeLog
2018-09-08  Tom Tromey  <tom@tromey.com>

	PR python/16047:
	* python/py-prettyprint.c (pretty_print_one_value): Check for
	to_string method.

gdb/testsuite/ChangeLog
2018-09-08  Tom Tromey  <tom@tromey.com>

	PR python/16047:
	* gdb.python/py-prettyprint.py (pp_int_typedef3): New class.
	(register_pretty_printers): Register new printer.
	* gdb.python/py-prettyprint.exp (run_lang_tests): Add int_type3
	test.
	* gdb.python/py-prettyprint.c (int_type3): New typedef.
	(an_int_type3): New global.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) fix handling of expression with parameterless function call
@ 2018-09-10 10:42 sergiodj+buildbot
  2018-09-11 11:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10 10:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 424da6cf3b30b889ff577b1babd09777148dc0e0 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 424da6cf3b30b889ff577b1babd09777148dc0e0

(Ada) fix handling of expression with parameterless function call

Consider the following function, which takes no parameter and returns
an integer:

    function Something return Integer;

For the purpose of this discussion, our function has been implemented
to always return 124:

    function Something return Integer is
    begin
       return 124;
    end Something;

In Ada, such function can been called without using the parentheses.
For instance, in the statement below, variable My_Value is assigned
the returned value from the call to Something:

    My_Value := Something;

The Ada expression interpeter in GDB supports this case, as we can
see below:

    (gdb) print something
    $1 = 124

However, we get fairly strange results when trying to use this feature
as part of a larger expression. For instance:

    (gdb) print something + 1
    $2 = 248

The problem occurs while doing the resolution pass of the expression.
After prefixying the expression, we obtain the following expression:

    0  BINOP_ADD
    1    OP_VAR_VALUE          Block @0x2021550, symbol @0x20213a0 (pck.something)
    5    OP_LONG               Type @0x1e3c170 (int), value 1 (0x1)

The resolution pass is then expected to remove the OP_VAR_VALUE
entry, and replace it with an OP_FUNCALL. This is what the call
to replace_operator_with_call in ada-lang.c::resolve_subexp is
expected to do:

      if (deprocedure_p
          && (TYPE_CODE (SYMBOL_TYPE (exp->elts[pc + 2].symbol))
              == TYPE_CODE_FUNC))
        {
          replace_operator_with_call (expp, pc, 0, 0,
                                      exp->elts[pc + 2].symbol,
                                      exp->elts[pc + 1].block);
          exp = expp->get ();
        }

The problem is that we're passing OPLEN (zero -- 4th parameter in
the call), and so replace_operator_with_call ends up removing zero
element from our expression, and inserting the corresponding OP_FUNCALL
instead. As a result, instead of having the OP_LONG (1) as the second
argument of the BINOP_ADD, it is now the OP_VAR_VALUE that we were
meant to replace. That OP_VAR_VALUE then itself gets transformed into
an OP_FUNCALL, with the same issue, and eventually, the resolved
expression now looks like this:

     0  BINOP_ADD
     1    OP_FUNCALL            Number of args: 0
     4      OP_VAR_VALUE          Block @0x2021550, symbol @0x20213a0 (pck.something)
     8    OP_FUNCALL            Number of args: 0
    11      OP_VAR_VALUE          Block @0x2021550, symbol @0x20213a0 (pck.something)
    15  OP_VAR_VALUE          Block @0x2021550, symbol @0x20213a0 (pck.something)
    19  OP_LONG               Type @0x1e3c170 (int), value 1 (0x1)

This explains why we get twice the result of the function call
instead of its value plus one. The extra entries in the expression
at the end are just ignored.

This patch fixes the issue by calling replace_operator_with_call
with the correct OPLEN equal to the size of an OP_VAR_VALUE (4).

gdb/ChangeLog:

        * ada-lang.c (resolve_subexp): Pass correct OPLEN in call to
        replace_operator_with_call.

gdb/testsuite/ChangeLog:

        * gdb.ada/expr_with_funcall: New testcase.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ada-lang.c::ada_value_cast: remove unnecessary parentheses
@ 2018-09-10  9:19 sergiodj+buildbot
  2018-09-11 11:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10  9:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95f39a5b2755e5aaaceb6248e585f8a593542331 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 95f39a5b2755e5aaaceb6248e585f8a593542331

ada-lang.c::ada_value_cast: remove unnecessary parentheses

No other code change.

gdb/ChangeLog:

        * ada-lang.c (ada_value_cast): Remove unnecessary parentheses.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) slightly incorrect bounds for type of array indexed by enum
@ 2018-09-10  9:00 sergiodj+buildbot
  2018-09-11 11:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10  9:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16b9eb7bfa56f060d183aa44165bf75cb3c414d8 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 16b9eb7bfa56f060d183aa44165bf75cb3c414d8

(Ada) slightly incorrect bounds for type of array indexed by enum

Consider the following code:

   type Enumerated is (Enum_A, Enum_B, Enum_C, Enum_Last);
   type Table is array (Enumerated) of Integer;
   --  Declare a variable of type Table to make sure the compiler
   --  does emit the debugging information for that type.
   V : Table := (others => 1);

Trying to print the type description of type Table, or of variable V
yields:

    (gdb) ptype v
    type = array (0 .. 3) of integer
    (gdb) ptype example.table
    type = array (0 .. 3) of integer

The compiler generates an XA type for the bounds...

 <1><cf6>: Abbrev Number: 13 (DW_TAG_structure_type)
    <cf7>   DW_AT_name        : example__table___XA

... whose member is described as being as:

 <2><cfe>: Abbrev Number: 14 (DW_TAG_member)
    <cff>   DW_AT_name        : example__enumerated
    <d05>   DW_AT_type        : <0xc69>

This leads us to DIE 0xc69, which is our enumeration type:

 <2><c69>: Abbrev Number: 4 (DW_TAG_enumeration_type)
    <c6a>   DW_AT_name        : example__enumerated

Normally, for arrays, we expect a range type, rather than an enumerated
type. However, for a situation like this, where the range of the array
index is the full enumeration type, it seems like a waste to require
an extra range layer.

Instead, looking at print_range, we see that we print the bounds
of our range using the target type:

       target_type = TYPE_TARGET_TYPE (type);
       if (target_type == NULL)
         target_type = type;
       [...]
       ada_print_scalar (target_type, lo, stream);
       fprintf_filtered (stream, " .. ");
       ada_print_scalar (target_type, hi, stream);

In this case, this causes us to use the enumerated type's subtype,
which is a plain integer type, hence the output we get. However,
there is no reason for using the target type, even in the TYPE_CODE_RANGE
situation. So this patch fixes the issue by simply printing the bounds
using the type being given, instead of its target type.

gdb/ChangeLog:

        * ada-typeprint.c (print_range): Print the bounds using TYPE
        rather than its TYPE_TARGET_TYPE.

A new test for this isn't necessary, as existing tests will demonstrate
this issue once a change in the compiler triggering the generation of
this type of debugging info gets pushed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] minor reformatting in ada-lang.c::ada_to_fixed_value
@ 2018-09-10  7:38 sergiodj+buildbot
  2018-09-11  7:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10  7:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8ce91275e421dfe57aa4e79bb9a58824c155e96 ***

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

minor reformatting in ada-lang.c::ada_to_fixed_value

The arguments in the call to ada_to_fixed_value_create where
improperly aligned. But I also noticed that all the arguments
do fit on a single-line (up to 79 characters). So this patch
just fixes the code by putting everything on that same line.

gdb/ChangeLog:

        * ada-lang.c (ada_to_fixed_value): Minor reformatting in
        call to ada_to_fixed_value_create.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Handle PPC64 function descriptor in Ada decoding
@ 2018-09-10  7:19 sergiodj+buildbot
  2018-09-11  4:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10  7:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d81f350ec01630ef7cd9ae4385a1dc504c54d73 ***

Author: Jerome Guitton <guitton@adacore.com>
Branch: master
Commit: 0d81f350ec01630ef7cd9ae4385a1dc504c54d73

Handle PPC64 function descriptor in Ada decoding

On PPC64, the entry point of the function "FN" is ".FN" when a function
descriptor is used. One of the consequences of this is that GDB then
presents the name of the function to the user (eg: in backtraces) with
the leading dot, which is a low-level internal detail that the user
should not be seeing.  The Ada decoding should strip it.

gdb/ChangeLog:

	* ada-lang.c (ada_decode): strip dot prefix in symbol name.

No testcase added, as a number of existing testcases should already
demonstrate that problem.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) infinite loop when hitting unhandled exception catchpoint
@ 2018-09-10  3:54 sergiodj+buildbot
  2018-09-11  4:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10  3:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb44b1a737ee7d53d5d88c4f2a3d449e8084d6c2 ***

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

(Ada) infinite loop when hitting unhandled exception catchpoint

When debugging a program compiled with an older version of GNAT,
hitting a catchpoint on unhandled exceptions can caused GDB to
got into an infinite loop. This happens while trying to find
the name of the exception that was raised. For that, it searches
for a frame corresponding to a specific function we know gets
called during the exeption handling.

In our particular case, the compiler was too old, and so GDB never
found that frame, and eventually got past the "main" subprogram,
all the way to system frames, where no symbol was available.
As a result, the code addresses could not be resolved into
a function name, leading to the infinite loop because of
a misplaced update of our loop variable "fi":

    while (fi != NULL)
      {
        char *func_name;
        enum language func_lang;

        find_frame_funname (fi, &func_name, &func_lang, NULL);
        if (func_name != NULL)
          {
            make_cleanup (xfree, func_name);

            if (strcmp (func_name,
                        data->exception_info->catch_exception_sym) == 0)
              break; /* We found the frame we were looking for...  */
            fi = get_prev_frame (fi);
          }
      }

If FUNC_NAME is NULL, then FI never gets updated ever after!

gdb/ChangeLog:

        * ada-lang.c (ada_unhandled_exception_name_addr_from_raise):
        Move update of loop variable "fi".

No testcase added, as the existing testcase gdb.ada/catch_ex.exp
should trigger it when using an older version of GNAT as the Ada
compiler.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (Ada) assigning packed array aggregate with variable as component
@ 2018-09-10  0:24 sergiodj+buildbot
  2018-09-11  2:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-10  0:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2a62dfa93f1980fd8d5b0651753c550942fa30b6 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 2a62dfa93f1980fd8d5b0651753c550942fa30b6

(Ada) assigning packed array aggregate with variable as component

Consider a variable "PRA" defined as a packed array of packed
records as follow:

   subtype Int is Integer range 0 .. 7;
   type Packed_Rec is record
      X, Y : Int;
      W    : Integer;
   end record;
   pragma Pack (Packed_Rec);
   type Packed_RecArr is array (Integer range <>) of Packed_Rec;
   pragma Pack (Packed_RecArr);

   PRA : Packed_RecArr (1 .. 3);

Consider also a variable "PR", which is a Packed_Rec record,
declared as follow:

   PR : Packed_Rec := (2, 2, 2);

Trying to assign a new value to PRA using an aggregate expression
where one of the components is our variable PR yields the wrong
result on big-endian machines (e.g. on ppc-linux):

    (gdb) p pra := (pr, (2,2,2), (2,2,2))
    $6 = ((x => 1, y => 0, w => 8), [...]

On the other hand, replacing "pr" by "(2,2,2)" does work.

I tracked the issue down to the bit offset we use to extract
the value of "PR" and copy it inside PRA. in value_assign_to_component,
we have:

  if (gdbarch_bits_big_endian (get_type_arch (value_type (container))))
    move_bits ([target buffer], [bit offset in target buffer],
               [source buffer where PR is stored],
               TYPE_LENGTH (value_type (component)) * TARGET_CHAR_BIT - bits,
               bits, 1);

The issue is with the third-to-last argument, which provides the bit
offset where the value of PR is stored relative to its start address,
and therefore the bit offset relative to the start of the source
buffer passed as the previous argument.

In our case, component is a 38bit packed record whose TYPE_LENGTH
is 5 bytes, so the bit-offset that gets calculated is 2 (bits).
However, that formula only really applies to scalars, whereas
in our case, we have a record (struct). The offset in the non-scalar
case should be zero.

gdb/ChangeLog:

        * ada-lang.c (value_assign_to_component): In the case of
        big-endian targets, extract the bits of the given VAL
        using an src_offset of zero if container is not a scalar.

gdb/testsuite/ChangeLog:

        * gdb.ada/packed_array_assign: New testcase.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Make disassebler work for --enable-targets=all config.
@ 2018-09-09  7:50 sergiodj+buildbot
  2018-09-11  1:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-09  7:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9da4dfd6816fa2198bd80fd6a7b12fef4d6c8361 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 9da4dfd6816fa2198bd80fd6a7b12fef4d6c8361

S12Z: Make disassebler work for --enable-targets=all config.

    opcodes/
    * disassemble.c (ARCH_s12z): Define if ARCH_all.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/testsuite: Make test names unique in gdb.base/watchpoint.exp
@ 2018-09-09  4:35 sergiodj+buildbot
  2018-09-11  1:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-09  4:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 96b6697fd807428f3832bdab1527ad55156e88d7 ***

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

gdb/testsuite: Make test names unique in gdb.base/watchpoint.exp

Extend test names and add test name prefixes to make test names
unique.

gdb/testsuite/ChangeLog:

	* gdb.base/watchpoint.exp (test_complex_watchpoint): Extend test
	names, and add test prefixes to make test names unique.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] compile: Remove non-const reference parameters
@ 2018-09-08 22:13 sergiodj+buildbot
  2018-09-11  1:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-08 22:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d82b3862f1218134f5301ed990c6db48fcb82b2f ***

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

compile: Remove non-const reference parameters

As mentioned here:

  https://sourceware.org/gdb/wiki/Internals%20GDB-C-Coding-Standards#Avoid_non-const_reference_parameters.2C_use_pointers_instead

we prefer to avoid non-const references.  This patch changes the
non-const references I could find in the compile/ directory, either by
making them rvalue-reference (&&) or changing them to pointers.

I'd say all the changes are pretty obvious, except the one in
compile_cplus_instance::enter_scope which might require more attention.

gdb/ChangeLog:

	* compile/compile-c.h (generate_c_for_variable_locations):
	Change reference to pointer.
	* compile/compile-c-support.c (compile_program) <compute>:
	Likewise.
	* compile/compile-c-symbols.c (generate_vla_size): Likewise.
	(generate_c_for_for_one_variable): Likewise
	(generate_c_for_variable_locations): Likewise
	* compile/compile-c-types.c (compile_c_instance::convert_type):
	Likewise
	* compile/compile-cplus-symbols.c (convert_one_symbol):
	std::move the scope passed to enter_scope.
	* compile/compile-cplus-types.c
	(compile_cplus_instance::enter_scope): Make parameter
	rvalue-reference.
	(compile_cplus_instance::new_scope): Change reference to
	pointer.
	(compile_cplus_instance::convert_type): Likewise
	(compile_cplus_convert_typedef): std::move the scope passed to
	enter_scope.
	(compile_cplus_convert_struct_or_union): Likewise.
	(compile_cplus_convert_enum): Likewise.
	(compile_cplus_convert_namespace): Likewise.
	* compile/compile-cplus.h (compile_cplus_instance)
	<enter_scope>: Make parameter rvalue-reference.
	* compile/compile-internal.h (compile_instance)
	<get_cached_type>: Likewise
	* compile/compile-loc2c.c (push): Likewise
	(pushf): Likewise
	(unary): Likewise
	(binary): Likewise
	(print_label): Likewise
	(pushf_register_address): Likewise
	(pushf_register): Likewise
	(do_compile_dwarf_expr_to_c): Likewise
	(compile_dwarf_expr_to_c): Likewise
	(compile_dwarf_bounds_to_c): Likewise
	* compile/compile.c (compile_instance::get_cached_type):
	Likewise
	* compile/compile.h (compile_dwarf_expr_to_c): Likewise.
	(compile_dwarf_bounds_to_c): Likewise
	* dwarf2loc.c (locexpr_generate_c_location): Likewise.
	(dwarf2_compile_property_to_c): Likewise
	* dwarf2loc.h (dwarf2_compile_property_to_c): Likewise
	* symtab.h (struct symbol_computed_ops) <generate_c_location>:
	Likewise


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused tui_win_element::highlight
@ 2018-09-08 22:11 sergiodj+buildbot
  2018-09-11  1:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-08 22:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc5a5ae5b7ea576bb8bf4bbebeaa70366851eacd ***

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

Remove unused tui_win_element::highlight

gdb/ChangeLog:

	* tui/tui-data.h (struct tui_win_element) <highlight>: Remove.
	* tui/tui-data.c (init_content_element): Don't initialize it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused tui_win_info::detail::opaque
@ 2018-09-08 17:19 sergiodj+buildbot
  2018-09-11  1:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-08 17:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 137be54029ed2d2fc95120bba2af88311e5a198a ***

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

Remove unused tui_win_info::detail::opaque

gdb/ChangeLog:

	* tui/tui-data.h (struct tui_win_info)
	<detail::opaque>: Remove.
	* tui/tui-data.c (init_win_info): Remove assignment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make -Wformat-nonliteral work with gcc
@ 2018-09-08  8:49 sergiodj+buildbot
  2018-09-11  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-08  8:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f1628857d783fee0171f16f1bad0b7816460dec5 ***

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

Make -Wformat-nonliteral work with gcc

After looking into why the build failed for Simon but not for me, we
found that the underlying cause was due to how gcc treats
-Wformat-nonliteral.  gcc requires -Wformat to be given first; but
warning.m4 was not doing this, so -Wformat-nonliteral was not being
used.

This patch changes warning.m4 to account gcc's requirement.

This then showed that the target-float.c build change in the earlier
Makefile patch was also incorrect.  Simon didn't see this in his
build, but gcc now points it out.  So, this patch fixes this problem
as well.

2018-09-05  Tom Tromey  <tom@tromey.com>

	* warning.m4 (AM_GDB_WARNINGS): Add -Wformat when testing
	-Wformat-nonliteral.
	* target-float.c (host_float_ops<T>::to_string)
	(host_float_ops<T>::from_string): Use
	DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL.
	* configure: Rebuild.

gdb/gdbserver/ChangeLog
2018-09-05  Tom Tromey  <tom@tromey.com>

	* configure: Rebuild.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Disable -Wformat-nonliteral in parts of printcmd.c
@ 2018-09-08  8:41 sergiodj+buildbot
  2018-09-10 23:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-08  8:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT af39b1c216ffb11e6ca8e8607b00749e0fc1ab41 ***

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

Disable -Wformat-nonliteral in parts of printcmd.c

commit 3322c5d9a1 ("Remove unneeded explicit .o targets") broke the
build with clang, because -Wno-format-nonliteral was in fact needed.
This patch fixes the problem by introducing
DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL and using it in printcmd.c.  This
seems preferable to reverting the patch because now the warning
suppression is more targeted.

gdb/ChangeLog
2018-09-05  Simon Marchi  <simon.marchi@ericsson.com>

	* printcmd.c (printf_c_string): Use
	DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL.
	(printf_wide_c_string, printf_pointer, ui_printf): Likewise.

include/ChangeLog
2018-09-05  Simon Marchi  <simon.marchi@ericsson.com>

	* diagnostics.h (DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL): New macro.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unnecessary casts from cli-cmds.c
@ 2018-09-07 15:23 sergiodj+buildbot
  2018-09-10 23:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-07 15:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 081bca4d622143b229cf02a1dda4afb9b457eefa ***

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

Remove unnecessary casts from cli-cmds.c

I noticed a couple of unnecessary casts in cli-cmds.c.  This patch
removes them.

Tested by rebuilding.  I'm checking this in.

gdb/ChangeLog
2018-09-05  Tom Tromey  <tom@tromey.com>

	* cli/cli-cmds.c (shell_escape, edit_command): Remove cast.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/exp] Handle DW_OP_GNU_variable_value refs to abstract dies
@ 2018-09-07  3:16 sergiodj+buildbot
  2018-09-10 23:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-07  3:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4a62c65fa8fe6a48b6ff564f45c1ac535f10f14 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: e4a62c65fa8fe6a48b6ff564f45c1ac535f10f14

[gdb/exp] Handle DW_OP_GNU_variable_value refs to abstract dies

Consider a vla variable 'a' in function f1:
...
 <2><1a7>: Abbrev Number: 11 (DW_TAG_variable)
    <1a8>   DW_AT_description : a
    <1aa>   DW_AT_abstract_origin: <0x311>
...
with abstract origin 'a':
...
 <2><311>: Abbrev Number: 3 (DW_TAG_variable)
    <312>   DW_AT_name        : a
    <317>   DW_AT_type        : <0x325>
...
and inherited abstract vla type:
...
 <1><325>: Abbrev Number: 9 (DW_TAG_array_type)
    <326>   DW_AT_type        : <0x33a>
 <2><32e>: Abbrev Number: 10 (DW_TAG_subrange_type)
    <32f>   DW_AT_type        : <0x2ea>
    <333>   DW_AT_upper_bound : 5 byte block: fd 1b 3 0 0
                                (DW_OP_GNU_variable_value: <0x31b>)
...
where the upper bound refers to this artificial variable D.1922 without location
attribute:
...
 <2><31b>: Abbrev Number: 8 (DW_TAG_variable)
    <31c>   DW_AT_description : (indirect string, offset: 0x39a): D.1922
    <320>   DW_AT_type        : <0x2ea>
    <324>   DW_AT_artificial  : 1
...

Currently, when we execute "p sizeof (a)" in f1, the upper bound is calculated
by evaluating the DW_OP_GNU_variable_value expression referring to D.1922, but
since that die doesn't have a location attribute, we get:
...
value has been optimized out
...

However, there's also artificial variable D.4283 that is sibling of vla
variable 'a', has artificial variable D.1922 as abstract origin, and has a
location attribute:
...
 <2><1ae>: Abbrev Number: 12 (DW_TAG_variable)
    <1af>   DW_AT_description : (indirect string, offset: 0x1f8): D.4283
    <1b3>   DW_AT_abstract_origin: <0x31b>
    <1b7>   DW_AT_location    : 11 byte block: 75 1 8 20 24 8 20 26 31 1c 9f
                                (DW_OP_breg5 (rdi):1; DW_OP_const1u: 32;
				 DW_OP_shl; DW_OP_const1u: 32; DW_OP_shra;
				 DW_OP_lit1; DW_OP_minus; DW_OP_stack_value)
...

The intended behaviour for DW_OP_GNU_variable_value is to find a die that
refers to D.1922 as abstract origin, has a location attribute and is
'in scope', so the expected behaviour is:
...
$1 = 6
...

The 'in scope' concept can be thought of as variable D.1922 having name
attribute "D.1922", and variable D.4283 inheriting that attribute, resulting
in D.4283 being declared with name "D.1922" alongside vla a in f1, and when we
lookup "DW_OP_GNU_variable_value D.1922", it should work as if we try to find
the value of a variable named "D.1922" on the gdb command line using
"p D.1922", and we should return the value of D.4283.

This patch fixes the case described above, by:
- adding a field abstract_to_concrete to struct dwarf2_per_objfile,
- using that field to keep track of which concrete dies are instances of an
  abstract die, and
- using that information when getting the value DW_OP_GNU_variable_value.

Build and reg-tested on x86_64-linux.

2018-09-05  Tom de Vries  <tdevries@suse.de>

	* dwarf2loc.c (sect_variable_value): Call indirect_synthetic_pointer
	with resolve_abstract_p == true.
	(indirect_synthetic_pointer): Add resolve_abstract_p parameter,
	defaulting to false. Propagate resolve_abstract_p to
	dwarf2_fetch_die_loc_sect_off.
	* dwarf2loc.h (dwarf2_fetch_die_loc_sect_off): Add resolve_abstract_p
	parameter, defaulting to false.
	* dwarf2read.c (read_variable): Add variable to abstract_to_concrete.
	(dwarf2_fetch_die_loc_sect_off): Add and handle resolve_abstract_p
	parameter.
	* dwarf2read.h (struct die_info): Forward-declare.
	(die_info_ptr): New typedef.
	(struct dwarf2_per_objfile): Add abstract_to_concrete field.

	* gdb.dwarf2/varval.exp: Add test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] bfd, sparc: avoid duplicated error messages on invalid relocations.
@ 2018-09-06  3:54 sergiodj+buildbot
  2018-09-10 23:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-06  3:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e920c014ecd9fbb630c76576d2771aa4631d93f7 ***

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

bfd, sparc: avoid duplicated error messages on invalid relocations.

This patch avoids a duplicated error message when an invalid
relocation number is read from an object file in sparc-* ELF targets:

$ strip -g test.o
strip: test.o: unsupported relocation type 0xd7
strip: test.o: unsupported relocation type 0xd7
strip: test.o: bad value

Tested in x86_64-linux-gnu, sparc64-linux-gnu and sparc-linux-gnu
targets.

bfd/ChangeLog:

2018-09-04  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* elfxx-sparc.c (_bfd_sparc_elf_info_to_howto): Do not issue an
	error when an invalid relocation is passed;  this is already done
	by `_bfd_sparc_elf_info_to_howto_ptr'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] bfd, sparc: issue an error when reading relocations with invalid symbol references.
@ 2018-09-06  3:53 sergiodj+buildbot
  2018-09-10 23:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-06  3:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8410d65b77164d020a45cc9aa17a0147dc76862d ***

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

bfd, sparc: issue an error when reading relocations with invalid symbol references.

The function `elf64_sparc_slurp_one_reloc_table' in elf64-sparc.c
currently checks that the symbol indexes read in the r_sym fields of
relocations are in range.  This is done for both dynamic and
non-dynamic symbols.  This avoids subsequent invalid memory accesses.
However, no error is issued to the user.

This patch makes BFD to issue an error when the read symbol index is
out of range, following the same behavior implemented in both the
generic ELF routines and other ELF backends (such as mips64).

Tested in x86_64-linux-gnu, sparc64-linux-gnu, and
--enable-targets=all.

2018-09-04  Jose E. Marchesi  <jose.marchesi@oracle.com>

            * elf64-sparc.c (elf64_sparc_slurp_one_reloc_table): Issue an
            error when an invalid symbol index is retrieved in ELF64_R_SYM of
            a relocation seen in an input file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Automatically update "aclocal_m4_deps" when updating gnulib
@ 2018-09-05 22:50 sergiodj+buildbot
  2018-09-10 20:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-05 22:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fcc9b044b7f563023633a9964810e76f4cde40d4 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fcc9b044b7f563023633a9964810e76f4cde40d4

Automatically update "aclocal_m4_deps" when updating gnulib

When we update gnulib using our "update-gnulib.sh" tool, it doesn't
automatically update the list of M4 files present at
gnulib/Makefile.in:aclocal_m4_deps.  This patch extends the tool to do
that.  It also puts "aclocal_m4_deps" in its own file (a Makefile
fragment), so that it's easier to update it programatically.

Tested by generating the file and diff'ing the results against the
current version of "aclocal_m4_deps".

gdb/ChangeLog:
2018-09-04  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gnulib/Makefile.in (aclocal_m4_deps): Move to
	"aclocal-m4-deps.mk".  Include file here.
	$(srcdir)/aclocal.m4: Add "configure.ac".
	* gnulib/aclocal-m4-deps.mk: New file.
	* gnulib/update-gnulib.sh: Automatically update
	"aclocal-m4-deps.mk".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Simplify ada-exp.o rule
@ 2018-09-05 15:32 sergiodj+buildbot
  2018-09-10 18:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-05 15:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8dc9fd87b0965f24e21922f295c4af9c3f624985 ***

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

Simplify ada-exp.o rule

The ada-exp.o rule no longer needs to pass -Wno-old-style-definition
to the compiler, as this option has no meaning in C++.  So, This patch
simplifies the explicit ada-exp.o rule in the Makefile.  The rule is
still needed because, according to the comment, ada-exp.c may appear
in the srcdir.

gdb/ChangeLog
2018-09-04  Tom Tromey  <tom@tromey.com>

	* Makefile.in (GDB_WARN_CFLAGS_NO_DEFS): Remove.
	(ada-exp.o): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove obsolete comments from Makefiles
@ 2018-09-05 12:05 sergiodj+buildbot
  2018-09-10 16:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-05 12:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba2bf2aaba97866f4c9c67239666916caa7bb150 ***

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

Remove obsolete comments from Makefiles

This removes an obsolete comment from Makefile.in.  This was copied
into gnulib/Makefile.in, so this removes that comment as well.

gdb/ChangeLog
2018-09-04  Tom Tromey  <tom@tromey.com>

	* gnulib/Makefile.in: Remove obsolete comment.
	* Makefile.in: Remove obsolete comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix batch exit status test failure on Fedora 28
@ 2018-09-05  9:57 sergiodj+buildbot
  2018-09-10 16:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-05  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd083ee23d23903e8bc595b64aa8ea62379491cd ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: dd083ee23d23903e8bc595b64aa8ea62379491cd

Fix batch exit status test failure on Fedora 28

This commit adds calls to remote_close and clear_gdb_spawn_id to
gdb.base/batch-exit-status.exp, fixing failures reported by buildbot
on Fedora 28 where gdb_spawn_id not being reset by the previous test
caused default_gdb_spawn to return without spawning.

This commit also changes the test to use detect GDB's exit using
gdb_test_multiple expecting 'eof', rather than using 'wait -i' alone.
This means the testcase won't hang forever on failure as fixed in
gdb.base/quit.exp by commit 15763a09d4ae ("Fix 'gdb.base/quit.exp
hangs forever' if the test fails").

gdb/testsuite/ChangeLog:

	* gdb.base/batch-exit-status.exp: Use gdb_test_multiple and expect
	'eof' before 'wait -i'.  Use remote_close and clear_gdb_spawn_id.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Fix an ARI warning
@ 2018-09-05  9:07 sergiodj+buildbot
  2018-09-10 16:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-05  9:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6c9d681b07e32d07f7ca0774360be62bbf065b82 ***

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

gdb/riscv: Fix an ARI warning

This patch fixes an ARI violation in riscv-tdep.c (line ends with
'+').

gdb/ChangeLog:

	* riscv-tdep.c (riscv_frame_cache): Fix ARI warning, don't end a
	line with '+'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Provide non-DWARF stack unwinder
@ 2018-09-04 20:01 sergiodj+buildbot
  2018-09-10 15:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-04 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 78a3b0fab8200fdca2b1b934645c29e7bd502d36 ***

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

gdb/riscv: Provide non-DWARF stack unwinder

Collects information during the prologue scan and uses this to unwind
registers when no DWARF information is available.

This patch has been tested by disabling the DWARF stack unwinders, and
running the complete GDB testsuite against a range of RISC-V targets.
The results are comparable to running with the DWARF unwinders in
place.

gdb/ChangeLog:

	* riscv-tdep.c: Add 'prologue-value.h' include.
	(struct riscv_unwind_cache): New struct.
	(riscv_debug_unwinder): New global.
	(riscv_scan_prologue): Update arguments, capture register details
	from prologue scan.
	(riscv_skip_prologue): Reformat arguments line, move end of
	prologue calculation into riscv_scan_prologue.
	(riscv_frame_cache): Update return type, create
	riscv_unwind_cache, scan the prologue, and fill in remaining cache
	details.
	(riscv_frame_this_id): Use frame id computed in riscv_frame_cache.
	(riscv_frame_prev_register): Use the trad_frame within the
	riscv_unwind_cache.
	(_initialize_riscv_tdep): Add 'set/show debug riscv unwinder'
	flag.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Extend the trad-frame API
@ 2018-09-04 19:39 sergiodj+buildbot
  2018-09-10 15:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-04 19:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23e60e7a4ea772eabb6ae4788913e228763755cf ***

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

gdb: Extend the trad-frame API

Adds two new functions to the trad-frame API and update the internals
of trad-frame to use the new functions.  These functions will be used
in later commits.

gdb/ChangeLog:

	* trad-frame.h (trad_frame_set_realreg): Declare.
	(trad_frame_set_addr): Declare.
	* trad-frame.c (trad_frame_set_realreg): Define new function.
	(trad_frame_set_addr): Define new function.
	(trad_frame_set_reg_realreg): Use new function.
	(trad_frame_set_reg_addr): Use new function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23595, simple objcopy of executable failure for msp430-elf
@ 2018-09-04 18:26 sergiodj+buildbot
  2018-09-10  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-04 18:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2542e49e21e6b7270f72c7be0fc4ff1a986371da ***

Author: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Branch: master
Commit: 2542e49e21e6b7270f72c7be0fc4ff1a986371da

PR23595, simple objcopy of executable failure for msp430-elf

VMA of the first section in the segment containing the ELF file header
(and possibly section headers too) can't be used to reliably find the
size of the headers plus padding.  What's really needed is sh_offset
of the first section assuming it has contents (vma does have a
relationship to sh_offset, but is only guaranteed in demand paged
executables).

If the first section is SHT_NOBITS and it hasn't been converted to
have file contents by the existence of a following SHT_PROGBITS
section in the same segment, the sh_offset value also isn't reliable.

	PR 23595
	elf.c (copy_elf_program_header): When first segment contains
	only the headers and SHT_NOBITS sections, use segment p_filesz
	to calculate header and padding size.  Use filepos of the first
	section otherwise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allow an IR object with unknown architecture
@ 2018-09-02  6:57 sergiodj+buildbot
  2018-09-09 23:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-02  6:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b986869b6605e45044626c5b3111390ac4e70b82 ***

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

Allow an IR object with unknown architecture

An IR object may have an unknown architecture.  But it is compatible
with other architecture.

	PR ld/23600
	* archures.c (bfd_arch_get_compatible): Allow an IR object with
	unknown architecture.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Correct the requirement of compressed floating point instructions
@ 2018-09-01  4:41 sergiodj+buildbot
  2018-09-09 22:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-01  4:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be192bc284b329fa0b38646bd3df9a02b880a704 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: be192bc284b329fa0b38646bd3df9a02b880a704

RISC-V: Correct the requirement of compressed floating point instructions

2018-08-31  Kito Cheng  <kito@andestech.com>
gas/
	* testsuite/gas/riscv/c-fld-fsd-fail.d: New.
	* testsuite/gas/riscv/c-fld-fsd-fail.l: Likewise.
	* testsuite/gas/riscv/c-fld-fsd-fail.s: Likewise.
opcodes/
	* riscv-opc.c (riscv_opcodes): Fix incorrect subset info for
	compressed floating point instructions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix a small bug in gdb.rust/simple.rs
@ 2018-09-01  1:47 sergiodj+buildbot
  2018-09-09 10:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-09-01  1:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aef9346c25b0a0c665bce793c00797f5ab82ed37 ***

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

Fix a small bug in gdb.rust/simple.rs

I noticed that gdb.rust/simple.rs had two local variables named "v".
This didn't previous cause problems, but with a newer rust compiler
this resulted in a test failure.  (It should have failed all along, so
I suppose earlier passes were due to a compiler bug.)

This patch renames the second variable.

gdb/testsuite/ChangeLog
2018-08-31  Tom Tromey  <tom@tromey.com>

	* gdb.rust/simple.rs: Rename second variable "v".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Regenerate gdbarch.h
@ 2018-08-31 23:08 sergiodj+buildbot
  2018-09-09  8:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-31 23:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0c8885885ab1d62971bbae22d4b5e335c31b19c9 ***

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

Regenerate gdbarch.h

The previous commit included a stale gdbarch.h from an earlier version
of that patch by mistake.

gdb/ChangeLog:
2018-08-31  Pedro Alves  <palves@redhat.com>

	* gdbarch.h: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add comment describing continuable/steppable/non-steppable watchpoints
@ 2018-08-31 22:25 sergiodj+buildbot
  2018-09-09  7:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-31 22:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ea65f08fa1b8279b65133a958de02fe84767eb9 ***

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

Add comment describing continuable/steppable/non-steppable watchpoints

These weren't described anywhere in the sources.

gdb/ChangeLog:
2018-08-31  Pedro Alves  <palves@redhat.com>

	* gdbarch.sh (have_nonsteppable_watchpoint): Add comment.
	* target.h (Hardware watchpoint interfaces): Describe
	continuable/steppable/non-steppable watchpoints.
	* gdbarch.h, gdbarch.c: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update gnulib/Makefile.in:aclocal_m4_deps
@ 2018-08-31 20:14 sergiodj+buildbot
  2018-09-09  7:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-31 20:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dab999b116b507ad431c70fab0a28074dfea29df ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: dab999b116b507ad431c70fab0a28074dfea29df

Update gnulib/Makefile.in:aclocal_m4_deps

It was pointed by Pedro that gnulib/Makefile.in should be updated
accordingly after our local gnulib is also updated.  The specific part
that needs to be refreshed is the "aclocal_m4_deps" variable, which
lists the .m4 files present under the "gnulib/import/m4/" directory.
This patch does that.

No regressions introduced.

gdb/ChangeLog:
2018-08-31  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gnulib/Makefile.in (aclocal_m4_deps): Update according to
	the files present in "gnulib/import/m4/".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PowerPC64 higher REL16 relocations
@ 2018-08-31 19:39 sergiodj+buildbot
  2018-09-09  7:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-31 19:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9699735b04d4629bd3dc418c265e7f0bc1f9ce ***

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

PowerPC64 higher REL16 relocations

There are occasions where someone might want to build a 64-bit
pc-relative offset from 16-bit pieces.  This adds the necessary REL16
relocs corresponding to existing ADDR16 relocs that can be used to
build 64-bit absolute values.

include/
	* elf/ppc64.h (R_PPC64_REL16_HIGH, R_PPC64_REL16_HIGHA),
	(R_PPC64_REL16_HIGHER, R_PPC64_REL16_HIGHERA),
	(R_PPC64_REL16_HIGHEST, R_PPC64_REL16_HIGHESTA): Define.
	(R_PPC64_LO_DS_OPT, R_PPC64_16DX_HA): Bump value.
bfd/
	* reloc.c (BFD_RELOC_PPC64_REL16_HIGH, BFD_RELOC_PPC64_REL16_HIGHA),
	(BFD_RELOC_PPC64_REL16_HIGHER, BFD_RELOC_PPC64_REL16_HIGHERA),
	(BFD_RELOC_PPC64_REL16_HIGHEST, BFD_RELOC_PPC64_REL16_HIGHESTA):
	Define.
	* elf64-ppc.c (ppc64_elf_howto_raw): Add new REL16 howtos.
	(ppc64_elf_reloc_type_lookup): Translate new REL16 relocs.
	(ppc64_elf_check_relocs, ppc64_elf_relocate_section): Handle them.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
gas/
	* config/tc-ppc.h (TC_FORCE_RELOCATION_SUB_LOCAL): Allow ADDR16
	HIGH, HIGHA, HIGHER, HIGHERA, HIGHEST, and HIGHESTA relocs.
	Group 16-bit relocs.
	* config/tc-ppc.c (md_apply_fix): Translate those ADDR16 relocs
	to REL16 when pcrel.  Sort relocs.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Rearrange ppc_size_one_stub and correct _notoc stub examples
@ 2018-08-31 19:26 sergiodj+buildbot
  2018-09-09  7:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-31 19:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f891966ff66639673a5207b94bd68ec928fb68bc ***

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

Rearrange ppc_size_one_stub and correct _notoc stub examples

This patch rearranges ppc_size_one_stub to make it a little easier to
compare against ppc_build_one_stub, and makes a few other random
changes that might help for future maintenance.  There should be no
functional changes here.

The patch also fixes code examples in comments.  A couple of "ori"
instructions lacked the source register operand, and "@high" is the
correct reloc modifier to use in a sequence building a 64-bit value.
(@hi reports overflow of a 32-bit signed value.)

	* elf64-ppc.c: Correct _notoc stub comments.
	(ppc_build_one_stub): Simplify output of branch for notoc
	long branch stub.  Don't include label offset of 8 bytes in
	"off" calculation for notoc plt stub.  Don't emit insns to get pc.
	(build_offset): Emit insns to get pc here instead.
	(size_offset): Add 4 extra insns.
	(plt_stub_size): Adjust for "off" and size_offset changes.
	(ppc_size_one_stub): Rearrange code into a switch, duplicating
	some to better match ppc_build_one_stub.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Allow instruction require more than one extension
@ 2018-08-31 16:33 sergiodj+buildbot
  2018-09-09  7:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-31 16:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43135d3b15ce10a786704f9bb4736d834d6581a8 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 43135d3b15ce10a786704f9bb4736d834d6581a8

RISC-V: Allow instruction require more than one extension

2018-08-29  Kito Cheng  <kito@andestech.com>

gas/
	* config/tc-riscv.c (riscv_subset_supports): New argument:
	xlen_required.
	(riscv_multi_subset_supports): New function, able to check more
	than one extension.
	(riscv_ip): Use riscv_multi_subset_supports instead of
	riscv_subset_supports.
	(riscv_set_arch): Update call-site for riscv_subset_supports.
	(riscv_after_parse_args): Likewise.

include/
	*opcode/riscv.h (MAX_SUBSET_NUM): New.
	(riscv_opcode): Add xlen_requirement field and change type of
	subset.

opcodes/
	* riscv-dis.c (riscv_disassemble_insn): Check XLEN by
	riscv_opcode.xlen_requirement.
	* riscv-opc.c (riscv_opcodes): Update for struct change.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Extend instruction decode to cover more instructions
@ 2018-08-30 22:32 sergiodj+buildbot
  2018-09-09  7:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30 22:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff3a05b3f87093e5ac2bcd5e510bca4bebf1bef2 ***

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

gdb/riscv: Extend instruction decode to cover more instructions

Extends the instruction decoder used during prologue scan and software
single step to cover more instructions.  These instructions are
encountered when running the current GDB testsuite with the DWARF
stack unwinders turned off.

gdb/ChangeLog:

	* riscv-tdep.c (riscv_insn::decode): Decode c.addi4spn, c.sd,
	c.sw, c.swsp, and c.sdsp.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: remove extra caching of misa register
@ 2018-08-30 21:42 sergiodj+buildbot
  2018-09-09  6:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30 21:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b3f9efc044d2971aa0d9bb39a4c76678bc4ea6d ***

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

gdb/riscv: remove extra caching of misa register

The RISC-V had a mechanism in place to cache the contents of the misa
register per-inferior, the original intention behind this was to
reduce the number of times the misa register had to be read (as the
contents should be constant), but it was pointed out on the mailing
list[1] that the register cache will mean the register is only
accessed once each time GDB stops, and any additional caching is
probably just unneeded extra complexity.

As such, until it can be shown that there's a real need for additional
caching, this commit removes all of the additional caching of the misa
register, and just accesses the misa register like a normal register.

[1] https://sourceware.org/ml/gdb-patches/2018-03/msg00136.html

gdb/ChangeLog:

	* riscv-tdep.c (struct riscv_inferior_data): Delete.
	(riscv_read_misa_reg): Don't cache value read into inferior data.
	(riscv_new_inferior_data): Delete.
	(riscv_inferior_data_cleanup): Delete.
	(riscv_inferior_data): Delete.
	(riscv_invalidate_inferior_data): Delete.
	(_initialize_riscv_tdep): Remove initialisation of inferior data.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Ensure compiler doesn't optimise variable out in test
@ 2018-08-30 21:26 sergiodj+buildbot
  2018-09-09  6:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30 21:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c67f2e1518a829c4ae4f346c316701ef5d56a30f ***

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

gdb: Ensure compiler doesn't optimise variable out in test

In the test gdb.base/funcargs.exp, there's this function:

    void recurse (SVAL a, int depth)
    {
      a.s = a.i = a.l = --depth;
      if (depth == 0)
        hitbottom ();
      else
        recurse (a, depth);
    }

The test script places a breakpoint in hitbottom, and runs the
executable which calls recurse with an initial depth of 4.

When GDB hits the breakpoint in hitbottom the testscript performs a
backtrace, and examines 'a' at each level.

The problem is that 'a' is not live after either the call to
'hitbottom' or the call to 'recurse', and as a result the test fails.

In the particular case I was looking at GCC for RISC-V 32-bit, the
variable 'a' is on the stack and GCC selects the register $ra (the
return address register) to hold the pointer to 'a'.  This is fine,
because, by the time the $ra register is needed to hold a return
address (calling hitbottom or recurse) then 'a' is dead.

In this patch I propose that a use of 'a' is added after the calls to
hitbottom and recurse, this should cause the compiler to keep 'a'
around, which should ensure GDB can find it.

gdb/testsuite/ChangeLog:

	* gdb.base/funcargs.c (use_a): New function.
	(recurse): Call use_a.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix compile-cplus-types.c build errors
@ 2018-08-30 20:30 sergiodj+buildbot
  2018-09-09  5:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a0dc02a6df86011462293cc11b4e35c0f18effd0 ***

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

Fix compile-cplus-types.c build errors

I see these errors when building with clang:

  CXX    compile/compile-cplus-types.o
/home/emaisin/src/binutils-gdb/gdb/compile/compile-cplus-types.c:306:56: error: cannot pass non-trivial object of type 'compile_scope' to variadic function; expected type from format string was 'void *' [-Wnon-pod-varargs]
        fprintf_unfiltered (gdb_stdlog, "leaving scope %p\n", current);
                                                       ~~     ^~~~~~~
/home/emaisin/src/binutils-gdb/gdb/compile/compile-cplus-types.c:1058:13: error: comparison of two values with different enumeration types ('enum_flags<gcc_cp_qualifiers>::enum_type' (aka 'gcc_cp_qualifiers') and 'gcc_cp_ref_qualifiers') [-Werror,-Wenum-compare]
  if (quals != GCC_CP_REF_QUAL_NONE)
      ~~~~~ ^  ~~~~~~~~~~~~~~~~~~~~

Fix the first one by using host_address_to_string.

Fix the second one by comparing to 0 instead.  I think the current
comparison simply uses the wrong enum type.  Comparing to 0 seems like
the right thing to do, because we want to check whether any flags are
specified.

gdb/ChangeLog:

	* compile/compile-cplus-types.c
	(compile_cplus_instance::leave_scope): Take the address of scope
	object.
	(compile_cplus_instance::convert_qualified_base): Compare quals
	to 0.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add new search_symbols_multiple API
@ 2018-08-30  1:51 sergiodj+buildbot
  2018-09-09  4:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30  1:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fcaad03cc027ec2cdf7f2cff70d792867d43c57f ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: fcaad03cc027ec2cdf7f2cff70d792867d43c57f

Add new search_symbols_multiple API

This patch adds a new symbol searching API based on linespec.c's parser
implementation.  This allows users to find "all* matching symbols instead
of the first found match (a la lookup_symbol).

gdb/ChangeLog:

	* linespec.c (collect_info::add_symbol): Make virtual.
	(struct symbol_searcher_collect_info): New struct.
	(symbol_searcher::find_all_symbols): New method.
	* symtab.h (class symbol_searcher): New class.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use block_symbol in linespec APIs
@ 2018-08-30  1:27 sergiodj+buildbot
  2018-09-09  3:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30  1:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e41c8db84bc6f74843dda40ae443d41977c0d20 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 7e41c8db84bc6f74843dda40ae443d41977c0d20

Use block_symbol in linespec APIs

This patch changes the linespec.c APIs to use block_symbol instead of just
a symbol.  lookup_symbol et al already return block_symbol's.

gdb/ChangeLog:

	* linespec.c (struct linespec) <function_symbols, label_symbols>:
	Change to vector of block_symbol.  Update all users.
	(struct collect_info) <symbols>: Likewise.
	(collect_info::add_symbol): Take block_symbol as argument.
	Update all callers.
	(decode_compound_collector) <m_symbols>: Change type to vector
	of block_symbol.  Update all users.
	(decode_compound_collector::operator ()): Change parameter type
	to block_symbol.
	(find_method, find_function_symbols, find_linespec_symbols)
	(find_label_symbols_in_block, find_label_symbols): Change symbol
	vectors to block_symbol vectors.
	* symtab.h (symbol_found_callback_ftype): Change parameter type to
	block_symbol.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change decode_compound_collector to use std::vector
@ 2018-08-30  1:07 sergiodj+buildbot
  2018-09-09  3:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30  1:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4dedf84da98ca7dcb9fc80895044d09b5787c1f0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 4dedf84da98ca7dcb9fc80895044d09b5787c1f0

Change decode_compound_collector to use std::vector

This patch changes decode_compound_collector to use std::vector instead of
VEC, eliminating a cleanup in the process.

gdb/ChangeLog:

	* linespec.c (decode_compound_collector::decode_compound_collector):
	Remove initialization for `m_symtabs'.
	(decode_compound_collector::release_symbols): Change return type
	to std::vector.  Update all callers.
	(class decode_compound_collector) <m_symbols>: Change type to
	std::vector.
	(lookup_prefix_sym): Change return type to std::vector.  Update all
	callers.
	(compare_symbols): Remove.
	(std_compare_symbols): Rename to `compare_symbols'.
	(find_method): Change `sym_classes' parameter to std::vector.
	Update all callers.  Use std::sort to sort sym_classes.
	(find_linespec_symbols): Remove cleanup.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change `minimal_symbols' to std::vector in linespec.c structures
@ 2018-08-30  0:47 sergiodj+buildbot
  2018-09-09  3:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30  0:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c2a031c5822b4256f116254def47b9887c230e68 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: c2a031c5822b4256f116254def47b9887c230e68

Change `minimal_symbols' to std::vector in linespec.c structures

This patch converts linespec.c's linespec.label_symbols member from a
VEC to a std::vector.

gdb/ChangeLog:

	* linespec.c (struct linespec) <minimal_symbols>: Change type to
	std::vector.  Update all users.
	(convert_linespec_to_sals): Use std::sort to sort minimal symbols.
	(struct collect_info) <minimal_symbols>: Likewise.
	(compare_msymbols): Return bool.  Change parameters to const
	bound_minimal_symbol references.
	(find_method, find_function_symbols, find_linespec_symbols): Change
	`minsyms' parameter to std::vector.  Update all callers.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change `function_symbols' to std::vector
@ 2018-08-30  0:11 sergiodj+buildbot
  2018-09-09  3:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-30  0:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7243d0118af6f72e3e72db1eb66941fec4530963 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 7243d0118af6f72e3e72db1eb66941fec4530963

Change `function_symbols' to std::vector

This patch changes the `function_symbols'  members in linespec.c structures
from a VEC to a std::vector.

gdb/ChangeLog:

	* linespec.c (struct linespec) <function_symbols>: Change type to
	std::vector.  Update all users.
	(struct collect_info) <function_symbols>: Likewise.
	(convert_linespec_to_sals): Use std::sort to sort function_symbols.
	(std_compare_symbols): New function.
	(find_method, find_function_symbols, find_linespec_symbols)
	(find_label_symbols_in_block): Change `symbols' parameter to
	std::vector.  Update all callers.
	(find_label_symbols): Likewise for `function_symbols' and
	`label_funcs_ret'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix windows-nat.c for -Wnarrowing
@ 2018-08-29 22:41 sergiodj+buildbot
  2018-09-09  3:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 22:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73c13fe69a4275433544533a610275861346ef44 ***

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

Fix windows-nat.c for -Wnarrowing

Sergio pointed out that the Windows builder was failing due to the
-Wnarrowing patch, with:

../../binutils-gdb/gdb/windows-nat.c:301:27: error: narrowing conversion of '3221225477' from 'DWORD {aka long unsigned int}' to 'int' inside { } [-Wnarrowing]
   {-1, GDB_SIGNAL_UNKNOWN}};
                           ^
../../binutils-gdb/gdb/windows-nat.c:301:27: error: narrowing conversion of '3221225725' from 'DWORD {aka long unsigned int}' to 'int' inside { } [-Wnarrowing]
../../binutils-gdb/gdb/windows-nat.c:301:27: error: narrowing conversion of '2147483651' from 'DWORD {aka long unsigned int}' to 'int' inside { } [-Wnarrowing]
../../binutils-gdb/gdb/windows-nat.c:301:27: error: narrowing conversion of '2147483652' from 'DWORD {aka long unsigned int}' to 'int' inside { } [-Wnarrowing]
../../binutils-gdb/gdb/windows-nat.c:301:27: error: narrowing conversion of '3221225614' from 'DWORD {aka long unsigned int}' to 'int' inside { } [-Wnarrowing]

Looking into this, I found two things.

First, in struct xlate_exception, it is better to have "them" be of
type DWORD, as that's the type actually in use.

Second, struct xlate_exception and xlate are not used in this file,
because the code in windows_nat_target::resume is #if'd out.

This patch changes the type of "them", but also similarly #if's out
this object.

In order to avoid a narrowing warning from the -1 entry, at Pedro's
suggestion I have removed this and changed windows_nat_target::resume
to use ranged for.

Tested by rebuilding using the mingw toolchain on x86-64 Fedora 28.  I
also tested it by temporarily removing the "#if 0"s and rebuilding.

gdb/ChangeLog
2018-08-29  Tom Tromey  <tom@tromey.com>

	* windows-nat.c (struct xlate_exception) <them>: Change type to
	DWORD.
	(xlate): Fix formatting.  Remove last entry.
	(struct xlate_exception, xlate): Comment out.
	(windows_nat_target::resume): Use ranged for.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [MIPS] Add Loongson 3A2000/3A3000 proccessor support.
@ 2018-08-29 22:36 sergiodj+buildbot
  2018-09-09  3:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 22:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd782c07b914f28fd927cec42eacd8adcf556dca ***

Author: Chenghua Xu <paul.hua.gm@gmail.com>
Branch: master
Commit: bd782c07b914f28fd927cec42eacd8adcf556dca

[MIPS] Add Loongson 3A2000/3A3000 proccessor support.

bfd/
	* archures.c (bfd_architecture): New machine
	bfd_mach_mips_gs464e.
	* bfd-in2.h (bfd_architecture): Likewise.
	* cpu-mips.c (enum I_xxx): Likewise.
	(arch_info_struct): Likewise.
	* elfxx-mips.c (_bfd_elf_mips_mach): Handle
	E_MIPS_MACH_GS464E.
	(mips_set_isa_flags): Likewise.
	(mips_mach_extensions): Map bfd_mach_mips_gs464e to
	bfd_mach_mips_gs464 extension.

binutils/
	* NEWS: Mention Loongson 3A2000/3A3000 proccessor support.
	* readelf.c (get_machine_flags): Handle gs464e.

elfcpp/
	* mips.c (EF_MIPS_MACH): New E_MIPS_MACH_GS464E.

gas/
	* config/tc-mips.c (ISA_HAS_ODD_SINGLE_FPR): Exclude CPU_GS464E.
	(mips_cpu_info_table): Add gs464e descriptors.
	* doc/as.texi (march table): Add gs464e.

include/
	* elf/mips.h (E_MIPS_MACH_XXX): New E_MIPS_MACH_GS464E.
	* opcode/mips.h (CPU_XXX): New CPU_GS464E.

ld/
	* testsuite/ld-mips-elf/mips-elf-flags.exp: Run good_combination
	gs464e and gs464.

opcodes/
	* mips-dis.c (mips_arch_choices): Add gs464e descriptors.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] sparc/leon: add support for partial write psr instruction
@ 2018-08-29 21:44 sergiodj+buildbot
  2018-09-09  3:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 21:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df28970fcc741fa744a51aece29bb755c20eceab ***

Author: Martin Aberg <maberg@gaisler.com>
Branch: master
Commit: df28970fcc741fa744a51aece29bb755c20eceab

sparc/leon: add support for partial write psr instruction

Partial write %PSR (PWRPSR) is a SPARC V8e option that allows the WRPSR
instruction to only affect the %PSR.ET field. When available it is enabled
by setting the rd field of the WRPSR instruction to a value other than 0.
For Leon processors with support for partial write %PSR (currently GR740
and GR716) the rd value must be 1.

opcodes/ChangeLog:

2018-08-29  Martin Aberg  <maberg@gaisler.com>

        * sparc-opc.c (sparc_opcodes): Add Leon specific partial write
        psr (PWRPSR) instruction.

gas/ChangeLog:

2018-08-29  Daniel Cederman  <cederman@gaisler.com>

        * testsuite/gas/sparc/leon.d: New test.
        * testsuite/gas/sparc/leon.s: New test.
        * testsuite/gas/sparc/sparc.exp: Execute the pwrpsr test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix riscv-linux native gdb build failure.
@ 2018-08-29 20:38 sergiodj+buildbot
  2018-09-09  3:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 20:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4d3928d7e0a141e0fb16405d33b375cbe2f13123 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 4d3928d7e0a141e0fb16405d33b375cbe2f13123

Fix riscv-linux native gdb build failure.

The linux kernel uses NT_PRFPREG.  Glibc before BZ 14890 defines NT_FPREGSET.
After it defines both.  Avoid glibc version dependency by using the gdb header
file instead of the glibc header file, and the macro name that gdb defines
which is NT_FPREGSET.

	gdb/
	* riscv-linux-nat.c: Include elf/common.h instead of elf.h.
	(riscv_linux_nat_target::fetch_registers): Use NT_FPREGSET instead
	of NT_PRFPREG.
	(riscv_linux_nat_target::store_registers): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [MIPS/GAS] Split Loongson EXT Instructions from loongson3a.
@ 2018-08-29 19:52 sergiodj+buildbot
  2018-09-09  3:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 19:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bdc6c06e3b08ec48ec5ee2174dedc846969c36fd ***

Author: Chenghua Xu <paul.hua.gm@gmail.com>
Branch: master
Commit: bdc6c06e3b08ec48ec5ee2174dedc846969c36fd

[MIPS/GAS] Split Loongson EXT Instructions from loongson3a.

bfd/
	 * elfxx-mips.c (infer_mips_abiflags): Use ases instead of
	 isa_ext for infer ABI flags.
	 (print_mips_ases): Add Loongson EXT extension.

binutils/
	 * readelf.c (print_mips_ases): Add Loongson EXT extension.

elfcpp/
	 * mips.h (AFL_ASE_LOONGSON_EXT): New enum.

gas/
	 * NEWS: Mention Loongson EXTensions (EXT) support.
	 * config/tc-mips.c (options): Add OPTION_LOONGSON_EXT and
	 OPTION_NO_LOONGSON_EXT.
	 (md_longopts): Likewise.
	 (mips_ases): Define availability for EXT.
	 (mips_convert_ase_flags): Map ASE_LOONGSON_EXT to
	 AFL_ASE_LOONGSON_EXT.
	 (mips_cpu_info_table): Add ASE_LOONGSON_EXT for loongson3a.
	 (md_show_usage): Add help for -mloongson-ext and
	 -mno-loongson-ext.
	 * doc/as.texi: Document -mloongson-ext, -mno-loongson-ext.
	 * doc/c-mips.texi: Document -mloongson-ext, -mno-loongson-ext,
	 .set loongson-ext and .set noloongson-ext.
	 * testsuite/gas/mips/loongson-mmi.d: Add ASE flag.

include/
	 * elf/mips.h (AFL_ASE_LOONGSON_EXT): New macro.
	 (AFL_ASE_MASK): Update to include AFL_ASE_LOONGSON_EXT.
	 * opcode/mips.h (ASE_LOONGSON_EXT): New macro.

opcodes/
	 * mips-dis.c (mips_arch_choices): Add EXT to loongson3a
	 descriptors.
	 (parse_mips_ase_option): Handle -M loongson-ext option.
	 (print_mips_disassembler_options): Document -M loongson-ext.
	 * mips-opc.c (IL3A): Delete.
	 * mips-opc.c (LEXT): New macro.
	 (mips_opcodes): Replace IL2F|IL3A marking with LEXT for EXT
	 instructions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Indicate batch mode failures by exiting with nonzero status
@ 2018-08-29 18:27 sergiodj+buildbot
  2018-09-09  3:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 18:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0f492b90f3d13da8ac80437e6ecb9a87db4a75b ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: b0f492b90f3d13da8ac80437e6ecb9a87db4a75b

Indicate batch mode failures by exiting with nonzero status

This commit causes GDB in batch mode to exit with nonzero status
if the last command to be executed fails.

gdb/ChangeLog:

	PR gdb/13000:
	* gdb/main.c (captured_main_1): Exit with nonzero status
	in batch mode if the last command to be executed failed.
	* NEWS: Mention the above.

gdb/testsuite/ChangeLog:

	PR gdb/13000:
	* gdb.base/batch-exit-status.exp: New file.
	* gdb.base/batch-exit-status.good-commands: Likewise.
	* gdb.base/batch-exit-status.bad-commands: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove newline at end of warning message
@ 2018-08-29 17:20 sergiodj+buildbot
  2018-09-09  3:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2362e7f76adb395df19c867cd27c75f77a0ade6f ***

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

Remove newline at end of warning message

... to fix this ARI warning:

  gdb/csky-tdep.c:1612: gettext: trailing new line: A message should not have a trailing new line
  gdb/csky-tdep.c:1612:    warning (_("Invalid breakpoint address 0x%x is an odd number.\n"),

gdb/ChangeLog:

	* csky-tdep.c (csky_memory_insert_breakpoint): Remove newline at
	end of warning message.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [MIPS/GAS] Split Loongson CAM Instructions from loongson3a
@ 2018-08-29 14:45 sergiodj+buildbot
  2018-09-09  2:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 14:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 716c08de28589a5560b3337f1b935ed84a49b5e5 ***

Author: Chenghua Xu <paul.hua.gm@gmail.com>
Branch: master
Commit: 716c08de28589a5560b3337f1b935ed84a49b5e5

[MIPS/GAS] Split Loongson CAM Instructions from loongson3a

bfd/
	* elfxx-mips.c (print_mips_ases): Add CAM extension.

binutils/
	* readelf.c (print_mips_ases): Add CAM extension.

gas/
	* NEWS: Mention Loongson Content Address Memory (CAM)
	support.
	* config/tc-mips.c (options): Add OPTION_LOONGSON_CAM and
	OPTION_NO_LOONGSON_CAM.
	(md_longopts): Likewise.
	(mips_ases): Define availability for CAM.
	(mips_convert_ase_flags): Map ASE_LOONGSON_CAM to
	AFL_ASE_LOONGSON_CAM.
	(mips_cpu_info_table): Add ASE_LOONGSON_CAM for loongson3a.
	(md_show_usage): Add help for -mloongson-cam and
	-mno-loongson-cam.
	* doc/as.texi: Document -mloongson-cam, -mno-loongson-cam.
	* doc/c-mips.texi: Document -mloongson-cam, -mno-loongson-cam,
	.set loongson-cam and .set noloongson-cam.
	* testsuite/gas/mips/loongson-3a-2.d: Move cam test to ...
	* testsuite/gas/mips/loongson-cam.d: Here.  Add ISA/ASE
	flag verification.
	* testsuite/gas/mips/loongson-3a-2.s: Move cam test to ...
	* testsuite/gas/mips/loongson-cam.s: Here.
	* testsuite/gas/mips/loongson-3a-mmi.d: Add ASE flag.
	* testsuite/gas/mips/mips.exp: Run loongson-cam test.

include/
	* elf/mips.h (AFL_ASE_LOONGSON_CAM): New macro.
	(AFL_ASE_MASK): Update to include AFL_ASE_LOONGSON_CAM.
	* opcode/mips.h (ASE_LOONGSON_CAM): New macro.

opcodes/
	* mips-dis.c (mips_arch_choices): Add CAM to loongson3a
	descriptors.
	(parse_mips_ase_option): Handle -M loongson-cam option.
	(print_mips_disassembler_options): Document -M loongson-cam.
	* mips-opc.c (LCAM): New macro.
	(mips_opcodes): Replace IL2F|IL3A marking with LCAM for CAM
	instructions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] infcall-nested-structs: Test up to five fields
@ 2018-08-29 14:27 sergiodj+buildbot
  2018-09-09  2:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 14:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 36eb4c5f9bbe675a4522a763652f463e5519a955 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 36eb4c5f9bbe675a4522a763652f463e5519a955

infcall-nested-structs: Test up to five fields

Aarch64 can pass structures of up to four members of identical
types in float registers (See AAPCS 5.3 and 5.4). Expand test to
cover this.

Remove the need to specify an additional sets of structures if tB
is not defined.

gdb/testsuite/
	* gdb.base/infcall-nested-structs.c (struct struct01): Remove.
	(struct struct02): Likewise.
	(struct struct03): Likewise.
	(struct struct04): Likewise.
	(struct struct_01_01): New struct.
	(struct struct_01_02): Likewise.
	(struct struct_01_03): Likewise.
	(struct struct_01_04): Likewise.
	(struct struct_02_01): Likewise.
	(struct struct_02_02): Likewise.
	(struct struct_02_03): Likewise.
	(struct struct_02_04): Likewise.
	(struct struct_04_01): Likewise.
	(struct struct_04_02): Likewise.
	(struct struct_04_03): Likewise.
	(struct struct_04_04): Likewise.
	(struct struct_05_01): Likewise.
	(struct struct_05_02): Likewise.
	(struct struct_05_03): Likewise.
	(struct struct_05_04): Likewise.
	(cmp_struct01): Remove function.
	(cmp_struct02): Likewise.
	(cmp_struct03): Likewise.
	(cmp_struct04): Likewise.
	(cmp_struct_01_01): Add Function.
	(cmp_struct_01_02): Likewise.
	(cmp_struct_01_03): Likewise.
	(cmp_struct_01_04): Likewise.
	(cmp_struct_02_01): Likewise.
	(cmp_struct_02_02): Likewise.
	(cmp_struct_02_03): Likewise.
	(cmp_struct_02_04): Likewise.
	(cmp_struct_04_01): Likewise.
	(cmp_struct_04_02): Likewise.
	(cmp_struct_04_03): Likewise.
	(cmp_struct_04_04): Likewise.
	(cmp_struct_05_01): Likewise.
	(cmp_struct_05_02): Likewise.
	(cmp_struct_05_03): Likewise.
	(cmp_struct_05_04): Likewise.
	(call_all): Add new structs.
	* gdb.base/infcall-nested-structs.exp: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64: Float register detection for return values
@ 2018-08-29 13:59 sergiodj+buildbot
  2018-09-09  2:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 13:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f4aedebed5397ba285c2abcd13fa0206d8af291 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 4f4aedebed5397ba285c2abcd13fa0206d8af291

Aarch64: Float register detection for return values

Use aapcs_is_vfp_call_or_return_candidate to detect float register
args.

gdb/
	PR gdb/22943:
	* aarch64-tdep.c (is_hfa_or_hva): Remove function.
	(aarch64_extract_return_value): Use
	aapcs_is_vfp_call_or_return_candidate.
	(aarch64_return_in_memory): Likewise.
	(aarch64_store_return_value): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64: Float register detection for _push_dummy_call
@ 2018-08-29 13:46 sergiodj+buildbot
  2018-09-09  2:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29 13:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e745c601150523093323c3fc77835604221a634 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 0e745c601150523093323c3fc77835604221a634

Aarch64: Float register detection for _push_dummy_call

Use aapcs_is_vfp_call_or_return_candidate to detect float register
args, then pass in registers if there is room.

gdb/
	* aarch64-tdep.c
	(aapcs_is_vfp_call_or_return_candidate): Make static
	(pass_in_v_or_stack): Remove function.
	(pass_in_v_vfp_candidate): New function.
	(aarch64_push_dummy_call): Check for float register candidates.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Get rid of -Wodr warning (PR build/23399)
@ 2018-08-29  3:17 sergiodj+buildbot
  2018-09-09  2:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-29  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad202fcc2277f351d41d4d4e897ad4f6d7c9f043 ***

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

Get rid of -Wodr warning (PR build/23399)

The PR reports that building with -Wodr -flto complains about different
versions of struct ipa_sym_addresses, in common/agent.c and
gdbserver/tracepoint.c.  This patch renames the version in common to
ipa_sym_addresses_common to avoid the name clash.  Because the IPA_SYM
assumed the name ipa_sym_addresses, it now requires the includer to
define the IPA_SYM_STRUCT_NAME macro to define the name of the structure
holding the IPA symbol addresses.

gdb/ChangeLog:

	PR build/23399
	* common/agent.c (IPA_SYM_STRUCT_NAME): Define.
	(struct ipa_sym_addresses): Rename to...
	(struct ipa_sym_addresses_common): ... this.
	* common/agent.h (IPA_SYM): Use IPA_SYM_STRUCT_NAME.

gdb/gdbserver/ChangeLog:

	PR build/23399
	* tracepoint.c (IPA_SYM_STRUCT_NAME): Define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Modify gdb.base/commands.exp to test multi breakpoints command clearing.
@ 2018-08-28 23:33 sergiodj+buildbot
  2018-09-09  2:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-28 23:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ead9aa39bfc80007336bc96c6374df7f79341485 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: ead9aa39bfc80007336bc96c6374df7f79341485

Modify gdb.base/commands.exp to test multi breakpoints command clearing.

gdb/testsuite/ChangeLog
2018-08-26  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.base/commands.exp: Test multi breakpoints command clearing.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix regression for multi breakpoints command line clearing.
@ 2018-08-28 23:18 sergiodj+buildbot
  2018-09-09  2:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-28 23:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 999700cd99a227bd6848e95cdc99117b2185e84c ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 999700cd99a227bd6848e95cdc99117b2185e84c

Fix regression for multi breakpoints command line clearing.

breakpoint.c is modified to fix the regression introduced
when clearing the commands of several breakpoints by giving an empty
list of commands, by just typing "end".
GDB should read an empty list of command once, but it reads
it for each breakpoint, as an empty list of command is NULL,
and NULL is interpreted as 'not having read the command list yet'.

The fix consists in having a boolean set to true once the
command list has been read.

gdb/ChangeLog

2018-08-26  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* breakpoint.c (commands_command_1): New boolean cmd_read
	to detect cmd was already read.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove some uses of VEC from parsers
@ 2018-08-28 22:22 sergiodj+buildbot
  2018-09-09  2:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-28 22:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5fe3f3e4633df1ea76ff24a2732d7c73dc983b90 ***

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

Remove some uses of VEC from parsers

This changes some uses of VEC in a few parsers to std::vector instead.

Tested by the buildbot.

gdb/ChangeLog
2018-08-28  Tom Tromey  <tom@tromey.com>

	* c-exp.y (struct token_and_value): Remove typedef and DEF_VEC.
	(token_fifo): Now a std::vector.
	(yylex, c_parse): Update.
	* d-exp.y (struct token_and_value): Remove typedef and DEF_VEC.
	(token_fifo): Now a std::vector.
	(yylex, d_parse): Update.
	* go-exp.y (struct token_and_value): Remove typedef and DEF_VEC.
	(token_fifo): Now a std::vector.
	(yylex, go_parse): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Implement struct type_stack with a vector
@ 2018-08-28 18:35 sergiodj+buildbot
  2018-09-09  1:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-28 18:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 858d8004b05b572c07a414ae3933299976880bab ***

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

Implement struct type_stack with a vector

This patch changes the home-made stack implementation with a vector,
which makes it a bit more concise and readable.

Regtested on the buildbot.

gdb/ChangeLog:

	* parser-defs.h (struct type_stack) <elements>: Change type to
	std::vector<union type_stack_elt>.
	<depth, size>: Remove.
	* parse.c (parse_exp_in_context_1): Adjust.
	(type_stack_reserve): Remove.
	(check_type_stack_depth): Remove.
	(insert_into_type_stack): Adjust to std::vector.
	(insert_type): Likewise.
	(push_type): Likewise.
	(push_type_int): Likewise.
	(insert_type_address_space): Likewise.
	(pop_type): Likewise.
	(pop_type_int): Likewise.
	(pop_typelist): Likewise.
	(pop_type_stack): Likewise.
	(append_type_stack): Likewise.
	(push_type_stack): Likewise.
	(get_type_stack): Likewise.
	(type_stack_cleanup): Likewise.
	(push_typelist): Likewise.
	(follow_types): Likewise.
	(_initialize_parse): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Don't mask out the GNU_PROPERTY_X86_UINT32_VALID bit
@ 2018-08-28  2:23 sergiodj+buildbot
  2018-09-08 23:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-28  2:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 90c745dc545408a6a3115ff97485672826649ade ***

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

x86: Don't mask out the GNU_PROPERTY_X86_UINT32_VALID bit

Since only the GNU_PROPERTY_X86_UINT32_VALID bit may be set in data-only
relocatable objects which don't contain any instructions, linker
shouldn't mask out the GNU_PROPERTY_X86_UINT32_VALID bit when merging
GNU_PROPERTY_X86_XXX bits.  Otherwise, linker output doesn't contain
GNU_PROPERTY_X86_XXX property with any data-only relocatable inputs.
This patch keeps the GNU_PROPERTY_X86_UINT32_VALID bit and updates
readelf to print "<None>" if GNU_PROPERTY_X86_XXX property only has
the GNU_PROPERTY_X86_UINT32_VALID bit.

bfd/

	* elfxx-x86.c (_bfd_x86_elf_parse_gnu_properties): Don't mask
	out the GNU_PROPERTY_X86_UINT32_VALID bit.

binutils/

	* readelf.c (decode_x86_isa): Print <None> if bitmask only
	contains the GNU_PROPERTY_X86_UINT32_VALID bit.
	(decode_x86_feature_1): Likewise.
	(decode_x86_feature_2): Likewise.
	(print_gnu_property_note): Don't mask out the
	GNU_PROPERTY_X86_UINT32_VALID bit.
	* testsuite/binutils-all/i386/pr21231b.d: Updated.
	* testsuite/binutils-all/x86-64/pr21231b.d: Likewise.

gas/

	* testsuite/gas/i386/i386.exp: Run property-1 and
	x86-64-property-1.
	* testsuite/gas/i386/property-1.d: New file.
	* testsuite/gas/i386/property-1.s: Likewise.
	* testsuite/gas/i386/x86-64-property-1.d: Likewise.

ld/

	* testsuite/ld-i386/i386.exp: Run property-x86-5.
	* testsuite/ld-i386/property-x86-5.d: New file.
	* testsuite/ld-x86-64/property-x86-5-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-5.d: Likewise.
	* testsuite/ld-x86-64/property-x86-5a.s: Likewise.
	* testsuite/ld-x86-64/property-x86-5b.s: Likewise.
	* testsuite/ld-x86-64/x86-64.exp: Run property-x86-5 and
	property-x86-5-x32.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove -Wno-narrowing from warnings.m4
@ 2018-08-27 23:36 sergiodj+buildbot
  2018-09-08 23:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27 23:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3d8724aac2f207467b1004b1424fed0446b6f8a ***

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

Remove -Wno-narrowing from warnings.m4

This removes -Wno-narrowing from warnings.m4.
This is PR build/23087.

gdb/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	PR build/23087:
	* configure: Rebuild.
	* warning.m4 (AM_GDB_WARNINGS): Remove -Wno-narrowing.

gdb/gdbserver/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	PR build/23087:
	* configure: Rebuild.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid -Wnarrowing warnings in aarch64-linux-tdep.c
@ 2018-08-27 23:16 sergiodj+buildbot
  2018-09-08 23:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27 23:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1885053bcb12dd05a6f129146cf514e966082c27 ***

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

Avoid -Wnarrowing warnings in aarch64-linux-tdep.c

This avoids -Wnarrowing warnings in
aarch64_linux_iterate_over_regset_sections, by adding some casts to
int.

gdb/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	* aarch64-linux-tdep.c
	(aarch64_linux_iterate_over_regset_sections) <sve_regmap>: Add
	casts to int.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid -Wnarrowing warnings in ppc64-tdep.c
@ 2018-08-27 22:23 sergiodj+buildbot
  2018-09-08 22:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8406672eca8d008dc0324198ec2f653a16fb9d21 ***

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

Avoid -Wnarrowing warnings in ppc64-tdep.c

This avoids -Wnarrowing warnings in ppc64-tdep.c, by adding a few
casts to unsigned.

gdb/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	* ppc64-tdep.c (insn_d, insn_ds, insn_xfx): Add casts to
	unsigned.
	(ppc64_standard_linkage1, ppc64_standard_linkage2)
	(ppc64_standard_linkage3, ppc64_standard_linkage4)
	(ppc64_standard_linkage5, ppc64_standard_linkage6)
	(ppc64_standard_linkage7, ppc64_standard_linkage8): Add casts to
	unsigned.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid -Wnarrowing warnings in struct tramp_frame instances
@ 2018-08-27 21:29 sergiodj+buildbot
  2018-09-08 22:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7bc02706c3e23b58e1a74ca47fada84fc68699c7 ***

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

Avoid -Wnarrowing warnings in struct tramp_frame instances

This avoids -Wnarrowing warnings in struct tramp_frame instances,
replacing uses of -1 with a new ULONGEST_MAX.  It also redefined
TRAMP_SENTINEL_INSN to avoid the same warning.

gdb/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	* tramp-frame.h (TRAMP_SENTINEL_INSN): Redefine.
	* tilegx-linux-tdep.c (tilegx_linux_rt_sigframe): Use
	ULONGEST_MAX.
	* tic6x-linux-tdep.c (tic6x_linux_rt_sigreturn_tramp_frame): Use
	ULONGEST_MAX.
	* sparc64-linux-tdep.c (sparc64_linux_rt_sigframe): Use
	ULONGEST_MAX.
	* sparc-linux-tdep.c (sparc32_linux_sigframe)
	(sparc32_linux_rt_sigframe): Use ULONGEST_MAX.
	* ppc-nbsd-tdep.c (ppcnbsd_sigtramp, ppcnbsd2_sigtramp): Use
	ULONGEST_MAX.
	* ppc-linux-tdep.c (ppc32_linux_sigaction_tramp_frame)
	(ppc64_linux_sigaction_tramp_frame)
	(ppc32_linux_sighandler_tramp_frame)
	(ppc64_linux_sighandler_tramp_frame): Use ULONGEST_MAX.
	* nios2-linux-tdep.c (nios2_r1_linux_rt_sigreturn_tramp_frame)
	(nios2_r2_linux_rt_sigreturn_tramp_frame): Use ULONGEST_MAX.
	* mn10300-linux-tdep.c (am33_linux_sigframe)
	(am33_linux_rt_sigframe): Use ULONGEST_MAX.
	* mips64-obsd-tdep.c (mips64obsd_sigframe): Use ULONGEST_MAX.
	* mips-linux-tdep.c (mips_linux_o32_sigframe)
	(mips_linux_o32_rt_sigframe, mips_linux_n32_rt_sigframe)
	(mips_linux_n64_rt_sigframe, micromips_linux_o32_sigframe)
	(micromips_linux_o32_rt_sigframe, micromips_linux_n32_rt_sigframe)
	(micromips_linux_n64_rt_sigframe): Use ULONGEST_MAX.
	* mips-fbsd-tdep.c (mips_fbsd_sigframe, mipsn32_fbsd_sigframe)
	(mips64_fbsd_sigframe): Use ULONGEST_MAX.
	* microblaze-linux-tdep.c
	(microblaze_linux_sighandler_tramp_frame): Use ULONGEST_MAX.
	* i386-nbsd-tdep.c (i386nbsd_sigtramp_sc16, i386nbsd_sigtramp_sc2)
	(i386nbsd_sigtramp_si2, i386nbsd_sigtramp_si31)
	(i386nbsd_sigtramp_si4): Use ULONGEST_MAX.
	* hppa-nbsd-tdep.c (hppanbsd_sigtramp_si4): Use ULONGEST_MAX.
	* common/common-types.h (ULONGEST_MAX): New define.
	(CORE_ADDR_MAX): Fix formatting.
	* bfin-linux-tdep.c (bfin_linux_sigframe): Use ULONGEST_MAX.
	* arm-obsd-tdep.c (armobsd_sigframe): Use ULONGEST_MAX.
	* arm-linux-tdep.c (arm_linux_sigreturn_tramp_frame)
	(arm_linux_rt_sigreturn_tramp_frame)
	(arm_eabi_linux_sigreturn_tramp_frame)
	(arm_eabi_linux_rt_sigreturn_tramp_frame)
	(thumb2_eabi_linux_sigreturn_tramp_frame)
	(thumb2_eabi_linux_rt_sigreturn_tramp_frame)
	(arm_linux_restart_syscall_tramp_frame)
	(arm_kernel_linux_restart_syscall_tramp_frame): Use ULONGEST_MAX.
	* arm-fbsd-tdep.c (arm_fbsd_sigframe): Use ULONGEST_MAX.
	* aarch64-linux-tdep.c (aarch64_linux_rt_sigframe): Use
	ULONGEST_MAX.
	* aarch64-fbsd-tdep.c (aarch64_fbsd_sigframe): Use ULONGEST_MAX.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use CORE_ADDR_MAX in various "breaks" arrays
@ 2018-08-27 20:41 sergiodj+buildbot
  2018-09-08 22:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27 20:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 70ab8ccd4f382a6c7e59c523c22b07fe03a95f52 ***

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

Use CORE_ADDR_MAX in various "breaks" arrays

Code like this:

  CORE_ADDR breaks[2] = {-1, -1};

... gives a warning with -Wnarrowing.  This patch changes all
instances of this to use CORE_ADDR_MAX instead.

gdb/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	* rs6000-tdep.c (ppc_deal_with_atomic_sequence): Use
	CORE_ADDR_MAX.
	* mips-tdep.c (mips_deal_with_atomic_sequence)
	(micromips_deal_with_atomic_sequence): Use CORE_ADDR_MAX.
	* arch/arm-get-next-pcs.c (thumb_deal_with_atomic_sequence_raw)
	(arm_deal_with_atomic_sequence_raw): Use CORE_ADDR_MAX.
	* alpha-tdep.c (alpha_deal_with_atomic_sequence): Use
	CORE_ADDR_MAX.
	* aarch64-tdep.c (aarch64_software_single_step): Use
	CORE_ADDR_MAX.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid -Wnarrowing warnings from quote_char()
@ 2018-08-27 20:13 sergiodj+buildbot
  2018-09-08 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27 20:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 896a7aa6a119ce9d4872de87dabb81176489b1a3 ***

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

Avoid -Wnarrowing warnings from quote_char()

This adds a couple of casts to avoid -Wnarrowing warnings coming from
the use of quote_char().

gdb/ChangeLog
2018-08-27  Tom Tromey  <tom@tromey.com>

	* linespec.c (complete_linespec_component): Add cast to "char".
	* completer.c (completion_tracker::build_completion_result): Add
	cast to "char".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make ada_tasks_inferior_data::task_list an std::vector
@ 2018-08-27  8:34 sergiodj+buildbot
  2018-09-08 22:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c645cda49e2b5fcf35773089d1ae16d6fc3481c6 ***

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

Make ada_tasks_inferior_data::task_list an std::vector

This removes a VEC type.  It requires converting ada_tasks_inferior_data
to C++ (initializing fields, allocating with new).  It seems, however,
that the allocated ada_tasks_inferior_data structures are never freed
(that should be fixed separately).

gdb/ChangeLog:

	* ada-tasks.c (ada_task_info_s): Remove typedef.
	(DEF_VEC_O(ada_task_info_s)): Remove.
	(struct ada_tasks_inferior_data): Initialize fields.
	<task_list>: Make an std::vector.
	(get_ada_tasks_inferior_data): Allocate with new.
	(ada_get_task_number): Adjust.
	(get_task_number_from_id): Likewise.
	(valid_task_id): Likewise.
	(ada_get_task_info_from_ptid): Likewise.
	(iterate_over_live_ada_tasks): Likewise.
	(add_ada_task): Likewise.
	(read_known_tasks): Likewise.
	(ada_build_task_list): Likewise.
	(print_ada_task_info): Likewise.
	(info_task): Likewise.
	(task_command_1): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make ada-lang.c::add_angle_brackets return an std::string
@ 2018-08-27  8:30 sergiodj+buildbot
  2018-09-08 22:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-27  8:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39e7af3e4b4e6c9f39d8d58cae73a2d307e6e1a1 ***

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

Make ada-lang.c::add_angle_brackets return an std::string

This removes the need for manual memory management.  It may also be a
bit more efficient, since the returned string can be moved all the way
into the destination, in ada_lookup_name_info::matches.

gdb/ChangeLog:

	* ada-lang.c (add_angle_brackets): Return std::string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Initialize variable in py_get_event_thread
@ 2018-08-26  1:39 sergiodj+buildbot
  2018-09-08  9:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-26  1:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bbbbbceebc342d583057a11d88bae85f451cd904 ***

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

Initialize variable in py_get_event_thread

The pythread variable could be used without being initialized, fix it by
initializing it to nullptr.

gdb/ChangeLog:

	* python/py-threadevent.c (py_get_event_thread): Initialize
	pythread.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] elf: Check for corrupt symbol version info
@ 2018-08-25 23:27 sergiodj+buildbot
  2018-09-08  8:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-25 23:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7a815dd566f3dd32435ac73aa0a0cc948d525e06 ***

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

elf: Check for corrupt symbol version info

The BFD linker with PR ld/23499 may generate shared libraries with
corrupt symbol version info which leads to linker error when the
corrupt shared library is used:

/usr/bin/ld: bin/libKF5Service.so.5.49.0: _edata: invalid version 21 (max 0)
/usr/bin/ld: bin/libKF5Service.so.5.49.0: error adding symbols: bad value

Add check for corrupt symbol version info to objdump:

00000000000af005 g    D  .data	0000000000000000  <corrupt>   _edata

and readelf:

   728: 00000000000af005     0 NOTYPE  GLOBAL DEFAULT   25 _edata@<corrupt> (5)

bfd/

	PR ld/23499
	* elf.c (_bfd_elf_get_symbol_version_string): Return
	_("<corrupt>") for corrupt symbol version info.

binutils/

	PR ld/23499
	* readelf.c (get_symbol_version_string): Return _("<corrupt>")
	for corrupt symbol version info.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/python: Use copy-initialization more when possible
@ 2018-08-25  0:03 sergiodj+buildbot
  2018-09-07 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-25  0:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d98fc15be2b8dd5699c1852db7d9d979231123dc ***

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

gdb/python: Use copy-initialization more when possible

gdb/ChangeLog:
2018-08-24  Pedro Alves  <palves@redhat.com>

	* python/py-bpevent.c (create_breakpoint_event_object): Use
	copy-initialization.
	* python/py-continueevent.c (emit_continue_event): Use
	copy-initialization.
	* python/py-exitedevent.c (create_exited_event_object): Return a
	gdbpy_ref<>.
	(emit_exited_event): Use copy-initialization.
	* python/py-inferior.c (python_new_inferior)
	(python_inferior_deleted, add_thread_object): Use
	copy-initialization.
	* python/py-infevents.c (create_inferior_call_event_object)
	(create_register_changed_event_object)
	(create_memory_changed_event_object): Return a gdbpy_ref<>.
	(emit_inferior_call_event, emit_memory_changed_event)
	(emit_register_changed_event): Use copy-initialization.
	* python/py-newobjfileevent.c (create_new_objfile_event_object):
	Return a gdbpy_ref<>.
	(emit_new_objfile_event): Use copy-initialization.
	(create_clear_objfiles_event_object): Return a gdbpy_ref<>.
	(emit_clear_objfiles_event): Use copy-initialization.
	* python/py-signalevent.c (create_signal_event_object): Use
	copy-initialization.
	* python/py-threadevent.c (create_thread_event_object): Use
	copy-initialization.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix 8.2 regression in gdb.python/py-evthreads.exp w/ gdbserver (PR gdb/23379)
@ 2018-08-24 23:08 sergiodj+buildbot
  2018-09-07 22:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24 23:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da3c873831707454d45cee6705075b27a1732f09 ***

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

Fix 8.2 regression in gdb.python/py-evthreads.exp w/ gdbserver (PR gdb/23379)

This commit fixes a 8.1->8.2 regression exposed by
gdb.python/py-evthreads.exp when testing with
--target_board=native-gdbserver.

gdb.log shows:

  src/gdb/thread.c:93: internal-error: thread_info* inferior_thread(): 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.python/py-evthreads.exp: run to breakpoint 1 (GDB internal error)

A backtrace shows (frames #2 and #10 highlighted) that the assertion
fails when GDB is setting up the connection to the remote target, in
non-stop mode:

  #0  0x0000000000622ff0 in internal_error(char const*, int, char const*, ...) (file=0xc1ad98 "src/gdb/thread.c", line=93, fmt=0xc1ad20 "%s: Assertion `%s' failed.") at src/gdb/common/errors.c:54
  #1  0x000000000089567e in inferior_thread() () at src/gdb/thread.c:93
= #2  0x00000000004da91d in get_event_thread() () at src/gdb/python/py-threadevent.c:38
  #3  0x00000000004da9b7 in create_thread_event_object(_typeobject*, _object*) (py_type=0x11574c0 <continue_event_object_type>, thread=0x0)
      at src/gdb/python/py-threadevent.c:60
  #4  0x00000000004bf6fe in create_continue_event_object() () at src/gdb/python/py-continueevent.c:27
  #5  0x00000000004bf738 in emit_continue_event(ptid_t) (ptid=...) at src/gdb/python/py-continueevent.c:40
  #6  0x00000000004c7d47 in python_on_resume(ptid_t) (ptid=...) at src/gdb/python/py-inferior.c:108
  #7  0x0000000000485bfb in std::_Function_handler<void (ptid_t), void (*)(ptid_t)>::_M_invoke(std::_Any_data const&, ptid_t&&) (__functor=..., __args#0=...) at /usr/include/c++/7/bits/std_function.h:316
  #8  0x000000000089b416 in std::function<void (ptid_t)>::operator()(ptid_t) const (this=0x12aa600, __args#0=...)
      at /usr/include/c++/7/bits/std_function.h:706
  #9  0x000000000089aa0e in gdb::observers::observable<ptid_t>::notify(ptid_t) const (this=0x118a7a0 <gdb::observers::target_resumed>, args#0=...)
      at src/gdb/common/observable.h:106
= #10 0x0000000000896fbe in set_running(ptid_t, int) (ptid=..., running=1) at src/gdb/thread.c:880
  #11 0x00000000007f750f in remote_target::remote_add_thread(ptid_t, bool, bool) (this=0x12c5440, ptid=..., running=true, executing=true) at src/gdb/remote.c:2434
  #12 0x00000000007f779d in remote_target::remote_notice_new_inferior(ptid_t, int) (this=0x12c5440, currthread=..., executing=1)
      at src/gdb/remote.c:2515
  #13 0x00000000007f9c44 in remote_target::update_thread_list() (this=0x12c5440) at src/gdb/remote.c:3831
  #14 0x00000000007fb922 in remote_target::start_remote(int, int) (this=0x12c5440, from_tty=0, extended_p=0)
      at src/gdb/remote.c:4655
  #15 0x00000000007fd102 in remote_target::open_1(char const*, int, int) (name=0x1a4f45e "localhost:2346", from_tty=0, extended_p=0)
      at src/gdb/remote.c:5638
  #16 0x00000000007fbec1 in remote_target::open(char const*, int) (name=0x1a4f45e "localhost:2346", from_tty=0)
      at src/gdb/remote.c:4862

So on frame #10, we're marking a newly-discovered thread as running,
and that causes the Python API to emit a gdb.ContinueEvent.
gdb.ContinueEvent is a gdb.ThreadEvent, and as such includes the event
thread as the "inferior_thread" attribute.  The problem is that when
we get to frame #3/#4, we lost all references to the thread that is
being marked as running.  create_continue_event_object assumes that it
is the current thread, which is not true in this case.

Fix this by passing down the right thread in
create_continue_event_object.  Also remove
create_thread_event_object's default argument and have the only other
caller left pass down the right thread explicitly too.

gdb/ChangeLog:
2018-08-24  Pedro Alves  <palves@redhat.com>
	    Simon Marchi  <simon.marchi@ericsson.com>

	PR gdb/23379
	* python/py-continueevent.c: Include "gdbthread.h".
	(create_continue_event_object): Add intro comment.  Add 'ptid'
	parameter.  Use it to find thread to pass to
	create_thread_event_object.
	(emit_continue_event): Pass PTID down to
	create_continue_event_object.
	* python/py-event.h (py_get_event_thread): Declare.
	(create_thread_event_object): Remove default from 'thread'
	parameter.
	* python/py-stopevent.c (create_stop_event_object): Use
	py_get_event_thread.
	* python/py-threadevent.c (get_event_thread): Rename to ...
	(py_get_event_thread): ... this, make extern, add 'ptid' parameter
	and use it to find the thread.
	(create_thread_event_object): Assert that THREAD isn't null.
	Don't find the event thread here.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Update GNU_PROPERTY_X86_XXX macros
@ 2018-08-24 15:00 sergiodj+buildbot
  2018-09-07 22:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24 15:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9eafb08b3f3dd4cd59757f0b99b44e896d620f1 ***

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

x86: Update GNU_PROPERTY_X86_XXX macros

This patch updates GNU_PROPERTY_X86_XXX macros:

1. GNU_PROPERTY_X86_UINT32_AND_XXX: A 4-byte unsigned integer property.
A bit is set if it is set in all relocatable inputs:

 #define GNU_PROPERTY_X86_UINT32_AND_LO      0xc0000002
 #define GNU_PROPERTY_X86_UINT32_AND_HI      0xc0007fff

2. GNU_PROPERTY_X86_UINT32_OR_XXX: A 4-byte unsigned integer property.
A bit is set if it is set in any relocatable inputs:

 #define GNU_PROPERTY_X86_UINT32_OR_LO    0xc0008000
 #define GNU_PROPERTY_X86_UINT32_OR_HI    0xc000ffff

3. GNU_PROPERTY_X86_UINT32_OR_AND_XXX: A 4-byte unsigned integer property.
A bit is set if it is set in any relocatable inputs and the property is
present in all relocatable inputs:

 #define GNU_PROPERTY_X86_UINT32_OR_AND_LO   0xc0010000
 #define GNU_PROPERTY_X86_UINT32_OR_AND_HI   0xc0017fff

4. GNU_PROPERTY_X86_FEATURE_2_NEEDED, GNU_PROPERTY_X86_FEATURE_2_USED
and GNU_PROPERTY_X86_FEATURE_2_XXX bits.

GNU_PROPERTY_X86_FEATURE_1_AND is unchanged.  GNU_PROPERTY_X86_ISA_1_USED
and GNU_PROPERTY_X86_ISA_1_NEEDED are updated to better support targeted
processors since GNU_PROPERTY_X86_ISA_1_?86 aren't isn't very useful.
A new set of GNU_PROPERTY_X86_ISA_1_XXX bits are defined.  The previous
GNU_PROPERTY_X86_ISA_1_XXX macros are deprecated and renamed to
GNU_PROPERTY_X86_COMPAT_ISA_1_XXX.

bfd/

	* elfxx-x86.c (_bfd_x86_elf_parse_gnu_properties): Handle
	X86_COMPAT_ISA_1_USED, X86_COMPAT_ISA_1_NEEDED,
	X86_UINT32_AND_LO, X86_UINT32_AND_HI, X86_UINT32_OR_LO,
	X86_UINT32_OR_HI, X86_UINT32_OR_AND_LO and X86_UINT32_OR_AND_HI
	instead of X86_ISA_1_USED, X86_ISA_1_NEEDED and X86_FEATURE_1_AND.
	(_bfd_x86_elf_merge_gnu_properties): Likewise.
	(_bfd_x86_elf_link_setup_gnu_properties): Add X86_FEATURE_2_NEEDED
	instead of X86_ISA_1_NEEDED.
	(_bfd_x86_elf_link_fixup_gnu_properties): Handle
	X86_COMPAT_ISA_1_USED, X86_COMPAT_ISA_1_NEEDED, X86_UINT32_AND_LO,
	X86_UINT32_AND_HI, X86_UINT32_OR_LO, X86_UINT32_OR_HI,
	X86_UINT32_OR_AND_LO and X86_UINT32_OR_AND_HI instead of
	X86_ISA_1_USED, X86_ISA_1_NEEDED and X86_FEATURE_1_AND.

binutils/

	* readelf.c (decode_x86_compat_isa): New function.
	(decode_x86_feature_2): Likewise.
	(decode_x86_isa): Updated for new X86_ISA_1_XXX bits.
	(decode_x86_feature): Renamed to ...
	(decode_x86_feature_1): This.  Remove the type argument.
	(print_gnu_property_note): Handle X86_COMPAT_ISA_1_USED,
	X86_COMPAT_ISA_1_NEEDED, X86_UINT32_AND_LO, X86_UINT32_AND_HI,
	X86_UINT32_OR_LO, X86_UINT32_OR_HI, X86_UINT32_OR_AND_LO and
	X86_UINT32_OR_AND_HI instead of X86_ISA_1_USED, X86_ISA_1_NEEDED
	and X86_FEATURE_1_AND.
	* testsuite/binutils-all/i386/pr21231b.s: Updated to the current
	GNU_PROPERTY_X86_ISA_1_USED and GNU_PROPERTY_X86_ISA_1_NEEDED
	values.
	* testsuite/binutils-all/x86-64/pr21231b.s: Likewise.
	* testsuite/binutils-all/x86-64/pr23494a.s: Likewise.
	* testsuite/binutils-all/x86-64/pr23494b.s: Likewise.
	* testsuite/binutils-all/x86-64/pr23494c.s: Likewise.
	* testsuite/binutils-all/i386/pr21231b.d: Updated.
	* testsuite/binutils-all/x86-64/pr21231b.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494a-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494a.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494c-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494c.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494d-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494d.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494e-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494e.d: Likewise.

include/

	* elf/common.h (GNU_PROPERTY_X86_ISA_1_USED): Renamed to ...
	(GNU_PROPERTY_X86_COMPAT_ISA_1_USED): This.
	(GNU_PROPERTY_X86_ISA_1_NEEDED): Renamed to ...
	(GNU_PROPERTY_X86_COMPAT_ISA_1_NEEDED): This.
	(GNU_PROPERTY_X86_ISA_1_XXX): Renamed to ...
	(GNU_PROPERTY_X86_COMPAT_ISA_1_XXX): This.
	(GNU_PROPERTY_X86_UINT32_AND_LO): New.
	(GNU_PROPERTY_X86_UINT32_AND_HI): Likewise.
	(GNU_PROPERTY_X86_UINT32_OR_LO): Likewise.
	(GNU_PROPERTY_X86_UINT32_OR_HI): Likewise.
	(GNU_PROPERTY_X86_UINT32_OR_AND_LO): Likewise.
	(GNU_PROPERTY_X86_UINT32_OR_AND_HI): Likewise.
	(GNU_PROPERTY_X86_ISA_1_CMOV): Likewise.
	(GNU_PROPERTY_X86_ISA_1_SSE): Likewise.
	(GNU_PROPERTY_X86_ISA_1_SSE2): Likewise.
	(GNU_PROPERTY_X86_ISA_1_SSE3): Likewise.
	(GNU_PROPERTY_X86_ISA_1_SSSE3): Likewise.
	(GNU_PROPERTY_X86_ISA_1_SSE4_1): Likewise.
	(GNU_PROPERTY_X86_ISA_1_SSE4_2): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX2): Likewise.
	(GNU_PROPERTY_X86_ISA_1_FMA): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512F): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512CD): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512ER): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512PF): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512VL): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512DQ): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512BW): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_4FMAPS): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_4VNNIW): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_BITALG): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_IFMA): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_VBMI): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_VBMI2): Likewise.
	(GNU_PROPERTY_X86_ISA_1_AVX512_VNNI): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_X86): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_X87): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_MMX): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_XMM): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_YMM): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_ZMM): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_FXSR): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_XSAVE): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_XSAVEOPT): Likewise.
	(GNU_PROPERTY_X86_FEATURE_2_XSAVEC): Likewise.
	(GNU_PROPERTY_X86_FEATURE_1_AND): Updated to
	(GNU_PROPERTY_X86_UINT32_AND_LO + 0).
	(GNU_PROPERTY_X86_ISA_1_NEEDED): Defined to
	(GNU_PROPERTY_X86_UINT32_OR_LO + 0).
	(GNU_PROPERTY_X86_FEATURE_2_NEEDED): New.  Defined to
	(GNU_PROPERTY_X86_UINT32_OR_LO + 1).
	(GNU_PROPERTY_X86_ISA_1_USED): Defined to
	(GNU_PROPERTY_X86_UINT32_OR_AND_LO + 0).
	(GNU_PROPERTY_X86_FEATURE_2_USED): New.  Defined to
	(GNU_PROPERTY_X86_UINT32_OR_AND_LO + 1).

ld/

	* testsuite/ld-i386/i386.exp: Run pr23372c, pr23372d, pr23486c
	and pr23486d.
	* testsuite/ld-i386/pr23372a.s: Update comments.
	* testsuite/ld-i386/pr23372b.s: Likewise.
	* testsuite/ld-i386/pr23372c.s: Likewise.
	* testsuite/ld-x86-64/pr23372a.s: Likewise.
	* testsuite/ld-x86-64/pr23372b.s: Likewise.
	* testsuite/ld-x86-64/pr23372c.s: Likewise.
	* testsuite/ld-x86-64/pr23486a.s: Likewise.
	* testsuite/ld-x86-64/pr23486b.s: Likewise.
	* testsuite/ld-i386/pr23372c.d: New file.
	* testsuite/ld-i386/pr23372d.d: Likewise.
	* testsuite/ld-i386/pr23486c.d: Likewise.
	* testsuite/ld-i386/pr23486d.d: Likewise.
	* testsuite/ld-x86-64/pr23372c-x32.d: Likewise.
	* testsuite/ld-x86-64/pr23372c.d: Likewise.
	* testsuite/ld-x86-64/pr23372d-x32.d: Likewise.
	* testsuite/ld-x86-64/pr23372d.d: Likewise.
	* testsuite/ld-x86-64/pr23372d.s: Likewise.
	* testsuite/ld-x86-64/pr23372e.s: Likewise.
	* testsuite/ld-x86-64/pr23372f.s: Likewise.
	* testsuite/ld-x86-64/pr23486c-x32.d: Likewise.
	* testsuite/ld-x86-64/pr23486c.d: Likewise.
	* testsuite/ld-x86-64/pr23486c.s: Likewise.
	* testsuite/ld-x86-64/pr23486d-x32.d: Likewise.
	* testsuite/ld-x86-64/pr23486d.d: Likewise.
	* testsuite/ld-x86-64/pr23486d.s: Likewise.
	* testsuite/ld-i386/property-3.r: Updated.
	* testsuite/ld-i386/property-4.r: Likewise.
	* testsuite/ld-i386/property-5.r: Likewise.
	* testsuite/ld-i386/property-x86-3.d: Likewise.
	* testsuite/ld-i386/property-x86-ibt3a.d: Likewise.
	* testsuite/ld-i386/property-x86-shstk3a.d: Likewise.
	* testsuite/ld-i386/property-x86-shstk3b.d: Likewise.
	* testsuite/ld-x86-64/property-3.r: Likewise.
	* testsuite/ld-x86-64/property-4.r: Likewise.
	* testsuite/ld-x86-64/property-5.r: Likewise.
	* testsuite/ld-x86-64/property-x86-3-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-3.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3a-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3a.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3b-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3b.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3a-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3a.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3b-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3b.d: Likewise.
	* testsuite/ld-i386/property-x86-1.S: Updated to the current
	GNU_PROPERTY_X86_ISA_1_USED and GNU_PROPERTY_X86_ISA_1_NEEDED
	values.
	* testsuite/ld-i386/property-x86-2.S: Likewise.
	* testsuite/ld-i386/property-x86-3.s: Likewise.
	* testsuite/ld-x86-64/property-x86-1.S: Likewise.
	* testsuite/ld-x86-64/property-x86-2.S: Likewise.
	* testsuite/ld-x86-64/property-x86-3.s: Likewise.
	* ld/testsuite/ld-x86-64/x86-64.exp: Run pr23372c, pr23372c-x32,
	pr23372d, pr23372d-x32, pr23486c, pr23486c-x32, pr23486d and
	pr23486d-x32.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Add GNU_PROPERTY_X86_UINT32_VALID
@ 2018-08-24 14:05 sergiodj+buildbot
  2018-09-07 21:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24 14:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aa7bca9b2e30cf128966631382731369f7b753d8 ***

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

x86: Add GNU_PROPERTY_X86_UINT32_VALID

The older linker treats .note.gnu.property section as a generic note
and just concatenates all .note.gnu.property sections from the input
to the output.  On CET-enabled OS, the output of the older linker is
marked as CET enabled, but in fact, it is not CET enabled and it crashes
on CET-enabled machines.

This patch defines GNU_PROPERTY_X86_UINT32_VALID.  Linker is updated to
set the GNU_PROPERTY_X86_UINT32_VALID bit in GNU property note for
non-relocatable output to differentiate outputs from the older linker.

bfd/

	* elfxx-x86.c (_bfd_x86_elf_parse_gnu_properties): Mask out the
	GNU_PROPERTY_X86_UINT32_VALID bit.
	(_bfd_x86_elf_link_fixup_gnu_properties): Set the
	GNU_PROPERTY_X86_UINT32_VALID bit for non-relocatable output.

binutils/

	* readelf.c (print_gnu_property_note): Check the
	GNU_PROPERTY_X86_UINT32_VALID bit for invalid GNU property note.

include/

	* elf/common.h (GNU_PROPERTY_X86_UINT32_VALID): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Test case for functions with non-contiguous ranges
@ 2018-08-24  9:28 sergiodj+buildbot
  2018-09-07 21:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24  9:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 450d1e88e32ef433f25959358521c953050f0037 ***

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

Test case for functions with non-contiguous ranges

See comments in the new files for what this is about - I tried to
explain it all there.

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/dw2-ranges-func.c: New file.
	* gdb.dwarf2/dw2-ranges-func.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for non-contiguous blocks to find_pc_partial_function
@ 2018-08-24  2:24 sergiodj+buildbot
  2018-09-07 13:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24  2:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fc811edd39fcdf6e52c95ebd2d975debee700223 ***

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

Add support for non-contiguous blocks to find_pc_partial_function

This change adds an optional output parameter BLOCK to
find_pc_partial_function.  If BLOCK is non-null, then *BLOCK will be
set to the address of the block corresponding to the function symbol
if such a symbol was found during lookup.  Otherwise it's set to the
NULL value.  Callers may wish to use the block information to
determine whether the block contains any non-contiguous ranges.  The
caller may also iterate over or examine those ranges.

When I first started looking at the broken stepping behavior associated
with functions w/ non-contiguous ranges, I found that I could "fix"
the problem by disabling the find_pc_partial_function cache.  It would
sometimes happen that the PC passed in would be between the low and
high cache values, but would be in some other function that happens to
be placed in between the ranges for the cached function.  This caused
incorrect values to be returned.

So dealing with this cache turns out to be very important for fixing
this problem.  I explored three different ways of dealing with the
cache.

My first approach was to clear the cache when a block was encountered
with more than one range.  This would cause the non-cache pathway to
be executed on the next call to find_pc_partial_function.

Another approach, which I suspect is slightly faster, checks to see
whether the PC is within one of the ranges associated with the cached
block.  If so, then the cached values can be used.  It falls back to
the original behavior if there is no cached block.

The current approach, suggested by Simon Marchi, is to restrict the
low/high pc values recorded for the cache to the beginning and end of
the range containing the PC value under consideration.  This allows us
to retain the simple (and fast) test for determining whether the
memoized (cached) values apply to the PC passed to
find_pc_partial_function.

Another choice that had to be made regards setting *ADDRESS and
*ENDADDR.  There are three possibilities which might make sense:

1) *ADDRESS and *ENDADDR represent the lowest and highest address
   of the function.
2) *ADDRESS and *ENDADDR are set to the start and end address of
   the range containing the entry pc.
3) *ADDRESS and *ENDADDR are set to the start and end address of
   the range in which PC is found.

An earlier version of this patch implemented option #1.  I found out
that it's not very useful though and, in fact, returns results that
are incorrect when used in the context of determining the start and
end of the function for doing prologue analysis.  While debugging a
function in which the entry pc was in the second range (of a function
containing two non-contiguous ranges), I noticed that
amd64_skip_prologue called find_pc_partial_function - the returned
start address was set to the beginning of the first range.  This is
incorrect for this function.  What was also interesting was that this
first invocation of find_pc_partial_function correctly set the cache
for the PC on which it had been invoked, but a slightly later call
from skip_prologue_using_sal could not use this cached value because
it was now being used to lookup the very lowest address of the
function - which is in a range not containing the entry pc.

Option #2 is attractive as it would provide a desirable result
when used in the context of prologue analysis.  However, many callers,
including some which do prologue analysis want the condition
*ADDRESS <= PC < *ENDADDR to hold.  This will not be the case when
find_pc_partial_function is called on a PC that's in a non-entry-pc
range.  A later patch to this series adds
find_function_entry_range_from_pc as a wrapper of
find_pc_partial_function.

Option #3 causes the *ADDRESS <= PC < *ENDADDR property to hold.  If
find_pc_partial_function is called with a PC that's within entry pc's
range, then it will correctly return the limits of that range.  So, if
the result of a minsym search is passed to find_pc_partial_function
to find the limits, then correct results will be achieved.  Returned
limits (for prologue analysis) won't be correct when PC is within some
other (non-entry-pc) range.  I don't yet know how big of a problem
this might be; I'm guessing that it won't be a serious problem - if a
compiler generates functions which have non-contiguous ranges, then it
also probably generates DWARF2 CFI which makes a lot of the old
prologue analysis moot.

I've implemented option #3 for this version of the patch.  I don't see
any regressions for x86-64.  Moreover, I don't expect to see
regressions for other targets either simply because
find_pc_partial_function behaves the same as it did before for the
contiguous address range case.  That said, there may be some
adjustments needed if GDB encounters a function requiring prologue
analysis which occupies non-contiguous ranges.

gdb/ChangeLog:

	* symtab.h (find_pc_partial_function): Add new parameter `block'.
	* blockframe.c (cache_pc_function_block): New static global.
	(clear_pc_function_cache): Clear cache_pc_function_block.
	(find_pc_partial_function): Move comment to symtab.h.  Add
	support for non-contiguous blocks.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Introduce find_function_entry_range_from_pc and use it in infrun.c
@ 2018-08-24  0:42 sergiodj+buildbot
  2018-09-07 21:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24  0:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59adbf5d03f5d9380f9870e22262c59f5f9beec8 ***

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

Introduce find_function_entry_range_from_pc and use it in infrun.c

An earlier version of this patch used the returned block in conjunction
with BLOCK_ENTRY_PC to set stop_func_start in fill_in_stop_func() in
infrun.c.  While I think this was the correct thing to do, changes
to find_inferior_partial_function could potentially end up with
stop_func_end < stop_func_start, which is definitely wrong.  For
this case, we want to set both stop_func_start and stop_func_end
to the start and end of the range containing the function's entry
pc.

I think that this functionality will be useful in many other places
too - it probably ought to be used in all of the various prologue
analyzers in GDB.

The change to infrun.c was simple: the call to
find_pc_partial_function was replaced with a call to
find_function_entry_range_from_pc.  The difference between these two
functions is that find_pc_partial_entry_function will (potentially)
return the start and end address corresponding to the range in which
PC is found, but find_function_entry_range_from_pc will (again,
potentially) return the start and end address of the range containing
the entry pc.  find_pc_partial_function has the property that
*ADDRESS <= PC < *ENDADDR.  This condition does not necessarily hold
for the outputs of find_function_entry_range_from_pc.

It should be noted that for functions which contain only a single
range, the outputs of find_pc_partial_function and
find_function_entry_range_from_pc are identical.

I think it might happen that find_function_entry_range_from_pc will come
to be used in place of many of the calls to find_pc_partial_function
within GDB.  Care must be taken in making this change, however, since
some of this code depends on the *ADDRESS <= PC < *ENDADDR property.

Finally, a note regarding the name: I had initially chosen a different
name with a find_pc_partial_ prefix, but Simon suggested the current
name citing the goal of eventually making naming consistent using
the form find_X_from_Y.  In this case X is "function_entry_range" and
Y is "pc".  Both the name and rationale made sense to me, so that's
how it came to be.

gdb/ChangeLog:

	* infrun.c (fill_in_stop_func): Use find_function_entry_range_from_pc
	in place of find_pc_partial_function.
	* blockframe.c (find_function_entry_range_from_pc): New function.
	* symtab.h (find_function_entry_range_from_pc): Declare and document.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Disassemble blocks with non-contiguous ranges
@ 2018-08-24  0:17 sergiodj+buildbot
  2018-09-07 14:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-24  0:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e94802301b37de0e75e9329a96b0e70d38e5ead9 ***

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

Disassemble blocks with non-contiguous ranges

This patch adds support for disassembly of blocks with non-contiguous
ranges.  These blocks are printed as follows:

(gdb) disassemble foo
Dump of assembler code for function foo:
Address range 0x401136 to 0x401151:
   0x0000000000401136 <+0>:     push   %rbp
   0x0000000000401137 <+1>:     mov    %rsp,%rbp
   0x000000000040113a <+4>:     callq  0x401134 <bar>
   0x000000000040113f <+9>:     mov    0x2eef(%rip),%eax        # 0x404034 <e>
   0x0000000000401145 <+15>:    test   %eax,%eax
   0x0000000000401147 <+17>:    je     0x40114e <foo+24>
   0x0000000000401149 <+19>:    callq  0x401128 <foo+4294967282>
   0x000000000040114e <+24>:    nop
   0x000000000040114f <+25>:    pop    %rbp
   0x0000000000401150 <+26>:    retq
Address range 0x401128 to 0x401134:
   0x0000000000401128 <+-14>:   push   %rbp
   0x0000000000401129 <+-13>:   mov    %rsp,%rbp
   0x000000000040112c <+-10>:   callq  0x401126 <baz>
   0x0000000000401131 <+-5>:    nop
   0x0000000000401132 <+-4>:    pop    %rbp
   0x0000000000401133 <+-3>:    retq
End of assembler dump.

This is an actual dump from the test case that I constructed for
this work.  The ranges are printed in the order encountered in the
debug info. For the above example, note that the second range occupies
lower addresses than the first range.

Functions with contiguous ranges are still printed as follows:

(gdb) disassemble main
Dump of assembler code for function main:
   0x0000000000401151 <+0>:     push   %rbp
   0x0000000000401152 <+1>:     mov    %rsp,%rbp
   0x0000000000401155 <+4>:     callq  0x401136 <foo>
   0x000000000040115a <+9>:     mov    $0x0,%eax
   0x000000000040115f <+14>:    pop    %rbp
   0x0000000000401160 <+15>:    retq
End of assembler dump.

gdb/ChangeLog:

	* cli/cli-cmds.c (block.h): Include.
	(print_disassembly): Handle printing of non-contiguous blocks.
	(disassemble_current_function): Likewise.
	(disassemble_command): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Record explicit block ranges from dwarf2read.c
@ 2018-08-23 23:54 sergiodj+buildbot
  2018-09-07 12:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23 23:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d5f09ec45f81a9c89a98c4629662d812774dfd0 ***

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

Record explicit block ranges from dwarf2read.c

This change sets BLOCK_RANGES for the block under consideration by
calling make_blockranges().  This action is performed in
dwarf2_record_block_ranges().

It should be noted that dwarf2_record_block_ranges() already does some
recording of the range via a call to record_block_range().  The ranges
recorded in that fashion end up in the address map associated with the
blockvector for the compilation unit's symtab.  Given an address, the
addrmap provides a fast way of finding the block containing that
address.  The address map does not, however, provide a convenient way
of determining which address ranges make up a particular block.

While reading a set of ranges, a vector of pairs is used to collect
the starting and ending addresses for each range in the block.  Once
all of the ranges for a block have been collected, make_blockranges()
is called to fill in BLOCK_RANGES for the block.

The ranges are stored for the block in the order that they're read
from the debug info.  For DWARF, the starting address of the first
range of the block will be the entry pc in cases where DW_AT_entry_pc
is not present.  (Well, that would ideally be the case.  At the moment
DW_AT_entry_pc is not being handled.)

gdb/ChangeLog:

	* dwarf2read.c (dwarf2_record_block_ranges): Fill in BLOCK_RANGES
	for block.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add block range data structure for blocks with non-contiguous address ranges
@ 2018-08-23 23:42 sergiodj+buildbot
  2018-09-07 11:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23 23:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26457a9cf3c0ae49a3a2d0d0d0f25e2658b5f0d4 ***

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

Add block range data structure for blocks with non-contiguous address ranges

This patch does the following:

- Introduces a block range data structure which is accessed via
  a new field in struct block.
- Defines several macros for accessing block ranges.
- Defines a new function, make_blockrange, which is responsible for
  creating the new data structure.

It should be noted that some support for non-contiguous ranges already
existed in GDB in the form of blockvector addrmaps.  This support
allowed GDB to quickly find a block containing a particular address
even when the block consists of non-contiguous addresses.  See
find_block_in_blockvector() in block.c, dwarf2_record_block_ranges()
in dwarf2read.c, and record_block_range() in buildsym.c.

Addrmaps do not provide a convenient way to examine address ranges
associated with a particular block.  This data structure (and its
interface) is set up for quickly finding the value (which in this case
is a block) associated with a particular address.  The interface
does not include a method for doing a reverse mapping from blocks to
addresses.  A linear time mapping might be attempted via use of the
addrmap's foreach method, but this is not as straightforward as it
might first appear due to the fact that blocks corresponding to inline
function instances and lexical blocks w/ variables end up getting
interspersed in in the set of transitions.

Note:  If this approach is deemed to be too expensive in terms of
space, an alternate approach might be to attempt the linear time
mapping noted above.  find_pc_partial_function() needs to be able to
quickly know whether there are discontiguous ranges, so a flag for
this property would have to be added to struct block.  Also integral
to this set of changes is the concept of an "entry pc" which might be
different from the block's start address.  An entry_pc field would
also need to be added to struct block.  This does not result in any
space savings in struct block though since the space for the flag and
entry_pc use more space than the blockranges struct pointer that I've
added.  There would, however, be some space savings due to the fact
that the new data structures that I've added for this patch would not
need to be allocated.  (I happen to like the approach I've come up
with, but I wanted to mention another possibility just in case someone
does not.)

gdb/ChangeLog:

	* block.h (blockrange, blockranges): New struct declarations.
	(struct block): Add new field named `ranges'.
	(BLOCK_RANGES, BLOCK_NRANGES, BLOCK_RANGE, BLOCK_CONTIGUOUS_P)
	(BLOCK_RANGE_START, BLOCK_RANGE_END, BLOCK_ENTRY_PC): New
	macros for accessing ranges in struct block.
	(make_blockranges): New declaration.
	block.c (make_blockranges): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid problems with plugins being loaded multiple times.
@ 2018-08-23 18:50 sergiodj+buildbot
  2018-09-07 10:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23 18:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b0ceb98aec8e1ab610deea9fee9ee75c5911bbc0 ***

Author: Zenith423 <zenith432@users.sourceforge.net>
Branch: master
Commit: b0ceb98aec8e1ab610deea9fee9ee75c5911bbc0

Avoid problems with plugins being loaded multiple times.

	PR 23460
	* plugin.c (struct plugin_list_entry): New structure.
	(plugin_list): New variable.
	(try_load_plugin): Place opened plugins on a list.  Ensure that
	the refcount in the dynamic loader is kept at 1.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Darwin: fix bad loop incrementation
@ 2018-08-23 15:47 sergiodj+buildbot
  2018-09-07  7:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23 15:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12a0d0f66172b9504e29000fa4f4e5c34109d6db ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: 12a0d0f66172b9504e29000fa4f4e5c34109d6db

Darwin: fix bad loop incrementation

When reading symbols from the vector of oso files on Mac OS X
Darwin, a previous commit introduce a change in the loop and add
an increment at each loop iteration whereas this incrementation is
not needed since the increment or set of the loop control variable
is already done in the loop.

gdb/ChangeLog:

	* machoread.c (macho_symfile_read_all_oso): Remove uneeded
	incrementation.

Change-Id: I3a5a6deb4e9d834ee7d4217a62d90c2ffb7241bc


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PowerPC64 "call lacks nop"
@ 2018-08-23 15:12 sergiodj+buildbot
  2018-09-06 23:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23 15:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f53ad3cf2b2dc34114a9b74439da5a418ac40e3d ***

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

PowerPC64 "call lacks nop"

The "-fPIC" and "-mcmodel=small" parts of these messages isn't always
true, so lets dispense with that and just report the type of stub
causing trouble.

	* elf64-ppc.c (ppc64_elf_relocate_section): Revise "call lacks
	nop" error message.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Replace unworkable code in HPPA relocs handelr with an assertion.
@ 2018-08-23 12:59 sergiodj+buildbot
  2018-09-06 22:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23 12:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 38cf70ca4d7adaad7ef085ce34e24e1e0bbee945 ***

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

Replace unworkable code in HPPA relocs handelr with an assertion.

	* elf64-hppa.c (elf_hppa_final_link_relocate): Replace unworkable
	code with an assertion.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix "unresolved reloc" error for NOTOC relocs
@ 2018-08-23  4:40 sergiodj+buildbot
  2018-09-06 18:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23  4:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d0abeec8d45514fbec790f27e3cadceb576df9b5 ***

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

Fix "unresolved reloc" error for NOTOC relocs

	* elf64-ppc.c (ppc64_elf_relocate_section): Don't miss clearing
	unresolved_reloc on ppc_stub_plt_call_notoc.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make read_program_headers_from_bfd return a gdb::byte_vector
@ 2018-08-23  4:23 sergiodj+buildbot
  2018-09-06 15:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23  4:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d1012b8e33aaebe988aaf0723d26ddef9e155dbf ***

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

Make read_program_headers_from_bfd return a gdb::byte_vector

This patch makes read_program_headers_from_bfd return a gdb::byte_vector
instead of a plain pointer.

gdb/ChangeLog:

	* solib-svr4.c (read_program_headers_from_bfd): Return
	gdb::optional<gdb::byte_vector>.
	(svr4_exec_displacement): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] bfd/development.sh: Add experimental
@ 2018-08-23  0:28 sergiodj+buildbot
  2018-09-06 14:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-23  0:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9eef0608951ba0e551dd6dd079ce1e20bae11f6b ***

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

bfd/development.sh: Add experimental

Add experimental to indicate whether this is a release branch.

	PR ld/23536
	* development.sh (experimental): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use the correct constants when setting the section type of HPPA unwind sections.
@ 2018-08-22 19:32 sergiodj+buildbot
  2018-09-06 13:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22 19:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f4286c4f7193606fd6200e46b152ff0934f9cc2 ***

Author: Helge Deller <deller@gmx.de>
Branch: master
Commit: 6f4286c4f7193606fd6200e46b152ff0934f9cc2

Use the correct constants when setting the section type of HPPA unwind sections.

	* elf-hppa.h (elf_hppa_fake_sections): Use SHT_PARISC_UNWIND as
	the section type of the .PARISC.unwind section on 64-bit binaries
	and SHT_PROGBITS for 32-bit binaries.  Add a comment about it.
	Add comment about the sh_entsize value.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make read_program_header return a gdb::byte_vector
@ 2018-08-22 18:38 sergiodj+buildbot
  2018-09-06 14:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22 18:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17658d46e48ad4a7f6fb850422639b06c9d963aa ***

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

Make read_program_header return a gdb::byte_vector

While reading a recent patch, I found this spot where a gdb::byte_vector
could be used instead of an allocated buffer returned as a plain
pointer.

gdb/ChangeLog:

	* solib-svr4.c (read_program_header): Return
	gdb::optional<gdb::byte_vector>, remove p_sect_size param.
	(find_program_interpreter): Return
	gdb::optional<gdb::byte_vector>.
	(scan_dyntag_auxv): Adjust.
	(enable_break): Adjust.
	(svr4_exec_displacement): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix restoring of inferior terminal settings
@ 2018-08-22 15:34 sergiodj+buildbot
  2018-09-06 14:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae739fe7b8cffac2332666d62ad37cab679a7758 ***

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

Fix restoring of inferior terminal settings

I noticed that the child_terminal_save_inferior function was not used
since the commit f6ac5f3d63e0 ("Convert struct target_ops to C++").  I
was able to make a little test program to illustrate the problem (see
test case).

I think we're just missing the override of the terminal_save_inferior
method in inf_child_target (along with the other terminal-related
methods).

Instead of creating a new test, I thought that gdb.base/term.exp was a
good candidate for testing that gdb restores properly the inferior's
terminal settings.

gdb/ChangeLog:

	* inf-child.h (inf_child_target) <terminal_save_inferior>: New.
	* inf-child.c (inf_child_target::terminal_save_inferior): New.

gdb/testsuite/ChangeLog:

	* gdb.base/term.exp: Compare terminal settings with values from
	the inferior.
	* gdb.base/term.c: Get and set terminal settings.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Replace xstrvprintf usages with string_vprintf
@ 2018-08-22 15:18 sergiodj+buildbot
  2018-09-06 14:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22 15:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 467dc1e2ea5a8b300b61194aa8565829ce7d65bc ***

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

Replace xstrvprintf usages with string_vprintf

Most usages of xstrvprintf in GDB can be replaced with string_vprintf,
removing some manual memory management.

gdb/ChangeLog:

	* guile/scm-string.c (gdbscm_scm_from_printf): Use
	string_vprintf.
	* guile/scm-utils.c (gdbscm_printf): Likewise.
	* serial.c (serial_printf): Likewise.
	* xml-support.c (gdb_xml_parser::vdebug): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix AArch64 stub layout algorithm to allow for the fact that section layut might change a stub's target location.
@ 2018-08-22  9:30 sergiodj+buildbot
  2018-09-06 13:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22  9:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3da64fe404031c093e8b59565d935fed214e28c1 ***

Author: Rafeal Auler <rafaelauler@gmail.com>
Branch: master
Commit: 3da64fe404031c093e8b59565d935fed214e28c1

Fix AArch64 stub layout algorithm to allow for the fact that section layut might change a stub's target location.

	PR 23560
	* elfnn-aarch64.c (elfNN_aarch64_size_stubs): Always update the
	stub's target, since it may have been changed after the layout.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64 SVE VG is Vector Granule
@ 2018-08-22  8:54 sergiodj+buildbot
  2018-09-06 12:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22  8:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9758a8f84b245f42cfa85be7a65b0728eabca491 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 9758a8f84b245f42cfa85be7a65b0728eabca491

Aarch64 SVE VG is Vector Granule

...not Vector Gradient.

See: DWARF for the ARM 64-bit Architecture (AArch64) with SVE support

gdb/
	* arch/aarch64.h (aarch64_regnum): Update comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add AArch64 SVE to NEWS and GDB manual
@ 2018-08-22  8:32 sergiodj+buildbot
  2018-09-06 12:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22  8:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1461bdac5c1034467d7095b6d109689e02d03987 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 1461bdac5c1034467d7095b6d109689e02d03987

Add AArch64 SVE to NEWS and GDB manual

gdb/
	* NEWS: Add SVE to 8.2 section.

gdb/doc/
	* doc/gdb.texinfo (AArch64 SVE): New subsubsection.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Rename reloc R_S12Z_UKNWN_3 to R_S12Z_EXT18 and implement according to recently inferred information about this reloc.
@ 2018-08-22  6:38 sergiodj+buildbot
  2018-09-06 11:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-22  6:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e57b456393946cb4f90131b78e162cdec903c8a ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 4e57b456393946cb4f90131b78e162cdec903c8a

S12Z: Rename reloc R_S12Z_UKNWN_3 to R_S12Z_EXT18 and implement according to recently inferred information about this reloc.

* bfd/elf32-s12z.c: (opru18_reloc): New function.
* bfd/elf32-s12z.c: (elf_s12z_howto_table): Adjust Howto according to new knowledge.
* include/elf/s12z.h: Rename R_S12Z_UKNWN_3 to R_S12Z_EXT18.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Don't throw Scheme exceptions with live std::vector objects
@ 2018-08-21 21:16 sergiodj+buildbot
  2018-09-06 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-21 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4895f384b47628c8c354dccbb0bfab45b8c33984 ***

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

Don't throw Scheme exceptions with live std::vector objects

A complication with the Guile code is that we have two types of
exceptions to consider: GDB/C++ exceptions, and Guile/SJLJ exceptions.

Because Guile exceptions are SJLJ based, we must make sure to not have
live local variables of types with non-trivial dtors when a Guile
exception is thrown, because the dtors won't be run when a Guile
exceptions is thrown.

gdbscm_parse_function_args currently violates this:

 void
 gdbscm_parse_function_args (const char *func_name,
			     int beginning_arg_pos,
			     const SCM *keywords,
			     const char *format, ...)
 {
 ...
   /* Keep track of malloc'd strings.  We need to free them upon error.  */
   std::vector<char *> allocated_strings;
 ...
   for (char *ptr : allocated_strings)
     xfree (ptr);
   gdbscm_throw (status); /// dtor of "allocated_strings" is not run!
 }

This commit fixes the above making using of gdbscm_wrap.

It would be nice if we had a way to make it impossible to write such
code.  PR guile/23429 has an idea for that, if someone's interested.

gdb/ChangeLog:
2018-08-21  Pedro Alves  <palves@redhat.com>

	* guile/scm-utils.c (gdbscm_parse_function_args_1): New, factored
	out from gdbscm_parse_function_args.
	(gdbscm_parse_function_args): Rework to use gdbscm_wrap and
	gdbscm_parse_function_args_1.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix running objcopy on Mach-O binaries.
@ 2018-08-21 21:01 sergiodj+buildbot
  2018-09-06 11:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-21 21:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae19acf3201ee0b921cde8e70e278fe123e82105 ***

Author: mephi42 <mephi42@gmail.com>
Branch: master
Commit: ae19acf3201ee0b921cde8e70e278fe123e82105

Fix running objcopy on Mach-O binaries.

	PR binutils/23315
	* mach-o.c (bfd_mach_o_mangle_symbols): Update n_type even if
	data is already considered filled.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use operand->extract to provide defaults for optional PowerPC operands
@ 2018-08-21 11:56 sergiodj+buildbot
  2018-09-06  6:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-21 11:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9cf7e5687f823a1009d25cb25ff653ee8372e517 ***

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

Use operand->extract to provide defaults for optional PowerPC operands

Most optional operands to powerpc instructions use a default value of
zero, but there are a few exceptions.  Those have been handled by
PPC_OPERAND_OPTIONAL_VALUE and an entry in the powerpc_operands table
for the default value, smuggled in the shift field.  This patch
changes that to using the operand extract function to provide non-zero
defaults.

I've also moved the code determining whether optional operands are
provided or omitted, to the point the first optional operand is seen,
and allowed for the possibility of optional base register operands
in a future patch.

The patch does change the error you get on invalid assembly like

  ld 3,4

You'll now see "missing operand" rather than
"syntax error; end of line, expected `('".

gas/
	* config/tc-ppc.c (md_assemble): Delay counting of optional
	operands until one is encountered.  Allow for the possibility
	of optional base regs, ie. PPC_OPERAND_PARENS.  Call
	ppc_optional_operand_value with extra args.
include/
	* opcode/ppc.h (struct powerpc_operand): Correct "insert" comment.
	Mention use of "extract" function to provide default value.
	(PPC_OPERAND_OPTIONAL_VALUE): Delete.
	(ppc_optional_operand_value): Rewrite to use extract function.
opcodes/
	* ppc-dis.c (operand_value_powerpc): Init "invalid".
	(skip_optional_operands): Count optional operands, and update
	ppc_optional_operand_value call.
	* ppc-opc.c (extract_dxdn): Remove ATTRIBUTE_UNUSED from used arg.
	(extract_vlensi): Likewise.
	(extract_fxm): Return default value for missing optional operand.
	(extract_ls, extract_raq, extract_tbr): Likewise.
	(insert_sxl, extract_sxl): New functions.
	(insert_esync, extract_esync): Remove Power9 handling and simplify.
	(powerpc_operands <FXM4, TBR>): Delete PPC_OPERAND_OPTIONAL_VALUE
	flag and extra entry.
	(powerpc_operands <SXL>): Likewise, and use insert_sxl and
	extract_sxl.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PowerPC HOWTOs
@ 2018-08-21  7:49 sergiodj+buildbot
  2018-09-06  4:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-21  7:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46807bf45106af5523ad06cf84e7b825dcb9f089 ***

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

PowerPC HOWTOs

These take up far too many lines in the files.  This patch introduces
a replacement for the HOWTO macro that simplifies the relow howto
initialization.  Apart from the two relocs mentioned in the ChangeLog,
no relocation howto is changed.

	* elf64-ppc.c (HOW): Define.
	(ONES): Delete.
	(ppc64_elf_howto_raw): Use HOW to initialize entries.
	* elf32-ppc.c (HOW): Define.
	(ppc_elf_howto_raw): Use HOW to initialize entries, updating
	R_PPC_VLE_REL15 and R_PPC_VLE_REL24 to use bitpos=0.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Delete NEWHOWTO and tidy some uses of reloc_howto_struct
@ 2018-08-21  7:05 sergiodj+buildbot
  2018-09-06  3:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-21  7:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 487096bf0bd5499b1d23ecbe5fd64f9f0079c0b5 ***

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

Delete NEWHOWTO and tidy some uses of reloc_howto_struct

NEWHOWTO was promised way back in 1991 (git commit e5683622186).
I doubt it's ever going to be implemented.  This patch removes it,
and tidies some reloc howtos.  I was going to make some changes to
reloc_howto_struct, so I think it's important that all relocs howtos
are initialized with HOWTO.

	* reloc.c (HOWTO): Revise comment.
	(NEWHOWTO, HOWTO_PREPARE): Delete.
	* coff-arm.c (coff_arm_reloc_type_lookup): Replace const struc
	reloc_howto_struct with reloc_howto_type.
	* ns32knetbsd.c (MY_bfd_reloc_type_lookup): Likewise.
	* vms-alpha.c (alpha_vms_bfd_reloc_type_lookup): Likewise.
	* elf-hppa.h (HOW): Define.
	(elf_hppa_howto_table): Use it to simplify this table, correcting
	name of R_PARISC_LTOFF16WF, R_PARISC_LTOFF_FPTR64, and
	R_PARISC_LTOFF_FPTR16DF.
	* elf32-mep.c (MEPREL): Use HOWTO.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix s12z test regexps
@ 2018-08-21  6:54 sergiodj+buildbot
  2018-09-05 23:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-21  6:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08a8fe2ffd9766877a74a52922b4391d37e85491 ***

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

Fix s12z test regexps

Fixes
ERROR: tcl error sourcing .../gas/testsuite/gas/s12z/s12z.exp.
ERROR: couldn't compile regular expression pattern: quantifier operand invalid

run_dump_test expected output lines are regexps.

	* testsuite/gas/s12z/bit-manip-invalid.d: Correct regexps.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Don't init array at run time
@ 2018-08-20  1:05 sergiodj+buildbot
  2018-09-05 11:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-20  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 865dcc8a4d397e4d9d032785e8ff318e28355d76 ***

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

Don't init array at run time

When it can be done at compile time.

	* mmo.c (valid_mmo_symbol_character_set): Initialize and make
	array const.
	(mmo_init): Don't init valid_mmo_symbol_character_set.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Tidy bit twiddling
@ 2018-08-20  0:54 sergiodj+buildbot
  2018-09-05 11:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-20  0:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d203b41ac79b011d63bc1e2467f9c8a81f468eed ***

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

Tidy bit twiddling

	* sh-opc.h (MASK): Simplify.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Balance parentheses in expression
@ 2018-08-20  0:43 sergiodj+buildbot
  2018-09-05 10:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-20  0:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba1c4c6fee7e8794481412fd8604462f04b2765f ***

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

Balance parentheses in expression

	* rs6000-core.c (CORE_COMMONSZ): Balance parentheses in expression.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix debugging of stripped PIE executables with padded PT_TLS
@ 2018-08-19 15:21 sergiodj+buildbot
  2018-09-05 10:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-19 15:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be2d111a878e1422c921226bc7714131a5c470fa ***

Author: Michael Spang <spang@google.com>
Branch: master
Commit: be2d111a878e1422c921226bc7714131a5c470fa

Fix debugging of stripped PIE executables with padded PT_TLS

Certain PIE executables produced by gold cannot be debugged by gdb after
being stripped. GDB requires program headers of PIE executables to match,
and those checks may fail due to adjustments made during stripping.

One case of this occurs because strip recomputes the memsz of PT_TLS and
does not add alignment, while gold does. This is another variant of PR
11786, so apply the same fix of relaxing the program header matching.

gdb/ChangeLog:

	PR gdb/11786
	* solib-svr4.c (svr4_exec_displacement): Ignore memsz fields
	for PT_TLS segments.

gdb/testsuite/ChangeLog:

	PR gdb/11786
	* gdb.base/gcore-tls-pie.c: New file.
	* gdb.base/gcore-tls-pie.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Test case for DW_OP_GNU_variable_value
@ 2018-08-18 23:19 sergiodj+buildbot
  2018-09-05  8:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-18 23:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d140d1a0be24da37c9103ed6cac98b0017829d9 ***

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

Test case for DW_OP_GNU_variable_value

gdb/testsuite/ChangeLog:

	* gdb.dwarf2/varval.c: New file.
	* gdb.dwarf2/varval.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support of DW_OP_GNU_variable_value to DWARF assembler
@ 2018-08-18 21:56 sergiodj+buildbot
  2018-09-05  8:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-18 21:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ae3a7c47e6a95d69a09838c11f9fd3c9cbb25cb6 ***

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

Add support of DW_OP_GNU_variable_value to DWARF assembler

gdb/testsuite/ChangeLog:

	* lib/dwarf.exp: Add support for DW_OP_GNU_variable_value.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for DW_OP_GNU_variable_value
@ 2018-08-18 20:51 sergiodj+buildbot
  2018-09-05  7:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-18 20:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6b786da4e3353bf634ec7d9c7bffbd7569e73c6 ***

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

Add support for DW_OP_GNU_variable_value

This patch adds support for DW_OP_GNU_variable_value to GDB.

Jakub Jelinek provides a fairly expansive discussion of this DWARF
expression opcode in his GCC patch...

    https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01499.html

It has also been proposed for addition to the DWARF Standard:

    http://www.dwarfstd.org/ShowIssue.php?issue=161109.2

If compiled with a suitable version of GCC, the test case associated
with GCC Bug 77589 uses DW_OP_GNU_variable_value in a DW_AT_byte_stride
expression.  Here's a link to the bug:

    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77589

This is what the DWARF looks like.  Look at the last line, which has
the DW_AT_byte_stride expression:

 <2><e1>: Abbrev Number: 12 (DW_TAG_variable)
    <e2>   DW_AT_name        : (indirect string, offset: 0x115): span.0
    <e6>   DW_AT_type        : <0x2e>
    <ea>   DW_AT_artificial  : 1
    <ea>   DW_AT_location    : 3 byte block: 91 b0 7f 	(DW_OP_fbreg: -80)
 ...
 <2><178>: Abbrev Number: 18 (DW_TAG_subrange_type)
    <179>   DW_AT_lower_bound : 4 byte block: 97 23 20 6 	(DW_OP_push_object_address; DW_OP_plus_uconst: 32; DW_OP_deref)
    <17e>   DW_AT_upper_bound : 4 byte block: 97 23 28 6 	(DW_OP_push_object_address; DW_OP_plus_uconst: 40; DW_OP_deref)
    <183>   DW_AT_byte_stride : 10 byte block: 97 23 18 6 fd e1 0 0 0 1e 	(DW_OP_push_object_address; DW_OP_plus_uconst: 24; DW_OP_deref; DW_OP_GNU_variable_value: <0xe1>; DW_OP_mul)

A patch to readelf, which I'm also submitting, is required to do this
decoding.

I found that GDB gave me the correct answer for "p c40pt(2)" once I
(correctly) implemented DW_OP_GNU_variable_value.

I also have test case (later in this series) which uses the DWARF
assembler and, therefore, do not rely on having a compiler with this
support.

gdb/ChangeLog:

	* dwarf2expr.h (struct dwarf_expr_context): Add virtual method
	dwarf_variable_value.
	* dwarf2-frame.c (class dwarf_expr_executor):
	Add override for dwarf_variable_value.
	* dwarf2loc.c (class dwarf_evaluate_loc_desc): Likewise.
	(class symbol_needs_eval_context): Likewise.
	(indirect_synthetic_pointer): Add forward declaration.
	(sect_variable_value): New function.
	(dwarf2_compile_expr_to_ax): Add case for DW_OP_GNU_variable_value.
	* dwarf2expr.c (dwarf_expr_context::execute_stack_op): Add case
	for DW_OP_GNU_variable_value.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Opcodes: (BRCLR / BRSET) Disassemble reserved codes instead of aborting.
@ 2018-08-18  6:31 sergiodj+buildbot
  2018-09-05  6:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-18  6:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f41078422a4381d4943f36aa1ef95b1d7c85ee7e ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: f41078422a4381d4943f36aa1ef95b1d7c85ee7e

Opcodes: (BRCLR / BRSET) Disassemble reserved codes instead of aborting.

Bit manipulation instructions which are not normally generated by the
assembler, should nevertheless be decoded by the disassembler.

opcodes/
	* s12z-dis.c: BM_RESERVED1 to behave like BM_OPR_REG, and
	BM_RESERVED0 like BM_REG_IMM.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Move opcode header to public include directory.
@ 2018-08-18  6:19 sergiodj+buildbot
  2018-09-05  5:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-18  6:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ba3ba91a3dbc43f7ff16c4899f7f1cbef056db0 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 7ba3ba91a3dbc43f7ff16c4899f7f1cbef056db0

S12Z: Move opcode header to public include directory.

opcodes/
        * s12z.h: Delete.
	* s12z-dis.c: Adjust path of included file.

include/
        * opcode/s12z.h: New file.

gas/
	* config/tc-s12z.c: Adjust path of included file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove "repeat" argument from command_line_input
@ 2018-08-17 23:39 sergiodj+buildbot
  2018-09-05  1:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-17 23:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 89fbedf3abc90b62fbb7f08782ed78d87b3fccaa ***

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

Remove "repeat" argument from command_line_input

After the previous patch, all callers pass 0 as the repeat argument to
command_line_input.  So, this patch removes it.

gdb/ChangeLog
2018-08-16  Tom Tromey  <tom@tromey.com>

	* top.c (read_command_file): Update.
	(command_line_input): Remove "repeat" argument.
	* ada-lang.c (get_selections): Update.
	* linespec.c (decode_line_2): Update.
	* defs.h (command_line_input): Remove argument.
	* cli/cli-script.c (read_next_line): Update.
	* python/py-gdb-readline.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix use-after-free in number_or_range_parser
@ 2018-08-17 23:38 sergiodj+buildbot
  2018-09-05  1:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-17 23:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12582533306990c9406aedd960fa411c317a67de ***

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

Fix use-after-free in number_or_range_parser

-fsanitize=address showed a use-after-free in number_or_range_parser.

The cause was that handle_line_of_input could stash the input into
"saved_command_line", and then this could be freed by reentrant calls.

This fixes the bug by preventing commands that are read by "commands"
from being eligible for repeating.

gdb/ChangeLog
2018-08-17  Tom Tromey  <tom@tromey.com>

	* cli/cli-script.c (read_next_line): Pass 0 as repeat argument to
	command_line_input.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Remove empty X86_FEATURE_1_AND property
@ 2018-08-17 11:11 sergiodj+buildbot
  2018-09-05  1:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-17 11:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfb1e8c15a6b7d02cd0b9a124d01722a07ebf09a ***

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

x86: Remove empty X86_FEATURE_1_AND property

There is no need to generate .note.gnu.property section with empty
X86_FEATURE_1_AND property.  This patch adds fixup_gnu_properties
to ELF linker backend so that x86 backend can remove it.

bfd/

	PR ld/23515
	* elf-bfd.h (elf_backend_data): Add fixup_gnu_properties.
	* elf-properties.c (_bfd_elf_link_setup_gnu_properties): Call
	backend fixup_gnu_properties if it isn't NULL.  Discard
	.note.gnu.property section if all properties have been removed.
	* elfxx-target.h (elf_backend_fixup_gnu_properties): New.
	(elfNN_bed): Initialize fixup_gnu_properties.
	* elfxx-x86.c (_bfd_x86_elf_link_fixup_gnu_properties): New
	function.
	* elfxx-x86.h (_bfd_x86_elf_link_fixup_gnu_properties): New
	prototype.
	(elf_backend_fixup_gnu_properties): New.

ld/

	PR ld/23515
	* testsuite/ld-i386/ibt-plt-2a.d: Updated.
	* testsuite/ld-i386/ibt-plt-2b.d: Likewise.
	* testsuite/ld-x86-64/ibt-plt-2a-x32.d: Likewise.
	* testsuite/ld-x86-64/ibt-plt-2a.d: Likewise.
	* testsuite/ld-x86-64/ibt-plt-2b-x32.d: Likewise.
	* testsuite/ld-x86-64/ibt-plt-2b.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Correct elf64-ppc.c linkage stub comment and formatting fixes
@ 2018-08-16 13:56 sergiodj+buildbot
  2018-09-05  0:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-16 13:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2cdcc33021214e77c2c185aa78ad4f9ae1b9e565 ***

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

Correct elf64-ppc.c linkage stub comment and formatting fixes

ppc_stub_long_branch_notoc will never need more than a 32-bit offset
for the r12 offset since the stub target must be in range of a
branch instruction.

	* elf64-ppc.c: Correct ppc_stub_long_branch_notoc example.
	Formatting.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use pulongest in aarch64-linux-tdep.c
@ 2018-08-15 17:01 sergiodj+buildbot
  2018-09-05  0:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-15 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 495143533ad95369811391c6e3c6dadd69d7dd67 ***

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

Use pulongest in aarch64-linux-tdep.c

While testing a patch on the buildbot, I got this error:

../../binutils-gdb/gdb/aarch64-linux-tdep.c: In function uint64_t aarch64_linux_core_read_vq(gdbarch*, bfd*):
../../binutils-gdb/gdb/aarch64-linux-tdep.c:285:29: error: format %ld expects argument of type long int, but argument 2 has type uint64_t {aka long long unsigned int} [-Werror=format=]

This patch avoids the problem by using pulongest rather than %ld.
This seems safe to me because, if aarch64-linux-tdep.c is included in
the build, then ULONGEST must be a 64-bit type.

gdb/ChangeLog
2018-08-15  Tom Tromey  <tom@tromey.com>

	* aarch64-linux-tdep.c (aarch64_linux_core_read_vq): Use pulongest.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MI: Add -a option to the "-data-disassemble" command
@ 2018-08-14 14:19 sergiodj+buildbot
  2018-09-05  0:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-14 14:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 26fb3983d7062c6f6bc43028ae2074cc29d22c7e ***

Author: Jan Vrany <jan.vrany@fit.cvut.cz>
Branch: master
Commit: 26fb3983d7062c6f6bc43028ae2074cc29d22c7e

MI: Add -a option to the "-data-disassemble" command

The CLI "disassemble" command allows specifying a single address - in
that case the function surrounding that address is disassembled.

This commit adds this feature to the equivalent MI command
"-data-disassemble".

gdb/ChangeLog:
2018-08-14  Jan Vrany  <jan.vrany@fit.cvut.cz>

	* mi/mi-cmd-disas.c (mi_cmd_disassemble): Add -a option.
	If used, use find_pc_partial_function to find address range
	to disassemble.
	* mi/mi-main.c (mi_cmd_list_features): Report
	"data-disassemble-a-option" feature.
	* NEWS: Mention new -data-disassemble option -a.

gdb/doc/ChangeLog:
2018-08-14  Jan Vrany  <jan.vrany@fit.cvut.cz>

	* gdb.texinfo (GDB/MI Data Manipulation): Document
	"-data-disassemble -a addr".
	(GDB/MI Support Commands): Document "data-disassemble-a-option"
	feature.

gdb/testsuite/ChangeLog:
2018-08-14  Jan Vrany  <jan.vrany@fit.cvut.cz>

	* gdb.mi/mi-disassemble.exp (test_disassembly_only): Add tests for
	-data-disassemble -a.
	(test_disassembly_bogus_args): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Define _FORTIFY_SOURCE in common-defs.h
@ 2018-08-13 16:16 sergiodj+buildbot
  2018-09-04 23:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-13 16:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a97b53dda99526d7c2890aeb9637008790cbdfa9 ***

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

Define _FORTIFY_SOURCE in common-defs.h

This defines _FORTIFY_SOURCE in common-defs.h.  This seems like a
sensible safety measure, and also it may help avoid build problems
with -Wunused-result on distros that already define _FORTIFY_SOURCE by
default.

Tested by the buildbot.

gdb/ChangeLog
2018-08-13  Tom Tromey  <tom@tromey.com>

	* common/common-defs.h (_FORTIFY_SOURCE): Define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] bfd: Move elf-properties.lo to BFD32_LIBS
@ 2018-08-13 15:01 sergiodj+buildbot
  2018-09-04 23:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-13 15:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98641896ad52915448c0dd1ab4b4bbe23148a582 ***

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

bfd: Move elf-properties.lo to BFD32_LIBS

commit 6404ab993797d1d6cd3d9e97cc281e3cb6226c12
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Aug 8 21:00:04 2018 -0700

    Convert .note.gnu.property section between ELF32 and ELF64

updated bfd_convert_section_size and bfd_convert_section_contents
in bfd.c to call _bfd_elf_convert_gnu_property_size and
_bfd_elf_convert_gnu_properties, which are defined in elf-properties.c.
It led to

bfd.c:2484: undefined reference to `_bfd_elf_convert_gnu_property_size'

for non-ELF targets.  Since elf-properties.c is a generic implementation
and doesn't reference any ELF specific functions directly, this patch
moves elf-properties.lo BFD32_LIBS.

Tested for many ELF and non-ELF targets.

	PR binutils/23494
	* Makefile.am (BFD32_LIBS): Add elf-properties.lo.
	(BFD32_LIBS_CFILES): Add elf-properties.c.
	(BFD32_BACKENDS): Remove elf-properties.lo.
	(BFD32_BACKENDS_CFILES): Remove elf-properties.c.
	* configure.ac (elf): Remove elf-properties.lo.
	* Makefile.in: Regenerated.
	* configure: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Detect SVE when reading aarch64 core files
@ 2018-08-13 10:33 sergiodj+buildbot
  2018-09-04 23:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-13 10:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7fd65b9dc0a9f132fba362493ec21dadc2994d7 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: b7fd65b9dc0a9f132fba362493ec21dadc2994d7

Detect SVE when reading aarch64 core files

The SVE section in a core file contains a header followed by the registers.
Add defines to easily access the header fields within a buffer.

gdb/
	* aarch64-linux-tdep.c (SVE_HEADER_SIZE_LENGTH): Add define.
	(SVE_HEADER_MAX_SIZE_LENGTH): Likewise.
	(SVE_HEADER_VL_LENGTH): Likewise.
	(SVE_HEADER_MAX_VL_LENGTH): Likewise.
	(SVE_HEADER_FLAGS_LENGTH): Likewise.
	(SVE_HEADER_RESERVED_LENGTH): Likewise.
	(SVE_HEADER_SIZE_OFFSET): Likewise.
	(SVE_HEADER_MAX_SIZE_OFFSET): Likewise.
	(SVE_HEADER_VL_OFFSET): Likewise.
	(SVE_HEADER_MAX_VL_OFFSET): Likewise.
	(SVE_HEADER_FLAGS_OFFSET): Likewise.
	(SVE_HEADER_RESERVED_OFFSET): Likewise.
	(SVE_HEADER_SIZE): Likewise.
	(aarch64_linux_core_read_vq): Add function.
	(aarch64_linux_core_read_description): Check for SVE section.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Split size in regset section iterators
@ 2018-08-13  9:34 sergiodj+buildbot
  2018-09-04 23:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-13  9:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a616bb94509c22c96ae8bf1432ec28a7f3e31778 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: a616bb94509c22c96ae8bf1432ec28a7f3e31778

Split size in regset section iterators

In the existing code, when using the regset section iteration functions, the
size parameter is used in different ways.

With collect, size is used to create the buffer in which to write the regset.
(see linux-tdep.c::linux_collect_regset_section_cb).

With supply, size is used to confirm the existing regset is the correct size.
If REGSET_VARIABLE_SIZE is set then the regset can be bigger than size.
Effectively, size is the minimum possible size of the regset.
(see corelow.c::get_core_register_section).

There are currently no targets with both REGSET_VARIABLE_SIZE and a collect
function.
In SVE, a corefile can contain one of two formats after the header, both of
which are different sizes. However, when writing a core file, we always want
to write out the full bigger size.

To allow support of collects for REGSET_VARIABLE_SIZE we need two sizes.
This is done by adding supply_size and collect_size.

gdb/

	* aarch64-fbsd-tdep.c
	(aarch64_fbsd_iterate_over_regset_sections): Add supply_size and
	collect_size.
	* aarch64-linux-tdep.c
	(aarch64_linux_iterate_over_regset_sections): Likewise.
	* alpha-linux-tdep.c
	(alpha_linux_iterate_over_regset_sections):
	* alpha-nbsd-tdep.c
	(alphanbsd_iterate_over_regset_sections): Likewise.
	* amd64-fbsd-tdep.c
	(amd64fbsd_iterate_over_regset_sections): Likewise.
	* amd64-linux-tdep.c
	(amd64_linux_iterate_over_regset_sections): Likewise.
	* arm-bsd-tdep.c
	(armbsd_iterate_over_regset_sections): Likewise.
	* arm-fbsd-tdep.c
	(arm_fbsd_iterate_over_regset_sections): Likewise.
	* arm-linux-tdep.c
	(arm_linux_iterate_over_regset_sections): Likewise.
	* corelow.c (get_core_registers_cb): Likewise.
	(core_target::fetch_registers): Likewise.
	* fbsd-tdep.c (fbsd_collect_regset_section_cb): Likewise.
	* frv-linux-tdep.c (frv_linux_iterate_over_regset_sections): Likewise.
	* gdbarch.h (void): Regenerate.
	* gdbarch.sh: Add supply_size and collect_size.
	* hppa-linux-tdep.c (hppa_linux_iterate_over_regset_sections): Likewise.
	* hppa-nbsd-tdep.c (hppanbsd_iterate_over_regset_sections): Likewise.
	* hppa-obsd-tdep.c (hppaobsd_iterate_over_regset_sections): Likewise.
	* i386-fbsd-tdep.c (i386fbsd_iterate_over_regset_sections): Likewise.
	* i386-linux-tdep.c (i386_linux_iterate_over_regset_sections): Likewise.
	* i386-tdep.c (i386_iterate_over_regset_sections): Likewise.
	* ia64-linux-tdep.c (ia64_linux_iterate_over_regset_sections): Likewise.
	* linux-tdep.c (linux_collect_regset_section_cb): Likewise.
	* m32r-linux-tdep.c (m32r_linux_iterate_over_regset_sections): Likewise.
	* m68k-bsd-tdep.c (m68kbsd_iterate_over_regset_sections): Likewise.
	* m68k-linux-tdep.c (m68k_linux_iterate_over_regset_sections): Likewise.
	* mips-fbsd-tdep.c (mips_fbsd_iterate_over_regset_sections): Likewise.
	* mips-linux-tdep.c (mips_linux_iterate_over_regset_sections): Likewise.
	* mips-nbsd-tdep.c (mipsnbsd_iterate_over_regset_sections): Likewise.
	* mips64-obsd-tdep.c (mips64obsd_iterate_over_regset_sections): Likewise.
	* mn10300-linux-tdep.c (am33_iterate_over_regset_sections): Likewise.
	* nios2-linux-tdep.c (nios2_iterate_over_regset_sections): Likewise.
	* ppc-fbsd-tdep.c (ppcfbsd_iterate_over_regset_sections): Likewise.
	* ppc-linux-tdep.c (ppc_linux_iterate_over_regset_sections): Likewise.
	* ppc-nbsd-tdep.c (ppcnbsd_iterate_over_regset_sections): Likewise.
	* ppc-obsd-tdep.c (ppcobsd_iterate_over_regset_sections): Likewise.
	* riscv-linux-tdep.c (riscv_linux_iterate_over_regset_sections): Likewise.
	* rs6000-aix-tdep.c (rs6000_aix_iterate_over_regset_sections): Likewise.
	* s390-linux-tdep.c (s390_iterate_over_regset_sections): Likewise.
	* score-tdep.c (score7_linux_iterate_over_regset_sections): Likewise.
	* sh-tdep.c (sh_iterate_over_regset_sections): Likewise.
	* sparc-tdep.c (sparc_iterate_over_regset_sections): Likewise.
	* tilegx-linux-tdep.c (tilegx_iterate_over_regset_sections): Likewise.
	* vax-tdep.c (vax_iterate_over_regset_sections): Likewise.
	* xtensa-tdep.c (xtensa_iterate_over_regset_sections): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Add CpuCMOV and CpuFXSR
@ 2018-08-11 21:54 sergiodj+buildbot
  2018-09-04 19:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-11 21:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d871f3f48388d57721d8077e281041ed16a745cf ***

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

x86: Add CpuCMOV and CpuFXSR

There are separate CPUID feature bits for fxsave/fxrstor and cmovCC
instructions.  This patch adds CpuCMOV and CpuFXSR to replace Cpu686
on corresponding instructions.

gas/

	* config/tc-i386.c (cpu_arch): Add .cmov and .fxsr.
	(cpu_noarch): Add nocmov and nofxsr.
	* doc/c-i386.texi: Document cmov and fxsr.

opcodes/

	* i386-gen.c (cpu_flag_init): Add CpuCMOV and CpuFXSR to
	CPU_I686_FLAGS.  Add CPU_CMOV_FLAGS, CPU_FXSR_FLAGS,
	CPU_ANY_CMOV_FLAGS and CPU_ANY_FXSR_FLAGS.
	(cpu_flags): Add CpuCMOV and CpuFXSR.
	* i386-opc.tbl: Replace Cpu686 with CpuFXSR on fxsave, fxsave64,
	fxrstor and fxrstor64.  Replace Cpu686 with CpuCMOV on cmovCC.
	* i386-init.h: Regenerated.
	* i386-tbl.h: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Factor out common relocation processing
@ 2018-08-11  9:28 sergiodj+buildbot
  2018-09-04 18:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-11  9:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1dc9e2d63e37839ff1768346b2e3f52e338baba5 ***

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

Factor out common relocation processing

This patch factors out some code common to both bfd_perform_relocation
and bfd_install_relocation, in the process fixing the omission of
"case -1" in bfd_install_relocation.

	* reloc.c (bfd_get_reloc_size): Sort switch.
	(read_reloc, write_reloc, apply_reloc): New functions.
	(bfd_perform_relocation, bfd_install_relocation): Use apply_reloc.
	(_bfd_relocate_contents): Use read_reloc and write_reloc.
	(_bfd_clear_contents): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix forgotten xstrprintf -> string_printf change
@ 2018-08-10 22:34 sergiodj+buildbot
  2018-09-04 18:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9925d4f9982ad897bc85f98076e5924e70232b1 ***

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

Fix forgotten xstrprintf -> string_printf change

The patch

  528e157 ("Replace some uses of xstrprintf with string_printf")

forgot to actually change an xstrprintf call to string_printf, this one
fixes it.

gdb/ChangeLog:

	* nat/linux-osdata.c (commandline_from_pid): Replace xstrprintf
	with string_printf.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move C-related declarations to compile-c.h
@ 2018-08-10 20:40 sergiodj+buildbot
  2018-09-04 18:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10 20:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7dc48b4a8006abb552c5e7d22f9841c86f2537d ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: b7dc48b4a8006abb552c5e7d22f9841c86f2537d

Move C-related declarations to compile-c.h

This patch simply moves a bunch of C language-related declarations from
the various compile header files into a new C-specific header, compile-c.h.

gdb/ChangeLog:
        * Makefile.in (SUBDIR_GCC_COMPILE_SRCS): Move header files ...
        (HFILES_NO_SRCDIR): ... to here.
        Add compile-internal.h and compile-c.h.
        * compile/compile-c-support.c: Include compile-c.h.
        * compile/compile-c-symbols.c: Include compile-c.h.
        (generate_c_for_variable_locations): Update comment.
        * compile/compile-c-types.c: Include compile-c.h.
        * compile/compile-c.h: New file -- moved C language declarations
        from other files here.
        * compile/compile-internal.h: Do not include hashtab.h or
        common/enum-flags.h.
        (gcc_qualifiers_flags, struct compile_c_instance, C_CTX)
        (gcc_convert_symbol, gcc_symbol_address)
        (generate_c_for_variable_locations, c_get_mode_for_size)
        (c_get_range_decl_name): Definitions moved to compile-c.h.
        * compile/compile-loc2c.c: Include compile-c.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Always clear h->verinfo.verdef when overriding a dynamic definition
@ 2018-08-10 20:17 sergiodj+buildbot
  2018-09-04 18:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10 20:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 48e30f5238c70e738f44474d595c476ef4e4ec38 ***

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

Always clear h->verinfo.verdef when overriding a dynamic definition

When linker defines a symbol to override a dynamic definition, it should
always clear h->verinfo.verdef so that the symbol won't be associated
with the version information from the dynamic object.  This happened to
the symbol "_edata" when creating an unversioned dynamic object linking
against:

1. libKF5ConfigCore.so.5.49.0
2. libKF5CoreAddons.so.5.49.0
3. libKF5I18n.so.5.49.0
4. libKF5DBusAddons.so.5.49.0
5. libQt5Xml.so.5.11.1
6. libQt5DBus.so.5.11.1
7. libQt5Core.so.5.11.1

Among them

libQt5Xml.so.5.11.1
   299: 000000000003e000     0 NOTYPE  GLOBAL DEFAULT   18 _edata@@Qt_5
libQt5DBus.so.5.11.1
   597: 0000000000092018     0 NOTYPE  GLOBAL DEFAULT   18 _edata@@Qt_5
libQt5Core.so.5.11.1
  2292: 00000000004df640     0 NOTYPE  GLOBAL DEFAULT   21 _edata@Qt_5
  2293: 00000000004df640     0 NOTYPE  GLOBAL DEFAULT   21 _edata@Qt_5

The problem is triggered by 2 duplicated entries of _edata@Qt_5 in
libQt5Core.so.5.11.1 which was created by gold.  Before this commit,
ld created the dynamic object with "_edata" in its dynamic symbol table
which was linker defined and associated with the version information
from libQt5Core.so.5.11.1.  The code in question was there when the
binutils source was imported to sourceware.org.  When such a dynamic
object was used later, we got:

/usr/bin/ld: bin/libKF5Service.so.5.49.0: _edata: invalid version 21 (max 0)
/usr/bin/ld: bin/libKF5Service.so.5.49.0: error adding symbols: bad value

Tested with many ELF targets.

	PR ld/23499
	* elflink.c (bfd_elf_record_link_assignment): Always clear
	h->verinfo.verdef when overriding a dynamic definition.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use policies for code generation
@ 2018-08-10 20:03 sergiodj+buildbot
  2018-09-04 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10 20:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad3a68e9b9b01fbdc09854fb7fd655db652c482f ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: ad3a68e9b9b01fbdc09854fb7fd655db652c482f

Use policies for code generation

This patch changes code generation procedures add_code_header,
add_code_footer, and several other language-specific code generation
functions into policies.

gdb/ChangeLog:
        * compile/compile-c-support.c (add_code_header, add_code_footer):
        Move into policy class.
        (c_push_user_expression, pop_user_expression_nop)
        (c_add_code_header, c_add_code_footer, c_add_input): New policy class.
        (compile_program): New host class.
        (c_compile_program): New typedef.
        (c_compute_porgram): Use c_compile_program.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Rename symbol_substitution_name
@ 2018-08-10 18:47 sergiodj+buildbot
  2018-09-04 18:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f36b6d29fdff5be77ec6dfdac693d5e4b5dee50 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 6f36b6d29fdff5be77ec6dfdac693d5e4b5dee50

Rename symbol_substitution_name

This patch simply adds a "c_" prefix to symbol_substitution_name to clarify
that this is a C language-related function.

gdb/ChangeLog:
        * compile/compile-c-symbols.c (symbol_substitution_name): Rename to ...
        (c_symbol_substitution_name): ... this.
        Update all callers.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return unique_xmalloc_ptr for generate_c_for_variable_locations
@ 2018-08-10 18:34 sergiodj+buildbot
  2018-09-04 17:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10 18:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd923e510884a92514a4f9d90d79592d248d5d92 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: bd923e510884a92514a4f9d90d79592d248d5d92

Return unique_xmalloc_ptr for generate_c_for_variable_locations

This patch eliminates two cleanups in compile/ by changing
generate_c_for_variable_locations so that it returns a unique_ptr.

gdb/ChangeLog:
        * compile/compile-c-support.c (c_compute_program): Use
        unique_xmalloc_ptr to eliminate cleanup.
        * compile/compile-c-symbols.c (generate_c_for_variable_locations):
        Return a unique_xmalloc_ptr and eliminate cleanup.
        * compile/compile-internal.h (generate_c_for_variable_locations):
        Return unique_xmalloc_ptr and update description.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Rename size in get_core_register_section
@ 2018-08-10  9:48 sergiodj+buildbot
  2018-09-04 17:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-10  9:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dbd534fee4a3d6479e4a84f0cd79bd188d94f4d0 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: dbd534fee4a3d6479e4a84f0cd79bd188d94f4d0

Rename size in get_core_register_section

Make it clearer that the size field indicates the size of the section.

gdb/

	* corelow.c (core_target::get_core_register_section): Rename
	min_size to section_min_size.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add configure support for riscv*-linux*.
@ 2018-08-09 21:16 sergiodj+buildbot
  2018-09-04 17:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-09 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52a187f8e78eeaefa38bdaff04aae1fd9a69d788 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 52a187f8e78eeaefa38bdaff04aae1fd9a69d788

RISC-V: Add configure support for riscv*-linux*.

This adds the target and native configure support, and the NEWS entries for
the new target and native configurations.

	gdb/
	* Makefile.in (ALL_TARGET_OBS): Add riscv-linux-tdep.c.
	(ALLDEPFILES): Add riscv-linux-nat.c, and riscv-linux-tdep.c.
	* NEWS: Mention new GNU/Linux RISC-V target.
	* configure.host: Add riscv*-*-linux*.
	* configure.nat: Add riscv*.
	* configure.tgt: Add riscv*-*-linux*.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add native linux support.
@ 2018-08-09 21:02 sergiodj+buildbot
  2018-09-04 17:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-09 21:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c77f97eb0825f5808f4a3a01aa5cc2fcffd5ed4 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 3c77f97eb0825f5808f4a3a01aa5cc2fcffd5ed4

RISC-V: Add native linux support.

Add initial native support for riscv*-linux*.

	gdb/
	* riscv-linux-nat.c: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Minor formatting fixes in riscv-tdep.h
@ 2018-08-09 17:57 sergiodj+buildbot
  2018-09-04 17:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-09 17:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06ab921988f5dfd64630a0b92d05dd94792e0a08 ***

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

Minor formatting fixes in riscv-tdep.h

This fixes some minor formatting issues in riscv-tdep.h, including one
pointed out by ARI.

ChangeLog
2018-08-09  Tom Tromey  <tom@tromey.com>

	* riscv-tdep.h: Minor formatting fixes.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Check element of optimised out vla exists
@ 2018-08-09 16:46 sergiodj+buildbot
  2018-09-04 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-09 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ff2bbae198cbd615885f26aa7d065b8cec8c278 ***

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

gdb: Check element of optimised out vla exists

If a vla is not in memory, and the upper bound is not defined, then we
can't know that an array element exists or not, and we should not try
to access the array element.  One case where this happens is for
arrays that have been optimised out, the array will then have
VALUE_LVAL of not_lval, and an undefined upper bound, if we then try
to access an element of this array we will index into random GDB
memory.

An argument could be made that even for arrays that are in inferior
memory, if the upper bound is not defined then we should not try to
access the array element, however, in some of the Fortran tests, it
seems as though we do rely indexing from a base address into an array
which has no bounds defined.  In this case GDBs standard protection
for detecting unreadable target memory prevents bad thing happening.

gdb/ChangeLog:

	* valarith.c (value_subscripted_rvalue): If an array is not in
	memory, and we don't know the upper bound, then we can't know that
	the requested element exists or not.

gdb/testsuite/ChangeLog:

	* gdb.base/vla-optimized-out.exp: Add new test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Merge similar tests into a single test script
@ 2018-08-09 16:34 sergiodj+buildbot
  2018-09-04 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-09 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5bbcd0f04911d671d0c43d57df9886c06018705 ***

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

gdb: Merge similar tests into a single test script

The three test scripts:

  gdb/testsuite/gdb.base/vla-optimized-out.exp
  gdb/testsuite/gdb.base/vla-optimized-out-o3.exp
  gdb/testsuite/gdb.base/vla-optimized-out-o3-strict.exp

are all pretty similar, with differences in the compile flags used,
and some of the expected results.

Instead of maintaining 3 files, merge them into a single test script,
and use parameters to control the test behaviour.

gdb/testsuite/ChangeLog:

	* gdb.base/vla-optimized-out-o3.exp: Delete.
	* gdb.base/vla-optimized-out-o3-strict.exp: Delete.
	* gdb.base/vla-optimized-out.exp: Extend to cover all of the
	deleted tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Convert .note.gnu.property section between ELF32 and ELF64
@ 2018-08-09  4:31 sergiodj+buildbot
  2018-09-04 16:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-09  4:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6404ab993797d1d6cd3d9e97cc281e3cb6226c12 ***

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

Convert .note.gnu.property section between ELF32 and ELF64

.note.gnu.property section has different alignments and section
sizes for 32-bit and 64-bit ELF binaries.  This patch updated
bfd_convert_section_size and bfd_convert_section_contents to
properly convert .note.gnu.property section between 32-bit and
64-bit ELF binaries.

bfd/

	PR binutils/23494
	* bfd.c (bfd_convert_section_size): Check BFD_DECOMPRESS after
	calling _bfd_elf_convert_gnu_property_size to convert
	.note.gnu.property section size.
	(bfd_convert_section_contents): Check BFD_DECOMPRESS after
	calling _bfd_elf_convert_gnu_properties to convert
	.note.gnu.property section.
	* elf-bfd.h (_bfd_elf_convert_gnu_property_size): New prototype.
	(_bfd_elf_convert_gnu_properties): Likewise.
	* elf-properties.c (elf_get_gnu_property_section_size): New
	function.
	(elf_write_gnu_properties): Likewise.
	(_bfd_elf_convert_gnu_property_size): Likewise.
	(_bfd_elf_convert_gnu_properties): Likewise.
	(_bfd_elf_link_setup_gnu_properties): Use
	elf_get_gnu_property_section_size and elf_write_gnu_properties.

binutils/

	PR binutils/23494
	* testsuite/binutils-all/x86-64/pr23494a-x32.d: New file.
	* testsuite/binutils-all/x86-64/pr23494a.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494a.s: Likewise.
	* testsuite/binutils-all/x86-64/pr23494b-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494b.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494b.s: Likewise.
	* testsuite/binutils-all/x86-64/pr23494c-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494c.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494d-x32.d: Likewise.
	* testsuite/binutils-all/x86-64/pr23494d.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix some comments in target.c
@ 2018-08-08 22:27 sergiodj+buildbot
  2018-09-04 16:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08 22:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fdbac7d8d1c9403a857db6e0c1dc92ce7bb65925 ***

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

Fix some comments in target.c

Fix a typo and add a missing one.

gdb/ChangeLog:

	* target.c (str_comma_list_concat_elem): Fix typo in comment.
	(target_options_to_string): Add comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add software single step support.
@ 2018-08-08 18:24 sergiodj+buildbot
  2018-09-04 16:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08 18:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c720ed8861b461193a507e61e3665b1cc840055 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 5c720ed8861b461193a507e61e3665b1cc840055

RISC-V: Add software single step support.

This adds software single step support that is needed by the linux native port.
This is modeled after equivalent code in the MIPS port.

This also fixes a few bugs in the compressed instruction decode support.  Some
instructions are RV32/RV64 specific, and this wasn't being checked.  Also, a
few instructions were accidentally using the non-compressed is_* function.

This has been tested on a HiFive Unleashed running Fedora, by putting a
breakpoint on start, typing stepi, and then holding down the return key until
it finishes, and observing that I see everything I expect to see along the way.
There is a problem in _dl_addr where I get into an infinite loop, but it seems
to be some synchronization code that doesn't agree with single step, so I have
to find the end of the loop, put a breakpoint there, continue, and then single
step again until the end.

	gdb/
	* riscv-tdep.c (enum opcode): Add jump, branch, lr, and sc opcodes.
	(decode_register_index_short): New.
	(decode_j_type_insn, decode_cj_type_insn): New.
	(decode_b_type_insn, decode_cb_type_insn): New.
	(riscv_insn::decode): Add support for jumps, branches, lr, and sc.  New
	local xlen.  Check xlen when decoding ambiguous compressed insns.  In
	compressed decode, use is_c_lui_insn instead of is_lui_insn, and
	is_c_sw_insn instead of is_sw_insn.
	(riscv_next_pc, riscv_next_pc_atomic_sequence): New.
	(riscv_software_single_step): New.
	* riscv-tdep.h (riscv_software_single_step): Declare.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Make riscv_isa_xlen a global function.
@ 2018-08-08 18:11 sergiodj+buildbot
  2018-09-04 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08 18:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 411baa470ef354e50b488c0c736ac7af8d856ded ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 411baa470ef354e50b488c0c736ac7af8d856ded

RISC-V: Make riscv_isa_xlen a global function.

This allows the function to be used from riscv OS files, which also need to
depend on XLEN size.

	gdb/
	* riscv-tdep.c (riscv_isa_xlen): Drop static.
	* riscv-tdep.h (riscv_isa_xlen): Add extern declaration.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Properly merge GNU_PROPERTY_X86_ISA_1_USED
@ 2018-08-08 13:26 sergiodj+buildbot
  2018-09-04 15:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08 13:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7309df20c4e787041cedc4a6aced89c15259e54 ***

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

x86: Properly merge GNU_PROPERTY_X86_ISA_1_USED

Without the GNU_PROPERTY_X86_ISA_1_USED property, all ISAs may be used.
If a bit in the GNU_PROPERTY_X86_ISA_1_USED property is unset, the
corresponding x86 instruction set isnt used.  When merging properties
from 2 input files and one input file doesn't have the
GNU_PROPERTY_X86_ISA_1_USED property, the output file shouldn't have
it neither.  This patch removes the GNU_PROPERTY_X86_ISA_1_USED
property if an input file doesn't have it.

This patch replaces the GNU_PROPERTY_X86_ISA_1_USED property with the
GNU_PROPERTY_X86_ISA_1_NEEDED property which is the minimum ISA
requirement.

bfd/

	PR ld/23486
	* elfxx-x86.c (_bfd_x86_elf_merge_gnu_properties): Remove
	GNU_PROPERTY_X86_ISA_1_USED if an input file doesn't have it.
	(_bfd_x86_elf_link_setup_gnu_properties): Adding the
	GNU_PROPERTY_X86_ISA_1_NEEDED, instead of
	GNU_PROPERTY_X86_ISA_1_USED, property.

ld/

	PR ld/23486
	* testsuite/ld-i386/i386.exp: Run PR ld/23486 tests.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-i386/pr23486a.d: New file.
	* testsuite/ld-i386/pr23486b.d: Likewise.
	* testsuite/ld-x86-64/pr23486a-x32.d: Likewise.
	* testsuite/ld-x86-64/pr23486a.d: Likewise.
	* testsuite/ld-x86-64/pr23486a.s: Likewise.
	* testsuite/ld-x86-64/pr23486b-x32.d: Likewise.
	* testsuite/ld-x86-64/pr23486b.d: Likewise.
	* testsuite/ld-x86-64/pr23486b.s: Likewise.
	* testsuite/ld-i386/property-3.r: Remove "x86 ISA used".
	* testsuite/ld-i386/property-4.r: Likewise.
	* testsuite/ld-i386/property-5.r: Likewise.
	* testsuite/ld-i386/property-x86-ibt3a.d: Likewise.
	* testsuite/ld-i386/property-x86-ibt3b.d: Likewise.
	* testsuite/ld-i386/property-x86-shstk3a.d: Likewise.
	* testsuite/ld-i386/property-x86-shstk3b.d: Likewise.
	* testsuite/ld-x86-64/property-3.r: Likewise.
	* testsuite/ld-x86-64/property-4.r: Likewise.
	* testsuite/ld-x86-64/property-5.r: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3a-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3a.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3b-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-ibt3b.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3a-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3a.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3b-x32.d: Likewise.
	* testsuite/ld-x86-64/property-x86-shstk3b.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Fix assert for extended-remote target (PR gdb/18050)
@ 2018-08-08 12:34 sergiodj+buildbot
  2018-09-04 15:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08 12:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d4a934ce604afea155c39f06834cdbc47e92a6e ***

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

gdb: Fix assert for extended-remote target (PR gdb/18050)

Consider the following GDB session:

   (gdb) target extended-remote :2347
   (gdb) file /path/to/exe
   (gdb) set remote exec-file /path/to/exe
   (gdb) set detach-on-fork off
   (gdb) break breakpt
   (gdb) run
   # ... hits breakpoint
   (gdb) info inferiors
     Num  Description       Executable
   * 1    process 17001     /path/to/exe
     2    process 17002     /path/to/exe
   (gdb) kill
   (gdb) info inferiors
     Num  Description       Executable
   * 1    <null>            /path/to/exe
     2    process 17002     /path/to/exe
   (gdb) target extended-remote :2348
   ../../src/gdb/thread.c:660: internal-error: thread_info* any_thread_of_process(int): Assertion `pid != 0' failed.
   A problem internal to GDB has been detected,
   further debugging may prove unreliable.

Or, from bug PR gdb/18050:

   (gdb) start
   (gdb) add-inferior -exec /path/to/exe
   (gdb) target extended-remote :2347
   ../../src/gdb/thread.c:660: internal-error: thread_info* any_thread_of_process(int): Assertion `pid != 0' failed.
   A problem internal to GDB has been detected,
   further debugging may prove unreliable.

The issue is calling target.c:dispose_inferior with a killed inferior in
the inferior list.  This assertion is fixed in this commit.

The new test for this issue only runs on platforms that support
'detach-on-fork', and when using
'--target_board=native-extended-gdbserver'.

gdb/ChangeLog:

	PR gdb/18050:
	* target.c (dispose_inferior): Don't dispose of inferiors that are
	already killed.

gdb/testsuite/ChangeLog:

	PR gdb/18050:
	* gdb.server/extended-remote-restart.c: New file.
	* gdb.server/extended-remote-restart.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make target_options_to_string return an std::string
@ 2018-08-08  8:34 sergiodj+buildbot
  2018-09-04 14:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08  8:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09ce46f230fee766c386384cd1f5672d12fde276 ***

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

Make target_options_to_string return an std::string

Return an std::string instead of a char *, saving some manual freeing.

I only manually tested with "set debug target 1" and "set debug lin-lwp
1", since this only deals with debug output.

gdb/ChangeLog:

	* target.h (target_options_to_string): Return an std::string.
	* target.c (str_comma_list_concat_elem): Return void, use
	std::string.
	(do_option): Likewise.
	(target_options_to_string): Return an std::string.
	* linux-nat.c (linux_nat_target::wait): Adjust.
	* target-debug.h (target_debug_print_options): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix gdb.fortran/nested-funcs.exp failure
@ 2018-08-08  3:19 sergiodj+buildbot
  2018-09-04 15:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08  3:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 045cf012860ed0fd6c01892505cab747ee27a21d ***

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

Fix gdb.fortran/nested-funcs.exp failure

Commit 87d6a7aa931f ("Add DWARF index cache") broke
gdb.fortran/nested-funcs.exp.  Because of the new "set index-cache"
command, the expression "set index = 42" now fails:

  set index = 42
  Undefined set index-cache command: "= 42".  Try "help set index-cache".
  (gdb) PASS: gdb.fortran/nested-funcs.exp: set index = 42

Fix it by changing it to "set variable index = 42".  Also, use
gdb_test_no_output to confirm that it worked (since that particular test
wrongfully passed).

gdb/testsuite/ChangeLog:

	* gdb.fortran/nested-funcs.exp: Replace "set index = 42" with
	"set variable index = 42".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Introduce mmap_file function
@ 2018-08-08  2:01 sergiodj+buildbot
  2018-09-04 11:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-08  2:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c831bb1eb6b22cd1705b98188b7d1b0633e7c54 ***

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

Introduce mmap_file function

New in v2:

- As Tom pointed out, we don't need to keep the fd around after
  mmapping.  This simplifies things quite a bit, since we don't need a
  new class.  It's now just a function that returns a scoped_mmap.

We already have scoped_mmap, which is a thin RAII layer over mmap.  If
one simply wants to mmap an entire file for reading, it takes a bit of
boilerplate.  This patch introduces the mmap_file function to make this
easier.

gdb/ChangeLog:

	* Makefile.in (COMMON_SFILES): Add common/scoped_mmap.c.
	* common/scoped_mmap.c: New file.
	* common/scoped_mmap.h (destroy): New method.
	(~scoped_mmap, reset): Use destroy.
	(scoped_mmap): New move constructor.
	(mmap_file): New declaration.
	* unittests/scoped_mmap-selftests.c (test_normal,
	test_invalid_filename, run_tests): New functions.
	(_initialize_scoped_mmap_selftests): Register selftest.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allow CPPFLAGS to be set on the make command line
@ 2018-08-07 23:53 sergiodj+buildbot
  2018-09-04 14:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07 23:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9c61296405d4299b7000e445a6e07c0232bb0342 ***

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

Allow CPPFLAGS to be set on the make command line

While looking into PR build/8751 (which seems to be fixed), I noticed
that it's not possible to change CPPFLAGS for gdb on the "make"
command line.  It's reasonable to want to do this sometimes, and I
think this patch should suffice.

gdb/ChangeLog
2018-08-07  Tom Tromey  <tom@tromey.com>

	* Makefile.in (CPPFLAGS): New variable.
	(INTERNAL_CPPFLAGS): Use it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add doc and news for DWARF index cache
@ 2018-08-07 23:40 sergiodj+buildbot
  2018-09-04 14:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07 23:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7d11235d04ded4832430cd40013ca785a3896e4d ***

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

Add doc and news for DWARF index cache

New in v3:

- Address Eli's comments.

This patch adds doc and news for the feature introduced by the previous
patch.

gdb/ChangeLog:

	* NEWS: Mention the index cache.

gdb/doc/ChangeLog:

	* gdb.texinfo (Index Files Speed Up GDB): Add section about
	symbol index cache.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add DWARF index cache
@ 2018-08-07 23:28 sergiodj+buildbot
  2018-09-04 14:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07 23:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87d6a7aa931f2bd4cfe784344b6a2cd595f6f2c9 ***

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

Add DWARF index cache

New in v3:

- Remove things related to the dwarf-5 format.
- Fix compilation on mingw (scoped_mmap.c).

GDB can generate indexes for DWARF debug information, which, when
integrated in the original binary, can speed up loading object files.
This can be done using the gdb-add-index script or directly by the
linker itself.  However, not many people know about this.  And even
among those who do, because it requires additional steps, I don't know a
lot of people who actually go through that trouble.

To help make using the DWARF index more transparent, this patch
introduces a DWARF index cache.  When enabled, loading an index-less
binary in GDB will automatically save an index file in ~/.cache/gdb.
When loading that same object file again, the index file will be looked
up and used to load the DWARF index.  You therefore get the benefit of
the DWARF index without having to do additional manual steps or
modifying your build system.  When an index section is already present
in the file, GDB will prefer that one over looking up the cache.

When doing my edit-compile-debug cycle, I often debug multiple times the
same build, so the cache helps reducing the load time of the debug
sessions after the first one.

- The saved index file is exactly the same as the output of the "save
  gdb-index" command.  It is therefore the exact same content that would
  be found in the .gdb_index or .debug_names section.  We just leave it
  as a standalone file instead of merging it in the binary.

- The cache is just a directory with files named after the object
  file's build-id.  It is not possible to save/load the index for an
  object file without build-id in the cache.

- The cache uses the gdb index format.  The problem with the dwarf-5
  format is that we can generate an addendum to the .debug_str section
  that you're supposed to integrate to the original binary.  This
  complicates a little bit loading the data from the cached index files,
  so I would leave this for later.

- The size taken up by ~/.cache/gdb is not limited.  I was thinking we
  could add configurable limit (like ccache does), but that would come
  after.  Also, maybe a command to flush the cache.

- The cache is disabled by default.  I think once it's been out there
  and tested for a while, it could be turned on by default, so that
  everybody can enjoy it.

- The code was made to follow the XDG specification: if the
  XDG_CACHE_HOME environment variable, it is used, otherwise it falls
  back to ~/.cache/gdb.  It is possible to change it using "set
  index-cache directory".  On other OSes than GNU/Linux, ~/.cache may
  not be the best place to put such data.  On macOS it should probably
  default to ~/Library/Caches/...  On Windows, %LocalAppData%/...  I
  don't intend to do this part, but further patches are welcome.

- I think that we need to be careful that multiple instances of GDB
  don't interfere with each other (not far fetched at all if you run GDB
  in some automated script) and the cache is always coherent (either the
  file is not found, or it is found and entirely valid).  Writing the
  file directly to its final location seems like a recipe for failure.
  One GDB could read a file in the index while it is being written by
  another GDB.  To mitigate this, I made write_psymtabs_to_index write
  to temporary files and rename them once it's done.  Two GDB instances
  writing the index for the same file should not step on each other's
  toes (the last file to be renamed will stay).  A GDB looking up a file
  will only see a complete file or no file.  Also, if GDB crashes while
  generating the index file, it will leave a work-in-progress file, but
  it won't be picked up by other instances looking up in the cache.

gdb/ChangeLog:

	* common/pathstuff.h (get_standard_cache_dir): New.
	* common/pathstuff.c (get_standard_cache_dir): New.
	* build-id.h (build_id_to_string): New.
	* dwarf-index-common.h (INDEX4_SUFFIX, INDEX5_SUFFIX,
	DEBUG_STR_SUFFIX): Move to here.
	* dwarf-index-write.c (INDEX4_SUFFIX, INDEX5_SUFFIX,
	DEBUG_STR_SUFFIX): Move from there.
	(write_psymtabs_to_index): Make non-static, add basename
	parameter.  Write to temporary files, rename when done.
	(save_gdb_index_command): Adjust call to
	write_psymtabs_to_index.
	* dwarf2read.h (dwarf2_per_objfile) <index_cache_res>: New
	field.
	* dwarf2read.c (dwz_file) <index_cache_res>: New field.
	(get_gdb_index_contents_from_cache): New.
	(get_gdb_index_contents_from_cache_dwz): New.
	(dwarf2_initialize_objfile): Read index from cache.
	(dwarf2_build_psymtabs): Save to index.
	* dwarf-index-cache.h: New file.
	* dwarf-index-cache.c: New file.
	* dwarf-index-write.h: New file.

gdb/testsuite/ChangeLog:

	* boards/index-cache-gdb.exp: New file.
	* gdb.dwarf2/index-cache.exp: New file.
	* gdb.dwarf2/index-cache.c: New file.
	* gdb.base/maint.exp: Check if we are using the index cache.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Import gnulib's mkdir module
@ 2018-08-07 23:03 sergiodj+buildbot
  2018-09-04 12:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07 23:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a99096f31142d7a58962066c801a35b4c5c8bfa ***

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

Import gnulib's mkdir module

The following patch makes use of the mkdir function.  Import the mkdir
gnulib module to ensure proper operation on all platforms.

gdb/ChangeLog:

	* gnulib/aclocal.m4: Re-generate.
	* gnulib/config.in: Re-generate.
	* gnulib/configure: Re-generate.
	* gnulib/import/Makefile.am: Re-generate.
	* gnulib/import/Makefile.in: Re-generate.
	* gnulib/import/m4/gnulib-cache.m4: Re-generate.
	* gnulib/import/m4/gnulib-comp.m4: Re-generate.
	* gnulib/import/m4/mkdir.m4: New file.
	* gnulib/import/mkdir.c: New file.
	* gnulib/update-gnulib.sh (IMPORTED_GNULIB_MODULES): Add mkdir
	module.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PowerPC64 EH info for _notoc linkage stubs
@ 2018-08-07  9:57 sergiodj+buildbot
  2018-09-04 11:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT df136d64fa2fd23052d7a5fcb7059c29d8e6385d ***

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

PowerPC64 EH info for _notoc linkage stubs

This patch generates EH info for the new _notoc linkage stubs, to
support unwinding from asynchronous signal handlers.  Unwinding
through the __tls_get_addr_opt stub was already supported, but that
was just a single stub.  With multiple stubs the EH opcodes need to be
emitted and sized when iterating over stubs, so this is done when
emitting and sizing the stub code.  Emitting the CIEs and FDEs is done
when sizing the stubs, as we did before in order to have the linker
generated FDEs indexed in .eh_frame_hdr.  I moved the final tweaks to
FDEs from ppc64_elf_finish_dynamic_sections to ppc64_elf_build_stubs
simply because it's tidier to be done with them at that point.

bfd/
	* elf64-ppc.c (struct map_stub): Delete tls_get_addr_opt_bctrl.
	Add lr_restore, eh_size and eh_base.
	(eh_advance, eh_advance_size): New functions.
	(build_tls_get_addr_stub): Emit EH info for stub.
	(ppc_build_one_stub): Likewise for _notoc stubs.
	(ppc_size_one_stub): Size EH info for stub.
	(group_sections): Init new map_stub fields.
	(stub_eh_frame_size): Delete.
	(ppc64_elf_size_stubs): Size EH info for stubs.  Set up dummy EH
	program for stubs.
	(ppc64_elf_build_stubs): Reinit new map_stub fields.  Set FDE
	offset to stub section here..
	(ppc64_elf_finish_dynamic_sections): ..rather than here.
ld/
	* testsuite/ld-powerpc/notoc.s: Generate some cfi.
	* testsuite/ld-powerpc/notoc.d: Adjust.
	* testsuite/ld-powerpc/notoc.wf: New file.
	* testsuite/ld-powerpc/powerpc.exp: Run "ext" and "notoc" tests
	as run_ld_link_tests rather than run_dump_test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] __tls_get_addr_opt stubs and tocsave optimization
@ 2018-08-07  9:44 sergiodj+buildbot
  2018-09-04 11:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07  9:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e81b4c933c1b88e29f4b27627dd9ea0bf9189944 ***

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

__tls_get_addr_opt stubs and tocsave optimization

This patch fixes a bug in the handling of the __tls_get_addr_opt
stub.  Calls via this stub don't have a toc restoring instruction
following the "bl", and the stub itself doesn't have an initial toc
save instruction.  Thus it is incorrect to skip over the first
instruction when a __tls_get_addr call is marked with a tocsave
reloc.

	* elf64-ppc.c (ppc64_elf_relocate_section): Don't skip first
	instruction of __tls_get_addr_opt stub.
	(plt_stub_size): Omit ALWAYS_EMIT_R2SAVE condition when
	dealing with __tls_get_addr_opt stub.
	(build_tls_get_addr_stub, ppc_size_one_stub): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix compilation failure in remote.c
@ 2018-08-07  4:19 sergiodj+buildbot
  2018-09-04 11:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07  4:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7f25a84f4cc1df5248c46346337f19a2a66af5a ***

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

Fix compilation failure in remote.c

A recent patch introduced a few of these:

/home/emaisin/src/binutils-gdb/gdb/remote.c:12862:19: error: format not a string literal and no format arguments [-Werror=format-security]
     error (err_msg);
                   ^

Fix them by replacing the call to error with

  error ("%s", err_msg);

gdb/ChangeLog:

	* remote.c (remote_target::download_tracepoint): Fix format
	string errors.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use remote register numbers in tracepoint mask
@ 2018-08-07  0:38 sergiodj+buildbot
  2018-09-04  7:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-07  0:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4277c4b87addb5354cc47b98d7a73e44cfaf22c2 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 4277c4b87addb5354cc47b98d7a73e44cfaf22c2

Use remote register numbers in tracepoint mask

Currently, tracepoint register masks in the QTDP packets include both
internal and remote register numbers, as well as pseudo-register
numbers.

This patch changes this so that the mask only includes remote register
numbers.

Register numbers from agent expressions are already set in the mask
using remote numbers.  Other tracepoint actions used internal numbers,
e.g. "collect $regs" or "collect $<pseudoreg>".  To handle pseudoreg
numbers, an empty agent expression is created and ax_reg_mask is
called for this expression and the pseudoreg.  This will cause the ax
to set its mask with the corresponding remote raw register
numbers (using ax_regs_mask, which calls
gdbarch_ax_pseudo_register_collect).

If ax_regs_mask and gdbarch_ax_pseudo_register_collect also generate
more ax bytecode, the ax is also appended to the collection list.  It
isn't clear that this was the original intent for
gdbarch_ax_pseudo_register_collect, and none of the arches seem to do
this, but if this changes in the future, it should work.

The patch also refactors the code used by validate_action line to
validate axs into a function that is now called from every place that
generates axs.  Previously, some parts of tracepoint.c that generated
axs didn't check if the ax length was greater than MAX_AGENT_EXPR_LEN.

gdb/ChangeLog:
2018-08-06  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* tracepoint.h (class collection_list) <add_register>: Remove.
	<add_remote_register, add_ax_registers, add_local_register>:
	Declare.
	<add_memrange>: Add scope parameter.
	* tracepoint.c (encode_actions_1): Likewise.
	(collection_list::add_register): Rename to ...
	(collection_list::add_remote_register): ... this.  Update
	comment.
	(collection_list::add_ax_registers, add_local_register): New
	methods.
	(collection_list::add_memrange): Add scope parameter.  Call
	add_local_register instead of add_register.
	(finalize_tracepoint_aexpr): New function.
	(collection_list::collect_symbol): Update calls to add_memrange.
	Call add_local_register instead of add_register.  Call
	add_ax_registers.  Call finalize_tracepoint_aexpr.
	(encode_actions_1): Get remote regnos for $reg action.  Call
	add_remote_register, add_ax_registers, and add_local_register.
	Update call to add_memrange.  Call finalize_tracepoint_aexpr.
	(validate_actionline): Call finalize_tracepoint_aexpr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allow larger regblock sizes when saving tracefiles
@ 2018-08-06 21:32 sergiodj+buildbot
  2018-09-04  9:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 21:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 296956befef3711ed458c7cba8041fde0dab9c50 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 296956befef3711ed458c7cba8041fde0dab9c50

Allow larger regblock sizes when saving tracefiles

The tracefile.c:trace_save function assumes trace_regblock_size won't
be larger than the MAX_TRACE_UPLOAD constant, used to size the buffer
which holds trace data.  This can cause buffer overruns when this is
not the case.  This patch changes this function so that the larger
size is used to size the buffer.

gdb/ChangeLog:
2018-08-06  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* tracefile.c: Include common/byte-vector.h.
	(trace_save): Change type of buf to gdb::byte_vector.  Initialize
	with trace_regblock_size if needed.  Update uses of buf.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Variable size for regs mask in collection list
@ 2018-08-06 21:20 sergiodj+buildbot
  2018-09-04  9:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 21:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a04b9d62a234923826e431a209d396a628661548 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: a04b9d62a234923826e431a209d396a628661548

Variable size for regs mask in collection list

This patch changes collection_list to allow larger register masks.

The mask is changed from an array to a vector and is initialized to
hold the maximum possible remote register number.  The stringify
method is updated to resize temp_buf if needed.

gdb/ChangeLog:
2018-08-06  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* tracepoint.h (collection_list) <m_regs_mask>: Change type to
	std::vector<unsigned char>.
	* tracepoint.c (collection_list::collection_list): Remove
	m_regs_mask initializer from initializer list.  Resize
	m_regs_mask using the largest remote register number.
	(collection_list::add_remote_register): Remove size check on
	m_regs_mask.  Use at to access element.
	(collection_list::stringify): Change type of temp_buf to
	gdb::char_vector.  Update uses of temp_buf.  Resize if needed to
	stringify the register mask.  Use pack_hex_byte for the register
	mask.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use get_remote_packet_size in download_tracepoint
@ 2018-08-06 20:55 sergiodj+buildbot
  2018-09-04  6:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 20:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3df3a985a475db004706d64f83d9085f99053611 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 3df3a985a475db004706d64f83d9085f99053611

Use get_remote_packet_size in download_tracepoint

This patch changes the remote target to use the remote packet size to
build QTDP packets, and to check if there is enough room for the
packet.

I changed the function to raise an error if the packet is too small,
instead of aborting gdb (through xsnprintf).  It isn't clear if gdb
will be in a consistent state with respect to the stub after this,
since it's possible that some packets will be sent but not others, and
there could be an incomplete tracepoint on the stub.

The char array used to build the packets is changed to a
gdb::char_vector and sized with the result from
get_remote_packet_size.

When checking if the buffer is large enough to hold the tracepoint
condition agent expression, the length of the expression is multiplied
by two, since it is encoded with two hex digits per expression
byte.  For simplicity, I assume that the result won't overflow, which
can happen for very long condition expressions.

gdb/ChangeLog:
2018-08-06  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* remote.c (remote_target::download_tracepoint): Remove BUF_SIZE.
	Replace array buf with gdb::char_vector buf, of size
	get_remote_packet_size ().  Replace references to buf and
	BUF_SIZE to buf.data () and buf.size ().  Replace strcpy, strcat
	and xsnprintf with snprintf.  Raise errors if the buffer is too
	small.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix indentation in remote_target::download_tracepoint
@ 2018-08-06 20:30 sergiodj+buildbot
  2018-09-04  4:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 20:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 05abfc39c719e740530000059bb963ad33462479 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
Branch: master
Commit: 05abfc39c719e740530000059bb963ad33462479

Fix indentation in remote_target::download_tracepoint

gdb/ChangeLog:
2018-08-06  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>

	* remote.c (remote_target::download_tracepoint): Fix indentation
	in for block.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Update warning reporting.
@ 2018-08-06 16:01 sergiodj+buildbot
  2018-09-03 16:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 16:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6af0448446f9212df4dc62e7618174d5d3f5e43e ***

Author: Claudiu Zissulescu <claziss@gmail.com>
Branch: master
Commit: 6af0448446f9212df4dc62e7618174d5d3f5e43e

[ARC] Update warning reporting.

MWDT compiler doesn't use eflags and makes use of 0x0c section. For
those, silence the gnu warning system.

bfd/
  Claudiu Zissulescu <claziss@synopsys.com>

        * elf32-arc.c (arc_elf_merge_private_bfd_data): Complain about
        efalgs only when in/out exists.
        (elf32_arc_section_from_shdr): Don't complain about 0x0c section
        type.  It is mwdt compiler specific.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Update merging attributes.
@ 2018-08-06 14:55 sergiodj+buildbot
  2018-09-03 16:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 14:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fd43d7870803bf0713f76118cc0fcb89407e873 ***

Author: claziss <claziss@synopsys.com>
Branch: master
Commit: 2fd43d7870803bf0713f76118cc0fcb89407e873

[ARC] Update merging attributes.

Some attributes were ignored during merging. Fix that, and add some
errors.

bfd/
2017-09-19  Claudiu Zissulescu <claziss@synopsys.com>

	* elf32-arc.c (arc_elf_merge_attributes): Fix merge attributes.

ld/
2017-09-19  Claudiu Zissulescu <claziss@synopsys.com>

	* testsuite/ld-arc/attr-merge-6.d: New file.
	* testsuite/ld-arc/attr-merge-6a.s: Likewise.
	* testsuite/ld-arc/attr-merge-6b.s: Likewise.
	* testsuite/ld-arc/attr-merge-6bis.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update dg-extract-results.* from gcc
@ 2018-08-06 14:52 sergiodj+buildbot
  2018-09-03 20:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 14:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5a6996172e6294ea37054b1a9caa3a923a8fe399 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 5a6996172e6294ea37054b1a9caa3a923a8fe399

Update dg-extract-results.* from gcc

When looking at the gdb.sum file produced by dg-extract-results.sh on
Solaris 11/x86, I noticed some wrong sorting, like this:

PASS: gdb.ada/addr_arith.exp: print something'address + 0
PASS: gdb.ada/addr_arith.exp: print 0 + something'address
PASS: gdb.ada/addr_arith.exp: print something'address - 0
PASS: gdb.ada/addr_arith.exp: print 0 - something'address

Looking closer, I noticed that while dg-extract-results.sh had been
copied over from contrib in the gcc repo, the corresponding
dg-extract-results.py file had not.  The latter not only fixes the
sorting problem I'd observed, but is also way faster than the shell
version (like a factor of 50 faster).

Therefore I propose to update both files from the gcc repo.  The changes
to the .sh version are trivial, just counting the number of DejaGnu
ERROR lines, too.

The files are moved to toplevel contrib:

* This way, they can easily be used should someone decide to parallelize
  one or more of the binutils, gas, or ld testsuites.

* They are less easily overlooked for updates from the gcc repo when
  they reside in the same place in both.

* The test_summary script needs to live in contrib since the toplevel
  Makefile's mail-report.log target expects it there.

Tested on amd64-pc-solaris2.11 with

	make -j16 check
and
	make -j16 -k RACY_ITER=5 check


	gdb/testsuite:
	* dg-extract-results.sh: Move to toplevel contrib.
	* Makefile.in (check-parallel): Reflect dg-extract-results.sh move.
	* Makefile.in (check-parallel-racy): Likewise.

	contrib:
	* dg-extract-results.sh: Move from gdb/testsuite.
	Update from gcc repo.
	* dg-extract-results.py: New from gcc repo.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Update handling AUX-registers.
@ 2018-08-06 14:06 sergiodj+buildbot
  2018-09-03 15:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 14:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6523c37fb52fc38da6e152328341caffd793749 ***

Author: claziss <claziss@synopsys.com>
Branch: master
Commit: b6523c37fb52fc38da6e152328341caffd793749

[ARC] Update handling AUX-registers.

Update aux-registers data-base, and accept aux-registers names with
upper/lowercase names.

opcode/
2017-07-18  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-regs.h: Update aux-registers.

gas/
2017-07-18  Claudiu Zissulescu  <claziss@synopsys.com>

	* config/tc-arc.c (find_opcode_match): Accept uppercase aux-regs
	names.
	* testsuite/gas/arc/ld2.d: Update test.
	* testsuite/gas/arc/taux.d: Likewise.
	* testsuite/gas/arc/taux.s: Likewise.

include/
2017-07-18  Claudiu Zissulescu  <claziss@synopsys.com>

	* opcode/arc.h (ARC_OPCODE_ARCV1): Define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused variables in procfs.c etc.
@ 2018-08-06 12:12 sergiodj+buildbot
  2018-09-03 15:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06 12:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 821a26825bdcb96358a51f5c2140475951429470 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 821a26825bdcb96358a51f5c2140475951429470

Remove unused variables in procfs.c etc.

The recent patch to enable -Wunused-variable uncovered a couple of
instances in Solaris-specific files:

/vol/src/gnu/gdb/hg/master/dist/gdb/proc-api.c: In function void _initialize_proc_api():
/vol/src/gnu/gdb/hg/master/dist/gdb/proc-api.c:422:28: error: unused variable c [-Werror=unused-variable]
   struct cmd_list_element *c;
                            ^

/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c: In function void procfs_init_inferior(target_ops*, int):
/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c:2895:12: error: unused variable signals [-Werror=unused-variable]
   sigset_t signals;
            ^~~~~~~
/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c: In member function virtual char* procfs_target::make_corefile_notes(bfd*, int*):
/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c:3845:19: error: unused variable old_chain [-Werror=unused-variable]
   struct cleanup *old_chain;
                   ^~~~~~~~~
/vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c:3847:18: error: unused variable fpregs [-Werror=unused-variable]
   gdb_fpregset_t fpregs;
                  ^~~~~~

Fixed as follows.  Tested on amd64-pc-solaris2.11, installed as obvious.

	* proc-api.c (_initialize_proc_api): Remove c, unused.
	* procfs.c (procfs_init_inferior): Remove signals, unused.
	(procfs_target::make_corefile_notes): Remove old_chain, fpregs,
	unused.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Avoid using W_STOPCODE(0) as this is ambiguous on MIPS
@ 2018-08-06  8:09 sergiodj+buildbot
  2018-09-03 15:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-06  8:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 953473375500a809fbb3eca3efa4dbb670c3a32f ***

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

gdb: Avoid using W_STOPCODE(0) as this is ambiguous on MIPS

The MIPS target supports 127 signals, and this can create an ambiguity
in process wait statuses.  A status value of 0x007f could potentially
indicate a process that has exited with signal 127, or a process that
has stopped with signal 0.

In uClibc-ng the interpretation of 0x007f is that the process has
exited with signal 127 rather than stopped with signal 0, and so,
WIFSTOPPED (W_STOPCODE (0)) will be false rather than true as it would
be on most other platforms.

Given that it's pretty easy to avoid using W_STOPCODE (0), lets do that.

gdb/ChangeLog:

	* linux-nat.c (linux_nat_target::follow_fork): Avoid using
	'W_STOPCODE (0)' as this could be ambiguous.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] R_PPC64_REL24_NOTOC support
@ 2018-08-05  8:47 sergiodj+buildbot
  2018-09-03 15:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-05  8:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 05d0e962f08af24f18cc79b890a68176b42bcb78 ***

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

R_PPC64_REL24_NOTOC support

R_PPC64_REL24_NOTOC is used on calls like "bl foo@notoc" to tell the
linker that linkage stubs for PLT calls or long branches can't use r2
for pic addressing.  Instead, new stubs that generate pc-relative
addresses are used.  One complication is that pc-relative offsets to
the PLT may need to be 64-bit in large programs, in contrast to the
toc-relative addressing used by older PLT linkage stubs where a 32-bit
offset is sufficient until the PLT itself exceeds 2G in size.

.eh_frame info to cover the _notoc stubs is yet to be implemented.

bfd/
	* elf64-ppc.c (ADDI_R12_R11, ADDI_R12_R12, LIS_R12),
	(ADDIS_R12_R11, ORIS_R12_R12_0, ORI_R12_R12_0),
	(SLDI_R12_R12_32, LDX_R12_R11_R12, ADD_R12_R11_R12): Define.
	(ppc64_elf_howto_raw): Add R_PPC64_REL24_NOTOC entry.
	(ppc64_elf_reloc_type_lookup): Support R_PPC64_REL24_NOTOC.
	(ppc_stub_type): Add ppc_stub_long_branch_notoc,
	ppc_stub_long_branch_both, ppc_stub_plt_branch_notoc,
	ppc_stub_plt_branch_both, ppc_stub_plt_call_notoc, and
	ppc_stub_plt_call_both.
	(is_branch_reloc): Add R_PPC64_REL24_NOTOC.
	(build_offset, size_offset): New functions.
	(plt_stub_size): Support plt_call_notoc and plt_call_both.
	(ppc_build_one_stub, ppc_size_one_stub): Support new stubs.
	(toc_adjusting_stub_needed): Handle R_PPC64_REL24_NOTOC.
	(ppc64_elf_size_stubs): Likewise, and new stubs.
	(ppc64_elf_build_stubs, ppc64_elf_relocate_section): Likewise.
	* reloc.c: Add BFD_RELOC_PPC64_REL24_NOTOC.
	* bfd-in2.h: Regenerate.
	* libbfd.h: Regenerate.
gas/
	* config/tc-ppc.c (ppc_elf_suffix): Support @notoc.
	(ppc_force_relocation, ppc_fix_adjustable): Handle REL24_NOTOC.
ld/
	* testsuite/ld-powerpc/ext.d,
	* testsuite/ld-powerpc/ext.s,
	* testsuite/ld-powerpc/ext.lnk,
	* testsuite/ld-powerpc/notoc.d,
	* testsuite/ld-powerpc/notoc.s: New tests.
	* testsuite/ld-powerpc/powerpc.exp: Run them.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Lose _r2off in powerpc64 stub names
@ 2018-08-05  8:17 sergiodj+buildbot
  2018-09-03 12:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-05  8:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f6ff4799bc50e6030bb707b2b2b525fcfdd2216 ***

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

Lose _r2off in powerpc64 stub names

Not a lot is conveyed by putting _r2off in a stub symbol that can't be
seen by inspecting the stub code or the toc restoring instruction
immediately after a call via such a stub.  Also, we don't distinguish
plt_call stub symbols from plt_call_r2save stub symbols, so this patch
makes long branch and plt branch stub symbols consistent with that
decision.

bfd/
	* elf64-ppc.c (ppc_build_one_stub): Lose "_r2off" in stub symbols.
ld/
	* testsuite/ld-powerpc/elfv2exe.d: Adjust for stub symbol change.
	* testsuite/ld-powerpc/tocopt6.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix thinko when deciding whether to disable TCP's Nagle algorithm
@ 2018-08-03 22:31 sergiodj+buildbot
  2018-09-02 22:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-03 22:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 425699f52d8fb875c2197b202b9e05bdc09d0115 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 425699f52d8fb875c2197b202b9e05bdc09d0115

Fix thinko when deciding whether to disable TCP's Nagle algorithm

This patch fixes a thinko that happened when I was implementing the
IPv6 support on GDB/gdbserver.  On certain situations, it is necessary
to disable TCP's Nagle algorithm (NODELAY).  For obvious reasons, this
only applies when we are dealing with a TCP connection.

While implementing the IPv6 patch, I noticed that the net_open
function (on gdb/ser-tcp.c) kept a flag indicating whether the
connection type was UDP or TCP.  I eliminated that flag, and started
using the 'struct addrinfo *' related to the successful connection
directly.  However, I made a mistake:

  if (success_ainfo->ai_socktype == IPPROTO_TCP)
                     ^^^^^^^^^^^
    {
      /* Disable Nagle algorithm.  Needed in some cases.  */
      int tmp = 1;

      setsockopt (scb->fd, IPPROTO_TCP, TCP_NODELAY,
		  (char *) &tmp, sizeof (tmp));
    }

The 'ai_socktype' field specifies the socket type (SOCK_STREAM or
SOCK_DGRAM), and not the protocol.  This test was always failing, and
the Nagle algorithm was never being disabled.

The obvious fix is to use the 'ai_protocol' field.  This is what this
patch does.

Huge "thank you" to Joel Brobecker who reported the regression (he was
experiencing an unusual delay while debugging a bare-metal program
running under QEMU) and helped me set up a proper reproducer for the
bug.

gdb/ChangeLog:
2018-08-03  Sergio Durigan Junior  <sergiodj@redhat.com>

	* ser-tcp.c (net_open): Fix thinko when deciding whether to
	disable TCP's Nagle algorithm (use "ai_protocol" instead of
	"ai_socktype").


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop NoRex64 from {,v}pmov{s,z}x*
@ 2018-08-03  8:58 sergiodj+buildbot
  2018-09-02 14:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-03  8:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dbf8be89edf7b6443fa0b7d31ca6d6ad202fadae ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: dbf8be89edf7b6443fa0b7d31ca6d6ad202fadae

x86: drop NoRex64 from {,v}pmov{s,z}x*

They're pointless with IgnoreSize also specified, and even more so when
no Qword operand exists.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop "mem" operand type attribute
@ 2018-08-03  7:47 sergiodj+buildbot
  2018-09-02 11:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-03  7:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c48dadc9a87f4fc3408987fc4dbd312bed50da9c ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: c48dadc9a87f4fc3408987fc4dbd312bed50da9c

x86: drop "mem" operand type attribute

No template specifies this bit, so there's no point recording it in the
templates. Use a flags[] bit instead.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Fix TLS and --gc-sections conflict.
@ 2018-08-03  1:21 sergiodj+buildbot
  2018-09-02  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-03  1:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 13755f406d6615e0750213edb04a023ec2ba7b9b ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 13755f406d6615e0750213edb04a023ec2ba7b9b

RISC-V: Fix TLS and --gc-sections conflict.

	bfd/
	* elfnn-riscv.c (riscv_elf_create_dynamic_sections): For .tdata.dyn,
	add SEC_LINKER_CREATED flag.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allow "info address" of a template parameter
@ 2018-08-02 22:45 sergiodj+buildbot
  2018-09-01 21:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-02 22:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e1d3d8c2494c021718ba957e83395958ee08a0f ***

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

Allow "info address" of a template parameter

PR symtab/16842 shows that gdb will crash when the user tries to
invoke "info address" of a template parameter.

The bug here is that dwarf2read.c does not set the symtab on the
template parameter symbols.  This is pedantically correct, given that
the template symbols do not appear in a symtab.  However, gdb
primarily uses the symtab backlink to find the symbol's objfile.  So,
this patch simply sets the symtab on these symbols.

Tested by the buildbot.

gdb/ChangeLog
2018-08-02  Tom Tromey  <tom@tromey.com>

	PR symtab/16842.
	* dwarf2read.c (read_func_scope): Set symtab on template parameter
	symbols.
	(process_structure_scope): Likewise.

gdb/testsuite/ChangeLog
2018-08-02  Tom Tromey  <tom@tromey.com>

	PR symtab/16842.
	* gdb.cp/temargs.exp: Test "info address" of a template
	parameter.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix kill issue leading to zombie process on MacOS Sierra
@ 2018-08-02 22:32 sergiodj+buildbot
  2018-09-01 20:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-02 22:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1584354913285389063622a39f845851f332eb9a ***

Author: Xavier Roirand <roirand@adacore.com>
Branch: master
Commit: 1584354913285389063622a39f845851f332eb9a

Fix kill issue leading to zombie process on MacOS Sierra

Starting with MacOS version Sierra, the gdb kill command
seems to work but inferior remains as zombie on the host.
Notice that, as zombie process, the inferior is not killable
by the user, nor by root.

The kill signal gdb sent to the inferior is not handled
in gdb as a signal sent by gdb thus no reply is made and
the process remains (since MacOS does not "release" the
inferior because no reply have been made to the signal
message).

This patch fixes this problem.

gdb/ChangeLog
2018-08-02  Xavier Roirand  <roirand@adacore.com>

	PR gdb/22629:
        * darwin-nat.c (darwin_kill_inferior): Fix handling of
        kill inferior.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Check results of get_darwin_inferior
@ 2018-08-02 22:19 sergiodj+buildbot
  2018-09-01 18:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-02 22:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b5bddbbbbcece5d52115bd3e1299cec2a3b362f0 ***

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

Check results of get_darwin_inferior

I noticed that the existing kill-detach-inferiors-cmd.exp test was
causing gdb to crash on macOS 10.13.  The bug was that an inferior
that hadn't yet been started would cause get_darwin_inferior to return
NULL, and this was not checked.

I went through the places calling get_darwin_inferior and added checks
where appropriate.  This makes the test get a bit further.  Not all of
these spots are exercised by the test, but they seem safe enough in
any case.

gdb/ChangeLog
2018-08-02  Tom Tromey  <tom@tromey.com>

	* darwin-nat.c (find_inferior_task_it, darwin_find_thread)
	(darwin_suspend_inferior, darwin_resume_inferior)
	(darwin_decode_notify_message, darwin_resume_inferior_threads)
	(darwin_check_new_threads): Check result of get_darwin_inferior.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Backport gettext fixes to get rid of warnings on macOS
@ 2018-08-02 19:11 sergiodj+buildbot
  2018-09-01 13:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-02 19:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8094f49a4dd9679c294e6254e928ea75c229aa95 ***

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

Backport gettext fixes to get rid of warnings on macOS

Two fixes were committed recently to the gettext repo in order to make
gdb build warning-free on macOS.  This patch backports them both:

  - Make the format_arg attribute effective also in the case _INTL_REDIRECT_INLINE.
    113893dce80358a4ae0d9463ce73c5670c81cf0c
    http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=113893dce80358a4ae0d9463ce73c5670c81cf0c

  - Enable the format_arg attribute also on clang on Mac OS X.
    bd6a52241c7c83c90e043ace2082a2508d273f55
    http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=bd6a52241c7c83c90e043ace2082a2508d273f55

intl/ChangeLog:

	* libgnuintl.h (_INTL_MAY_RETURN_STRING_ARG, gettext, dgettext,
	dcgettext, ngettext, dngettext, dcngettext): Backport changes
	from upstream gettext.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix potential illegal memory access in AVR backend.
@ 2018-08-01 14:09 sergiodj+buildbot
  2018-09-01  6:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-01 14:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a9f7d653c089fdd8ca66a51caab7c9687f50cd1 ***

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

Fix potential illegal memory access in AVR backend.

	* elf32-avr.c (avr_stub_name): Check for a NULL return from
	bfd_malloc.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Close resource leaks in the BFD library's plugin handler.
@ 2018-08-01 13:53 sergiodj+buildbot
  2018-09-01  3:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-01 13:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 103da91bc083f94769e3758175a96d06cef1f8fe ***

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

Close resource leaks in the BFD library's plugin handler.

	PR 23460
	* plugin.c (bfd_plugin_open_input): Close file descriptor if the
	call to fstat fails.
	(try_claim): Always close the file descriptor at the end of the
	function.
	(try_load_plugin): If a plugin has already been registered, then
	skip the dlopen and onload steps and go straight to claiming the
	file.  If these is an error, close the plugin.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PowerPC64 __tls_get_addr_opt stub .eh_frame fix
@ 2018-08-01  3:21 sergiodj+buildbot
  2018-08-31 23:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-01  3:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1aa4214141d30f99f941266a3bedbc332d674c04 ***

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

PowerPC64 __tls_get_addr_opt stub .eh_frame fix

This patch sets stub_offset in ppc_size_one_stub rather than in
ppc_build_one_stub.  That allows the plt stub alignment to be done in
just ppc_size_one_stub rather than both functions.  The patch also
corrects the place where the alignment was done, fixing a possible
error in .eh_frame data, and tidies some offset calculations.

bfd/
	* elf64-ppc.c (plt_stub_pad): Delay plt_stub_size call until needed.
	(ppc_build_one_stub): Don't set stub_offset, instead assert that
	it is sane.  Don't adjust stub_offset for alignment.  Adjust size
	calculation.  Use "targ" temp when calculating offsets.
	(ppc_size_one_stub): Set stub_offset here.  Use "targ" temp when
	calculating offsets.  Adjust for alignment before setting
	tls_get_addr_opt_bctrl.
ld/
	* testsuite/ld-powerpc/powerpc.exp: Run tlsopt5 with plt alignment.
	* testsuite/ld-powerpc/tlsopt5.s: Add extra call.
	* testsuite/ld-powerpc/tlsopt5.wf: Adjust expected output.
	* testsuite/ld-powerpc/tlsopt5.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] csky regen
@ 2018-08-01  3:08 sergiodj+buildbot
  2018-08-31 21:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-08-01  3:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb86a42aba5b6e1c135433e1c0c26223fd0f7a7f ***

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

csky regen

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


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Correct previous update - new translation for the opcodes subdirectory.
@ 2018-07-31 21:29 sergiodj+buildbot
  2018-08-31 19:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-31 21:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 07cc045019bf655b84692465232e9f0faf7d868f ***

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

Correct previous update - new translation for the opcodes subdirectory.

opcodes	* po/sv.po: Updated Swedish translation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: also optimize KXOR{D,Q} and KANDN{D,Q}
@ 2018-07-31  9:53 sergiodj+buildbot
  2018-08-31 19:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-31  9:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1424ad867742286be44932bf29720539add19ae0 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 1424ad867742286be44932bf29720539add19ae0

x86: also optimize KXOR{D,Q} and KANDN{D,Q}

These can be converted to 2-byte VEX encoding when both source registers
are the same, by using KXORW / KANDNW as replacement.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86/Intel: correct permitted operand sizes for AVX512 scatter/gather
@ 2018-07-31  9:28 sergiodj+buildbot
  2018-08-31 19:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-31  9:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6ff00b5e12e7256738d9a4dac66e5a7745b771ea ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 6ff00b5e12e7256738d9a4dac66e5a7745b771ea

x86/Intel: correct permitted operand sizes for AVX512 scatter/gather

AVX gather insns correctly allow the element size to be specified rather
than the full vector size. Make AVX512 ones match.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Match any kind of error after "cannot resolve name" on lib/gdbserver-support.exp:gdbserver_start
@ 2018-07-30 21:33 sergiodj+buildbot
  2018-08-31 19:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-30 21:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fb66cde8a42a383b111f0f1f48eb9f6daf9d736c ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fb66cde8a42a383b111f0f1f48eb9f6daf9d736c

Match any kind of error after "cannot resolve name" on lib/gdbserver-support.exp:gdbserver_start

On commit:

commit 7f1f7e23939adc7d71036a17fc6081e3af7ca585
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Date:   Fri Jul 13 16:20:34 2018 -0400

    Expect for another variant of error message when gdbserver cannot resolve hostname

I extended the regular expression being used to identify whether
gdbserver could not resolve a (host)name.  This was needed because the
error message being printed had a different variation across some
systems.  However, as it turns out, I've just noticed that the message
has yet another variation:

  target remote tcp8:123:2353
  tcp8:123:2353: cannot resolve name: System error
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  tcp8:123:2353: No such file or directory.
  (gdb) FAIL: gdb.server/server-connect.exp: tcp8: connect to gdbserver using tcp8:123

which is causing FAILs on some systems (namely, Fedora-i686 on
BuildBot).

So instead of trying to predict everything that can be printed, I
decided to just match anything after the "cannot resolve name: " part.
This patch implements that.

Regression tested on the BuildBot.

gdb/testsuite/ChangeLog:
2018-07-30  Sergio Durigan Junior  <sergiodj@redhat.com>

	* lib/gdbserver-support.exp (gdbserver_start): Match any kind of
	error after "cannot resolve name" string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Fix sizeof for dynamic types other than arrays
@ 2018-07-30 19:07 sergiodj+buildbot
  2018-08-31 18:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-30 19:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8f2dc0dc967222673d71a0493958a587c53ae3c ***

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

gdb: Fix sizeof for dynamic types other than arrays

In commit:

   commit 37cc0caeca4c9a8552370040f4cfeaeceaa03369
   Date:   Wed Jul 18 13:38:35 2018 +0200
   [gdb/exp] Interpret size of vla with unknown size as <optimized out>

All dynamic types are treated as arrays in the 'sizeof' code path,
which means that structures can incorrectly be treated as arrays.
This can cause a failure in the gdb.base/vla-datatypes.exp test
script.

This commit adds a check that we do have an array before checking the
array bounds, and I also check that the array index type is dynamic
too.  This second check probably isn't strictly necessary, but
shouldn't hurt, a non-dynamic index type shouldn't have undefined high
bound.

gdb/ChangeLog:

	* eval.c (evaluate_subexp_for_sizeof): Check for array type before
	checking array bounds are defined.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix crash with -D_GLIBCXX_DEBUG
@ 2018-07-30 15:34 sergiodj+buildbot
  2018-08-31 18:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-30 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 463c08d160e55d6eaf0f9bc3729781ce90f4de3f ***

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

Fix crash with -D_GLIBCXX_DEBUG

I noticed a buildbot failure where gdb crashed in info-os.exp, when
compiled with -D_GLIBCXX_DEBUG:

    (gdb) info os procgroups
    /usr/include/c++/7/bits/stl_algo.h:4834:
    Error: comparison doesn't meet irreflexive requirements, assert(!(a < a)).
    Objects involved in the operation:
	iterator::value_type "< operator type" {
	  type = pid_pgid_entry;
	}

The bug here is that pid_pgid_entry::operator< violates the C++
irreflexivity rule; that is, that an object cannot be less than
itself.

Tested locally by re-running info-os.exp.

gdb/ChangeLog
2018-07-30  Tom Tromey  <tom@tromey.com>

	* nat/linux-osdata.c (pid_pgid_entry::operator<): Fix
	irreflexivity violation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove old lint code
@ 2018-07-30 14:44 sergiodj+buildbot
  2018-08-31 18:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-30 14:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dba7455e76f87abe81cc9e4e9b1f979c1da02846 ***

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

Remove old lint code

This removes dead code that, according to the comments, existed to
placate lint.  I don't think this has been relevant in a long time,
and certainly not since gdb switched to C++.

Tested by rebuilding.

ChangeLog
2018-07-30  Tom Tromey  <tom@tromey.com>

	* cli/cli-decode.c (lookup_cmd): Remove lint code.
	* value.c (unpack_long): Remove lint code.
	* valops.c (value_ind): Remove lint code.
	* valarith.c (value_x_binop, value_x_unop, value_equal)
	(value_pos): Remove lint code.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Prevent a seg-fault in the linker when trying to process SH object files with bogus relocs.
@ 2018-07-30 13:14 sergiodj+buildbot
  2018-08-31 18:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-30 13:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a05b9f5e1eb8f01eea23eff3902fa57f1f28a4e1 ***

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

Prevent a seg-fault in the linker when trying to process SH object files with bogus relocs.

	PR 22706
	* elf32-sh.c (sh_elf_relocate_section): When processing
	translation relocs, fail if the relocation offset is too small.
	Replace BFD_ASSERTs with more helpful error messages.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for the C_SKY series of processors.
@ 2018-07-30 11:50 sergiodj+buildbot
  2018-08-31 18:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-30 11:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8891f8d622a31306062065813fc278d8a94fe21 ***

Author: Andrew Jenner <andrew@codesourcery.com>
Branch: master
Commit: b8891f8d622a31306062065813fc278d8a94fe21

Add support for the C_SKY series of processors.

This patch series is a new binutils port for C-SKY processors, including support for both the V1 and V2 processor variants.  V1 is derived from the MCore architecture while V2 is substantially different, with mixed 16- and 32-bit instructions, a larger register set, a different (but overlapping) ABI, etc.  There is support for bare-metal ELF targets and Linux with both glibc and uClibc.

This code is being contributed jointly by C-SKY Microsystems and Mentor Graphics.  C-SKY is responsible for the technical content and has proposed Lifang Xia and Yunhai Shang as port maintainers.  (Note that C-SKY does have a corporate copyright assignment on file with the FSF.) Mentor Graphics' role has been cleaning up the code, adding documentation and additional test cases, etc, to address issues we anticipated reviewers would complain about.

bfd     * Makefile.am (ALL_MACHINES, ALL_MACHINES_CFILES): Add C-SKY.
        (BFD32_BACKENDS, BFD_BACKENDS_CFILES): Likewise.
        * Makefile.in: Regenerated.
        * archures.c (enum bfd_architecture): Add bfd_arch_csky and
        related bfd_mach defines.
        (bfd_csky_arch): Declare.
        (bfd_archures_list): Add C-SKY.
        * bfd-in.h (elf32_csky_build_stubs): Declare.
        (elf32_csky_size_stubs): Declare.
        (elf32_csky_next_input_section: Declare.
        (elf32_csky_setup_section_lists): Declare.
        * bfd-in2.h: Regenerated.
        * config.bfd: Add C-SKY.
        * configure.ac: Likewise.
        * configure: Regenerated.
        * cpu-csky.c: New file.
        * elf-bfd.h (enum elf_target_id): Add C-SKY.
        * elf32-csky.c: New file.
        * libbfd.h: Regenerated.
        * reloc.c: Add C-SKY relocations.
        * targets.c (csky_elf32_be_vec, csky_elf32_le_vec): Declare.
        (_bfd_target_vector): Add C-SKY target vector entries.

binutils* readelf.c: Include elf/csky.h.
        (guess_is_rela): Handle EM_CSKY.
        (dump_relocations): Likewise.
        (get_machine_name): Likewise.
        (is_32bit_abs_reloc): Likewise.

include  * dis-asm.h (csky_symbol_is_valid): Declare.
         * opcode/csky.h: New file.

opcodes  * Makefile.am (TARGET_LIBOPCODES_CFILES): Add csky-dis.c.
         * Makefile.in: Regenerated.
         * configure.ac: Add C-SKY.
         * configure: Regenerated.
         * csky-dis.c: New file.
         * csky-opc.h: New file.
         * disassemble.c (ARCH_csky): Define.
         (disassembler, disassemble_init_for_target): Add case for ARCH_csky.
         * disassemble.h (print_insn_csky, csky_get_disassembler): Declare.

gas      * Makefile.am (TARGET_CPU_CFILES): Add entry for C-SKY.
         (TARGET_CPU_HFILES, TARGET_ENV_HFILES): Likewise.
         * Makefile.in: Regenerated.
         * config/tc-csky.c: New file.
         * config/tc-csky.h: New file.
         * config/te-csky_abiv1.h: New file.
         * config/te-csky_abiv1_linux.h: New file.
         * config/te-csky_abiv2.h: New file.
         * config/te-csky_abiv2_linux.h: New file.
         * configure.tgt: Add C-SKY.
         * doc/Makefile.am (CPU_DOCS): Add entry for C-SKY.
         * doc/Makefile.in: Regenerated.
         * doc/all.texi: Set CSKY feature.
         * doc/as.texi (Overview): Add C-SKY options.
         (Machine Dependencies): Likewise.
         * doc/c-csky.texi: New file.
         * testsuite/gas/csky/*: New test cases.

ld      * Makefile.am (ALL_EMULATION_SOURCES): Add C-SKY emulations.
        (ecskyelf.c, ecskyelf_linux.c): New rules.
        * Makefile.in: Regenerated.
        * configure.tgt: Add C-SKY.
        * emulparams/cskyelf.sh: New file.
        * emulparams/cskyelf_linux.sh: New file.
        * emultempl/cskyelf.em: New file.
        * gen-doc.texi: Add C-SKY.
        * ld.texi: Likewise.
        (Options specific to C-SKY targets): New section.
        * testsuite/ld-csky/*: New tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Don't call gdb_load_shlib unless GDB is running
@ 2018-07-28 19:47 sergiodj+buildbot
  2018-08-31 18:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-28 19:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c708f4d256f1f1a92310fcb323a108d95d5fd5da ***

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

gdb: Don't call gdb_load_shlib unless GDB is running

The gdb_load_shlib function will, on remote targets, try to run some
GDB commands.  This obviously isn't going to work unless GDB is
running.

The gdb.trace/tspeed.exp test calls gdb_load_shlib before starting
GDB.  Don't do that.

The failure that's triggered is actually DeJaGNU complaining that the
variable $use_gdb_stub doesn't exist, this is only created when GDB is
started.  Something like this should trigger a failure:

  make check-gdb \
    RUNTESTFLAGS="--target_board=remote-gdbserver-on-localhost \
                  gdb.trace/tspeed.exp"

This commit also adds a check to gdb_load_shlib that GDB is running.
The check is always performed, so this should catch cases where a GDB
developer adds a use of gdb_load_shlib but doesn't test their code
with a remote target.

gdb/testsuite/ChangeLog:

	* gdb.trace/tspeed.exp: Only call gdb_load_shlib after gdb has
	started.
	* lib/gdb.exp (gdb_load_shlib): Call perror if GDB is not running.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/exp] Interpret size of vla with unknown size as <optimized out>
@ 2018-07-28  8:33 sergiodj+buildbot
  2018-08-31 17:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-28  8:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37cc0caeca4c9a8552370040f4cfeaeceaa03369 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 37cc0caeca4c9a8552370040f4cfeaeceaa03369

[gdb/exp] Interpret size of vla with unknown size as <optimized out>

At -O3 -g -gstrict-dwarf, gcc generates for an optimized out vla 'a' a
DW_TAG_variable with type DW_TAG_array_type containing one
DW_TAG_subrange_type, but without DW_AT_upper_bound or DW_AT_count, which
makes the upper bound value 'unknown':
...
	.uleb128 0x15   # (DIE (0x161) DW_TAG_variable)
        .long   0xec    # DW_AT_abstract_origin
        .long   0x170   # DW_AT_type
	...
        .uleb128 0xa    # (DIE (0x170) DW_TAG_array_type)
        .long   0x110   # DW_AT_type
        .long   0x17f   # DW_AT_sibling
        .uleb128 0x17   # (DIE (0x179) DW_TAG_subrange_type)
        .long   0xc6    # DW_AT_type
        .byte   0       # end of children of DIE 0x170
...

But gdb prints '0' for the size of 'a':
...
/gdb ./vla-1.exe -batch -ex "b f1" -ex "run" -ex "p sizeof(a)"
Breakpoint 1 at 0x4004c0: f1. (2 locations)

Breakpoint 1, f1 (i=<optimized out>) at vla-1.c:18
18      }
$1 = 0
...
while <optimized out> would be more appropriate.

This patch fixes that in evaluate_subexp_for_sizeof.

Build and reg-tested on x86_64-linux.

2018-07-28  Tom de Vries  <tdevries@suse.de>

	* eval.c (evaluate_subexp_for_sizeof): Interpret size of dynamic type
	with undefined upper bound as <optimized out>.

	* gdb.base/vla-optimized-out-o3-strict.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Improve gcore manpage and clarify "-o" option
@ 2018-07-27 20:23 sergiodj+buildbot
  2018-08-31 17:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-27 20:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 129eb0f1f16dc7a49799a024a7bcb109d954a1e7 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 129eb0f1f16dc7a49799a024a7bcb109d954a1e7

Improve gcore manpage and clarify "-o" option

Ref.: https://bugs.debian.org/904628

It has been reported that gcore's manpage is a bit imprecise when it
comes to two things:

- It doesn't explicity say that the command accepts more than one PID
  on its CLI.

- It fails to mention that the argument passed through the "-o" option
  is actually a prefix that will be used to compose the corefile's
  filename, and not the actual filename.

I decided to give it a try and rewrite parts of the text to further
clarify these two points.  I ended up rewording the "Description"
section because, IMHO, it was a bit confuse to understand.

To make things consistent, I've also renamed the "$name" variable in
the gcore.in script, and expanded the usage text.

gdb/doc/ChangeLog:
2018-07-27  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gdb.texinfo (gcore man): Rewrite "Description" and "-o"
	option sections to further clarify that gcore can take more
	than one PID, and that "-o" is used to specify a prefix, not a
	filename.

gdb/ChangeLog:
2018-07-27  Sergio Durigan Junior  <sergiodj@redhat.com>

	* gcore.in: Rename variable "name" to "prefix".  Expand
	"usage" text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Remove ELF_TARGET_ID macro
@ 2018-07-27  2:40 sergiodj+buildbot
  2018-08-31 17:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-27  2:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 469d3b57cef3d9e02d4bc584a9cc814ef22cdb4e ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 469d3b57cef3d9e02d4bc584a9cc814ef22cdb4e

S12Z: Remove ELF_TARGET_ID macro

	* elf32-s12z.c (ELF_TARGET_ID): Don't define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add functions and macros to read and write 24 bit values.
@ 2018-07-27  2:27 sergiodj+buildbot
  2018-08-31 16:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-27  2:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 370e4b5079ff8d62be3adee7396948d4c5795091 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 370e4b5079ff8d62be3adee7396948d4c5795091

Add functions and macros to read and write 24 bit values.

	* libbfd.c (bfd_getb24, bfd_getl24): New functions.
	(bfd_get_24, bfd_put_24): New macros.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S12Z: Remove inappropriate comment.
@ 2018-07-27  2:25 sergiodj+buildbot
  2018-08-31 15:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-27  2:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd4d353f812a3ecb29cabf0e62319253daf510fa ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: cd4d353f812a3ecb29cabf0e62319253daf510fa

S12Z: Remove inappropriate comment.

	* elf32-s12z.c (s12z_elf_set_mach_from_flags): Remove comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/GAS: Correct the AFL_ASE_MASK macro
@ 2018-07-27  0:35 sergiodj+buildbot
  2018-08-31 15:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-27  0:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2bb9bbe2e8faa7fd9ee156da0254605720eb16d6 ***

Author: Chenghua Xu <paul.hua.gm@gmail.com>
Branch: master
Commit: 2bb9bbe2e8faa7fd9ee156da0254605720eb16d6

MIPS/GAS: Correct the AFL_ASE_MASK macro

Fix an issue with commit 8095d2f70e1a ("MIPS/GAS: Split Loongson MMI
Instructions from loongson2f/3a"), AFL_ASE_MASK should be 0x0006ffff
instead of 0x0004ffff.

2018-07-27  Chenghua Xu  <paul.hua.gm@gmail.com>
            Maciej W. Rozycki  <macro@linux-mips.org>

include/
	* elf/mips.h (AFL_ASE_MASK): Correct typo.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix Cygwin compilation after target_ops C++ conversion.
@ 2018-07-26 21:37 sergiodj+buildbot
  2018-08-30 20:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 21:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6af79d7b5a21a40c4036541fbfa821f9d1260ebf ***

Author: Jon Turney <jon.turney@dronecode.org.uk>
Branch: master
Commit: 6af79d7b5a21a40c4036541fbfa821f9d1260ebf

Fix Cygwin compilation after target_ops C++ conversion.

After f6ac5f3d "Convert struct target_ops to C++", we need to explicitly use
the global namespace when calling ::close() from windows_nat_target methods,
as that object has a close() method.

gdb/ChangeLog:

2018-07-14  Jon Turney  <jon.turney@dronecode.org.uk>

	* windows-nat.c (windows_nat_target::create_inferior): Update to
	call close() in global namespace.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Introduce partial_symbol::address
@ 2018-07-26 17:20 sergiodj+buildbot
  2018-08-30 16:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02e9e7f7e2bed3b82cb6541f566caf07256b9b2f ***

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

Introduce partial_symbol::address

This introduces a partial_symbol::address method.  This method takes
an objfile argument.  This is necessary so that we can later relocate
a partial symbol at its point of use.  It also adds an accessor to
compute the unrelocated value; and a method to be used for setting the
field.

Note that the new method doesn't actually perform any relocation yet.
That will come in a subsequent patch.  However, the comments are
written to reflect the intended, rather than the temporary, semantics.

gdb/ChangeLog
2018-07-26  Tom Tromey  <tromey@redhat.com>

	* psympriv.h (struct partial_symbol) <unrelocated_address,
	address, set_address>: New methods.
	* psymtab.c (find_pc_sect_psymtab_closer, find_pc_sect_psymbol)
	(fixup_psymbol_section, relocate_psymtabs): Update.
	(print_partial_symbols): Add 'objfile' parameter.  Update.
	(dump_psymtab, add_psymbol_to_bcache, psym_fill_psymbol_map):
	Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make psymbols and psymtabs independent of the program space
@ 2018-07-26 16:52 sergiodj+buildbot
  2018-08-30 19:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 16:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7974897237f7708d440c45bc74cdfb70a2db8124 ***

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

Make psymbols and psymtabs independent of the program space

This patch finally makes partial symbols and partial symtabs
independent of the program space.

Specifically:

It changes add_psymbol_to_list to accept a section index, and changes
the psymbol readers to pass this.  At the same time it removes the
code to add the objfile's section offset to the psymbol.

It adds an objfile argument to the psymtab textlow and texthigh
accessors and changes some code to use the raw variants instead.

It removes the "relocate" method from struct quick_symbol_functions,
as it is no longer needed any more.

It changes partial_symbol::address so that the relevant offset is now
applied at the point of use.

gdb/ChangeLog
2018-07-26  Tom Tromey  <tom@tromey.com>

	* dwarf-index-write.c (add_address_entry): Don't add objfile
	offsets.
	* dbxread.c (find_stab_function): Rename from
	find_stab_function_addr.  Return a bound_minimal_symbol.
	(read_dbx_symtab): Use raw_text_low, raw_text_high.
	Don't add objfile offsets.
	(end_psymtab): Use raw_text_low, raw_text_high,
	MSYMBOL_VALUE_RAW_ADDRESS.
	(read_ofile_symtab): Update.
	(process_one_symbol): Update.
	* dwarf2read.c (create_addrmap_from_index): Don't add objfile
	offsets.
	(dw2_relocate): Remove.
	(dw2_find_pc_sect_symtab): Bias PC by the text offset before
	searching addrmap.
	(dwarf2_gdb_index_functions, dwarf2_debug_names_functions):
	Update.
	(process_psymtab_comp_unit_reader, add_partial_symbol)
	(add_partial_subprogram, dwarf2_ranges_read): Update.
	(load_partial_dies): Update.
	(add_address_entry): Don't add objfile offsets.
	(dwarf2_build_include_psymtabs): Update.
	(create_addrmap_from_aranges): Don't add objfile offsets.
	(dw2_find_pc_sect_compunit_symtab): Update.
	* mdebugread.c (parse_symbol): Don't add objfile offsets.
	(parse_lines): Remove 'pst' parameter, replace with 'textlow'.
	Update.
	(parse_partial_symbols): Don't add objfile offsets.  Use
	raw_text_low, raw_text_high.  Update.
	(handle_psymbol_enumerators, psymtab_to_symtab_1): Update.
	* objfiles.c (objfile_relocate1): Don't relocate psymtabs_addrmap
	or call 'relocate' quick function.  Clear psymbol_map.
	* psympriv.h (struct partial_symbol) <address>: Add section
	offset.
	<set_unrelocated_address>: Rename from set_address.
	<raw_text_low, raw_text_high>: New methods.
	<text_low, text_high>: Add objfile parameter.
	(add_psymbol_to_bcache): Add 'section' parameter.  Call
	set_unrelocated_address.
	* psymtab.c (find_pc_sect_psymtab_closer, find_pc_sect_psymtab)
	(find_pc_psymbol): Update.
	(fixup_psymbol_section, relocate_psymtabs): Remove.
	(dump_psymtab, psym_functions): Update.
	(add_psymbol_to_bcache, add_psymbol_to_list): Add 'section'
	parameter.
	(maintenance_info_psymtabs, maintenance_check_psymtabs): Update.
	(start_psymtab_common): Update.
	* symfile-debug.c (debug_qf_relocate): Remove.
	(debug_sym_quick_functions): Update.
	* symfile.h (struct quick_symbol_functions) <relocate>: Remove.
	* xcoffread.c (scan_xcoff_symtab): Don't add objfile offsets.
	Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add validity bits for psymtab high and low fields
@ 2018-07-26 16:39 sergiodj+buildbot
  2018-08-30 19:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 16:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 52948f01e4a11f5fcebdca112036f907ac69e7ad ***

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

Add validity bits for psymtab high and low fields

Right now some psymtab code checks whether a psymtab's textlow or
texthigh fields are valid by comparing against 0.

I imagine this is mildly wrong in the current environment, but once
psymtabs are relocated dynamically, it will no longer be correct,
because it will be much more normal to see a psymtab with a textlow of
zero -- this will just mean it appears at the start of the text
section.

This patch introduces validity bits to handle this situation more
nicely, and changes users of the code to follow.

gdb/ChangeLog
2018-07-26  Tom Tromey  <tromey@redhat.com>

	* dbxread.c (end_psymtab): Use text_high_valid and
	text_low_valid.
	* mdebugread.c (parse_partial_symbols): Use text_low_valid.
	(psymtab_to_symtab_1): Use text_high_valid and text_low_valid.
	* psympriv.h (struct partial_symtab) <m_text_low, m_text_high>:
	Update comment.
	<text_low_valid, text_high_valid>: New fields.
	<set_text_low, set_text_high>: Update.
	* xcoffread.c (scan_xcoff_symtab): Use text_low_valid.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change representation of psymbol to flush out accessors
@ 2018-07-26 16:02 sergiodj+buildbot
  2018-08-30 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8a6d4234503bfe1c656d8cd335cac828507df9a3 ***

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

Change representation of psymbol to flush out accessors

This is the psymbol analog to the patch to change the representation
of minimal symbols:

    https://sourceware.org/ml/gdb-patches/2013-10/msg00524.html

It has the same rationale: namely, that we're going to change the code
to apply psymbol offsets at runtime.  This will be done by adding an
argument to the SYMBOL_VALUE_ADDRESS macro -- but since we can't
convert all the symbol types at once, we need a new approach.

Because gdb now is in C++, this patch changes partial_symbol to
inherit from general_symbol_info, rather than renaming the field.
This simplifies code in some places.

Also, as noted before, these macros implement a kind of "phony
polymorphism" that is not actually useful in practice; so this patch
removes the macros in favor of simply referring directly to members.
In a few cases -- obj_section in this patch and the symbol address in
the future -- methods will be used instead.

Note that this removes the blanket memset from add_psymbol_to_bcache.
This hasn't really been needed since bcache was modified to allow
holes in objects and since psymtab took advantage of that.  This
deletion was required due to changing partial_symbol to derive from
general_symbol_info.

gdb/ChangeLog
2018-07-26  Tom Tromey  <tom@tromey.com>

	* dwarf-index-write.c (write_psymbols, debug_names::insert)
	(debug_names::write_psymbols): Update.
	* psympriv.h (struct partial_symbol): Derive from
	general_symbol_info.
	<obj_section>: New method.
	(PSYMBOL_DOMAIN, PSYMBOL_CLASS): Remove.n
	* psymtab.c (find_pc_sect_psymtab_closer, find_pc_sect_psymtab)
	(find_pc_sect_psymbol, fixup_psymbol_section)
	(match_partial_symbol, lookup_partial_symbol, relocate_psymtabs)
	(print_partial_symbols, recursively_search_psymtabs)
	(compare_psymbols, psymbol_hash, psymbol_compare)
	(add_psymbol_to_bcache, maintenance_check_psymtabs)
	(psymbol_name_matches, psym_fill_psymbol_map): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove dead code in end_psymtab
@ 2018-07-26 15:38 sergiodj+buildbot
  2018-08-30 15:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 15:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 08994e1ddcc8e5e1e003602409662ae799a1ff30 ***

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

Remove dead code in end_psymtab

I noticed that there is a bit of dead code in end_psymtab.
This deletes it.

Normally I would investigate a fix for the code.  However, considering
that the code has been this way a long time (since the first import to
sourceware) and considering that dbxread.c is not as important any
more, I think it's safe to just consider that there's no bug.

gdb/ChangeLog
2018-07-26  Tom Tromey  <tromey@redhat.com>

	* dbxread.c (end_psymtab): Remove dead code.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Add comment in gdb.base/vla-optimized-out.c
@ 2018-07-26 10:16 sergiodj+buildbot
  2018-08-30 15:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26 10:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63b4ecf76fec65c6853ea01ffab31642533801e9 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 63b4ecf76fec65c6853ea01ffab31642533801e9

[gdb/testsuite] Add comment in gdb.base/vla-optimized-out.c

2018-07-26  Tom de Vries  <tdevries@suse.de>

	* gdb.base/vla-optimized-out.c: Add comment about origin of test-case.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PowerPC Improve support for Gekko & Broadway
@ 2018-07-26  8:36 sergiodj+buildbot
  2018-08-30 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26  8:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fa758a70467c37cfe7b261e1dc20d431be3db62e ***

Author: Alex Chadwick <Alex.Chadwick@cl.cam.ac.uk>
Branch: master
Commit: fa758a70467c37cfe7b261e1dc20d431be3db62e

PowerPC Improve support for Gekko & Broadway

This is a relatively straightforward patch to improve support for the
IBM Gekko and IBM Broadway processors.  Broadway is functionally
equivalent to the IBM 750CL, while Gekko's functionality is a subset
of theirs.  The patch simplifies this reality and adds -mgekko and
-mbroadway as aliases for -m750cl.  I didn't feel it was worth wasting
a PPC_OPCODE_* bit to differentiate Gekko.  The patch adds a number of
simplified mnemonics for special purpose register access.  Notably,
Broadway adds 4 additional IBAT and DBAT registers but these are not
assigned sequential SPR numbers.

gas/
	* config/tc-ppc.c (md_show_usage): Add -mgekko and -mbroadway.
	* doc/as.texi (Target PowerPC options): Add -mgekko and -mbroadway.
	* doc/c-ppc.texi (PowerPC-Opts): Likewise.
	* testsuite/gas/ppc/broadway.d,
	* testsuite/gas/ppc/broadway.s: New test for broadway.
	* testsuite/gas/ppc/ppc.exp: Run new test.
include/
	* opcode/ppc.h (PPC_OPCODE_750): Adjust comment.
opcodes/
	* ppc-dis.c (ppc_opts): Add -mgekko and -mbroadway.
	(powerpc_init_dialect): Handle bfd_mach_ppc_750.
	* ppc-opc.c (insert_sprbat, extract_sprbat): New functions to
	support disjointed BAT.
	(powerpc_operands): Allow extra bit in SPRBAT_MASK.  Add SPRGQR.
	(XSPRGQR_MASK, GEKKO, BROADWAY): Define.
	(powerpc_opcodes): Add 750cl extended mnemonics for spr access.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Implement PowerPC64 .localentry for value 1
@ 2018-07-26  3:50 sergiodj+buildbot
  2018-08-30 14:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-26  3:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33cb30a1f932b5a211aa319a01783d4957ae5d57 ***

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

Implement PowerPC64 .localentry for value 1

This adds support for ".localentry 1", a new st_other
STO_PPC64_LOCAL_MASK encoding that signifies a function with a single
entry point like ".localentry 0", but unlike a ".localentry 0"
function does not preserve r2.

include/
	* elf/ppc64.h: Specify byte offset to local entry for values
	of two to six in STO_PPC64_LOCAL_MASK.  Clarify r2 return
	value for such functions when entering via global entry point.
	Specify meaning of a value of one in STO_PPC64_LOCAL_MASK.
bfd/
	* elf64-ppc.c (ppc64_elf_size_stubs): Use a ppc_stub_long_branch_r2off
	for calls to symbols with STO_PPC64_LOCAL_MASK bits set to 1.
gas/
	* config/tc-ppc.c (ppc_elf_localentry): Allow .localentry values
	of 1 and 7 to directly set value into STO_PPC64_LOCAL_MASK bits.
ld/testsuite/
	* ld-powerpc/elfv2.s: Add .localentry f5,1 testcase.
	* ld-powerpc/elfv2exe.d: Update.
	* ld-powerpc/elfv2so.d: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Expand Broadcast to 3 bits
@ 2018-07-25 23:35 sergiodj+buildbot
  2018-08-30 13:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-25 23:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a1b91eabbe77f4d906a0895121d76a0653c3cf3 ***

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

x86: Expand Broadcast to 3 bits

Expand Broadcast to 3 bits so that the number of bytes to broadcast
can be computed as 1 << (Broadcast - 1).  Use it to simplify x86
assembler.

gas/

	* config/tc-i386.c (Broadcast_Operation): Add bytes.
	(build_evex_prefix): Use i.broadcast->bytes.
	(match_broadcast_size): New function.
	(check_VecOperands): Use the broadcast field to compute the
	number of bytes to broadcast directly.  Set i.broadcast->bytes.
	Use match_broadcast_size.

opcodes/

	* i386-gen.c (adjust_broadcast_modifier): New function.
	(process_i386_opcode_modifier): Add an argument for operands.
	Adjust the Broadcast value based on operands.
	(output_i386_opcode): Pass operand_types to
	process_i386_opcode_modifier.
	(process_i386_opcodes): Pass NULL as operands to
	process_i386_opcode_modifier.
	* i386-opc.h (BYTE_BROADCAST): New.
	(WORD_BROADCAST): Likewise.
	(DWORD_BROADCAST): Likewise.
	(QWORD_BROADCAST): Likewise.
	(i386_opcode_modifier): Expand broadcast to 3 bits.
	* i386-tbl.h: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/breakpoints] Fix sigsegv in info prog at exec catchpoint
@ 2018-07-25 23:11 sergiodj+buildbot
  2018-08-30 13:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-25 23:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9e7f3bbbbf5a13e879a4cc3cfa958412ffac0d9d ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 9e7f3bbbbf5a13e879a4cc3cfa958412ffac0d9d

[gdb/breakpoints] Fix sigsegv in info prog at exec catchpoint

With the test-case contained in this patch and compiled for debug we run into
a segfault with trunk gdb:
...
$ gdb catch-follow-exec -batch -ex "catch exec" \
  -ex "set follow-exec-mode new" -ex "run" -ex "info prog"
Catchpoint 1 (exec)
process xxx is executing new program: /usr/bin/ls
[New inferior 2 (process 0)]
[New process xxx]

Thread 2.1 "ls" hit Catchpoint 1 (exec'd /usr/bin/ls), in _start () from
  /lib64/ld-linux-x86-64.so.2
Segmentation fault (core dumped)
...

The patch fixes the segfault by returning an error in info_program_command
if get_last_target_status returns minus_one_ptid.

The test-case is non-standard, because the standard approach runs into
PR23368, a problem with gdb going to the background.

Build and reg-tested on x86_64-linux.

2018-07-26  Tom de Vries  <tdevries@suse.de>

	PR breakpoints/23366
	* infcmd.c (info_program_command): Handle ptid == minus_one_ptid.

	* gdb.base/catch-follow-exec.c: New test.
	* gdb.base/catch-follow-exec.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/symtab] Warn about unresolved DW_AT_upper_bound/DW_AT_count
@ 2018-07-25 22:34 sergiodj+buildbot
  2018-08-30 13:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-25 22:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 506f5c41cab71dbc3e562ba367d2dc6b355b64a6 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 506f5c41cab71dbc3e562ba367d2dc6b355b64a6

[gdb/symtab] Warn about unresolved DW_AT_upper_bound/DW_AT_count

This patch generates a warning if DW_AT_upper_bound or DW_AT_count is defined,
but can't be translated.  This is triggered for current gcc in lto mode for
vla test-cases.

Build and reg-tested on x86_64-linux.

2018-07-26  Tom de Vries  <tdevries@suse.de>

	* dwarf2read.c (read_subrange_type): Warn if DW_AT_upper_bound or
	DW_AT_count can't be translated to a dynamic prop.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Notify about breakpoint modification when enabling/disabling single location
@ 2018-07-25 18:04 sergiodj+buildbot
  2018-08-30 12:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-25 18:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d7154a8d08b142d1258dc2e4189ff0d00cd26493 ***

Author: Jan Vrany <jan.vrany@fit.cvut.cz>
Branch: master
Commit: d7154a8d08b142d1258dc2e4189ff0d00cd26493

Notify about breakpoint modification when enabling/disabling single location

When a single breakpoint location enableness was modified by a CLI
command, observers were not notified about it. This issue is now fixed.

gdb/ChangeLog:

	* breakpoint.c (enable_disable_bp_num_loc): Notify observers.

gdb/testsuite/ChangeLog:

	* gdb.mi/mi-breakpoint-location-ena-dis.cc: New file.
	* gdb.mi/mi-breakpoint-location-ena-dis.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] list Tom Tromey as GDB Global Maintainer
@ 2018-07-25 15:42 sergiodj+buildbot
  2018-08-30 11:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-25 15:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a45389f60d4372bdb3484e432935f3169037d88c ***

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

list Tom Tromey as GDB Global Maintainer

gdb/ChangeLog:

        * MAINTAINERS (Global Maintainers): Add Tom Tromey.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Suppress string diagnostics for pre-release GCC
@ 2018-07-25  3:02 sergiodj+buildbot
  2018-08-30 10:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-25  3:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be3e27bb5554e45d54d7cdc74353dda246239475 ***

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

Suppress string diagnostics for pre-release GCC

Extends commit 898ade12ee8 to cover other targets.

	* elf32-arm.c (elf32_arm_nabi_write_core_note): Disable
	-Wstringop-truncation warning for gcc-8.0 too.
	* elf32-ppc.c (ppc_elf_write_core_note): Likewise.
	* elf64-ppc.c (ppc64_elf_write_core_note): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_write_core_note): Likewise.
	* elf32-s390.c (elf_s390_write_core_note): Comment fix.
	* elf64-s390.c (elf_s390_write_core_note): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Set CU language before processing any DIEs (symtab/23010 et al)
@ 2018-07-24 20:51 sergiodj+buildbot
  2018-08-30  9:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-24 20:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 380618d68a2b4ee60cebf3941d11a5af4e0aeee0 ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 380618d68a2b4ee60cebf3941d11a5af4e0aeee0

Set CU language before processing any DIEs (symtab/23010 et al)

This patch is another attempt at really fixing the multitude of assertions
being seen where symbols of one language are being added to symbol lists of
another language.

In this specific case, the backtrace command (thread apply all bt full) that
is looking for the compunit containing the PC of the thread. That calls
get_prev_frame several times. This function calls (eventually)
dwarf2_frame_prev_register. That eventually ends up calling
find_pc_compunit_symtab.

In this function (find_pc_sect_compunit_symtab actually), we loop over all
compunits, calling the "quick" function dw2_find_pc_sect_compunit_symtab.
That function calls dw2_instantiate_symtab to read in all the CU's symbols.
Now the fun begins.

dw2_do_instantiate_symtab queues the per_cu for reading, using a default
"pretend" language of language_minimal with the expectation that this will
be set later.

The DIEs of this (only queued) CU are then processed.

The first DIE is DW_TAG_compile_unit. That's handled by read_file_scope.

(Nearly) The first thing read_file_scope does is:

  get_scope_pc_bounds (die, &lowpc, &highpc, cu);

This function loops over the children of the current DIE (a compile_unit),
looking for bounds. The first such child is a subprogram, and we attempt to
get its bounds. We use dwarf2_attr to get at DW_AT_high_pc.

This subprogram has DW_AT_specification set, so dwarf_attr (via
follow_die_ref/follow_die_offset) will follow that, but follow_die_offset
*also* attempts to load the containing CU for the spec DIE. That spec DIE
lives inside a CU that is a partial_unit and has no language attribute. So
it simply inherits the language from the CU that elicited the read. [That
all happens in follow_die_offset.]

The original CU's language is still language_minimal -- we haven't gotten to
the line in read_file_scope that actually sets the language yet!

And that is the cause of these problems. The call to prepare_one_comp_unit
needs to be the *first* thing that is done when reading a CU so that the
CU's language can be recorded (and inherited by any referenced
partial_units).

Since a test reproducer for this has been so elusive, this patch also adds a
wrapper function around add_symbol_to_list which asserts when adding a
symbol of one language to a list containing symbols of a different language.

gdb/ChangeLog:
2017-07-24  Keith Seitz  <keiths@redhat.com>

        PR symtab/23010
        * dwarf2read.c (dw2_add_symbol_to_list): New function.
        (fixup_go_packaging, new_symbol): Use dw2_add_symbol_to_list
        instead of add_symbol_to_list.
        (read_file_scope): Call prepare_one_comp_unit before reading
        any other DIEs.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix indentation in scoped_mmap.h
@ 2018-07-24 18:49 sergiodj+buildbot
  2018-08-30  7:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-24 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b17aefe753a8d62ccd491b6a39dabdc69e91445 ***

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

Fix indentation in scoped_mmap.h

gdb/ChangeLog:

	* common/scoped_mmap.h (class scoped_mmap): Fix indentation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove some unnecessary declarations and configury
@ 2018-07-24 17:47 sergiodj+buildbot
  2018-08-30  7:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-24 17:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29d17e4773334ae60ffac7ea7f92d507c23b70f6 ***

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

Remove some unnecessary declarations and configury

configure checks for declarations of free, malloc, and realloc; but
the results are only used in a single spot: utils.c.  I think these
checks are long since obsolete, so this patch removes them.

Grepping the entire tree for these HAVE_DECL_ symbols, the only uses
of possible interest to gdb come from bfd/sysdep.h; but this is not
(nor should be) included by gdb.  (And furthermore I think the code
there is probably also obsolete.)

gdb/ChangeLog
2018-07-24  Tom Tromey  <tom@tromey.com>

	* utils.c (malloc, realloc, free): Don't declare.
	* configure, config.in: Rebuild.
	* configure.ac: Don't check for declarations of free, malloc, or
	realloc.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] xtensa: move dynamic relocations sections consistency check
@ 2018-07-23 19:36 sergiodj+buildbot
  2018-08-30  2:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-23 19:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f82863d797e461b936dff2b659a3aa65088ee87e ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: f82863d797e461b936dff2b659a3aa65088ee87e

xtensa: move dynamic relocations sections consistency check

The function elf_xtensa_finish_dynamic_sections checks that sizes of
sections .rela.dyn and .rela.plt match number of corresponding relocation
records, but the check is only done when .rela.plt is non-empty, so, e.g.
it is never run for the static PIE.
Rearrange the test so that .rela.dyn and .rela.plt are checked always.

bfd/
2018-07-23  Max Filippov  <jcmvbkbc@gmail.com>

	* elf32-xtensa.c (elf_xtensa_finish_dynamic_sections): Move
	relocation sections consistency check to always check both
	.rela.dyn and .rela.plt when they exist. Rearrange variable
	definition and assignment places.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARC] Allow vewt instruction for ARC EM family.
@ 2018-07-23 19:26 sergiodj+buildbot
  2018-08-30  1:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-23 19:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 47e6f81c7c269ab5ef2b3004bb5ebe0de5cfb969 ***

Author: Claudiu Zissulescu <claziss@gmail.com>
Branch: master
Commit: 47e6f81c7c269ab5ef2b3004bb5ebe0de5cfb969

[ARC] Allow vewt instruction for ARC EM family.

opcode/
  Claudiu Zissulescu  <claziss@synopsys.com>

	* arc-tbl.h (vewt): Allow it for ARC EM family.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid ubsan complaint in BFD
@ 2018-07-23 14:29 sergiodj+buildbot
  2018-08-30  2:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-23 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 01bcaf636ad0b1d5fe44a21917ec900af86072a8 ***

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

Avoid ubsan complaint in BFD

I built gdb with ubsan and ran the test suite.

One complaint was due to bfd_get_elf_phdrs passing NULL to memcpy.
This patch avoids the complaint.

bfd/ChangeLog
2018-07-23  Tom Tromey  <tom@tromey.com>

	* elf.c (bfd_get_elf_phdrs): Don't call memcpy with size 0.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] S/390: Suppress string diagnostics for pre-release GCC
@ 2018-07-23  9:02 sergiodj+buildbot
  2018-08-30  0:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-23  9:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 898ade12ee835c3a55460ae4fe311f40a01cf586 ***

Author: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Branch: master
Commit: 898ade12ee835c3a55460ae4fe311f40a01cf586

S/390: Suppress string diagnostics for pre-release GCC

Building for S/390 currently fails when using a GCC 8.1 pre-release
version like 8.0.1 (as it is used by F28).  Fixed with the attached patch.

bfd/ChangeLog:

2018-07-23  Andreas Krebbel  <krebbel@linux.ibm.com>

	* elf32-s390.c (elf_s390_write_core_note): Make GCC version 8.0 to
	be covered by the check as well.
	* elf64-s390.c (elf_s390_write_core_note): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] power9 mfupmc/mtupmc
@ 2018-07-23  4:05 sergiodj+buildbot
  2018-08-29 23:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-23  4:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb71536f2841449252952ac4f759c1e0eca7e137 ***

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

power9 mfupmc/mtupmc

	PR 23419
	* ppc-opc.c (powerpc_opcodes): Add mtupmc/mfupmc/mfpmc extended
	opcode variants for mtspr/mfspr encodings.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove some unused variables
@ 2018-07-23  3:41 sergiodj+buildbot
  2018-08-29 22:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-23  3:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf4088a92f240b01e6db8f39a5a3abfa918f6f2c ***

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

Remove some unused variables

Found using the newly-enabled -Wunused-variable.

gdb/ChangeLog:

	* aarch64-linux-nat.c
	(aarch64_linux_nat_target::stopped_data_address): Remove unused
	variable.
	* arm-linux-nat.c (fetch_regs): Likewise.
	(store_regs): Likewise.
	(fetch_vfp_regs): Likewise.
	(store_vfp_regs): Likewise.
	(arm_linux_nat_target::insert_hw_breakpoint): Likewise.
	(arm_linux_nat_target::remove_hw_breakpoint): Likewise.
	(arm_linux_nat_target::insert_watchpoint): Likewise.
	(arm_linux_nat_target::remove_watchpoint): Likewise.
	* mips-linux-nat.c (mips_linux_nat_target::insert_watchpoint):
	Likewise.
	* nat/aarch64-sve-linux-ptrace.c (aarch64_sve_get_sveregs):
	Likewise.
	* ppc-linux-nat.c (fetch_register): Likewise.
	(fetch_all_gp_regs): Likewise.
	(fetch_ppc_registers): Likewise.
	(store_all_gp_regs): Likewise.
	(store_ppc_registers): Likewise.
	(hwdebug_insert_point): Likewise.
	(can_use_watchpoint_cond_accel): Likewise.
	* remote-sim.c (gdb_os_write_stdout): Likewise.

gdb/gdbserver/ChangeLog:

	* linux-mips-low.c (mips_collect_ptrace_register): Remove unused
	variable.
	(mips_supply_ptrace_register): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use a previously unused variable in bfin-tdep.c
@ 2018-07-22 23:44 sergiodj+buildbot
  2018-08-29 16:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 23:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 996d693a07973411897103a36e89bccee6c94479 ***

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

Use a previously unused variable in bfin-tdep.c

This changes bfin_push_dummy_call to use the result of check_typedef.
Calling check_typedef for effect was probably ok as well, but this
seemed a little nicer.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* bfin-tdep.c (bfin_push_dummy_call): Use arg_type, not
	value_type.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Conditionally define xmltarget_${name} variable in regdat.sh
@ 2018-07-22 22:07 sergiodj+buildbot
  2018-08-29 21:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 22:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3b20124b3d6df31b5bde0f6bcd718cc40de8d49b ***

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

Conditionally define xmltarget_${name} variable in regdat.sh

This changes regdat.sh to emit the xmltarget_${name} variable inside
the #ifndef IN_PROCESS_AGENT block.  This avoids a -Wunused-variable
warning for some builds.  Thanks to Pedro for investigating this one.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* regformats/regdat.sh: Define xmltarget_${name} inside
	#ifndef IN_PROCESS_AGENT.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unused declaration from value.c
@ 2018-07-22 21:41 sergiodj+buildbot
  2018-08-29 20:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c8807f43924ec0f936b9bb59fd73d8fa4956e9e ***

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

Remove unused declaration from value.c

This removes an unused declaration from value_fetch_lazy_bitfield.
Because it is not completely clear if the check_typedef call is needed
somewhere beneath this function, this is broken out into a separate
patch.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* value.c (value_fetch_lazy_bitfield): Remove unused variable.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix ravenscar-thread.c to use arch_ops
@ 2018-07-22 21:17 sergiodj+buildbot
  2018-08-29 19:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 21:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 494f80a9321dccb939bf39afed66649702b563fe ***

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

Fix ravenscar-thread.c to use arch_ops

The change to turn target ops into methods accidentally introduced a
bug in ravenscar-thread.c, changing some calls that were using
"arch_ops" to use the target beneath.

This patch changes ravenscar-thread.c to use these variables where
appropriate.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* ravenscar-thread.c (ravenscar_thread_target::store_registers):
	Use arch_ops.
	(ravenscar_thread_target::prepare_to_store): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Call some functions in guile/ for effect
@ 2018-07-22 20:37 sergiodj+buildbot
  2018-08-29 17:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 20:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5e9a511c4bbb25a7e6844169aa9e5b3fc7ef453 ***

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

Call some functions in guile/ for effect

This changes a couple of spots in guile/ to remove a variable
declaration but to still call a function for effect.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* guile/scm-cmd.c (gdbscm_dont_repeat): Call
	cmdscm_get_valid_command_smob_arg_unsafe for effect.
	* guile/scm-block.c (gdbscm_make_block_syms_iter): Call
	bkscm_get_valid_block_smob_arg_unsafe for effect.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove an unused variable from spu_get_overlay_table
@ 2018-07-22 19:59 sergiodj+buildbot
  2018-08-29 15:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 19:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f4e80e1301f916ae7952abaf4ff1ebeac00951b3 ***

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

Remove an unused variable from spu_get_overlay_table

This removes an unused variable from spu_get_overlay_table, replacing
it with an explanatory comment.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* spu-tdep.c (spu_get_overlay_table): Remove unused variable.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Simple unused variable removals
@ 2018-07-22 19:46 sergiodj+buildbot
  2018-07-22 19:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22 19:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d49165d8382e29bff8d60d208934596e3994305 ***

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

Simple unused variable removals

This patch holds all the straightforward unused variable deletions.

gdb/ChangeLog
2018-07-22  Tom Tromey  <tom@tromey.com>

	* guile/scm-value.c (gdbscm_value_call): Remove unused variables.
	* guile/scm-math.c (vlscm_unop_gdbthrow, vlscm_binop_gdbthrow)
	(vlscm_convert_typed_value_from_scheme): Remove unused variable.
	* buildsym-legacy.c (get_macro_table): Remove unused variable.
	* stack.c (frame_apply_level_command): Remove unused variable.
	* tic6x-tdep.c (tic6x_push_dummy_call): Remove unused variable.
	* sparc64-tdep.c (adi_examine_command): Remove unused variable.
	* rs6000-lynx178-tdep.c (rs6000_lynx178_push_dummy_call): Remove
	unused variable.
	* nios2-tdep.c (nios2_push_dummy_call): Remove unused variable.
	* mep-tdep.c (mep_push_dummy_call): Remove unused variable.
	* ada-lang.c (ada_lookup_symbol_list_worker): Remove unused
	variable.
	* amd64-tdep.c (amd64_supply_xsave): Remove unused variable.
	* arm-tdep.c (arm_record_data_proc_misc_ld_str): Remove unused
	variable.
	* breakpoint.c (check_no_tracepoint_commands, update_watchpoint):
	Remove unused variable.
	* cli/cli-script.c (recurse_read_control_structure): Remove unused
	variable.
	* common/tdesc.c (print_xml_feature::visit): Remove unused
	variable.
	* compile/compile-object-load.c (store_regs): Remove unused
	variables.
	* complaints.c (clear_complaints): Remove unused variable.
	* corelow.c (core_target_open): Remove unused variable.
	* fbsd-tdep.c (fbsd_core_info_proc_status): Remove unused
	variable.
	* guile/scm-frame.c (gdbscm_frame_read_var): Remove unused
	variable.
	* guile/scm-symtab.c (stscm_print_sal_smob): Remove unused
	variable.
	* guile/scm-type.c (gdbscm_field_baseclass_p): Remove unused
	variable.
	* guile/scm-utils.c (gdbscm_parse_function_args): Remove unused
	variable.
	* hppa-tdep.c (hppa_stub_frame_unwind_cache): Remove unused
	variable.
	* ia64-tdep.c (examine_prologue): Remove unused variable.
	* infcall.c (run_inferior_call): Remove unused variable.
	* inferior.c (exit_inferior): Remove unused variable.
	* infrun.c (infrun_thread_ptid_changed): Remove unused variable.
	* linespec.c (decode_line_2): Remove unused variable.
	* linux-nat.c (super_close): Remove.
	* linux-tdep.c (linux_info_proc): Remove unused variable.
	* mi/mi-main.c (mi_execute_command): Remove unused variable.
	* microblaze-linux-tdep.c (microblaze_linux_sigtramp_cache):
	Remove unused variable.
	* parse.c (find_minsym_type_and_address): Remove unused variable.
	* printcmd.c (info_symbol_command, printf_floating): Remove unused
	variable.
	* python/py-breakpoint.c (bppy_set_commands): Remove unused
	variable.
	* python/py-unwind.c (unwind_infopy_dealloc): Remove unused
	variables.
	* record-btrace.c (record_btrace_target::store_registers): Remove
	unused variable.
	(cmd_show_record_btrace_cpu): Remove unused variable.
	* riscv-tdep.c (riscv_register_reggroup_p)
	(riscv_push_dummy_call, riscv_return_value): Remove unused
	variable.
	* rust-exp.y (literal): Remove unused variable.
	* rust-lang.c (rust_evaluate_subexp) <OP_RUST_ARARAY>: Remove
	unused variable.
	<STRUCTOP_ANONYMOUS>: Likewise.
	* s390-linux-tdep.c (s390_linux_init_abi_31)
	(s390_linux_init_abi_64): Remove unused variable.
	* ser-ming2.c (ser_windows_read_prim, pipe_select_thread)
	(file_select_thread, net_windows_open, _initialize_ser_windows):
	Remove unused variables.
	* symtab.c (find_pc_sect_line): Remove unused variable.
	* target-memory.c (compute_garbled_blocks): Remove unused
	variable.
	(target_write_memory_blocks): Remove unused variable.
	* target.c (target_stack::unpush): Remove unused variables.
	* tracepoint.c (start_tracing, all_tracepoint_actions)
	(merge_uploaded_trace_state_variables)
	(print_one_static_tracepoint_marker): Remove unused variable.
	* unittests/basic_string_view/element_access/char/1.cc (test01):
	Remove unused variable.
	* windows-nat.c (windows_continue, windows_add_all_dlls)
	(do_initial_windows_stuff, windows_nat_target::create_inferior):
	Remove unused variables.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix -Wunused-variable warnings related to conditional compilation
@ 2018-07-22  2:41 sergiodj+buildbot
  2018-07-22  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-22  2:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17cbafdbbef78d7e05ade53d4cc867fa8ac2f432 ***

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

Fix -Wunused-variable warnings related to conditional compilation

Some variables are not used when !HAVE_ELF, so avoid declaring them in
that case.

gdb/ChangeLog:

	* arm-tdep.c (arm_gdbarch_init): Declare attr_arch and
	attr_profile in HAVE_ELF.
	* rs6000-tdep.c (bfd_uses_spe_extensions): Declare vector_abi in
	HAVE_ELF.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Initialize GOT slot for local symbol in non-PIC link.
@ 2018-07-21 13:17 sergiodj+buildbot
  2018-07-21 13:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-21 13:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2376f038d10f901d3e1a2777407f350e4e54d284 ***

Author: Eric Botcazou <ebotcazou@gcc.gnu.org>
Branch: master
Commit: 2376f038d10f901d3e1a2777407f350e4e54d284

Initialize GOT slot for local symbol in non-PIC link.

On ARM/VxWorks 7, the R_ARM_TARGET2 relocation used for exception handling
is R_ARM_GOT_PREL; moreover in Ada you can define local exceptions. In this
case, you may end up with a GOT relocation against a local symbol in a
non-PIC link and the ARM linker leaves the GOT slot uninitialized, unlike
for example the i386 or the SPARC linkers in the same situation.

bfd/
	* elf32-arm.c (elf32_arm_final_link_relocate) <R_ARM_GOT32>: Small
	cleanup for the case of a global symbol that binds locally.  Also
	install a value in the GOT slot in the case of a local symbol in
	a non-PIC link.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/Linux/native: Convert to `get_ptrace_pid' for PID extraction
@ 2018-07-21  3:46 sergiodj+buildbot
  2018-07-21  3:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-21  3:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2d38991535ecfcd092f3c57da84844efc3d49877 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 2d38991535ecfcd092f3c57da84844efc3d49877

MIPS/Linux/native: Convert to `get_ptrace_pid' for PID extraction

Use `get_ptrace_pid' to get the ptrace PID from `inferior_ptid' rather
than extracting it by hand.

	gdb/
	* mips-linux-nat.c (mips_linux_nat_target::read_description):
	Call `get_ptrace_pid' rather than extracting the ptrace PID by
	hand.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Rename some frame unwind function parameters
@ 2018-07-21  2:36 sergiodj+buildbot
  2018-07-21  4:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-21  2:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ee6c332f36222a73abee41bc5168bacf78c9189 ***

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

Rename some frame unwind function parameters

I am currently working with these functions, and though this renaming
could help to reason about the code.  Some functions take a frame and
will return the value associated to that frame, others will return the
value associated to the previous frame.  Those usually conveniently
contain "unwind" in their name, but naming the variable next_frame
instead of frame helps remembering which frame we are dealing with.

I also included a little typo fix at the top of frame.h.

gdb/ChangeLog:

	* frame.c (frame_register_unwind): Change parameter name.
	(frame_unwind_register): Likewise.
	(frame_unwind_register_value): Likewise.
	(frame_unwind_register_signed): Likewise.
	(frame_unwind_register_unsigned): Likewise.
	* frame.h (frame_register_unwind): Likewise.
	(frame_unwind_register): Likewise.
	(frame_unwind_register_value): Likewise.
	(frame_unwind_register_signed): Likewise.
	(frame_unwind_register_unsigned): Likewise.
	(frame_unwind_arch): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove record_line_ftype
@ 2018-07-21  2:18 sergiodj+buildbot
  2018-07-21  2:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-21  2:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfe2e011c004b88687ae4514cfdb00072a9cee63 ***

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

Remove record_line_ftype

The record_line_ftype typedef was only used in the DWARF reader, and
we removed those uses a few patches ago.  So, remove the typedef.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym-legacy.h (record_line): Don't use record_line_ftype.
	* buildsym.h (record_line_ftype): Remove typedef.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Introduce buildsym-legacy.h
@ 2018-07-21  0:39 sergiodj+buildbot
  2018-07-21  0:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-21  0:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0baae8dbd38534c0f3dcedc7b9204bbc8f18de1b ***

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

Introduce buildsym-legacy.h

This introduces a new header, buildsym-legacy.h, and changes all the
symbol readers to use it.  The idea is to put the function-based
interface, that relies on the buildsym_compunit global, into a
separate header.  Then when a symbol reader is updated to use the new
interface, it can simply not include buildsym-legacy.h, so it's easy
to be sure that the new API is used everywhere.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* xcoffread.c: Include buildsym-legacy.h.
	* windows-nat.c: Include buildsym-legacy.h.
	* stabsread.c: Include buildsym-legacy.h.
	* mdebugread.c: Include buildsym-legacy.h.
	* buildsym-legacy.h: New file.
	* buildsym-legacy.c: New file, from buildsym.c.
	* go32-nat.c: Include buildsym-legacy.h.
	* dwarf2read.c: Include buildsym-legacy.h.
	* dbxread.c: Include buildsym-legacy.h.
	* cp-namespace.c: Include buildsym-legacy.h.
	* coffread.c: Include buildsym-legacy.h.
	* buildsym.h: Move some contents to buildsym-legacy.h.
	* buildsym.c: Include buildsym-legacy.h.  Move many functions to
	buildsym-legacy.c.
	* Makefile.in (HFILES_NO_SRCDIR): Add buildsym-legacy.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove reset_symtab_globals
@ 2018-07-20 23:54 sergiodj+buildbot
  2018-07-20 23:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 23:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 74c72eac237232e9c23c2b4e21d24941d804dae9 ***

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

Remove reset_symtab_globals

This patch arranges for the remaining buildsym global --
buildsym_compunit -- to only be cleared by the wrapper functions, not
by methods on struct buildsym_compunit.  In the process,
reset_symtab_globals is removed.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym.c (reset_symtab_globals): Remove.
	(buildsym_compunit::end_symtab_from_static_block): Update.
	(buildsym_compunit::augment_type_symtab): Update.
	(end_symtab_from_static_block): Call free_buildsym_compunit.
	(augment_type_symtab, end_symtab, end_expandable_symtab):
	Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Add a GNU_PROPERTY_X86_ISA_1_USED note if needed
@ 2018-07-20 21:34 sergiodj+buildbot
  2018-07-21  3:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 241e64e3b42cd9eba514b8e0ad2ef39a337f10a5 ***

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

x86: Add a GNU_PROPERTY_X86_ISA_1_USED note if needed

When -z separate-code, which is enabled by default for Linux/x86, is
used to create executable, ld won't place any data in the code-only
PT_LOAD segment.  If there are no data sections placed before the
code-only PT_LOAD segment, the program headers won't be mapped into
any PT_LOAD segment.  When the executable tries to access it (based
on the program header address passed in AT_PHDR), it will lead to
segfault.  This patch inserts a GNU_PROPERTY_X86_ISA_1_USED note if
there may be no data sections before the text section so that the
first PT_LOAD segment won't be code-only and will contain the program
header.

Testcases are adjusted to either pass "-z noseparate-code" to ld or
discard the .note.gnu.property section.  A Linux/x86 run-time test is
added.

bfd/

	PR ld/23428
	* elfxx-x86.c (_bfd_x86_elf_link_setup_gnu_properties): If the
	separate code program header is needed, make sure that the first
	read-only PT_LOAD segment has no code by adding a
	GNU_PROPERTY_X86_ISA_1_USED note.

ld/

	PR ld/23428
	* testsuite/ld-elf/linux-x86.S: New file.
	* testsuite/ld-elf/linux-x86.exp: Likewise.
	* testsuite/ld-elf/pr23428.c: Likewise.
	* testsuite/ld-elf/sec64k.exp: Pass "-z noseparate-code" to ld
	for Linux/x86 targets.
	* testsuite/ld-i386/abs-iamcu.d: Likewise.
	* testsuite/ld-i386/abs.d: Likewise.
	* testsuite/ld-i386/pr12718.d: Likewise.
	* testsuite/ld-i386/pr12921.d: Likewise.
	* testsuite/ld-x86-64/abs-k1om.d: Likewise.
	* testsuite/ld-x86-64/abs-l1om.d: Likewise.
	* testsuite/ld-x86-64/abs.d: Likewise.
	* testsuite/ld-x86-64/pr12718.d: Likewise.
	* testsuite/ld-x86-64/pr12921.d: Likewise.
	* testsuite/ld-linkonce/zeroeh.ld: Discard .note.gnu.property
	section.
	* testsuite/ld-scripts/print-memory-usage.t: Likewise.
	* testsuite/ld-scripts/size-2.t: Likewise.
	* testsuite/lib/ld-lib.exp (run_ld_link_exec_tests): Use ld
	to create executable if language is "asm".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Rename remaining members of buildsym_compunit to start with "m_"
@ 2018-07-20 21:21 sergiodj+buildbot
  2018-07-21  2:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cbb09508e4b515501273288aaa11a8ef5e15e0ff ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: cbb09508e4b515501273288aaa11a8ef5e15e0ff

Rename remaining members of buildsym_compunit to start with "m_"

This renames all the remaining members of buildsym_compunit to start
with "m_" to follow the general naming convention.

gdb/ChangeLog
2018-07-20  Keith Seitz  <keiths@redhat.com>

	* buildsym.h (struct buildsym_compunit) <m_objfile, m_subfiles,
	m_main_subfile, m_comp_dir, m_producer, m_debugformat,
	m_compunit_symtab, m_language>: Add "m_" prefix.
	Update all uses.
	* buildsym.c: Update all uses.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove some unused buildsym functions
@ 2018-07-20 20:57 sergiodj+buildbot
  2018-07-21  1:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 20:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e6f30610fdb50b4974b349ed3673b744d03e9a9 ***

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

Remove some unused buildsym functions

Now that the DWARF reader uses the builder-based API, we can remove a
few "legacy" functions that were only ever called by it.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym-legacy.h (augment_type_symtab): Don't declare.
	(end_expandable_symtab): Likewise.
	(end_symtab_get_static_block): Likewise.
	(end_symtab_from_static_block): Likewise.
	* buildsym-legacy.c (augment_type_symtab): Remove.
	(end_expandable_symtab): Remove.
	(end_symtab_get_static_block): Remove.
	(end_symtab_from_static_block): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Convert the DWARF reader to new-style buildysm
@ 2018-07-20 20:45 sergiodj+buildbot
  2018-07-21  1:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 20:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 804d27291b2922f01fe5cc2d9ae759533d4a2f6f ***

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

Convert the DWARF reader to new-style buildysm

This converts the DWARF reader to use the new-style buildsym API.  A
new buildsym_compunit is created for each CU and is used to construct
the symbol table.  In some cases the CU must be passed to functions
which previously did not accept it.  FWIW I tend to think that most
methods in the DWARF reader ought to be methods on the dwarf2_cu
object.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c: Include buildsym.h.
	(struct dwarf2_cu) <builder>: New method.
	(fixup_go_packaging): Update.
	(process_full_comp_unit, process_full_type_unit): Update.  Don't
	use scoped_free_pendings.
	(using_directives): Add "cu" parameter, remove "language".
	(read_import_statement, setup_type_unit_groups, )
	(read_func_scope, read_lexical_block_scope)
	(dwarf2_record_block_ranges, read_namespace): Update.
	(lnp_state_machine::lnp_state_machine): Add cu parameter.
	(lnp_state_machine::handle_end_sequence): Update.
	(class lnp_state_machine) <m_cu>: New member.
	<m_record_line_callback>: Remove.
	<m_currently_recording_lines>: New member.
	(lnp_state_machine::handle_set_file): Update.
	(noop_record_line): Remove.
	(dwarf_record_line_p): Add cu parameter.
	(dwarf_record_line_1, dwarf_finish_line): Likewise.
	(lnp_state_machine::record_line)
	(lnp_state_machine::lnp_state_machine)
	(lnp_state_machine::check_line_address, dwarf_decode_lines_1)
	(dwarf_decode_lines): Update.
	(dwarf2_start_subfile): Add cu parameter.
	(dwarf2_start_symtab, new_symbol): Update.
	(macro_start_file, dwarf_decode_macro_bytes): Add cu parameter.
	Remove dwarf2_per_objfile parameter.
	(dwarf_decode_macros): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Parameterize cp_scan_for_anonymous_namespaces
@ 2018-07-20 20:33 sergiodj+buildbot
  2018-07-21  1:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 20:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 80e649fcac86101a8a4581317e867e89de015d28 ***

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

Parameterize cp_scan_for_anonymous_namespaces

This changes cp_scan_for_anonymous_namespaces to use the
buildsym_compunit API, rather than the function-based API.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* stabsread.c (define_symbol): Update.
	* buildsym-legacy.h (get_buildsym_compunit): Declare.
	* dwarf2read.c (new_symbol): Update.
	* cp-support.h (cp_scan_for_anonymous_namespaces): Update.
	* cp-namespace.c: Include buildsym.h.
	(cp_scan_for_anonymous_namespaces): Add "compunit" parameter.
	* buildsym-legacy.c (get_buildsym_compunit): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move struct buildsym_compunit to buildsym.h
@ 2018-07-20 20:08 sergiodj+buildbot
  2018-07-21  0:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 20:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab209f6fa9dbaf0d3d0c42e2a8f14bf3ff7dfce8 ***

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

Move struct buildsym_compunit to buildsym.h

This moves struct buildsym_compunit to buildsym.h.  Now that the
members are private, and it no longer affects any global state in
buildsym.c, an instance can be used directly for symtab creation.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym.h (struct buildsym_compunit): Move from buildsym.c.
	* buildsym.c (struct buildsym_compunit): Move to buildsym.h.
	(buildsym_compunit::buildsym_compunit)
	(buildsym_compunit::~buildsym_compunit)
	(buildsym_compunit::get_macro_table): Define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Do not use buildsym.h in some files
@ 2018-07-20 19:44 sergiodj+buildbot
  2018-07-20 23:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 19:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da6580e59c5c2c5dda086f9c407688e79377e49e ***

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

Do not use buildsym.h in some files

A few files no longer need to include buildsym.h.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* arch-utils.c: Do not include buildsym.h.
	* mipsread.c: Do not include buildsym.h.
	* machoread.c: Do not include buildsym.h.
	* elfread.c: Do not include buildsym.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove parameter from record_pending_block
@ 2018-07-20 19:20 sergiodj+buildbot
  2018-07-20 22:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 19:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b213a4778fae60d40257aee37c3fdec837ea574 ***

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

Remove parameter from record_pending_block

This removes a redundant parameter from record_pending_block.  It also
moves record_pending_block earlier in the file, so that a forward
declaration is no longer needed.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym.c (record_pending_block): Move earlier.  Remove objfile
	parameter.
	(finish_block_internal): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove the "listhead" argument from finish_block
@ 2018-07-20 18:36 sergiodj+buildbot
  2018-07-20 18:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c233e9c641a84e69603bd94d0e85050c361b64a6 ***

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

Remove the "listhead" argument from finish_block

finish_block is only ever called with "&local_symbols" as the
"listhead" argument.  So, remove this argument.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* xcoffread.c (read_xcoff_symtab): Update.
	* dwarf2read.c (read_func_scope, read_lexical_block_scope):
	Update.
	* dbxread.c (process_one_symbol): Update.
	* coffread.c (coff_symtab_read): Update.
	* buildsym.h (finish_block): Update.
	* buildsym.c (finish_block): Remove "listhead" argument.
	(end_symtab_get_static_block): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove buildsym_init
@ 2018-07-20 18:23 sergiodj+buildbot
  2018-07-20 21:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 18:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b37dd3bcaac70cede547ba41fdac7878a0f4c67e ***

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

Remove buildsym_init

Now that buildsym_init does nothing, it can be removed.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* coffread.c (coff_symtab_read): Update.
	* xcoffread.c (xcoff_psymtab_to_symtab_1): Update.
	(xcoff_new_init): Update.
	* mipsread.c (mipscoff_new_init): Update.
	* mdebugread.c (mdebug_build_psymtabs): Update.
	* elfread.c (elf_new_init): Update.
	* dwarf2read.c (process_full_comp_unit, process_full_type_unit):
	Update.
	* dbxread.c (dbx_new_init, dbx_psymtab_to_symtab_1)
	(coffstab_build_psymtabs, elfstab_build_psymtabs)
	(stabsect_build_psymtabs): Update.
	* buildsym.h (buildsym_init): Don't declare.
	* buildsym.c: Update comment.
	(prepare_for_building): Remove.
	(start_symtab, restart_symtab): Update.
	(reset_symtab_globals): Update comment.
	(buildsym_init): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Set list_in_scope later in DWARF reader
@ 2018-07-20 17:58 sergiodj+buildbot
  2018-07-20 20:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 17:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 93b8bea4143cafae79076076c64aaa4c46a9b73c ***

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

Set list_in_scope later in DWARF reader

Currently the DWARF reader sets the list_in_scope member of the CU
when first starting to process symbols.  Future changes will make this
assert -- code will not be able to refer to these lists until after
start_symtab has been called.  This patch prepares for the problem by
arranging to initialize list_in_scope in dwarf2_start_symtab.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (process_full_comp_unit): Do not set list_in_scope.
	(process_full_type_unit): Likewise.
	(dwarf2_start_symtab): Set list_in_scope.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move pending_blocks and pending_block_obstack to buildsym_compunit
@ 2018-07-20 16:47 sergiodj+buildbot
  2018-07-20 17:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ac045503de7dde6793b318f89d251addc161f66 ***

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

Move pending_blocks and pending_block_obstack to buildsym_compunit

This moves the pending_blocks and pending_block_obstack into
buildsym_compunit.

The obstack could perhaps be merged with the addrmap obstack, but I
did not do that in this series.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym.h (class scoped_free_pendings): Remove constructor.
	* buildsym.c (struct buildsym_compunit) <free_pending_blocks>: New
	method.
	<m_pending_block_obstack, m_pending_blocks>: New members.
	(pending_block_obstack, pending_blocks): Remove.
	(scoped_free_pendings::scoped_free_pendings): Default.
	(~scoped_free_pendings): Update.
	(free_pending_blocks): Remove.
	(finish_block_internal, record_pending_block, make_blockvector)
	(end_symtab_get_static_block, augment_type_symtab, push_context)
	(buildsym_init): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move pending addrmap globals to buildsym_compunit
@ 2018-07-20 16:34 sergiodj+buildbot
  2018-07-20 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ea05a7b634a895128e87c8c71e8e611758cd4bb ***

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

Move pending addrmap globals to buildsym_compunit

This moves the pending addrmap-related globals into buildsym_compunit.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* buildsym.c (struct buildsym_compunit) <m_pending_addrmap,
	m_pending_addrmap_obstack, m_pending_addrmap_interesting>: New
	members.
	(pending_addrmap, pending_addrmap_obstack)
	(pending_addrmap_interesting): Remove.
	(scoped_free_pendings, record_block_range, make_blockvector)
	(prepare_for_building, reset_symtab_globals, buildsym_init):
	Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move current_subfile to buildsym_compunit
@ 2018-07-20 16:23 sergiodj+buildbot
  2018-07-20 17:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 16:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c65e5b31cb5587773deff979099435b9687a0f4 ***

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

Move current_subfile to buildsym_compunit

This moves the global current_subfile into buildsym_compunit.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* xcoffread.c (process_linenos): Update.
	* stabsread.c (define_symbol, read_type, read_enum_type): Update.
	* mdebugread.c (psymtab_to_symtab_1): Update.
	* dwarf2read.c (setup_type_unit_groups)
	(lnp_state_machine::handle_set_file, dwarf_record_line_p)
	(lnp_state_machine::record_line, dwarf_decode_lines): Update.
	* dbxread.c (process_one_symbol): Update.
	* coffread.c (coff_symtab_read, enter_linenos)
	(process_coff_symbol): Update.
	* buildsym.h (current_subfile): Don't declare.
	(get_current_subfile): Declare.
	* buildsym.c (struct buildsym_compunit) <m_current_subfile>: New
	member.
	(start_subfile, free_buildsym_compunit, push_subfile)
	(prepare_for_building, start_symtab): Update.
	(get_current_subfile): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make the Rust parser pure
@ 2018-07-20 15:57 sergiodj+buildbot
  2018-07-20 16:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 56ba65a04713fd8ff23908d4c57f75427317b8bb ***

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

Make the Rust parser pure

This makes the Rust parser a pure parser and removes all the
(non-constant) globals from rust-exp.y.  This seemed like a nice
simplification to me and I think it should probably be applied to all
the parsers.  Perhaps it would be good to go even one step farther and
have all parsers derive from parser_state.

Tested on x86-64 Fedora 26.

gdb/ChangeLog
2018-07-20  Tom Tromey  <tom@tromey.com>

	* rust-exp.y: Now a pure parser.  Update all rules.
	(%union): Move earlier.
	(current_parser, work_obstack): Remove globals.
	(rust_parser, ~rust_parser): Update.
	(class rust_parser) <copy_name, concat3, crate_name, super_name,
	lex_character, lex_number, lex_string, lex_identifier,
	rust_lookup_type, convert_params_to_types, convert_ast_to_type,
	convert_name, convert_params_to_expression,
	convert_ast_to_expression, ast_basic_type, ast_operation,
	ast_compound_assignment, rust_op, ast_literal, ast_dliteral,
	ast_structop, ast_structop_anonymous, ast_unary, ast_cast,
	ast_call_ish, ast_path, ast_string, ast_struct, ast_range,
	ast_array_type, ast_slice_type, ast_reference_type,
	ast_pointer_type, ast_function_type, ast_tuple_type>: New methods.
	(rust_parse): Update.
	(rustyyerror, rustyylex): Add parser parameter.
	(rust_lex_test_one, rust_lex_int_test, rust_lex_exception_test)
	(rust_lex_stringish_test, rust_lex_test_sequence)
	(rust_lex_test_trailing_dot, rust_lex_test_completion)
	(rust_lex_test_push_back, rust_lex_tests): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Make noclone conditional in vla-optimized-out.c
@ 2018-07-20 15:34 sergiodj+buildbot
  2018-07-20 15:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 232a00325b0f97e108014148c68ae314e90cbb36 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 232a00325b0f97e108014148c68ae314e90cbb36

[gdb/testsuite] Make noclone conditional in vla-optimized-out.c

Make the noclone attribute on f1 in vla-optimized-out.c conditional.  This
makes the test-case by default identical to
gcc/testsuite/gcc.dg/guality/vla-1.c.

Tested on x86_64-linux.

2018-07-20  Tom de Vries  <tdevries@suse.de>

	* gdb.base/vla-optimized-out.c: Make noclone attribute conditional on
	NOCLONE macro.
	* gdb.base/vla-optimized-out.exp: Use additional_flags -DNOCLONE.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/GAS: Split Loongson MMI Instructions from loongson2f/3a
@ 2018-07-20 12:50 sergiodj+buildbot
  2018-07-20 13:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20 12:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8095d2f70e1a982c006f306be1a9e1c892758914 ***

Author: Chenghua Xu <paul.hua.gm@gmail.com>
Branch: master
Commit: 8095d2f70e1a982c006f306be1a9e1c892758914

MIPS/GAS: Split Loongson MMI Instructions from loongson2f/3a

The MMI instruction set has been implemented in many Loongson
processors.  There is a lot of software optimized for MMI.  This patch
splits MMI from loongson2f/3a, and adds GAS and disassembler options for
MMI instructions.

2018-07-20  Chenghua Xu  <paul.hua.gm@gmail.com>
            Maciej W. Rozycki  <macro@mips.com>

bfd/
	* elfxx-mips.c (print_mips_ases): Add MMI extension.

binutils/
	* readelf.c (print_mips_ases): Add MMI extension.

gas/
	* NEWS: Mention MultiMedia extensions Instructions (MMI)
	support.
	* config/tc-mips.c (options): Add OPTION_LOONGSON_MMI and
	OPTION_NO_LOONGSON_MMI.
	(md_longopts): Likewise.
	(mips_ases): Define availability for MMI.
	(mips_convert_ase_flags): Map ASE_LOONGSON_MMI to
	AFL_ASE_LOONGSON_MMI.
	(mips_cpu_info_table): Add ASE_LOONGSON_MMI for loongson2f/3a.
	(md_show_usage): Add help for -mloongson-mmi and
	-mno-loongson-mmi.
	* doc/as.texi: Document -mloongson-mmi, -mno-loongson-mmi.
	* doc/c-mips.texi: Document -mloongson-mmi, -mno-loongson-mmi,
	.set loongson-mmi and .set noloongson-mmi.
	* testsuite/gas/mips/loongson-2f.d: Move mmi test to ...
	* testsuite/gas/mips/loongson-2f-mmi.d: Here.  Add ISA/ASE
	flag verification.
	* testsuite/gas/mips/loongson-2f.s: Move mmi test to ...
	* testsuite/gas/mips/loongson-2f-mmi.s: Here.
	* testsuite/gas/mips/loongson-3a.d: Move mmi test to ...
	* testsuite/gas/mips/loongson-3a-mmi.d: Here.  Add ISA/ASE
	flag verification.
	* testsuite/gas/mips/loongson-3a.s: Move mmi test to ...
	* testsuite/gas/mips/loongson-3a-mmi.s: Here.
	* testsuite/gas/mips/mips.exp: Run loongson-2f-mmi and
	loongson-3a-mmi tests.

include/
	* elf/mips.h (AFL_ASE_MMI): New macro.
	(AFL_ASE_MASK): Update to include AFL_ASE_LOONGSON_MMI.
	* opcode/mips.h (ASE_LOONGSON_MMI): New macro.

opcodes/
	* mips-dis.c (mips_arch_choices): Add MMI to loongson2f and
	loongson3a descriptors.
	(parse_mips_ase_option): Handle -M loongson-mmi option.
	(print_mips_disassembler_options): Document -M loongson-mmi.
	* mips-opc.c (LMMI): New macro.
	(mips_opcodes): Replace IL2F|IL3A marking with LMMI for MMI
	instructions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove myself from target-specific MAINTAINERS
@ 2018-07-20  2:23 sergiodj+buildbot
  2018-07-20  2:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-20  2:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 79f5b65e3e7b10d914b1328ce6e9ad7c9ae39c63 ***

Author: DJ Delorie <dj@redhat.com>
Branch: master
Commit: 79f5b65e3e7b10d914b1328ce6e9ad7c9ae39c63

Remove myself from target-specific MAINTAINERS

[binutils]
	* MAINTAINERS (RL78, RX): Remove myself as maintainer.
[sim]
	* MAINTAINERS (rl78, m32c, rx, v850): Remove myself as maintainer.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove make_cleanup_value_free_to_mark
@ 2018-07-19 16:25 sergiodj+buildbot
  2018-07-19 16:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4581dc8297381651284e2f4a9f835eebcc6f2328 ***

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

Remove make_cleanup_value_free_to_mark

Pedro's patch to introduce gdbscm_wrap removed the last caller of
make_cleanup_value_free_to_mark.  This patch removes this function.

I'm checking this in as obvious.  Tested by rebuilding, and by
grepping.

gdb/ChangeLog
2018-07-19  Tom Tromey  <tom@tromey.com>

	* utils.c (do_value_free_to_mark)
	(make_cleanup_value_free_to_mark): Remove.
	* utils.h (make_cleanup_value_free_to_mark): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Fix regexp in list-thread-groups-available.exp
@ 2018-07-19 15:05 sergiodj+buildbot
  2018-07-19 15:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19 15:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fbb1d502eeae135dbe6ac3b0b122e574a9b888d6 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: fbb1d502eeae135dbe6ac3b0b122e574a9b888d6

[gdb/testsuite] Fix regexp in list-thread-groups-available.exp

I ran into a gdb.mi/list-thread-groups-available.exp failure:
...
Running gdb/testsuite/gdb.mi/list-thread-groups-available.exp ...
FAIL: gdb.mi/list-thread-groups-available.exp:
        list available thread groups (unexpected output)
PASS: gdb.mi/list-thread-groups-available.exp:
        list available thread groups with filter
...
When doing an experiment of running it 100 times in a row, the failure
reproduced 3 times.

Analyzing the original failure led to insufficient quoting of square brackets
in a regexp.  This patch fixes the regexp, which resulted in 0 failures in a
100-in-a-row run.

Tested on x86_64-linux.

2018-07-19  Tom de Vries  <tdevries@suse.de>

	* gdb.mi/list-thread-groups-available.exp (cores_re): Fix quoting in
	regular	expression.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix GDB build using mingw.org's MinGW
@ 2018-07-19 14:29 sergiodj+buildbot
  2018-07-19 14:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19 14:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db3410f80f793189d3c8afb8b80951333d3fe007 ***

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

Fix GDB build using mingw.org's MinGW

libiberty/
2018-07-18  Eli Zaretskii  <eliz@gnu.org>

	PR gdb/23434
	* libiberty/simple-object-elf.c (ENOTSUP): If not defined by
        errno.h, redirect ENOTSUP to ENOSYS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold narrowing VCVT* templates
@ 2018-07-19 10:09 sergiodj+buildbot
  2018-07-19 10:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19 10:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5f32791e1ea970cabd6ca764f1cc282d9e8fef22 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 5f32791e1ea970cabd6ca764f1cc282d9e8fef22

x86: fold narrowing VCVT* templates

When multiple (here: two) forms of an insn take different width inputs
but produce identical size outputs (here: RegXMM), the templates can be
combined.

Also drop IgnoreSize (and the now redundant size specifiers) wherever
applicable.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold various AVX512BW templates
@ 2018-07-19  8:16 sergiodj+buildbot
  2018-07-19  8:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19  8:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8282b7ad0dfaffce380cb668dc2a8ca473758760 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 8282b7ad0dfaffce380cb668dc2a8ca473758760

x86: fold various AVX512BW templates


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold VFPCLASSP{D,S} templates
@ 2018-07-19  8:06 sergiodj+buildbot
  2018-07-19  9:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19  8:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 625cbd7ac121a6df6d237c8368262f6634fb61ab ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 625cbd7ac121a6df6d237c8368262f6634fb61ab

x86: fold VFPCLASSP{D,S} templates

These are special because they may not have a register operand to derive
the vector length from, which requires to also deal with the braodcast
case when determining vector length in build_evex_prefix().

Also drop IgnoreSize (and the now redundant size specifiers) from their
suffixed counterparts.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold various AVX512* templates
@ 2018-07-19  7:54 sergiodj+buildbot
  2018-07-19  9:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19  7:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 86b15c32040ae35c74e84b18f7b65dea94436458 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 86b15c32040ae35c74e84b18f7b65dea94436458

x86: fold various AVX512* templates


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold various AVX512DQ templates
@ 2018-07-19  7:40 sergiodj+buildbot
  2018-07-19  8:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19  7:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf769ed505ed9b3eca24df67bb9cfc0adc1a033f ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: cf769ed505ed9b3eca24df67bb9cfc0adc1a033f

x86: fold various AVX512DQ templates


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold various AVX512CD templates
@ 2018-07-19  7:13 sergiodj+buildbot
  2018-07-19  7:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19  7:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 755908cce568d1cb5f2a3f1cc64472ed43eef8b5 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 755908cce568d1cb5f2a3f1cc64472ed43eef8b5

x86: fold various AVX512CD templates


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: pre-process opcodes table before parsing
@ 2018-07-19  6:47 sergiodj+buildbot
  2018-07-19  6:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-19  6:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c30be56ebf7989e36f5c7d4a703cb00f7d4ca2ab ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: c30be56ebf7989e36f5c7d4a703cb00f7d4ca2ab

x86: pre-process opcodes table before parsing

Instead of expanding macro-like constructs in i386-gen, have the C pre-
processor do this for us. Besides being a prerequisite for the next
template folding steps, this also paves the way for removing various
hidden dependencies between #define-s in i386-opc.h and plain literal
numbers used in i386-opc.tbl.

The #undef of None is solely to leave the generated i386-tbl.h entirely
unchanged.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Eliminate most remaining cleanups under gdb/guile/
@ 2018-07-18 22:37 sergiodj+buildbot
  2018-07-18 22:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-18 22:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 557e56be2648db13cd5d9876f702ba119ee9e7fd ***

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

Eliminate most remaining cleanups under gdb/guile/

The main complication with the Guile code is that we have two types of
exceptions to consider.  GDB/C++ exceptions, and Guile/SJLJ
exceptions.  Code that is facing the Guile interpreter must not throw
GDB exceptions, instead Scheme exceptions must be thrown.  Also,
because Guile exceptions are SJLJ based, Guile-facing code must not
use local objects with dtors, unless wrapped in a scope with a
TRY/CATCH, because the dtors won't otherwise be run when a Guile
exceptions is thrown.

This commit adds a new gdbscm_wrap wrapper function than encapsulates
a pattern I noticed in many of the functions using
GDBSCM_HANDLE_GDB_EXCEPTION_WITH_CLEANUPS.  The wrapper is written
such that you can pass either a lambda to it, or a function plus a
variable number of forwarded args.  I used a lambda when its body
would be reasonably short, and a separate function in the larger
cases.

This also convers a few functions that were using
GDBSCM_HANDLE_GDB_EXCEPTION to use gdbscm_wrap too because they
followed a similar pattern.

A few cases of make_cleanup calls are replaced with explicit xfree
calls.  The make_cleanup/do_cleanups calls in those cases are
pointless, because do_cleanups won't be called when a Scheme exception
is thrown.

We also have a couple cases of Guile-facing code using RAII-type
objects to manage memory, but those are incorrect, exactly because
their dtor won't be called if a Guile exception is thrown.

gdb/ChangeLog:
2018-07-18  Pedro Alves  <palves@redhat.com>

	* guile/guile-internal.h: Add comment about mixing GDB and Scheme
	exceptions.
	(GDBSCM_HANDLE_GDB_EXCEPTION_WITH_CLEANUPS): Delete.
	(gdbscm_wrap): New.
	* guile/scm-frame.c (gdbscm_frame_read_register): Use xfree
	directly instead of a cleanup.
	* guile/scm-math.c (vlscm_unop_gdbthrow): New, factored out from ...
	(vlscm_unop): ... this.  Reimplement using gdbscm_wrap.
	(vlscm_binop_gdbthrow): New, factored out from ...
	(vlscm_binop): ... this.  Reimplement using gdbscm_wrap.
	(vlscm_rich_compare): Use gdbscm_wrap.
	* guile/scm-symbol.c (gdbscm_lookup_symbol): Use xfree directly
	instead of a cleanup.
	(gdbscm_lookup_global_symbol): Use xfree directly instead of a
	cleanup.
	* guile/scm-type.c (gdbscm_type_field, gdbscm_type_has_field_p):
	Use xfree directly instead of a cleanup.
	* guile/scm-value.c (gdbscm_make_value, gdbscm_make_lazy_value):
	Adjust to use gdbscm_wrap and scoped_value_mark.
	(gdbscm_value_optimized_out_p): Adjust to use gdbscm_wrap.
	(gdbscm_value_address, gdbscm_value_dereference)
	(gdbscm_value_referenced_value): Adjust to use gdbscm_wrap and
	scoped_value_mark.
	(gdbscm_value_dynamic_type): Use scoped_value_mark.
	(vlscm_do_cast, gdbscm_value_field): Adjust to use gdbscm_wrap and
	scoped_value_mark.
	(gdbscm_value_subscript, gdbscm_value_call): Adjust to use
	gdbscm_wrap and scoped_value_mark.
	(gdbscm_value_to_string): Use xfree directly instead of a
	cleanup.  Move 'buffer' unique_ptr to TRY scope.
	(gdbscm_value_to_lazy_string): Use xfree directly instead of a
	cleanup.  Move 'buffer' unique_ptr to TRY scope.  Use
	scoped_value_mark.
	(gdbscm_value_fetch_lazy_x): Use gdbscm_wrap.
	(gdbscm_parse_and_eval): Adjust to use gdbscm_wrap and
	scoped_value_mark.
	(gdbscm_history_ref, gdbscm_history_append_x): Adjust to use
	gdbscm_wrap.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/exp] Fix printing of type of optimized out vla
@ 2018-07-18 20:19 sergiodj+buildbot
  2018-07-18 20:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-18 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 42dc7699a26be0157c438dcaeb89da38287c6d2d ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 42dc7699a26be0157c438dcaeb89da38287c6d2d

[gdb/exp] Fix printing of type of optimized out vla

Consider this snippet from gcc/testsuite/gcc.dg/guality/vla-1.c:
...
int __attribute__((noinline))
f1 (int i)
{
  char a[i + 1];
  a[0] = 5;             /* { dg-final { gdb-test .+1 "i" "5" } } */
  return a[0];          /* { dg-final { gdb-test . "sizeof (a)" "6" } } */
}
...

When we compile the test-case with -O1 -g, and query the size of optimized
out vla 'a', we get:
...
$ ./gdb -batch -ex "b f1" -ex "r" -ex "p sizeof (a)" vla-1.exe
Breakpoint 1 at 0x4004a8: file vla-1.c, line 17.

Breakpoint 1, f1 (i=i@entry=5) at vla-1.c:17
17        return a[0];
$1 = 0
...
while we expect a size of '6'.

The problem is that default_read_var_value does not resolve the dynamic type
of a variable if the variable is optimized out.

This patch fixes that, and consequently gdb prints '6', as expected.

Tested on x86_64-linux.

2018-07-18  Tom de Vries  <tdevries@suse.de>

	* findvar.c (default_read_var_value): Also resolve dynamic type for
	LOC_OPTIMIZED_OUT vars.

	* gdb.base/vla-optimized-out.c: New test.
	* gdb.base/vla-optimized-out.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] BFD/XCOFF: Fix storage class setting for weak defined symbols
@ 2018-07-18 17:09 sergiodj+buildbot
  2018-07-18 17:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-18 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3554ec1ed057f4ecfee35d4bec81f9d5a545cb1 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: d3554ec1ed057f4ecfee35d4bec81f9d5a545cb1

BFD/XCOFF: Fix storage class setting for weak defined symbols

Fix an issue with commit 8602d4fea60d ("Add AIX weak support"),
<https://sourceware.org/ml/binutils/2009-03/msg00189.html>, and use the
correct condition to set the storage class for weak defined symbols.

The context here is as follows:

  else if ((h->root.type == bfd_link_hash_defined
            || h->root.type == bfd_link_hash_defweak)
           && h->smclas == XMC_XO)
    {
      BFD_ASSERT (bfd_is_abs_section (h->root.u.def.section));
      isym.n_value = h->root.u.def.value;
      isym.n_scnum = N_UNDEF;
      if (h->root.type == bfd_link_hash_undefweak
          && C_WEAKEXT == C_AIX_WEAKEXT)
        isym.n_sclass = C_WEAKEXT;
      else
        isym.n_sclass = C_EXT;
      aux.x_csect.x_smtyp = XTY_ER;
    }

so clearly the inner condition can never be true.  Correct the condition
then to check for the `bfd_link_hash_defweak' symbol type instead here,
and in a similar place a little further down in the same function.

	bfd/
	* xcofflink.c (xcoff_write_global_symbol): Fix symbol type
	checks for defined weak symbols.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return unique_xmalloc_ptr from gdbscm_scm_to_string
@ 2018-07-17 21:55 sergiodj+buildbot
  2018-07-17 21:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17 21:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c6c6149af440c3032eb7d02c2852907c61aac470 ***

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

Return unique_xmalloc_ptr from gdbscm_scm_to_string

This changes gdbscm_scm_to_string to return a unique_xmalloc_ptr and
then fixes all the callers.  This allows for the removal of some
cleanups.

gdb/ChangeLog
2018-07-17  Tom Tromey  <tom@tromey.com>

	* guile/scm-param.c (pascm_set_func, pascm_show_func)
	(compute_enum_list, pascm_set_param_value_x)
	(gdbscm_parameter_value): Update.
	* guile/guile-internal.h (gdbscm_scm_to_string): Update.
	(gdbscm_scm_to_host_string): Update.
	* guile/scm-math.c (vlscm_convert_typed_value_from_scheme):
	Update.
	* guile/scm-cmd.c (cmdscm_add_completion): Update.
	* guile/scm-pretty-print.c (ppscm_print_string_repr): Update.
	* guile/scm-string.c (gdbscm_scm_to_string): Return
	unique_xmalloc_ptr.
	(gdbscm_scm_to_host_string): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Return unique_xmalloc_ptr from gdbscm_safe_eval_string
@ 2018-07-17 20:28 sergiodj+buildbot
  2018-07-17 21:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1a31cb8dce7d1bfa7878dc08c28af330ef2ed69 ***

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

Return unique_xmalloc_ptr from gdbscm_safe_eval_string

This changes gdbscm_safe_eval_string to return a unique_xmalloc_ptr.
This allows for the removal of some cleanups.  It also fixes a
potential latent memory leak in gdbscm_set_backtrace.

gdb/ChangeLog
2018-07-17  Tom Tromey  <tom@tromey.com>

	* guile/guile.c (gdbscm_eval_from_control_command): Update.
	* guile/guile-internal.h (gdbscm_safe_eval_string): Update.
	* guile/scm-objfile.c (gdbscm_execute_objfile_script): Update.
	* guile/scm-safe-call.c (gdbscm_safe_eval_string): Return
	unique_xmalloc_ptr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] BFD: Use `bfd_is_abs_symbol' to determine whether a symbol is absolute
@ 2018-07-17 20:04 sergiodj+buildbot
  2018-07-17 20:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17 20:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c691de6a16a87adc686ce5cd6c9be54ee0b1a8c1 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: c691de6a16a87adc686ce5cd6c9be54ee0b1a8c1

BFD: Use `bfd_is_abs_symbol' to determine whether a symbol is absolute

Use `bfd_is_abs_symbol' to determine whether a symbol is absolute,
avoiding a problem with ordinary symbols defined in a linker script
outside an output section definition.  Such symbols have its owning
section set to the absolute section up to the final link phase.  A flag
has been added to the link hash to identify such symbols.  Rather than
checking the flag by hand, use the macro that does it uniformly for all
users.

	bfd/
	* elf32-nds32.c (nds32_elf_relax_loadstore): Use
	`bfd_is_abs_symbol' rather than `bfd_is_abs_section' in checking
	whether the symbol is absolute.
	(nds32_elf_relax_lo12): Likewise.
	* elfnn-aarch64.c (elfNN_aarch64_final_link_relocate): Likewise.
	(elfNN_aarch64_check_relocs): Likewise.
	* xcofflink.c (xcoff_need_ldrel_p): Likewise.
	(bfd_xcoff_import_symbol): Likewise.
	(xcoff_write_global_symbol): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] LD: Export relative-from-absolute symbol marking to BFD
@ 2018-07-17 19:20 sergiodj+buildbot
  2018-07-17 19:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17 19:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d5c928c05356b22af08450bf43b262ccc1b1d8ee ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: d5c928c05356b22af08450bf43b262ccc1b1d8ee

LD: Export relative-from-absolute symbol marking to BFD

It is usually possible to tell absolute and ordinary symbols apart in
BFD throughout the link, by checking whether the section that owns the
symbol is absolute or not.

That however does not work for ordinary symbols defined in a linker
script outside an output section statement.  Initially such symbols are
entered into to the link hash as absolute symbols, owned by the absolute
section.  A flag is set in the internal linker expression defining such
symbols to tell the linker to convert them to section-relative ones in
the final phase of the link.  That flag is however not accessible to BFD
linker code, including BFD target code in particular.

Add a flag to the link hash then to copy the information held in the
linker expression.  Define a macro, `bfd_is_abs_symbol', for BFD code to
use where determining whether a symbol is absolute or ordinary is
required before the final link phase.

This macro will correctly identify the special `__ehdr_start' symbol as
ordinary throughout link, for example, even though early on it will be
assigned to the absolute section.  Of course this does not let BFD code
identify what the symbol's ultimate section will be before the final
link phase has converted this symbol (in `update_definedness').

	include/
	* bfdlink.h (bfd_link_hash_entry): Add `rel_from_abs' member.

	bfd/
	* linker.c (bfd_is_abs_symbol): New macro.
	* bfd-in2.h: Regenerate.

	ld/
	* ldexp.c (exp_fold_tree_1) <etree_assign, etree_provide>
	<etree_provided>: Copy expression's `rel_from_abs' flag to the
	link hash.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Don't decrement pc after break.
@ 2018-07-17 17:29 sergiodj+buildbot
  2018-07-17 18:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27724bad005cd734eb0b990205d315f8e2d3bd35 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 27724bad005cd734eb0b990205d315f8e2d3bd35

RISC-V: Don't decrement pc after break.

	gdb/
	* riscv-tdep.c (riscv_has_feature): Delete comment that refers to
	set_gdbarch_decr_pc_after_break.  Call riscv_read_misa_reg always.
	(riscv_gdbarch_init): Delete local has_compressed_isa.  Delete now
	unecessary braces after EF_RISCV_RVC test.  Delete call to
	set_gdbarch_decr_pc_after_break.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove --disable-gdbcli
@ 2018-07-17 16:55 sergiodj+buildbot
  2018-07-17 17:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17 16:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 056dec39ed11e0027ae399018c3fef3a719718b9 ***

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

Remove --disable-gdbcli

I think it doesn't really make sense to allow building gdb without the
CLI.  Perhaps at one time this was a goal, but libgdb is long gone and
the CLI is intrinsic to gdb.

So, this patch removes the implementation of this configure option.
It is still recognized (this is autoconf's default), but does nothing.

This simplifies configure.ac and Makefile.in a bit.

Tested by rebuilding.

gdb/ChangeLog
2018-07-17  Tom Tromey  <tom@tromey.com>

	* configure.ac: Remove --disable-gdbcli.
	* configure: Rebuild.
	* Makefile.in (SUBDIR_CLI_DEPS, SUBDIR_CLI_LDFLAGS)
	(SUBDIR_CLI_CFLAGS): Remove.
	(SFILES): Use SUBDIR_CLI_SRCS.
	(COMMON_OBS): Use SUBDIR_CLI_OBS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix compilation error in ia64-vms-tdep.c with libunwind-ia64
@ 2018-07-17  3:26 sergiodj+buildbot
  2018-07-17  3:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17  3:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ec74dcd894ce3087dad2b6d0da96c572d5e0c7c6 ***

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

Fix compilation error in ia64-vms-tdep.c with libunwind-ia64

I found this when doing a --enable-targets=all build with libunwind-ia64
properly configured.

  CXX    ia64-vms-tdep.o
/home/emaisin/src/binutils-gdb/gdb/ia64-vms-tdep.c: In function int ia64_vms_find_proc_info_x(unw_addr_space_t, unw_word_t, unw_proc_info_t*, int, void*):
/home/emaisin/src/binutils-gdb/gdb/ia64-vms-tdep.c:79:33: error: invalid conversion from void* to gdb_byte* {aka unsigned char*} [-fpermissive]
                             pi->unwind_info, pi->unwind_info_size);
                                 ^
In file included from /home/emaisin/src/binutils-gdb/gdb/target.h:70:0,
                 from /home/emaisin/src/binutils-gdb/gdb/exec.h:23,
                 from /home/emaisin/src/binutils-gdb/gdb/gdbcore.h:29,
                 from /home/emaisin/src/binutils-gdb/gdb/ia64-vms-tdep.c:25:
/home/emaisin/src/binutils-gdb/gdb/target/target.h:35:12: note:   initializing argument 2 of int target_read_memory(CORE_ADDR, gdb_byte*, ssize_t)
 extern int target_read_memory (CORE_ADDR memaddr, gdb_byte *myaddr,
            ^

gdb/ChangeLog:

	* ia64-vms-tdep.c (ia64_vms_find_proc_info_x): Add cast.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix compilation error in ia64-tdep.c with libunwind-ia64
@ 2018-07-17  2:21 sergiodj+buildbot
  2018-07-17  2:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-17  2:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d691c8829d0e5c4c4b9cfb147c8a873ce18085b ***

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

Fix compilation error in ia64-tdep.c with libunwind-ia64

Commit

  9018be22e022 ("Make target_read_alloc & al return vectors")

failed to update the code in ia64-tdep.c, for HAVE_LIBUNWIND_IA64_H.
This patch fixes that.

gdb/ChangeLog:

	* ia64-tdep.c (ktab_buf): New global.
	(getunwind_table): Return a gdb::optional<gdb::byte_vector>.
	(get_kernel_table): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use gdb_assert in two places in buildsym.c
@ 2018-07-16 23:48 sergiodj+buildbot
  2018-07-16 23:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 23:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ccdac490bb3b568e88626afc84017c79e2d086e7 ***

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

Use gdb_assert in two places in buildsym.c

This changes buildsym.c to use gdb_assert rather than internal_error
in a couple of spots.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* buildsym.c (push_subfile): Use gdb_assert.
	(pop_subfile): Use gdb_assert.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove merge_symbol_lists
@ 2018-07-16 23:14 sergiodj+buildbot
  2018-07-16 23:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 23:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43130d6f969cebcd407e210fd06e565647401ba9 ***

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

Remove merge_symbol_lists

I discovered that merge_symbol_lists is unused, so this removes it.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* buildsym.h (merge_symbol_lists): Remove.
	* buildsym.c (merge_symbol_lists): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add grok/write functions for new ppc core note sections
@ 2018-07-16 21:45 sergiodj+buildbot
  2018-07-17  4:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 21:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cb2366c198d4c22b4bae6fca8f9ab4b0234c64aa ***

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

Add grok/write functions for new ppc core note sections

This patch adds functions for grokking and writing more register core
note sections (NT_PPC_TAR, NT_PPC_PPR, NT_PPC_DSCR, NT_PPC_EBB,
NT_PPC_PMU, NT_PPC_TM_CGPR, NT_PPC_TM_CFPR, NT_PPC_TM_CVMX,
NT_PPC_TM_CVSX, NT_PPC_TM_SPR, NT_PPC_TM_CTAR, NT_PPC_TM_CPPR,
NT_PPC_TM_CDSCR).

2018-07-16  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

bfd/
	* elf-bfd.h (elfcore_write_ppc_tar): Add prototype.
	(elfcore_write_ppc_ppr): Likewise.
	(elfcore_write_ppc_dscr): Likewise.
	(elfcore_write_ppc_ebb): Likewise.
	(elfcore_write_ppc_pmu): Likewise.
	(elfcore_write_ppc_tm_cgpr): Likewise.
	(elfcore_write_ppc_tm_cfpr): Likewise.
	(elfcore_write_ppc_tm_cvmx): Likewise.
	(elfcore_write_ppc_tm_cvsx): Likewise.
	(elfcore_write_ppc_tm_spr): Likewise.
	(elfcore_write_ppc_tm_ctar): Likewise.
	(elfcore_write_ppc_tm_cppr): Likewise.
	(elfcore_write_ppc_tm_cdscr): Likewise.
	* elf.c (elfcore_write_ppc_tar): New function.
	(elfcore_write_ppc_ppr): Likewise.
	(elfcore_write_ppc_dscr): Likewise.
	(elfcore_write_ppc_ebb): Likewise.
	(elfcore_write_ppc_pmu): Likewise.
	(elfcore_write_ppc_tm_cgpr): Likewise.
	(elfcore_write_ppc_tm_cfpr): Likewise.
	(elfcore_write_ppc_tm_cvmx): Likewise.
	(elfcore_write_ppc_tm_cvsx): Likewise.
	(elfcore_write_ppc_tm_spr): Likewise.
	(elfcore_write_ppc_tm_ctar): Likewise.
	(elfcore_write_ppc_tm_cppr): Likewise.
	(elfcore_write_ppc_tm_cdscr): Likewise.
	(elfcore_write_register_note): Call them.
	(elfcore_grok_ppc_tar): New function.
	(elfcore_grok_ppc_ppr): Likewise.
	(elfcore_grok_ppc_dscr): Likewise.
	(elfcore_grok_ppc_ebb): Likewise.
	(elfcore_grok_ppc_pmu): Likewise.
	(elfcore_grok_ppc_tm_cgpr): Likewise.
	(elfcore_grok_ppc_tm_cfpr): Likewise.
	(elfcore_grok_ppc_tm_cvmx): Likewise.
	(elfcore_grok_ppc_tm_cvsx): Likewise.
	(elfcore_grok_ppc_tm_spr): Likewise.
	(elfcore_grok_ppc_tm_ctar): Likewise.
	(elfcore_grok_ppc_tm_cppr): Likewise.
	(elfcore_grok_ppc_tm_cdscr): Likewise.
	(elfcore_grok_note): Call them.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move processing_gcc to stabsread
@ 2018-07-16 21:34 sergiodj+buildbot
  2018-07-16 21:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b84eeb21628a89b40c985b527d3d5db7806c93c ***

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

Move processing_gcc to stabsread

processing_gcc is also only used by stabsread -- it is set by the
DWARF reader, but this turns out not to be needed.  So, this patch
moves processing_gcc and removes the assignment from the DWARF reader.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* stabsread.h (processing_gcc_compilation): Move from buildsym.h.
	* dwarf2read.c (dwarf2_start_symtab): Don't set
	processing_gcc_compilation.
	* buildsym.h (processing_gcc_compilation): Move to stabsread.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote-sim.c: Remove unused variables
@ 2018-07-16 21:09 sergiodj+buildbot
  2018-07-17  2:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 21:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a700e753e5b019fb5d783c4e15cb29f165a339d3 ***

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

remote-sim.c: Remove unused variables

gdb/ChangeLog:

	* remote-sim.c (gdbsim_target::close,
	gdbsim_target::mourn_inferior): Remove unused variables.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use outermost_context_p in more places
@ 2018-07-16 20:47 sergiodj+buildbot
  2018-07-17  1:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT edb0470b99a9f399ccb5d666173c4315f6cb02c0 ***

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

Use outermost_context_p in more places

This changes a few explicit checks of context_stack_depth to use
outermost_context_p instead.  This simplifies some future work.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* xcoffread.c (read_xcoff_symtab): Use outermost_context_p.
	* dwarf2read.c (using_directives, new_symbol): Use
	outermost_context_p.
	* dbxread.c (process_one_symbol): Use outermost_context_p.
	* coffread.c (coff_symtab_read): Use outermost_context_p.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move the using directives to buildsym_compunit
@ 2018-07-16 20:35 sergiodj+buildbot
  2018-07-17  1:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6cccc9a89160455aab634784c231af4590d943f3 ***

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

Move the using directives to buildsym_compunit

This moves the globals local_using_directives and
global_using_directives to be members of buildsym_compunit, and adds
the necessary accessors.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (using_directives, read_func_scope)
	(read_lexical_block_scope): Update.
	* cp-namespace.c (cp_scan_for_anonymous_namespaces): Update.
	* buildsym.h (local_using_directives, global_using_directives):
	Don't declare.
	(get_local_using_directives, set_local_using_directives)
	(get_global_using_directives): Declare.
	* buildsym.c (struct buildsym_compunit) <m_local_using_directives,
	m_global_using_directives>: New members.
	(finish_block_internal, prepare_for_building)
	(reset_symtab_globals, end_symtab_get_static_block)
	(push_context): Update.
	(get_local_using_directives, set_local_using_directives)
	(get_global_using_directives): New functions.
	(buildsym_init): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move scan_file_globals declaration to stabsread.h
@ 2018-07-16 18:54 sergiodj+buildbot
  2018-07-16 22:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 18:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 77d6f1aa16685bc715c95decf6e3d3ae2e70dbc1 ***

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

Move scan_file_globals declaration to stabsread.h

scan_file_globals is defined in stabsread.c, so move its declaration
to stabsread.h.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* stabsread.c (scan_file_globals): Update comment.
	* stabsread.h (scan_file_globals): Move from buildsym.h.
	* buildsym.h (scan_file_globals): Move to stabsread.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move last_source_start_addr to buildsym_compunit
@ 2018-07-16 18:47 sergiodj+buildbot
  2018-07-16 18:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 18:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c99ee5c4f44d52258fa176563cc6a4cfbf0069d ***

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

Move last_source_start_addr to buildsym_compunit

This moves the global last_source_start_addr into buildsym_compunit,
adding some accessors as well.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* xcoffread.c (aix_process_linenos, complete_symtab): Update.
	* dbxread.c (read_ofile_symtab): Update.
	* coffread.c (coff_start_symtab, coff_end_symtab): Update.
	* buildsym.h (last_source_start_addr): Remove.
	(set_last_source_start_addr, get_last_source_start_addr):
	Declare.
	* buildsym.c (buildsym_compunit::buildsym_compunit): Add last_addr
	parameter.
	(struct buildsym_compunit) <m_last_source_start_addr>: New
	member.
	(prepare_for_building): Remove start_addr parameter.
	(start_symtab, restart_symtab, end_symtab_get_static_block)
	(end_symtab_with_blockvector): Update.
	(set_last_source_start_addr, get_last_source_start_addr): New
	functions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move some code from buildsym to stabsread
@ 2018-07-16 18:07 sergiodj+buildbot
  2018-07-16 20:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 18:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2150c3ef045a525b1d74c06eb8b0811621f264e3 ***

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

Move some code from buildsym to stabsread

A few things that currently reside in buildsym.c turn out to be
specific to the stabs reader.  This patch moves these from
buildsym.[ch] to stabsread.[ch].

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* stabsread.h (HASHSIZE, hashname, symnum, next_symbol_text)
	(next_symbol_text_func): Move from buildsym.h.
	* stabsread.c (hashname): Move from buildsym.c.
	* buildsym.h (HASHSIZE, symnum, next_symbol_text)
	(next_symbol_text_func, hashname): Move to stabsread.h.
	* buildsym.c: Don't include bcache.h
	(hashname): Move to stasbread.c.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move last_source file to buildsym_compunit
@ 2018-07-16 17:29 sergiodj+buildbot
  2018-07-16 17:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 17:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0015d4497e0057536b5ec7e0fed8f8bca07572e ***

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

Move last_source file to buildsym_compunit

This moves the global last_source_file into buildsym_compunit.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* buildsym.c (buildsym_compunit::buildsym_compunit): Add name
	parameter.
	(buildsym_compunit::set_last_source_file): New method.
	<m_last_source_file>: New member.
	(prepare_for_building): Remove "name" parameter.
	(start_symtab, restart_symtab, reset_symtab_globals): Update.
	(last_source_file): Remove.
	(set_last_source_file, get_last_source_file): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move have_line_numbers to buildsym_compunit
@ 2018-07-16 17:20 sergiodj+buildbot
  2018-07-16 18:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 530fedbcbf61b6d74c76a8ba720fe29d98896831 ***

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

Move have_line_numbers to buildsym_compunit

This moves the global have_line_numbers into buildsym_compunit.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* buildsym.c (struct buildsym_compunit) <m_have_line_numbers>: New
	member.
	(have_line_numbers): Remove.
	(record_line, prepare_for_building, end_symtab_get_static_block)
	(augment_type_symtab): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move pending_macros to buildsym_compunit
@ 2018-07-16 17:07 sergiodj+buildbot
  2018-07-16 17:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 17:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a976300e78cf6c90b5b70626ff1b28f495d8bab ***

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

Move pending_macros to buildsym_compunit

This moves the pending_macros global into buildsym_compunit.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* buildsym.c (~buildsym_compunit): Free the macro table.
	(struct buildsym_compunit) <get_macro_table, release_macros>: New
	methods.
	<m_pending_macros>: New member.
	(pending_macros): Remove.
	(~scoped_free_pendings, get_macro_table, prepare_for_building)
	(reset_symtab_globals, end_symtab_get_static_block)
	(end_symtab_with_blockvector, augment_type_symtab)
	(buildsym_init): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add assert in prepare_for_building
@ 2018-07-16 17:06 sergiodj+buildbot
  2018-07-16 17:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e62cca7ccb9ea47d18a0812a2c27f00e5048367b ***

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

Add assert in prepare_for_building

This adds an assertion in prepare_for_building.  This was useful for
verifying whether some subsequent changes were valid.

gdb/ChangeLog
2018-07-16  Tom Tromey  <tom@tromey.com>

	* buildsym.c (prepare_for_building): Add assert.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update the src-release script to include the new top level files test-driver and ar-lib.
@ 2018-07-16 13:25 sergiodj+buildbot
  2018-07-16 13:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-16 13:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a8288f78ad4d8d273b3dc7ab10b0fd43464d0aa ***

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

Update the src-release script to include the new top level files test-driver and ar-lib.

	* src-release.sh (DEVO_SUPPORT): Add test-driver and ar-lib.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove struct keyword in range-based for loop
@ 2018-07-14  2:23 sergiodj+buildbot
  2018-07-14  2:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-14  2:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff27d0737ef0c9433a6a7c83c1e678ac57a27699 ***

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

Remove struct keyword in range-based for loop

Fix this with  gcc 6.3.0:

/home/simark/src/binutils-gdb/gdb/symfile.c: In function 'void set_objfile_default_section_offset(objfile*, const section_addr_info&, CORE_ADDR)':
/home/simark/src/binutils-gdb/gdb/symfile.c:2114:14: error: types may not be defined in a for-range-declaration [-Werror]
   for (const struct other_sections *objf_sect : objf_addrs_sorted)
              ^~~~~~
gdb/ChangeLog:

	* symfile.c (set_objfile_default_section_offset): Remove struct
	keyword.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] sim: Add Stafford Horne as or1k maintainer.
@ 2018-07-13 21:45 sergiodj+buildbot
  2018-07-13 21:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-13 21:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31375626546b074268b2e1ccc7b52704b04bdb6c ***

Author: Stafford Horne <shorne@gmail.com>
Branch: master
Commit: 31375626546b074268b2e1ccc7b52704b04bdb6c

sim: Add Stafford Horne as or1k maintainer.

Since I helped upstream the or1k port I would like to claim myself as
maintainer.

sim/ChangeLog:

yyyy-mm-dd  Stafford Horne  <shorne@gmail.com>

	* MAINTAINERS (or1k): Add myself as or1k maintainer.

Signed-off-by: Stafford Horne <shorne@gmail.com>


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Add Stafford Horne as or1k maintainer.
@ 2018-07-13 21:14 sergiodj+buildbot
  2018-07-13 21:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-13 21:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6a15ecf5e0538ba416f6578403fceb9e5af98120 ***

Author: Stafford Horne <shorne@gmail.com>
Branch: master
Commit: 6a15ecf5e0538ba416f6578403fceb9e5af98120

gdb: Add Stafford Horne as or1k maintainer.

Since I helped upstream openrisc I would like to claim responsibility to
maintain it.

gdb/ChangeLog:

yyyy-mm-dd  Stafford Horne  <shorne@gmail.com>

	* (Responsible Maintainers): Add myself as or1k maintainer.

Signed-off-by: Stafford Horne <shorne@gmail.com>


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a warning on macOS
@ 2018-07-13 17:43 sergiodj+buildbot
  2018-07-13 17:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-13 17:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 027a4c30d03e3f434ddfa61e7f026e3b15f83daa ***

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

Remove a warning on macOS

This removes a clang warning coming from -Wmissing-braces.

ChangeLog
2018-07-13  Tom Tromey  <tom@tromey.com>

	* symfile.c (set_objfile_default_section_offset): Use extra braces
	around initializer.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add remainder of Em16 restrictions for AArch64 gas.
@ 2018-07-12  9:57 sergiodj+buildbot
  2018-07-12 10:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-12  9:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45a28947f3fe5693560e9a1d6373807a9e82c04a ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 45a28947f3fe5693560e9a1d6373807a9e82c04a

Add remainder of Em16 restrictions for AArch64 gas.

This adds the missing Em16 constraints the rest of the instructions requiring them
and also adds a testcase to test all the instructions so these are checked from
now on.

The Em16 operand constrains the valid registers to the lower 16 registers when used
with a half precision qualifier.

The list has been cross checked (by hand) through the Arm ARM version Ca.

opcodes/

	PR binutils/23192
	* aarch64-tbl.h (sqdmlal, sqdmlal2, smlsl, smlsl2, sqdmlsl, sqdmlsl2,
	mul, smull, smull2, sqdmull, sqdmull2, sqdmulh, sqrdmulh, mla, umlal,
	umlal2, mls, umlsl, umlsl2, umull, umull2, sqdmlal, sqdmlsl, sqdmull,
	sqdmulh, sqrdmulh): Use Em16.

gas/

	PR binutils/23192
	* testsuite/gas/aarch64/illegal-by-element.s: New.
	* testsuite/gas/aarch64/illegal-by-element.d: New.
	* testsuite/gas/aarch64/illegal-by-element.l: New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Implement IPv6 support for GDB/gdbserver
@ 2018-07-12  0:20 sergiodj+buildbot
  2018-07-12  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-12  0:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c7ab0aef11d91b637bf091aa9176b8dc4aadee46 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: c7ab0aef11d91b637bf091aa9176b8dc4aadee46

Implement IPv6 support for GDB/gdbserver

This patch implements IPv6 support for both GDB and gdbserver.  Based
on my research, it is the fourth attempt to do that since 2006.  Since
I used ideas from all of the previous patches, I also added their
authors's names on the ChangeLogs as a way to recognize their
efforts.  For reference sake, you can find the previous attempts at:

  https://sourceware.org/ml/gdb-patches/2006-09/msg00192.html

  https://sourceware.org/ml/gdb-patches/2014-02/msg00248.html

  https://sourceware.org/ml/gdb-patches/2016-02/msg00226.html

The basic idea behind the patch is to start using the new
'getaddrinfo'/'getnameinfo' calls, which are responsible for
translating names and addresses in a protocol-independent way.  This
means that if we ever have a new version of the IP protocol, we won't
need to change the code again (or, at least, won't have to change the
majority of the code).

The function 'getaddrinfo' returns a linked list of possible addresses
to connect to.  Dealing with multiple addresses proved to be a hard
task with the current TCP auto-retry mechanism implemented on
ser-tcp:net_open.  For example, when gdbserver listened only on an
IPv4 socket:

  $ ./gdbserver --once 127.0.0.1:1234 ./a.out

and GDB was instructed to try to connect to both IPv6 and IPv4
sockets:

  $ ./gdb -ex 'target extended-remote localhost:1234' ./a.out

the user would notice a somewhat big delay before GDB was able to
connect to the IPv4 socket.  This happened because GDB was trying to
connect to the IPv6 socket first, and had to wait until the connection
timed out before it tried to connect to the IPv4 socket.

For that reason, I had to rewrite the main loop and implement a new
method for handling multiple connections.  After some discussion,
Pedro and I agreed on the following algorithm:

  1) For each entry returned by 'getaddrinfo', we try to open a socket
  and connect to it.

  2.a) If we have a successful 'connect', we just use that connection.

  2.b) If we don't have a successfull 'connect', but if we've got a
  ECONNREFUSED (meaning the the connection was refused), we keep track
  of this fact by using a flag.

  2.c) If we don't have a successfull 'connect', but if we've got a
  EINPROGRESS (meaning that the connection is in progress), we perform
  a 'select' call on the socket until we have a result (either a
  successful connection, or an error on the socket).

  3) If tcp_auto_retry is true, and we haven't gotten a successful
  connection, and at least one of our attempts failed with
  ECONNREFUSED, then we wait a little bit (i.e., call
  'wait_for_connect'), check to see if there was a
  timeout/interruption (in which case we bail out), and then go back
  to (1).

After multiple tests, I was able to connect without delay on the
scenario described above, and was also able to connect in all other
types of scenarios.

I also implemented some hostname parsing functions (along with their
corresponding unit tests) which are used to help GDB and gdbserver to
parse hostname strings provided by the user.  These new functions are
living inside common/netstuff.[ch].  I've had to do that since IPv6
introduces a new URL scheme, which defines that square brackets can be
used to enclose the host part and differentiate it from the
port (e.g., "[::1]:1234" means "host ::1, port 1234").  I spent some
time thinking about a reasonable way to interpret what the user wants,
and I came up with the following:

  - If the user has provided a prefix that doesn't specify the protocol
    version (i.e., "tcp:" or "udp:"), or if the user has not provided
    any prefix, don't make any assumptions (i.e., assume AF_UNSPEC when
    dealing with 'getaddrinfo') *unless* the host starts with "[" (in
    which case, assume it's an IPv6 host).

  - If the user has provided a prefix that does specify the protocol
    version (i.e., "tcp4:", "tcp6:", "udp4:" or "udp6:"), then respect
    that.

This method doesn't follow strictly what RFC 2732 proposes (that
literal IPv6 addresses should be provided enclosed in "[" and "]")
because IPv6 addresses still can be provided without square brackets
in our case, but since we have prefixes to specify protocol versions I
think this is not an issue.

Another thing worth mentioning is the new 'GDB_TEST_SOCKETHOST'
testcase parameter, which makes it possible to specify the
hostname (without the port) to be used when testing GDB and
gdbserver.  For example, to run IPv6 tests:

  $ make check-gdb RUNTESTFLAGS='GDB_TEST_SOCKETHOST=tcp6:[::1]'

Or, to run IPv4 tests:

  $ make check-gdb RUNTESTFLAGS='GDB_TEST_SOCKETHOST=tcp4:127.0.0.1'

This required a few changes on the gdbserver-base.exp, and also a
minimal adjustment on gdb.server/run-without-local-binary.exp.

Finally, I've implemented a new testcase,
gdb.server/server-connect.exp, which is supposed to run on the native
host and perform various "smoke tests" using different connection
methods.

This patch has been regression-tested on BuildBot and locally, and
also built using a x86_64-w64-mingw32 GCC, and no problems were found.

gdb/ChangeLog:
2018-07-11  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Paul Fertser  <fercerpav@gmail.com>
	    Tsutomu Seki  <sekiriki@gmail.com>
	    Pedro Alves  <palves@redhat.com>

	* Makefile.in (SUBDIR_UNITTESTS_SRCS): Add
	'unittests/parse-connection-spec-selftests.c'.
	(COMMON_SFILES): Add 'common/netstuff.c'.
	(HFILES_NO_SRCDIR): Add 'common/netstuff.h'.
	* NEWS (Changes since GDB 8.2): Mention IPv6 support.
	* common/netstuff.c: New file.
	* common/netstuff.h: New file.
	* ser-tcp.c: Include 'netstuff.h' and 'wspiapi.h'.
	(wait_for_connect): Update comment.  New parameter
	'gdb::optional<int> sock' instead of 'struct serial *scb'.
	Use 'sock' directly instead of 'scb->fd'.
	(try_connect): New function, with code from 'net_open'.
	(net_open): Rewrite main loop to deal with multiple
	sockets/addresses.  Handle IPv6-style hostnames; implement
	support for IPv6 connections.
	* unittests/parse-connection-spec-selftests.c: New file.

gdb/gdbserver/ChangeLog:
2018-07-11  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Paul Fertser  <fercerpav@gmail.com>
	    Tsutomu Seki  <sekiriki@gmail.com>

	* Makefile.in (SFILES): Add '$(srcdir)/common/netstuff.c'.
	(OBS): Add 'common/netstuff.o'.
	(GDBREPLAY_OBS): Likewise.
	* gdbreplay.c: Include 'wspiapi.h' and 'netstuff.h'.
	(remote_open): Implement support for IPv6
	connections.
	* remote-utils.c: Include 'netstuff.h', 'filestuff.h'
	and 'wspiapi.h'.
	(handle_accept_event): Accept connections from IPv6 sources.
	(remote_prepare): Handle IPv6-style hostnames; implement
	support for IPv6 connections.
	(remote_open): Implement support for printing connections from
	IPv6 sources.

gdb/testsuite/ChangeLog:
2018-07-11  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Paul Fertser  <fercerpav@gmail.com>
	    Tsutomu Seki  <sekiriki@gmail.com>

	* README (Testsuite Parameters): Mention new 'GDB_TEST_SOCKETHOST'
	parameter.
	* boards/native-extended-gdbserver.exp: Do not set 'sockethost'
	by default.
	* boards/native-gdbserver.exp: Likewise.
	* gdb.server/run-without-local-binary.exp: Improve regexp used
	for detecting when a remote debugging connection succeeds.
	* gdb.server/server-connect.exp: New file.
	* lib/gdbserver-support.exp (gdbserver_default_get_comm_port):
	Do not prefix the port number with ":".
	(gdbserver_start): New global GDB_TEST_SOCKETHOST.  Implement
	support for detecting and using it.  Add '$debughost_gdbserver'
	to the list of arguments used to start gdbserver.  Handle case
	when gdbserver cannot resolve a network name.

gdb/doc/ChangeLog:
2018-07-11  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Jan Kratochvil  <jan.kratochvil@redhat.com>
	    Paul Fertser  <fercerpav@gmail.com>
	    Tsutomu Seki  <sekiriki@gmail.com>

	* gdb.texinfo (Remote Connection Commands): Add explanation
	about new IPv6 support.  Add new connection prefixes.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB: Work around D; PID handling bug in older GDBservers (PR gdb/23377)
@ 2018-07-11 23:34 sergiodj+buildbot
  2018-07-11 23:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11 23:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c7333b308f5178813745f40e641231efb1cb763 ***

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

GDB: Work around D;PID handling bug in older GDBservers (PR gdb/23377)

This commit adds a GDB workaround for the GDBserver bug exposed by
commit f2ffa92bbce9 ("gdb: Eliminate the 'stop_pc' global"), so that
newer GDBs can continue working with older GDBservers.

gdb/ChangeLog:
2018-07-11  Pedro Alves  <palves@redhat.com>

	PR gdb/23377
	* remote.c (remote_target::remote_detach_pid): Call
	set_current_process.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Remove traces of h8300 ecoff support
@ 2018-07-11 20:12 sergiodj+buildbot
  2018-07-11 21:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a6f88f6e4458e672b8a72ee0c0998fdc79cf601e ***

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

gdb: Remove traces of h8300 ecoff support

There's this little bit of ecoff support in the h8300 port that I ran
into that I think we could remove.  Grepping around BFD, I don't think
ECOFF is supported for h8300.

And if not, I'm failing to see why we'd support ECOFF debug info in
ELF for h8300 (.mdebug).  It kind of seems like someone just installed
the set_gdbarch_ecoff_reg_to_regnum hook at the same time the dwarf2
and stabs hooks were installed.

I'm removing this so that greps for ecoff stuff only lead to MIPS, as
ISTR that Linux/MIPS support still relies on some subset of ECOFF for
something.

gdb/ChangeLog:
2018-07-11  Pedro Alves  <palves@redhat.com>

	* h8300-tdep.c (h8300_gdbarch_init): Remove
	set_gdbarch_ecoff_reg_to_regnum calls.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix PR c++/23373: GDB hangs when printing a struct with a static member of itself
@ 2018-07-11 19:19 sergiodj+buildbot
  2018-07-11 19:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11 19:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 16ff70ddd430b63ca4dd68bf1d52828f2ed4f030 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 16ff70ddd430b63ca4dd68bf1d52828f2ed4f030

Fix PR c++/23373: GDB hangs when printing a struct with a static member of itself

This patch fixes a failure that happens when a structure has a static
member whose type is the same as itself.  From the bug report:

  Example code:
  struct A
  {
      static A Empty;
      int a;
  };

  int main(void) {
      A a;
      return 0;
  }

  Output:
  (gdb) ptype/o A
  /* offset    |  size */  type = struct A {
			     static struct A {
				 static struct A {
				     static struct A {
					 static struct A {
					     static struct A {
						 static struct A {
						     ... # infinite loop

The problem here is that GDB is not taking into account the fact that
static members inside a class/struct are not stored in the
class/struct, and therefore they should not be accounted for during
the display of the offsets/sizes.  The fix is simple: we just check if
the field we're dealing with (on
c-typeprint.c:c_type_print_base_struct_union) is static, and if it is
then we don't iterate over it.

This patch also adds a new test for this case, and doesn't introduce
any regressions.  I believe it is important enough to be included in
the 8.2 branch.

OK?

gdb/ChangeLog:
2018-07-11  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR c++/23373
	* c-typeprint.c (c_type_print_base_struct_union): Don't print
	offsets/sizes for static members of a class/struct.

gdb/testsuite/ChangeLog:
2018-07-11  Sergio Durigan Junior  <sergiodj@redhat.com>

	PR c++/23373
	* gdb.base/ptype-offsets.cc (struct static_member): New
	struct.
	(main) <stmember>: New variable.
	* gdb.base/ptype-offsets.exp: Add test for printing a struct
	with a static member in it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/BFD: Fix TLS relocation resolution for regular executables
@ 2018-07-11 17:31 sergiodj+buildbot
  2018-07-11 17:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11 17:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1cb83cac9a8974bdb12aac90018ad1165ba86274 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 1cb83cac9a8974bdb12aac90018ad1165ba86274

MIPS/BFD: Fix TLS relocation resolution for regular executables

Correct an issue with commit 0f20cc3522e7 ("TLS support for MIPS"),
<https://sourceware.org/ml/binutils/2005-02/msg00607.html>, where a
condition used to determine whether to use a dynamic symbol for GD, LD
and IE TLS dynamic relocations against a symbol that has been defined
locally has been incorrectly reversed.

It's executables rather than dynamic shared objects where no symbol is
required, because such symbols cannot be preempted and therefore their
values (thread pointer offsets) are fixed at the static link time as is
the associated module ID of the main executable, so the original
condition should have been `shared' instead of `!shared'.  This wrong
condition was then later converted from `!shared' to `!bfd_link_pic',
with commit 0e1862bb401f ("Add output_type to bfd_link_info").

Use the correct `bfd_link_dll' condition then, and adjust code for the
dynamic symbol index possibly being -1 as with symbols that have been
forced local, removing unnecessary dynamic relocations from dynamic
regular executables.  PIE executables are unaffected as the existing
condition excluded them by chance due to the conversion mentioned above.

Adjust test cases accordingly.

	bfd/
	* elfxx-mips.c (mips_tls_got_relocs): Use `bfd_link_dll' rather
	than `!bfd_link_pic' in determining the dynamic symbol index.
	Avoid the index of -1.
	(mips_elf_initialize_tls_slots): Likewise.  Flatten code by
	moving `dyn' to the beginning of the function block.

	ld/
	* testsuite/ld-mips-elf/tlsdyn-o32.d: Update test for dynamic
	relocation removal.
	* testsuite/ld-mips-elf/tlsdyn-o32.got: Likewise.
	* testsuite/ld-mips-elf/tlsdyn-o32-1.d: Likewise.
	* testsuite/ld-mips-elf/tlsdyn-o32-1.got: Likewise.
	* testsuite/ld-mips-elf/tlsdyn-o32-2.d: Likewise.
	* testsuite/ld-mips-elf/tlsdyn-o32-2.got: Likewise.
	* testsuite/ld-mips-elf/tlsdyn-o32-3.d: Likewise.
	* testsuite/ld-mips-elf/tlsdyn-o32-3.got: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Adds the speculation barrier instructions to the ARM assembler and disassembler.
@ 2018-07-11 17:28 sergiodj+buildbot
  2018-07-11 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c597cc3d6eb76802dd079b1262f2d425e07da3eb ***

Author: Sudakshina Das <sudi.das@arm.com>
Branch: master
Commit: c597cc3d6eb76802dd079b1262f2d425e07da3eb

Adds the speculation barrier instructions to the ARM assembler and disassembler.

See:
https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability/download-the-whitepaper

opcodes	* arm-dis.c (arm_opcodes): Add ssbb and pssbb and move
	csdb together with them.
	(thumb32_opcodes): Likewise.

gas	* config/tc-arm.c (insns): Add new ssbb and pssbb instructions.
	* testsuite/gas/arm/csdb.s: Add new tests for ssbb and pssbb.
	* testsuite/gas/arm/csdb.d: Likewise
	* testsuite/gas/arm/thumb2_it_bad.s: Likewise.
	* testsuite/gas/arm/thumb2_it_bad.l: Likewise.
	* testsuite/gas/arm/barrier.d: Update with ssbb.
	* testsuite/gas/arm/barrier-thumb.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR ld/22570: MIPS/BFD: Fix TLS relocation resolution for PIE executables
@ 2018-07-11 17:09 sergiodj+buildbot
  2018-07-11 17:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9143e72c6d4ddefbcb41c0f6361ad140354145ef ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 9143e72c6d4ddefbcb41c0f6361ad140354145ef

PR ld/22570: MIPS/BFD: Fix TLS relocation resolution for PIE executables

Correct a commit 0e1862bb401f ("Add output_type to bfd_link_info") issue
and use `bfd_link_dll' rather than `bfd_link_pic' in determining whether
to fully resolve GD, LD and IE TLS relocations referring to symbols
locally defined rather than deferring them to the load time by means of
dynamic relocations.

Such symbols cannot be preempted in PIE executables, which are
necessarily PIC, and therefore their values (thread pointer offsets) are
fixed at the static link time as is the associated module ID of the main
executable.

Given the `tlsbin-o32.s' and `tlsdyn-o32.s' sources from our test suite
this removes the absolute TLS relocations from the static:

DYNAMIC RELOCATION RECORDS
OFFSET   TYPE              VALUE
00000000 R_MIPS_NONE       *ABS*
1000002c R_MIPS_TLS_TPREL32  *ABS*
10000030 R_MIPS_TLS_DTPMOD32  *ABS*
10000038 R_MIPS_TLS_DTPMOD32  *ABS*

and the dynamic:

DYNAMIC RELOCATION RECORDS
OFFSET   TYPE              VALUE
00000000 R_MIPS_NONE       *ABS*
1000002c R_MIPS_TLS_TPREL32  *ABS*
10000038 R_MIPS_TLS_DTPMOD32  *ABS*
10000044 R_MIPS_TLS_DTPMOD32  *ABS*
10000030 R_MIPS_TLS_DTPMOD32  tlsvar_gd
10000034 R_MIPS_TLS_DTPREL32  tlsvar_gd
10000040 R_MIPS_TLS_TPREL32  tlsvar_ie

PIE executable respectively, as reported by `objdump -R', and fills the
corresponding GOT slots with the values expected, as recorded with the
test cases added.  The new output from `objdump -R' is:

DYNAMIC RELOCATION RECORDS (none)

and:

DYNAMIC RELOCATION RECORDS
OFFSET   TYPE              VALUE
00000000 R_MIPS_NONE       *ABS*
10000030 R_MIPS_TLS_DTPMOD32  tlsvar_gd
10000034 R_MIPS_TLS_DTPREL32  tlsvar_gd
10000040 R_MIPS_TLS_TPREL32  tlsvar_ie

for the static and the dynamic executable respectively.

2018-07-11  Maciej W. Rozycki  <macro@mips.com>
            Rich Felker  <bugdal@aerifal.cx>

	bfd/
	PR ld/22570
	* elfxx-mips.c (mips_tls_got_relocs): Use `bfd_link_dll' rather
	than `bfd_link_pic' to determine whether dynamic relocations are
	to be produced.
	(mips_elf_initialize_tls_slots): Likewise.

	ld/
	PR ld/22570
	* testsuite/ld-mips-elf/tlsbin-pie-o32.d: New test.
	* testsuite/ld-mips-elf/tlsbin-pie-o32.got: New test.
	* testsuite/ld-mips-elf/tlsdyn-pie-o32.d: New test.
	* testsuite/ld-mips-elf/tlsdyn-pie-o32.got: New test.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: adjust monitor/mwait templates
@ 2018-07-11  9:15 sergiodj+buildbot
  2018-07-11 10:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11  9:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a79eaed6a5075ca062d6d8ff3d7a5ccce5d1908f ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: a79eaed6a5075ca062d6d8ff3d7a5ccce5d1908f

x86: adjust monitor/mwait templates

Architecturally, MONITOR's and MONITORX'es memory operand is a 16- or
32-bit register outside of 64-bit mode, and a 64- or 32-bit register
inside 64-bit mode. The other register operands, including all of them
for MWAIT and MWAITX, are uniformly 32-bit, irrespective of mode. Retain
the original 64-bit MONITOR{,X} templates for compatibility only, and
fold the MWAIT{,X} ones.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: drop {,reg16_}inoutportreg variables
@ 2018-07-11  9:04 sergiodj+buildbot
  2018-07-11  9:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11  9:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2fb5be8dac9db623ef6e2a61b1f5b09fd246872b ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 2fb5be8dac9db623ef6e2a61b1f5b09fd246872b

x86: drop {,reg16_}inoutportreg variables

The checking against reg16_inoutportreg can be had with a simple test of
a bit, and the value setting from inoutportreg can be replaced by using
the actual register's reg_type field.

Note that the so far redundant 2nd instance of OPERAND_TYPE_INOUTPORTREG
is left in place, for its use in type_names[].


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86/Intel: accept memory operand size specifiers for CET insns
@ 2018-07-11  8:52 sergiodj+buildbot
  2018-07-11  9:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f5cad304773ecbfe8b390e0b5d79fe11edb2a6b ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 7f5cad304773ecbfe8b390e0b5d79fe11edb2a6b

x86/Intel: accept memory operand size specifiers for CET insns


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: replace off-by-one OTMax
@ 2018-07-11  8:40 sergiodj+buildbot
  2018-07-11  8:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11  8:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f0a85b07061964d6c608e6280ce61aa3fed1eabf ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: f0a85b07061964d6c608e6280ce61aa3fed1eabf

x86: replace off-by-one OTMax

With its name it should equal to the largest prior enumerator, which is
not very helpful as that will change every once in a while. Rename it to
OTNum instead to make name and value match, and correct use sites to no
longer use one too large a value.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use std::vector for moribund_locations
@ 2018-07-11  1:58 sergiodj+buildbot
  2018-07-11  2:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11  1:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1123588c0bf1d777a3eb9c01f2370473a14a1ca5 ***

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

Use std::vector for moribund_locations

This changes moribund_locations to use a std::vector rather than VEC.
I also noticed that moribund_locations is only used in breakpoint.c,
so now it is static as well.

It might be possible to make this code a bit simpler by using a
ref_ptr in moribund_locations; however, I have not done this.

Tested by the buildbot.

gdb/ChangeLog
2018-07-10  Tom Tromey  <tom@tromey.com>

	* breakpoint.c (moribund_locations): Now static and a
	std::vector.
	(breakpoint_init_inferior, moribund_breakpoint_here_p)
	(build_bpstat_chain, update_global_location_list)
	(breakpoint_retire_moribund): Update.
	* breakpoint.h (bp_location_p): Remove typedef.  Don't declare
	VEC.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] BFD/ELF: Correct a `remove' global shadowing error for pre-4.8 GCC
@ 2018-07-11  0:07 sergiodj+buildbot
  2018-07-11  0:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-11  0:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5270eddc6ed6b5d8e4e2817491bb44b784fa6f81 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 5270eddc6ed6b5d8e4e2817491bb44b784fa6f81

BFD/ELF: Correct a `remove' global shadowing error for pre-4.8 GCC

Remove `-Wshadow' compilation errors:

cc1: warnings being treated as errors
.../bfd/elflink.c: In function 'bfd_elf_final_link':
.../bfd/elflink.c:11722: error: declaration of 'remove' shadows a global declaration
/usr/include/stdio.h:154: error: shadowed declaration is here

which for versions of GCC before 4.8 prevent support for ELF targets
from being built.  See also GCC PR c/53066.

	bfd/
	* elflink.c (bfd_elf_final_link): Rename `remove' local variable
	to `remove_section'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] xgate cleanup
@ 2018-07-10 15:13 sergiodj+buildbot
  2018-07-10 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-10 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1594e052d4fec8690b6bfabd369bc030135eb91a ***

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

xgate cleanup

elf32-xgate.c contains many functions that are only stubs and
elf32-xgate.h contains unused declarations.  While this might be
reasonable for the initial commit of a port with subsequent work
fleshing out the stubs, xgate has only had two minor target specific
patches since the initial commit over six years ago.  The rest of the
changes have been general maintenance work applied to all ELF targets,
and some of this work could have been avoided if the stubs hadn't been
there.  So this patch removes all the stubs.

I've kept the functionality of the old elf32_xgate_add_symbol_hook,
implemented in elf32_xgate_backend_symbol_processing.  Presumably,
that's to set the symbol st_target_internal flag for use in
elf32-m68hc1x.c:elf32_m68hc11_relocate_section.

The empty elf32_xgate_relocate_section meant that xgate had no linker.
Or at least, no linker relocation processing.  Deleting the
elf_backend_relocate_section define means the target will now use the
generic linker reloc processing.  How good that is will depend on the
accuracy of the reloc howtos..

I haven't updated the ld testsuite to xfail tests expected to fail
for generic elf targets.

bfd/
	* elf32-xgate.h: Delete.
	* elf32-xgate.c: Delete unnecessary forward declarations, add two
	that are now needed.
	(xgate_elf_bfd_link_hash_table_create)
	(xgate_elf_bfd_link_hash_table_free)
	(xgate_elf_set_mach_from_flags, struct xgate_scan_param)
	(stub_hash_newfunc, elf32_xgate_add_symbol_hook)
	(elf32_xgate_setup_section_lists, elf32_xgate_size_stubs)
	(elf32_xgate_build_stubs, elf32_xgate_check_relocs)
	(elf32_xgate_relocate_section, _bfd_xgate_elf_set_private_flags)
	(elf32_xgate_post_process_headers): Delete.
	(elf32_xgate_backend_symbol_processing): New function.
	(xgate_elf_ignore_reloc, xgate_elf_special_reloc)
	(_bfd_xgate_elf_print_private_bfd_data): Make static.
	(ELF_TARGET_ID, elf_info_to_howto, elf_backend_check_relocs)
	(elf_backend_relocate_section, elf_backend_object_p)
	(elf_backend_final_write_processing, elf_backend_can_gc_sections)
	(elf_backend_post_process_headers, elf_backend_add_symbol_hook)
	(bfd_elf32_bfd_link_hash_table_create)
	(bfd_elf32_bfd_set_private_flags)
	(xgate_stub_hash_lookup): Don't define.
	(elf_backend_symbol_processing): Define.
	* elf-bfd.h (elf_target_id): Delete XGATE_ELF_DATA.
ld/
	* emulparams/xgateelf.sh (TEMPLATE_NAME) Set to generic.
	(EXTRA_EM_FILE): Set to genelf.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/riscv: Fix assertion in inferior call code
@ 2018-07-10 12:43 sergiodj+buildbot
  2018-07-10 12:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-10 12:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8c49aa89abb92516dfc3507b540f736ca6339c0c ***

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

gdb/riscv: Fix assertion in inferior call code

An assertion when setting up arguments for an inferior call checks the
size of the argument against xlen.  However, if xlen and flen are
different sizes, and the argument is being placed into a floating
pointer register then we should be comparing against flen not xlen.

This issue shows up as an assertion failure when running on an rv32g
target with a binary compiled using the rv32f abi and making an
inferior call involving large floating point arguments, for example
the test gdb.base/infcall-nested-structs.exp.

gdb/ChangeLog:

	* riscv-tdep.c (riscv_is_fp_regno_p): New function.
	(riscv_register_reggroup_p): Use new function, remove unneeded
	parenthesis.
	(riscv_push_dummy_call): Extend assert to compare against xlen or
	flen based on register type.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/BFD: Do not redirect to discarded lazy binding stubs
@ 2018-07-09 20:43 sergiodj+buildbot
  2018-07-09 21:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 20:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b8377e7dbd9e53149268685ba4810a7b09fb0cb ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 4b8377e7dbd9e53149268685ba4810a7b09fb0cb

MIPS/BFD: Do not redirect to discarded lazy binding stubs

Correct a MIPS/BFD linker issue with dynamic symbol and corresponding
GOT entry values being redirected to lazy binding stubs where the stubs
section has been discarded by assigning to the `/DISCARD/' output
section in the linker script used.  The issue manifests itself by the
values entered being relative to the absolute section, which is what any
discarded sections are internally assigned in the linker.

For the `stub-dynsym-2.s' piece of code included as a test case with
this change this issue results in the dynamic symbol table and the GOT
looking like:

Symbol table '.dynsym' contains 3 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 00000010     0 FUNC    GLOBAL DEFAULT  UND bar
     2: 00000000     0 FUNC    GLOBAL DEFAULT  UND foo

Primary GOT:
 Canonical gp value: 00097ff0

 Reserved entries:
   Address     Access  Initial Purpose
  00090000 -32752(gp) 00000000 Lazy resolver
  00090004 -32748(gp) 80000000 Module pointer (GNU extension)

 Global entries:
   Address     Access  Initial Sym.Val. Type    Ndx Name
  00090008 -32744(gp) 00000010 00000010 FUNC    UND bar
  0009000c -32740(gp) 00000000 00000000 FUNC    UND foo

if assembled to regular MIPS code, or:

Symbol table '.dynsym' contains 3 entries:
   Num:    Value  Size Type    Bind   Vis      Ndx Name
     0: 00000000     0 NOTYPE  LOCAL  DEFAULT  UND
     1: 0000000d     0 FUNC    GLOBAL DEFAULT  UND bar
     2: 00000001     0 FUNC    GLOBAL DEFAULT  UND foo

Primary GOT:
 Canonical gp value: 00097ff0

 Reserved entries:
   Address     Access  Initial Purpose
  00090000 -32752(gp) 00000000 Lazy resolver
  00090004 -32748(gp) 80000000 Module pointer (GNU extension)

 Global entries:
   Address     Access  Initial Sym.Val. Type    Ndx Name
  00090008 -32744(gp) 0000000d 0000000d FUNC    UND bar
  0009000c -32740(gp) 00000001 00000001 FUNC    UND foo

if assembled to microMIPS code.  Symbol values and GOT entries record
the offset into the inexistent stubs section and the ISA bit rather than
zero, which would be the case if a lazy binding stub was not used for
other reasons, such as the value of the symbol being taken for a purpose
other than making a function call (e.g. an R_MIPS_GOT16 relocation).

Correct the issue by refraining from redirecting symbols to lazy binding
stubs if the stubs section is going to be discarded.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_adjust_dynamic_symbol): Don't set
	`->needs_lazy_stub' if the stubs output section is the absolute
	section.

	ld/
	* testsuite/ld-mips-elf/stub-dynsym-2.dd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-2.gd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-2.sd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-discard-2.gd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-discard-2.sd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-micromips-2.dd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-micromips-2.gd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-micromips-2.sd: New test.
	* testsuite/ld-mips-elf/stub-dynsym-micromips-insn32-2.dd: New
	test.
	* testsuite/ld-mips-elf/stub-dynsym-micromips-insn32-2.gd: New
	test.
	* testsuite/ld-mips-elf/stub-dynsym-micromips-insn32-2.sd: New
	test.
	* testsuite/ld-mips-elf/stub-dynsym-2.ld: New test linker
	script.
	* testsuite/ld-mips-elf/stub-dynsym-discard-2.ld: New test
	linker script.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Don't mention XM_CDEPS or NAT_CLIBS
@ 2018-07-09 18:43 sergiodj+buildbot
  2018-07-09 18:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 18:43 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8fd32c1ce66c66b02b2eb506a038cfc615aad1cb ***

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

Don't mention XM_CDEPS or NAT_CLIBS

Neither XM_CDEPS nor NAT_CLIBS are defined anywhere, so remove the
uses.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (CDEPS): Don't mention XM_CDEPS.
	(CLIBS): Don't mention NAT_CLIBS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Use add_setshow_zuinteger_unlimited_cmd in remote.c
@ 2018-07-09 17:53 sergiodj+buildbot
  2018-07-09 20:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 17:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 055303e28f70880f7b2c3e44df0ba7646fc85cf8 ***

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

gdb: Use add_setshow_zuinteger_unlimited_cmd in remote.c

Switch to use add_setshow_zuinteger_unlimited_cmd for some of the
control variables in remote.c.  The variables
hardware-watchpoint-limit, hardware-breakpoint-limit, and
hardware-watchpoint-length-limit are all changed.  For example, a user
will now see this:

    (gdb) show remote hardware-breakpoint-limit
    The maximum number of target hardware breakpoints is unlimited.

Instead of this:

    (gdb) show remote hardware-breakpoint-limit
    The maximum number of target hardware breakpoints is -1.

And can do this:

    (gdb) set remote hardware-breakpoint-limit unlimited

However, previously any negative value implied "unlimited", now only
-1, or the text "unlimited" can be used for unlimited.  Any other
negative value will give an error about invalid input.  This is a
small change in the user interface, but, hopefully, this will not
cause too many problems.

I've also added show functions for these three variables to allow for
internationalisation.

gdb/ChangeLog:

	* remote.c (show_hardware_watchpoint_limit): New function.
	(show_hardware_watchpoint_length_limit): New function.
	(show_hardware_breakpoint_limit): New function.
	(_initialize_remote): Use add_setshow_zuinteger_unlimited_cmd
	where appropriate, update help text.

gdb/doc/ChangeLog:

	* gdb.texinfo (Remote Configuration): Update descriptions for
	set/show of hardware-watchpoint-limit, hardware-breakpoint-limit,
	and hardware-watchpoint-length-limit variables.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/testsuite: Allow for failure to read some memory addresses
@ 2018-07-09 17:30 sergiodj+buildbot
  2018-07-09 19:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 17:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8ad9b9a31aa3e6039567fc1f152dd454c946d5f ***

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

gdb/testsuite: Allow for failure to read some memory addresses

In the gdb.base/examine-backward.exp test script, we check to see if
address zero is readable, and then read memory first forward from
address zero, and then backward from address zero.

The problem is, being able to read address zero does not guarantee
that you'll be able to read from the other end of the address space,
and the test probably shouldn't assume that is the case.

This patch updates the test script so that even if address zero is
known non-readable, we still run the tests, the tests in question are
mostly about, can GDB calculate the correct address to read from, we
can confirm this even if the final read ultimately fails.  We also no
longer assume that if address zero is readable, then the other end of
the address space will be readable.

One further change is that, when we examined the memory at address
zero, the regexp used to match the address expected that the zero
address would have two '0' digits as the least significant digits.  As
GDB strips leading zeros from addresses this was causing the test to
fail.  I've reduced the zero address to a single 0 digit.

gdb/testsuite/ChangeLog:

	* gdb.base/examine-backward.exp: Still run tests around address
	0x0, even if address 0x0 is not readable.  Update the pattern for
	matching address 0x0 in expected output.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix exec.c handling in Makefile
@ 2018-07-09 17:05 sergiodj+buildbot
  2018-07-09 17:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 17:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 981e0c0c1aabcd78409184c79e8f88b5de918e38 ***

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

Fix exec.c handling in Makefile

exec.c ws handled specially in COMMON_OBS, but there doesn't seem to
be a reason for this.  This changes the Makefile to treat exec.c as an
ordinary source file.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (ALLDEPFILES): Remove exec.c.
	(COMMON_OBS): Remove exec.o.
	(COMMON_SFILES): Add exec.c.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ADD_FILES and ADD_DEPS from Makefile.in
@ 2018-07-09 16:34 sergiodj+buildbot
  2018-07-09 18:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 16:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 31278b5193ea6025c09110aef2d67d81a952ebcc ***

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

Remove ADD_FILES and ADD_DEPS from Makefile.in

Nothing defines XM_ADD_FILES, TM_ADD_FILES, or NAT_ADD_FILES any more,
so consequently ADD_FILES and ADD_DEPS are no longer needed.  So, this
removes them.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (ADD_FILES, ADD_DEPS): Remove.
	(LIBGDB_OBS, clean mostlyclean): Update.
	(gdb$(EXEEXT), insight$(EXEEXT)): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Minimize yacc and lex output
@ 2018-07-09 16:22 sergiodj+buildbot
  2018-07-09 17:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 16:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5fd1493fd9c2d8d55fd15b9bd6539781ee56209 ***

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

Minimize yacc and lex output

This minimizes the "make" output from the yacc and lex rules,
following the same technique as the rest of the Makefile.

The lex rule had a special case to deal with the situation where flex
is not available.  I don't think this is needed, so I removed it.  If
flex is truly unavailable, the person building gdb can simply "touch"
the output file.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (%.c: %.y): Use ECHO_YACC.
	(%.c: %.l): Use ECHO_LEX.  Just fail if flex not available.
	* silent-rules.mk (ECHO_YACC, ECHO_LEX): New variables.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove lint support
@ 2018-07-09 15:58 sergiodj+buildbot
  2018-07-09 16:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 15:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14ccceb2e24df7defd5264ec3d078f79ecfa1b76 ***

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

Remove lint support

I don't think anyone uses lint any more, so this removes the support
for it from the Makefile.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (LINT, LINTFLAGS, LINTFILES, lint): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use a stamp file for init.c
@ 2018-07-09 15:15 sergiodj+buildbot
  2018-07-09 15:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 15:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1998086d5436499e8eaf16772e300459662c3d7c ***

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

Use a stamp file for init.c

This introduces a stamp file for init.c.  This prevents constant
rebuilds of init.o, by arranging for init.c to only be modified when
its contents change.  (FWIW this is a standard idiom in use by
Automake and by gdb itself for many years.)

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (init.c): Depend on stamp-init.
	(stamp-init): New rule, from init.c rule.
	(clean mostlyclean): Remove stamp-init.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove some unused code from init.c build rule
@ 2018-07-09 15:04 sergiodj+buildbot
  2018-07-09 15:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6497f1dd035530c483fdae22aaa6fcc715775f58 ***

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

Remove some unused code from init.c build rule

The init.c build rule has a few sed expressions that aren't necessary
any more.  This removes them.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (init.c): Remove some unused sed rules.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove TSOBS from gdb/Makefile.in
@ 2018-07-09 14:39 sergiodj+buildbot
  2018-07-09 14:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09 14:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 97a34db94284f42829e5e5c9c4fa65b216739bcb ***

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

Remove TSOBS from gdb/Makefile.in

The TSOBS variable doesn't seem to serve a useful purpose in
gdb/Makefile.in, so remove it.

gdb/ChangeLog
2018-07-09  Tom Tromey  <tom@tromey.com>

	* Makefile.in (TSOBS): Remove.
	(INIT_FILES): Update.
	(LIBGDB_OBS): Update.
	(COMMON_SFILES): Add inflow.c.
	(SFILES): Remove inflow.c.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] m68hc1* fixes
@ 2018-07-09  8:51 sergiodj+buildbot
  2018-07-09  9:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-09  8:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61658d78f08920e6afe7b43bcaa287521da196aa ***

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

m68hc1* fixes

With config.sub now properly returning m68hc12-unknown-elf rather than
m68hc12-unknown-none, more ELF tests run.  This patch enables
STB_GNU_UNIQUE processing fixing some testsuite failures that probably
no m68hc12 user cares about, and removes some XPASSes.

bfd/
	* elf32-m68hc1x.c (elf32_m68hc11_post_process_headers): Call
	_bfd_elf_post_process_headers.
ld/
	* testsuite/ld-discard/extern.d: Remove m68hc12 xfail.
	* testsuite/ld-discard/start.d: Likewise.
	* testsuite/ld-discard/static.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ia64-tdep.c: Fix -Wwrite-strings errors
@ 2018-07-07 15:31 sergiodj+buildbot
  2018-07-07 15:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-07 15:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e83f4d97504515f8c5f290eeb25eac87cca6892f ***

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

ia64-tdep.c: Fix -Wwrite-strings errors

Simply add const where necessary to get rid of errors like:

/home/simark/src/binutils-gdb/gdb/ia64-libunwind-tdep.c:114:1: error: ISO C++ forbids converting a string constant to char* [-Werror=write-strings]
 static char *get_reg_name = STRINGIFY(UNW_OBJ(get_reg));
 ^~~~~~~~~~~~~~
/home/simark/src/binutils-gdb/gdb/common/preprocessor.h:28:25: note: in definition of macro STRINGIFY_1
 #define STRINGIFY_1(x) #x
                         ^
/home/simark/src/binutils-gdb/gdb/ia64-libunwind-tdep.c:114:29: note: in expansion of macro STRINGIFY
 static char *get_reg_name = STRINGIFY(UNW_OBJ(get_reg));
                             ^~~~~~~~~

gdb/ChangeLog:

	* ia64-tdep.c (get_reg_name, get_fpreg_name, get_saveloc_name,
	is_signal_frame_name, step_name, init_remote_name,
	create_addr_space_name, destroy_addr_space_name,
	search_unwind_table_name, find_dyn_list_name): Constify.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] xtensa: don't emit dynamic relocation for weak undefined symbol
@ 2018-07-06 23:23 sergiodj+buildbot
  2018-07-06 23:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-06 23:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c451bb34ae8bd2d0669bd563366883cfbcf0de9b ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: c451bb34ae8bd2d0669bd563366883cfbcf0de9b

xtensa: don't emit dynamic relocation for weak undefined symbol

Resolved reference to a weak undefined symbol in PIE must not have
a dynamic relative relocation against itself, otherwise the value of a
reference will be changed from 0 to the base of executable, breaking
code like the following:

  void weak_function (void);
  if (weak_function)
    weak_function ();

This fixes tests for PR ld/22269 and a number of PIE tests in xtensa gcc
testsuite.

bfd/
2018-07-06  Max Filippov  <jcmvbkbc@gmail.com>

	* elf32-xtensa.c (elf_xtensa_allocate_dynrelocs): Don't allocate
	space for dynamic relocation for undefined weak symbol.
	(elf_xtensa_relocate_section): Don't emit R_XTENSA_RELATIVE
	relocation for undefined weak symbols.
	(shrink_dynamic_reloc_sections): Don't shrink dynamic relocation
	section for relocations against undefined weak symbols.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add checks for the NT_ARM_SVE section in a core file.
@ 2018-07-06 16:04 sergiodj+buildbot
  2018-07-06 16:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-06 16:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ad1cc4e492e51ff334df81b5e8610f91b50e373a ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: ad1cc4e492e51ff334df81b5e8610f91b50e373a

Add checks for the NT_ARM_SVE section in a core file.

The NT_ARM_SVE section is documented here:
  https://github.com/torvalds/linux/blob/master/Documentation/arm64/sve.txt
  * A NT_ARM_SVE note will be added to each coredump for each thread of the
   dumped process.  The contents will be equivalent to the data that would have
   been read if a PTRACE_GETREGSET of NT_ARM_SVE were executed for each thread
   when the coredump was generated.

	* elf.c (elfcore_grok_aarch_sve): New function.
	(elfcore_grok_note): Check for Aarch64 SVE.
	(elfcore_write_aarch_sve): New function.
	(elfcore_write_register_note): Check for Aarch64 SVE.
	* elf-bfd.h(elfcore_grok_aarch_sve): New declaration.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix SBO bit in disassembly mask for ldrah on AArch64.
@ 2018-07-06 15:50 sergiodj+buildbot
  2018-07-06 16:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-06 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f311ba7ed84d66ae2cd77bd969747d7ab959d866 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: f311ba7ed84d66ae2cd77bd969747d7ab959d866

Fix SBO bit in disassembly mask for ldrah on AArch64.

The disassembly mask for ldarh incorrectly didn't mask out bit 20 which
is part of the SBO part of the instruction and shouldn't be considered input.

This fixes the wrong bit fixing the disassembly of instructions to
ldarh and makes the behavior consistent.

opcodes/

	PR binutils/23242
	* aarch64-tbl.h (ldarh): Fix disassembly mask.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix the read/write flag for these registers on AArch64
@ 2018-07-06 15:46 sergiodj+buildbot
  2018-07-06 15:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-06 15:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cba05feb51cb97f75f9a7814b081ce45245ac7b2 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: cba05feb51cb97f75f9a7814b081ce45245ac7b2

Fix the read/write flag for these registers on AArch64

The previous constraints were based on information already in opcodes and it
seems that a few of them were wrong.  I have now hand verified the ones changed
by the previous patch and corrected where needed.

This prevents a warning to be issued when one shouldn't be.

opcodes/

	PR binutils/23369
	* aarch64-opc.c (aarch64_sys_regs): Make read/write csselr_el1,
	vsesr_el2, osdtrrx_el1, osdtrtx_el1, pmsidr_el1.

gas/testsuite/

	PR binutils/23369
	* gas/aarch64/msr.d (csselr_el1,
	vsesr_el2, osdtrrx_el1, osdtrtx_el1, pmsidr_el1): New.
	* gas/aarch64/msr.s: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/testsuite: Ensure test links in malloc and free
@ 2018-07-06 13:55 sergiodj+buildbot
  2018-07-06 13:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-06 13:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0e5e971ae89da1ded13013bb7378dc5f09363af ***

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

gdb/testsuite: Ensure test links in malloc and free

The test associated with the source file
gdb.base/share-env-with-gdbserver.c relies on calling malloc and free
within the inferior from GDB.  However, as the test source itself
makes no use of these functions, there's no requirement that they be
linked into the test executable.

This commit adds a dummy call to malloc and free to ensure they are
linked into the test executable.

gdb/testsuite/ChangeLog:

	* gdb.base/share-env-with-gdbserver.c (main): Add call to
	malloc/free.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update config.sub
@ 2018-07-06  6:41 sergiodj+buildbot
  2018-07-06  6:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-06  6:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 269965964e8a6586a07912a60e08eeb0053bfb2a ***

Author: Sebastian Huber <sebastian.huber@embedded-brains.de>
Branch: master
Commit: 269965964e8a6586a07912a60e08eeb0053bfb2a

Update config.sub

	* config.sub: Sync with upstream version 2018-07-03.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update config.guess and config.sub
@ 2018-07-05 12:16 sergiodj+buildbot
  2018-07-05 12:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-05 12:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c524414837791938eb5aed58a3334c4f8e04fe4b ***

Author: Sebastian Huber <sebastian.huber@embedded-brains.de>
Branch: master
Commit: c524414837791938eb5aed58a3334c4f8e04fe4b

Update config.guess and config.sub

	* config.guess: Sync with upstream version 2018-06-26.
	* config.sub: Sync with upstream version 2018-07-02.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Updated Russian, Bulgarian, and Brazilian Portuguese translations for various components of the binutuls.
@ 2018-07-05 11:32 sergiodj+buildbot
  2018-07-05 11:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-05 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d8dab05495df17d8c961be8913e7a1e152670382 ***

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

Updated Russian, Bulgarian, and Brazilian Portuguese translations for various components of the binutuls.

ld	* po/bg.po: Updated Bulgarian translation.
	* po/pt_BR.po: Updated Brazilian Portuguese translation.

binutils* po/bg.po: Updated Bulgarian translation.

bfd,gas	* po/ru.po: Updated Russian translation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Error for mismatched powerpc ABI tags
@ 2018-07-05  1:05 sergiodj+buildbot
  2018-07-05  1:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-05  1:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4a91d0ba307eb24eb87ad27f4ea8fcde823c3e61 ***

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

Error for mismatched powerpc ABI tags

And report the two input files that are incompatible rather than
reporting that an input file is incompatible with the output.

bfd/
	* elf-bfd.h (_bfd_elf_ppc_merge_fp_attributes): Update prototype.
	* elf32-ppc.c (_bfd_elf_ppc_merge_fp_attributes): Return error
	on mismatch.  Remove "warning: " from messages.  Track last bfd
	used to set tags.
	(ppc_elf_merge_obj_attributes): Likewise.  Handle status from
	_bfd_elf_ppc_merge_fp_attributes.
	* elf64-ppc.c (ppc64_elf_merge_private_bfd_data): Handle status
	from _bfd_elf_ppc_merge_fp_attributes.
ld/
	* testsuite/ld-powerpc/attr-gnu-4-12.d: Update expected output.
	* testsuite/ld-powerpc/attr-gnu-4-13.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-21.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-23.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-31.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-4-32.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-8-23.d: Likewise.
	* testsuite/ld-powerpc/attr-gnu-12-21.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use exit_inferior in darwin_attach_pid
@ 2018-07-04 20:19 sergiodj+buildbot
  2018-07-04 20:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-04 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a7d0f0f000b39269c25509a22a12549c6ef26b1f ***

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

Use exit_inferior in darwin_attach_pid

Commit a50c11c666 was intended to use exit_inferior in
darwin_attach_pid, but I accidentally pushed the wrong version of the
patch.  This fixes the problem.

gdb/ChangeLog
2018-07-04  Tom Tromey  <tom@tromey.com>

	* darwin-nat.c (darwin_attach_pid): Use exit_inferior.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update NEWS post GDB 8.2 branch creation.
@ 2018-07-04 16:41 sergiodj+buildbot
  2018-07-04 17:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-04 16:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e5b2f8961a385056922f45a5cbb02bbbad4a737 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 4e5b2f8961a385056922f45a5cbb02bbbad4a737

Update NEWS post GDB 8.2 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] 5167+ messages in thread
* [binutils-gdb] Warn if /proc is not accessible
@ 2018-07-04 15:34 sergiodj+buildbot
  2018-07-04 15:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-04 15:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1b919490e8ba30bf1d6941df0ed112b0e557017e ***

Author: Vyacheslav Barinov <v.barinov@samsung.com>
Branch: master
Commit: 1b919490e8ba30bf1d6941df0ed112b0e557017e

Warn if /proc is not accessible

There's a buildroot where I want to debug a binary, and I tried to
connect to it from outside, but got very weird errors like
architecture mismatch or protocol errors.  At last, after switching on
'--debug' for gdbserver I found a message 'Can't open /proc/pid/'
message and suddenly found that I forgot to mount procfs in my
buildroot.

Make discovering the problem easier by making GDB / GDBserver warn
(even without --debug) if /proc can not be accessed.

Native debugging:

 (gdb) start
 Temporary breakpoint 1 at 0x400835: file test.c, line 10.
 Starting program: /tmp/test
 warning: /proc is not accessible.

GDBserver/remote debugging:

 $ ./gdbserver :9999 ./gdbserver
 gdbserver: /proc is not accessible.

gdb/ChangeLog:
2018-07-04  Vyacheslav Barinov  <v.barinov@samsung.com>
	    Pedro Alves  <palves@redhat.com>

	* linux-nat.c (linux_init_ptrace): Rename to ...
	(linux_init_ptrace_procfs): ... this.  Call
	linux_proc_init_warnings.
	(linux_nat_target::post_attach)
	(linux_nat_target::post_startup_inferior): Adjust.
	* nat/linux-procfs.c (linux_proc_init_warnings): Define function.
	* nat/linux-procfs.h (linux_proc_init_warnings): Declare function.

gdb/gdbserver/ChangeLog:
2018-07-04  Vyacheslav Barinov  <v.barinov@samsung.com>
	    Pedro Alves  <palves@redhat.com>

	* linux-low.c (initialize_low): Call linux_proc_init_warnings.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Also install diagnostics.h
@ 2018-07-04 13:41 sergiodj+buildbot
  2018-07-04 13:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-04 13:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT db40acb0bed088872837f916029d8800c33f9f94 ***

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

Also install diagnostics.h

Since bfd.h is an installed header, also install diagnostics.h.

	* Makefile.am (bfdinclude_HEADERS): Add $(INCDIR)/diagnostics.h.
	* Makefile.in: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/symtab] Fix version check in dwarf compilation unit header
@ 2018-07-04 10:14 sergiodj+buildbot
  2018-07-04 10:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-04 10:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ea5da02629b4bf9c4cea50aee189f94fa7d1a3b ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 1ea5da02629b4bf9c4cea50aee189f94fa7d1a3b

[gdb/symtab] Fix version check in dwarf compilation unit header

The version check of the dwarf compilation unit header in
error_check_comp_unit_head is done too late, and consequently dwarf code with
an unsupported version in the compilation unit header is interpreted as dwarf5
code in read_comp_unit_head.

Fixed by moving the check earlier.

Build and reg-tested on x86_64-linux.

2018-07-04  Tom de Vries  <tdevries@suse.de>

	* dwarf2read.c (error_check_comp_unit_head): Move dwarf version
	check ...
	(read_comp_unit_head): ... here.

	* gdb.dwarf2/dw2-error.exp: Update expected error message.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove VEC from breakpoint
@ 2018-07-04  5:32 sergiodj+buildbot
  2018-07-04  5:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-04  5:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f51e0e20bd303a9b366084ac719db10978402713 ***

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

Remove VEC from breakpoint

This removes a use of VEC from breakpoint.h, also removing the
now-unnecessary breakpoint_p typedef.

This patch fixes a latent memory leak in
find_matching_tracepoint_location, which neglected to free the vector
returned by all_tracepoints.

Tested by the buildbot.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* tracepoint.c (process_tracepoint_on_disconnect, start_tracing)
	(stop_tracing, tstatus_command)
	(find_matching_tracepoint_location, merge_uploaded_tracepoints)
	(print_one_static_tracepoint_marker): Update.
	* breakpoint.c (static_tracepoints_here, all_tracepoints): Return
	std::vector.
	* breakpoint.h (breakpoint_p): Remove typedef.  Don't declare
	VEC.
	(all_tracepoints, static_tracepoints_here): Return std::vector.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ptid_get_tid
@ 2018-07-03 20:37 sergiodj+buildbot
  2018-07-03 20:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 20:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc6bcb548d67a5a0a7223d81bd43c299312320c8 ***

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

Remove ptid_get_tid

This removes ptid_get_tid in favor of calling the ptid_t::tid method.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* common/ptid.c (ptid_get_tid): Remove.
	* common/ptid.h (ptid_get_tid): Don't declare.
	* ada-tasks.c: Update.
	* aix-thread.c: Update.
	* bsd-uthread.c: Update.
	* darwin-nat.c: Update.
	* fbsd-nat.c: Update.
	* i386-darwin-nat.c: Update.
	* infrun.c: Update.
	* linux-tdep.c: Update.
	* nto-procfs.c: Update.
	* ppc-ravenscar-thread.c: Update.
	* python/py-infthread.c: Update.
	* ravenscar-thread.c: Update.
	* sol-thread.c: Update.
	* sparc-ravenscar-thread.c: Update.
	* windows-nat.c: Update.

gdb/gdbserver/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* target.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ptid_tid_p
@ 2018-07-03 20:22 sergiodj+buildbot
  2018-07-03 22:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 20:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d2a107e3f9e84808ae0860693f1c488b1e3f5559 ***

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

Remove ptid_tid_p

This removes ptid_tid_p in favor of the ptid_t::tid_p method.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* common/ptid.c (ptid_tid_p): Remove.
	* common/ptid.h (ptid_tid_p): Don't declare.
	* sol-thread.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ptid_is_pid
@ 2018-07-03 19:56 sergiodj+buildbot
  2018-07-03 21:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 19:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e998d966be13e548721109a4e44b2887fc5cb24 ***

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

Remove ptid_is_pid

This removes ptid_is_pid in favor of the ptid_t::is_pid method.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* common/ptid.c (ptid_is_pid): Remove.
	* common/ptid.h (ptid_is_pid): Don't declare.
	* infrun.c: Update.
	* linux-nat.c: Update.
	* mi/mi-interp.c: Update.
	* remote.c: Update.
	* thread.c: Update.

gdb/gdbserver/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* linux-low.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ptid_get_pid
@ 2018-07-03 19:37 sergiodj+buildbot
  2018-07-03 19:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 19:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e99b03dcf42606425eab8bd12eadb8aa4007f35a ***

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

Remove ptid_get_pid

This removes ptid_get_pid in favor of calling the ptid_t::pid method.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* common/ptid.c (ptid_get_pid): Remove.
	* common/ptid.h (ptid_get_pid): Don't declare.
	* aarch64-linux-nat.c: Update.
	* ada-lang.c: Update.
	* aix-thread.c: Update.
	* alpha-bsd-nat.c: Update.
	* amd64-fbsd-nat.c: Update.
	* amd64-linux-nat.c: Update.
	* arm-linux-nat.c: Update.
	* arm-nbsd-nat.c: Update.
	* auxv.c: Update.
	* break-catch-syscall.c: Update.
	* breakpoint.c: Update.
	* bsd-uthread.c: Update.
	* corelow.c: Update.
	* ctf.c: Update.
	* darwin-nat.c: Update.
	* fbsd-nat.c: Update.
	* fbsd-tdep.c: Update.
	* gcore.c: Update.
	* gnu-nat.c: Update.
	* hppa-nbsd-nat.c: Update.
	* hppa-obsd-nat.c: Update.
	* i386-fbsd-nat.c: Update.
	* ia64-linux-nat.c: Update.
	* inf-ptrace.c: Update.
	* infcmd.c: Update.
	* inferior.c: Update.
	* inferior.h: Update.
	* inflow.c: Update.
	* infrun.c: Update.
	* linux-fork.c: Update.
	* linux-nat.c: Update.
	* linux-tdep.c: Update.
	* linux-thread-db.c: Update.
	* m68k-bsd-nat.c: Update.
	* mi/mi-interp.c: Update.
	* mi/mi-main.c: Update.
	* mips-linux-nat.c: Update.
	* mips-nbsd-nat.c: Update.
	* mips64-obsd-nat.c: Update.
	* nat/aarch64-linux-hw-point.c: Update.
	* nat/aarch64-linux.c: Update.
	* nat/linux-btrace.c: Update.
	* nat/linux-osdata.c: Update.
	* nat/linux-procfs.c: Update.
	* nat/x86-linux-dregs.c: Update.
	* nto-procfs.c: Update.
	* obsd-nat.c: Update.
	* ppc-linux-nat.c: Update.
	* ppc-nbsd-nat.c: Update.
	* ppc-obsd-nat.c: Update.
	* proc-service.c: Update.
	* procfs.c: Update.
	* python/py-inferior.c: Update.
	* python/py-infthread.c: Update.
	* ravenscar-thread.c: Update.
	* record.c: Update.
	* remote-sim.c: Update.
	* remote.c: Update.
	* rs6000-nat.c: Update.
	* s390-linux-nat.c: Update.
	* sh-nbsd-nat.c: Update.
	* sol-thread.c: Update.
	* sparc-nat.c: Update.
	* sparc64-tdep.c: Update.
	* spu-linux-nat.c: Update.
	* spu-tdep.c: Update.
	* target-debug.h: Update.
	* target.c: Update.
	* thread.c: Update.
	* tid-parse.c: Update.
	* tracefile-tfile.c: Update.
	* vax-bsd-nat.c: Update.
	* windows-nat.c: Update.
	* x86-linux-nat.c: Update.
	* x86-nat.c: Update.

gdb/gdbserver/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* linux-low.c: Update.
	* linux-mips-low.c: Update.
	* lynx-low.c: Update.
	* mem-break.c: Update.
	* nto-low.c: Update.
	* remote-utils.c: Update.
	* server.c: Update.
	* spu-low.c: Update.
	* target.c: Update.
	* tracepoint.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove ptid_get_lwp
@ 2018-07-03 19:30 sergiodj+buildbot
  2018-07-03 20:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 19:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e38504b39279fa86cbb2c4a45ab8ec34e3aef90b ***

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

Remove ptid_get_lwp

This removes ptid_get_lwp in favor of calling the ptid_t::lwp method.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* common/ptid.c (ptid_get_lwp): Remove.
	* common/ptid.h (ptid_get_lwp): Don't declare.
	* aarch64-linux-nat.c: Update.
	* ada-tasks.c: Update.
	* aix-thread.c: Update.
	* amd64-linux-nat.c: Update.
	* arm-linux-nat.c: Update.
	* corelow.c: Update.
	* fbsd-nat.c: Update.
	* fbsd-tdep.c: Update.
	* gnu-nat.c: Update.
	* i386-cygwin-tdep.c: Update.
	* i386-gnu-nat.c: Update.
	* i386-linux-nat.c: Update.
	* ia64-linux-nat.c: Update.
	* inf-ptrace.c: Update.
	* infrun.c: Update.
	* linux-fork.c: Update.
	* linux-nat.c: Update.
	* linux-tdep.c: Update.
	* linux-thread-db.c: Update.
	* mips-linux-nat.c: Update.
	* nat/aarch64-linux-hw-point.c: Update.
	* nat/aarch64-linux.c: Update.
	* nat/linux-btrace.c: Update.
	* nat/linux-osdata.c: Update.
	* nat/linux-procfs.c: Update.
	* nat/x86-linux-dregs.c: Update.
	* obsd-nat.c: Update.
	* ppc-fbsd-nat.c: Update.
	* ppc-linux-nat.c: Update.
	* procfs.c: Update.
	* python/py-infthread.c: Update.
	* ravenscar-thread.c: Update.
	* remote.c: Update.
	* s390-linux-nat.c: Update.
	* sol-thread.c: Update.
	* sol2-tdep.c: Update.
	* spu-linux-nat.c: Update.
	* x86-linux-nat.c: Update.
	* xtensa-linux-nat.c: Update.

gdb/gdbserver/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* linux-low.c: Update.
	* linux-mips-low.c: Update.
	* lynx-low.c: Update.
	* nto-low.c: Update.
	* remote-utils.c: Update.
	* server.c: Update.
	* spu-low.c: Update.
	* target.c: Update.
	* thread-db.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove pid_to_ptid
@ 2018-07-03 19:08 sergiodj+buildbot
  2018-07-03 19:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 19:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f2907e49910853edf3c1aec995b3c44b3bba8999 ***

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

Remove pid_to_ptid

This removes pid_to_ptid in favor of calling the ptid_t constructor
directly.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* common/ptid.c (pid_to_ptid): Remove.
	* common/ptid.h (pid_to_ptid): Don't declare.
	* aix-thread.c: Update.
	* arm-linux-nat.c: Update.
	* common/ptid.c: Update.
	* common/ptid.h: Update.
	* corelow.c: Update.
	* ctf.c: Update.
	* darwin-nat.c: Update.
	* fbsd-nat.c: Update.
	* fork-child.c: Update.
	* gnu-nat.c: Update.
	* go32-nat.c: Update.
	* inf-ptrace.c: Update.
	* infcmd.c: Update.
	* inferior.c: Update.
	* infrun.c: Update.
	* linux-fork.c: Update.
	* linux-nat.c: Update.
	* nat/aarch64-linux-hw-point.c: Update.
	* nat/fork-inferior.c: Update.
	* nat/x86-linux-dregs.c: Update.
	* nto-procfs.c: Update.
	* obsd-nat.c: Update.
	* procfs.c: Update.
	* progspace.c: Update.
	* remote.c: Update.
	* rs6000-nat.c: Update.
	* s390-linux-nat.c: Update.
	* sol-thread.c: Update.
	* spu-linux-nat.c: Update.
	* target.c: Update.
	* top.c: Update.
	* tracefile-tfile.c: Update.
	* windows-nat.c: Update.

gdb/gdbserver/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* linux-low.c: Update.
	* linux-ppc-low.c: Update.
	* linux-x86-low.c: Update.
	* proc-service.c: Update.
	* server.c: Update.
	* spu-low.c: Update.
	* thread-db.c: Update.
	* win32-low.c: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove exit_inferior_num_silent
@ 2018-07-03 17:56 sergiodj+buildbot
  2018-07-03 18:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 17:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 057302ceb3b1c171afe9bfa24642af208a60b6e9 ***

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

Remove exit_inferior_num_silent

The sole caller of exit_inferior_num_silent was getting the inferior's
number to then use the number to look up the inferior again.  I think
it's better to simply not have exit_inferior_num_silent; any potential
callers that only have the inferior's number should probably be
converted to pass the inferior itself around instead.

Tested by the buildbot.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	* infrun.c (follow_exec): Use exit_inferior_silent.
	* inferior.c (exit_inferior_num_silent): Remove.
	* inferior.h (exit_inferior_num_silent): Don't declare.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix crash in "run" on macOS when gdb is not signed
@ 2018-07-03 16:21 sergiodj+buildbot
  2018-07-03 16:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03 16:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a50c11c666e07b922d64aa5bb2747f180ce17c03 ***

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

Fix crash in "run" on macOS when gdb is not signed

On macOS, when gdb is not code-signed, it will throw an exception from
darwin_attach_pid.  However, gdb also then crashes:

thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion `tp' failed.

I think the problem here is that darwin_attach_pid does not clean up
inferior_ptid and inf->pid on failure.  This leads to a situation
where gdb tries to find a thread, but cannot.

In other cases, gdb would mourn the inferior at this point; but here
this is not possible because the target has not been pushed.  Instead
this patch works by simply updating the inferior and inferior_ptid on
failure.

Tested by building an unsigned gdb on macOS and trying to run an
inferior.

gdb/ChangeLog
2018-07-03  Tom Tromey  <tom@tromey.com>

	PR cli/23340:
	* darwin-nat.c (darwin_attach_pid): Reset inferior and
	inferior_ptid on error.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GNU attribute output on errors
@ 2018-07-03  7:50 sergiodj+buildbot
  2018-07-03  8:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03  7:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8d2c8c3d17926826864f4b739362f66af547428f ***

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

GNU attribute output on errors

.gnu.attributes entries from linker input files are merged to the
output file, the output having the union of compatible input
attributes.  Incompatible attributes generally cause a linker error
and no output.  However in some cases only a warning is emitted, and
one of the incompatible input attributes is passed on to the output.

PowerPC tends to emit warnings rather than errors, and the output
takes the first input attribute.  For example, if we have two input
files with Tag_GNU_Power_ABI_FP, the first with a value signifying
"double-precision hard float, IBM long double", the second with a
value signifying "double-precision hard float, IEEE long double",
we'll get a warning about incompatible long double types and the
output will say "double-precision hard float, IBM long double".
The output attribute of course isn't correct.  It would be correct to
specify "IBM and IEEE long double", but we don't have a way to
represent that currently.  While it would be possible to extend the
encoding, there isn't much gain in doing so.  A shared library
providing support for both long double types should link against
objects using either long double type without warning or error.  That
is what you'd get if such a shared library had no Tag_GNU_Power_ABI_FP
attribute.

So this patch provides a way for the backend to omit .gnu.attributes
tags from the output.

	* elf-bfd.h (ATTR_TYPE_FLAG_ERROR, ATTR_TYPE_HAS_ERROR): Define.
	* elf-attrs.c (is_default_attr): Handle ATTR_TYPE_HAS_ERROR.
	* elf32-ppc.c (_bfd_elf_ppc_merge_fp_attributes): Use
	ATTR_TYPE_FLAG_INT_VAL.  Set ATTR_TYPE_HAS_ERROR on finding
	incompatible attribute.
	(ppc_elf_merge_obj_attributes): Likewise.  Return
	_bfd_elf_merge_object_attributes result.
	* elf64-ppc.c (ppc64_elf_merge_private_bfd_data): Return
	_bfd_elf_merge_object_attributes result.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/BFD: Make section GC work with `ict_irix5' targets
@ 2018-07-03  1:00 sergiodj+buildbot
  2018-07-03  1:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03  1:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 12f09816cecc4e4ee7574a86846b3a17adbf7904 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 12f09816cecc4e4ee7574a86846b3a17adbf7904

MIPS/BFD: Make section GC work with `ict_irix5' targets

Prevent runtime procedure table symbols, produced with `ict_irix5' MIPS
targets, from being swept in section GC, fixing linker errors like:

./ld-new: tmpdir/dump: protected symbol `_procedure_table_size' isn't defined
./ld-new: final link failed: bad value

triggered whenever section GC is enabled with those targets and
consequently removing the following test suite failures:

FAIL: Build pr22649-2a.so
FAIL: Build pr22649-2c.so
FAIL: PR ld/20828 dynamic symbols with section GC (auxiliary shared library)
FAIL: PR ld/20828 dynamic symbols with section GC (plain)
FAIL: PR ld/20828 dynamic symbols with section GC (version script)
FAIL: PR ld/20828 dynamic symbols with section GC (versioned shared library)
FAIL: PR ld/20828 dynamic symbols with section GC (versioned)
FAIL: --gc-sections with .text._init
FAIL: pr20022

observed with `mips-elf', `tx39-elf', `mipsisa32-elf', `mipsisa64-elf',
`mipsel-elf', `mipsisa32el-elf', `mipsisa64el-elf', `mips64vr-elf',
`mips64vrel-elf', `mips64vr4300-elf', `mips64vr4300el-elf',
`mips-sgi-irix5' and `mips-rtems' targets, among others.  This fix makes
section GC usable with the affected targets.

	bfd/
	* elfxx-mips.c (_bfd_mips_elf_create_dynamic_sections): Set
	`mark' for symbols created from `mips_elf_dynsym_rtproc_names'
	list.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] microMIPS/BFD: Add missing NewABI TLS and miscellaneous relocations
@ 2018-07-03  0:01 sergiodj+buildbot
  2018-07-03  0:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-03  0:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 156f2c001e22dfeee69c92bdb380d5eb28a3de78 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 156f2c001e22dfeee69c92bdb380d5eb28a3de78

microMIPS/BFD: Add missing NewABI TLS and miscellaneous relocations

Complement commit df58fc944dbc ("MIPS: microMIPS ASE support"),
<https://sourceware.org/ml/binutils/2011-07/msg00198.html>, and add TLS
and a few miscellaneous relocations to NewABI microMIPS support, fixing
GAS assertion failures:

.../gas/testsuite/gas/mips/elf-rel28.s: Assembler messages:
.../gas/testsuite/gas/mips/elf-rel28.s:19: Internal error in append_insn at .../gas/config/tc-mips.c:7660.
Please report this bug.

observed if an attempt is made to assemble the `elf-rel28.s' test case
to microMIPS code.  The relocations are the same as with o32 support,
except for `partial_inplace' and `src_mask' updates for the respective
RELA variants.

	bfd/
	* elf64-mips.c (micromips_elf64_howto_table_rel): Add
	R_MICROMIPS_HI0_LO16, R_MICROMIPS_TLS_GD, R_MICROMIPS_TLS_LDM,
	R_MICROMIPS_TLS_DTPREL_HI16, R_MICROMIPS_TLS_DTPREL_LO16,
	R_MICROMIPS_TLS_GOTTPREL, R_MICROMIPS_TLS_TPREL_HI16,
	R_MICROMIPS_TLS_TPREL_LO16, R_MICROMIPS_GPREL7_S2 and
	R_MICROMIPS_PC23_S2 relocation entries.
	(micromips_elf64_howto_table_rela): Likewise.
	(micromips_reloc_map): Likewise.
	* elfn32-mips.c (elf_micromips_howto_table_rel): Likewise.
	(elf_micromips_howto_table_rela): Likewise.
	(micromips_reloc_map): Likewise.

	gas/
	* testsuite/gas/mips/elf-rel28-micromips-n32.d: New test.
	* testsuite/gas/mips/elf-rel28-micromips-n64.d: New test.
	* testsuite/gas/mips/mips.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] GDB PR tdep/8282: MIPS: Wire in `set disassembler-options'
@ 2018-07-02 23:22 sergiodj+buildbot
  2018-07-02 23:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-02 23:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 471b9d15076fffb738f1bc6fcea41d0dcb59c947 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 471b9d15076fffb738f1bc6fcea41d0dcb59c947

GDB PR tdep/8282: MIPS: Wire in `set disassembler-options'

Implement MIPS target support for passing options to the disassembler,
complementing commit 65b48a81404c ("GDB: Add support for the new
set/show disassembler-options commands.").

This includes options that expect an argument, so adjust the generic
code and data structures used so as to handle such options.  So as to
give backends syntax flexibility no specific delimiter has been defined
to separate options from their respective arguments, so it has to be
included as the last character of the option name.  Completion code
however has not been adjusted and consequently option arguments cannot
be completed at this time.

Also the MIPS target has non-empty defaults for the options, so that ABI
names for the general-purpose registers respect our `set mips abi ...'
setting rather than always being determined from the ELF headers of the
binary file selected.  Handle these defaults as implicit options, never
shown to the user and always prepended to the user-specified options, so
that the latters can override the defaults.

The resulting output for the MIPS target is as follows:

(gdb) show disassembler-options
The current disassembler options are ''

The following disassembler options are supported for use with the
'set disassembler-options <option>[,<option>...]' command:

  no-aliases      Use canonical instruction forms.

  msa             Recognize MSA instructions.

  virt            Recognize the virtualization ASE instructions.

  xpa             Recognize the eXtended Physical Address (XPA) ASE
                  instructions.

  ginv            Recognize the Global INValidate (GINV) ASE instructions.

  gpr-names=ABI   Print GPR names according to specified ABI.
                  Default: based on binary being disassembled.

  fpr-names=ABI   Print FPR names according to specified ABI.
                  Default: numeric.

  cp0-names=ARCH  Print CP0 register names according to specified architecture.
                  Default: based on binary being disassembled.

  hwr-names=ARCH  Print HWR names according to specified architecture.
                  Default: based on binary being disassembled.

  reg-names=ABI   Print GPR and FPR names according to specified ABI.

  reg-names=ARCH  Print CP0 register and HWR names according to specified
                  architecture.

  For the options above, the following values are supported for "ABI":
    numeric 32 n32 64

  For the options above, the following values are supported for "ARCH":
    numeric r3000 r3900 r4000 r4010 vr4100 vr4111 vr4120 r4300 r4400 r4600
    r4650 r5000 vr5400 vr5500 r5900 r6000 rm7000 rm9000 r8000 r10000 r12000
    r14000 r16000 mips5 mips32 mips32r2 mips32r3 mips32r5 mips32r6 mips64
    mips64r2 mips64r3 mips64r5 mips64r6 interaptiv-mr2 sb1 loongson2e
    loongson2f loongson3a octeon octeon+ octeon2 octeon3 xlr xlp
(gdb)

which corresponds to what `objdump --help' used to print for the MIPS
target, with minor formatting changes, most notably option argument
lists being wrapped, but also the amount of white space separating
options from the respective descriptions.  The relevant part the new
code is now also used by `objdump --help', which means these formatting
changes apply to both outputs, except for argument list wrapping, which
is GDB-specific.

This also adds a separating new line between the heading and option
lists where descriptions are provided, hence:

(gdb) set architecture s390:31-bit
(gdb) show disassembler-options
The current disassembler options are ''

The following disassembler options are supported for use with the
'set disassembler-options <option>[,<option>...]' command:

  esa         Disassemble in ESA architecture mode
  zarch       Disassemble in z/Architecture mode
  insnlength  Print unknown instructions according to length from first two bits
(gdb)

but:

(gdb) set architecture powerpc:common
(gdb) show disassembler-options
The current disassembler options are ''

The following disassembler options are supported for use with the
'set disassembler-options <option>[,<option>...]' command:
  403, 405, 440, 464, 476, 601, 603, 604, 620, 7400, 7410, 7450, 7455, 750cl,
  821, 850, 860, a2, altivec, any, booke, booke32, cell, com, e200z4, e300,
  e500, e500mc, e500mc64, e5500, e6500, e500x2, efs, efs2, power4, power5,
  power6, power7, power8, power9, ppc, ppc32, 32, ppc64, 64, ppc64bridge,
  ppcps, pwr, pwr2, pwr4, pwr5, pwr5x, pwr6, pwr7, pwr8, pwr9, pwrx, raw, spe,
  spe2, titan, vle, vsx
(gdb)

Existing affected target backends have been adjusted accordingly.

This has been verified manually with:

(gdb) set architecture arm
(gdb) set architecture powerpc:common
(gdb) set architecture s390:31-bit

to cause no issues with the `show disassembler-options' and `set
disassembler-options' commands.  A test case for the MIPS target has
also been provided, covering the default settings with ABI overrides as
well as disassembler option overrides.

2018-07-02  Maciej W. Rozycki  <macro@mips.com>
            Simon Marchi  <simon.marchi@polymtl.ca>

	include/
	PR tdep/8282
	* dis-asm.h (disasm_option_arg_t): New typedef.
	(disasm_options_and_args_t): Likewise.
	(disasm_options_t): Add `arg' member, document members.
	(disassembler_options_mips): New prototype.
	(disassembler_options_arm, disassembler_options_powerpc)
	(disassembler_options_s390): Update prototypes.

	opcodes/
	PR tdep/8282
	* mips-dis.c (mips_option_arg_t): New enumeration.
	(mips_options): New variable.
	(disassembler_options_mips): New function.
	(print_mips_disassembler_options): Reimplement in terms of
	`disassembler_options_mips'.
	* arm-dis.c (disassembler_options_arm): Adapt to using the
	`disasm_options_and_args_t' structure.
	* ppc-dis.c (disassembler_options_powerpc): Likewise.
	* s390-dis.c (disassembler_options_s390): Likewise.

	gdb/
	PR tdep/8282
	* disasm.h (gdb_disassembler): Add
	`m_disassembler_options_holder'. member
	* disasm.c (get_all_disassembler_options): New function.
	(gdb_disassembler::gdb_disassembler): Use it.
	(gdb_buffered_insn_length_init_dis): Likewise.
	(gdb_buffered_insn_length): Adjust accordingly.
	(set_disassembler_options): Handle options with arguments.
	(show_disassembler_options_sfunc): Likewise.  Add a leading new
	line if showing options with descriptions.
	(disassembler_options_completer): Adapt to using the
	`disasm_options_and_args_t' structure.
	* mips-tdep.c (mips_disassembler_options): New variable.
	(mips_disassembler_options_o32): Likewise.
	(mips_disassembler_options_n32): Likewise.
	(mips_disassembler_options_n64): Likewise.
	(gdb_print_insn_mips): Don't set `disassembler_options'.
	(gdb_print_insn_mips_n32, gdb_print_insn_mips_n64): Remove
	functions.
	(mips_gdbarch_init): Always set `gdbarch_print_insn' to
	`gdb_print_insn_mips'.  Set `gdbarch_disassembler_options',
	`gdbarch_disassembler_options_implicit' and
	`gdbarch_valid_disassembler_options'.
	* arm-tdep.c (_initialize_arm_tdep): Adapt to using the
	`disasm_options_and_args_t' structure.
	* gdbarch.sh (disassembler_options_implicit): New `gdbarch'
	method.
	(valid_disassembler_options): Switch from `disasm_options_t' to
	the `disasm_options_and_args_t' structure.
	* NEWS: Document `set disassembler-options' support for the MIPS
	target.
	* gdbarch.h: Regenerate.
	* gdbarch.c: Regenerate.

	gdb/doc/
	PR tdep/8282
	* gdb.texinfo (Source and Machine Code): Document `set
	disassembler-options' support for the MIPS target.

	gdb/testsuite/
	PR tdep/8282
	* gdb.arch/mips-disassembler-options.exp: New test.
	* gdb.arch/mips-disassembler-options.s: New test source.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86-64: Clear the R_X86_64_converted_reloc_bit bit
@ 2018-07-02 20:29 sergiodj+buildbot
  2018-07-02 20:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-02 20:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b638b5d57fafc84a8dc0ff91d7579a3c24aad90c ***

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

x86-64: Clear the R_X86_64_converted_reloc_bit bit

We need to clear the R_X86_64_converted_reloc_bit bit after setting it
to avoid leaking it out by --emit-relocs.

bfd/

	PR ld/23324
	* elf64-x86-64.c (elf_x86_64_relocate_section): Clear the
	R_X86_64_converted_reloc_bit bit.

ld/

	PR ld/23324
	* testsuite/ld-x86-64/pr23324.s: New file.
	* testsuite/ld-x86-64/pr23324a.d: Likewise.
	* testsuite/ld-x86-64/pr23324b.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Prefer RISC-V register name "s0" over "fp"
@ 2018-07-02 13:44 sergiodj+buildbot
  2018-07-02 14:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-02 13:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41823f29a811bb250ae274652281a6294fdc2530 ***

Author: Sebastian Huber <sebastian.huber@embedded-brains.de>
Branch: master
Commit: 41823f29a811bb250ae274652281a6294fdc2530

gdb: Prefer RISC-V register name "s0" over "fp"

The "fp" register name is an alias for "s0" which is an alias for "x8".
The "fp" name is only understood by very recent Binutils and thus not
used by GCC.  GCC does not emit a frame pointer with common optimization
options such as -Og or -O2.

It is still possible to use the "fp" register name, e.g.

  (gdb) p/x $fp
  $1 = 0x800367c8

works.

However, in the register dump you see now:

  (gdb) info registers
  ...
  t2             0xffffffffffffffff       18446744073709551615
  s0             0x800367c8       0x800367c8
  s1             0x80033280       2147693184
  ...

gdb/

	* riscv-tdep.c (riscv_register_aliases): Swap "fp" and "s0"
	entries.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [ARM] Update bfd's Tag_CPU_arch knowledge
@ 2018-07-02 10:50 sergiodj+buildbot
  2018-07-02 11:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-07-02 10:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0c468d562649df0f695737262b6230b7a56a4bb ***

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

[ARM] Update bfd's Tag_CPU_arch knowledge

BFD's bfd_get_mach () function returns a bfd specific value representing
the architecture of the target which is populated from the Tag_CPU_arch
build attribute value of that target. Among other users of that
interfacem, objdump which uses it to print the architecture version of
the binary being examinated and to decide what instruction is available
if run with "-m arm" via its own mapping from bfd_mach_arm_X values to
feature bits available.

However, both BFD and objdump's most recent known architecture is
Armv5TE. When encountering a newer architecture bfd_get_mach will return
bfd_mach_arm_unknown. This is unfortunate since objdump uses that value
to allow all instructions on all architectures which is already what it
does by default, making the "-m arm" trick useless.

This patch updates BFD and objdump's knowledge of Arm architecture
versions up to the latest Armv8-M Baseline and Mainline, Armv8-R and
Armv8.4-A architectures. Since several architecture versions (eg. 8.X-A)
share the same Tag_CPU_arch build attribute value and
bfd_mach_arm values, the mapping from bfd machine value to feature bits
need to return the most featureful feature bits that would yield the
given bfd machine value otherwise some instruction would not disassemble
under "-m arm" mode. The patch rework that mapping to make this clearer
and simplify writing the mapping rules. In particular, for simplicity
all FPU instructions are allowed in all cases.

Finally, the patch also rewrite the cpu_arch_ver table in GAS to use the
TAG_CPU_ARCH_X macros rather than hardcode their value.

2018-07-02  Thomas Preud'homme  <thomas.preudhomme@arm.com>

bfd/
	* archures.c (bfd_mach_arm_5TEJ, bfd_mach_arm_6, bfd_mach_arm_6KZ,
	bfd_mach_arm_6T2, bfd_mach_arm_6K, bfd_mach_arm_7, bfd_mach_arm_6M,
	bfd_mach_arm_6SM, bfd_mach_arm_7EM, bfd_mach_arm_8, bfd_mach_arm_8R,
	bfd_mach_arm_8M_BASE, bfd_mach_arm_8M_MAIN): Define.
	* bfd-in2.h: Regenerate.
	* cpu-arm.c (arch_info_struct): Add entries for above new
	bfd_mach_arm values.
	* elf32-arm.c (bfd_arm_get_mach_from_attributes): Add Tag_CPU_arch to
	bfd_mach_arm mapping logic for pre Armv4 and Armv5TEJ and later
	architectures.  Force assert failure for any new Tag_CPU_arch value.

gas/
	* config/tc-arm.c (cpu_arch_ver): Use symbolic TAG_CPU_ARCH macros
	rather than hardcode their values.

ld/
	* arm-dis.c (select_arm_features): Fix typo in heading comment.  Allow
	all FPU features and add mapping from new bfd_mach_arm values to
	allowed CPU feature bits.

opcodes/
	* testsuite/ld-arm/tls-descrelax-be8.d: Add architecture version in
	expected result.
	* testsuite/ld-arm/tls-descrelax-v7.d: Likewise.
	* testsuite/ld-arm/tls-longplt-lib.d: Likewise.
	* testsuite/ld-arm/tls-longplt.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add missing parameter to 'amd64_create_target_description' (and unbreak build)
@ 2018-06-30  2:07 sergiodj+buildbot
  2018-06-30  3:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-30  2:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c0867626d277101afcead91e94f20cbe89a3aced ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: c0867626d277101afcead91e94f20cbe89a3aced

Add missing parameter to 'amd64_create_target_description' (and unbreak build)

While building gdbserver on GNU/Linux, the build failed with:

  ../../../binutils-gdb/gdb/gdbserver/linux-x86-tdesc.c: In function const target_desc* amd64_linux_read_description(uint64_t, bool):
  ../../../binutils-gdb/gdb/gdbserver/linux-x86-tdesc.c:121:67: error: too few arguments to function target_desc* amd64_create_target_description(uint64_t, bool, bool, bool)
         *tdesc = amd64_create_target_description (xcr0, is_x32, true);
                                                                     ^
  In file included from ../../../binutils-gdb/gdb/gdbserver/linux-x86-tdesc.c:26:0:
  ../../../binutils-gdb/gdb/gdbserver/../arch/amd64.h:21:14: note: declared here
   target_desc *amd64_create_target_description (uint64_t xcr0, bool is_x32,
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

According to Joel Brobecker:

> I think the parameter should be set to "true". Otherwise, it will
> not include the fs_base and gs_base register in the list of registers.
> Although the name of the source file says x86, the code itself is
> protected by...
>
>     #ifdef __x86_64__
>
> ... and is inside a function called amd64_linux_read_description.
> I also verified that this file gets compiled on amd64-linux platforms.
> See gdb/gdbserver/configure.srv:
>
>   x86_64-*-linux*)      srv_regobj="$srv_amd64_linux_regobj $srv_i386_linux_regobj"
>
> The last piece of confirmation is that setting the parameter to "true"
> provides the behavior before the parameter was added; and the reason
> for adding the parameter was to remove the {fs,gs}_base registers
> from the list for Windows only.

Therefore I'm pushing the patch to unbreak the build.

gdb/gdbserver/ChangeLog:
2018-06-29  Joel Brobecker  <brobecker@adacore.com>

	* linux-x86-tdesc.c (amd64_linux_read_description): Add missing
	parameter in call to 'amd64_create_target_description'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] fix GDB build failure for various amd64 targets
@ 2018-06-29 23:09 sergiodj+buildbot
  2018-06-29 23:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 23:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41206e32fb909ebacf6db009fc1f177bde74a652 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 41206e32fb909ebacf6db009fc1f177bde74a652

fix GDB build failure for various amd64 targets

The following patch caused some amd64-*-tdep files to fail to compile:

  | commit de52b9607d2623f18b7a7dbee3e1123d8d63f5da
  | Date:   Tue Jun 26 16:33:27 2018 +0100
  | Subject: x86_64-windows GDB crash due to fs_base/gs_base registers

This is because we added one additional "segments" argument to
function amd64_target_description and forgot to update all the callers.
This patch fixes the omissions.

gdb/ChangeLog:

        * amd64-darwin-tdep.c (x86_darwin_init_abi_64): Add missing
        parameter in call to amd64_target_description.
        * amd64-dicos-tdep.c (amd64_dicos_init_abi): Likewise.
        * amd64-fbsd-tdep.c (amd64fbsd_core_read_description)
        (amd64fbsd_init_abi): Likewise.
        * amd64-nbsd-tdep.c (amd64nbsd_init_abi): Likewise.
        * amd64-obsd-tdep.c (amd64obsd_init_abi): Likewise.
        * amd64-sol2-tdep.c (amd64_sol2_init_abi): Likewise.
        * amd64-fbsd-nat.c (amd64_fbsd_nat_target): Likewise.

The change to amd64-fbsd-nat.c was done "blind" (no access to system),
but is reasonably straightforward. The changes to the -tdep.c files
were verify by rebuilding GDB on x86_64-linux when configured with
--enable-targets=all.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Improve alignment of "info threads" output, align "Target Id" column
@ 2018-06-29 21:10 sergiodj+buildbot
  2018-06-29 21:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 21:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75acb4867dc8bdd701983af6899d823c9e2e53a4 ***

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

Improve alignment of "info threads" output, align "Target Id" column

It's long annoyed me that "info threads"'s columns are misaligned.

Particularly the "Target Id" column's content is usually longer than
the specified column width, so the table ends up with the "Frame"
column misaligned.  For example, currently we get this:

 (gdb) info threads
   Id   Target Id         Frame
   1    Thread 0x7ffff7fb5740 (LWP 9056) "threads" 0x00007ffff7bc28ad in __pthread_join (threadid=140737345763072, thread_return=0x7fffffffd3e8) at pthread_join.c:90
   2    Thread 0x7ffff7803700 (LWP 9060) "function0" thread_function0 (arg=0x0) at threads.c:90
 * 3    Thread 0x7ffff7002700 (LWP 9061) "threads" thread_function1 (arg=0x1) at threads.c:106

The fact that the "Frame" heading is in a weird spot is particularly
annoying.

This commit turns the above into into this:

 (gdb) info threads
   Id   Target Id                                    Frame
   1    Thread 0x7ffff7fb5740 (LWP 7548) "threads"   0x00007ffff7bc28ad in __pthread_join (threadid=140737345763072, thread_return=0x7fffffffd3e8) at pthread_join.c:90
   2    Thread 0x7ffff7803700 (LWP 7555) "function0" thread_function0 (arg=0x0) at threads.c:91
 * 3    Thread 0x7ffff7002700 (LWP 7557) "threads"   thread_function1 (arg=0x1) at threads.c:104

It does that by computing the max width of the "Target Id" column and
using that as column width when creating the table.

This results in calling target_pid_to_str / target_extra_thread_info /
target_thread_name twice for each thread, but I think that it doesn't
matter in practice performance-wise, because the remote target caches
the info, and with native targets it shouldn't be noticeable.  It
could matter if we have many threads (say, thousands), but then "info
threads" is practically useless in such a scenario anyway -- better
thread filtering and aggregation would be necessary.

(Note: I have an old branch somewhere where I attempted at making
gdb's "info threads"-like tables follow a model/view design, so that a
general framework took care of issues like these, but it's incomplete
and a much bigger change.  This patch doesn't prevent going in that
direction in the future, of course.)

gdb/ChangeLog:
2018-06-29  Pedro Alves  <palves@redhat.com>

	* thread.c (thread_target_id_str): New, factored out from ...
	(print_thread_info_1): ... here.  Use it to compute the max
	"Target Id" column width.

gdb/testsuite/ChangeLog:
2018-06-29  Pedro Alves  <palves@redhat.com>

	* gdb.threads/names.exp: Adjust expected "info threads" output.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote & target_extra_thread_info, use cache w/ qThreadExtraInfo and qP too
@ 2018-06-29 20:19 sergiodj+buildbot
  2018-06-29 20:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 20:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c76a8ea36c9567b2b194285ceeae29bbfc26b20a ***

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

remote & target_extra_thread_info, use cache w/ qThreadExtraInfo and qP too

The following patch will make "info threads" call target_extra_thread_info
more frequently.  When I looked at the remote implementation, I noticed
that if we're not using qXfer:threads:read, then we'd be increasing the
remote protocol traffic.  This commit prevents that from happening.

Also, it removes a gratuitous local static buffer, which seems good on
its own.

gdb/ChangeLog:
2018-06-29  Pedro Alves  <palves@redhat.com>

	* remote.c (remote_target::extra_thread_info): Delete
	'display_buf' and 'n' locals.  from the cache, regardless of
	packet mechanims is in use.  Use cache for qThreadExtra and qP
	methods too.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] "break LINENO/*ADDRESS", inline functions and "info break" output
@ 2018-06-29 19:23 sergiodj+buildbot
  2018-06-29 20:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 19:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cd2bb709940d33668fe6dbe8d4ffee0ed44c25e6 ***

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

"break LINENO/*ADDRESS", inline functions and "info break" output

While experimenting with the previous patch, I noticed this inconsistency
in GDB's output:

  (gdb) b 32
  Breakpoint 1 at 0x40062f: file inline-break.c, line 32.                  (1)
  (gdb) r
  ....
  Breakpoint 1, func1 (x=1) at inline-break.c:32                           (2)
  32        return x * 23; /* break here */
  (gdb) info breakpoints
  Num     Type           Disp Enb Address    What
  1       breakpoint     keep y   0x40062f   in main at inline-break.c:32  (3)
	  breakpoint already hit 1 time
  (gdb)

Notice that when the breakpoint as set, GDB showed "inline-break.c,
line 32" (1), the same line number that was specified in the command.

When we run to the breakpoint, we present the stop at the same line
number, and correctly show "func1" as the function name (2).

But in "info break" output (3), notice that we say "in main", not "in
func1".

The same thing happens if you set a breakpoint by address.  I.e.:

  (gdb) b *0x40062f
  Breakpoint 2 at 0x40062f: file inline-break.c, line 32.
  (gdb) info breakpoints
  Num     Type           Disp Enb Address            What
  2       breakpoint     keep y   0x000000000040062f in main at inline-break.c:32
   (gdb) r
   ....
  Breakpoint 2, func1 (x=1) at inline-break.c:32
  32        return x * 23; /* break here */

The problem is that the breakpoints were set at an inline function,
but when we set such a breakpoint by line number or address, we don't
record the functions symbol in the sal, and as consequence the
breakpoint location does not have an associated symbol either.

Then, in print_breakpoint_location, if the location does not have a
symbol, we call find_pc_sect_function to find one, and this is what
finds "main", because find_pc_sect_function uses
block_linkage_function:

  /* Return the symbol for the function which contains a specified
     lexical block, described by a struct block BL.  The return value
     will not be an inlined function; the containing function will be
     returned instead.  */

  struct symbol *
  block_linkage_function (const struct block *bl)

To fix this, this commit adds an alternative to find_pc_sect_function
that uses block_containing_function instead:

  /* Return the symbol for the function which contains a specified
     block, described by a struct block BL.  The return value will be
     the closest enclosing function, which might be an inline
     function.  */

  struct symbol *
  block_containing_function (const struct block *bl)

(It seems odd to me that block_linkage_function says "the CONTAINING
function will be returned", and then block_containing_function says it
returns "the closest enclosing function".  Something seems reversed
here.  Still, I've kept the same nomenclature and copied the comments,
so that at least there's consistency.  Maybe we should fix that up
somehow.)

Then I wondered, why make print_breakpoint_location look up the symbol
every time it is called, instead of just always storing the symbol
when the location is created, since the location already stores the
symbol in some cases.  So to find which cases might be missing setting
the symbol in the sal which is used to create the breakpoint location,
I added an assertion to print_breakpoint_location, and ran the
testsuite.  That caught a few places, unsurprisingly:

 - setting a breakpoint by line number
 - setting a breapoint by address
 - ifunc resolving

Those are all fixed by this commit.  I decided not to add the
assertion to block_linkage_function and leave the existing "if (sym)"
check in place, because it's plausible that we have symtabs with line
info but no symbols.  I.e., that would not be a GDB bug, but
a peculiarity of debug info input.

gdb/ChangeLog:
2018-06-29  Pedro Alves  <palves@redhat.com>

	* blockframe.c (find_pc_sect_containing_function): New function.
	* breakpoint.c (print_breakpoint_location): Don't call
	find_pc_sect_function.
	* linespec.c (create_sals_line_offset): Record the location's
	symbol in the sal.
	* linespec.c (convert_address_location_to_sals): Fill in sal's
	symbol with find_pc_sect_containing_function.
	* symtab.c (find_function_start_sal): Rename to ...
	(find_function_start_sal_1): ... this.
	(find_function_start_sal): Reimplement as wrapper around
	find_function_start_sal_1, and use
	find_pc_sect_containing_function to fill in the sal's symbol.
	(find_function_start_sal(symbol*, bool)): Adjust.
	* symtab.h (find_pc_function, find_pc_sect_function): Adjust
	comments.
	(find_pc_sect_containing_function): Declare.

gdb/testsuite/ChangeLog:
2018-06-29  Pedro Alves  <palves@redhat.com>

	* gdb.opt/inline-break.exp (line number, address): Add "info
	break" tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove unstable test output
@ 2018-06-29 17:02 sergiodj+buildbot
  2018-06-29 17:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 49af4b7012b682470bba3d66262bd34f48b9f500 ***

Author: Richard Bunt <richard.bunt@arm.com>
Branch: master
Commit: 49af4b7012b682470bba3d66262bd34f48b9f500

Remove unstable test output

Changed test output from:
PASS: gdb.base/watchpoint-hw-attach.exp: attach 25501
to
PASS: gdb.base/watchpoint-hw-attach.exp: attach

gdb/testsuite/ChangeLog:

	* gdb.base/watchpoint-hw-attach.exp: Remove unstable output.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/BFD: Remove extraneous undefined weak symbol visibility check
@ 2018-06-29 15:19 sergiodj+buildbot
  2018-06-29 15:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 15:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 262e07d0115adc08cf7481689d9d146a01ee5bb8 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 262e07d0115adc08cf7481689d9d146a01ee5bb8

MIPS/BFD: Remove extraneous undefined weak symbol visibility check

Remove an extraneous symbol visibility check made for undefined weak
symbols in determination whether an R_MIPS_REL32 dynamic relocation has
to be placed in output, complementing commit ad9512030937 ("mips: Check
UNDEFWEAK_NO_DYNAMIC_RELOC").  That check duplicates one already made by
the UNDEFWEAK_NO_DYNAMIC_RELOC macro as a part of a broader condition
used to decide if to enter undefined weak symbols to the dynamic symbol
table or not.

	bfd/
	* elfxx-mips.c (allocate_dynrelocs): Remove extraneous symbol
	visibility check made for undefined weak symbols.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix AArch64 encodings for by element instructions.
@ 2018-06-29 11:46 sergiodj+buildbot
  2018-06-29 11:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-29 11:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 369c9167d47e69aad2e260cc1db17f8c894c138b ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 369c9167d47e69aad2e260cc1db17f8c894c138b

Fix AArch64 encodings for by element instructions.

Some instructions in Armv8-a place a limitation on FP16 registers that can be
used as the register from which to select an element from.

e.g. fmla restricts Rm to 4 bits when using an FP16 register.  This restriction
does not apply for all instructions, e.g. fcmla does not have this restriction
as it gets an extra bit from the M field.

Unfortunately, this restriction to S_H was added for all _Em operands before,
meaning for a large number of instructions you couldn't use the full register
file.

This fixes the issue by introducing a new operand _Em16 which applies this
restriction only when paired with S_H and leaves the _Em and the other
qualifiers for _Em16 unbounded (i.e. using the full 5 bit range).

Also the patch updates all instructions that should be affected by this.

opcodes/

	PR binutils/23192
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Likewise.
	* aarch64-opc-2.c: Likewise.
	* aarch64-dis.c (aarch64_ext_reglane): Add AARCH64_OPND_Em16 constraint.
	* aarch64-opc.c (operand_general_constraint_met_p,
	aarch64_print_operand): Likewise.
	* aarch64-tbl.h (aarch64_opcode_table): Change Em to Em16 for smlal,
	smlal2, fmla, fmls, fmul, fmulx, sqrdmlah, sqrdlsh, fmlal, fmlsl,
	fmlal2, fmlsl2.
	(AARCH64_OPERANDS): Add Em2.

gas/

	PR binutils/23192
	* config/tc-aarch64.c (process_omitted_operand, parse_operands): Add
	AARCH64_OPND_Em16
	* testsuite/gas/aarch64/advsimd-armv8_3.s: Expand tests to cover upper
	16 registers.
	* testsuite/gas/aarch64/advsimd-armv8_3.d: Likewise.
	* testsuite/gas/aarch64/advsimd-compnum.s: Likewise.
	* testsuite/gas/aarch64/advsimd-compnum.d: Likewise.
	* testsuite/gas/aarch64/sve.d: Likewise.

include/

	PR binutils/23192
	*opcode/aarch64.h (aarch64_opnd): Add AARCH64_OPND_Em16.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix follow-exec regression / crash
@ 2018-06-28 16:39 sergiodj+buildbot
  2018-06-28 16:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-28 16:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ecdc3a72c89e43e0e13c5478723b4f70b3964e9f ***

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

Fix follow-exec regression / crash

After commit 00431a78b28f ("Use thread_info and inferior pointers more
throughout"), following an exec can result in gdb crashing.  On some
systems, this is visible with gdb.multi/multi-arch-exec.exp and
gdb.base/foll-exec-mode.exp.  E.g.:

  $ make check TESTS="gdb.multi/multi-arch-exec.exp gdb.base/foll-exec-mode.exp"
  [snip]
  FAIL: gdb.multi/multi-arch-exec.exp: first_arch=1: selected_thread=1: follow_exec_mode=new: continue across exec that changes architecture (GDB internal error)
  ERROR: : spawn id exp10 not open
      while executing

Running multi-arch-exec under Valgrind we easily spot the problem:

  process 16305 is executing new program: ..../gdb.multi/multi-arch-exec/1-multi-arch-exec-hello
  [New inferior 2 (process 0)]
  [New process 16305]
  ==16129== Invalid read of size 8
  ==16129==    at 0x7FA14D: get_thread_regcache(thread_info*) (regcache.c:399)
  ==16129==    by 0x75E54B: handle_inferior_event_1(execution_control_state*) (infrun.c:5292)
  ==16129==    by 0x75E82D: handle_inferior_event(execution_control_state*) (infrun.c:5382)
  ==16129==    by 0x75BC6A: fetch_inferior_event(void*) (infrun.c:3918)
  ==16129==    by 0x748DA3: inferior_event_handler(inferior_event_type, void*) (inf-loop.c:43)
  ==16129==    by 0x464B5D: handle_target_event(int, void*) (linux-nat.c:4359)
  ==16129==    by 0x7047E0: handle_file_event(file_handler*, int) (event-loop.c:733)
  ==16129==    by 0x704D83: gdb_wait_for_event(int) (event-loop.c:859)
  ==16129==    by 0x703BF6: gdb_do_one_event() (event-loop.c:322)
  ==16129==    by 0x703CA2: start_event_loop() (event-loop.c:371)
  ==16129==    by 0x791D95: captured_command_loop() (main.c:330)
  ==16129==    by 0x79311C: captured_main(void*) (main.c:1157)
  ==16129==  Address 0x15a5bad0 is 32 bytes inside a block of size 600 free'd
  ==16129==    at 0x4C2E1E8: operator delete(void*) (vg_replace_malloc.c:576)
  ==16129==    by 0x8A15D0: delete_thread_1(thread_info*, bool) (thread.c:465)
  ==16129==    by 0x8A15FA: delete_thread(thread_info*) (thread.c:476)
  ==16129==    by 0x8A0D43: add_thread_silent(ptid_t) (thread.c:291)
  ==16129==    by 0x8A0DF0: add_thread_with_info(ptid_t, private_thread_info*) (thread.c:317)
  ==16129==    by 0x8A0E79: add_thread(ptid_t) (thread.c:331)
  ==16129==    by 0x75764C: follow_exec(ptid_t, char*) (infrun.c:1233)
  ==16129==    by 0x75E534: handle_inferior_event_1(execution_control_state*) (infrun.c:5290)
  ==16129==    by 0x75E82D: handle_inferior_event(execution_control_state*) (infrun.c:5382)
  ==16129==    by 0x75BC6A: fetch_inferior_event(void*) (infrun.c:3918)
  ==16129==    by 0x748DA3: inferior_event_handler(inferior_event_type, void*) (inf-loop.c:43)
  ==16129==    by 0x464B5D: handle_target_event(int, void*) (linux-nat.c:4359)

The problem is that handle_inferior_event_1 is reading the stop_pc off
of a thread that was deleted by follow_exec.  Before commit
00431a78b28f, we didn't crash because we were passing down a ptid to
get_thread_regcache instead of ecs->event_thread.

Fix this by simply moving the stop_pc reading until after
ecs->event_thread is refreshed.

gdb/ChangeLog:
2018-06-28  Pedro Alves  <palves@redhat.com>

	* infrun.c (handle_inferior_event_1) <TARGET_WAITKIND_EXECD>:
	Moving fetching stop_pc until after ecs->event_thread is refreshed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fixed top frame assumption in watchpoint-hw-attach
@ 2018-06-28  8:32 sergiodj+buildbot
  2018-06-28  9:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-28  8:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT be1b6474f0d471c01f5c4d1f33e4f13df9ffb82c ***

Author: Richard Bunt <richard.bunt@arm.com>
Branch: master
Commit: be1b6474f0d471c01f5c4d1f33e4f13df9ffb82c

Fixed top frame assumption in watchpoint-hw-attach

watchpoint-hw-attach.exp was noticed to fail on some machines.
Thanks to the input from sergiodj and palves on the IRC channel,
it was concluded that the test case incorrectly assumed that on
attach it was landed in the top-most frame of the inferior. This
was fixed by running to a break point in main by explicitly
defining the source file name before continuing with the test.

Tested on the following architectures x86_64, aarch64 and ppc64le.

gdb/testsuite/ChangeLog:

	* gdb.base/watchpoint-hw-attach.c (main): Remove unneeded
	code.
	* gdb.base/watchpoint-hw-attach.exp: Break in outermost frame.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make sure that sorting does not change section order
@ 2018-06-28  8:08 sergiodj+buildbot
  2018-06-28  8:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-28  8:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d81a3eaff36b41ed67758a119a6864b50f60a60d ***

Author: Petr Tesarik <ptesarik@suse.cz>
Branch: master
Commit: d81a3eaff36b41ed67758a119a6864b50f60a60d

Make sure that sorting does not change section order

Symbol files may contain multiple sections with the same name.
Section addresses specified by add-symbol-file are assigned to the
corresponding BFD sections in addr_info_make_relative using sorted
indexes of both vectors.  Since the sort algorithm is not inherently
stable, the comparison function uses sectindex to maintain the
original order.  However, add_symbol_file_command uses zero for all
sections, so if the user specifies multiple sections with the same
name, they will be assigned randomly to symbol file sections with
the same name.

gdb/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* symfile.c (add_symbol_file_command): Make sure that sections


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make add-symbol-file's address argument optional
@ 2018-06-28  7:44 sergiodj+buildbot
  2018-06-28  7:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-28  7:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ed6dfe517ee323ed631aa8b9816289ea35219409 ***

Author: Petr Tesarik <ptesarik@suse.cz>
Branch: master
Commit: ed6dfe517ee323ed631aa8b9816289ea35219409

Make add-symbol-file's address argument optional

The (first) .text section must be always specified as the second
non-option argument.  The documentation states that GDB cannot
figure out this address by itself.  This is true if the object file
was indeed relocated, but it is also confusing, because all other
sections can be omitted and will use the address provided by BFD.

gdb/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* symfile.c (add_symbol_file_command, _initialize_symfile): Do not
	require the second argument.  If omitted, load sections at the
	addresses specified in the file.

gdb/doc/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* gdb.texinfo (Files): The address argument for "add-symbol-file"
	is no longer mandatory.

gdb/testsuite/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* gdb.base/relocate.exp: Test add-symbol-file behavior when the
	address argument is omitted.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add an optional offset option to the "symbol-file" command
@ 2018-06-28  7:01 sergiodj+buildbot
  2018-06-28  7:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-28  7:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d4d429d589c4d6a4450146fbcac8e1aad445114d ***

Author: Petr Tesarik <ptesarik@suse.cz>
Branch: master
Commit: d4d429d589c4d6a4450146fbcac8e1aad445114d

Add an optional offset option to the "symbol-file" command

If the main file is relocated at runtime, all symbols are offset by
a fixed amount.  Let the user specify this offset when loading a
symbol file.

gdb/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* symfile.c (symbol_file_command, symbol_file_add_main_1)
	(_initialize_symfile): Add option "-o" to symbol-file to add an
	offset to each section of the symbol file.

gdb/doc/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* gdb.texinfo (Files): Document "symbol-file -o offset".

gdb/testsuite/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* gdb.base/relocate.exp: Add test for "symbol-file -o ".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add myself as a write-after-approval GDB maintainer.
@ 2018-06-28  6:51 sergiodj+buildbot
  2018-06-28  6:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-28  6:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39b27ab6ae77d4fe1735417f2de90eada658dc6b ***

Author: Petr Tesarik <ptesarik@suse.cz>
Branch: master
Commit: 39b27ab6ae77d4fe1735417f2de90eada658dc6b

Add myself as a write-after-approval GDB maintainer.

gdb/ChangeLog:
2018-06-28  Petr Tesarik  <ptesarik@suse.cz>

	* MAINTAINERS (Write After Approval): Add Petr Tesarik.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update "func" help text to GNU standards
@ 2018-06-27 21:34 sergiodj+buildbot
  2018-06-27 22:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41827fc34de3463891160a9d57df9f5c58c0b65f ***

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

Update "func" help text to GNU standards

In my earlier series to change help text to follow the GNU standards
for metasyntactic variables, I missed one: the "func" command.  This
patch updates its help text.

Tested by the buildbot.

gdb/ChangeLog
2018-06-27  Tom Tromey  <tom@tromey.com>

	* stack.c (_initialize_stack): Update "func" help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix crash in machoread.c
@ 2018-06-27 21:08 sergiodj+buildbot
  2018-06-27 21:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 21:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6317728958287f0876f04941267de5d87eefa578 ***

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

Fix crash in machoread.c

"./gdb ./gdb" was crashing for me on macOS.  Investigating showed that
macho_symfile_read was crashing because "symbol_table" was being freed
too soon.  This was introduced by my earlier patch to change
macho_symfile_read to use a std::vector.

Tested on macOS 10.13.5 using "./gdb ./gdb".  This should un-break
various already existing tests (testsuite/gdb.gdb at least), so no new
test case.

I'm checking this in as obvious.

gdb/ChangeLog
2018-06-27  Tom Tromey  <tom@tromey.com>

	* machoread.c (macho_symfile_read): Define "symbol_table" earlier.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add pretty-printer for CORE_ADDR
@ 2018-06-27 19:47 sergiodj+buildbot
  2018-06-27 20:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 19:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a14af7b1a6765a353d4bf710d267a1c47a162fb ***

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

Add pretty-printer for CORE_ADDR

Add a pretty-printer that prints CORE_ADDR values in hex.

gdb/ChangeLog:

	* gdb-gdb.py.in (CoreAddrPrettyPrinter): New class.
	(type_lookup_function): Recognize CORE_ADDR values.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb-gdb.py.in: Fix ordering of TypeFlags objects with Python 3
@ 2018-06-27 19:18 sergiodj+buildbot
  2018-06-27 19:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 19:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 68ad5fb9aa5ea8d00f95a19cd0c3ab211fb21f83 ***

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

gdb-gdb.py.in: Fix ordering of TypeFlags objects with Python 3

Python 3 doesn't use __cmp__ to order objects, it uses __lt__.  Because
of this, we get this exception when trying to pretty-print "type"
objects:

I tested it with Python 2.7 as well.

gdb/ChangeLog:

	* gdb-gdb.py.in (TypeFlag) <__cmp__>: Remove.
	<__lt__>: Add.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Copy gdb-gdb.py to build dir
@ 2018-06-27 19:03 sergiodj+buildbot
  2018-06-27 19:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 19:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 141ec9f67f11a34bae5953b2923bb71fc74dd52f ***

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

Copy gdb-gdb.py to build dir

I have thought for a long time how nice it would be to have cool pretty
printers for GDB's internal types.  Well, turns out there are few
already in gdb-gdb.py!  Unfortunately, if you build GDB outside of the
source directory, that file never gets loaded.  top-gdb will look for a
file called

  ../path/to/build/gdb/gdb-gdb.py

but that file is in the source directory at

  ../path/to/src/gdb/gdb-gdb.py

This patch makes it so we copy it to the build directory, just like we
do for gdb-gdb.gdb.  With this, I can at least see the file getting
automatically loaded:

(top-gdb) info pretty-printer
global pretty-printers:
  builtin
    mpx_bound128
  objfile /home/emaisin/build/binutils-gdb/gdb/gdb pretty-printers:
  type_lookup_function

I noticed that running "make" didn't re-generate gdb-gdb.py from
gdb-gdb.py.in.  That's because it's copied when running the configure
script and that's it.  I added a rule in the Makefile for that (and for
gdb-gdb.gdb too) and added them as a dependency to the "all" target.

gdb/ChangeLog:

	* gdb-gdb.py: Move to...
	* gdb-gdb.py.in: ... here.
	* configure.ac (AC_CONFIG_FILES): Add gdb-gdb.py.
	* Makefile.in (all): Add gdb-gdb.gdb and gdb-gdb.py as
	dependencies.
	(distclean): Remove gdb-gdb.py when cleaning.
	(gdb-gdb.py, gdb-gdb.gdb): New rules.
	* configure: Re-generate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix Cell debugging regression
@ 2018-06-27 16:49 sergiodj+buildbot
  2018-06-27 16:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 16:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4c4e7ad46ed77f552e2624d2f711c0ce51714395 ***

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

Fix Cell debugging regression

Commit 00431a78b28f ("Use thread_info and inferior pointers more
throughout") broke Cell multi-arch debugging, because it made the
proc-service routines (ps_lgetregs etc.) access registers using the
SPU architecture if GDB happens to interrupt SPU code.  The
proc-service routines must always operate on the "main" (in this case
PowerPC) architecture, because that's the register set libthread_db
expects to be using.

Restore the previous behavior, but wrapped in a new
get_ps_regcache function with a describing comment.

Also, the ps_l*regs routines have an explicit lwpid parameter that
said commit missed; with the commit mentioned above, we started always
reading the registers off of the current thread, which is incorrect.
That is fixed by this commit too.

gdb/ChangeLog:
2018-06-27  Pedro Alves  <palves@redhat.com>

	* proc-service.c (get_ps_regcache): New.
	(ps_lgetregs, ps_lsetregs, ps_lgetfpregs)
	(ps_lsetfpregs): Use it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix lost line info for symbol at addr zero
@ 2018-06-27 15:41 sergiodj+buildbot
  2018-06-27 15:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 15:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ab6656f274b450942deb8800257c0d2e060fa84 ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: 7ab6656f274b450942deb8800257c0d2e060fa84

Fix lost line info for symbol at addr zero

This patch fixes a unique condition where GDB fails to provide line
information of symbol at address zero when code is compiled with text
address zero but loaded at an offset > 0.

For example lets compile following code snippet:

int main() {
  return 0;
}

gcc -O0 -g3 -nostdlib -emain -Wl,-Ttext=0x00 -o file.out file.c

Start gdb and run:

add-symbol-file file.out 0xffff0000
info line main

GDB will return error saying no line info is available for the symbol.

This is a direct consequence of the fix for PR 12528 where GDB tries to ignore
line table for a function which has been garbage collected by the linker.

As the garbage collected symbols are sent to address zero GDB assumes a symbol
actually placed at address zero as garbage collected.

This was fixed with an additional check address < lowpc. But when symbol is
loaded at an offset lowpc becomes lowpc + offset while no offset is added to
address rather final symbol address is calculated based on baseaddr and address
added together. So in case where symbols are loaded at an offset the condition
address < lowpc will always return true.

This patch fixes this by comparing address against a non offset lowpc.

This patch also adds a GDB test case to replicate this behavior.

gdb:

2018-06-27  Omair Javaid  <omair.javaid@linaro.org>

	PR gdb/21695
	* dwarf2read.c (lnp_state_machine::check_line_address): Update declaration.
	(dwarf_decode_lines_1): Adjust.

gdb/testsuite:

2018-06-27  Omair Javaid  <omair.javaid@linaro.org>

	PR gdb/21695
	* gdb.base/infoline-reloc-main-from-zero.exp: New test.
	* gdb.base/infoline-reloc-main-from-zero.c: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add overrides, fix FreeBSD build
@ 2018-06-27 15:14 sergiodj+buildbot
  2018-06-27 15:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-27 15:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd583225a52f920f71e417ef87092d25553dc85e ***

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

Add overrides, fix FreeBSD build

Fix this:

  CXX    fbsd-nat.o
In file included from fbsd-nat.c:44:
./fbsd-nat.h:40:7: error: 'find_memory_regions' overrides a member function but is not marked 'override' [-Werror,-Winconsistent-missing-override]
  int find_memory_regions (find_memory_region_ftype func, void *data);
      ^
./target.h:702:17: note: overridden virtual function is here
    virtual int find_memory_regions (find_memory_region_ftype func, void *data)
                ^
In file included from fbsd-nat.c:44:
./fbsd-nat.h:42:8: error: 'info_proc' overrides a member function but is not marked 'override' [-Werror,-Winconsistent-missing-override]
  bool info_proc (const char *, enum info_proc_what);
       ^
./target.h:950:18: note: overridden virtual function is here
    virtual bool info_proc (const char *, enum info_proc_what);
                 ^

gdb/ChangeLog:

	* fbsd-nat.h (class fbsd_nat_target) <find_memory_regions>: Add
	override.
	<info_proc>: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Minor reorganization of fetch_registers/store_registers in windows-nat.c
@ 2018-06-26 22:03 sergiodj+buildbot
  2018-06-26 22:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-26 22:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9a325b7b3ff056647de536941eaba911d1d794ad ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 9a325b7b3ff056647de536941eaba911d1d794ad

Minor reorganization of fetch_registers/store_registers in windows-nat.c

This patch is a small reorganizational patch that splits
do_windows_fetch_inferior_registers into two parts:

  (a) One part that first reloads the thread's context when needed,
      and then decides based on the given register number whether
      one register needs to be fetched or all of them.

      This part is moved to windows_nat_target::fetch_registers.

  (b) The rest of the code, which actually fetches the register value
      and supplies it to the regcache.

A similar treatment is applied to do_windows_store_inferior_registers.

This change is preparation work for changing the way we calculate
the location of a given register in the thread context structure,
and should be a no op.

gdb/ChangeLog:

        * windows-nat.c (do_windows_fetch_inferior_registers): Rename
        to windows_fetch_one_register, and only handle the case of
        fetching one register.  Move the code that reloads the context
        and iterates over all registers if R is negative to...
        (windows_nat_target::fetch_registers): ... here.
        (do_windows_store_inferior_registers): Rename to
        windows_store_one_register, and only handle the case of storing
        one register.  Move the code that handles the case where r is
        negative to...
        (windows_nat_target::store_registers) ... here.

Tested on x86-windows and x86_64-windows using AdaCore's testsuite.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move ptype/o printing code to typeprint.c
@ 2018-06-26 21:17 sergiodj+buildbot
  2018-06-26 21:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-26 21:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e0c547d14ae1d5c06b59178f4b1dd1f5e08b3feb ***

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

Move ptype/o printing code to typeprint.c

This moves the hole-printing support code for ptype/o from
c-typeprint.c to be methods on print_offset_data.  This allows the
code to be used from non-C languages.

gdb/ChangeLog
2018-06-26  Tom Tromey  <tom@tromey.com>

	* typeprint.h (struct print_offset_data) <update, finish,
	maybe_print_hole>: New methods.
	<indentation>: New constant.
	* typeprint.c (print_offset_data::indentation): Define.
	(print_offset_data::maybe_print_hole, print_offset_data::update)
	(print_offset_data::finish): Move from c-typeprint.c and rename.
	* c-typeprint.c (OFFSET_SPC_LEN): Remove.
	(print_spaces_filtered_with_print_options): Update.
	(c_print_type_union_field_offset, maybe_print_hole)
	(c_print_type_struct_field_offset): Move to typeprint.c and
	rename.
	(c_type_print_base_struct_union): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Updated translations.
@ 2018-06-26 13:21 sergiodj+buildbot
  2018-06-26 13:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-26 13:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 30aa13067f70ba1d11c35d13be753118c457842c ***

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

Updated translations.

gas	* po/uk.po: Updated Ukranian translation.
bfd	* po/uk.po: Updated Ukranian translation.
ld	* po/uk.po: Updated Ukranian translation.
gold	* po/uk.po: Updated Ukranian translation.

opcodes	* po/uk.po: Updated Ukranian translation.
	* po/de.po: Updated German translation.
	* po/pt_BR.po: Updated Brazilian Portuguese translation.

binutils* po/sv.po: Updated Swedish translation.
	* po/uk.po: Updated Ukranian translation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix spelling mistakes.
@ 2018-06-26 12:14 sergiodj+buildbot
  2018-06-26 12:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-26 12:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT eca4b721468e239a6a1ca7c9bd9c967085067dfe ***

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

Fix spelling mistakes.

opcodes	* nfp-dis.c: Fix spelling mistake.

ld	* emultempl/aarch64elf.em: Fix spelling mistake.
	* emultempl/avrelf.em: Likewise.
	* emultempl/elf32.em: Likewise.

binutils* doc/binutils.texi: Fix spelling mistakes.
	* README--how-to-make-a-release: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: For macOS, s/thread_info/struct thread_info/
@ 2018-06-25 17:40 sergiodj+buildbot
  2018-06-25 18:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-25 17:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75cbc781e371279f4403045be93b07fd8fe7fde5 ***

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

gdb: For macOS, s/thread_info/struct thread_info/

The macOS build currently fails with several instances of this problem:

  In file included from ../../src/gdb/darwin-nat.h:22:0,
		   from ../../src/gdb/i386-darwin-nat.c:37:
  ../../src/gdb/gdbthread.h:376:59: error: type/value mismatch at argument 1 in template parameter list for 'template<class T, class Policy> class gdb::ref_ptr'
     = gdb::ref_ptr<thread_info, refcounted_object_ref_policy>;
							     ^
  ../../src/gdb/gdbthread.h:376:59: note:   expected a type, got 'thread_info'
  ../../src/gdb/gdbthread.h:396:28: error: variable or field 'delete_thread' declared void
   extern void delete_thread (thread_info *thread);
			      ^
(...)

This is because there's a thread_info function in the Darwin/XNU/mach API:

 http://web.mit.edu/darwin/src/modules/xnu/osfmk/man/thread_info.html

Fix this in the same way it had been fixed in commit 7aabaf9d4ad5
("Create private_thread_info hierarchy"), by adding an explicit
"struct" keyword.

gdb/ChangeLog:
2018-06-25  Pedro Alves  <palves@redhat.com>

	* gdbthread.h (thread_info_ref, delete_thread)
	(delete_thread_silent, first_thread_of_inferior)
	(any_thread_of_inferior, switch_to_thread)
	(enable_thread_stack_temporaries)
	(thread_stack_temporaries_enabled_p, push_thread_stack_temporary)
	(get_last_thread_stack_temporary)
	(value_in_thread_stack_temporaries, can_access_registers_thread):
	Spell out "struct thread_info" instead of just "thread_info".
	* inferior.h (notice_new_inferior): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Fix build on several hosts/ports
@ 2018-06-25 17:11 sergiodj+buildbot
  2018-06-25 17:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-25 17:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b7a08269ca53323c5fe190370da281358dfee6b2 ***

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

gdb: Fix build on several hosts/ports

Commit 00431a78b28f ("Use thread_info and inferior pointers more
throughout") missed updating some callers, like e.g.,:

 gdb/remote-sim.c: In member function 'virtual void gdbsim_target::mourn_inferior()':
 gdb/remote-sim.c:1198:50: error: cannot convert 'ptid_t' to 'thread_info*' for argument '1' to 'void delete_thread_silent(thread_info*)'
   delete_thread_silent (sim_data->remote_sim_ptid);

 gdb/mygit/src/gdb/procfs.c: In member function virtual void procfs_target::detach(inferior*, int):
 gdb/mygit/src/gdb/procfs.c:1931:23: error: invalid conversion from int to inferior* [-fpermissive]
    detach_inferior (pid);
			 ^
 In file included from gdb/mygit/src/gdb/procfs.c:24:0:
 gdb/mygit/src/gdb/inferior.h:476:13: note:   initializing argument 1 of void detach_inferior(inferior*)

 etc.

This fixes it.

The delete_thread_silent calls in both go32-nat.c and remote-sim.c are
unnecessary because generic_mourn_inferior calls exit_inferior, which
deletes the inferior's threads.

gdb/ChangeLog:
2018-06-25  Pedro Alves  <palves@redhat.com>

	* windows-nat.c (windows_delete_thread): Use find_thread_ptid and
	pass thread_info pointer to delete_thread.
	(windows_nat_target::detach): Pass inferior pointer to
	detach_inferior.
	* aix-thread.c (sync_threadlists): Pass thread_info pointer to
	delete_thread.
	* bsd-kvm.c (bsd_kvm_target::close): Use discard_all_inferiors.
	* darwin-nat.c (darwin_check_new_threads): Use find_thread_ptid
	and pass a thread_info pointer to delete_thread.
	* fbsd-nat.c (fbsd_nat_target::wait): Use find_thread_ptid and
	pass thread_info pointer to delete_thread.
	* go32-nat.c (go32_nat_target::mourn_inferior): Remove
	delete_thread_silent call.
	* procfs.c (procfs_target::detach): Pass inferior pointer to
	detach_inferior.
	(procfs_target::wait): Pass thread_info pointer to delete_thread.
	* remote-sim.c (gdbsim_target::mourn_inferior): Remove
	delete_thread_silent call.
	* windows-nat.c (windows_delete_thread): Use find_thread_ptid and
	pass thread_info pointer to delete_thread.
	(windows_nat_target::detach): Pass inferior pointer to
	delete_inferior.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Regenerate configure and pot files with updated binutils version number.
@ 2018-06-24 18:48 sergiodj+buildbot
  2018-06-24 19:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-24 18:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71300e2c0c24442979a3d01b8423cfaf8ea83003 ***

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

Regenerate configure and pot files with updated binutils version number.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update version number on development (aka HEAD) branch.
@ 2018-06-24 18:32 sergiodj+buildbot
  2018-06-24 18:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-24 18:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5127f207329b795f865234f4461b230d159e2a22 ***

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

Update version number on development (aka HEAD) branch.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix "info registers" regexes in gdb.base/jit-reader.exp
@ 2018-06-22 18:03 sergiodj+buildbot
  2018-06-22 18:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-22 18:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6d72d289c4718c72f36880876d7460d6da4fa21a ***

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

Fix "info registers" regexes in gdb.base/jit-reader.exp

Commit

  e813d34 ("Align natural-format register values to the same column")

changed the output of "info registers" (tabs to spaces), but didn't
update gdb.base/jit-reader.exp.  Update the regexes to expect spaces
instead.

gdb/testsuite/ChangeLog:

	* gdb.base/jit-reader.exp (jit_reader_test): Expect spaces in
	"info registers" output.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Correct negs aliasing on AArch64.
@ 2018-06-22 11:54 sergiodj+buildbot
  2018-06-22 12:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-22 11:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 514cd3a0f589fa48ca7bc9504c36436c0cbefcb2 ***

Author: Tamar Christina <tamar.christina@arm.com>
Branch: master
Commit: 514cd3a0f589fa48ca7bc9504c36436c0cbefcb2

Correct negs aliasing on AArch64.

This patch fixes a disassembly issue with the aliases to subs with a shifted
register.  The subs instruction with the zero register as destination is
supposed to alias to cmp and when the first input register is the zero register
the subs is supposed to be aliased to negs.

This means that a subs with destination and first input registers the zero
register is supposed to be a cmp.

This is done by raising the priority of the cmp alias.

opcodes/

	* aarch64-tbl.h (aarch64_opcode_table): Fix alias flag for negs
	* aarch64-asm-2.c: Regenerate.
	* aarch64-dis-2.c: Likewise.

gas/

	* testsuite/gas/aarch64/addsub.s: Add negs to zero reg test.
	* testsuite/gas/aarch64/addsub.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix up HAS_SVE_STATE macro
@ 2018-06-22 11:32 sergiodj+buildbot
  2018-06-22 11:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-22 11:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bfd60e344c8001910825a358ad674003738ebb6b ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: bfd60e344c8001910825a358ad674003738ebb6b

Fix up HAS_SVE_STATE macro

Prevents build break on aarch64 Suse.

2018-06-22  Alan Hayward  <alan.hayward@arm.com>

gdb/
	* nat/aarch64-sve-linux-ptrace.h (HAS_SVE_STATE): Use &.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/opcodes: Fix a typo in `-M ginv' option description
@ 2018-06-21 22:06 sergiodj+buildbot
  2018-06-21 23:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21 22:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 385e4d0f27945ef38e19a8fd3ec4cd76ff3b87a5 ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 385e4d0f27945ef38e19a8fd3ec4cd76ff3b87a5

MIPS/opcodes: Fix a typo in `-M ginv' option description

	opcodes/
	* mips-dis.c (print_mips_disassembler_options): Fix a typo in
	`-M ginv' option description.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/BFD: Use enumeration constants for EI_ABIVERSION
@ 2018-06-21 21:05 sergiodj+buildbot
  2018-06-21 21:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21 21:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bb29b84d8c2cc2e91f8dec7f7eb64f03470bd03c ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: bb29b84d8c2cc2e91f8dec7f7eb64f03470bd03c

MIPS/BFD: Use enumeration constants for EI_ABIVERSION

Define enumeration constants based on generated `libc-abis.h' from GNU
libc, adding a MIPS_ prefix as these are port-specific.  Use them to
replace magic numbers stored in the EI_ABIVERSION field of the ELF file
header.

	bfd/
	* elfxx-mips.c (MIPS_LIBC_ABI_DEFAULT, MIPS_LIBC_ABI_MIPS_PLT)
	(MIPS_LIBC_ABI_UNIQUE, MIPS_LIBC_ABI_MIPS_O32_FP64)
	(MIPS_LIBC_ABI_MAX): New enumeration constants.
	(_bfd_mips_post_process_headers): Use them in place of magic
	numbers.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use thread_info and inferior pointers more throughout
@ 2018-06-21 16:38 sergiodj+buildbot
  2018-06-21 16:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21 16:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 00431a78b28f913a9d5c912c49680e39cfd20847 ***

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

Use thread_info and inferior pointers more throughout

This is more preparation bits for multi-target support.

In a multi-target scenario, we need to address the case of different
processes/threads running on different targets that happen to have the
same PID/PTID.  E.g., we can have both process 123 in target 1, and
process 123 in target 2, while they're in reality different processes
running on different machines.  Or maybe we've loaded multiple
instances of the same core file.  Etc.

To address this, in my WIP multi-target branch, threads and processes
are uniquely identified by the (process_stratum target_ops *, ptid_t)
and (process_stratum target_ops *, pid) tuples respectively.  I.e.,
each process_stratum instance has its own thread/process number space.

As you can imagine, that requires passing around target_ops * pointers
in a number of functions where we're currently passing only a ptid_t
or an int.  E.g., when we look up a thread_info object by ptid_t in
find_thread_ptid, the ptid_t alone isn't sufficient.

In many cases though, we already have the thread_info or inferior
pointer handy, but we "lose" it somewhere along the call stack, only
to look it up again by ptid_t/pid.  Since thread_info or inferior
objects know their parent target, if we pass around thread_info or
inferior pointers when possible, we avoid having to add extra
target_ops parameters to many functions, and also, we eliminate a
number of by ptid_t/int lookups.

So that's what this patch does.  In a bit more detail:

- Changes a number of functions and methods to take a thread_info or
  inferior pointer instead of a ptid_t or int parameter.

- Changes a number of structure fields from ptid_t/int to inferior or
  thread_info pointers.

- Uses the inferior_thread() function whenever possible instead of
  inferior_ptid.

- Uses thread_info pointers directly when possible instead of the
  is_running/is_stopped etc. routines that require a lookup.

- A number of functions are eliminated along the way, such as:

  int valid_gdb_inferior_id (int num);
  int pid_to_gdb_inferior_id (int pid);
  int gdb_inferior_id_to_pid (int num);
  int in_inferior_list (int pid);

- A few structures and places hold a thread_info pointer across
  inferior execution, so now they take a strong reference to the
  (refcounted) thread_info object to avoid the thread_info pointer
  getting stale.  This is done in enable_thread_stack_temporaries and
  in the infcall.c code.

- Related, there's a spot in infcall.c where using a RAII object to
  handle the refcount would be handy, so a gdb::ref_ptr specialization
  for thread_info is added (thread_info_ref, in gdbthread.h), along
  with a gdb_ref_ptr policy that works for all refcounted_object types
  (in common/refcounted-object.h).

gdb/ChangeLog:
2018-06-21  Pedro Alves  <palves@redhat.com>

	* ada-lang.h (ada_get_task_number): Take a thread_info pointer
	instead of a ptid_t.  All callers adjusted.
	* ada-tasks.c (ada_get_task_number): Likewise.  All callers
	adjusted.
	(print_ada_task_info, display_current_task_id, task_command_1):
	Adjust.
	* breakpoint.c (watchpoint_in_thread_scope): Adjust to use
	inferior_thread.
	(breakpoint_kind): Adjust.
	(remove_breakpoints_pid): Rename to ...
	(remove_breakpoints_inf): ... this.  Adjust to take an inferior
	pointer.  All callers adjusted.
	(bpstat_clear_actions): Use inferior_thread.
	(get_bpstat_thread): New.
	(bpstat_do_actions): Use it.
	(bpstat_check_breakpoint_conditions, bpstat_stop_status): Adjust
	to take a thread_info pointer.  All callers adjusted.
	(set_longjmp_breakpoint_for_call_dummy, set_momentary_breakpoint)
	(breakpoint_re_set_thread): Use inferior_thread.
	* breakpoint.h (struct inferior): Forward declare.
	(bpstat_stop_status): Update.
	(remove_breakpoints_pid): Delete.
	(remove_breakpoints_inf): New.
	* bsd-uthread.c (bsd_uthread_target::wait)
	(bsd_uthread_target::update_thread_list): Use find_thread_ptid.
	* btrace.c (btrace_add_pc, btrace_enable, btrace_fetch)
	(maint_btrace_packet_history_cmd)
	(maint_btrace_clear_packet_history_cmd): Adjust.
	(maint_btrace_clear_cmd, maint_info_btrace_cmd): Adjust to use
	inferior_thread.
	* cli/cli-interp.c: Include "inferior.h".
	* common/refcounted-object.h (struct
	refcounted_object_ref_policy): New.
	* compile/compile-object-load.c: Include gdbthread.h.
	(store_regs): Use inferior_thread.
	* corelow.c (core_target::close): Use current_inferior.
	(core_target_open): Adjust to use first_thread_of_inferior and use
	the current inferior.
	* ctf.c (ctf_target::close): Adjust to use current_inferior.
	* dummy-frame.c (dummy_frame_id) <ptid>: Delete, replaced by ...
	<thread>: ... this new field.  All references adjusted.
	(dummy_frame_pop, dummy_frame_discard, register_dummy_frame_dtor):
	Take a thread_info pointer instead of a ptid_t.
	* dummy-frame.h (dummy_frame_push, dummy_frame_pop)
	(dummy_frame_discard, register_dummy_frame_dtor): Take a
	thread_info pointer instead of a ptid_t.
	* elfread.c: Include "inferior.h".
	(elf_gnu_ifunc_resolver_stop, elf_gnu_ifunc_resolver_return_stop):
	Use inferior_thread.
	* eval.c (evaluate_subexp): Likewise.
	* frame.c (frame_pop, has_stack_frames, find_frame_sal): Use
	inferior_thread.
	* gdb_proc_service.h (struct thread_info): Forward declare.
	(struct ps_prochandle) <ptid>: Delete, replaced by ...
	<thread>: ... this new field.  All references adjusted.
	* gdbarch.h, gdbarch.c: Regenerate.
	* gdbarch.sh (get_syscall_number): Replace 'ptid' parameter with a
	'thread' parameter.  All implementations and callers adjusted.
	* gdbthread.h (thread_info) <set_running>: New method.
	(delete_thread, delete_thread_silent): Take a thread_info pointer
	instead of a ptid.
	(global_thread_id_to_ptid, ptid_to_global_thread_id): Delete.
	(first_thread_of_process): Delete, replaced by ...
	(first_thread_of_inferior): ... this new function.  All callers
	adjusted.
	(any_live_thread_of_process): Delete, replaced by ...
	(any_live_thread_of_inferior): ... this new function.  All callers
	adjusted.
	(switch_to_thread, switch_to_no_thread): Declare.
	(is_executing): Delete.
	(enable_thread_stack_temporaries): Update comment.
	<enable_thread_stack_temporaries>: Take a thread_info pointer
	instead of a ptid_t.  Incref the thread.
	<~enable_thread_stack_temporaries>: Decref the thread.
	<m_ptid>: Delete
	<m_thr>: New.
	(thread_stack_temporaries_enabled_p, push_thread_stack_temporary)
	(get_last_thread_stack_temporary)
	(value_in_thread_stack_temporaries, can_access_registers_thread):
	Take a thread_info pointer instead of a ptid_t.  All callers
	adjusted.
	* infcall.c (get_call_return_value): Use inferior_thread.
	(run_inferior_call): Work with thread pointers instead of ptid_t.
	(call_function_by_hand_dummy): Work with thread pointers instead
	of ptid_t.  Use thread_info_ref.
	* infcmd.c (proceed_thread_callback): Access thread's state
	directly.
	(ensure_valid_thread, ensure_not_running): Use inferior_thread,
	access thread's state directly.
	(continue_command): Use inferior_thread.
	(info_program_command): Use find_thread_ptid and access thread
	state directly.
	(proceed_after_attach_callback): Use thread state directly.
	(notice_new_inferior): Take a thread_info pointer instead of a
	ptid_t.  All callers adjusted.
	(exit_inferior): Take an inferior pointer instead of a pid.  All
	callers adjusted.
	(exit_inferior_silent): New.
	(detach_inferior): Delete.
	(valid_gdb_inferior_id, pid_to_gdb_inferior_id)
	(gdb_inferior_id_to_pid, in_inferior_list): Delete.
	(detach_inferior_command, kill_inferior_command): Use
	find_inferior_id instead of valid_gdb_inferior_id and
	gdb_inferior_id_to_pid.
	(inferior_command): Use inferior and thread pointers.
	* inferior.h (struct thread_info): Forward declare.
	(notice_new_inferior): Take a thread_info pointer instead of a
	ptid_t.  All callers adjusted.
	(detach_inferior): Delete declaration.
	(exit_inferior, exit_inferior_silent): Take an inferior pointer
	instead of a pid.  All callers adjusted.
	(gdb_inferior_id_to_pid, pid_to_gdb_inferior_id, in_inferior_list)
	(valid_gdb_inferior_id): Delete.
	* infrun.c (follow_fork_inferior, proceed_after_vfork_done)
	(handle_vfork_child_exec_or_exit, follow_exec): Adjust.
	(struct displaced_step_inferior_state) <pid>: Delete, replaced by
	...
	<inf>: ... this new field.
	<step_ptid>: Delete, replaced by ...
	<step_thread>: ... this new field.
	(get_displaced_stepping_state): Take an inferior pointer instead
	of a pid.  All callers adjusted.
	(displaced_step_in_progress_any_inferior): Adjust.
	(displaced_step_in_progress_thread): Take a thread pointer instead
	of a ptid_t.  All callers adjusted.
	(displaced_step_in_progress, add_displaced_stepping_state): Take
	an inferior pointer instead of a pid.  All callers adjusted.
	(get_displaced_step_closure_by_addr): Adjust.
	(remove_displaced_stepping_state): Take an inferior pointer
	instead of a pid.  All callers adjusted.
	(displaced_step_prepare_throw, displaced_step_prepare)
	(displaced_step_fixup): Take a thread pointer instead of a ptid_t.
	All callers adjusted.
	(start_step_over): Adjust.
	(infrun_thread_ptid_changed): Remove bit updating ptids in the
	displaced step queue.
	(do_target_resume): Adjust.
	(fetch_inferior_event): Use inferior_thread.
	(context_switch, get_inferior_stop_soon): Take an
	execution_control_state pointer instead of a ptid_t.  All callers
	adjusted.
	(switch_to_thread_cleanup): Delete.
	(stop_all_threads): Use scoped_restore_current_thread.
	* inline-frame.c: Include "gdbthread.h".
	(inline_state) <inline_state>: Take a thread pointer instead of a
	ptid_t.  All callers adjusted.
	<ptid>: Delete, replaced by ...
	<thread>: ... this new field.
	(find_inline_frame_state): Take a thread pointer instead of a
	ptid_t.  All callers adjusted.
	(skip_inline_frames, step_into_inline_frame)
	(inline_skipped_frames, inline_skipped_symbol): Take a thread
	pointer instead of a ptid_t.  All callers adjusted.
	* inline-frame.h (skip_inline_frames, step_into_inline_frame)
	(inline_skipped_frames, inline_skipped_symbol): Likewise.
	* linux-fork.c (delete_checkpoint_command): Adjust to use thread
	pointers directly.
	* linux-nat.c (get_detach_signal): Likewise.
	* linux-thread-db.c (thread_from_lwp): New 'stopped' parameter.
	(thread_db_notice_clone): Adjust.
	(thread_db_find_new_threads_silently)
	(thread_db_find_new_threads_2, thread_db_find_new_threads_1): Take
	a thread pointer instead of a ptid_t.  All callers adjusted.
	* mi/mi-cmd-var.c: Include "inferior.h".
	(mi_cmd_var_update_iter): Update to use thread pointers.
	* mi/mi-interp.c (mi_new_thread): Update to use the thread's
	inferior directly.
	(mi_output_running_pid, mi_inferior_count): Delete, bits factored
	out to ...
	(mi_output_running): ... this new function.
	(mi_on_resume_1): Adjust to use it.
	(mi_user_selected_context_changed): Adjust to use inferior_thread.
	* mi/mi-main.c (proceed_thread): Adjust to use thread pointers
	directly.
	(interrupt_thread_callback): : Adjust to use thread and inferior
	pointers.
	* proc-service.c: Include "gdbthread.h".
	(ps_pglobal_lookup): Adjust to use the thread's inferior directly.
	* progspace-and-thread.c: Include "inferior.h".
	* progspace.c: Include "inferior.h".
	* python/py-exitedevent.c (create_exited_event_object): Adjust to
	hold a reference to an inferior_object.
	* python/py-finishbreakpoint.c (bpfinishpy_init): Adjust to use
	inferior_thread.
	* python/py-inferior.c (struct inferior_object): Give the type a
	tag name instead of a typedef.
	(python_on_normal_stop): No need to check if the current thread is
	listed.
	(inferior_to_inferior_object): Change return type to
	inferior_object.  All callers adjusted.
	(find_thread_object): Delete, bits factored out to ...
	(thread_to_thread_object): ... this new function.
	* python/py-infthread.c (create_thread_object): Use
	inferior_to_inferior_object.
	(thpy_is_stopped): Use thread pointer directly.
	(gdbpy_selected_thread): Use inferior_thread.
	* python/py-record-btrace.c (btpy_list_object) <ptid>: Delete
	field, replaced with ...
	<thread>: ... this new field.  All users adjusted.
	(btpy_insn_or_gap_new): Drop const.
	(btpy_list_new): Take a thread pointer instead of a ptid_t.  All
	callers adjusted.
	* python/py-record.c: Include "gdbthread.h".
	(recpy_insn_new, recpy_func_new): Take a thread pointer instead of
	a ptid_t.  All callers adjusted.
	(gdbpy_current_recording): Use inferior_thread.
	* python/py-record.h (recpy_record_object) <ptid>: Delete
	field, replaced with ...
	<thread>: ... this new field.  All users adjusted.
	(recpy_element_object) <ptid>: Delete
	field, replaced with ...
	<thread>: ... this new field.  All users adjusted.
	(recpy_insn_new, recpy_func_new): Take a thread pointer instead of
	a ptid_t.  All callers adjusted.
	* python/py-threadevent.c: Include "gdbthread.h".
	(get_event_thread): Use thread_to_thread_object.
	* python/python-internal.h (struct inferior_object): Forward
	declare.
	(find_thread_object, find_inferior_object): Delete declarations.
	(thread_to_thread_object, inferior_to_inferior_object): New
	declarations.
	* record-btrace.c: Include "inferior.h".
	(require_btrace_thread): Use inferior_thread.
	(record_btrace_frame_sniffer)
	(record_btrace_tailcall_frame_sniffer): Use inferior_thread.
	(get_thread_current_frame): Use scoped_restore_current_thread and
	switch_to_thread.
	(get_thread_current_frame): Use thread pointer directly.
	(record_btrace_replay_at_breakpoint): Use thread's inferior
	pointer directly.
	* record-full.c: Include "inferior.h".
	* regcache.c: Include "gdbthread.h".
	(get_thread_arch_regcache): Use the inferior's address space
	directly.
	(get_thread_regcache, registers_changed_thread): New.
	* regcache.h (get_thread_regcache(thread_info *thread)): New
	overload.
	(registers_changed_thread): New.
	(remote_target) <remote_detach_1>: Swap order of parameters.
	(remote_add_thread): <remote_add_thread>: Return the new thread.
	(get_remote_thread_info(ptid_t)): New overload.
	(remote_target::remote_notice_new_inferior): Use thread pointers
	directly.
	(remote_target::process_initial_stop_replies): Use
	thread_info::set_running.
	(remote_target::remote_detach_1, remote_target::detach)
	(extended_remote_target::detach): Adjust.
	* stack.c (frame_show_address): Use inferior_thread.
	* target-debug.h (target_debug_print_thread_info_pp): New.
	* target-delegates.c: Regenerate.
	* target.c (default_thread_address_space): Delete.
	(memory_xfer_partial_1): Use current_inferior.
	(target_detach): Use current_inferior.
	(target_thread_address_space): Delete.
	(generic_mourn_inferior): Use current_inferior.
	* target.h (struct target_ops) <thread_address_space>: Delete.
	(target_thread_address_space): Delete.
	* thread.c (init_thread_list): Use ALL_THREADS_SAFE.  Use thread
	pointers directly.
	(delete_thread_1, delete_thread, delete_thread_silent): Take a
	thread pointer instead of a ptid_t.  Adjust all callers.
	(ptid_to_global_thread_id, global_thread_id_to_ptid): Delete.
	(first_thread_of_process): Delete, replaced by ...
	(first_thread_of_inferior): ... this new function.  All callers
	adjusted.
	(any_thread_of_process): Rename to ...
	(any_thread_of_inferior): ... this, and take an inferior pointer.
	(any_live_thread_of_process): Rename to ...
	(any_live_thread_of_inferior): ... this, and take an inferior
	pointer.
	(thread_stack_temporaries_enabled_p, push_thread_stack_temporary)
	(value_in_thread_stack_temporaries)
	(get_last_thread_stack_temporary): Take a thread pointer instead
	of a ptid_t.  Adjust all callers.
	(thread_info::set_running): New.
	(validate_registers_access): Use inferior_thread.
	(can_access_registers_ptid): Rename to ...
	(can_access_registers_thread): ... this, and take a thread
	pointer.
	(print_thread_info_1): Adjust to compare thread pointers instead
	of ptids.
	(switch_to_no_thread, switch_to_thread): Make extern.
	(scoped_restore_current_thread::~scoped_restore_current_thread):
	Use m_thread pointer directly.
	(scoped_restore_current_thread::scoped_restore_current_thread):
	Use inferior_thread.
	(thread_command): Use thread pointer directly.
	(thread_num_make_value_helper): Use inferior_thread.
	* top.c (execute_command): Use inferior_thread.
	* tui/tui-interp.c: Include "inferior.h".
	* varobj.c (varobj_create): Use inferior_thread.
	(value_of_root_1): Use find_thread_global_id instead of
	global_thread_id_to_ptid.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid memcpys in regcache read_part/write_part for full registers.
@ 2018-06-21 15:51 sergiodj+buildbot
  2018-06-21 16:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21 15:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 33bab475a6984afedac8a036b3bb40b5555b4127 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 33bab475a6984afedac8a036b3bb40b5555b4127

Avoid memcpys in regcache read_part/write_part for full registers.

Additionally, tidy up the functions: Remove asserts, use gdb_byte,
update comments.

gdb/
	* regcache.c (readable_regcache::read_part): Avoid memcpy when
	possible.
	(regcache::write_part): Likewise.
	(readable_regcache::cooked_read_part): Update comment.
	(readable_regcache::cooked_write_part): Likewise.
	* regcache.h: (readable_regcache::read_part): Likewise.
	(regcache::write_part): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Regen doc/Makefile.in
@ 2018-06-21 13:57 sergiodj+buildbot
  2018-06-21 14:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21 13:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d388f64333fb977c1b975cb9d26c762b143f4cb9 ***

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

Regen doc/Makefile.in

Also make the automake strictness "foreign".  My regeneration of the
three doc/Makefile.in files already had --foreign in the automake
invocation, so this just makes it explicit.

bfd/
	* doc/Makefile.am (AUTOMAKE_OPTIONS): Add "foreign".
	* doc/Makefile.in: Regenerate.
binutils/
	* doc/Makefile.am (AUTOMAKE_OPTIONS): Add "foreign".
	* doc/Makefile.in: Regenerate.
gas/
	* doc/Makefile.am (AUTOMAKE_OPTIONS): Add "foreign".
	* doc/Makefile.in: Regenerate.
zlib/
	* Makefile.in: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Enable hardware watchpoints on attach for aarch64
@ 2018-06-21 13:34 sergiodj+buildbot
  2018-06-21 13:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21 13:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8363f9d5f2fab2c8b5a25c35c572f0426a716b66 ***

Author: Richard Bunt <richard.bunt@arm.com>
Branch: master
Commit: 8363f9d5f2fab2c8b5a25c35c572f0426a716b66

Enable hardware watchpoints on attach for aarch64

This commit fixes a bug whereby hardware watchpoints are not used on
aarch64 when attaching to a target. The fix adds an aarch64 specialization
of post_attach which records the number of available hardware debug registers
using aarch64_linux_get_debug_reg_capacity. This implementation mirrors that
of aarch64_linux_child_post_startup_inferior which successfully enables the
use of hardware watchpoints when launching the target under the debugger.

gdb/ChangeLog:

	* aarch64-linux-nat.c (post_attach): New.
	(aarch64_linux_nat_target::post_attach): Override post_attach to
	record the number of hardware debug registers.

gdb/testsuite/ChangeLog:

	* gdb.base/watchpoint-hw-attach.c: New test.
	* gdb.base/watchpoint-hw-attach.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use offsets instead of addresses in ELF_SECTION_IN_SEGMENT for non SHT_NOBITS
@ 2018-06-21  9:06 sergiodj+buildbot
  2018-06-21  9:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21  9:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 57c0d77c2ce5e583dab322e05f8291bcbad0ccd3 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 57c0d77c2ce5e583dab322e05f8291bcbad0ccd3

Use offsets instead of addresses in ELF_SECTION_IN_SEGMENT for non SHT_NOBITS

For sections that are not SHT_NOBITS, use sh_offset and p_offset instead of
sh_addr and p_vaddr when calculating if a section fits in a segment. Both
methods are valid when using the GNU linker.

include/
	* elf/internal.h (ELF_SECTION_IN_SEGMENT): Dont check addresses
	for non SHT_NOBITS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix a memory leak in py-param.c
@ 2018-06-21  3:34 sergiodj+buildbot
  2018-06-21  3:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-21  3:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0d0b0ea29af6abc0790d22f843a3d0cb09424a3a ***

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

Fix a memory leak in py-param.c

Mark Wielaard pointed out this memory leak to me:

    ==17633== 775 bytes in 1 blocks are definitely lost in loss record 13,346 of 13,967
    ==17633==    at 0x4C2DB6B: malloc (vg_replace_malloc.c:299)
    ==17633==    by 0x6652B7: xmalloc (common-utils.c:45)
    ==17633==    by 0xC4C889: xstrdup (xstrdup.c:34)
    ==17633==    by 0x5A71FD: unicode_to_encoded_string(_object*, char const*) (py-utils.c:81)
    ==17633==    by 0x5A73EB: python_string_to_host_string(_object*) (py-utils.c:158)
    ==17633==    by 0x59CC6C: get_doc_string(_object*, _object*) (py-param.c:334)
    ==17633==    by 0x59D2AA: parmpy_init(_object*, _object*, _object*) (py-param.c:728)

The bug here is that parmpy_init is written as though
add_setshow_generic takes ownership of its doc-string arguments.
However, it does not.  This patch fixes the bug in a straightforward
way and also applies some missing constification to make the problem
more apparent.

Tested on x86-64 Fedora 26.

gdb/ChangeLog
2018-06-20  Tom Tromey  <tom@tromey.com>

	* python/py-param.c (add_setshow_generic): Make parameters const.
	(parmpy_init): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Rename regcache_cooked_read_ftype and make a function_view
@ 2018-06-20 18:31 sergiodj+buildbot
  2018-06-20 18:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20 18:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 302abd6e9facdfec3473e19ff65a5479f850ad62 ***

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

Rename regcache_cooked_read_ftype and make a function_view

regcache_cooked_read_ftype can be converted to a function_view, which
allows us to use lambda functions and therefore avoid having to pass an
opaque pointer parameter.

Adjusting the fallouts showed that the "const regcache &" passed to the
readonly_detached_regcache constructor is cast to non-const in
do_cooked_read.  I changed the constructor parameter to be non-const.

Finally, I renamed the typedef from regcache_cooked_read_ftype to
register_read_ftype, since there is nothing that forces us to use it
only for regcaches nor cooked registers.

gdb/ChangeLog:

	* regcache.h (regcache_cooked_read_ftype): Rename to...
	(register_read_ftype): ...this, change type to function_view.
	(class reg_buffer) <save>: Remove src parameter.
	(readonly_detached_regcache) <readonly_detached_regcache>: Make
	parameter non-const in first overload.  Remove src parameter in
	second overload.
	* regcache.c (do_cooked_read): Remove.
	(readonly_detached_regcache::readonly_detached_regcache): Make
	parameter non-const, adjust call to other constructor.
	(reg_buffer::save): Remove src parameter.
	* frame.c (do_frame_register_read): Remove.
	(frame_save_as_regcache): Use lambda function.
	* ppc-linux-tdep.c (ppu2spu_unwind_register): Change type of src
	parameter to ppu2spu_data *.
	(ppu2spu_sniffer): Use lambda function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] testsuite: Fix cc-with-tweaks.sh being executed in the wrong shell
@ 2018-06-20 17:09 sergiodj+buildbot
  2018-06-20 17:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20 17:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f00674fe074f6ea778503a50132c3214a9c6aec8 ***

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

testsuite: Fix cc-with-tweaks.sh being executed in the wrong shell

The cc-with-tweaks.sh script needs to be executed with bash.  When
trying to run this:

  make check RUNTESTFLAGS="--target_board=dwarf4-gdb-index" TESTS="gdb.base/return.exp"

I get:

  gdb compile failed, /home/emaisin/src/binutils-gdb/gdb/contrib/cc-with-tweaks.sh: 174: /home/emaisin/src/binutils-gdb/gdb/contrib/cc-with-tweaks.sh: Bad substitution

The reason is that the board files execute cc-with-tweaks.sh using
/bin/sh, which points to dash on my machine.  Remove the /bin/sh part
and let the shebang choose the right interpreter.

gdb/testsuite/ChangeLog:

	* boards/cc-with-tweaks.exp: Don't call cc-with-tweaks.sh
	through /bin/sh.
	* boards/dwarf4-gdb-index.exp: Likewise.
	* boards/fission-dwp.exp: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove struct keyword in range-based for-loop
@ 2018-06-20 17:01 sergiodj+buildbot
  2018-06-20 17:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 19f3f25f370fbf7f5c2aa12a909d57f6e38ee2da ***

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

Remove struct keyword in range-based for-loop

Fix this with gcc 6.3.0, and make the loop variable const while at it:

/home/simark/src/binutils-gdb/gdb/record-full.c: In member function 'virtual int record_full_target::insert_breakpoint(gdbarch*, bp_target_info*)':
/home/simark/src/binutils-gdb/gdb/record-full.c:1789:8: error: types may not be defined in a for-range-declaration [-Werror]
   for (struct record_full_breakpoint &bp : record_full_breakpoints)

gdb/ChangeLog:

	* record-full.c (record_full_target::insert_breakpoint): Remove
	"struct" keyword, add const.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix potential illegal memroy access when using a build-id note with a negative size.
@ 2018-06-20 15:49 sergiodj+buildbot
  2018-06-20 16:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20 15:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6077de0645ce12a9c4e99f8839a846b42a535b0a ***

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

Fix potential illegal memroy access when using a build-id note with a negative size.

	PR 23316
	* opncls.c (get_build_id): Check for a negative or excessive data
	size in the build-id note.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Improve gdb.base/float128.exp failure message
@ 2018-06-20 14:46 sergiodj+buildbot
  2018-06-20 14:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20 14:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d554008b3747c6ccaa8e3a08cc797cfade242f3 ***

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

Improve gdb.base/float128.exp failure message

If the "print large128" sub-test fails in a manner that typically
indicates internal overflow due to GDB being built without MPFR
support, explicitly state this in the failure message.

gdb/testsuite/ChangeLog:
2018-06-20  Ulrich Weigand  <uweigand@de.ibm.com>

	* gdb.base/float128.exp: Add comment and improved fail message
	to the failure case of "print large128" test.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [BFD][AARCH64]Properly truncate no overflow checking relocation value for load/store immediate.
@ 2018-06-20 14:11 sergiodj+buildbot
  2018-06-20 14:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20 14:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b939d8a0dedbe0f0667500e1741e25baf03fe64c ***

Author: Renlin Li <renlin.li@arm.com>
Branch: master
Commit: b939d8a0dedbe0f0667500e1741e25baf03fe64c

[BFD][AARCH64]Properly truncate no overflow checking relocation value for load/store immediate.

bfd/ChangeLog:

2018-06-20  Renlin Li  <renlin.li@arm.com>

	* elfxx-aarch64.c (_bfd_aarch64_elf_resolve_relocation): Use PG_OFFSET
	to resolve BFD_RELOC_AARCH64_TLSLD_LDST16_DTPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLD_LDST32_DTPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLD_LDST64_DTPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLD_LDST8_DTPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLE_LDST16_TPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLE_LDST32_TPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLE_LDST64_TPREL_LO12_NC,
	BFD_RELOC_AARCH64_TLSLE_LDST8_TPREL_LO12_NC.

ld/ChangeLog:

2018-06-20 Renlin Li  <renlin.li@arm.com>

	* testsuite/ld-aarch64/emit-relocs-115.d: Update test with new value.
	* testsuite/ld-aarch64/emit-relocs-534.d: Likewise.
	* testsuite/ld-aarch64/emit-relocs-555.d: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Accept constant operands in la and lla
@ 2018-06-20  5:42 sergiodj+buildbot
  2018-06-20  6:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20  5:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 160d1b3d74593bf42155da24569f54a6e7140f65 ***

Author: Sebastian Huber <sebastian.huber@embedded-brains.de>
Branch: master
Commit: 160d1b3d74593bf42155da24569f54a6e7140f65

RISC-V: Accept constant operands in la and lla

opcodes/
	PR gas/23305
	* riscv-opc.c (riscv_opcodes): Use new format specifier 'B' for
	la and lla.

gas/
	PR gas/23305
	* config/tc-riscv.c (riscv_ip): Add format specifier 'B' for
	constants and symbols.
	* testsuite/gas/riscv/lla32.d: New file.
	* testsuite/gas/riscv/lla32.s: Likewise.
	* testsuite/gas/riscv/lla64-fail.d: Likewise.
	* testsuite/gas/riscv/lla64-fail.l: Likewise.
	* testsuite/gas/riscv/lla64-fail.s: Likewise.
	* testsuite/gas/riscv/lla64.d: Likewise.
	* testsuite/gas/riscv/lla64.s: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR ld/22966: Fix n64 MIPS `.got.plt' range checks
@ 2018-06-20  0:36 sergiodj+buildbot
  2018-06-20  0:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-20  0:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 789ff5b6c26ce7e4ebfcfa5a9a695407c17fa4ea ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 789ff5b6c26ce7e4ebfcfa5a9a695407c17fa4ea

PR ld/22966: Fix n64 MIPS `.got.plt' range checks

The addressable signed 32-bit range for n64 MIPS `.got.plt' references
is from 0xffffffff7fff8000 to 0x7fff7fff, due to how the composition of
an LUI and an LD instruction works for address calculation in the 64-bit
addressing mode, such as when CP0.Status.UX=1.

We currently have a range check in `mips_finish_exec_plt', however it is
not correct as it verifies that the `.got.plt' start address referred is
between 0xffffffff80000000 and 0x7fffffff.  It is also implemented as an
assertion rather than a proper error message despite that the situation
can be triggered by user input.  Additionally there is no check made for
individual `.got.plt' entries referred even though they can be out of
range while the `.got.plt' start address is not.

Fix all these problems and use the correct range for the check, limiting
it to n64 output files, and then issue a proper error message both in
`mips_finish_exec_plt' and in `_bfd_mips_elf_finish_dynamic_symbol',
suggesting the use of the `-Ttext-segment=...' option that will often
work and with the default linker scripts in particular.  Add suitable
tests covering boundary cases.

	bfd/
	PR ld/22966
	* elfxx-mips.c (_bfd_mips_elf_finish_dynamic_symbol): Verify the
	`.got.plt' entry referred is in range.
	(mips_finish_exec_plt): Correct the range check for `.got.plt'
	start.  Replace the assertion used for that with a proper error
	message.

	ld/
	PR ld/22966
	* testsuite/ld-mips-elf/n64-plt-1.dd: New test.
	* testsuite/ld-mips-elf/n64-plt-1.gd: New test.
	* testsuite/ld-mips-elf/n64-plt-2.ed: New test.
	* testsuite/ld-mips-elf/n64-plt-3.ed: New test.
	* testsuite/ld-mips-elf/n64-plt-4.dd: New test.
	* testsuite/ld-mips-elf/n64-plt-4.gd: New test.
	* testsuite/ld-mips-elf/n64-plt-1.ld: New test linker script.
	* testsuite/ld-mips-elf/n64-plt-2.ld: New test linker script.
	* testsuite/ld-mips-elf/n64-plt-3.ld: New test linker script.
	* testsuite/ld-mips-elf/n64-plt-4.ld: New test linker script.
	* testsuite/ld-mips-elf/n64-plt.s: New test source.
	* testsuite/ld-mips-elf/n64-plt-lib.s: New test source.
	* testsuite/ld-mips-elf/mips-elf.exp: Run the new tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] include: Sync with GCC
@ 2018-06-19 18:36 sergiodj+buildbot
  2018-06-19 18:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-19 18:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d856f9a8d64ef35b66000c42981f2f66f133d794 ***

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

include: Sync with GCC

Bring changes from GCC in shared headers.

include/ChangeLog:

	Sync with GCC

	2018-05-24  Tom Rix  <trix@juniper.net>

	* dwarf2.def (DW_FORM_strx*, DW_FORM_addrx*): New.

	2017-11-20  Kito Cheng  <kito.cheng@gmail.com>

	* longlong.h [__riscv] (__umulsidi3): Define.
	[__riscv] (umul_ppmm): Likewise.
	[__riscv] (__muluw3): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change inline frame breakpoint skipping logic (fix gdb.gdb/selftest.exp)
@ 2018-06-19 16:56 sergiodj+buildbot
  2018-06-19 17:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-19 16:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61b04dd04ac2c64d455bc6e17f08a106305b06b3 ***

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

Change inline frame breakpoint skipping logic (fix gdb.gdb/selftest.exp)

Currently, gdb.gdb/selftest.exp fails if you build GDB with
optimization (-O2, etc.).

The reason is that after setting a breakpoint in captured_main, we
stop at:
 ...
 Breakpoint 1, captured_main_1 (context=<optimized out>) at src/gdb/main.c:492
 ...
while selftest_setup expects a stop at captured_main.

Here, captured_main_1 has been inlined into captured_main, and
captured_main has been inlined into gdb_main:

 ...
 $ nm ./build/gdb/gdb | egrep ' [tT] .*captured_main|gdb_main' | c++filt
 000000000061b950 T gdb_main(captured_main_args*)
 ...

Indeed, the two inlined functions show up in the backtrace:

 ...
 (gdb) bt
 #0  captured_main_1 (context=<optimized out>) at main.c:492
 #1  captured_main (data=<optimized out>) at main.c:1147
 #2  gdb_main (args=args@entry=0x7fffffffdb80) at main.c:1173
 #3  0x000000000040fea5 in main (argc=<optimized out>, argv=<optimized out>)
     at gdb.c:32
 ...

We're now stopping at captured_main_1 because commit ddfe970e6bec
("Don't elide all inlined frames") makes GDB present a stop at the
innermost inlined frame if the program stopped by a user breakpoint.

Now, the selftest.exp testcase explicitly asks to stop at
"captured_main", not "captured_main_1", so I'm thinking that it's
GDB'S behavior that should be improved.  That is what this commit
does, by only showing a stop at an inline frame if the user breakpoint
was set in that frame's block.

Before this commit:

 (top-gdb) b captured_main
 Breakpoint 1 at 0x792f99: file src/gdb/main.c, line 492.
 (top-gdb) r
 Starting program: build/gdb/gdb

 Breakpoint 1, captured_main_1 (context=<optimized out>) at src/gdb/main.c:492
 492       lim_at_start = (char *) sbrk (0);
 (top-gdb)

After this commit, we now instead get:

 (top-gdb) b captured_main
 Breakpoint 1 at 0x791339: file src/gdb/main.c, line 492.
 (top-gdb) r
 Starting program: build/gdb/gdb

 Breakpoint 1, captured_main (data=<optimized out>) at src/gdb/main.c:1147
 1147      captured_main_1 (context);
 (top-gdb)

and:

 (top-gdb) b captured_main_1
 Breakpoint 2 at 0x791339: file src/gdb/main.c, line 492.
 (top-gdb) r
 Starting program: build/gdb/gdb
 Breakpoint 2, captured_main_1 (context=<optimized out>) at src/gdb/main.c:492
 492       lim_at_start = (char *) sbrk (0);
 (top-gdb)

Note that both captured_main and captured_main_1 resolved to the same
address, 0x791339.  That is necessary to trigger the issue in
question.  The gdb.base/inline-break.exp testcase currently does not
exercise that, but the new test added by this commit does.  That new
test fails without the GDB fix and passes with the fix.  No
regressions on x86-64 GNU/Linux.

While at it, the THIS_PC comparison in stopped_by_user_bp_inline_frame
is basically a nop, so just remove it -- if a software or hardware
breakpoint explains the stop, then it must be that it was installed at
the current PC.

gdb/ChangeLog:
2018-06-19  Pedro Alves  <palves@redhat.com>

	* inline-frame.c (stopped_by_user_bp_inline_frame): Replace PC
	parameter with a block parameter.  Compare location's block symbol
	with the frame's block instead of addresses.
	(skip_inline_frames): Pass the current block instead of the
	frame's address.  Break out as soon as we determine the frame
	should not be skipped.

gdb/testsuite/ChangeLog:
2018-06-19  Pedro Alves  <palves@redhat.com>

	* gdb.opt/inline-break.c (func_inline_callee, func_inline_caller)
	(func_extern_caller): New.
	(main): Call func_extern_caller.
	* gdb.opt/inline-break.exp: Add tests for inline frame skipping
	logic change.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] readelf: Handle more RISC-V relocations
@ 2018-06-19  9:25 sergiodj+buildbot
  2018-06-19  9:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-19  9:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39e07931b1be69b13acb8322687f825bd00afe91 ***

Author: Andreas Schwab <schwab@suse.de>
Branch: master
Commit: 39e07931b1be69b13acb8322687f825bd00afe91

readelf: Handle more RISC-V relocations

	* readelf.c (is_16bit_abs_reloc): Handle R_RISCV_SET16.
	(is_8bit_abs_reloc): New function.
	(is_6bit_abs_reloc): New function.
	(is_6bit_inplace_sub_reloc): New function.
	(apply_relocations): Use them.  Handle 6-bit relocations.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] This was already applied on the GCC side.
@ 2018-06-18 22:38 sergiodj+buildbot
  2018-06-18 23:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 22:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e054112458e12cb562cf84cabcb1970ca5ef1ff1 ***

Author: Eric Botcazou <ebotcazou@gcc.gnu.org>
Branch: master
Commit: e054112458e12cb562cf84cabcb1970ca5ef1ff1

This was already applied on the GCC side.

	* Makefile.def (fortran): Add check-target-libgomp-fortran.
	* Makefile.tpl (check-target-libgomp-fortran): New phony target.
	* Makefile.in: Regenerate.

	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove current_traceframe declaration
@ 2018-06-18 20:52 sergiodj+buildbot
  2018-06-18 22:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 20:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c4eb05ff9a3739378f8a846751da4d0e221b4c8c ***

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

Remove current_traceframe declaration

The variable has been removed in c12a508 ("Add client_state struct."),
remove the leftover declaration.

gdb/gdbserver/ChangeLog:

	* tracepoint.h (current_traceframe): Remove declaration.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use unique_xmalloc_ptr in solib-aix.c
@ 2018-06-18 20:35 sergiodj+buildbot
  2018-06-18 22:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 20:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f709fabb61246953e68ae46478a3b269c0615fce ***

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

Use unique_xmalloc_ptr in solib-aix.c

This removes a cleanup from solib-aix.c via unique_xmalloc_ptr.

gdb/ChangeLog
2018-06-18  Tom Tromey  <tom@tromey.com>

	* solib-aix.c (solib_aix_get_section_offsets): Return
	unique_xmalloc_ptr.
	(solib_aix_solib_create_inferior_hook): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use unique_xmalloc_ptr in darwin_current_sos
@ 2018-06-18 20:28 sergiodj+buildbot
  2018-06-18 21:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 20:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 668eb2f045ea535976cf484355831a8808b5ff35 ***

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

Use unique_xmalloc_ptr in darwin_current_sos

This changes darwin_current_sos to use unique_xmalloc_ptr rather than
a cleanup.

gdb/ChangeLog
2018-06-18  Tom Tromey  <tom@tromey.com>

	* solib-darwin.c (darwin_current_sos): Use unique_xmalloc_ptr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove resume_section_map_updates_cleanup
@ 2018-06-18 20:02 sergiodj+buildbot
  2018-06-18 20:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 20:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 06424eac62da949519c0c641fbc3e8372a9c7f0b ***

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

Remove resume_section_map_updates_cleanup

This removes resume_section_map_updates_cleanup, replacing it with a
scoped_restore.

Tested by the buildbot.

gdb/ChangeLog
2018-06-18  Tom Tromey  <tom@tromey.com>

	* objfiles.h (inhibit_section_map_updates): Update.
	(resume_section_map_updates, resume_section_map_updates_cleanup):
	Remove.
	* solib-svr4.c (svr4_handle_solib_event): Update.
	* objfiles.c (inhibit_section_map_updates): Return
	scoped_restore_tmpl<int>.
	(resume_section_map_updates, resume_section_map_updates_cleanup):
	Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use unique_xmalloc_ptr for read_string
@ 2018-06-18 19:25 sergiodj+buildbot
  2018-06-18 20:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b4be9fadea469e2c937c81a8f1d3243206f9bcfc ***

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

Use unique_xmalloc_ptr for read_string

This changes read_string's "buffer" out-parameter to be a
unique_xmalloc_ptr, then updates the users.  This allows for the
removal of some cleanups.

I chose unique_xmalloc_ptr rather than byte_vector here due to the way
Guile unwinding seems to work.

Tested by the buildbot.

gdb/ChangeLog
2018-06-18  Tom Tromey  <tom@tromey.com>

	* valprint.h (read_string): Update.
	* valprint.c (read_string): Change type of "buffer".
	(val_print_string): Update.
	* python/py-value.c (valpy_string): Update.
	* language.h (struct language_defn) <la_get_string>: Change
	type of "buffer".
	(default_get_string, c_get_string): Update.
	* language.c (default_get_string): Change type of "buffer".
	* guile/scm-value.c (gdbscm_value_to_string): Update.
	* c-lang.c (c_get_string): Change type of "buffer".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove la_error
@ 2018-06-18 19:14 sergiodj+buildbot
  2018-06-18 19:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 19:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69d340c68449f238fe665abf4a3a7989cd2d8376 ***

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

Remove la_error

While working on the parser code, I noticed that yyerror is exported
from each parser.  It is used by this code in parse.c:

   TRY
     {
       if (lang->la_parser (&ps))
         lang->la_error (NULL);
     }

However, it seems to me that la_error will never be called here,
because in every case, la_parser throws an exception on error -- each
implementation of yyerror just calls error.

So, this patch removes la_error and makes all the yyerror functions
static.  This is handy primarily because it makes it simpler to make
the expression parsers pure.

Tested by the buildbot.

gdb/ChangeLog
2018-06-18  Tom Tromey  <tom@tromey.com>

	* rust-lang.h (rust_yyerror): Don't declare.
	* rust-lang.c (rust_language_defn): Update.
	* rust-exp.y (yyerror): Now static.
	* parse.c (parse_exp_in_context_1): Update.
	* p-lang.h (p_yyerror): Don't declare.
	* p-lang.c (p_language_defn): Update.
	* p-exp.y (yyerror): Now static.
	* opencl-lang.c (opencl_language_defn): Update.
	* objc-lang.c (objc_language_defn): Update.
	* m2-lang.h (m2_yyerror): Don't declare.
	* m2-lang.c (m2_language_defn): Update.
	* m2-exp.y (yyerror): Now static.
	* language.h (struct language_defn) <la_error>: Remove.
	* language.c (unk_lang_error): Remove.
	(unknown_language_defn, auto_language_defn): Remove.
	* go-lang.h (go_yyerror): Don't declare.
	* go-lang.c (go_language_defn): Update.
	* go-exp.y (yyerror): Now static.
	* f-lang.h (f_yyerror): Don't declare.
	* f-lang.c (f_language_defn): Update.
	* f-exp.y (yyerror): Now static.
	* d-lang.h (d_yyerror): Don't declare.
	* d-lang.c (d_language_defn): Update.
	* d-exp.y (yyerror): Now static.
	* c-lang.h (c_yyerror): Don't declare.
	* c-lang.c (c_language_defn, cplus_language_defn)
	(asm_language_defn, minimal_language_defn): Update.
	* c-exp.y (yyerror): Now static.
	* ada-lang.h (ada_yyerror): Don't declare.
	* ada-lang.c (ada_language_defn): Update.
	* ada-exp.y (yyerror): Now static.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanups from ser-mingw.c
@ 2018-06-18 19:11 sergiodj+buildbot
  2018-06-18 19:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 19:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3f0dbd670b59aade6224aadcbc3a1943a4645a68 ***

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

Remove cleanups from ser-mingw.c

This removes the only cleanup from ser-mingw.c, replacing it with a
specialization of std::unique_ptr.

Tested by the buildbot.

gdb/ChangeLog
2018-06-18  Tom Tromey  <tom@tromey.com>

	* ser-mingw.c (struct pipe_state_destroyer): New.
	(pipe_state_up): New typedef.
	(cleanup_pipe_state): Remove.
	(pipe_windows_open): Use pipe_state_up.  Don't release argv.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] libiberty: Sync with GCC
@ 2018-06-18 15:08 sergiodj+buildbot
  2018-06-18 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 15:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 978588dc5854b02dc24e0eed18741415176753d8 ***

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

libiberty: Sync with GCC

Also sync include/simple-object.h, which goes together with the change
in libiberty.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] libdecnumber: Sync with GCC
@ 2018-06-18 14:36 sergiodj+buildbot
  2018-06-18 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 14:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f57a3bca61357a599be99552aaa6084bd8276682 ***

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

libdecnumber: Sync with GCC


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] config: Sync with GCC
@ 2018-06-18 14:08 sergiodj+buildbot
  2018-06-18 14:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 14:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 37f980dc03cc85795ea2e4de4ca69d3d7d1153c7 ***

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

config: Sync with GCC

... and re-generate all possible configure files, since they may depend
on things in config/.

config/ChangeLog:

	Sync with GCC
	2018-06-08  Martin Liska  <mliska@suse.cz>

	* bootstrap-mpx.mk: Remove.

	2018-05-10  Martin Liska  <mliska@suse.cz>

	PR bootstrap/64914
	* bootstrap-ubsan.mk: Define UBSAN_BOOTSTRAP.

	2018-05-09  Joshua Watt <jpewhacker@gmail.com>

        * ax_pthread.m4: Add file.

	2018-05-08  Richard Biener  <rguenther@suse.de>

	PR bootstrap/85571
	* bootstrap-lto-noplugin.mk: Disable compare.
	* bootstrap-lto.mk: Supply contrib/compare-lto for do-compare.

	2018-04-24  H.J. Lu  <hongjiu.lu@intel.com>

	PR bootstrap/85490
	* bootstrap-cet.mk (STAGE4_CFLAGS): New.

	2018-04-24  H.J. Lu  <hongjiu.lu@intel.com>

	PR target/85485
	* bootstrap-cet.mk (STAGE2_CFLAGS): Remove -mcet.
	(STAGE3_CFLAGS): Likewise.

	2018-04-24  H.J. Lu  <hongjiu.lu@intel.com>

	PR target/85485
	* cet.m4 (GCC_CET_FLAGS): Replace -mcet with -mshstk.

	2018-04-19  Jakub Jelinek  <jakub@redhat.com>

	* cet.m4 (GCC_CET_FLAGS): Default to --disable-cet, replace
	--enable-cet=default with --enable-cet=auto.

	2018-04-18  David Malcolm  <dmalcolm@redhat.com>

	PR jit/85384
	* acx.m4 (GCC_BASE_VER): Remove \$\$ from sed expression.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Ptrace support for AArch64 SVE gdbserver
@ 2018-06-18 10:38 sergiodj+buildbot
  2018-06-18 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 10:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02895270ec7243f46ea3e84dc385515533dc0139 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 02895270ec7243f46ea3e84dc385515533dc0139

Ptrace support for AArch64 SVE gdbserver

Add checks to detect SVE tdesc. Easiest way to do this is by checking the
size of the vector registers.

Use the common aarch64 ptrace copy functions for reading/writing registers.
A wrapper is required due to the common functions using reg_buffer_common.

gdbserver/
	* linux-aarch64-low.c (is_sve_tdesc): New function.
	(aarch64_sve_regs_copy_to_regcache): Likewise.
	(aarch64_sve_regs_copy_from_regcache):  Likewise.
	(aarch64_regs_info): Add SVE checks.
	(initialize_low_arch): Initialize SVE.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Ptrace support for Aarch64 SVE
@ 2018-06-18 10:30 sergiodj+buildbot
  2018-06-18 11:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 10:30 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9902bfc28b80190c76ffe5fad3bb73fd4a2ba28 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: e9902bfc28b80190c76ffe5fad3bb73fd4a2ba28

Ptrace support for Aarch64 SVE

Add support for reading and writing registers for Aarch64 SVE.

We need to support the cases where the kernel only gives us a
fpsimd structure. This occurs when there is no active SVE state
in the kernel (for example, after starting a new process).

Added checks to make sure the vector length has not changed whilst
the process is running.

gdb/
	* aarch64-linux-nat.c (fetch_sveregs_from_thread): New function.
	(store_sveregs_to_thread): Likewise.
	(aarch64_linux_fetch_inferior_registers): Check for SVE.
	(aarch64_linux_store_inferior_registers): Likewise.
	* nat/aarch64-sve-linux-ptrace.c (aarch64_sve_get_sveregs): New
	function.
	(aarch64_sve_regs_copy_to_regcache): Likewise.
	(aarch64_sve_regs_copy_from_regcache): Likewise.
	* nat/aarch64-sve-linux-ptrace.h (aarch64_sve_get_sveregs): New
	declaration.
	(aarch64_sve_regs_copy_to_regcache): Likewise.
	(aarch64_sve_regs_copy_from_regcache): Likewise.
	(sve_context): Structure from Linux headers.
	(SVE_SIG_ZREGS_SIZE): Define from Linux headers.
	(SVE_SIG_ZREG_SIZE): Likewise.
	(SVE_SIG_PREG_SIZE): Likewise.
	(SVE_SIG_FFR_SIZE): Likewise.
	(SVE_SIG_REGS_OFFSET): Likewise.
	(SVE_SIG_ZREGS_OFFSET): Likewise.
	(SVE_SIG_ZREG_OFFSET): Likewise.
	(SVE_SIG_ZREGS_SIZE): Likewise.
	(SVE_SIG_PREGS_OFFSET): Likewise.
	(SVE_SIG_PREG_OFFSET): Likewise.
	(SVE_SIG_PREGS_SIZE): Likewise.
	(SVE_SIG_FFR_OFFSET): Likewise.
	(SVE_SIG_REGS_SIZE): Likewise.
	(SVE_SIG_CONTEXT_SIZE): Likewise.
	(SVE_PT_REGS_MASK): Likewise.
	(SVE_PT_REGS_FPSIMD): Likewise.
	(SVE_PT_REGS_SVE): Likewise.
	(SVE_PT_VL_INHERIT): Likewise.
	(SVE_PT_VL_ONEXEC): Likewise.
	(SVE_PT_REGS_OFFSET): Likewise.
	(SVE_PT_FPSIMD_OFFSET): Likewise.
	(SVE_PT_FPSIMD_SIZE): Likewise.
	(SVE_PT_SVE_ZREG_SIZE): Likewise.
	(SVE_PT_SVE_PREG_SIZE): Likewise.
	(SVE_PT_SVE_FFR_SIZE): Likewise.
	(SVE_PT_SVE_FPSR_SIZE): Likewise.
	(SVE_PT_SVE_FPCR_SIZE): Likewise.
	(__SVE_SIG_TO_PT): Likewise.
	(SVE_PT_SVE_OFFSET): Likewise.
	(SVE_PT_SVE_ZREGS_OFFSET): Likewise.
	(SVE_PT_SVE_ZREG_OFFSET): Likewise.
	(SVE_PT_SVE_ZREGS_SIZE): Likewise.
	(SVE_PT_SVE_PREGS_OFFSET): Likewise.
	(SVE_PT_SVE_PREG_OFFSET): Likewise.
	(SVE_PT_SVE_PREGS_SIZE): Likewise.
	(SVE_PT_SVE_FFR_OFFSET): Likewise.
	(SVE_PT_SVE_FPSR_OFFSET): Likewise.
	(SVE_PT_SVE_FPCR_OFFSET): Likewise.
	(SVE_PT_SVE_SIZE): Likewise.
	(SVE_PT_SIZE): Likewise.
	(HAS_SVE_STATE): New define.

gdbserver/
	* Makefile.in: Add aarch64-sve-linux-ptrace.c.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add Aarch64 SVE compatibility macros
@ 2018-06-18 10:19 sergiodj+buildbot
  2018-06-18 10:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18 10:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 17a1cc89b5706f0ad8142ab85d62bce33249e905 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 17a1cc89b5706f0ad8142ab85d62bce33249e905

Add Aarch64 SVE compatibility macros

This header provides compatibility support for SVE allow building
even when the underlying host system lacks support for SVE.
If the binary is then run on an SVE-enabled kernel then support
will automatically be available.

gdb/
	* nat/aarch64-sve-linux-sigcontext.h: New file.
	* nat/aarch64-sve-linux-ptrace.h (SVE_VQ_BYTES): Move to
	new files.
	(SVE_VQ_MIN): Likewise.
	(SVE_VQ_MAX): Likewise.
	(SVE_VL_MIN): Likewise.
	(SVE_VL_MAX): Likewise.
	(SVE_NUM_ZREGS): Likewise.
	(SVE_NUM_PREGS): Likewise.
	(sve_vl_valid): Likewise.
	(struct user_sve_header): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite/ada] Fix number-of-bp test in bp_inlined_func.exp
@ 2018-06-18  7:22 sergiodj+buildbot
  2018-06-18  7:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-18  7:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fe3a558306ba4792c96e7258bd7209a206e2867 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 0fe3a558306ba4792c96e7258bd7209a206e2867

[gdb/testsuite/ada] Fix number-of-bp test in bp_inlined_func.exp

At the moment, bp_inlined_func.exp passes for a combined current gcc and
gdb-binutils repos build but fails for a build with system gcc (7.3.1) and
ld (2.29.1).

It checks for 4 breakpoints on read_small:
...
gdb_test "break read_small" \
         "Breakpoint $decimal at $hex: read_small\\. \\(4 locations\\)" \
         "set breakpoint at read_small"
...
and fails because it gets 5 breakpoint locations instead:
...
(gdb) break read_small
Breakpoint 2 at 0x401f9a: read_small. (5 locations)
(gdb) FAIL: gdb.ada/bp_inlined_func.exp: set breakpoint at read_small
...

The 4 expected breakpoint locations are inlined versions of read_small, and
the 5th breakpoint location has this address:
...
(gdb) info breakpoint
Num     Type           Disp Enb Address            What
1       breakpoint     keep y   <MULTIPLE>
1.1                         y     0x0000000000401f9a in b.read_small
                                                   at bp_inlined_func/b.adb:20
...
which is the read_small function itself:
...
(gdb) x 0x0000000000401f9a
0x401f9a <b__read_small+4>:     0x22f8058b
...

This patch updates the test to allow 5 breakpoint locations.

Tested on the configurations mentioned above, on x86_64.

2018-06-18  Tom de Vries  <tdevries@suse.de>

	* gdb.ada/bp_inlined_func.exp: Allow 5 breakpoint locations.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Don't drop SIGSTOP during stop_all_threads
@ 2018-06-16  0:27 sergiodj+buildbot
  2018-06-16  0:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-16  0:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7010835a6c5fd3679feae7e6345f2f10d4d761b4 ***

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

gdb: Don't drop SIGSTOP during stop_all_threads

This patch fixes an issue where GDB would sometimes hang when
attaching to a multi-threaded process.  This issue was especially
likely to trigger if the machine (running the inferior) was under
load.

In summary, the problem is an imbalance between two functions in
linux-nat.c, stop_callback and stop_wait_callback.  In stop_callback
we send SIGSTOP to a thread, but _only_ if the thread is not already
stopped, and if it is not signalled, which means it should stop soon.
In stop_wait_callback we wait for the SIGSTOP to arrive, however, we
are aware that the thread might have been signalled for some other
reason, and so if a signal other than SIGSTOP causes the thread to
stop then we stash that signal away so it can be reported back later.
If we get a SIGSTOP then this is discarded, after all, this signal was
sent from stop_callback.  Except that this might not be the case, it
could be that SIGSTOP was sent to a thread from elsewhere in GDB, in
which case we would not have sent another SIGSTOP from stop_callback
and the SIGSTOP received in stop_wait_callback should not be ignored.

Below I've laid out the exact sequence of events that I saw that lead
me to track down the above diagnosis.

After attaching to the inferior GDB sends a SIGSTOP to all of the
threads and then returns to the event loop waiting for interesting
things to happen.

Eventually the first target event is detected (this will be the first
SIGSTOP arriving) and GDB calls inferior_event_handler which calls
fetch_inferior_event.  Inside fetch_inferior_event GDB calls
do_target_wait which calls target_wait to find a thread with an event.

The target_wait call ends up in linux_nat_wait_1, which first checks
to see if any threads already have stashed stop events to report, and
if there are none then we enter a loop fetching as many events as
possible out of the kernel.  This event fetching is non-blocking, and
we give up once the kernel has no more events ready to give us.

All of the events from the kernel are passed through
linux_nat_filter_event which stashes the wait status for all of the
threads that reported a SIGSTOP, these will be returned by future
calls to linux_nat_wait_1.

Lets assume for a moment that we've attached to a multi-threaded
inferior, and that all but one thread has reported its stop during the
initial wait call in linux_nat_wait_1.  The other thread will be
reporting a SIGSTOP, but the kernel has not yet managed to deliver
that signal to GDB before GDB gave up waiting and continued handling
the events it already had.  GDB selects one of the threads that has
reported a SIGSTOP and passes this thread ID back to
fetch_inferior_event.

To handle the thread's SIGSTOP, GDB calls handle_signal_stop, which
calls stop_all_threads, this calls wait_one, which in turn calls
target_wait.

The first call to target_wait at this point will result in a stashed
wait status being returned, at which point we call setup_inferior.
The call to setup_inferior leads to a call into try_thread_db_load_1
which results in a call to linux_stop_and_wait_all_lwps.  This in turn
calls stop_callback on each thread followed by stop_wait_callback on
each thread.

We're now ready to make the mistake.  In stop_callback we see that our
problem thread is not stopped, but is signalled, so it should stop
soon.  As a result we don't send another SIGSTOP.

We then enter stop_wait_callback, eventually the problem thread stops
with SIGSTOP which we _incorrectly_ assume came from stop_callback,
and we discard.

Once stop_wait_callback has done its damage we return from
linux_stop_and_wait_all_lwps, finish in try_thread_db_load_1, and
eventually unwind back to the call to setup_inferior in
stop_all_threads.  GDB now loops around, and performs another
target_wait to get the next event from the inferior.

The target_wait calls causes us to once again reach linux_nat_wait_1,
and we pass through some code that calls resume_stopped_resumed_lwps.
This allows GDB to resume threads that are physically stopped, but
which GDB doesn't see any good reason for the thread to remain
stopped.  In our case, the problem thread which had its SIGSTOP
discarded is stopped, but doesn't have a stashed wait status to
report, and so GDB sets the thread going again.

We are now stuck waiting for an event on the problem thread that might
never arrive.

When considering how to write a test for this bug I struggled.  The
issue was only spotted _randomly_ when a machine was heavily loaded
with many multi-threaded applications, and GDB was being attached (by
script) to all of these applications in parallel.  In one reproducer I
required around 5 applications each of 5 threads per machine core in
order to reproduce the bug 2 out of 3 times.

What we really want to do though is simulate the kernel being slow to
report events through waitpid during the initial attach.  The solution
I came up with was to write an LD_PRELOAD library that intercepts
(some) waitpid calls and rate limits them to one per-second.  Any more
than that simply return 0 indicating there's no event available.
Obviously this can only be applied to waitpid calls that have the
WNOHANG flag set.

Unfortunately, once you ignore a waitpid call GDB can get a bit stuck.
Usually, once the kernel has made a child status available to waitpid
GDB will be sent a SIGCHLD signal.  However, if the kernel makes 5
child statuses available but, due to the preload library we only
collect one of them, then the kernel will not send any further SIGCHLD
signals, and so, when GDB, thinking that the remaining statuses have
not yet arrived sits waiting for a SIGCHLD it will be disappointed.

The solution, implemented within the preload library, is that, when we
hold back a waitpid result from GDB we spawn a new thread.  This
thread delays for a short period, and then sends GDB a SIGCHLD.  This
causes GDB to retry the waitpid, at which point sufficient time has
passed and our library allows the waitpid call to complete.

gdb/ChangeLog:

	* linux-nat.c (stop_wait_callback): Don't discard SIGSTOP if it
	was requested by GDB.

gdb/testsuite/ChangeLog:

	* gdb.threads/attach-slow-waitpid.c: New file.
	* gdb.threads/attach-slow-waitpid.exp: New file.
	* gdb.threads/slow-waitpid.c: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] update-gnulib.sh: Report required versions of autoconf/aclocal
@ 2018-06-14 23:27 sergiodj+buildbot
  2018-06-15  0:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 23:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8199b8f4d45b2240d09142f1df70849dda2cc638 ***

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

update-gnulib.sh: Report required versions of autoconf/aclocal

Update the messages printed when the wrong version of autoconf/aclocal
is found to include the expected version too, like we already do for
automake.

gdb/ChangeLog:

	* gnulib/update-gnulib.sh: Print expected versions of
	autoconf/aclocal.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS: Add Global INValidate ASE support
@ 2018-06-14 22:50 sergiodj+buildbot
  2018-06-14 23:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 22:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f20c942c3dbc08d02f74e4d508e19f8617bc5e3 ***

Author: Faraz Shahbazker <Faraz.Shahbazker@mips.com>
Branch: master
Commit: 6f20c942c3dbc08d02f74e4d508e19f8617bc5e3

MIPS: Add Global INValidate ASE support

Add support for the Global INValidate Application Specific Extension
for Release 6 of the MIPS Architecture.

[1] "MIPS Architecture for Programmers Volume II-A: The MIPS32
    Instruction Set Manual", Imagination Technologies Ltd., Document
    Number: MD00086, Revision 6.06, December 15, 2016, Section 3.2
    "Alphabetical List of Instructions", pp. 187-191

bfd/
	* elfxx-mips.c (print_mips_ases): Add GINV extension.

binutils/
	* readelf.c (print_mips_ases): Add GINV extension.

gas/
	* NEWS: Mention MIPS Global INValidate ASE support.
	* config/tc-mips.c (options): Add OPTION_GINV and OPTION_NO_GINV.
	(md_longopts): Likewise.
	(mips_ases): Define availability for GINV.
	(mips_convert_ase_flags): Map ASE_GINV to AFL_ASE_GINV.
	(md_show_usage): Add help for -mginv and -mno-ginv.
	* doc/as.texinfo: Document -mginv, -mno-ginv.
	* doc/c-mips.texi: Document -mginv, -mno-ginv, .set ginv and
	.set noginv.
	* testsuite/gas/mips/ase-errors-1.s: Add error checks for GINV
	ASE.
	* testsuite/gas/mips/ase-errors-2.s: Likewise.
	* testsuite/gas/mips/ase-errors-1.l: Likewise.
	* testsuite/gas/mips/ase-errors-2.l: Likewise.
	* testsuite/gas/mips/ginv.d: New test.
	* testsuite/gas/mips/ginv-err.d: New test.
	* testsuite/gas/mips/ginv-err.l: New test stderr output.
	* testsuite/gas/mips/ginv.s: New test source.
	* testsuite/gas/mips/ginv-err.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

include/
	* elf/mips.h (AFL_ASE_GINV, AFL_ASE_RESERVED1): New macros.
	(AFL_ASE_MASK): Update to include AFL_ASE_GINV.
	* opcode/mips.h: Document "+\" operand format.
	(ASE_GINV): New macro.

opcodes/
	* mips-dis.c (mips_arch_choices): Add GINV to mips32r6 and
	mips64r6 descriptors.
	(parse_mips_ase_option): Handle -Mginv option.
	(print_mips_disassembler_options): Document -Mginv.
	* mips-opc.c (decode_mips_operand) <+\>: New operand format.
	(GINV): New macro.
	(mips_opcodes): Define ginvi and ginvt.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix "beneath" conversion on AIX
@ 2018-06-14 22:07 sergiodj+buildbot
  2018-06-14 23:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 22:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b9a3c020eab9f6e73a439592b3ba8f8cdadcaa1e ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: b9a3c020eab9f6e73a439592b3ba8f8cdadcaa1e

Fix "beneath" conversion on AIX

GDB build on AIX is broken according to BuildBot:

  ../../binutils-gdb/gdb/aix-thread.c: In member function 'virtual void aix_thread_target::mourn_inferior()':
  ../../binutils-gdb/gdb/aix-thread.c:1735:34: error: 'beneath' cannot be used as a function
     target_ops *beneath = beneath ();
				    ^
This obvious commit fixes it.  There's apparently another issue
breaking the build there, but that's unrelated.

gdb/ChangeLog:
2018-06-14  Sergio Durigan Junior  <sergiodj@redhat.com>

	* aix-thread.c (aix_thread_target::xfer_partial): Use
	"beneath" as a method.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix/improve on-line help of 'define' command.
@ 2018-06-14 21:46 sergiodj+buildbot
  2018-06-14 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 21:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 87a8eca781910ec2079426f309145be18df8106c ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 87a8eca781910ec2079426f309145be18df8106c

Fix/improve on-line help of 'define' command.

There is an inconsistency between the doc and the online help.
=> the doc is correct, so fixing/improving the on-line help.

2018-06-14  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* cli/cli-script.c (_initialize_cli_script): Fix online documentation
	of 'define' command.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Avoid gdb.base/fork-running-state.exp lingering processes
@ 2018-06-14 17:28 sergiodj+buildbot
  2018-06-14 17:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 17:28 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 14897d65b5a279684289bf6b99136de60c31f1c0 ***

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

Avoid gdb.base/fork-running-state.exp lingering processes

Currently, the gdb.base/fork-running-state.exp testcase leaves a few
processes lingering until a 3 minutes alarm kills them:

 pedro    28308     1  0 13:55 ?        00:00:00 /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/fork-running-state/fork-running-state
 pedro    28340     1  0 13:55 ?        00:00:00 /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/fork-running-state/fork-running-state
 pedro    28372     1  0 13:55 ?        00:00:00 /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/fork-running-state/fork-running-state
 pedro    28400     1  0 13:55 ?        00:00:00 /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/fork-running-state/fork-running-state
 pedro    28431     1  0 13:55 ?        00:00:00 /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/fork-running-state/fork-running-state
 pedro    28463     1  0 13:55 ?        00:00:00 /home/pedro/gdb/binutils-gdb/build/gdb/testsuite/outputs/gdb.base/fork-running-state/fork-running-state

Those processes used to kill themselves, but that was changed by
commit f50d8a2eaea0 ("Fix gdb.base/fork-running-state.exp race").

This commit restores the self-killing, but only in the cases gdb won't
try killing the processes, thus avoiding the old race.

(The restored code in fork_parent isn't exactly the same as it was.
In this version, we're exiting immediately when 'wait' returns
success, while in the old version we'd loop again and end up in the
perror call.  The output from that perror call is not expected by the
"kill inferior" tests, and would result in a test FAIL.)

gdb/testsuite/ChangeLog:
2018-06-14  Pedro Alves  <palves@redhat.com>

	* gdb.base/fork-running-state.c: Include <errno.h>.
	(exit_if_relative_exits): New.
	(fork_child): If 'exit_if_relative_exits' is true, exit if the parent
	exits.
	(fork_parent): If 'exit_if_relative_exits' is true, exit if the
	child exits.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/cli] Honour 'print pretty' when printing result of finish command
@ 2018-06-14 13:54 sergiodj+buildbot
  2018-06-14 14:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 13:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5d9a06087942ddf4f9ab724b5b4c1a45507d8321 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: 5d9a06087942ddf4f9ab724b5b4c1a45507d8321

[gdb/cli] Honour 'print pretty' when printing result of finish command

Consider this testcase:
...
struct s {
  int a;
  int b;
};

struct s foo ()
{
  struct s r;
  r.a = 1;
  r.b = 2;
  return r;
}

int
main (void)
{
  struct s v;
  v = foo ();
  return v.a + v.b;
}
...

When we compile it with -g, load the exec with gdb, and run till the end of foo,
we can print r:
...
(gdb) p r
$1 = {a = 1, b = 2}
...

and by setting pretty printing to on, we can get the fields of r printed each
on its own line:
...
(gdb) set print pretty
(gdb) p r
$2 = {
  a = 1,
  b = 2
}
...

However, when we finish foo, the printed function result value is not using
the pretty printing setting:
...
(gdb) finish
Run till exit from #0  foo () at test.c:11
0x00000000004004c1 in main () at test.c:18
18        v = foo ();
Value returned is $3 = {a = 1, b = 2}
...

This patch fixes that by using get_user_print_options instead of
get_no_prettyformat_print_options in print_return_value_1, which gives us:
...
(gdb) finish
Run till exit from #0  foo () at test.c:11
0x00000000004004c1 in main () at test.c:18
18        v = foo ();
Value returned is $2 = {
  a = 1,
  b = 2
}
...

Build & reg-tested on x86_64.

2018-06-14  Tom de Vries  <tdevries@suse.de>

	PR cli/22573
	* infcmd.c (print_return_value_1): Use get_user_print_options instead of
	get_no_prettyformat_print_options.

	* gdb.base/finish-pretty.c: New test.
	* gdb.base/finish-pretty.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Revert accidental push of "Inline breakpoints" commit
@ 2018-06-14 12:44 sergiodj+buildbot
  2018-06-14 13:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 12:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b045207d1b8980add1c87b643504e3ef987e7a2 ***

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

Revert accidental push of "Inline breakpoints" commit


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb.gdb/selftest.exp, Use multi_line to build gdb's expected startup output
@ 2018-06-14 12:29 sergiodj+buildbot
  2018-06-14 12:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 12:29 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 11ae5818f76e0af4dcf7ee069e0756ccf6901ebe ***

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

gdb.gdb/selftest.exp, Use multi_line to build gdb's expected startup output

This regex had to be touched at least twice these past few days.  Use
multi_line to make it more readable.

Note this also tightens the regex a little bit in some spots.

gdb/testsuite/ChangeLog:
2018-06-14  Pedro Alves  <palves@redhat.com>

	* gdb.gdb/selftest.exp (test_with_self): Use multi_line to build
	gdb's expected startup output.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove stale inline function handling from selftest_setup
@ 2018-06-14 11:02 sergiodj+buildbot
  2018-06-14 11:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14 11:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d39de443a38448226ffc408290c17c54c598c39 ***

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

Remove stale inline function handling from selftest_setup

Before commit 70ee000084aa ("[gdb] Allow function arguments in bp
print match in selftest_setup"), this pattern in selftest_setup:

	-re "Starting program.*Breakpoint \[0-9\]+,.* at .*main.c:.*$function.*$gdb_prompt $" {
	    # $function may be inlined, so the program stops at the line
	    # calling $function.
	    pass "$description"
	}

happened to match if captured_main_1 was inlined and captured_main was
not, because captured_main calls captured_main_1 first thing, which
coincidentally matches "$function.*":

 Breakpoint 1, captured_main (data=<optimized out>) at src/gdb/main.c:1147
 1147      captured_main_1 (context);

That would probably be better "$function .*", with a space, but I
think that even better is to remove the "may be inlined" case too now,
because since ddfe970e6bec ("Don't elide all inlined frames") GDB
presents the stop at the inline function instead of at the caller.

gdb/testsuite/ChangeLog:
2018-06-14  Pedro Alves  <palves@redhat.com>

	* lib/selftest-support.exp (selftest_setup): Remove inlined
	function handling.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ELF dynsyms
@ 2018-06-14  3:54 sergiodj+buildbot
  2018-06-14  4:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14  3:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f923b7fd2a7c55f2337b3b79a2b2081a7bbe22b ***

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

ELF dynsyms

Many ELF targets arrange to emit a number of section symbols in
.dynsym for use by dynamic relocations.  This happens before the
dynamic relocations are output, and the need for those symbols
determined.  In most cases they are not needed.  A proper analysis of
the need for dynamic section symbols is target specific and tedious,
so this patch just excludes them in the obvious case when no
dynamic relocations are present.

The patch also runs the new pr23161 and pr23162 tests on more targets.

bfd/
	* elf-bfd.h (struct elf_link_hash_table): Add "dynamic_relocs".
	* elflink.c (_bfd_elf_init_2_index_sections): Comment fix.
	(_bfd_elf_add_dynamic_entry): Set "dynamic_relocs".
	(_bfd_elf_link_renumber_dynsyms): Exclude all section symbols when
	"dynamic_relocs" is not set.
	* elfxx-mips.c (count_section_dynsyms): Likewise.
ld/
	* testsuite/ld-elf/readelf.exp: Delete DUMP and selection of
	variant ver_def.vd.
	* testsuite/ld-elf/ver_def-tic6x.vd: Delete.
	* testsuite/ld-elf/shared.exp: Run most pr23161 and pr23162 tests for
	linux, nacl and gnu targets.
	* testsuite/ld-mips-elf/mips-elf.exp: Set base_syms to 1.
	* testsuite/ld-elf/pr23161a.rd: Don't check reloc type.  Allow any
	order of __bss_start, _edata and _end.
	* testsuite/ld-elf/pr23161b.rd: Don't check plt and dyn relocs.
	Allow and order of __bss_start, _edata and _end.
	* testsuite/ld-elf/pr23162.rd: Fail if __bss_start, _edata or _end
	relocs are present rather than testing for no relocations.
	* testsuite/ld-aarch64/gc-plt-relocs.d,
	* testsuite/ld-aarch64/ifunc-1-local.d,
	* testsuite/ld-aarch64/ifunc-1.d,
	* testsuite/ld-aarch64/ifunc-2-local.d,
	* testsuite/ld-aarch64/ifunc-2.d,
	* testsuite/ld-aarch64/ifunc-21.d,
	* testsuite/ld-aarch64/ifunc-3a.d,
	* testsuite/ld-arm/farcall-mixed-lib-v4t.d,
	* testsuite/ld-arm/farcall-mixed-lib.d,
	* testsuite/ld-arm/gc-hidden-1.d,
	* testsuite/ld-arm/tls-gdesc-got.d,
	* testsuite/ld-arm/tls-lib-loc.d,
	* testsuite/ld-arm/tls-longplt-lib.d,
	* testsuite/ld-arm/tls-thumb1.d,
	* testsuite/ld-cris/libdso-10.d,
	* testsuite/ld-cris/libdso-11.d,
	* testsuite/ld-cris/libdso-13b.d,
	* testsuite/ld-cris/libdso-14.d,
	* testsuite/ld-cris/libdso-15.d,
	* testsuite/ld-cris/pic-gc-72.d,
	* testsuite/ld-cris/pic-gc-73.d,
	* testsuite/ld-cris/tls-gc-71.d,
	* testsuite/ld-mips-elf/mips16-pic-4a.nd,
	* testsuite/ld-mips-elf/pic-and-nonpic-3a.dd,
	* testsuite/ld-mips-elf/pie-n32.d,
	* testsuite/ld-mips-elf/pie-n64.d,
	* testsuite/ld-mips-elf/pie-o32.d: Update for removed dynamic
	section symbols.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23282, Reinstate seek optimization
@ 2018-06-14  2:26 sergiodj+buildbot
  2018-06-14  2:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14  2:26 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff91d2f0e20fc91b6b101a0b20cbd38ab2d7fb50 ***

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

PR23282, Reinstate seek optimization

	PR 23282
	* bfdio.c (bfd_seek): Optimize away seeks to current position.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix GDB sparc build
@ 2018-06-14  2:16 sergiodj+buildbot
  2018-06-14  2:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-14  2:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ab89b5a57cff984d1edbcb6ca19c8f4a77c511a8 ***

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

Fix GDB sparc build

Cross-compiling for sparc64 bumped into a few issues, fixed by this
patch.

1. Include target.h in sparc-nat.h fixes:

/home/emaisin/src/binutils-gdb/gdb/sparc-nat.h:45:8: error: target_xfer_status does not name a type
 extern target_xfer_status sparc_xfer_wcookie (enum target_object object,

2. Remove extra semi-colon at sparc64-linux-nat.c:40 fixes:

/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c:41:3: error: expected unqualified-id before { token
   { sparc_store_inferior_registers (this, regcache, regnum); }

3. Remove "this" argument fixes:

/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c: In member function virtual void sparc64_linux_nat_target::fetch_registers(regcache*, int):
/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c:38:59: error: cannot convert sparc64_linux_nat_target* to regcache* for argument 1 to void sparc_fetch_inferior_registers(regcache*, int)
   { sparc_fetch_inferior_registers (this, regcache, regnum); }
                                                           ^
/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c: In member function virtual void sparc64_linux_nat_target::store_registers(regcache*, int):
/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c:41:59: error: cannot convert sparc64_linux_nat_target* to regcache* for argument 1 to void sparc_store_inferior_registers(regcache*, int)
   { sparc_store_inferior_registers (this, regcache, regnum); }
                                                           ^
4. Use sparc64_forget_process instead of sparc_forget_process fixes:

/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c: In member function virtual void sparc64_linux_nat_target::low_forget_process(pid_t):
/home/emaisin/src/binutils-gdb/gdb/sparc64-linux-nat.c:47:30: error: sparc_forget_process was not declared in this scope
   { sparc_forget_process (pid); }
                              ^

gdb/ChangeLog:

	* sparc-nat.h: Include target.h.
	* sparc64-linux-nat.c (class sparc64_linux_nat_target)
	<fetch_registers>: Remove this argument in function call.
	<store_registers>: Remove this argument in function call, remove
	extra semicolon.
	<low_forget_process>: Call sparc64_forget_process instead of
	sparc_forget_process.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS: Add CRC ASE support
@ 2018-06-13 15:04 sergiodj+buildbot
  2018-06-13 15:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-13 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 730c31740a69eaee73e0fc5430d80daa683c26e7 ***

Author: Scott Egerton <scott.egerton@imgtec.com>
Branch: master
Commit: 730c31740a69eaee73e0fc5430d80daa683c26e7

MIPS: Add CRC ASE support

Add support for the CRC Application Specific Extension for Release 6 of
the MIPS Architecture.

[1] "MIPS Architecture for Programmers Volume II-A: The MIPS32
    Instruction Set Manual", Imagination Technologies Ltd., Document
    Number: MD00086, Revision 6.06, December 15, 2016, Section 3.2
    "Alphabetical List of Instructions", pp. 143-148

[2] "MIPS Architecture for Programmers Volume II-A: The MIPS64
    Instruction Set Manual", Imagination Technologies Ltd., Document
    Number: MD00087, Revision 6.06, December 15, 2016, Section 3.2
    "Alphabetical List of Instructions", pp. 165-170

ChangeLog:

bfd/
2018-06-13  Scott Egerton  <scott.egerton@imgtec.com>
            Faraz Shahbazker  <Faraz.Shahbazker@mips.com>

	* elfxx-mips.c (print_mips_ases): Add CRC.

binutils/
2018-06-13  Scott Egerton  <scott.egerton@imgtec.com>
            Faraz Shahbazker  <Faraz.Shahbazker@mips.com>

	* readelf.c (print_mips_ases): Add CRC.

gas/
2018-06-13  Scott Egerton  <scott.egerton@imgtec.com>
            Faraz Shahbazker  <Faraz.Shahbazker@mips.com>
            Maciej W. Rozycki  <macro@mips.com>

	* config/tc-mips.c (options): Add OPTION_CRC and OPTION_NO_CRC.
	(md_longopts): Likewise.
	(md_show_usage): Add help for -mcrc and -mno-crc.
	(mips_ases): Define availability for CRC and CRC64.
	(mips_convert_ase_flags): Map ASE_CRC to AFL_ASE_CRC.
	* doc/as.texinfo: Document -mcrc, -mno-crc.
	* doc/c-mips.texi: Document -mcrc, -mno-crc, .set crc and
	.set no-crc.
	* testsuite/gas/mips/ase-errors-1.l: Add error checks for CRC
	ASE.
	* testsuite/gas/mips/ase-errors-2.l: Likewise.
	* testsuite/gas/mips/ase-errors-1.s: Likewise.
	* testsuite/gas/mips/ase-errors-2.s: Likewise.
	* testsuite/gas/mips/crc.d: New test.
	* testsuite/gas/mips/crc64.d: New test.
	* testsuite/gas/mips/crc-err.d: New test.
	* testsuite/gas/mips/crc64-err.d: New test.
	* testsuite/gas/mips/crc-err.l: New test stderr output.
	* testsuite/gas/mips/crc64-err.l: New test stderr output.
	* testsuite/gas/mips/crc.s: New test source.
	* testsuite/gas/mips/crc64.s: New test source.
	* testsuite/gas/mips/crc-err.s: New test source.
	* testsuite/gas/mips/crc64-err.s: New test source.
	* testsuite/gas/mips/mips.exp: Run the new tests.

include/
2018-06-13  Scott Egerton  <scott.egerton@imgtec.com>
            Faraz Shahbazker  <Faraz.Shahbazker@mips.com>

	* elf/mips.h (AFL_ASE_CRC): New macro.
	(AFL_ASE_MASK): Update to include AFL_ASE_CRC.
	* opcode/mips.h (ASE_CRC): New macro.
	* opcode/mips.h (ASE_CRC64): Likewise.

opcodes/
2018-06-13  Scott Egerton  <scott.egerton@imgtec.com>
            Faraz Shahbazker  <Faraz.Shahbazker@mips.com>

	* mips-dis.c (mips_arch_choices): Add CRC and CRC64 ASEs.
	* mips-opc.c (CRC, CRC64): New macros.
	(mips_builtin_opcodes): Define crc32b, crc32h, crc32w,
	crc32cb, crc32ch and crc32cw for CRC.  Define crc32d and
	crc32cd for CRC64.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Fix hang in fork-running-state.c
@ 2018-06-13 13:04 sergiodj+buildbot
  2018-06-13 13:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-13 13:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a08ac84b963facb4c4a85c4d5df057d44e2a276d ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: a08ac84b963facb4c4a85c4d5df057d44e2a276d

[gdb/testsuite] Fix hang in fork-running-state.c

When I run make check:
...
$ cd build/gdb
$ make check 2>&1 | tee ../CHECKLOG.gdb
...
I see after ~30m the summary of the test run printed, but make still hangs.

This seems to be due to some sleeping processes:
...
$ ps  fx | grep fork-run
 6475 ?        S      0:00 gdb.base/fork-running-state/fork-running-state
 6451 ?        S      0:00 gdb.base/fork-running-state/fork-running-state
 6427 ?        S      0:00 gdb.base/fork-running-state/fork-running-state
...

Killing the sleeping processes like this:
...
kill -9 $(ps -A  | grep fork-running-st | awk '{print $1}')
...
allows make to finish.

If I isolate one debug session from fork-running-state.exp that causes one of
these sleeping processes, we get:
...
(gdb) set non-stop on
(gdb) break main
Breakpoint 1 at 0x400665: file src/gdb/testsuite/gdb.base/fork-running-state.c,
line 52.
(gdb) run
Starting program: build/gdb/testsuite/outputs/gdb.base/fork-running-state/
fork-running-state

Breakpoint 1, main () at src/gdb/testsuite/gdb.base/fork-running-state.c:52
52        save_parent = getpid ();
(gdb) set detach-on-fork on
(gdb) set follow-fork parent
(gdb) continue &
Continuing.
[Detaching after fork from child process 18797]
(gdb) info threads
  Id   Target Id         Frame
* 1    process 18793 "fork-running-st" (running)
(gdb) set print inferior-events off
(gdb) kill inferior 1
...
So, AFAIU, the hanging process is the child process that gdb detaches from.

There's an alarm set in main before the fork, but alarms are not preserved in
the fork child:
...
$ man alarm
   ...
NOTES
       Alarms created by alarm() are preserved across execve(2) and are not
       inherited by children created via fork(2).
...
So, AFAIU, once the parent is killed, there's no alarm to terminate the child.

The patch fixes this by moving the setting of the alarm into the
fork_main/fork_child functions, making sure that an alarm will trigger for
the child.

Tested with make check on x86_64.

2018-06-13  Tom de Vries  <tdevries@suse.de>

	PR testsuite/23269
	* gdb.base/fork-running-state.c (main): Move setting of alarm ...
	(fork_child): ... here, and ...
	(fork_parent): ... here.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [gdb/testsuite] Update gdb startup text in selftest.exp
@ 2018-06-13 12:58 sergiodj+buildbot
  2018-06-13 13:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-13 12:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c75d3d4144fa8b5312bf581451bf800251b7bd71 ***

Author: Tom de Vries <tdevries@suse.de>
Branch: master
Commit: c75d3d4144fa8b5312bf581451bf800251b7bd71

[gdb/testsuite] Update gdb startup text in selftest.exp

Atm selftest.exp fails for me.

One of the reasons is that in c61b06a19a34baab66e3809c7b41b0c31009ed9f (Remove
some text from --version output) an eol was added after "There is NO
WARRANTY, to the extent permitted by law".

This patch updates the matching of the gdb startup message in selftest.exp
accordingly.

Tested selftest.exp (with two other selftest.exp related fixes applied).

2018-06-12  Tom de Vries  <tdevries@suse.de>

	* gdb.gdb/selftest.exp (test_with_self): Update gdb startup text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix procfs.c compilation
@ 2018-06-13  9:37 sergiodj+buildbot
  2018-06-13  9:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-13  9:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62c808aef64d77d5585f54c792ebe3f388a960a9 ***

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Branch: master
Commit: 62c808aef64d77d5585f54c792ebe3f388a960a9

Fix procfs.c compilation

procfs.c currently doesn't compile on Solaris:

/vol/src/gnu/gdb/gdb/local/gdb/procfs.c: In function `void _initialize_procfs()':
/vol/src/gnu/gdb/gdb/local/gdb/procfs.c:3734:15: error: invalid initialization of reference of type `const target_info&' from expression of type `procfs_target*'
   add_target (&the_procfs_target);
               ^~~~~~~~~~~~~~~~~~
In file included from /vol/src/gnu/gdb/gdb/local/gdb/inferior.h:40,
                 from /vol/src/gnu/gdb/gdb/local/gdb/procfs.c:24:
/vol/src/gnu/gdb/gdb/local/gdb/target.h:2305:13: note: in passing argument 1 of `void add_target(const target_info&, void (*)(const char*, int), void (*)(cmd_list_element*, completion_tracker&, const char*, const char*))'
 extern void add_target (const target_info &info,
             ^~~~~~~~~~
/vol/src/gnu/gdb/gdb/local/gdb/procfs.c: In member function `virtual char* procfs_target::make_corefile_notes(bfd*, int*)':
/vol/src/gnu/gdb/gdb/local/gdb/procfs.c:3898:16: error: too many arguments to function `gdb::optional<std::vector<unsigned char, gdb::default_init_allocator<unsigned char, std::allocator<unsigned char> > > > target_read_alloc(target_ops*, target_object, const char*)'
     NULL, &auxv);
                ^
In file included from /vol/src/gnu/gdb/gdb/local/gdb/inferior.h:40,
                 from /vol/src/gnu/gdb/gdb/local/gdb/procfs.c:24:
/vol/src/gnu/gdb/gdb/local/gdb/target.h:341:40: note: declared here
 extern gdb::optional<gdb::byte_vector> target_read_alloc
                                        ^~~~~~~~~~~~~~~~~
/vol/src/gnu/gdb/gdb/local/gdb/procfs.c:3898:16: error: cannot convert `gdb::optional<std::vector<unsigned char, gdb::default_init_allocator<unsigned char, std::allocator<unsigned char> > > >' to `int' in assignment
     NULL, &auxv);
                ^

Fixed as follows.  Built and ran make check on 64-bit Solaris 11.5/x86
(amd64-pc-solaris2.11) only.

	* procfs.c (_initialize_procfs): Use add_inf_child_target.
	(procfs_target::make_corefile_notes): Adjust to new
	target_read_alloc return type.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Run INF_EXEC_COMPLETE handler for additional cases
@ 2018-06-12 22:38 sergiodj+buildbot
  2018-06-12 22:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-12 22:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1840d81a201932a2d5ad5b089aad85943a5a0a82 ***

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

gdb: Run INF_EXEC_COMPLETE handler for additional cases

When making an inferior call, and non-stop mode is off, then, once the
inferior call is complete all threads will be stopped, and we should
run the INF_EXEC_COMPLETE handler.  This will result in a call to
'target_async(0)' to remove the event handlers for the target.

This was discussed by Yao Qi in this mailing list thread:

    https://sourceware.org/ml/gdb/2017-10/msg00032.html

Without this then the target event handlers are left in place even
when the target is stopped, which is different to what happens during
a standard stop proceedure (for example when one thread hits a
breakpoint).

gdb/ChangeLog:

	PR gdb/22882
	* infrun.c (fetch_inferior_event): If GDB is not proceeding then
	run INF_EXEC_COMPLETE handler, even when not calling normal_stop.
	Move should_notify_stop local into more inner scope.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Fix an infrun debug log message
@ 2018-06-12 21:42 sergiodj+buildbot
  2018-06-12 21:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-12 21:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT defd21729f1ceb51999afcb342310835f8ab2faf ***

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

gdb: Fix an infrun debug log message

Run the test gdb.threads/multiple-successive-infcall.exp by hand, if
you turn on 'debug infrun 1', you'll see that the debug line fixed in
this commit is printed and contains the wrong $pc value.  Fixed in
this commit.

gdb/ChangeLog:

	* infrun.c (do_target_wait): Change old version of $pc printed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix gdb build on hppa-linux
@ 2018-06-12  2:23 sergiodj+buildbot
  2018-06-12  2:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-12  2:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 69c67a0b2a93ba8c431d1ebb90d57a1e4d0ec3a1 ***

Author: John David Anglin <danglin@gcc.gnu.org>
Branch: master
Commit: 69c67a0b2a93ba8c431d1ebb90d57a1e4d0ec3a1

Fix gdb build on hppa-linux

Fixes:

  CXX    hppa-linux-nat.o
../../src/gdb/hppa-linux-nat.c:277:17: error: no 'void hppa_linux_nat_target::fetch_inferior_registers(regcache*, int)' member function declared in class 'hppa_linux_nat_target'
        int regno)
                 ^
../../src/gdb/hppa-linux-nat.c:224:1: error: 'void fetch_register(regcache*, int)' defined but not used [-Werror=unused-function]
 fetch_register (struct regcache *regcache, int regno)
 ^~~~~~~~~~~~~~

gdb/ChangeLog:

	* gdb/hppa-linux-nat.c
	(hppa_linux_nat_target::fetch_inferior_registers): Rename to
	hppa_linux_nat_target::fetch_registers.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Enable Aarch64 SVE for gdbserver
@ 2018-06-11 13:00 sergiodj+buildbot
  2018-06-11 12:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-11 13:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fefa175e8f518f17121a1870270a415c851cbacc ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: fefa175e8f518f17121a1870270a415c851cbacc

Enable Aarch64 SVE for gdbserver

gdbserver/
	* linux-aarch64-ipa.c (get_ipa_tdesc): Add null VQ param.
	(initialize_low_tracepoint): Likewise
	* linux-aarch64-low.c (aarch64_arch_setup): Get VQ.
	* linux-aarch64-tdesc-selftest.c (aarch64_tdesc_test): Add null VQ
	param.
	* linux-aarch64-tdesc.c (aarch64_linux_read_description): Add VQ
	checks.
	* linux-aarch64-tdesc.h (aarch64_linux_read_description): Add VQ.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Increase gdbsever PBUFSIZ
@ 2018-06-11 11:25 sergiodj+buildbot
  2018-06-11 11:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-11 11:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b91ad3ff949be78a43653b6138cbd515d4bdb637 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: b91ad3ff949be78a43653b6138cbd515d4bdb637

Increase gdbsever PBUFSIZ

PBUFSIZ is no longer big enough for SVE. Increase accordingly.

gdbserver/
            * server.h (PBUFSIZ): Increase size


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add Aarch64 SVE dwarf regnums
@ 2018-06-11 10:47 sergiodj+buildbot
  2018-06-11 10:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-11 10:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 65d4cadafd7d9d5bb84810cde98a8c3a007a0594 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 65d4cadafd7d9d5bb84810cde98a8c3a007a0594

Add Aarch64 SVE dwarf regnums

This is as per the spec:
https://developer.arm.com/products/architecture/a-profile/docs/100985/0000

gdb/
	* aarch64-tdep.c (aarch64_dwarf_reg_to_regnum): Add mappings.
	* aarch64-tdep.h (AARCH64_DWARF_SVE_VG): Add define.
	(AARCH64_DWARF_SVE_FFR): Likewise.
	(AARCH64_DWARF_SVE_P0): Likewise.
	(AARCH64_DWARF_SVE_Z0): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanups from record-full.c
@ 2018-06-11  5:54 sergiodj+buildbot
  2018-06-11  5:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-11  5:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1ddbba9df5fda9b1af5306fe182a5f1c3197f53a ***

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

Remove cleanups from record-full.c

This removes cleanups from record-full.c.  In this case, the cleanups
were only ever run when an exception was thrown.  So, I replaced these
with try/catch, rather than introduce a new specialized RAII type.

Tested by the buildbot.

gdb/ChangeLog
2018-06-10  Tom Tromey  <tom@tromey.com>

	* record-full.c (record_full_arch_list_cleanups): Remove.
	(record_full_message): Use try/catch.
	(record_full_wait_cleanups): Remove.
	(record_full_wait_1): Use try/catch.
	(record_full_restore): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove more "struct" keywords in range-based for loops
@ 2018-06-11  3:01 sergiodj+buildbot
  2018-06-11  2:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-11  3:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 71b73764977a3895b0dda3e7260eece7a8d3e60c ***

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

Remove more "struct" keywords in range-based for loops

GCC 6.3.0 produces this kind of errors:

  CXX    dwarf2read.o
/home/simark/src/binutils-gdb/gdb/dwarf2read.c: In function 'void process_cu_includes(dwarf2_per_objfile*)':
/home/simark/src/binutils-gdb/gdb/dwarf2read.c:10220:8: error: types may not be defined in a for-range-declaration [-Werror]
   for (struct dwarf2_per_cu_data *iter : dwarf2_per_objfile->just_read_cus)
        ^~~~~~

Removing the struct keyword makes it happy.

gdb/ChangeLog:

	* dwarf2read.c (process_cu_includes): Remove struct keyword.
	* serial.c (serial_interface_lookup): Remove struct keyword.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanups from tracefile.c
@ 2018-06-10 14:17 sergiodj+buildbot
  2018-06-10 16:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-10 14:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d14b92bf8a7f4c57eb6c5fca559c7bbb8a747358 ***

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

Remove cleanups from tracefile.c

This removes cleanups from tracefile.c, by introducing a unique_ptr
specialization.

This code could be made even simpler via a deeper C++-ification, but I
have not attempted that.

Tested by the buildbot.

gdb/ChangeLog
2018-06-10  Tom Tromey  <tom@tromey.com>

	* tracefile.c (struct trace_file_writer_deleter): New.
	<operator()>: Rename from trace_file_writer_xfree.
	(trace_file_writer_up): New typedef.
	(tsave_command, trace_save_tfile, trace_save_ctf): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use std::unique_ptr in reg_buffer
@ 2018-06-10  4:07 sergiodj+buildbot
  2018-06-10  4:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-10  4:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 835dcf92618e294d3c6c2bedd94af712809c96a3 ***

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

Use std::unique_ptr in reg_buffer

Using std::unique_ptr allows to remove the manual xfree in the
destructor.

If I understand correctly, using the () after the new operator will make
sure the allocated objects will be value initialized, which for scalars
means they are zero-initialized.  So it should have the same behavior as
XCNEWVEC.

gdb/ChangeLog:

	* regcache.h (reg_buffer) <~reg_buffer>: Use default destructor.
	<m_registers, m_register_status>: Change type to
	std::unique_ptr.
	* regcache.c (reg_buffer::reg_buffer): Use new instead of
	XCNEWVEC.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove use of queue.h from gdbserver/event-loop.c
@ 2018-06-10  0:49 sergiodj+buildbot
  2018-06-10  0:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-10  0:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 405918449085378e96dc841a3d536ce161ce1539 ***

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

Remove use of queue.h from gdbserver/event-loop.c

This removes a use of queue.h from gdbserver/event-loop.c, replacing
it with std::queue.

I was not completely sure whether std::queue is even that useful.
Perhaps plain std::list could be used just as easily.

Tested by the buildbot.

gdb/gdbserver/ChangeLog
2018-06-09  Tom Tromey  <tom@tromey.com>

	* event-loop.c (gdb_event, gdb_event_p): Remove typedefs.  Don't
	declare queue.
	(event_queue): Use std::queue.
	(gdb_event_xfree): Remove.
	(initialize_event_loop, process_event, wait_for_event): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a VEC from serial.c
@ 2018-06-10  0:10 sergiodj+buildbot
  2018-06-10  0:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-10  0:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 191cca638351fcaf9bee93a396bd4f8b74f915eb ***

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

Remove a VEC from serial.c

This replaces a VEC in serial.c with a std::vector.

Tested by the buildbot.

gdb/ChangeLog
2018-06-09  Tom Tromey  <tom@tromey.com>

	* serial.c (serial_ops_p): Remove typedef.  Don't declare VEC.
	(serial_ops_list): Now static, std::vector.
	(serial_interface_lookup, serial_add_interface): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add missing client_state struct references to win target.
@ 2018-06-08 21:24 sergiodj+buildbot
  2018-06-08 22:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 21:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6341380d5cb8e645d79953a24701219a048f426f ***

Author: Stan Cox <scox@redhat.com>
Branch: master
Commit: 6341380d5cb8e645d79953a24701219a048f426f

Add missing client_state struct references to win target.

gdbserver/ChangeLog
	* win32-low.c (win32_create_inferior):  last_ptid and last_status
	moved to client_state.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make gdbreplay use more common routines
@ 2018-06-08 20:50 sergiodj+buildbot
  2018-06-08 21:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 20:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 03349c934525d0f78a3f971a351b1202ea21ec94 ***

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

Make gdbreplay use more common routines

This makes gdbreplay share a bit more code with gdbserver, and paves
the way to share more in future.  Including common-defs.h pulls in
defines and headers that gdb and gdbserver assume are always
defined/available too, such as for example _(), ansidecl.h or a set of
system headers.  Including that revealed (static vs extern conflict)
gdbreplay had a local copy of perror_with_name (which exited directly
instead of throwing an error).  So I removed gdbreplay's local copy,
and then added enough .o files until gdbreplay linked successfully.

Also, use xstrdup instead of strdup.

gdb/gdbserver/ChangeLog:
2018-06-08  Pedro Alves  <palves@redhat.com>

	* Makefile.in (GDBREPLAY_OBS): Add common/cleanups.o,
	common/common-exceptions.o, common/common-utils.o,
	common/errors.o, common/print-utils.o and utils.o.
	* gdbreplay.c: Include "common-defs.h" instead of the two
	'config.h's here.  Don't include stdio.h, errno.h, stdlib.h,
	string.h or alloca.h.
	(perror_with_name): Delete.
	(remote_open): Use xstrdup instead of strdup.
	(main): Rename to ...
	(captured_main): ... this.
	(main): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ld/x86: Remove hidden _edata, __bss_start, and _end
@ 2018-06-08 20:50 sergiodj+buildbot
  2018-06-08 20:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 20:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ecf99cc09236316db27fd8ffaedca864f81ea081 ***

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

ld/x86: Remove hidden _edata, __bss_start, and _end

There is no need to put hidden _edata, __bss_start, and _end in dynamic
symbol table in shared libraries.

bfd/

	PR ld/23161
	* elfxx-x86.c (elf_x86_hide_linker_defined): New function.
	(_bfd_x86_elf_link_check_relocs): Use it to hide hidden
	__bss_start, _end and _edata in shared libraries.

ld/

	PR ld/23161
	* testsuite/ld-elf/pr23161d.rd: Remove local _edata, __bss_start,
	and _end from dynamic symbol table.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix build issue with Python 3.7
@ 2018-06-08 18:19 sergiodj+buildbot
  2018-06-08 19:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 18:19 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT aeab512851bf6ed623d1c6c4305b6ce05e51a10c ***

Author: Paul Koning <paul_koning@dell.com>
Branch: master
Commit: aeab512851bf6ed623d1c6c4305b6ce05e51a10c

Fix build issue with Python 3.7

Originally reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1577396 -- gdb build fails
with Python 3.7 due to references to a Python internal function whose
declaration changed in 3.7.

gdb/ChangeLog
2018-06-08  Paul Koning  <paul_koning@dell.com>

	    PR gdb/23252

	    * python/python.c (do_start_initialization):
	    Avoid call to internal Python API.
	    (init__gdb_module): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] linux: Add maintenance commands to test libthread_db
@ 2018-06-08 17:39 sergiodj+buildbot
  2018-06-08 17:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 17:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5045b3d78903d1f6faa4cb511fa801e50dfacf48 ***

Author: Gary Benson <gbenson@redhat.com>
Branch: master
Commit: 5045b3d78903d1f6faa4cb511fa801e50dfacf48

linux: Add maintenance commands to test libthread_db

This commit adds two new commands which may be used to test thread
debugging libraries used by GDB:

  * "maint check libthread-db" tests the thread debugging library GDB
     is using for the current inferior.

  * "maint set/show check-libthread-db" selects whether libthread_db
     tests should be run automatically as libthread_db is auto-loaded.
     The default is to not run tests automatically.

The test itself is a basic integrity check exercising all libthread_db
functions used by GDB on GNU/Linux systems.  By extension this also
exercises the proc_service functions provided by GDB that libthread_db
uses.

This functionality is useful for NPTL developers and libthread_db
developers.  It could also prove useful investigating bugs reported
against GDB where the thread debugging library or GDB's proc_service
layer is suspect.

gdb/ChangeLog:

	* linux-thread-db.c (valprint.h): New include.
	(struct check_thread_db_info): New structure.
	(check_thread_db_on_load, tdb_testinfo): New static globals.
	(check_thread_db, check_thread_db_callback): New functions.
	(try_thread_db_load_1): Run integrity checks if requested.
	(maintenance_check_libthread_db): New function.
	(_initialize_thread_db): Register "maint check libthread-db"
	and "maint set/show check-libthread-db".
	* NEWS: Mention the above new commands.

gdb/doc/ChangeLog:

	* gdb.texinfo (Maintenance Commands): Document "maint check
	libthread-db" and "maint set/show check-libthread-db".

gdb/testsuite/ChangeLog:

	* gdb.threads/check-libthread-db.exp: New file.
	* gdb.threads/check-libthread-db.c: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix gdb mingw build
@ 2018-06-08 16:46 sergiodj+buildbot
  2018-06-08 17:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 16:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2f4f025ff15b900706c8597060003a506107cf23 ***

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

Fix gdb mingw build

I noticed that the mingw build was failing in the buildbot.  This
patch fixes the problem.  I'm checking it in as obvious.

gdb/ChangeLog
2018-06-08  Tom Tromey  <tom@tromey.com>

	* windows-nat.c (windows_nat_target::xfer_partial): "beneath" is
	now a method.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove last cleanup from btrace code
@ 2018-06-08 14:56 sergiodj+buildbot
  2018-06-08 15:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 14:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 343b0027aed57c5a2d499e7e6e228608969a10be ***

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

Remove last cleanup from btrace code

This removes the last cleanup from btrace.c, replacing it with a use
of unique_xmalloc_ptr.

gdb/ChangeLog
2018-06-08  Tom Tromey  <tom@tromey.com>

	* btrace.c (parse_xml_raw): Use gdb::unique_xmalloc_ptr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanups from btrace code
@ 2018-06-08 14:44 sergiodj+buildbot
  2018-06-08 14:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-08 14:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8dcc53b37f4fe4797825c2a43bb1fb3df56b30d1 ***

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

Remove cleanups from btrace code

This removes some cleanups from the btrace code by minorly C++-ifying
struct btrace_data.

gdb/ChangeLog
2018-06-08  Tom Tromey  <tom@tromey.com>

	* common/btrace-common.h (struct btrace_data): Add constructor,
	destructor, move assignment operator.
	<empty, clear, fini>: New methods.
	<format>: Initialize.
	(btrace_data_init, btrace_data_fini, btrace_data_clear)
	(btrace_data_empty): Don't declare.
	* common/btrace-common.c (btrace_data_init): Remove.
	(btrace_data::fini): Rename from btrace_data_fini.
	(btrace_data::empty): Rename from btrace_data_empty.
	(btrace_data::clear): Rename from btrace_data_clear.  Return
	bool.
	* btrace.h (make_cleanup_btrace_data): Don't declare.
	* btrace.c (btrace_add_pc, btrace_stitch_trace, btrace_clear)
	(parse_xml_btrace): Update.
	(do_btrace_data_cleanup, make_cleanup_btrace_data): Remove.
	(maint_btrace_clear_packet_history_cmd): Update.

gdb/gdbserver/ChangeLog
2018-06-08  Tom Tromey  <tom@tromey.com>

	* linux-low.c (linux_low_read_btrace): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Introduce class target_stack
@ 2018-06-07 20:49 sergiodj+buildbot
  2018-06-07 21:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-07 20:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a1740ee1573d6e0e21692f815b322e3d062bbbee ***

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

Introduce class target_stack

Currently, the target stack is represented by a singly linked list,
with target_ops having a pointer to the target beneath.  This poses a
problem for multi-process / multi-target debugging.  In that case, we
will naturally want multiple instances of target stacks.  E.g., one
stack for inferior 1 which is debugging a core file, and another
target stack for inferior 2 which is debugging a remote process.  The
problem then is in finding a target's "beneath" target, if we consider
that for some target_ops types, we'll be sharing a single target_ops
instance between several inferiors.  For example, so far, I found no
need to have multiple instances of the spu_multiarch_target /
exec_target / dummy_target targets.

Thus this patch, which changes the target stack representation to an
array of pointers.  For now, there's still a single global instance of
this new target_stack class, though further down in the multi-target
work, each inferior will have its own instance.

gdb/ChangeLog:
2018-06-07  Pedro Alves  <palves@redhat.com>

	* target.h (target_ops) <beneath>: Now a method.  All references
	updated.
	(class target_stack): New.
	* target.c (g_target_stack): New.
	(g_current_top_target): Delete.
	(current_top_target): Get the top target out of g_target_stack.
	(target_stack::push, target_stack::unpush): New.
	(push_target, unpush_target): Reimplement.
	(target_is_pushed): Reimplement in terms of g_target_stack.
	(target_ops::beneath, target_stack::find_beneath): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Eliminate find_target_beneath
@ 2018-06-07 20:16 sergiodj+buildbot
  2018-06-07 20:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-07 20:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d6ca69cddc3fc6ef61fdfe3c3803d13b0b4e13e9 ***

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

Eliminate find_target_beneath

Call target_ops::beneath() throughout instead.

gdb/ChangeLog:
2018-06-07  Pedro Alves  <palves@redhat.com>

	* target.h (find_target_beneath): Delete declaration.
	* target.c (find_target_beneath): Delete definition.
	* aix-thread.c: All callers of find_target_beneath adjusted to
	call target_ops::beneath instead.
	* bsd-uthread.c: Likewise.
	* linux-thread-db.c: Likewise.
	* ravenscar-thread.c: Likewise.
	* sol-thread.c: Likewise.
	* spu-multiarch.c: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] target_ops::beneath -> target_ops::beneath()
@ 2018-06-07 19:21 sergiodj+buildbot
  2018-06-07 20:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-07 19:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b6a8c27bb8fb383be6f57724eb9aafa9f2f83aa5 ***

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

target_ops::beneath -> target_ops::beneath()

This changes target_ops::beneath from a pointer to a method, and
adjusts all references throughout.  The idea here is to make it easier
to change the target stack representation from an intrusive singly
linked list to something else without leaking implementation details
throughout.

The commit does not change the representation yet, that will be done
in a following patch.  That is why a new target_ops::m_beneath field
appears here.  That new field isn't really documented properly or made
private, simply because it will be removed shortly.

Note that target_ops::beneath() is essentially the same as the current
find_target_beneath routine.  The following patch will eliminate the
latter.

gdb/ChangeLog:
2018-06-07  Pedro Alves  <palves@redhat.com>

	* target.h (target_ops) <beneath>: Now a method.  All references
	updated.
	(target_ops) <m_beneath>: New.
	* target.c (target_ops::beneath): New.
	* corelow.c: Adjust all references to target_ops::beneath.
	* linux-thread-db.c: Likewise.
	* make-target-delegates: Likewise.
	* record-btrace.c: Likewise.
	* record-full.c: Likewise.
	* remote.c: Likewise.
	* target.c: Likewise.
	* target-delegates.c: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] target_stack -> current_top_target() throughout
@ 2018-06-07 18:59 sergiodj+buildbot
  2018-06-07 19:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-07 18:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8b88a78e63526b84d540b9c7d5f459593a248d5e ***

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

target_stack -> current_top_target() throughout

The recent C++ification of target_ops replaced references to the old
"current_target" squashed target throughout with references to a
"target_stack" pointer.  I had picked the "target_stack" name very
early in the multi-target work, and managed to stick with it, even
though it's a bit of a misnomer, since it isn't really a "target
stack" object, but a pointer into the current top target in the stack.
As I'm splitting more pieces off of the multi-target branch, I've come
to think that it's better to rename it now.  A following patch will
introduce a new class to represent a target stack, and "target_stack"
would be _its_ ideal name.  (In the branch, the class is called
a_target_stack to work around the clash.)

Thus this commit renames target_stack to current_top_target and
replaces all references throughout.  Also, while at it,
current_top_target is made a function instead of a pointer, to make it
possible to change its internal implementation without leaking
implementation details out.  In a couple patches, the implementation
of the function will change to refer to a target stack object, and
then further down the multi-target work, it'll change again to find
the right target stack for the current inferior.

gdb/ChangeLog:
2018-06-07  Pedro Alves  <palves@redhat.com>

	* target.h (target_stack): Delete.
	(current_top_target): Declare function.
	* target.c (target_stack): Delete.
	(g_current_top_target): New.
	(current_top_target): New function.
	* auxv.c: Use current_top_target instead of target_stack
	throughout.
	* avr-tdep.c: Likewise.
	* breakpoint.c: Likewise.
	* corefile.c: Likewise.
	* elfread.c: Likewise.
	* eval.c: Likewise.
	* exceptions.c: Likewise.
	* frame.c: Likewise.
	* gdbarch-selftests.c: Likewise.
	* gnu-v3-abi.c: Likewise.
	* ia64-tdep.c: Likewise.
	* ia64-vms-tdep.c: Likewise.
	* infcall.c: Likewise.
	* infcmd.c: Likewise.
	* infrun.c: Likewise.
	* linespec.c: Likewise.
	* linux-tdep.c: Likewise.
	* minsyms.c: Likewise.
	* ppc-linux-nat.c: Likewise.
	* ppc-linux-tdep.c: Likewise.
	* procfs.c: Likewise.
	* regcache.c: Likewise.
	* remote.c: Likewise.
	* rs6000-tdep.c: Likewise.
	* s390-linux-nat.c: Likewise.
	* s390-tdep.c: Likewise.
	* solib-aix.c: Likewise.
	* solib-darwin.c: Likewise.
	* solib-dsbt.c: Likewise.
	* solib-spu.c: Likewise.
	* solib-svr4.c: Likewise.
	* solib-target.c: Likewise.
	* sparc-tdep.c: Likewise.
	* sparc64-tdep.c: Likewise.
	* spu-tdep.c: Likewise.
	* symfile.c: Likewise.
	* symtab.c: Likewise.
	* target-descriptions.c: Likewise.
	* target-memory.c: Likewise.
	* target.c: Likewise.
	* target.h: Likewise.
	* tracefile-tfile.c: Likewise.
	* tracepoint.c: Likewise.
	* valops.c: Likewise.
	* valprint.c: Likewise.
	* value.c: Likewise.
	* windows-tdep.c: Likewise.
	* mi/mi-main.c: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Aarch64 SVE pseudo register support
@ 2018-06-07 10:06 sergiodj+buildbot
  2018-06-07 10:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-07 10:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 63bad7b636870e3a0af4fc97cc2b8ec5c2603a41 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 63bad7b636870e3a0af4fc97cc2b8ec5c2603a41

Aarch64 SVE pseudo register support

Add the functionality for reading/writing pseudo registers.

On SVE the V registers are pseudo registers. This is supported
by adding AARCH64_SVE_V0_REGNUM.

	* aarch64-tdep.c (AARCH64_SVE_V0_REGNUM): Add define.
	(aarch64_vnv_type): Add function.
	(aarch64_pseudo_register_name): Add V regs for SVE.
	(aarch64_pseudo_register_type): Likewise.
	(aarch64_pseudo_register_reggroup_p): Likewise.
	(aarch64_pseudo_read_value_2): Use V0 offset for SVE
	(aarch64_pseudo_read_value): Add V regs for SVE.
	(aarch64_pseudo_write_2): Use V0 offset for SVE
	(aarch64_pseudo_write): Add V regs for SVE.
	* aarch64-tdep.h (struct gdbarch_tdep): Add vnv_type.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] TIC6X __c6xabi_DSBT_BASE
@ 2018-06-07  0:45 sergiodj+buildbot
  2018-06-07  0:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-07  0:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 527278f3360dde3e5439b8d10f3f635155b35aca ***

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

TIC6X __c6xabi_DSBT_BASE

Adding an undefined __c6xabi_DSBT_BASE via an EXTERN in the linker
script isn't ideal, as the symbol is not always needed.  This patch
adds the undefined symbol on encountering relocations where it is
implicitly referenced.

bfd/
	* elf32-tic6x.c (elf32_tic6x_check_relocs): Reference
	__c6xabi_DSBT_BASE explicitly for R_C6000_SBR_* relocs.
ld/
	* emulparams/elf32_tic6x_le.sh (EXECUTABLE_SYMBOLS): Don't define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Guard declarations of 'sve_{vq, vl}_from_{vl, vq}' macros on Aarch64 (and unbreak build)
@ 2018-06-06 22:15 sergiodj+buildbot
  2018-06-06 22:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-06 22:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e5a77256e8961294b3ea7d483124834311ca363b ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: e5a77256e8961294b3ea7d483124834311ca363b

Guard declarations of 'sve_{vq,vl}_from_{vl,vq}' macros on Aarch64 (and unbreak build)

Commit 122394f1476b1c925a281b15399119500c8231c1 ("Function for reading
the Aarch64 SVE vector length") has added macros to manipulate SVE
vector sizes based on Linux kernel sources, but did not guard them
with #ifndef's, which breaks the build when the system headers already
have these macros:

    CXX    aarch64-linux-nat.o
  In file included from ../../gdb/aarch64-tdep.h:25,
                   from ../../gdb/aarch64-linux-nat.c:30:
  ../../gdb/arch/aarch64.h:79: error: "sve_vq_from_vl" redefined [-Werror]
   #define sve_vq_from_vl(vl) ((vl) / 0x10)

  In file included from /usr/include/bits/sigcontext.h:30,
                   from /usr/include/signal.h:291,
                   from build-gnulib/import/signal.h:52,
                   from ../../gdb/linux-nat.h:23,
                   from ../../gdb/aarch64-linux-nat.c:26:
  /usr/include/asm/sigcontext.h:154: note: this is the location of the previous definition
   #define sve_vq_from_vl(vl) ((vl) / SVE_VQ_BYTES)

  In file included from ../../gdb/aarch64-tdep.h:25,
                   from ../../gdb/aarch64-linux-nat.c:30:
  ../../gdb/arch/aarch64.h:80: error: "sve_vl_from_vq" redefined [-Werror]
   #define sve_vl_from_vq(vq) ((vq) * 0x10)

  In file included from /usr/include/bits/sigcontext.h:30,
                   from /usr/include/signal.h:291,
                   from build-gnulib/import/signal.h:52,
                   from ../../gdb/linux-nat.h:23,
                   from ../../gdb/aarch64-linux-nat.c:26:
  /usr/include/asm/sigcontext.h:155: note: this is the location of the previous definition
   #define sve_vl_from_vq(vq) ((vq) * SVE_VQ_BYTES)

In order to fix this breakage, this commit guards the declaration of
the macros using #ifndef's.

gdb/ChangeLog:
2018-06-06  Sergio Durigan Junior  <sergiodj@redhat.com>

	* arch/aarch64.h (sve_vg_from_vl): Guard with #ifndef.
	(sve_vl_from_vg): Likewise.
	(sve_vq_from_vl): Likewise.
	(sve_vl_from_vq): Likewise.
	(sve_vq_from_vg): Likewise.
	(sve_vg_from_vq): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix typo in common/enum-flags.h example
@ 2018-06-06  0:46 sergiodj+buildbot
  2018-06-06  7:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-06  0:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 115f7325b5b76450b9a1d16848a2a54f54e49747 ***

Author: David Malcolm <dmalcolm@redhat.com>
Branch: master
Commit: 115f7325b5b76450b9a1d16848a2a54f54e49747

Fix typo in common/enum-flags.h example

The DEF_ENUM_FLAGS_TYPE macro should be used with a trailing
semicolon, but the example in the comment lacks one.

gdb/ChangeLog:
2018-06-05  David Malcolm  <dmalcolm@redhat.com>

	* common/enum-flags.h: Add trailing semicolon to example in
	comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Tidy bfdio to consistenly use containing archive
@ 2018-06-05 23:06 sergiodj+buildbot
  2018-06-06  7:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-05 23:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5c4ce239a3ab9263163a0fe8e7487b39a41c43d1 ***

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

Tidy bfdio to consistenly use containing archive

Archive element IO is performed on the file of the containing archive,
which leads to the BFD "where" field of archives and their elements
being out of sync with the real file position.  (We're talking
traditional archives here, not thin archives.)  The old bfd_seek code
recognized this by not attempting to optimize away seeks for
archives.  However, there was other code that could return bogus
results.  For example, cache.c limits the number of open files by
closing a file and remembering its state once the limit is reached.
If bfd_tell is called on an archive element when the containing
archive is closed, it will return an invalid file pointer.

It's possible to have a valid "where" field for archives by always
using and updating the containing archive BFD.  That's what this patch
does.  Note that cache.c used to find the containing archive BFD
anyway for the iostream, so we're not really doing extra work, just
transferring it up to the correct abstraction level.

The patch also gets rid of some hacks.  bfd_tell was called when
bfd_seek failed, in an attempt to correct "where".  That's got to be
papering over another problem, so that code has been removed.
bfd_read also had an "optimiziation" to return early when the number
of bytes was zero, and bfd_seek optimized calls that didn't move the
file pointer.  This was covering for a coff_slurp_line_table bug where
IO was attempted on a pe-dll BFD without an iovec.

	* bfd.c (struct bfd): Update comment on "where" usage.
	* bfdio.c (bfd_bwrite, bfd_stat): Use and update "iovec",
	"iostream", and "where" from containing archive file.  Return
	error on NULL iovec.
	(bfd_bread): Similarly, and return error attempted out of
	bounds archive element access.
	(bfd_tell, bfd_flush): Use and update "iovec", "iostream", and
	"where" from containing archive file.
	(bfd_seek): Likewise.  Return error on NULL iovec.  Don't
	attempt to optimize away seeks.  Don't paper over errors by
	calling bfd_tell.
	(bfd_get_mtime): Call bfd_stat rather than iovec->bstat.
	(bfd_get_size): Likewise.
	(bfd_mmap): Operate on and use iovec of containing archive
	file.  Return error on NULL iovec.
	* cache.c (bfd_cache_lookup_worker): Abort if working on
	archive element bfd.
	(cache_bread_1): Delete bfd parameter, add FILE* parameter.
	Don't ignore zero byte reads.
	(cache_bread): Look up FILE* in cache here.  Error on NULL
	lookup.
	(cache_bwrite): Rename "where" to "from".
	(cache_bmmap): Don't handle archive elements.
	* coffcode.h (coff_slurp_line_table): Exit early on zero
	lineno count.
	* bfd-in2.h: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23254, ld.bfd mishandles file pointers while scanning archive
@ 2018-06-05 13:50 sergiodj+buildbot
  2018-06-06  6:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-05 13:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 27b0767593284f97384b3597ebd211164f8c8b47 ***

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

PR23254, ld.bfd mishandles file pointers while scanning archive

Best practice is to not mix lseek/read with fseek/fread on the same
underlying file descriptor, as not all stdio implementations will cope.
Since the plugin uses lseek/read while bfd uses fseek/fread this patch
reopens the file for exclusive use by the plugin rather than trying to
restore the file descriptor.  That allows the plugin to read the file
after plugin_call_claim_file too.

bfd/
	PR 23254
	* plugin.c (bfd_plugin_open_input): Allow for possibility of
	nested archives.  Open file again for plugin.
	(try_claim): Don't save and restore file position.  Close file
	if not claimed.
	* sysdep.h (O_BINARY): Define.
ld/
	PR 23254
	* plugin.c (plugin_call_claim_file): Revert 2016-07-19 patch.
	(plugin_object_p): Don't dup file descriptor.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove last Ada cleanups
@ 2018-06-05  6:27 sergiodj+buildbot
  2018-06-06  4:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-05  6:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 54d343a24019367e85bb2e90966f2da483868637 ***

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

Remove last Ada cleanups

This removes the last cleanups from the Ada code by changing
ada_lookup_symbol_list's out parameter to be a std::vector, and then
fixing up the fallout.

This is a relatively shallow change.  Deeper changes are possible, for
example (1) changing various other functions to accept a vector rather
than a pointer, or (2) changing ada_lookup_symbol_list to return the
vector and omitting the length entirely.

Tested by the buildbot, but I'll wait for Joel to test these as well.

gdb/ChangeLog
2018-06-04  Tom Tromey  <tom@tromey.com>

	* ada-lang.h (ada_lookup_symbol_list): Update.
	* ada-lang.c (resolve_subexp): Update.
	(symbols_are_identical_enums): Change type of syms.  Remove nsyms
	parameter.
	(remove_extra_symbols, remove_irrelevant_renamings): Likewise.
	(ada_lookup_symbol_list_worker, ada_lookup_symbol_list): Change
	results parameter to std::vector.
	(ada_iterate_over_symbols, ada_lookup_symbol, get_var_value):
	Update.
	* ada-exp.y (block_lookup): Update.
	(select_possible_type_sym): Change type of syms.  Remove nsyms
	parameter.
	(write_var_or_type, write_name_assoc): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (windows) GDB/MI crash when using "-list-thread-groups --available"
@ 2018-06-04 22:09 sergiodj+buildbot
  2018-06-04 22:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 22:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 178d6a638693d1a7a66b0553f16b1df95b4f27ee ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 178d6a638693d1a7a66b0553f16b1df95b4f27ee

(windows) GDB/MI crash when using "-list-thread-groups --available"

On Windows, using the "-list-thread-groups --available" GDB/MI command
before an inferior is being debugged:

    % gdb -q -i=mi
    =thread-group-added,id="i1"
    =cmd-param-changed,param="auto-load safe-path",value="/"
    (gdb)
    -list-thread-groups --available
    Segmentation fault

Ooops!

The SEGV happens because the -list-thread-groups --available command
triggers a windows_nat_target::xfer_partial call for a TARGET_OBJECT_OSDATA
object.  Until a program is being debugged, the target_ops layer that
gets the call is the Windows "native" layer. Except for a couple of
specific objects (TARGET_OBJECT_MEMORY and TARGET_OBJECT_LIBRARIES),
this layer's xfer_partial method delegates the xfer of other objects
to the target beneath:

    default:
      return beneath->xfer_partial (object, annex,
                                    readbuf, writebuf, offset, len,
                                    xfered_len);

Unfortunately, there is no "beneath layer" in this case, so
beneath is NULL and dereferencing it leads to the SEGV.

This patch fixes the issue by checking beneath before trying
to delegate the request.

gdb/ChangeLog:

        * windows-nat.c (windows_nat_target::xfer_partial): Return
        TARGET_XFER_E_IO if we need to delegate to the target beneath
        but BENEATH is NULL.

gdb/testsuite/ChangeLog:

        * gdb.mi/list-thread-groups-no-inferior.exp: New testcase.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] xtensa: add separate property sections option
@ 2018-06-04 19:51 sergiodj+buildbot
  2018-06-04 19:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 19:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8255c61b8ad5ac933672d26e5c9454aaf09ccaeb ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: 8255c61b8ad5ac933672d26e5c9454aaf09ccaeb

xtensa: add separate property sections option

It is currently not possible to correctly match .xt.prop information
for sections with identical VMA. Allow creation of separate property
sections in the BFD. Add assembler option --separate-prop-tables to
allow creation of separate property sections.

2018-06-04  Volodymyr Arbatov  <arbatov@cadence.com>
bfd/

	* elf32-xtensa.c (elf32xtensa_separate_props): New global
	variable.
	(xtensa_add_names): New function.
	(xtensa_property_section_name): Add new parameter
	separate_sections, use it to choose property section name.
	(xtensa_get_separate_property_section): New function.
	(xtensa_get_property_section): Invoke
	xtensa_get_separate_property_section to get individual property
	section if it exists, common property section otherwise.
	(xtensa_make_property_section): Pass elf32xtensa_separate_props
	to xtensa_property_section_name.

gas/
	* config/tc-xtensa.c (elf32xtensa_separate_props): New
	declaration.
	(option_separate_props, option_no_separate_props): New
	enumeration constants.
	(md_longopts): Add separate-prop-tables option.
	(md_parse_option): Add cases for option_separate_props and
	option_no_separate_props.
	(md_show_usage): Add help for [no-]separate-prop-tables options.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] xtensa: use property tables for correct disassembly
@ 2018-06-04 18:56 sergiodj+buildbot
  2018-06-04 21:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 18:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4b8e28c79356265b2c111e044142fb6d6d2db44e ***

Author: Max Filippov <jcmvbkbc@gmail.com>
Branch: master
Commit: 4b8e28c79356265b2c111e044142fb6d6d2db44e

xtensa: use property tables for correct disassembly

xtensa disassembler does not use information from the .xt.prop sections
to switch between code/data disassembly in text sections. This may
result in incorrect disassembly when data is interpreted as code and
disassembler loses synchronization with instruction stream. Use .xt.prop
section information to correctly interpret code and data and synchronize
with instruction stream.

2018-06-04  Max Filippov  <jcmvbkbc@gmail.com>
bfd/
	* elf32-xtensa.c (xtensa_read_table_entries): Make global.
	(compute_fill_extra_space): Drop declaration. Rename function to
	xtensa_compute_fill_extra_space.
	(compute_ebb_actions, remove_dead_literal): Update references to
	compute_fill_extra_space.

include/
	* elf/xtensa.h (xtensa_read_table_entries)
	(xtensa_compute_fill_extra_space): New declarations.

opcodes/
	* xtensa-dis.c (bfd.h, elf/xtensa.h): New includes.
	(dis_private): Add new fields for property section tracking.
	(xtensa_coalesce_insn_tables, xtensa_find_table_entry)
	(xtensa_instruction_fits): New functions.
	(fetch_data): Bump minimal fetch size to 4.
	(print_insn_xtensa): Make struct dis_private static.
	Load and prepare property table on section change.
	Don't disassemble literals. Don't disassemble instructions that
	cross property table boundaries.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION to silence GCC 8.1
@ 2018-06-04 18:33 sergiodj+buildbot
  2018-06-04 18:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 18:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95da9854466ada2572b42f5528711a06a2d42db1 ***

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

Use DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION to silence GCC 8.1

GCC 8.1 warns about destination size with -Wstringop-truncation:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643

Use DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION to silence it.

bfd/

	PR binutils/23146
	* bfd-in.h: Include "diagnostics.h".
	* bfd-in2.h: Regenerated.
	* elf32-arm.c (elf32_arm_nabi_write_core_note): Use
	DIAGNOSTIC_PUSH, DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION and
	DIAGNOSTIC_POP to silence GCC 8.1 warnings with
	-Wstringop-truncation.
	* elf32-ppc.c (ppc_elf_write_core_note): Likewse.
	* elf32-s390.c (elf_s390_write_core_note): Likewse.
	* elf64-ppc.c (ppc64_elf_write_core_note): Likewse.
	* elf64-s390.c (elf_s390_write_core_note): Likewse.
	* elfxx-aarch64.c (_bfd_aarch64_elf_write_core_note): Likewse.

include/

	* diagnostics.h (DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION): Always
	define for GCC.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use ELF_SECTION_IN_SEGMENT to map segments
@ 2018-06-04 17:01 sergiodj+buildbot
  2018-06-04 17:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 62b74cb8b00ca2b42de30ceff4d2f1552b77a10d ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 62b74cb8b00ca2b42de30ceff4d2f1552b77a10d

Use ELF_SECTION_IN_SEGMENT to map segments

The macro ELF_SECTION_IN_SEGMENT should be used when calculating if
a section maps to a segment.

gdb/
	* elfread.c (elf_symfile_segments): Use ELF_SECTION_IN_SEGMENT.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add configure.nat as a dependency of config.status
@ 2018-06-04 16:02 sergiodj+buildbot
  2018-06-04 16:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 16:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT baf00c2d75351de7a42dae32aea3a71c8902cd25 ***

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

Add configure.nat as a dependency of config.status

After pulling Alan's change that added aarch64-sve-linux-ptrace.o to
configure.nat, I got an undefined reference to aarch64_sve_get_vq when
doing a "make clean && make".  It turns out that re-running configure
(./config.status --recheck) was needed to re-generate the Makefile with
aarch64-sve-linux-ptrace.o included in the object list.  Putting
configure.nat in the dependencies of config.status would make sure that
when we modify configure.nat, the configure script is re-ran.  I think
it also makes sense because configure.tgt and configure.host are also
there.

gdb/ChangeLog:

	* Makefile.in (config.status): Add configure.nat as a
	dependency.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add client_state struct.
@ 2018-06-04 15:13 sergiodj+buildbot
  2018-06-04 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 15:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c12a5089640109567e2e06f0c5d2d1bf4fb3f5eb ***

Author: Stan Cox <scox@redhat.com>
Branch: master
Commit: c12a5089640109567e2e06f0c5d2d1bf4fb3f5eb

Add client_state struct.

Collect per client specific global data items into struct client_state,
which is similar in purpose to remote.c::remote_state.

gdbserver/ChangeLog
	* server.h (struct client_state): New.
	* server.c (cont_thread, general_thread, multi_process)
	(report_fork_events, report_vfork_events, report_exec_events)
	(report_thread_events, swbreak_feature, hwbreak_feature)
	(vCont_supported, disable_randomization, pass_signals)
	(program_signals, program_signals_p, last_status, last_ptid, own_buf):
	Moved to client_state.
	* remote-utils.c (remote_debug, noack_mode)
	(transport_is_reliable): Moved to client_state.
	* tracepoint.c (current_traceframe): Moved to client_state.

	Update all callers.
	* server.c, remote-utils.c, tracepoint.c, fork-child.c,
	linux-low.c, remote-utils.h, target.c: Use client_state.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION
@ 2018-06-04 14:50 sergiodj+buildbot
  2018-06-04 14:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 14:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 23081219bfe58dd07b1e0a110728d7195155d0e2 ***

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

Add DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION

Add DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION for GCC 8.1 to silence
-Wstringop-truncation warning:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643

	* diagnostics.h (DIAGNOSTIC_STRINGIFY_1): New.
	(DIAGNOSTIC_STRINGIFY): Likewise.
	(DIAGNOSTIC_IGNORE): Replace STRINGIFY with DIAGNOSTIC_STRINGIFY.
	(DIAGNOSTIC_IGNORE_SELF_MOVE): Define empty if not defined.
	(DIAGNOSTIC_IGNORE_DEPRECATED_REGISTER): Likewise.
	(DIAGNOSTIC_IGNORE_UNUSED_FUNCTION): Likewise.
	(DIAGNOSTIC_IGNORE_SWITCH_DIFFERENT_ENUM_TYPES): Likewise.
	(DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION): New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change functions in cp-name-parser.y into methods
@ 2018-06-04 14:05 sergiodj+buildbot
  2018-06-04 14:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 14:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 214b073cedadbdc7a0d272dc5ede79a5ab7785ea ***

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

Change functions in cp-name-parser.y into methods

Pedro pointed out in an earlier patch that it would be possible to
make some helper functions in cp-name-parser.y into methods on
cpname_state, cleaning up the code a bit.  This patch implements this
idea.

Doing this required moving the %union earlier in the .y file, so the
patch is somewhat bigger than you might expect.

Tested by building with both bison and byacc, and then running the
gdb.cp tests.

gdb/ChangeLog
2018-06-04  Tom Tromey  <tom@tromey.com>

	* cp-name-parser.y (cpname_state): Add method declarations.
	(HANDLE_QUAL): Update.
	(cpname_state::d_grab, cpname_state::fill_comp)
	(cpname_state::make_operator, cpname_state::make_dtor)
	(cpname_state::make_builtin_type, cpname_state::make_name)
	(cpname_state::d_qualify, cpname_state::d_int_type)
	(cpname_state::d_unary, cpname_state::d_binary): Now methods.
	(%union): Move earlier.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add aarch64 pseudo help functions
@ 2018-06-04 13:45 sergiodj+buildbot
  2018-06-04 13:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 13:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c5cd5c3b4dcb88da4ff980186b63fa169ba9263 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 3c5cd5c3b4dcb88da4ff980186b63fa169ba9263

Add aarch64 pseudo help functions

Reduce code copy/paste by adding two helper functions for
aarch64_pseudo_read_value and aarch64_pseudo_write
Does not change any functionality.

gdb/
	* aarch64-tdep.c (aarch64_pseudo_read_value_1): New helper func.
	(aarch64_pseudo_write_1): Likewise.
	(aarch64_pseudo_read_value): Use helper.
	(aarch64_pseudo_write): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use uint64_t for aarch64 tdep VQ
@ 2018-06-04 11:57 sergiodj+buildbot
  2018-06-04 12:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 11:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1332a1400145b5cca04c4d1ea77e0191d8dc5727 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 1332a1400145b5cca04c4d1ea77e0191d8dc5727

Use uint64_t for aarch64 tdep VQ


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Enable SVE for GDB
@ 2018-06-04 11:39 sergiodj+buildbot
  2018-06-04 11:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 11:39 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ba2d2bb24ea593c7fb17f51ef23f122064bb17d7 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: ba2d2bb24ea593c7fb17f51ef23f122064bb17d7

Enable SVE for GDB

Enable SVE support for GDB by reading the VQ when creating a
target description.

Also ensurse that SVE is taken into account when creating
the tdep structure, and store the current VQ value directly in tdep.

gdb/
	* aarch64-linux-nat.c (aarch64_linux_read_description): Support SVE.
	* aarch64-tdep.c (aarch64_get_tdesc_vq): New function.
	(aarch64_gdbarch_init): Check for SVE.
	* aarch64-tdep.h (gdbarch_tdep::has_sve): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use uint64_t for SVE VQ
@ 2018-06-04 10:40 sergiodj+buildbot
  2018-06-04 11:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-04 10:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 39bfb9373c5cca78948c94174d46891c1a3d3613 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 39bfb9373c5cca78948c94174d46891c1a3d3613

Use uint64_t for SVE VQ

Previously VQ was of type long. Using uint64_t ensures it always matches the
same type as the VG register.
Note that in the Linux kernel, VQ is 16bits. We cast it up to 64bits
immediately after reading to ensure we always use the same type throughout
the code.

gdb/
	* aarch64-tdep.c (aarch64_read_description): Use uint64_t for VQ.
	* aarch64-tdep.h (aarch64_read_description): Likewise.
	* arch/aarch64.c (aarch64_create_target_description): Likewise.
	* arch/aarch64.h (aarch64_create_target_description): Likewise.
	* features/aarch64-sve.c (create_feature_aarch64_sve): Likewise.
	* nat/aarch64-sve-linux-ptrace.c(aarch64_sve_get_vq): Likewise.
	* nat/aarch64-sve-linux-ptrace.h (aarch64_sve_get_vq): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Handle out-of-range calls to undefined weak.
@ 2018-06-03 23:24 sergiodj+buildbot
  2018-06-03 23:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-03 23:24 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cf7a5066b92552b62ca4d247c241a19d1a6e599d ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: cf7a5066b92552b62ca4d247c241a19d1a6e599d

RISC-V: Handle out-of-range calls to undefined weak.

	bfd/
	PR ld/23244
	* elfnn-riscv.c (riscv_elf_relocate_section) <R_RISCV_CALL>: Check
	for and handle an undefined weak with no PLT.

	ld/
	* testsuite/ld-riscv-elf/ld-riscv-elf.exp: Run new weak ref tests.
	* testsuite/ld-riscv-elf/weakref.ld: New.
	* testsuite/ld-riscv-elf/weakref32.d: New.
	* testsuite/ld-riscv-elf/weakref32.s: New.
	* testsuite/ld-riscv-elf/weakref64.d: New.
	* testsuite/ld-riscv-elf/weakref64.s: New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Fix symbol address problem with versioned symbols.
@ 2018-06-03 22:23 sergiodj+buildbot
  2018-06-03 22:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-03 22:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 137b5cbd204241ec47873c353cf7e41b47182d53 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 137b5cbd204241ec47873c353cf7e41b47182d53

RISC-V: Fix symbol address problem with versioned symbols.

	bfd/
	PR ld/22756
	* elfnn-riscv.c (riscv_relax_delete_bytes): Add versioned_hidden check
	to code that ignores duplicate symbols.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Split value_fetch_lazy
@ 2018-06-02 14:08 sergiodj+buildbot
  2018-06-02 14:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-02 14:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41c60b4b2668947726fb5762de95d57b931a3200 ***

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

Split value_fetch_lazy

While reading value_fetch_lazy, I thought it would be good to split it
in small functions (especially the part that handles lval_register).

gdb/ChangeLog:

	* value.c (value_fetch_lazy_bitfield): New.
	(value_fetch_lazy_memory): New.
	(value_fetch_lazy_register): New.
	(value_fetch_lazy): Factor out to smaller functions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Include parser-defs.h in cp-name-parser.y
@ 2018-06-01 22:57 sergiodj+buildbot
  2018-06-01 23:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 98e69eb381347eb06dfedaa0b185ad26818ce5cd ***

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

Include parser-defs.h in cp-name-parser.y

This changes cp-name-parser.y to include parser-defs.h, removing the
copy-pasted declaration of parser_fprintf.  This can be done now that
cp-name-parser.y does not define any global variables.

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* cp-name-parser.y: Include parser-defs.h.
	(parser_fprintf): Remove declaration.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use yy-remap.h in cp-name-parser.y
@ 2018-06-01 21:21 sergiodj+buildbot
  2018-06-01 22:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 21:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55b6c9849624fc105539e08222fb8ff128a5f7e2 ***

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

Use yy-remap.h in cp-name-parser.y

This changes cp-name-parser.y to use yy-remap.h, rather than its old
manual approach.

This required declaring parser_fprintf in cp-name-parser.y.
parser-defs.h can't be included here because parser-defs.h declares a
global "lexptr", which conflicts with the local one in
cp-name-parser.y.  This is only temporary, and will be cleaned up
later in the series.

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* cp-name-parser.y (parser_fprintf): Declare.
	(GDB_YY_REMAP_PREFIX): Define.
	Include yy-remap.h.  Don't redefine yy* identifiers.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Move gdb/common/diagnostics.h to include/diagnostics.h
@ 2018-06-01 21:12 sergiodj+buildbot
  2018-06-01 21:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 21:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e9cb46ab59ff2ea94a7fd9fa857a084d3a9b8b39 ***

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

Move gdb/common/diagnostics.h to include/diagnostics.h

Move gdb/common/diagnostics.h to include/diagnostics.h so that it can
be used in binutils.

gdb/

	* ada-lex.l: Include "diagnostics.h" instead of
	"common/diagnostics.h".
	* unittests/environ-selftests.c: Likewise.
	* common/diagnostics.h: Moved to ../include.

include/

	* diagnostics.h: Moved from ../gdb/common/diagnostics.h.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a static buffer from cp-name-parser.y
@ 2018-06-01 20:47 sergiodj+buildbot
  2018-06-01 22:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 20:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3513a6bb20ef286e303367d4ef4963b5dab877cb ***

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

Remove a static buffer from cp-name-parser.y

This removes a static buffer from cp-name-parser.y by replacing the
fixed-sized buffer with a std::string out parameter.

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* python/py-type.c (typy_legacy_template_argument): Update.
	* cp-support.h (cp_demangled_name_to_comp): Update.
	* cp-name-parser.y (cp_demangled_name_to_comp): Change errmsg
	parameter to be a "std::string *".
	(main): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] inadvertent language switch during breakpoint_re_set_one
@ 2018-06-01 20:36 sergiodj+buildbot
  2018-06-01 20:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 20:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 8e817061976910fd1ac7bb8f689dbd96123ea593 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 8e817061976910fd1ac7bb8f689dbd96123ea593

inadvertent language switch during breakpoint_re_set_one

Trying to insert a breakpoint using *FUNC'address with an Ada program
and then running the program until reaching that breakpoint currently
yields the following behavior:

    (gdb) break *a'address
    Breakpoint 1 at 0x40240c: file a.adb, line 1.
    (gdb) run
    [1]  + 27222 suspended (tty output) /[...]/gdb -q simple_main

Unsuspending GDB then shows it was suspended trying to report
the following error:

    Starting program: /home/takamaka.a/brobecke/ex/simple/a
    Error in re-setting breakpoint 1: Unmatched single quote.
    Error in re-setting breakpoint 1: Unmatched single quote.
    Error in re-setting breakpoint 1: Unmatched single quote.
    [Inferior 1 (process 32470) exited normally]

The "a'address" is Ada speak for function A's address ("A" by
itself means the result of calling A with no arguments). The
transcript above shows that we're having problems trying to
parse the breakpoint location while re-setting it.  As a result,
we also fail to stop at the breakpoint.

Normally, breakpoint locations are evaluated with the current_language
being set to the language of the breakpoint. But, unfortunately for us,
what happened in this case is that parse_exp_in_context_1 calls
get_selected_block which eventually leads to a call to select_frame
because the current_frame hadn't been set yet.  select_frame then
finds that our language_mode is auto, and therefore changes the
current_language to match the language of the frame we just selected.
In our case, the language chosen was 'c', which of course is not
able to parse an Ada expression, hence the error.

This patch prevents this by forcing the language_mode to manual
before we call breakpoint_re_set_one.

gdb/ChangeLog:

        * breakpoint.c (breakpoint_re_set): Temporarily force language_mode
        to language_mode_manual while calling breakpoint_re_set_one.

gdb/testsuite/ChangeLog:

        * gdb.ada/bp_fun_addr: New testcase.

Tested on x86_64-linux.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Bump version number to 2.30.52
@ 2018-06-01 19:10 sergiodj+buildbot
  2018-06-01 19:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 19:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55e99962b24d9f2dc8a64b473259ca12e369fd20 ***

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

Bump version number to 2.30.52

Bump version number to 2.30.52 since _bfd_link_hide_symbol has been added
to bfd_target.

bfd/

	* version.m4: Bump version to 2.30.52
	* configure: Regenerated.

binutils/

	* configure: Regenerated.

gas/

	* configure: Regenerated.

gprof/

	* configure: Regenerated.

ld/

	* configure: Regenerated.

opcodes/

	* configure: Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove type_name_no_tag and rename type_name_no_tag_or_error
@ 2018-06-01 18:49 sergiodj+buildbot
  2018-06-01 18:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 18:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a737d952e0a9122dd0d439ba2a2ca531b070e6bd ***

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

Remove type_name_no_tag and rename type_name_no_tag_or_error

type_name_no_tag is just a plain wrapper for TYPE_NAME now, so this
patch removes it.  And, because tag names no longer exist, this
renames type_name_no_tag_or_error to type_name_or_error.

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* valops.c (value_cast_structs, destructor_name_p): Update.
	* symtab.c (gdb_mangle_name): Update.
	* stabsread.c (define_symbol, read_cpp_abbrev, read_baseclasses):
	Update.
	* p-valprint.c (pascal_object_is_vtbl_ptr_type)
	(pascal_object_print_value_fields, pascal_object_print_value):
	Update.
	* p-typeprint.c (pascal_type_print_derivation_info): Update.
	* linespec.c (find_methods): Update.
	* gdbtypes.h (type_name_no_tag): Remove.
	(type_name_or_error): Rename from type_name_no_tag_or_error.
	* gdbtypes.c (type_name_no_tag): Remove.
	(type_name_or_error): Rename from type_name_no_tag_or_error.
	(lookup_struct_elt_type, check_typedef): Update.
	* expprint.c (print_subexp_standard): Update.
	* dwarf2read.c (dwarf2_add_field, load_partial_dies): Update.
	* d-namespace.c (d_lookup_nested_symbol): Update.
	* cp-valprint.c (cp_is_vtbl_ptr_type, cp_print_value_fields)
	(cp_print_class_member): Update.
	* cp-namespace.c (cp_lookup_nested_symbol): Update.
	* completer.c (add_struct_fields): Update.
	* c-typeprint.c (cp_type_print_derivation_info)
	(c_type_print_varspec_prefix, c_type_print_base_struct_union):
	Update.
	* ada-lang.c (parse_old_style_renaming, xget_renaming_scope)
	(ada_prefer_type, ada_is_exception_sym): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove TYPE_TAG_NAME
@ 2018-06-01 18:09 sergiodj+buildbot
  2018-06-01 18:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 18:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e86ca25fd6cc06488c9dda936cf83f0fcdf6b58b ***

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

Remove TYPE_TAG_NAME

TYPE_TAG_NAME has been an occasional source of confusion and bugs.  It
seems to me that it is only useful for C and C++ -- but even there,
not so much, because at least with DWARF there doesn't seem to be any
way to wind up with a type where the name and the tag name are both
non-NULL and different.

So, this patch removes TYPE_TAG_NAME entirely.  This should save a
little memory, but more importantly, it simplifies this part of gdb.

A few minor test suite adjustments were needed.  In some situations
the new code does not yield identical output to the old code.

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* valops.c (enum_constant_from_type, value_namespace_elt)
	(value_maybe_namespace_elt): Update.
	* valarith.c (find_size_for_pointer_math): Update.
	* target-descriptions.c (make_gdb_type): Update.
	* symmisc.c (print_symbol): Update.
	* stabsread.c (define_symbol, read_type)
	(complain_about_struct_wipeout, add_undefined_type)
	(cleanup_undefined_types_1): Update.
	* rust-lang.c (rust_tuple_type_p, rust_slice_type_p)
	(rust_range_type_p, val_print_struct, rust_print_struct_def)
	(rust_internal_print_type, rust_composite_type)
	(rust_evaluate_funcall, rust_evaluate_subexp)
	(rust_inclusive_range_type_p): Update.
	* python/py-type.c (typy_get_tag): Update.
	* p-typeprint.c (pascal_type_print_base): Update.
	* mdebugread.c (parse_symbol, parse_type): Update.
	* m2-typeprint.c (m2_long_set, m2_record_fields, m2_enum):
	Update.
	* guile/scm-type.c (gdbscm_type_tag): Update.
	* go-lang.c (sixg_string_p): Update.
	* gnu-v3-abi.c (build_gdb_vtable_type, build_std_type_info_type):
	Update.
	* gdbtypes.h (struct main_type) <tag_name>: Remove.
	(TYPE_TAG_NAME): Remove.
	* gdbtypes.c (type_name_no_tag): Simplify.
	(check_typedef, check_types_equal, recursive_dump_type)
	(copy_type_recursive, arch_composite_type): Update.
	* f-typeprint.c (f_type_print_base): Update.  Print "Type" prefix
	in summary mode when needed.
	* eval.c (evaluate_funcall): Update.
	* dwarf2read.c (fixup_go_packaging, read_structure_type)
	(process_structure_scope, read_enumeration_type)
	(read_namespace_type, read_module_type, determine_prefix): Update.
	* cp-support.c (inspect_type): Update.
	* coffread.c (process_coff_symbol, decode_base_type): Update.
	* c-varobj.c (c_is_path_expr_parent): Update.
	* c-typeprint.c (c_type_print_base_struct_union): Update.
	(c_type_print_base_1): Update.  Print struct/class/union/enum in
	summary when using C language.
	* ax-gdb.c (gen_struct_ref, gen_namespace_elt)
	(gen_maybe_namespace_elt): Update.
	* ada-lang.c (ada_type_name): Simplify.
	(empty_record, ada_template_to_fixed_record_type_1)
	(template_to_static_fixed_type)
	(to_record_with_fixed_variant_part, ada_check_typedef): Update.

gdb/testsuite/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* gdb.xml/tdesc-regs.exp (load_description): Update expected
	results.
	* gdb.dwarf2/method-ptr.exp: Set language to C++.
	* gdb.dwarf2/member-ptr-forwardref.exp: Set language to C++.
	* gdb.cp/typeid.exp (do_typeid_tests): Update type_re.
	* gdb.base/maint.exp (maint_pass_if): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Thread language through c_type_print_args
@ 2018-06-01 17:38 sergiodj+buildbot
  2018-06-01 18:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 17:38 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c1ec8cea7ff53eb76cb7c354b813c67fde755409 ***

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

Thread language through c_type_print_args

Currently dwarf2read.c will pass the CU's language to
c_type_print_args -- but this doesn't affect all aspects of type
printing, because some code in c-typeprint.c refers to
current_language.

This patch threads the language through more of the type printing
code, adding an overload to c_type_print.  Some uses of
current_language remain, but now they are only in top-level functions.

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (dwarf2_compute_name): Pass CU's language to
	c_print_type.
	* c-typeprint.c (c_print_type_1): Add "language" parameter.
	(c_print_type): Update.
	(c_print_type): New overload.
	(c_type_print_varspec_prefix, c_type_print_args)
	(c_type_print_varspec_suffix, c_print_type_no_offsets)
	(c_type_print_base_struct_union, c_type_print_base_1)
	(cp_type_print_method_args): Add "language" parameter.
	(c_type_print_base): Update.
	* c-lang.h (c_print_type): Add new overload.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make c_type_print_varspec_suffix static
@ 2018-06-01 17:11 sergiodj+buildbot
  2018-06-01 17:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 17:11 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bc8453a7bb617a5f14a465516f9f87c2ab6e05d5 ***

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

Make c_type_print_varspec_suffix static

I noticed that c_type_print_varspec_suffix is only called from
c-typeprint.c, so this patch makes it "static".

gdb/ChangeLog
2018-06-01  Tom Tromey  <tom@tromey.com>

	* typeprint.h (c_type_print_varspec_suffix): Don't declare.
	* c-typeprint.c (c_type_print_varspec_suffix): Now static.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add SVE register defines
@ 2018-06-01 16:14 sergiodj+buildbot
  2018-06-01 17:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01 16:14 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 739e8682ff1cffc2809c91853efeef232d29e582 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 739e8682ff1cffc2809c91853efeef232d29e582

Add SVE register defines

In order to prevent gaps in the register numbering, the Z registers
reuse the V register numbers (which become pseudos on SVE).

2018-06-01  Alan Hayward  <alan.hayward@arm.com>

	* aarch64-tdep.c (aarch64_sve_register_names): New const
	var.
	* arch/aarch64.h (enum aarch64_regnum): Add SVE entries.
	(AARCH64_SVE_Z_REGS_NUM): New define.
	(AARCH64_SVE_P_REGS_NUM): Likewise.
	(AARCH64_SVE_NUM_REGS): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: fold MOV to/from segment register templates
@ 2018-06-01  8:50 sergiodj+buildbot
  2018-06-01  8:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01  8:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 733bd0abdd059beff9d2c3be94fcd3b72fd44aaf ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 733bd0abdd059beff9d2c3be94fcd3b72fd44aaf

x86: fold MOV to/from segment register templates

First of all there's no point in having separate Cpu386 templates - the
respective SReg3 registers can't be specified for pre-386 anyway; see
parse_real_register().

And then we can also make use of D here for the memory forms of the
insn. This cannot be done for the non-64bit GPR forms because of the
IgnoreSize that cannot be dropped from the to-SREG variant.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86/Intel: accept "oword ptr" for INVPCID
@ 2018-06-01  7:37 sergiodj+buildbot
  2018-06-01  7:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01  7:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 647957107595c7f8209686577739240b7a222aba ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 647957107595c7f8209686577739240b7a222aba

x86/Intel: accept "oword ptr" for INVPCID

The insn is no different in this reagrd from INVEPT and INVVPID.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make _bfd_error_handler available outside libbfd
@ 2018-06-01  4:20 sergiodj+buildbot
  2018-06-01  4:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-06-01  4:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 030157d8a65afcc6292a4d3d183b816ed2ff7c57 ***

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

Make _bfd_error_handler available outside libbfd

Needed when building libopcodes.so.

bfd/
	* bfd.c (_bfd_error_handler): Arrange for this function to be
	declared in bfd-in2.h.
	* libbfd-in.h (_bfd_error_handler): Don't declare.
	* libbfd.h: Regenerate.
	* bfd-in2.h: Regenerate.
opcodes/
	* sysdep.h (_bfd_error_handler): Don't declare.
	* msp430-decode.opc: Include bfd.h.  Don't include ansidecl.h here.
	* rl78-decode.opc: Likewise.
	* msp430-decode.c: Regenerate.
	* rl78-decode.c: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix "set" handling of Python parameters
@ 2018-05-31 22:06 sergiodj+buildbot
  2018-05-31 22:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 22:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 984ee559a26e138d8bcc1f850c1cacb9eded2b1c ***

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

Fix "set" handling of Python parameters

It's long bothered me that setting a Python parameter from the CLI
will print the "set" help text by default.  I think usually "set"
commands should be silent.  And, while you can modify this behavior a
bit by providing a "get_set_string" method, if this method returns an
empty string, a blank line will be printed.

This patch removes the "help" behavior and changes the get_set_string
behavior to avoid printing a blank line.  The code has a comment about
preserving API behavior, but I don't think this is truly important;
and in any case the workaround -- implementing get_set_string -- is
trivial.

Regression tested on x86-64 Fedora 26.

2018-04-26  Tom Tromey  <tom@tromey.com>

	* NEWS: Mention new "set" behavior.
	* python/py-param.c (get_set_value): Don't print an empty string.
	Don't call get_doc_string.

gdb/doc/ChangeLog
2018-04-26  Tom Tromey  <tom@tromey.com>

	* python.texi (Parameters In Python): Update get_set_string
	documentation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add basic Python API for convenience variables
@ 2018-05-31 21:41 sergiodj+buildbot
  2018-05-31 21:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 21:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7729052b5377bfbf1c5ec5eaab59dd5071d4c5b1 ***

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

Add basic Python API for convenience variables

This adds a basic Python API for accessing convenience variables.
With this, convenience variables can be read and set from Python.
Although gdb supports convenience variables whose value changes at
each call, this is not exposed to Python; it could be, but I think
it's just as good to write a convenience function in this situation.

This is PR python/23080.

Tested on x86-64 Fedora 26.

2018-04-22  Tom Tromey  <tom@tromey.com>

	PR python/23080:
	* NEWS: Update for new functions.
	* python/py-value.c (gdbpy_set_convenience_variable)
	(gdbpy_convenience_variable): New functions.
	* python/python-internal.h (gdbpy_convenience_variable)
	(gdbpy_set_convenience_variable): Declare.
	* python/python.c (python_GdbMethods): Add convenience_variable,
	set_convenience_variable.

doc/ChangeLog
2018-04-22  Tom Tromey  <tom@tromey.com>

	PR python/23080:
	* python.texi (Basic Python): Document gdb.convenience_variable,
	gdb.set_convenience_variable.

testsuite/ChangeLog
2018-04-22  Tom Tromey  <tom@tromey.com>

	PR python/23080:
	* gdb.python/python.exp: Add convenience variable tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Function for reading the Aarch64 SVE vector length
@ 2018-05-31 14:18 sergiodj+buildbot
  2018-05-31 14:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 14:18 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 122394f1476b1c925a281b15399119500c8231c1 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 122394f1476b1c925a281b15399119500c8231c1

Function for reading the Aarch64 SVE vector length

Returns 0 for systems without SVE support.

Note the defines taken from Linux kernel headers
in aarch64-sve-linux-ptrace.h.

gdb/
	* Makefile.in: Add new header.
	* gdb/arch/aarch64.h (sve_vg_from_vl): New macro.
	(sve_vl_from_vg): Likewise.
	(sve_vq_from_vl): Likewise.
	(sve_vl_from_vq): Likewise.
	(sve_vq_from_vg): Likewise.
	(sve_vg_from_vq): Likewise.
	* configure.nat: Add new c file.
	* nat/aarch64-sve-linux-ptrace.c: New file.
	* nat/aarch64-sve-linux-ptrace.h: New file.

gdbserver/
	* configure.srv: Add new c/h file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add Aarch64 SVE target description
@ 2018-05-31 14:03 sergiodj+buildbot
  2018-05-31 14:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 14:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 95228a0d790f16deae3436e18f41b70fc711a5b2 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 95228a0d790f16deae3436e18f41b70fc711a5b2

Add Aarch64 SVE target description

No code uses the new descriptions yet.

gdb/
	* aarch64-linux-nat.c (aarch64_linux_read_description):
	Add parmeter zero.
	* aarch64-linux-tdep.c (aarch64_linux_core_read_description):
	Likewise.
	* aarch64-tdep.c (tdesc_aarch64_list): Add.
	(aarch64_read_description): Use VQ to index tdesc_aarch64_list.
	(aarch64_gdbarch_init): Add parmeter zero.
	* aarch64-tdep.h (aarch64_read_description): Add VQ parmeter.
	* arch/aarch64.c (aarch64_create_target_description): Check VQ.
	* arch/aarch64.h (aarch64_create_target_description): Add VQ.
	parmeter.
	* doc/gdb.texinfo: Describe SVE feature
	* features/aarch64-sve.c: New file.

gdbserver/
	* linux-aarch64-tdesc.c (aarch64_linux_read_description): Add
	null VQ.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] include: 2018-05-28 Bernd Edlinger <bernd.edlinger@hotmail.de>
@ 2018-05-31 11:05 sergiodj+buildbot
  2018-05-31 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 11:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 22467434fdc240e7c166f77f371909a8a07fc358 ***

Author: edlinger <edlinger@138bc75d-0d04-0410-961f-82ee72b054a4>
Branch: master
Commit: 22467434fdc240e7c166f77f371909a8a07fc358

include: 2018-05-28 Bernd Edlinger <bernd.edlinger@hotmail.de>

include:
        * splay-tree.h (splay_tree_compare_strings,
        splay_tree_delete_pointers): Declare new utility functions.

libiberty:
2018-05-28  Bernd Edlinger  <bernd.edlinger@hotmail.de>

        * splay-tree.c (splay_tree_compare_strings,
        splay_tree_delete_pointers): New utility functions.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@260850 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Improve boostrap-ubsan config (PR bootstrap/64914).
@ 2018-05-31 11:00 sergiodj+buildbot
  2018-05-31 10:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 11:00 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5b372a4d35bd5874c1a6db2b89f42c7ed3097c63 ***

Author: marxin <marxin@138bc75d-0d04-0410-961f-82ee72b054a4>
Branch: master
Commit: 5b372a4d35bd5874c1a6db2b89f42c7ed3097c63

Improve boostrap-ubsan config (PR bootstrap/64914).

2018-05-10  Martin Liska  <mliska@suse.cz>

	PR bootstrap/64914
	* md5.c: Use strict alignment with UBSAN_BOOTSTRAP.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@260112 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] * argv.c (expandargv): Fix memory leak for expanded arguments.
@ 2018-05-31 10:07 sergiodj+buildbot
  2018-05-31 10:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31 10:07 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4554bf70235e3ebb10521ddbcbb2bf17abe4865 ***

Author: law <law@138bc75d-0d04-0410-961f-82ee72b054a4>
Branch: master
Commit: e4554bf70235e3ebb10521ddbcbb2bf17abe4865

* argv.c (expandargv): Fix memory leak for expanded arguments.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@259775 138bc75d-0d04-0410-961f-82ee72b054a4


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Unset gdbarch significant_addr_bit by default
@ 2018-05-31  3:17 sergiodj+buildbot
  2018-05-31  3:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  3:17 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5969f0dba74e17c694faf333b120f1e0b95783ed ***

Author: Omair Javaid <omair.javaid@linaro.org>
Branch: master
Commit: 5969f0dba74e17c694faf333b120f1e0b95783ed

Unset gdbarch significant_addr_bit by default

This patch fixes a bug introduced by fix to AArch64 pointer tagging.

In our fix for tagged pointer support our agreed approach was to sign
extend user-space address after clearing tag bits. This is not same
for all architectures and this patch allows sign extension for
addresses on targets which specifically set significant_addr_bit.

More information about patch that caused the issues and discussion
around tagged pointer support can be found in links below:

https://sourceware.org/ml/gdb-patches/2018-05/msg00000.html
https://sourceware.org/ml/gdb-patches/2017-12/msg00159.html

gdb/ChangeLog:

2018-05-31  Omair Javaid  <omair.javaid@linaro.org>

	PR gdb/23210
	* gdbarch.sh (significant_addr_bit): Default to zero when
	not set by target architecture.
	* gdbarch.c: Re-generated.
	* utils.c (address_significant): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] (ARI) remove trailing newline in call to error in stack.c::func_command
@ 2018-05-31  2:45 sergiodj+buildbot
  2018-05-31  2:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  2:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 61367c61574e4d1f422e0f560672c4e63116fd7a ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 61367c61574e4d1f422e0f560672c4e63116fd7a

(ARI) remove trailing newline in call to error in stack.c::func_command

gdb/ChangeLog:

        * stack.c (func_command): Remove trailing newline in call to error.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_raw_supply
@ 2018-05-31  2:01 sergiodj+buildbot
  2018-05-31  2:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  2:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73e1c03f93f0294b464dc2b67de1f9aaae84838d ***

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

Remove regcache_raw_supply

Remove regcache_raw_supply, update callers to use
detached_regcache::raw_supply.

gdb/ChangeLog:

	* regcache.h (regcache_raw_supply): Remove, update callers to
	use detached_regcache::raw_supply.
	* regcache.c (regcache_raw_supply): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_cooked_write_part
@ 2018-05-31  1:41 sergiodj+buildbot
  2018-05-31  1:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  1:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4c4a59b48b2cec10cffac4f562937de00cb5f3f ***

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

Remove regcache_cooked_write_part

Remove regcache_cooked_write_part, update callers to use
regcache::cooked_write_part.

gdb/ChangeLog:

	* regcache.h (regcache_cooked_write_part): Remove, update
	callers to use regcache::cooked_write_part.
	* regcache.c (regcache_cooked_write_part): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_cooked_read_part
@ 2018-05-31  1:08 sergiodj+buildbot
  2018-05-31  1:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  1:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 73bb0000525a67694c1e8921e7c34ee0d985787e ***

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

Remove regcache_cooked_read_part

Remove regcache_cooked_read_part, update callers to use
readable_regcache::cooked_read_part.

gdb/ChangeLog:

	* regcache.h (regcache_cooked_read_part): Remove, update callers
	to use readable_regcache::cooked_read_part.
	* regcache.c (regcache_cooked_read_part): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_cooked_read_value
@ 2018-05-31  0:44 sergiodj+buildbot
  2018-05-31  0:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  0:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 46a45e9d5b067e484971e3972fa3eae0a224324f ***

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

Remove regcache_cooked_read_value

Remove regcache_cooked_read_value, update callers to use
readable_regcache::cooked_read_value.

gdb/ChangeLog:

	* regcache.h (regcache_cooked_read_value): Remove, update
	callers to use readable_regcache::cooked_read_value.
	* regcache.c (regcache_cooked_read_value): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_cooked_write
@ 2018-05-31  0:08 sergiodj+buildbot
  2018-05-31  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-31  0:08 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b66f5587de2a096f357124b20376b2bab980238b ***

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

Remove regcache_cooked_write

Remove regcache_cooked_write, update callers to use
regcache::cooked_write.

gdb/ChangeLog:

	* regcache.h (regcache_cooked_write): Remove, update callers to
	use regcache::cooked_write.
	* regcache.c (regcache_cooked_write): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_raw_write_part
@ 2018-05-30 23:40 sergiodj+buildbot
  2018-05-30 23:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 23:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4f0420fdabda76f462bd29a02d9be575e0e0cce7 ***

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

Remove regcache_raw_write_part

Remove regcache_raw_write_part, update callers to use
regcache::raw_write_part instead.

gdb/ChangeLog:

	* regcache.h (regcache_raw_write_part): Remove, update callers
	to use regcache::raw_write_part instead.
	* regcache.c (regcache_raw_write_part): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_raw_read_part
@ 2018-05-30 22:37 sergiodj+buildbot
  2018-05-30 22:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 22:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 502fe83eb549476fac09ec62c7fd66447791ba2a ***

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

Remove regcache_raw_read_part

Remove regcache_raw_read_part, update callers to use
readable_regcache::raw_read_part instead.

gdb/ChangeLog:

	* regcache.h (regcache_raw_read_part): Remove, update callers to
	use readable_regcache::raw_read_part instead.
	* regcache.c (regcache_raw_read_part): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_cooked_read
@ 2018-05-30 22:21 sergiodj+buildbot
  2018-05-30 22:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 22:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dca08e1fe158d04517ba3ddd7ece9dd1596c8e8c ***

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

Remove regcache_cooked_read

Remove regcache_cooked_read, update callers to use
readable_regcache::cooked_read instead.

gdb/ChangeLog:

	* regcache.h (regcache_cooked_read): Remove, update callers to
	use readable_regcache::cooked_read instead.
	* regcache.c (regcache_cooked_read): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_raw_read
@ 2018-05-30 21:34 sergiodj+buildbot
  2018-05-30 22:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 21:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b8835861cde41744a08f215b48fccd135815b63 ***

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

Remove regcache_raw_read

Remove regcache_raw_read, update all callers to use
readable_regcache::raw_read instead.

gdb/ChangeLog:

	* regcache.h (regcache_raw_read): Remove, update callers to use
	readable_regcache::raw_read instead.
	* regcache.c (regcache_raw_read): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_raw_update
@ 2018-05-30 20:58 sergiodj+buildbot
  2018-05-30 21:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 20:58 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b47d9858ca0805cd52ba959276d08899c7b9f8c ***

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

Remove regcache_raw_update

Remove regcache_raw_update, update callers to use
readable_regcache::raw_update instead.

gdb/ChangeLog:

	* regcache.h (regcache_raw_update): Remove, update callers to
	use readable_regcache::raw_update instead.
	* regcache.c (regcache_raw_update): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_register_status
@ 2018-05-30 20:37 sergiodj+buildbot
  2018-05-30 20:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 20:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ec9f11447514a797ae13760825fa45f9deedd8c ***

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

Remove regcache_register_status

Remove regcache_register_status, change callers to use
reg_buffer::get_register_status directly.

gdb/ChangeLog:

	* regcache.h (regcache_register_status): Remove, update callers
	to use reg_buffer::get_register_status directly instead.
	* regcache.c (regcache_register_status): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove regcache_get_ptid
@ 2018-05-30 20:01 sergiodj+buildbot
  2018-05-30 20:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 20:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 222312d359fe0a68f8583ba315583ee8cc94f252 ***

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

Remove regcache_get_ptid

Remove regcache_get_ptid, change all callers to call the regcache method
directly.

gdb/ChangeLog:

	* regcache.h (regcache_get_ptid): Remove, update all callers to
	call regcache::ptid instead.
	* regcache.c (regcache_get_ptid): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add or1k target to --enable-targets=all
@ 2018-05-30 16:57 sergiodj+buildbot
  2018-05-30 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 16:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT fdbe37e35fed48091296434652101a63fa4360cf ***

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

Add or1k target to --enable-targets=all

The or1k-tdep.o object is missing from the ALL_TARGET_OBS, which means
it's not currently included in an --enable-targets=all build.

gdb/ChangeLog:

	* Makefile.in (ALL_TARGET_OBS): Add or1k-tdep.o.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Mark END_CATCH as ATTRIBUTE_NORETURN (-Wmaybe-uninitialized warnings)
@ 2018-05-30 15:56 sergiodj+buildbot
  2018-05-30 15:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30 15:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT f7c6f42310233479ea6339430b7c1ca1f9ec68e1 ***

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

Mark END_CATCH as ATTRIBUTE_NORETURN (-Wmaybe-uninitialized warnings)

This commit fixes a set of -Wmaybe-uninitialized warnings in GDB and
GDBserver, seen with GCC 7.3.1 on F27 at -O2.  Specifically, all of
these:

 src/gdb/breakpoint.c:5040:4: warning: e may be used uninitialized in this function [-Wmaybe-uninitialized]
 src/gdb/cli/cli-cmds.c:277:71: warning: tracker may be used uninitialized in this function [-Wmaybe-uninitialized]
 src/gdb/cli/cli-cmds.c:302:22: warning: word may be used uninitialized in this function [-Wmaybe-uninitialized]
 src/gdb/gdbserver/server.c:1895:7: warning: result may be used uninitialized in this function [-Wmaybe-uninitialized]
 src/gdb/gdbserver/server.c:1966:7: warning: result may be used uninitialized in this function [-Wmaybe-uninitialized]

For example, looking at one of the gdbserver ones in more detail:

 ../../../src/gdb/gdbserver/server.c: In function int handle_qxfer_btrace_conf(const char*, gdb_byte*, const gdb_byte*, ULONGEST, LONGEST):
 ../../../src/gdb/gdbserver/server.c:1966:7: warning: result may be used uninitialized in this function [-Wmaybe-uninitialized]
	if (result != 0)
	^~

In this case (like the others), the 'result' variable is assigned in
both TRY and CATCH blocks:

      TRY
        {
          result = target_read_btrace_conf (thread->btrace, &cache);
          if (result != 0)
            memcpy (own_buf, cache.buffer, cache.used_size);
        }
      CATCH (exception, RETURN_MASK_ERROR)
        {
          sprintf (own_buf, "E.%s", exception.message);
          result = -1;
        }
      END_CATCH

      if (result != 0)
        return -3;

so it would seem like the warning is bogus.

However, END_CATCH is really a catch block in disguise, and that path
indeed does not initialize the variable:

#define END_CATCH				\
    catch (...)					\
      {						\
	exception_rethrow ();			\
      }						\
  }

exception_rethrow does not return normally (it rethrows the current
exception after running cleanups), but the compiler can not see that.
If it could return normally, then indeed 'result' could be used
uninitialized if the TRY block threw some non-gdb exception, which
would be caught by END_CATCH.

The fix it to let the compiler know that the exception_rethrow does
not return normally, using ATTRIBUTE_NORETURN.

gdb/ChangeLog:
2018-05-30  Pedro Alves  <palves@redhat.com>

	* common/common-exceptions.h (exception_rethrow): Use
	ATTRIBUTE_NORETURN.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add znver2 support.
@ 2018-05-30  8:52 sergiodj+buildbot
  2018-05-30 13:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30  8:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a9660a6f4063c7e1fb892ec709c954c56896ab8d ***

Author: Amit Pawar <Amit.Pawar@amd.com>
Branch: master
Commit: a9660a6f4063c7e1fb892ec709c954c56896ab8d

Add znver2 support.

	gas/
	* config/tc-i386.c (cpu_flag_init): Add CPU_ZNVER2_FLAGS.
	* doc/c-i386.texi : Document znver2.
	* gas/testsuite/gas/i386/arch-13.s: Updated for znver2.
	* gas/testsuite/gas/i386/arch-13.d: Updated.
	* gas/testsuite/gas/i386/arch-13-znver1.d: Updated.
	* gas/testsuite/gas/i386/arch-13-znver2.d: New file.
	* gas/testsuite/gas/i386/x86-64-arch-3.s: Updated for znver2.
	* gas/testsuite/gas/i386/x86-64-arch-3.d: Updated.
	* gas/testsuite/gas/i386/x86-64-arch-3-znver1.d: Updated.
	* gas/testsuite/gas/i386/x86-64-arch-3-znver2.d: New file.
	* gas/testsuite/gas/i386/i386.exp: Updated for new test.

	opcode/
	* i386-gen.c (cpu_flag_init): Add CPU_ZNVER2_FLAGS.
	* i386-init.h : Regenerated.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove "struct" keyword in range-based for loops
@ 2018-05-30  1:23 sergiodj+buildbot
  2018-05-30  2:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30  1:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5294170687db7d997a00f88b765ef353121aa441 ***

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

Remove "struct" keyword in range-based for loops

I get this kind of errors with GCC 6.3.0:

/home/simark/src/binutils-gdb/gdb/breakpoint.c: In function 'void print_solib_event(int)':
/home/simark/src/binutils-gdb/gdb/breakpoint.c:4618:12: error: types may not be defined in a for-range-declaration [-Werror]
       for (struct so_list *iter : current_program_space->added_solibs)
            ^~~~~~

Removing the struct keyword makes it happy.

gdb/ChangeLog:

	* breakpoint.c (print_solib_event, check_status_catch_solib):
	Remove struct keyword in range-based for loops.
	* dbxread.c (find_corresponding_bincl_psymtab): Likewise.
	* dwarf2read.c (compute_delayed_physnames, rust_union_quirks);
	Likewise.
	* linespec.c (find_superclass_methods, search_minsyms_for_name):
	Likewise.
	* symfile.c (addr_info_make_relative): Likewise.
	* thread.c (value_in_thread_stack_temporaries): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Removing lookup_minimal_symbol_and_objfile
@ 2018-05-30  0:37 sergiodj+buildbot
  2018-05-30  0:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-30  0:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 64cc34d87089ff24b43e0a8760be132b7afa6f34 ***

Author: Weimin Pan <weimin.pan@oracle.com>
Branch: master
Commit: 64cc34d87089ff24b43e0a8760be132b7afa6f34

Removing lookup_minimal_symbol_and_objfile

Function lookup_minimal_symbol_and_objfile iterates on all objfiles and
calls lookup_minimal_symbol for each of them, effectively searching in all
objfiles.  lookup_bound_minimal_symbol calls lookup_minimal_symbol with NULL,
which also effectively searches all objfiles.  AFAIK, they do exactly the same
thing, so we can get rid of one (and lookup_minimal_symbol_and_objfile happens
to be the most inefficient because it ends up n^2 on the number of objfiles).

Tested in both aarch64-linux-gnu and amd64-linux-gnu. No regressions.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix fall-through comment in windows-nat.c
@ 2018-05-29 23:51 sergiodj+buildbot
  2018-05-29 23:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-29 23:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e7ec8713ec12a633fcdfc5524c9ee050389b6f9d ***

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

Fix fall-through comment in windows-nat.c

Now that the mingw builder in the buildbot is working again, it
pointed out a build failure due to a missing fall-through comment in
windows-nat.c.  This patch fixes the problem.

Tested by first triggering the failure with a local mingw build, then
by rebuilding successfully with the patch.

I'm checking this in as obvious.

gdb/ChangeLog
2018-05-29  Tom Tromey  <tom@tromey.com>

	* windows-nat.c (handle_exception): Update fall-through comment.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change program_space::added_solibs to a std::vector
@ 2018-05-29 19:05 sergiodj+buildbot
  2018-05-29 20:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-29 19:05 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bcb430e4cd5bcd913813236536031f1fc7f72aee ***

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

Change program_space::added_solibs to a std::vector

This changes program_space::added_solibs to a std::vector, removing a
VEC.

Tested by the buildbot.

gdb/ChangeLog
2018-05-29  Tom Tromey  <tom@tromey.com>

	* progspace.h (so_list_ptr): Remove typedef.  Don't declare VEC.
	(struct program_space) <added_solibs>: Now a std::vector.
	* breakpoint.c (print_solib_event): Update.
	(check_status_catch_solib): Update.
	* progspace.c (clear_program_space_solib_cache): Update.
	* solib.c (update_solib_list): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a VEC from type.c
@ 2018-05-29 18:44 sergiodj+buildbot
  2018-05-29 18:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-29 18:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 894882e344735ace5231f179484086f7697d27cc ***

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

Remove a VEC from type.c

This removes a VEC from type.c, by using std::vector.

While doing this I also took the opportunity to change
types_deeply_equal to return bool.  This caught some weird code in
typy_richcompare, now fixed.

And, since I was changing types_deeply_equal, it seemed like a good
idea to also change types_equal, so this patch includes that as well.

Tested by the buildbot.

ChangeLog
2018-05-29  Tom Tromey  <tom@tromey.com>

	* python/py-type.c (typy_richcompare): Update.
	* guile/scm-type.c (tyscm_equal_p_type_smob): Update.
	* gdbtypes.h (types_deeply_equal): Return bool.
	(types_equal): Likewise.
	* gdbtypes.c (type_equality_entry_d): Remove typedef.  Don't
	declare VEC.
	(check_types_equal): Change worklist to std::vector.  Return
	bool.
	(struct type_equality_entry): Add constructor.
	(compare_maybe_null_strings): Return bool.
	(check_types_worklist): Return bool.  Change worklist to
	std::vector.
	(types_deeply_equal): Use std::vector.
	(types_equal): Return bool.
	(compare_maybe_null_strings): Simplify.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove tp_t typedef
@ 2018-05-29 16:25 sergiodj+buildbot
  2018-05-29 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-29 16:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 10b2ded43caa3298cded1df8b620caaaee3f9209 ***

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

Remove tp_t typedef

The tp_t typedef is no longer used and can be removed.

ChangeLog
2018-05-29  Tom Tromey  <tom@tromey.com>

	* record-btrace.c (tp_t): Remove typedef.  Don't declare VEC.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86-64: Add TLSDESC fields to elf_x86_lazy_plt_layout
@ 2018-05-28 19:57 sergiodj+buildbot
  2018-05-28 18:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-28 19:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 92e68c1d65f844c0027f471a0c9e1722d781ef7d ***

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

x86-64: Add TLSDESC fields to elf_x86_lazy_plt_layout

ENDBR64 is added to the special TLSDESC entry, which is similar to the
PLT0 entry, in the x86-64 lazy procedure linkage table to support Intel
CET.  The NaCl PLT is different from the normal PLT.  This patch adds
plt_tlsdesc_entry, plt_tlsdesc_entry_size, plt_tlsdesc_got1_offset,
plt_tlsdesc_got2_offset, plt_tlsdesc_got1_insn_end and
plt_tlsdesc_got2_insn_end to elf_x86_lazy_plt_layout to support both
normal and NaCl TLSDESC entries.  This fixed

FAIL: TLS descriptor -fpic -shared transitions

for x86_64-nacl.

	* elf32-i386.c (elf_i386_lazy_plt): Add plt_tlsdesc_entry,
	plt_tlsdesc_entry_size, plt_tlsdesc_got1_offset,
	plt_tlsdesc_got2_offset, plt_tlsdesc_got1_insn_end and
	plt_tlsdesc_got2_insn_end for TLSDESC entry.
	(elf_i386_lazy_ibt_plt): Likewise.
	(elf_i386_nacl_plt): Likewise.
	* elf64-x86-64.c (tlsdesc_plt_entry): Moved and renamed to ...
	(elf_x86_64_tlsdesc_plt_entry): This.
	(elf_x86_64_lazy_plt): Add plt_tlsdesc_entry,
	plt_tlsdesc_entry_size, plt_tlsdesc_got1_offset,
	plt_tlsdesc_got2_offset, plt_tlsdesc_got1_insn_end and
	plt_tlsdesc_got2_insn_end for TLSDESC entry.
	(elf_x86_64_lazy_bnd_plt): Likewise.
	(elf_x86_64_lazy_ibt_plt): Likewise.
	(elf_x32_lazy_ibt_plt): Likewise.
	(elf_x86_64_nacl_plt): Likewise.
	(elf_x86_64_finish_dynamic_sections): Use plt_tlsdesc_entry,
	plt_tlsdesc_entry_size, plt_tlsdesc_got1_offset,
	plt_tlsdesc_got2_offset, plt_tlsdesc_got1_insn_end and
	plt_tlsdesc_got2_insn_end to update TLSDESC entry.
	* elfxx-x86.h (elf_x86_lazy_plt_layout): Update comments.
	Add plt_tlsdesc_entry, plt_tlsdesc_entry_size,
	plt_tlsdesc_got1_offset, plt_tlsdesc_got2_offset,
	plt_tlsdesc_got1_insn_end and plt_tlsdesc_got2_insn_end.
	(elf_x86_non_lazy_plt_layout): Update comments.
	(elf_x86_plt_layout): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] ld: Unify STT_GNU_IFUNC handling
@ 2018-05-28 16:20 sergiodj+buildbot
  2018-05-28 16:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-28 16:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ac98f9e2275ffcca560eaa0bddd282a1ff94fc28 ***

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

ld: Unify STT_GNU_IFUNC handling

Take STT_GNU_IFUNC handling scattered across targets and gather it in
the generic ELF linker.

bfd/

	PR ld/23238
	* elf-s390-common.c (elf_s390_add_symbol_hook): Removed.
	* elf32-arc.c (elf_arc_add_symbol_hook): Likewise.
	(elf_backend_add_symbol_hook): Likewise.
	* elf32-m68k.c (elf_m68k_add_symbol_hook): Likewise.
	(elf_backend_add_symbol_hook): Likewise.
	* elf32-s390.c (elf_backend_add_symbol_hook): Likewise.
	* elf32-sparc.c (elf32_sparc_add_symbol_hook): Likewise.
	(elf_backend_add_symbol_hook): Likewise.
	* elf64-s390.c (elf_backend_add_symbol_hook): Likewise.
	* elfxx-aarch64.c (_bfd_aarch64_elf_add_symbol_hook): Likewise.
	* elfxx-aarch64.h (_bfd_aarch64_elf_add_symbol_hook): Likewise.
	(elf_backend_add_symbol_hook): Likewise.
	* elf32-arm.c (elf32_arm_add_symbol_hook): Remove STT_GNU_IFUNC
	handling.
	* elf32-ppc.c (ppc_elf_add_symbol_hook): Likewise.
	* elf64-ppc.c (ppc64_elf_add_symbol_hook): Likewise.
	* elf64-sparc.c (elf64_sparc_add_symbol_hook): Likewise.
	* elflink.c (elf_link_add_object_symbols): Set
	elf_gnu_symbol_ifunc for STT_GNU_IFUNC symbols.

ld/

	PR ld/23238
	* testsuite/ld-ifunc/ifunc-26.d: New file.
	* testsuite/ld-ifunc/ifunc-26.s: Likewise.
	* testsuite/ld-ifunc/ifunc.exp: Run *.d tests without a
	working compiler.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove last reference to REMOTE_OBS
@ 2018-05-27 22:16 sergiodj+buildbot
  2018-05-27 21:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-27 22:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b8283aea9e599f17dbae7f52223994e3a9168143 ***

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

Remove last reference to REMOTE_OBS

REMOTE_OBS was removed from Makefile.in in
18ca73470a0d7eb96a807c97559cbb9fddb4b461, but one reference remains.
This patch removes the lingerer.

ChangeLog
2018-05-27  Tom Tromey  <tom@tromey.com>

	* Makefile.in (DEPFILES): Don't reference REMOTE_OBS.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Clear entire "location" in value constructor
@ 2018-05-25 22:57 sergiodj+buildbot
  2018-05-25 23:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 22:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 41a883c8edf98e86176d007bc8ad1c86c9675528 ***

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

Clear entire "location" in value constructor

My recent change to allocate values with "new" may have introduced a
small bug.  In particular, the previous code allocated with XCNEW, but
the new code only clears a part of the "location" field in the
constructor.  I didn't try very hard to actually trigger a bug here,
the problem remains theoretical.

This patch just arranges to initialize the entire location.

Regression tested by the buildbot.

2018-05-25  Tom Tromey  <tom@tromey.com>

	* value.c (value::location): Initialize.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove interp_name
@ 2018-05-25 20:59 sergiodj+buildbot
  2018-05-25 21:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 20:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da505cff6e29b18244dc9f6886bcb4d436263dee ***

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

Remove interp_name

This removes the interp_name function.  It is only used a few spots --
one of which was only calling it on "this".  It's simpler to remove
it; and should class interp become opaque in the future, it will be
just as easy to update the two remaining spots to use an accessor.

ChangeLog
2018-05-25  Tom Tromey	<tom@tromey.com>

	* interps.c (interp_name): Remove.
	* mi/mi-interp.c (mi_interp::init): Update.
	* interps.h (interp_name): Remove.
	(~scoped_restore_interp): Update.
	* tui/tui.c (tui_enable): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Change the as_*_interp functions to use dynamic_cast
@ 2018-05-25 20:32 sergiodj+buildbot
  2018-05-25 20:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 20:32 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 716b8bc52eef6044f1ff361e3e2eeb9307849034 ***

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

Change the as_*_interp functions to use dynamic_cast

This changes the various as_*_interp functions to be implemented using
dynamic_cast.  I believe this is a small improvement, because it is
more typesafe -- the C++ runtime does the type-checking for us.

ChangeLog
2018-05-25  Tom Tromey  <tom@tromey.com>

	* tui/tui-interp.c (as_tui_interp): Use dynamic_cast.
	* mi/mi-interp.c (as_mi_interp): Use dynamic_cast.
	* cli/cli-interp.c (as_cli_interp): Use dynamic_cast.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use scoped_restore in a couple of interp-related places
@ 2018-05-25 19:42 sergiodj+buildbot
  2018-05-25 20:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 19:42 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 753ff9bd837e2ba183e3ff789847a81221561392 ***

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

Use scoped_restore in a couple of interp-related places

While looking through the "interp" code I found a couple of spots that
could use scoped_restore.

ChangeLog
2018-05-25  Tom Tromey  <tom@tromey.com>

	* cli/cli-interp.c (safe_execute_command): Use scoped_restore.
	* interps.c (interp_exec): Use scoped_restore.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use gdb::byte_vector in remote.c
@ 2018-05-25 17:52 sergiodj+buildbot
  2018-05-25 18:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 17:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 5ca3b2605cc9ab5b33032c6478147366be60cd95 ***

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

Use gdb::byte_vector in remote.c

This changes a couple of spots in remote.c to use gdb::byte_vector,
allowing for some cleanup removal.

ChangeLog
2018-05-25  Tom Tromey  <tom@tromey.com>

	* remote.c (remote_target::remote_file_get): Use
	gdb::byte_vector.
	(remote_target::remote_file_put): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanups from coff-pe-read.c
@ 2018-05-25 17:20 sergiodj+buildbot
  2018-05-25 17:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 17:20 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3173aa2fc212389268f76433e70b35116a936a8d ***

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

Remove cleanups from coff-pe-read.c

This removes cleanups from coff-pe-read.c, using std::string,
std::vector, and gdb::def_vector.

Tested by the buildbot, though I'm not sure these code paths are
exercised there.

ChangeLog
2018-05-25  Tom Tromey  <tom@tromey.com>

	* coff-pe-read.c (struct read_pe_section_data) <section_name>: Now
	a std::string.
	(get_pe_section_index, add_pe_exported_sym): Update.
	(read_pe_exported_syms): Use gdb::def_vector.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use TRY/CATCH in remove_prev_frame
@ 2018-05-25 15:49 sergiodj+buildbot
  2018-05-25 17:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 15:49 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 09a5e1b570eefbc029939fd43c99152996060d95 ***

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

Use TRY/CATCH in remove_prev_frame

This changes remove_prev_frame to use TRY/CATCH instead of a cleanup.
TRY/CATCH seemed appropriate here because the cleanup is only needed
in the case where an exception is thrown.

Tested by the buildbot.

ChangeLog
2018-05-25  Tom Tromey  <tom@tromey.com>

	* frame.c (remove_prev_frame): Remove.
	(get_prev_frame_if_no_cycle): Use TRY/CATCH.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote_target::m_remote_state, pointer -> object
@ 2018-05-25 11:59 sergiodj+buildbot
  2018-05-25 11:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25 11:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3c69da406c72423afa4bd0e4fc4c805ec0b944a1 ***

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

remote_target::m_remote_state, pointer -> object

The only reason remote_target::m_remote_state is a pointer is that
struct remote_state is incomplete when struct remote_target is
defined.

This commit thus moves struct remote_state (and its dependencies)
higher up and makes remote_target::m_remote_state an object instead of
a pointer.

gdb/ChangeLog:
2018-05-25  Pedro Alves  <palves@redhat.com>

	* remote.c (struct vCont_action_support, MAXTHREADLISTRESULTS)
	(struct readahead_cache, struct packet_reg, struct
	remote_arch_state, class remote_state): Move higher up in the
	file.
	(remote_target::m_remote_state): Now an object instead of a pointer.
	(remote_target::get_remote_state): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] s12z regen
@ 2018-05-25  7:27 sergiodj+buildbot
  2018-05-25  9:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25  7:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 277eb7f64ae0c949715751a382350368ef14e95e ***

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

s12z regen

This patch regenerates a number of files that either were edited by
hand or not regenerated when s12z support was added to binutils.

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


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix hidden visibility compiler test
@ 2018-05-25  7:02 sergiodj+buildbot
  2018-05-25  6:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25  7:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 629dabe3b731c6194499652301935f34c3c20e0c ***

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

Fix hidden visibility compiler test

Warnings from configure tests aren't usually checked.  gcc's
"visibility attribute not supported in this configuration" warning is
enabled by default so we don't need to add any warning flag except
-Werror.

	* configure.ac (bfd_cv_hidden): Run test with -Werror in CFLAGS.
	* configure: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PATCH (obvious): Fix a comment, and pass stream to cb_data.
@ 2018-05-25  1:35 sergiodj+buildbot
  2018-05-25  1:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25  1:35 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d392224a0942df2f23b1149a71f62afc7f34beb8 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: d392224a0942df2f23b1149a71f62afc7f34beb8

PATCH (obvious): Fix a comment, and pass stream to cb_data.

iterate_over_block_arg_vars is a void function, so does
not return 1 or 0.
print_frame_arg_vars tells it prints on STREAM,
so pass STREAM in the cb_data, not gdb_stdout.

gdb/ChangeLog

2018-05-24  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* stack.c (iterate_over_block_arg_vars): Fix comment.
	(print_frame_arg_vars): Pass stream in cb_data, not gdb_stdout.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text in record.c
@ 2018-05-25  0:21 sergiodj+buildbot
  2018-05-25  0:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-25  0:21 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a974b5ec9a253d330290d132098065b77f29bd36 ***

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

Update help text in record.c

This updates some help text in record.c to conform to GNU standards.
I also added a "Usage" line to "record save".

2018-04-29  Tom Tromey  <tom@tromey.com>

	* record.c (_initialize_record): Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text in linux-fork.c
@ 2018-05-24 23:53 sergiodj+buildbot
  2018-05-25  0:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 23:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT c8a15b78e676b9101045b729a38128cbe5673701 ***

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

Update help text in linux-fork.c

This updates some help text in linux-fork.c to conform to GNU
standards.

2018-04-29  Tom Tromey  <tom@tromey.com>

	* linux-fork.c (_initialize_linux_fork): Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text in record-btrace.c
@ 2018-05-24 23:52 sergiodj+buildbot
  2018-05-24 23:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 23:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 55063ddb8e9a3179b65047db21f4c8607782d075 ***

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

Update help text in record-btrace.c

This updates the help text in record-btrace.c to conform to GNU
standards.

2018-04-29  Tom Tromey  <tom@tromey.com>

	* record-btrace.c (_initialize_record_btrace): Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text in tracepoint.c
@ 2018-05-24 22:52 sergiodj+buildbot
  2018-05-24 22:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 22:52 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 02d016b71fd38648fad589c1557b83135b1dd552 ***

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

Update help text in tracepoint.c

This changes the help text of a couple of commands in tracepoint.c to
follow the GNU style.

ChangeLog
2018-04-29  Tom Tromey  <tom@tromey.com>

	* tracepoint.c (_initialize_tracepoint): Update help text.

testsuite/ChangeLog
2018-04-30  Tom Tromey  <tom@tromey.com>

	* gdb.trace/tfind.exp: Update help tests.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text in disasm.c
@ 2018-05-24 22:04 sergiodj+buildbot
  2018-05-24 22:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 22:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7c9ee61b9f5fcad94fda11af1ab7469d78f17fbe ***

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

Update help text in disasm.c

This changes some help text in disasm.c to follow the GNU style.

2018-04-29  Tom Tromey  <tom@tromey.com>

	* disasm.c (_initialize_disasm): Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text for "jump" command
@ 2018-05-24 21:53 sergiodj+buildbot
  2018-05-24 22:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 21:53 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0a8ba311d0c4facef158af3d79c78489d5efcc4b ***

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

Update help text for "jump" command

This updates the usage text for the "jump" command to conform to the
GNU style.

2018-04-29  Tom Tromey  <tom@tromey.com>

	* infcmd.c (_initialize_infcmd): Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help text in dcache.c
@ 2018-05-24 21:16 sergiodj+buildbot
  2018-05-24 21:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ffb2b66cabe9deefefa1312ef0b7bb064656e611 ***

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

Update help text in dcache.c

This updates some text in dcache.c to follow GNU standards.
Here, I found a couple of spots needing an update.

2018-04-29  Tom Tromey  <tom@tromey.com>

	* dcache.c (dcache_info_1): Update usage text.
	(_initialize_dcache): Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help strings in TUI
@ 2018-05-24 21:10 sergiodj+buildbot
  2018-05-24 21:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 21:10 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bf212be198a7dd7700e08862f241ed85f88408e3 ***

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

Update help strings in TUI

This updates some help strings in the TUI to more closely follow GNU
standards.  In this case I chose to reuse some existing "usage" macros
in the help text.  Also, I found that XDBWIN_HEIGHT_USAGE is unused,
so I removed it.

ChangeLog
2018-04-29  Tom Tromey  <tom@tromey.com>

	* tui/tui-layout.c (_initialize_tui_layout): Update help text.
	* tui/tui-win.c (WIN_HEIGHT_USAGE, FOCUS_USAGE): Update
	(XDBWIN_HEIGHT_USAGE): Remove.
	(_initialize_tui_win): Use macros.  Update help text.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update memattr.c help strings
@ 2018-05-24 20:37 sergiodj+buildbot
  2018-05-24 20:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 20:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 99806209a4f89fc76d338982239ab8c214df4b4d ***

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

Update memattr.c help strings

This changes memattr.c to use the GNU style for help strings.

2018-04-29  Tom Tromey  <tom@tromey.com>

	* memattr.c (_initialize_mem): Update help string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update core-related help strings
@ 2018-05-24 20:12 sergiodj+buildbot
  2018-05-24 20:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 20:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0cab2f1e91f92130c5e0d89a99ce639ebd8ec1b0 ***

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

Update core-related help strings

This updates some help strings in corefile.c and gcore.c.

2018-04-27  Tom Tromey  <tom@tromey.com>

	* corefile.c (_initialize_core): Update help string.
	* gcore.c (_initialize_gcore): Update help string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Update help strings in skip.c
@ 2018-05-24 20:09 sergiodj+buildbot
  2018-05-24 20:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 20:09 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 784e4b3e80c1093203ae1a0da33be7a670942713 ***

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

Update help strings in skip.c

This changes help strings in skip.c to follow the GNU style.

2018-04-27  Tom Tromey  <tom@tromey.com>

	* skip.c (_initialize_step_skip): Update help strings.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb: Restore selected frame in print_frame_local_vars
@ 2018-05-24 18:01 sergiodj+buildbot
  2018-05-24 18:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 18:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 45f25d6c83c31a48a01ef8293bb3978f5e58e653 ***

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

gdb: Restore selected frame in print_frame_local_vars

PR gdb/23203 reports 'bt full' causing the currently selected frame to
change, this issue is fixed in this commit.

Add a new class scoped_restore_selected_frame that saves and restores
the selected frame.  Make use of this in print_frame_local_vars to
restore the selected frame on exit.

gdb/ChangeLog:

	PR gdb/23203
	* frame.c
	(scoped_restore_selected_frame::scoped_restore_selected_frame):
	Define.
	(scoped_restore_selected_frame::~scoped_restore_selected_frame):
	Define.
	* frame.h (class scoped_restore_selected_frame): New class.
	* stack.c (print_frame_local_vars): Remove catching and rethrowing
	of any exception, use scoped_restore_selected_frame to restore the
	frame instead.

gdb/testsuite/ChangeLog:

	PR gdb/23203
	* gdb.base/bt-selected-frame.c: New file.
	* gdb.base/bt-selected-frame.exp: New file.
	* lib/gdb.exp (get_current_frame_number): New function.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] testsuite: Extend TLS core file testing with an OS-generated dump
@ 2018-05-24 15:23 sergiodj+buildbot
  2018-05-24 15:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 15:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d9f6d7f8b636a2b32004273143d72a77d82b40de ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: d9f6d7f8b636a2b32004273143d72a77d82b40de

testsuite: Extend TLS core file testing with an OS-generated dump

Complementing commit 280ca31f4d60 ("Add test for fetching TLS from
core file") extend gdb.threads/tls-core.exp with an OS-generated dump
where supported.

This verifies not only that our core dump interpreter is consistent
with our producer, but that it matches the OS verified as well,
avoiding a possible case where our interpreter would be bug-compatible
with our producer but not the OS and it would go unnoticed in testing.

This results in:

 PASS: gdb.threads/tls-core.exp: native: load core file
 PASS: gdb.threads/tls-core.exp: native: print thread-local storage variable
 PASS: gdb.threads/tls-core.exp: gcore: load core file
 PASS: gdb.threads/tls-core.exp: gcore: print thread-local storage variable

with local testing and:

 UNSUPPORTED: gdb.threads/tls-core.exp: native: load core file
 UNSUPPORTED: gdb.threads/tls-core.exp: native: print thread-local storage variable
 PASS: gdb.threads/tls-core.exp: gcore: load core file
 PASS: gdb.threads/tls-core.exp: gcore: print thread-local storage variable

with remote testing, or for testing on ports that don't supports
cores.

gdb/testsuite/ChangeLog:
2018-05-24  Maciej W. Rozycki  <macro@mips.com>
	    Pedro Alves  <palves@redhat.com>

	* gdb.threads/tls-core.c: Include <stdlib.h>
	(thread_proc): Call `abort'.
	* gdb.threads/tls-core.exp: Generate a core with core_find too.
	(tls_core_test): New procedure, bits factored out from ...
	(top level): ... here.  Test both native cores and gcore cores.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix macOS build, missing override
@ 2018-05-24 13:02 sergiodj+buildbot
  2018-05-24 14:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-24 13:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT da05d921f0b7b9f9f07ac4e78ee228e7ecf847e0 ***

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

Fix macOS build, missing override

Fixes:

In file included from ../../src/gdb/darwin-nat.c:63:0:
../../src/gdb/darwin-nat.h:28:8: error: 'virtual void darwin_nat_target::create_inferior(const char*, const string&, char**, int)' can be marked override [-Werror=suggest-override]
   void create_inferior (const char *exec_file,
        ^

gdb/ChangeLog:
2018-05-24  Pedro Alves  <palves@redhat.com>

	* darwin-nat.h (darwin_nat_target::create_inferior): Mark with
	override.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add ATTRIBUTE_NONSTRING to ppc64_elf_write_core_note
@ 2018-05-23 20:46 sergiodj+buildbot
  2018-05-23 20:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 20:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9ef6d1e31f380349c8f329d1adb47ee53ec1f6c2 ***

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

Add ATTRIBUTE_NONSTRING to ppc64_elf_write_core_note

This patch silences gcc8 -Wstringop-truncation warnings.

	* elf64-ppc.c (ppc64_elf_write_core_note): Add ATTRIBUTE_NONSTRING
	to data.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove struct complaints
@ 2018-05-23 20:13 sergiodj+buildbot
  2018-05-23 20:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 20:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT a8be540e8ae8d16da5854c75d4724f3875aeba2e ***

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

Remove struct complaints

struct complaints now just holds a single enum value, so remove it and
symfile_complaint_book and replace it with a global variable.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (struct complaints): Remove.
	(symfile_complaint_book): Remove.
	(series): New global.
	(complaint_internal): Update.
	(clear_complaints): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove struct complain
@ 2018-05-23 19:44 sergiodj+buildbot
  2018-05-23 20:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 19:44 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ff1cf532dbabdee0d34974a77809bf2fa23d43a5 ***

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

Remove struct complain

At this point, struct complain is just holds a key, a value, and a
"next" pointer to form a linked list.  It's simpler to replace this
with an unordered map.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (counters): New global.
	(struct complain): Remove.
	(struct complaints) <root>: Remove.
	(complaint_sentinel): Remove.
	(symfile_complaint_book): Update.
	(find_complaint) Remove.
	(complaint_internal, clear_complaints): Update.

gdb/testsuite/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* gdb.gdb/complaints.exp (test_initial_complaints): Simplify.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove file and line from struct complain
@ 2018-05-23 19:22 sergiodj+buildbot
  2018-05-23 19:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 19:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ff8817441fcebe3d32343dbd9d514366bfe8e23 ***

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

Remove file and line from struct complain

The file and line handling in complaints.c wasn't used once
internal_complaint was removed.  This patch removes all the related
code.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (struct complain) <file, line>: Remove.
	(find_complaint): Remove file, line parameters.
	(complaint_internal): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove struct explanation
@ 2018-05-23 18:12 sergiodj+buildbot
  2018-05-23 18:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 18:12 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2ac237e52beb08e09037ff917924319246b5ea6d ***

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

Remove struct explanation

Now that there's only a single reason for a complaint to be emitted,
this removes "struct explanation" and changes vcomplaint to emit the
desired messages directly.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (struct complaints) <explanation>: Remove.
	(symfile_explanations): Remove.
	(symfile_complaint_book): Update.
	(vcomplaint): Update.
	(struct explanation): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove symfile_complaints
@ 2018-05-23 17:33 sergiodj+buildbot
  2018-05-23 17:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 17:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b98664d3862579c5a0d23901b1e2fc1f595f39ff ***

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

Remove symfile_complaints

The complaint system seems to allow for multiple different complaint
topics.  However, in practice only symfile_complaints has ever been
defined.  Seeing that complaints.c dates to 1992, and that no new
complaints have been added in the intervening years, I think it is
reasonable to admit that complaints are specifically related to
debuginfo reading.

This patch removes symfile_complaints and updates all the callers.
Some of these spots should perhaps be calls to warning instead, but I
did not make that change.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (symfile_complaints): Remove.
	(complaint_internal): Remove "complaints" parameter.
	(clear_complaints, vcomplaint): Remove "c" parameter.
	(get_complaints): Remove.
	* dwarf2read.c (dwarf2_statement_list_fits_in_line_number_section_complaint)
	(dwarf2_debug_line_missing_file_complaint)
	(dwarf2_debug_line_missing_end_sequence_complaint)
	(dwarf2_complex_location_expr_complaint)
	(dwarf2_const_value_length_mismatch_complaint)
	(dwarf2_section_buffer_overflow_complaint)
	(dwarf2_macro_malformed_definition_complaint)
	(dwarf2_invalid_attrib_class_complaint)
	(create_addrmap_from_index, dw2_symtab_iter_next)
	(dw2_expand_marked_cus)
	(dw2_debug_names_iterator::find_vec_in_debug_names)
	(dw2_debug_names_iterator::next, dw2_debug_names_iterator::next)
	(create_debug_type_hash_table, init_cutu_and_read_dies)
	(partial_die_parent_scope, add_partial_enumeration)
	(skip_one_die, fixup_go_packaging, quirk_rust_enum, process_die)
	(dwarf2_compute_name, dwarf2_physname, read_namespace_alias)
	(read_import_statement, read_file_scope, create_dwo_cu_reader)
	(create_cus_hash_table, create_dwp_hash_table)
	(inherit_abstract_dies, read_func_scope, read_call_site_scope)
	(dwarf2_rnglists_process, dwarf2_ranges_process)
	(dwarf2_add_type_defn, dwarf2_attach_fields_to_type)
	(dwarf2_add_member_fn, get_alignment, maybe_set_alignment)
	(handle_struct_member_die, process_structure_scope)
	(read_array_type, read_common_block, read_module_type)
	(read_tag_pointer_type, read_typedef, read_base_type)
	(read_subrange_type, load_partial_dies, partial_die_info::read)
	(partial_die_info::read, partial_die_info::read)
	(partial_die_info::read, read_checked_initial_length_and_offset)
	(dwarf2_string_attr, read_formatted_entries)
	(dwarf_decode_line_header)
	(lnp_state_machine::check_line_address, dwarf_decode_lines_1)
	(new_symbol, dwarf2_const_value_attr, lookup_die_type)
	(read_type_die_1, determine_prefix, dwarf2_get_ref_die_offset)
	(dwarf2_get_attr_constant_value, dwarf2_fetch_constant_bytes)
	(get_signatured_type, get_DW_AT_signature_type)
	(decode_locdesc, file_file_name, consume_improper_spaces)
	(skip_form_bytes, skip_unknown_opcode, dwarf_parse_macro_header)
	(dwarf_decode_macro_bytes, dwarf_decode_macros)
	(dwarf2_symbol_mark_computed, set_die_type)
	(read_attribute_value): Update.
	* stap-probe.c (handle_stap_probe, get_stap_base_address):
	Update.
	* dbxread.c (unknown_symtype_complaint)
	(lbrac_mismatch_complaint, repeated_header_complaint)
	(set_namestring, function_outside_compilation_unit_complaint)
	(read_dbx_symtab, process_one_symbol): Update.
	* gdbtypes.c (stub_noname_complaint): Update.
	* windows-nat.c (handle_unload_dll): Update.
	* coffread.c (coff_symtab_read, enter_linenos, decode_type)
	(decode_base_type): Update.
	* xcoffread.c (bf_notfound_complaint, ef_complaint)
	(eb_complaint, record_include_begin, record_include_end)
	(enter_line_range, xcoff_next_symbol_text, read_xcoff_symtab)
	(process_xcoff_symbol, read_symbol)
	(function_outside_compilation_unit_complaint)
	(scan_xcoff_symtab): Update.
	* machoread.c (macho_symtab_read, macho_add_oso_symfile): Update.
	* buildsym.c (finish_block_internal, make_blockvector)
	(end_symtab_get_static_block, augment_type_symtab): Update.
	* dtrace-probe.c (dtrace_process_dof)
	(dtrace_static_probe_ops::get_probes): Update.
	* complaints.h (struct complaint): Don't declare.
	(symfile_complaints): Remove.
	(complaint_internal): Remove "complaints" parameter.
	(complaint): Likewise.
	(clear_complaints): Likewise.
	* symfile.c (syms_from_objfile_1, finish_new_objfile)
	(reread_symbols): Update.
	* dwarf2-frame.c (dwarf2_restore_rule, execute_cfa_program)
	(dwarf2_frame_cache, decode_frame_entry): Update.
	* dwarf2loc.c (dwarf_reg_to_regnum): Update.
	* objc-lang.c (lookup_objc_class, lookup_child_selector)
	(info_selectors_command): Update.
	* macrotab.c (macro_include, check_for_redefinition)
	(macro_undef): Update.
	* objfiles.c (filter_overlapping_sections): Update.
	* stabsread.c (invalid_cpp_abbrev_complaint)
	(reg_value_complaint, stabs_general_complaint, dbx_lookup_type)
	(define_symbol, error_type, read_type, rs6000_builtin_type)
	(stabs_method_name_from_physname, read_member_functions)
	(read_cpp_abbrev, read_baseclasses, read_tilde_fields)
	(attach_fields_to_type, complain_about_struct_wipeout)
	(read_range_type, read_args, common_block_start)
	(common_block_end, cleanup_undefined_types_1, scan_file_globals):
	Update.
	* mdebugread.c (index_complaint, unknown_ext_complaint)
	(basic_type_complaint, bad_tag_guess_complaint)
	(bad_rfd_entry_complaint, unexpected_type_code_complaint)
	(reg_value_complaint, parse_symbol, parse_type, upgrade_type)
	(parse_procedure, parse_lines)
	(function_outside_compilation_unit_complaint)
	(parse_partial_symbols, psymtab_to_symtab_1, cross_ref)
	(bad_tag_guess_complaint, reg_value_complaint): Update.
	* cp-support.c (demangled_name_complaint): Update.
	* macroscope.c (sal_macro_scope): Update.
	* dwarf-index-write.c (class debug_names): Update.

gdb/testsuite/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* gdb.gdb/complaints.exp (test_initial_complaints): Don't mention
	symfile_complaints.
	(test_short_complaints): Likewise.
	(test_empty_complaints): Likewise.
	(test_initial_complaints): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove "noisy" parameter from clear_complaints
@ 2018-05-23 17:01 sergiodj+buildbot
  2018-05-23 17:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 17:01 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4e9668d0d1ddad73af7c20a92a00704fbea2a8d9 ***

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

Remove "noisy" parameter from clear_complaints

After the previous patch, the "noisy" parameter to clear_complaints is
no longer used, so this patch removes it.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (clear_complaints): Remove "noisy" parameter.
	* complaints.h (clear_complaints): Update.
	* symfile.c (syms_from_objfile_1, finish_new_objfile)
	(reread_symbols): Update.

gdb/testsuite/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* gdb.gdb/complaints.exp (test_empty_complaints): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove internal_complaint
@ 2018-05-23 15:59 sergiodj+buildbot
  2018-05-23 16:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23 15:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2b9496b2b4781b21bc30a70337e24205f8a923d8 ***

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

Remove internal_complaint

I happened to notice that gdb has both complaint_internal and
internal_complaint.  The latter is unused, so this patch removes it.

gdb/ChangeLog
2018-05-23  Tom Tromey  <tom@tromey.com>

	* complaints.c (internal_complaint): Remove.
	* complaints.h (internal_complaint): Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix gdb.base/remote.exp with native-extended-gdbserver board
@ 2018-05-23  3:06 sergiodj+buildbot
  2018-05-23  2:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23  3:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 035522c0228be33b2124ada2f178187e7e53aa6c ***

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

Fix gdb.base/remote.exp with native-extended-gdbserver board

This fixes gdb.base/remote.exp regressions caused by the previous
commit to the testcase, when tested with
--target_board=native-extended-gdbserver.  For example:

  ...
  show remote memory-write-packet-size
  The memory-write-packet-size is 0 (default). Packets are limited to 16383 bytes.
  (gdb) FAIL: gdb.base/remote.exp: write-packet default
  ...

With that board, GDB connects to GDBserver at gdb_start time, so GDB
is showing the actual remote/gdbserver packet size limits.

Fix it using the usual "disconnect" pattern.  While at it, there's no
need to start GDB before compiling the testcase.

gdb/testsuite/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* gdb.base/remote.exp: Only gdb_start after compiling the
	testcase.  Issue "disconnect" before testing "set remote" command
	defaults.  Issue clean_restart before running to main.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] gdb/x86: Fix `-Wstrict-overflow' build error in `i387_collect_xsave'
@ 2018-05-23  2:03 sergiodj+buildbot
  2018-05-23  2:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23  2:03 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 35f1fea3fcd44546a6cf074029c284c64ad25b3c ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 35f1fea3fcd44546a6cf074029c284c64ad25b3c

gdb/x86: Fix `-Wstrict-overflow' build error in `i387_collect_xsave'

Make `i' defined within `i387_collect_xsave' unsigned, removing a
`-Werror=strict-overflow' compilation error:

.../gdb/i387-tdep.c: In function 'void i387_collect_xsave(const regcache*, int, void*, int)':
.../gdb/i387-tdep.c:1348:1: error: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Werror=strict-overflow]
 i387_collect_xsave (const struct regcache *regcache, int regnum,
 ^
cc1plus: all warnings being treated as errors
Makefile:1610: recipe for target 'i387-tdep.o' failed
make: *** [i387-tdep.o] Error 1

seen with GCC 5.4.0, a commit 8ee22052f690 ("gdb/x86: Handle kernels
using compact xsave format") regression.  While `regnum' can be -1 on
entry to the function, to mean all registers, `i' is only used with
non-negative register numbers.

	gdb/
	* i387-tdep.c (i387_collect_xsave): Make `i' unsigned.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/gdbserver: Correctly handle narrow big-endian register transfers
@ 2018-05-23  1:46 sergiodj+buildbot
  2018-05-23  1:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23  1:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7e947ad3438b2954e0bd248fd2c95a86bd9fe33b ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 7e947ad3438b2954e0bd248fd2c95a86bd9fe33b

MIPS/gdbserver: Correctly handle narrow big-endian register transfers

Fix an issue with `gdbserver' on big-endian n64 MIPS targets, where
$dspctl is 32-bit while the `ptrace' transfer data type is 64-bit.

Such register data is held in the low order 32 bits of the 64-bit data
quantity exchanged with the buffer used by `fetch_register' and
`store_register', however `supply_register' and `collect_register'
access the same data as a 32-bit quantity.  Consequently the register is
presented and written as all-zeros held in the most-significant part of
the big-endian 64-bit data quantity represented in the buffer:

(gdb) info registers
                  zero               at               v0               v1
 R0   0000000000000000 0000000000000001 0000000000000001 0000000000000000
                    a0               a1               a2               a3
 R4   00000001200212b0 0000000000000000 0000000000000021 000000012001a260
                    a4               a5               a6               a7
 R8   000000012001a260 0000000000000004 800000010c60c000 fffffffffffffff8
                    t0               t1               t2               t3
 R12  0000000000000000 000000fff7edab68 0000000000000001 0000000000000000
                    s0               s1               s2               s3
 R16  000000fff7ee2068 0000000120008b80 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  000000000052e5c8 000000000052f008 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000000 00000001200027c0 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  00000001200212b0 000000ffffffc850 000000ffffffc850 0000000120005ee8
                status               lo               hi         badvaddr
      0000000000109cf3 0000000000943efe 000000000000000e 000000012001a008
                 cause               pc
      0000000000800024 0000000120005ee8
                  fcsr              fir              hi1              lo1
              0e800000         00f30000 0000000000000000 0101010101010101
                   hi2              lo2              hi3              lo3
      0202020202020202 0303030303030303 0404040404040404 0505050505050505
                dspctl          restart
              00000000 0000000000000000
(gdb)

Correct this problem then by using the `mips_supply_register'
`mips_collect_register' accessors for 32-bit registers where the
`ptrace' data type is 64-bit.  These accessors already operate on 32-bit
data quantities held in 64-bit containers:

(gdb) info registers
                  zero               at               v0               v1
 R0   0000000000000000 0000000000000001 0000000000000001 0000000000000000
                    a0               a1               a2               a3
 R4   00000001200212b0 0000000000000000 0000000000000021 000000012001a260
                    a4               a5               a6               a7
 R8   000000012001a260 0000000000000004 800000010d82e900 fffffffffffffff8
                    t0               t1               t2               t3
 R12  0000000000000000 000000fff7edab68 0000000000000001 0000000000000000
                    s0               s1               s2               s3
 R16  000000fff7ee2068 0000000120008b80 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  000000000052e5c8 000000000052f008 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000000 00000001200027c0 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  00000001200212b0 000000ffffffc850 000000ffffffc850 0000000120005ee8
                status               lo               hi         badvaddr
      0000000000109cf3 0000000000943efe 000000000000000e 000000012001a008
                 cause               pc
      0000000000800024 0000000120005ee8
                  fcsr              fir              hi1              lo1
              0e800000         00f30000 0000000000000000 0101010101010101
                   hi2              lo2              hi3              lo3
      0202020202020202 0303030303030303 0404040404040404 0505050505050505
                dspctl          restart
              55aa33cc 0000000000000000
(gdb)

	gdb/gdbserver/
	* linux-mips-low.c [HAVE_PTRACE_GETREGS] (mips_collect_register)
	(mips_supply_register): Move outside HAVE_PTRACE_GETREGS.
	(mips_collect_ptrace_register, mips_supply_ptrace_register): New
	functions.
	(the_low_target): Wire them.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: one struct remote_state per struct remote_target
@ 2018-05-23  1:41 sergiodj+buildbot
  2018-05-23  1:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23  1:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6b8edb5101861228778b7c2d014e20c5ba0c156a ***

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

remote: one struct remote_state per struct remote_target

'struct remote_state' today contains per-connection state, however
there's only a single global instance of that type.  In order to
support multiple connections, we must have one such object per
connection.

Thus this patch eliminates the 'remote_state' global in favor of
having a remote_state instance per remote_target instance.

The get_remote_state free function is eliminated as well, by making it
a remote_target method instead.

The patch then fixes the fallout by making all free functions that
refer to get_remote_state() directly or indirectly be methods of
remote_target too.

Likewise, remote-fileio.c and remote-notif.c routines are
parameterized with a remote_target pointer too, so they can call into
the right remote_target instance.

References to the global 'get_remote_state ()->remote_desc' to tell
whether the remote target is open (!= nullptr) must be replaced with
something else:

 - Command implementations use a new get_current_remote_target free
 function.

 - remote_target::open_1 checks the exception type instead.

Finally, remote_target and extended_remote_target are made
heap-allocated targets.  As with the earlier core target patches, it
still won't be possible to have more than one remote_target instance
in practice, but this puts us closer.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote-fileio.c (remote_fileio_reply, remote_fileio_ioerror)
	(remote_fileio_badfd, remote_fileio_return_errno)
	(remote_fileio_return_success, remote_fileio_func_open)
	(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): Add
	remote_target parameter.
	(remote_fio_func_map) <func>: Add remote_target parameter.
	(do_remote_fileio_request, remote_fileio_request):
	* remote-fileio.h (remote_fileio_request):
	* remote-notif.c (remote_notif_ack, remote_notif_parse, ): Add
	remote_target parameter.
	(remote_notif_process, handle_notification): Adjust to pass down
	the remote.
	(remote_notif_state_allocate): Add remote_target parameter.  Save
	it.
	* remote-notif.h (struct remote_target): Forward declare.
	(struct notif_client) <parse, ack, can_get_pending_events>: Add
	remote_target parameter.
	(struct remote_notif_state) <remote>: New field.
	(remote_notif_ack, remote_notif_parse): Add remote_target
	parameter.
	(remote_notif_state_allocate, remote_notif_state_allocate): Add
	remote_target parameter.
	* remote.c (OPAQUETHREADBYTES, threadref, gdb_ext_thread_info)
	(threads_listing_context, rmt_thread_action, protocol_feature)
	(packet_reg, stop_reply, stop_reply_p, enum packet_support)
	(packet_result, struct threads_listing_context, remote_state):
	Move definitions and declarations higher up.
	(remote_target) <~remote_target>: Declare.
	(remote_download_command_source, remote_file_put, remote_file_get)
	(remote_file_delete, remote_hostio_pread, remote_hostio_pwrite)
	(remote_hostio_pread_vFile, remote_hostio_send_command)
	(remote_hostio_set_filesystem, remote_hostio_open)
	(remote_hostio_close, remote_hostio_unlink, remote_state)
	(get_remote_state, get_remote_packet_size, get_memory_packet_size)
	(get_memory_write_packet_size, get_memory_read_packet_size)
	(append_pending_thread_resumptions, remote_detach_1)
	(append_resumption, remote_resume_with_vcont)
	(add_current_inferior_and_thread, wait_ns, wait_as)
	(process_stop_reply, remote_notice_new_inferior)
	(process_initial_stop_replies, remote_add_thread)
	(btrace_sync_conf, remote_btrace_maybe_reopen)
	(remove_new_fork_children, kill_new_fork_children)
	(discard_pending_stop_replies, stop_reply_queue_length)
	(check_pending_events_prevent_wildcard_vcont)
	(discard_pending_stop_replies_in_queue, stop_reply)
	(remote_notif_remove_queued_reply, stop_reply *queued_stop_reply)
	(peek_stop_reply, remote_parse_stop_reply, remote_stop_ns)
	(remote_interrupt_as, remote_interrupt_ns)
	(remote_get_noisy_reply, remote_query_attached)
	(remote_add_inferior, remote_current_thread, get_current_thread)
	(set_thread, set_general_thread, set_continue_thread)
	(set_general_process, write_ptid)
	(remote_unpack_thread_info_response, remote_get_threadinfo)
	(parse_threadlist_response, remote_get_threadlist)
	(remote_threadlist_iterator, remote_get_threads_with_ql)
	(remote_get_threads_with_qxfer)
	(remote_get_threads_with_qthreadinfo, extended_remote_restart)
	(get_offsets, remote_check_symbols, remote_supported_packet)
	(remote_query_supported, remote_packet_size)
	(remote_serial_quit_handler, remote_detach_pid)
	(remote_vcont_probe, remote_resume_with_hc)
	(send_interrupt_sequence, interrupt_query)
	(remote_notif_get_pending_events, fetch_register_using_p)
	(send_g_packet, process_g_packet, fetch_registers_using_g)
	(store_register_using_P, store_registers_using_G)
	(set_remote_traceframe, check_binary_download)
	(remote_write_bytes_aux, remote_write_bytes, remote_read_bytes_1)
	(remote_xfer_live_readonly_partial, remote_read_bytes)
	(remote_send_printf, remote_flash_write, readchar)
	(remote_serial_write, putpkt, putpkt_binary, skip_frame)
	(read_frame, getpkt, getpkt_or_notif_sane_1, getpkt_sane)
	(getpkt_or_notif_sane, remote_vkill, remote_kill_k)
	(extended_remote_disable_randomization, extended_remote_run)
	(send_environment_packet, extended_remote_environment_support)
	(extended_remote_set_inferior_cwd, remote_write_qxfer)
	(remote_read_qxfer, push_stop_reply, vcont_r_supported)
	(packet_command): Now methods of ...
	(remote_target): ... this class.
	(m_remote_state) <remote_target>: New field.
	(struct remote_state) <stop_reply_queue,
	remote_async_inferior_event_token, wait_forever_enabled_p>: New
	fields.
	(remote_state::remote_state): Allocate stop_reply_queue.
	(remote_state): Delete global.
	(get_remote_state_raw): Delete.
	(remote_target::get_remote_state): Allocate m_remote_state on
	demand.
	(get_current_remote_target): New.
	(remote_ops, extended_remote_ops): Delete.
	(wait_forever_enabled_p, remote_async_inferior_event_token):
	Delete, moved to struct remote_state.
	(remote_target::close): Delete self.  Destruction bits split to
	...
	(remote_target::~remote_target): ... this.
	(show_memory_packet_size): Adjust to use
	get_current_remote_target.
	(struct protocol_feature) <func>: Add remote_target parameter.
	All callers adjusted.
	(curr_quit_handler_target): New.
	(remote_serial_quit_handler): Reimplement.
	(remote_target::open_1): Adjust to use get_current_remote_target.
	Heap-allocate remote_target/extended_remote_target instances.
	(vcont_builder::vcont_builder): Add remote_target parameter, and
	save it in m_remote.  All callers adjusted.
	(vcont_builder::m_remote): New field.
	(vcont_builder::restart, vcont_builder::flush)
	(vcont_builder::push_action): Use it.
	(remote_target::commit_resume): Use it.
	(struct queue_iter_param) <remote>: New field.
	(remote_target::remove_new_fork_children): Fill in 'remote' field.
	(check_pending_event_prevents_wildcard_vcont_callback_data): New.
	(check_pending_event_prevents_wildcard_vcont_callback)
	(remote_target::check_pending_events_prevent_wildcard_vcont)
	(remote_target::discard_pending_stop_replies)
	(remote_target::discard_pending_stop_replies_in_queue)
	(remote_target::remote_notif_remove_queued_reply): Fill in
	'remote' field.
	(remote_notif_get_pending_events): New.
	(remote_target::readchar, remote_target::remote_serial_write):
	Save/restore curr_quit_handler_target.
	(putpkt): New.
	(kill_new_fork_children): Fill in 'remote' field.
	(packet_command): Use get_current_remote_target, defer to
	remote_target method of same name.
	(scoped_remote_fd::scoped_remote_fd): Add 'remote_target'
	parameter, and save it in m_remote.  All callers adjusted.
	(scoped_remote_fd::release): Use m_remote.
	(scoped_remote_fd::m_remote): New field.
	(remote_file_put, remote_file_get, remote_file_delete): Use
	get_current_remote_target, defer to remote_target method of same
	name.
	(remote_btrace_reset): Add remote_state paremeter.  Update all
	callers.
	(remote_async_inferior_event_handler). Pass down 'data'.
	(remote_new_objfile): Use get_current_remote_target.
	(remote_target::vcont_r_supported): New.
	(set_range_stepping): Use get_current_remote_target and
	remote_target::vcont_r_supported.
	(_initialize_remote): Don't allocate 'remote_state' and
	'stop_reply_queue' globals.
	* remote.h (struct remote_target): Forward declare.
	(getpkt, putpkt, remote_notif_get_pending_events): Add
	'remote_target' parameter.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Handle "show remote memory-write-packet-size" when not connected
@ 2018-05-23  0:48 sergiodj+buildbot
  2018-05-23  1:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-23  0:48 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT cc0be08f80d4348e8f81471c80409710c4d4cd1a ***

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

Handle "show remote memory-write-packet-size" when not connected

Currently "show remote memory-write-packet-size" says that the packet
size is limited to whatever is stored in the remote_state global, even
if not connected to a target.

When we get to support multiple instances of remote targets, there
won't be a remote_state global anymore, so that must be replaced by
something else.

Since it doesn't make sense to print the limit of the packet size of a
non-existing connection, this patch makes us say that the limit will
be further reduced when we connect.

The text is taken from the command's online help, which says:

 "The actual limit is further reduced dependent on the target."

Note that a value of "0" is special, as per "help set remote
memory-write-packet-size":

 ~~~
 Specify the number of bytes in a packet or 0 (zero) for the
 default packet size.
 ~~~

I've tweaked "show remote memory-write-packet-size" to include
"(default)" in the output in that case, like this:

 (gdb) show remote memory-write-packet-size
 The memory-write-packet-size is 0 (default). The actual limit will be further reduced dependent on the target.

While working on this, I noticed that an explicit "set remote
write-packet-size 0" does not makes GDB go back to the exact same
state as the default state when GDB starts up:

 (gdb) show remote memory-write-packet-size
 The memory-write-packet-size is 0. [...]
                                 ^^

 (gdb) set remote memory-write-packet-size 0
 (gdb) show remote memory-write-packet-size
 The memory-write-packet-size is 16384. [...]
                                 ^^^^^

The "16384" number comes from DEFAULT_MAX_MEMORY_PACKET_SIZE.

This happens because git commit a5c0808e221c ("gdb: remove packet size
limit") at
<https://sourceware.org/ml/gdb-patches/2015-08/msg00743.html>, added
this:

  /* So that the query shows the correct value.  */
  if (size <= 0)
    size = DEFAULT_MAX_MEMORY_PACKET_SIZE;

to set_memory_packet_size, but despite what the comment suggests, that
also has the side-effect of recording DEFAULT_MAX_MEMORY_PACKET_SIZE
in config->size.

Finally, DEFAULT_MAX_MEMORY_PACKET_SIZE only makes sense for "set
remote memory-write-packet-size fixed", so I've renamed it
accordingly, to make it a little bit clearer.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote.c (DEFAULT_MAX_MEMORY_PACKET_SIZE): Rename to ...
	(DEFAULT_MAX_MEMORY_PACKET_SIZE_FIXED): ... this.
	(get_fixed_memory_packet_size): New.
	(get_memory_packet_size): Use it.
	(set_memory_packet_size): Don't override the config size with
	DEFAULT_MAX_MEMORY_PACKET_SIZE.
	(show_memory_packet_size): Use get_fixed_memory_packet_size.
	Don't refer to get_memory_packet_size if not connected to a remote
	target.  Show "(default)" if configured size is 0.

gdb/testsuite/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* gdb.base/remote.exp: Adjust expected output of "show remote
	memory-write-packet-size".  Add tests for "set remote
	memory-write-packet-size 0" and "set remote
	memory-write-packet-size fixed/limit".


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: Small cleanup in compare_section_command
@ 2018-05-22 23:57 sergiodj+buildbot
  2018-05-23  0:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 23:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0e9a6b2f040e016c9dd7f9841a0272e488ed2fd5 ***

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

remote: Small cleanup in compare_section_command

The set_general_process call in compare_sections_command isn't
actually needed.  remote_target::verify_memory and
remote_target::xfer_partial already handle making sure the remote is
pointing at the right process or thread.

Getting this out of the way helps a bit with further elimination of
the remote_state global, because we have to handle the case of a user
invoking the command even if not connect to a remote target.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote.c (compare_section_command): Remove set_general_process
	call.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: remote_arch_state pointers -> remote_arch_state objects
@ 2018-05-22 23:27 sergiodj+buildbot
  2018-05-22 23:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 23:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 43c3a0e4735033ed2fe3a4cb65f911cee69f55ae ***

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

remote: remote_arch_state pointers -> remote_arch_state objects

The previous patch made the map store pointers to remote_arch_state
instead of objects directly, simply because struct remote_arch_state
is still incomplete where struct remote_state is declared.  This patch
thus moves the remote_arch_state declaration higher up in the file,
and makes the map store remote_arch_state objects directly instead of
pointers to objects.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote.c (struct packet_reg, struct remote_arch_state):
	Move higher up in the file.
	(remote_state) <m_arch_states>: Store remote_arch_state values
	instead of remote_arch_state pointers.
	(remote_state::get_remote_arch_state): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: multiple remote_arch_state instances per arch
@ 2018-05-22 22:55 sergiodj+buildbot
  2018-05-22 23:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 22:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 9d6eea31325e4027b5f035e941864fa6d780a8ca ***

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

remote: multiple remote_arch_state instances per arch

Currently, we associate gdbarch-related remote protocol state on a
per-gdbarch data object.  Things like the size of the g/G packet, and
the max remote packet size.  If we'll support being connected to
different remote servers at the same time, then we need to cope with
each having their own packet sizes, even if they are each debugging
programs of the same architecture.  I.e., a single instance of
remote_arch_state per arch is not sufficient.

This patch moves the remote_arch_state object to a map of
gdbarch-to-remote_arch_state saved in the remote_state structure.
Usually there will only be one entry in the map, though we may see
more with stubs that support multi-process and/or archs with multiple
ABIs (e.g, one remote_arch_state for 64-bit inferiors and another for
32-bit inferiors).

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote.c: Include <unordered_map>.
	(remote_state): Now a class.
	(remote_state) <get_remote_arch_state>: Declare method.
	<get_remote_arch_state>: New field.
	(remote_arch_state) <remote_arch_state>: Declare ctor.
	<regs>: Now a unique_ptr.
	(remote_gdbarch_data_handle): Delete.
	(get_remote_arch_state): Delete.
	(remote_state::get_remote_arch_state): New.
	(get_remote_state): Adjust to call remote_state's
	get_remote_arch_state method.
	(init_remote_state): Delete, bits factored out to ...
	(remote_arch_state::remote_arch_state): ... this new method.
	(get_remote_packet_size, get_memory_packet_size)
	(process_g_packet, remote_target::fetch_registers)
	(remote_target::prepare_to_store, store_registers_using_G)
	(remote_target::store_registers, remote_target::get_trace_status):
	Adjust to call remote_state's method.
	(_initialize_remote): Remove reference to
	remote_gdbarch_data_handle.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: Make readahead_cache a C++ class
@ 2018-05-22 22:50 sergiodj+buildbot
  2018-05-22 22:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 22:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT dd194f6b36727987dc7f0d707512bd886982099c ***

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

remote: Make readahead_cache a C++ class

The idea here is eliminate the get_remote_state calls from within
readahead_cache_invalidate, readahead_cache_invalidate_fd,
remote_hostio_pread_from_cache by making those functions be class
methods instead.  Later on we'll have one readahead_cache instance per
remote connection, and this change makes that easier.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote.c (struct readahead_cache) <invalidate, invalidate_fd,
	pread>: New method declarations.
	(remote_target::open_1): Adjust.
	(readahead_cache_invalidate): Rename to ...
	(readahead_cache::invalidate): ... this, and adjust to be a class
	method.
	(readahead_cache_invalidate_fd): Rename to ...
	(readahead_cache::invalidate_fd): ... this, and adjust to be a
	class method.
	(remote_hostio_pwrite): Adjust.
	(remote_hostio_pread_from_cache): Rename to ...
	(readahead_cache::pread): ... this, and adjust to be a class
	method.
	(remote_hostio_close): Adjust.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: Eliminate remote_hostio_close_cleanup
@ 2018-05-22 22:22 sergiodj+buildbot
  2018-05-22 22:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 22:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 440b7aece49b9a1e9ff4537214134c3cd06425d9 ***

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

remote: Eliminate remote_hostio_close_cleanup

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	* remote.c (remote_hostio_close_cleanup): Delete.
	(class scoped_remote_fd): New.
	(remote_file_put, remote_file_get): Use it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] remote: struct remote_state, use op new, fix leaks
@ 2018-05-22 21:16 sergiodj+buildbot
  2018-05-22 21:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 21:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT de44f5a73576b426b32b605e0d5016d4fae9b4b1 ***

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

remote: struct remote_state, use op new, fix leaks

A bit of C++ification.  Also plugs a few leaks, since currently
nothing is freeing a few fields of remote_state.  They're now freed in
the added destructor.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	(struct vCont_action_support): Use bool and initialize all fields.
	(struct readahead_cache): Initialize all fields.
	(remote_state): Use bool and initialize all fields.
	(remote_state::remote_state, remote_state::~remote_state): New.
	(new_remote_state): Delete.
	(_initialize_remote): Use new to allocate remote_state.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Support UTF-8 identifiers in C/C++ expressions (PR gdb/22973)
@ 2018-05-22 20:16 sergiodj+buildbot
  2018-05-22 20:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 20:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b1b60145aedb8adcb0b9dcf43a5ae735c2f03b51 ***

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

Support UTF-8 identifiers in C/C++ expressions (PR gdb/22973)

Factor out cp_ident_is_alpha/cp_ident_is_alnum out of
gdb/cp-name-parser.y and use it in the C/C++ expression parser too.

New test included.

gdb/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>
	      <zjz@zjz.name>

	PR gdb/22973
	* c-exp.y: Include "c-support.h".
	(parse_number, c_parse_escape, lex_one_token): Use TOLOWER instead
	of tolower.  Use c_ident_is_alpha to scan names.
	* c-lang.c: Include "c-support.h".
	(convert_ucn, convert_octal, convert_hex, convert_escape): Use
	ISXDIGIT instead of isxdigit and ISDIGIT instead of isdigit.
	* c-support.h: New file, with bits factored out from ...
	* cp-name-parser.y: ... this file.
	Include "c-support.h".
	(cp_ident_is_alpha, cp_ident_is_alnum): Deleted, moved to
	c-support.h and renamed.
	(symbol_end, yylex): Adjust.

gdb/testsuite/ChangeLog:
2018-05-22  Pedro Alves  <palves@redhat.com>

	PR gdb/22973
	* gdb.base/utf8-identifiers.c: New file.
	* gdb.base/utf8-identifiers.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Recognize isa205 in linux core files
@ 2018-05-22 19:25 sergiodj+buildbot
  2018-05-22 19:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 19:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0ec848ad25bb77edd9c9c3c097c3dd5b8874a6c0 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: 0ec848ad25bb77edd9c9c3c097c3dd5b8874a6c0

[PowerPC] Recognize isa205 in linux core files

Currently the ppc linux core file target doesn't return target
descriptions with the lager FPSCR introduced in isa205.

This patch changes the core file target so that the auxv is read from
the core file to determine the size of FPSCR, so that the appropriate
target description is selected.

gdb/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* arch/ppc-linux-common.c (ppc_linux_has_isa205): Change the
	parameter type to CORE_ADDR.
	* arch/ppc-linux-common.h (ppc_linux_has_isa205): Change the
	parameter type in declaration to CORE_ADDR.
	* ppc-linux-tdep.c (ppc_linux_core_read_description): Call
	target_auxv_search to get AT_HWCAP and use the result to get the
	target description.
	* ppc-linux-nat.c (ppc_linux_get_hwcap): Change the return type
	to CORE_ADDR. Remove the cast of the return value to unsigned
	long. Fix error predicate of target_auxv_search.
	(ppc_linux_nat_target::read_description): Change the type of the
	hwcap variable to CORE_ADDR.

gdb/testsuite/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* gdb.arch/powerpc-fpscr-gcore.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Fix inclusion of dfp pseudoregs in tdep
@ 2018-05-22 19:13 sergiodj+buildbot
  2018-05-22 19:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 19:13 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0fb2aaa15e04238644471f7d89be3667784b19c0 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: 0fb2aaa15e04238644471f7d89be3667784b19c0

[PowerPC] Fix inclusion of dfp pseudoregs in tdep

Previously, decimal floating point pseudoregisters were always included
in the target if it had a floating point unit.

This patch changes this to only include them if the target description
indicates that they are present, i.e. if the FPSCR register has more
than 32 bits.

gdb/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* rs6000-tdep.c (rs6000_gdbarch_init): Assign 1 to have_dfp only
	if the size of fpscr is larger than 32 bits.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Fix VSX registers in linux core files
@ 2018-05-22 18:22 sergiodj+buildbot
  2018-05-22 18:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 2c3305f6b0432e37d26ce7761d0c4415ab5ca911 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: 2c3305f6b0432e37d26ce7761d0c4415ab5ca911

[PowerPC] Fix VSX registers in linux core files

The functions used by the VSX regset to collect and supply registers
from core files where incorrect. This patch changes the regset to use
the standard regset collect/supply functions to fix this. The native
target is also changed to use the same regset.

gdb/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* ppc-linux-tdep.c (ppc_linux_vsxregset): New function.
	(ppc32_linux_vsxregmap): New global.
	(ppc32_linux_vsxregset): Initialize with ppc32_linux_vsxregmap,
	regcache_supply_regset, and regcache_collect_regset.
	* ppc-linux-tdep.h (ppc_linux_vsxregset): Declare.
	* ppc-linux-nat.c (supply_vsxregset, fill_vsxregset): Remove.
	(fetch_vsx_register, store_vsx_register): Remove.
	(fetch_vsx_registers): Add regno parameter. Get regset using
	ppc_linux_vsxregset. Use regset to supply registers.
	(store_vsx_registers): Add regno parameter. Get regset using
	ppc_linux_vsxregset. Use regset to collect registers.
	(fetch_register): Call fetch_vsx_registers instead of
	fetch_vsx_register.
	(store_register): Call store_vsx_registers instead of
	store_vsx_register.
	(fetch_ppc_registers): Call fetch_vsx_registers with -1 for the
	new regno parameter.
	(store_ppc_registers): Call store_vsx_registers with -1 for the
	new regno parameter.
	* rs6000-tdep.c (ppc_vsx_support_p, ppc_supply_vsxreget)
	(ppc_collect_vsxregset): Remove.

gdb/testsuite/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* gdb.arch/powerpc-vsx-gcore.exp: New file.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Fix access to VSCR in linux targets
@ 2018-05-22 17:34 sergiodj+buildbot
  2018-05-22 17:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 17:34 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d75a65809b49d41e97518b99c551a4bb2517500 ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: 1d75a65809b49d41e97518b99c551a4bb2517500

[PowerPC] Fix access to VSCR in linux targets

The 4-byte VSCR register is found inside a 16-byte field in the regset
returned by ptrace and in core files. The position of VSCR depends on
the endianess of the target, which was previously assumed to be
big-endian for the purpose of getting VSCR. This patch removes this
assumption to fix access to VSCR in little-endian mode.

gdb/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* ppc-tdep.h (struct ppc_reg_offsets): Remove vector register
	offset fields.
	* ppc-fbsd-tdep.c (ppc32_fbsd_reg_offsets): Remove initializers
	for vector register offset fields.
	(ppc64_fbsd_reg_offsets): Likewise.
	* ppc-nbsd-tdep.c (_initialize_ppcnbsd_tdep): Remove assignment
	to vector register offset fields.
	* ppc-obsd-tdep.c (_initialize_ppcnbsd_tdep): Remove assignment
	to vector register offset fields.
	* ppc-obsd-nat.c (_initialize_ppcobsd_nat): Remove assignment to
	vector register offset fields.
	* rs6000-aix-tdep.c (rs6000_aix32_reg_offsets): Remove
	initializers for vector register offset fields.
	(rs6000_aix64_reg_offsets): Likewise.
	* rs6000-tdep.c (ppc_vrreg_offset): Remove.
	(ppc_supply_vrregset): Remove.
	(ppc_collect_vrregset): Remove.
	* ppc-linux-tdep.c (ppc_linux_collect_vrregset): New function.
	(ppc_linux_vrregset) : New function.
	(ppc32_le_linux_vrregmap, ppc32_be_linux_vrregmap)
	(ppc32_le_linux_vrregset, ppc32_be_linux_vrregset): New globals.
	(ppc32_linux_vrregset): Remove.
	(ppc_linux_iterate_over_regset_sections): Call ppc_linux_vrregset
	and use result instead of ppc32_linux_vrregset.
	(ppc32_linux_reg_offsets): Remove initializers for vector register
	offset fields.
	(ppc64_linux_reg_offsets): Likewise.
	* ppc-linux-tdep.h (ppc_linux_vrregset): New declaration.
	* ppc-linux-nat.c: Include regset.h.
	(gdb_vrregset_t): Adjust comment to account for little-endian
	mode.
	(supply_vrregset, fill_vrregset): Remove.
	(fetch_altivec_register, store_altivec_register): Remove.
	(fetch_altivec_registers): Add regno parameter. Get regset using
	ppc_linux_vrregset. Use regset to supply registers.
	(store_altivec_registers): Add regno parameter. Get regset using
	ppc_linux_vrregset. Use regset to collect registers.
	(fetch_register): Call fetch_altivec_registers instead of
	fetch_altivec_register.
	(store_register): Call store_altivec_registers instead of
	store_altivec_register.
	(fetch_ppc_registers): Call fetch_altivec_registers with -1 for
	the new regno parameter.
	(store_ppc_registers): Call store_altivec_registers with -1 for
	the new regno parameter.

gdb/gdbserver/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* linux-ppc-low.c (ppc_fill_vrregset): Add vscr_offset variable.
	Set vscr_offset to 0 in little-endian mode and 12 in big-endian
	mode. Call collect_register_by_name with vscr using
	vscr_offset. Zero-pad vscr and vrsave fields in collector buffer.
	(ppc_store_vrregset): Add and set vscr_offset variable as in
	ppc_fill_vrregset. Call supply_register_by_name with vscr using
	vscr_offset.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Consolidate linux vector regset sizes
@ 2018-05-22 17:02 sergiodj+buildbot
  2018-05-22 17:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 17:02 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d078308a2ed1290e587b4365e2d7382d951a26af ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: d078308a2ed1290e587b4365e2d7382d951a26af

[PowerPC] Consolidate linux vector regset sizes

This patch defines constants for the sizes of the two vector
regsets (vector-scalar registers and regular vector registers).

The native, gdbserver and core file targets are changed to use these
constants.

The Linux ptrace calls return (or read) a smaller regset than the one
found in core files for vector registers, because ptrace uses a single
4-byte quantity for vrsave at the end of the regset, while the
core-file regset uses a full 16-byte field for vrsave. For simplicity,
the larger size is used in both cases, and so a buffer with 12 unused
additional bytes is passed to ptrace in the native target.

gdb/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* arch/ppc-linux-common.h (PPC_LINUX_SIZEOF_VRREGSET)
	(PPC_LINUX_SIZEOF_VSXREGSET): Define.
	* ppc-linux-nat.c (SIZEOF_VSXREGS, SIZEOF_VRREGS): Remove.
	(gdb_vrregset_t): Change array type size to
	PPC_LINUX_SIZEOF_VRREGSET.
	(gdb_vsxregset_t): Change array type size to
	PPC_LINUX_SIZEOF_VSXREGSET.
	* ppc-linux-tdep.c (ppc_linux_iterate_over_regset_sections):
	Change integer literals to PPC_LINUX_SIZEOF_VRREGSET and
	PPC_LINUX_SIZEOF_VSXREGSET.

gdb/gdbserver/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* linux-ppc-low.c (SIZEOF_VSXREGS, SIZEOF_VRREGS): Remove.
	(ppc_arch_setup): Change SIZEOF_VRREGS and SIZEOF_VSXREGS to
	PPC_LINUX_SIZEOF_VRREGSET and PPC_LINUX_SIZEOF_VSXREGSET.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Disable regsets using zero sizes in gdbserver
@ 2018-05-22 16:47 sergiodj+buildbot
  2018-05-22 16:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 16:47 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7273b5fc4baef93f8caaed678476e8cb3625338d ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: 7273b5fc4baef93f8caaed678476e8cb3625338d

[PowerPC] Disable regsets using zero sizes in gdbserver

Currently the linux-ppc-low.c fill/store functions for extended
regsets check whether they should execute by using the global hwcap
variable.

This patch explicitly sets the regset sizes to zero when needed to
disable them instead, so that the fill/store functions are not called
in the first place by regsets_fetch_inferior_registers in linux-low.c.

gdb/gdbserver/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* linux-ppc-low.c (ppc_fill_vsxregset): Remove ppc_hwcap check.
	(ppc_store_vsxregset): Likewise.
	(ppc_fill_vrregset): Likewise.
	(ppc_store_vrregset): Likewise.
	(ppc_fill_evrregset): Likewise.
	(ppc_store_evrregset): Likewise.
	(ppc_regsets): Set VSX/VR/EVR regset sizes to 0.
	(ppc_arch_setup): Iterate through ppc_regsets and set sizes when
	needed.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] [PowerPC] Consolidate linux target description selection
@ 2018-05-22 15:57 sergiodj+buildbot
  2018-05-22 16:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 15:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT bd64614eb737096f40b976fb505ddd42e7f1614c ***

Author: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Branch: master
Commit: bd64614eb737096f40b976fb505ddd42e7f1614c

[PowerPC] Consolidate linux target description selection

Share target description declarations and selection among ppc linux
native targets, core files, gdbserver and IPA.

To avoid complicated define guards, gdbserver and IPA now have
declarations for all descriptions, including 64-bit generated
descriptions when compiled in 32-bit mode. These have always been
linked into the gdbserver and IPA binaries. Because they might be
uninitialized, the selection function checks that the selected
description is initialized.

gdb/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* arch/ppc-linux-common.c: New file.
	* arch/ppc-linux-common.h: New file.
	* arch/ppc-linux-tdesc.h: New file.
	* configure.tgt (powerpc*-*-linux*): Add arch/ppc-linux-common.o.
	* Makefile.in (ALL_TARGET_OBS): Add arch/ppc-linux-common.o.
	(HFILES_NO_SRCDIR): Add arch/ppc-linux-common.h and
	arch/ppc-linux-tdesc.h.
	* ppc-linux-nat.c: Include arch/ppc-linux-common.h and
	arch/ppc-linux-tdesc.h.
	(ppc_linux_nat_target::read_description): Remove target
	description matching code. Fill a ppc_linux_features struct and
	call ppc_linux_match_description with it. Move comment about ISA
	2.05 to ppc-linux-common.c.
	* ppc-linux-tdep.c: Include arch/ppc-linux-common.h and
	arch/ppc-linux-tdesc.h.
	(ppc_linux_core_read_description): Remove target description
	matching code. Fill a ppc_linux_features struct and call
	ppc_linux_match_description with it.
	* ppc-linux-tdep.h (tdesc_powerpc_32l, tdesc_powerpc_64l)
	(tdesc_powerpc_altivec32l, tdesc_powerpc_altivec64l)
	(tdesc_powerpc_cell32l, tdesc_powerpc_cell64l)
	(tdesc_powerpc_vsx32l, tdesc_powerpc_vsx64l)
	(tdesc_powerpc_isa205_32l, tdesc_powerpc_isa205_64l)
	(tdesc_powerpc_isa205_altivec32l, tdesc_powerpc_isa205_altivec64l)
	(tdesc_powerpc_isa205_vsx32l, tdesc_powerpc_isa205_vsx64l)
	(tdesc_powerpc_e500l): Remove.

gdb/gdbserver/ChangeLog:
2018-05-22  Pedro Franco de Carvalho  <pedromfc@linux.vnet.ibm.com>

	* configure.srv (srv_tgtobj): Add arch/ppc-linux-common.o.
	* Makefile.in (SFILES): Add arch/ppc-linux-common.c.
	* linux-ppc-tdesc.h: Rename to linux-ppc-tdesc-init.h.
	* linux-ppc-tdesc-init.h (tdesc_powerpc_32l, tdesc_powerpc_64l)
	(tdesc_powerpc_altivec32l, tdesc_powerpc_altivec64l)
	(tdesc_powerpc_cell32l, tdesc_powerpc_cell64l)
	(tdesc_powerpc_vsx32l, tdesc_powerpc_vsx64l)
	(tdesc_powerpc_isa205_32l, tdesc_powerpc_isa205_64l)
	(tdesc_powerpc_isa205_altivec32l, tdesc_powerpc_isa205_altivec64l)
	(tdesc_powerpc_isa205_vsx32l, tdesc_powerpc_isa205_vsx64l)
	(tdesc_powerpc_e500l): Remove.
	* linux-ppc-ipa.c: Include arch/ppc-linux-tdesc.h and
	linux-ppc-tdesc-init.h. Don't include linux-ppc-tdesc.h.
	* linux-ppc-low.c: Include arch/ppc-linux-common.h,
	arch/ppc-linux-tdesc.h, and linux-ppc-tdesc-init.h. Don't include
	linux-ppc-tdesc.h.
	(ppc_arch_setup): Remove target description matching code. Fill a
	ppc_linux_features struct and call ppc_linux_match_description
	with it.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] fix "stale cleanup" internal-warning when using "catch assert" command
@ 2018-05-22 15:04 sergiodj+buildbot
  2018-05-22 15:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22 15:04 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 241db429d5735ae8875e38991c82204b310c2ff5 ***

Author: Joel Brobecker <brobecker@adacore.com>
Branch: master
Commit: 241db429d5735ae8875e38991c82204b310c2ff5

fix "stale cleanup" internal-warning when using "catch assert" command

Trying to insert a catchpoint on all Ada assertions now triggers
the following internal warning regardless of the situation. For
instance, not even debugging any program:

    (gdb) catch assert
    /[...]/gdb/common/cleanups.c:264: internal-warning:
    restore_my_cleanups has found a stale cleanup

This is due to a small bug in the following C++-ification commit:

    commit bc18fbb575437dd10089ef4619e46c0b9a93097d
    Author: Tom Tromey <tom@tromey.com>
    Date:   Fri May 18 15:58:50 2018 -0600
    Subject: Change ada_catchpoint::excep_string to be a std::string

The stale cleanup in question is the following one in top.c:execute_command:

    cleanup_if_error = make_bpstat_clear_actions_cleanup ();

This cleanup is expected to be discarded if there are no exception.
There were no GDB exception; however, a C++ exception was triggered,
because we passed NULL as the excep_string argument when calling
create_ada_exception_catchpoint, which is a reference to a const
string. So we get a C++ exception during the std::string constructor,
which propagates up, causing the cleanup to unexpectedly remain
in the cleanup chain.

This patch fixes the immediate issue of the incorrect call to
create_ada_exception_catchpoint.

gdb/ChangeLog:

        * ada-lang.c (catch_assert_command): Pass empty string instead
        of NULL for excep_string argument.

Tested on x86_64-linux, fixes the following failures:

  * catch_assert_if.exp: insert catchpoint on failed assertions with condition
  * catch_ex.exp: insert catchpoint on failed assertions

This also fixes about a dozen UNRESOLVED tests that are a consequence
of the two tests above failing and crashing GDB.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23207, hppa ld SIGSEGVs on invalid object files
@ 2018-05-22  6:36 sergiodj+buildbot
  2018-05-22  7:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22  6:36 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7455c018e45766ab7193cbd45f98f781e0dc7d84 ***

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

PR23207, hppa ld SIGSEGVs on invalid object files

We don't create PLT call stubs for anything in non-alloc sections,
so it doesn't pay to go looking for them.  The problem is that
non-alloc sections aren't processed by group_sections and thus don't
get a link_sec set up for them.

	PR 23207
	* elf32-hppa.c (final_link_relocate): Don't look for plt call
	stubs in non-alloc sections.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/Linux: Disable n32 USR `ptrace' accesses to 64-bit registers
@ 2018-05-22  1:57 sergiodj+buildbot
  2018-05-22  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22  1:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 75d74ccace05f6166a45dbaa352abf753891d3be ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 75d74ccace05f6166a45dbaa352abf753891d3be

MIPS/Linux: Disable n32 USR `ptrace' accesses to 64-bit registers

On the MIPS target DSP ASE registers can only be accessed with the
PTRACE_PEEKUSR and PTRACE_POKEUSR `ptrace' requests.  With the n32 ABI
these requests only pass 32-bit data quantities, which are narrower than
the width of DSP accumulator registers, which are 64-bit.

Generic code is prepared to transfer registers wider than the `ptrace'
data type by offsetting into the USR address space, by the data width
transferred.  That however does not work with the MIPS target, because
of how the API has been defined, where USR register addresses are
actually indices rather than offsets.  Consequently given address `a'
using `a + 4' accesses the fourth next register rather than the upper
half of the original register.

With native debugging this causes clobbered register contents, as well
as access failures as locations beyond the available USR space are
addressed:

(gdb) info registers
                  zero               at               v0               v1
 R0   0000000000000000 0000000000000001 0000000000000001 0000000000000000
                    a0               a1               a2               a3
 R4   0000000010019158 0000000000000000 0000000000000011 0000000010019160
                    a4               a5               a6               a7
 R8   0000000010019160 fffffffffff00000 fffffffffffffff8 0000000000000000
                    t0               t1               t2               t3
 R12  0000000010019150 0000000000000001 0000000000000001 000000000000000f
                    s0               s1               s2               s3
 R16  0000000077ee6f20 0000000010007bb0 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  000000000052e668 000000000052f008 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000001 0000000010019010 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  0000000010020280 000000007fff4c10 000000007fff4c10 0000000010004f48
                status               lo               hi         badvaddr
      0000000000109cf3 0000000000943efe 000000000000000e 000000001001900c
                 cause               pc
      0000000000800024 0000000010004f48
                  fcsr              fir              hi1              lo1
              0e800000         00f30000 0000000004040404 0101010105050505
                   hi2              lo2              hi3              lo3
      0202020255aa33cc Couldn't read register  (#75): Input/output error.
(gdb)

With `gdbserver' this makes debugging impossible due to a fatal failure:

(gdb) target remote :2346
Remote debugging using :2346
Reading symbols from .../sysroot/mips-r2-hard/lib32/ld.so.1...done.
0x77fc3d50 in __start () from .../sysroot/mips-r2-hard/lib32/ld.so.1
(gdb) continue
Continuing.
warning: Remote failure reply: E01
Remote communication error.  Target disconnected.: Connection reset by peer.
(gdb)

Correct the problem by marking any register in the MIPS backend whose
width exceeds the width of the `ptrace' data type unavailable for the
purpose of PTRACE_PEEKUSR and PTRACE_POKEUSR requests:

(gdb) info registers
                  zero               at               v0               v1
 R0   0000000000000000 0000000000000001 0000000000000001 0000000000000000
                    a0               a1               a2               a3
 R4   0000000010019158 0000000000000000 0000000000000011 0000000010019160
                    a4               a5               a6               a7
 R8   0000000010019160 fffffffffff00000 fffffffffffffff8 0000000000000000
                    t0               t1               t2               t3
 R12  0000000010019150 0000000000000001 0000000000000001 000000000000000f
                    s0               s1               s2               s3
 R16  0000000077ee6f20 0000000010007bb0 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  000000000052e5c8 000000000052f008 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000001 0000000010019010 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  0000000010020280 000000007fff4be0 000000007fff4be0 0000000010004f48
                status               lo               hi         badvaddr
      0000000000109cf3 0000000000943efe 000000000000000e 000000001001900c
                 cause               pc
      0000000000800024 0000000010004f48
                  fcsr              fir              hi1              lo1
              0e800000         00f30000    <unavailable>    <unavailable>
                   hi2              lo2              hi3              lo3
         <unavailable>    <unavailable>    <unavailable>    <unavailable>
                dspctl          restart
              55aa33cc 0000000000000000
(gdb)

as there is no way to access full contents of these registers with the
limited API available anyway.

This obviously does not affect general-purpose registers (which use the
PTRACE_GETREGS and PTRACE_SETREGS requests for access) or floating-point
general registers (which use PTRACE_GETFPREGS and PTRACE_SETFPREGS).
And $dspctl, being 32-bit, remains accessible too, which is important
for BPOSGE32 branch decoding in single-stepping.

For DSP accumulator access with the n32 ABI a new `ptrace' API is required
on the kernel side.

	gdb/
	* mips-linux-nat.c (mips64_linux_register_addr): Return -1 if
	the width of the requested register exceeds the width of the
	`ptrace' data type.

	gdb/gdbserver/
	* linux-mips-low.c (mips_cannot_fetch_register): Return 1 if the
	width of the requested register exceeds the width of the
	`ptrace' data type.
	(mips_cannot_store_register): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] MIPS/gdbserver: Fix issues with $zero register reads
@ 2018-05-22  0:40 sergiodj+buildbot
  2018-05-22  1:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-22  0:40 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT e4439e4346ec0d2cb0e65b497d26382e1054c93b ***

Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: e4439e4346ec0d2cb0e65b497d26382e1054c93b

MIPS/gdbserver: Fix issues with $zero register reads

Consistently supply hardwired $zero as a zeroed register, correcting
issues with the PTRACE_GETREGS path that currently copies the value of
$restart into $zero as illustrated by this program:

$ cat read.c

int
main (void)
{
  char buf[1024];
  ssize_t size;

  size = read (0, buf, sizeof (buf));

  return size;
}
$

and this corresponding debug session:

(gdb) break main
Breakpoint 1 at 0x120000970: file read.c, line 9.
(gdb) target remote :2346
Remote debugging using :2346
Reading symbols from .../sysroot/mips-r2-hard/lib64/ld.so.1...done.
0x000000fff7fca5a0 in __start ()
   from .../sysroot/mips-r2-hard/lib64/ld.so.1
(gdb) continue
Continuing.

Breakpoint 1, main () at read.c:9
9	  size = read (0, buf, sizeof (buf));
(gdb) info registers
                  zero               at               v0               v1
 R0   0000000000000000 0000000000000001 000000fff7ffe710 0000000000000000
                    a0               a1               a2               a3
 R4   0000000000000001 000000ffffffeb88 000000ffffffeb98 0000000000000000
                    a4               a5               a6               a7
 R8   000000fff7fc8800 000000fff7fc38f0 000000ffffffeb80 2f2f2f2f2f2f2f2f
                    t0               t1               t2               t3
 R12  0000000000000437 0000000000000002 000000fff7ffd000 0000000120000a00
                    s0               s1               s2               s3
 R16  000000fff7fc7068 0000000120000b90 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  0000000000521d88 0000000000522608 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000000 0000000120000970 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  000000fff7fc8800 000000ffffffea50 0000000000000000 000000fff7e4088c
                status               lo               hi         badvaddr
      0000000000109cf3 0000000000005ea5 0000000000000211 000000fff7eadf00
                 cause               pc
      0000000000800024 0000000120000970
                  fcsr              fir          restart
              00000000         00f30000 0000000000000000
(gdb) continue
Continuing.
^C

Program received signal SIGINT, Interrupt.
0x000000fff7f084ac in __GI___libc_read (fd=0, buf=0xffffffe640, nbytes=1024)
    at ../sysdeps/unix/sysv/linux/read.c:27
27	  return SYSCALL_CANCEL (read, fd, buf, nbytes);
(gdb) info registers
                  zero               at               v0               v1
 R0   0000000000001388 0000000000000001 0000000000000200 000000fff7ffe710
                    a0               a1               a2               a3
 R4   0000000000000000 000000ffffffe640 0000000000000400 0000000000000001
                    a4               a5               a6               a7
 R8   000000fff7fc8800 000000fff7fc38f0 000000ffffffeb80 2f2f2f2f2f2f2f2f
                    t0               t1               t2               t3
 R12  00000000000005e3 0000000000000002 000000fff7ffd000 000000012000099c
                    s0               s1               s2               s3
 R16  000000fff7fc7068 0000000120000b90 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  0000000000521d88 0000000000522608 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000000 000000fff7f2da20 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  000000fff7fc8800 000000ffffffe600 0000000000000000 000000012000099c
                status               lo               hi         badvaddr
      0000000000109cf3 00000000000001e6 00000000000000be 000000fff7f08470
                 cause               pc
      0000000000800020 000000fff7f084ac
                  fcsr              fir          restart
              00000000         00f30000 0000000000001388
(gdb)

and with the PTRACE_PEEKUSR path that does not supply this register at
all, causing issues analogous to ones addressed for the native MIPS
backend with commit 4e6ff0e1b86f ("MIPS/Linux/native: Supply $zero for
the !PTRACE_GETREGS case"):

(gdb) info registers
                  zero               at               v0               v1
 R0      <unavailable> 0000000000000001 0000000000000001 0000000000000000
                    a0               a1               a2               a3
 R4   00000001200212b0 0000000000000000 0000000000000021 000000012001a260
                    a4               a5               a6               a7
 R8   000000012001a260 0000000000000004 800000010cab1680 fffffffffffffff8
                    t0               t1               t2               t3
 R12  0000000000000000 000000fff7edab68 0000000000000001 0000000000000000
                    s0               s1               s2               s3
 R16  000000fff7ee2068 0000000120008b80 0000000000000000 0000000000000000
                    s4               s5               s6               s7
 R20  000000000052e5c8 000000000052f008 0000000000000000 0000000000000000
                    t8               t9               k0               k1
 R24  0000000000000000 00000001200027c0 0000000000000000 0000000000000000
                    gp               sp               s8               ra
 R28  00000001200212b0 000000ffffffc880 000000ffffffc880 0000000120005ee8
                status               lo               hi         badvaddr
         <unavailable> 0000000000943efe 000000000000000e 000000012001a008
                 cause               pc
      0000000000800024 0000000120005ee8
                  fcsr              fir          restart
              0e800000         00f30000 0000000000000000
(gdb)

and (under certain circumstances):

(gdb) next
Register 0 is not available
(gdb)

The problem with PTRACE_GETREGS happens because `mips_store_gregset'
supplies the contents of register slot #0, occupied by $restart, to
$zero.  The problem with PTRACE_PEEKUSR happens because for $zero
`mips_cannot_fetch_register' returns one, and no alternative way to
supply that register has been defined.

Correct `mips_store_gregset' then for the PTRACE_GETREGS case and add
`mips_fetch_register' for the PTRACE_PEEKUSR case.

	gdb/gdbserver/
	* linux-mips-low.c (mips_fetch_register): New function.  Update
	preceding comment.
	(mips_store_gregset): Supply 0 rather than $restart for $zero.
	(the_low_target): Wire `mips_fetch_register'.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove output_command_const
@ 2018-05-21 20:25 sergiodj+buildbot
  2018-05-21 22:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-21 20:25 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 122b53ea6a99c8811fb9cb84869b949b1ac55b22 ***

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

Remove output_command_const

I happened to notice that output_command_const still exists, but is
not needed any more -- commands are always const-correct now.  This
patch removes this leftover.

2018-05-21  Tom Tromey  <tom@tromey.com>

	* printcmd.c (output_command): Remove.
	(output_command_const): Rename to output_command.
	* valprint.h (output_command): Rename from output_command_const.
	* tracepoint.c (trace_dump_actions): Call output_command.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanup from ada_collect_symbol_completion_matches
@ 2018-05-21 18:46 sergiodj+buildbot
  2018-05-21 19:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-21 18:46 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 790217f6736cc0f0a177a681ba1c7cc5f995cfe7 ***

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

Remove cleanup from ada_collect_symbol_completion_matches

ada_collect_symbol_completion_matches installs a null_cleanup but not
any other cleanups.  This patch removes it.

ChangeLog
2018-05-21  Tom Tromey  <tom@tromey.com>

	* ada-lang.c (ada_collect_symbol_completion_matches): Remove
	cleanup.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove cleanup from ada-lang.c
@ 2018-05-21 18:22 sergiodj+buildbot
  2018-05-21 18:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-21 18:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 6f46ac8531ead61003c96b8e2fa6a383ea8d8c58 ***

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

Remove cleanup from ada-lang.c

This removes a cleanup from ada-lang.c by having
ada_exception_message_1 return a unique_xmalloc_ptr.

ChangeLog
2018-05-21  Tom Tromey  <tom@tromey.com>

	* ada-lang.c (ada_exception_message_1, ada_exception_message):
	Return unique_xmalloc_ptr.
	(print_it_exception): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove a cleanup from trace_dump_actions
@ 2018-05-21 18:16 sergiodj+buildbot
  2018-05-21 18:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-21 18:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 15b6611c69f6fdb7a20cd50d33d9acf8c5c32037 ***

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

Remove a cleanup from trace_dump_actions

This changes trace_dump_actions to use std::string, removing a
cleanup.

Tested by the buildbot.

ChangeLog
2018-05-21  Tom Tromey  <tom@tromey.com>

	* tracepoint.c (trace_dump_actions): Use std::string.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix copy-pasto, allocate objfile_per_bfd_storage with obstack_new
@ 2018-05-21  3:57 sergiodj+buildbot
  2018-05-21  4:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-21  3:57 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 184cde7552b5434196b8380be23b39ff4a5a17e6 ***

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

Fix copy-pasto, allocate objfile_per_bfd_storage with obstack_new

I realized after pushing that I made a copy-pasto, I had:

  # define HAVE_IS_TRIVIALLY_COPYABLE 1

instead of

  # define HAVE_IS_TRIVIALLY_CONSTRUCTIBLE 1

with the consequence that IsMallocable was always std::true_type (and
was therefore not enforcing anything).  Fixing that mistake triggered a
build failure:

/home/simark/src/binutils-gdb/gdb/objfiles.c:150:12:   required from here
/home/simark/src/binutils-gdb/gdb/common/poison.h:228:3: error: static assertion failed: Trying to use XOBNEW with a non-POD data type.

I am not sure why I did not see this when I originally wrote the patch
(but I saw and fixed other failures).  In any case, I swapped XOBNEW
with obstack_new to get rid of it.

Regtested on the buildbot.

gdb/ChangeLog:

	* common/traits.h (HAVE_IS_TRIVIALLY_COPYABLE): Rename the wrong
	instance to...
	(HAVE_IS_TRIVIALLY_CONSTRUCTIBLE): ... this.
	* objfiles.c (get_objfile_bfd_data): Allocate
	objfile_per_bfd_storage with obstack_new when allocating on
	obstack.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Introduce obstack_new, poison other "typed" obstack functions
@ 2018-05-21  1:51 sergiodj+buildbot
  2018-05-21  1:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-21  1:51 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 284a0e3cbffa92ee5c94065fcdd5a528482344fc ***

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

Introduce obstack_new, poison other "typed" obstack functions

Since we use obstacks with objects that are not default constructible,
we sometimes need to manually call the constructor by hand using
placement new:

  foo *f = obstack_alloc (obstack, sizeof (foo));
  f = new (f) foo;

It's possible to use allocate_on_obstack instead, but there are types
that we sometimes want to allocate on an obstack, and sometimes on the
regular heap.  This patch introduces a utility to make this pattern
simpler if allocate_on_obstack is not an option:

  foo *f = obstack_new<foo> (obstack);

Right now there's only one usage (in tdesc_data_init).

To help catch places where we would forget to call new when allocating
such an object on an obstack, this patch also poisons some other methods
of allocating an instance of a type on an obstack:

  - OBSTACK_ZALLOC/OBSTACK_CALLOC
  - XOBNEW/XOBNEW
  - GDBARCH_OBSTACK_ZALLOC/GDBARCH_OBSTACK_CALLOC

Unfortunately, there's no way to catch wrong usages of obstack_alloc.

By pulling on that string though, it tripped on allocating struct
template_symbol using OBSTACK_ZALLOC.  The criterion currently used to
know whether it's safe to "malloc" an instance of a struct is whether it
is a POD.  Because it inherits from struct symbol, template_symbol is
not a POD.  This criterion is a bit too strict however, it should still
safe to allocate memory for a template_symbol and memset it to 0.  We
didn't use is_trivially_constructible as the criterion in the first
place only because it is not available in gcc < 5.  So here I considered
two alternatives:

1. Relax that criterion to use std::is_trivially_constructible and add a
   bit more glue code to make it work with gcc < 5
2. Continue pulling on the string and change how the symbol structures
   are allocated and initialized

I managed to do both, but I decided to go with #1 to keep this patch
simpler and more focused.  When building with a compiler that does not
have is_trivially_constructible, the check will just not be enforced.

gdb/ChangeLog:

	* common/traits.h (HAVE_IS_TRIVIALLY_COPYABLE): Define if
	compiler supports std::is_trivially_constructible.
	* common/poison.h: Include obstack.h.
	(IsMallocable): Define to is_trivially_constructible if the
	compiler supports it, define to true_type otherwise.
	(xobnew): New.
	(XOBNEW): Redefine.
	(xobnewvec): New.
	(XOBNEWVEC): Redefine.
	* gdb_obstack.h (obstack_zalloc): New.
	(OBSTACK_ZALLOC): Redefine.
	(obstack_calloc): New.
	(OBSTACK_CALLOC): Redefine.
	(obstack_new): New.
	* gdbarch.sh: Include gdb_obstack in gdbarch.h.
	(gdbarch_obstack): New declaration in gdbarch.h, definition in
	gdbarch.c.
	(GDBARCH_OBSTACK_CALLOC, GDBARCH_OBSTACK_ZALLOC): Use
	obstack_calloc/obstack_zalloc.
	(gdbarch_obstack_zalloc): Remove.
	* target-descriptions.c (tdesc_data_init): Use obstack_new.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove useless variable int i in backtrace_command_1
@ 2018-05-20  0:37 sergiodj+buildbot
  2018-05-20  1:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-20  0:37 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 59f66be3aca7ef310c1d4464e93b251fe87135e0 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 59f66be3aca7ef310c1d4464e93b251fe87135e0

Remove useless variable int i in backtrace_command_1

value of int i was not used in the loop or after the loop.
Pushed as obvious.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix reference in comment: SRC_AND_LOC instead of LOC_AND_SRC
@ 2018-05-19  7:33 sergiodj+buildbot
  2018-05-19  7:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-19  7:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 50c65c2d60b371b8b85a804a5a71bf967ba9b355 ***

Author: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Branch: master
Commit: 50c65c2d60b371b8b85a804a5a71bf967ba9b355

Fix reference in comment: SRC_AND_LOC instead of LOC_AND_SRC

Pushed as obvious


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allocate dwz_file with new
@ 2018-05-19  3:06 sergiodj+buildbot
  2018-05-19  3:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-19  3:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7ff8cb8c51adec9cd1b461f9b670223d01223fef ***

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

Allocate dwz_file with new

This adds a constructor to struct dwz_file and arranges for it to be
allocated with "new" and wrapped in a unique_ptr.  This cuts down on
the amount of manual memory management that must be done.

Regression tested by the buildbot.

gdb/ChangeLog
2018-05-18  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (struct dwz_file): Add constructor, initializers.
	<dwz_bfd>: Now a gdb_bfd_ref_ptr.
	(~dwarf2_per_objfile): Update
	(dwarf2_get_dwz_file): Use new.
	* dwarf2read.h (struct dwarf2_per_objfile) <dwz_file>: Now a
	unique_ptr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] RISC-V: Add RV32E support.
@ 2018-05-19  2:16 sergiodj+buildbot
  2018-05-19  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-19  2:16 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7f99954970001cfc1b155d877ac2966d77e2c647 ***

Author: Jim Wilson <jimw@sifive.com>
Branch: master
Commit: 7f99954970001cfc1b155d877ac2966d77e2c647

RISC-V: Add RV32E support.

	Kito Cheng  <kito.cheng@gmail.com>
	Monk Chiang  <sh.chiang04@gmail.com>

	bfd/
	* elfnn-riscv.c (_bfd_riscv_elf_merge_private_bfd_data): Handle
	EF_RISCV_RVE.

	binutils/
	* readelf.c (get_machine_flags): Handle EF_RISCV_RVE.

	gas/
	* config/tc-riscv.c (rve_abi): New.
	(riscv_set_options): Add rve field.  Initialize it.
	(riscv_set_rve) New function.
	(riscv_set_arch): Support 'e' ISA subset.
	(reg_lookup_internal): If rve, check register is available.
	(riscv_set_abi): New parameter rve.
	(md_parse_option): Pass new argument to riscv_set_abi.
	(riscv_after_parse_args): Call riscv_set_rve.  If rve_abi, set
	EF_RISCV_RVE.
	* doc/c-riscv.texi (-mabi): Document new ilp32e argument.

	include/
	* elf/riscv.h (EF_RISCV_RVE): New define.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Allocate dwp_file with new
@ 2018-05-19  1:41 sergiodj+buildbot
  2018-05-19  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-19  1:41 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 400174b12a46fffbfad7c2504c33bb3ac29f3ef9 ***

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

Allocate dwp_file with new

This adds a constructor and initializer to dwp_file and changes it to
be allocated with "new".  This removes a bit of manual refcount
management.

Tested by the buildbot.

gdb/ChangeLog
2018-05-18  Tom Tromey  <tom@tromey.com>

	* dwarf2read.h (struct dwarf2_per_objfile) <dwp_file>: Now a
	unique_ptr.
	* dwarf2read.c (struct dwp_file): Add constructor and
	initializers.
	(open_and_init_dwp_file): Return a unique_ptr.
	(dwarf2_per_objfile, create_dwp_hash_table)
	(create_dwo_unit_in_dwp_v1, create_dwo_unit_in_dwp_v2)
	(lookup_dwo_unit_in_dwp): Update.
	(open_and_init_dwp_file, get_dwp_file): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Use new to allocate mapped_index
@ 2018-05-19  1:31 sergiodj+buildbot
  2018-05-19  2:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-19  1:31 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3063847f29cb83bae0cdf018c2dca68b65a50780 ***

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

Use new to allocate mapped_index

This changes struct mapped_index to be allocated with new.  This
simplifies the creation a bit (see dwarf2_read_index) and also removes
a somewhat ugly explicit destructor call from ~dwarf2_per_objfile.

Tested by the buildbot.

gdb/ChangeLog
2018-05-18  Tom Tromey  <tom@tromey.com>

	* dwarf2read.c (dwarf2_per_objfile): Update.
	(struct mapped_index): Add initializers.
	(dwarf2_read_index): Use new.
	(dw2_symtab_iter_init): Update.
	* dwarf2read.h (struct dwarf2_per_objfile) <index_table>: Now a
	unique_ptr.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Remove mapped_index::total_size
@ 2018-05-18 23:56 sergiodj+buildbot
  2018-05-19  0:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18 23:56 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT d3d02dee8d33ef46ed91b3e87ea1b377b14ec845 ***

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

Remove mapped_index::total_size

It is unused.

gdb/ChangeLog:

	* dwarf2read.c (mapped_index) <total_size>: Remove.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] format_pieces-selftests.c: Silence ARI warnings
@ 2018-05-18 22:33 sergiodj+buildbot
  2018-05-18 22:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18 22:33 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 1d143c36eedc0f0b124e6aa6fb3b98b1e6ff74b0 ***

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

format_pieces-selftests.c: Silence ARI warnings

Silence this:

unittests/format_pieces-selftests.c:51: warning: code: Do not use printf("%ll"), instead use printf("%s",phex()) to dump a `long long' value
unittests/format_pieces-selftests.c:56: warning: code: Do not use printf("%ll"), instead use printf("%s",phex()) to dump a `long long' value

gdb/ChangeLog:

	* unittests/format_pieces-selftests.c (test_format_specifier):
	Add ARI comments.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Show padding in ptype/o output
@ 2018-05-18 20:15 sergiodj+buildbot
  2018-05-18 20:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18 20:15 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT ce1e8424c69793139ec8d2a60c4a21ab136ae9e0 ***

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

Show padding in ptype/o output

I was recently using ptype/o to look at the layout of some objects in
gdb.  I noticed that trailing padding was not shown -- but I wanted to
be able to look at that, too.

This patch changes ptype/o to also print trailing holes.

Tested on x86-64 Fedora 26.

gdb/ChangeLog
2018-05-18  Tom Tromey  <tom@tromey.com>

	* c-typeprint.c (maybe_print_hole): New function.
	(c_print_type_struct_field_offset): Update.
	(c_type_print_base_struct_union): Call maybe_print_hole.

gdb/testsuite/ChangeLog
2018-05-18  Tom Tromey  <tom@tromey.com>

	* gdb.base/ptype-offsets.exp: Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Add support for the Freescale s12z processor.
@ 2018-05-18 15:27 sergiodj+buildbot
  2018-05-18 15:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18 15:27 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 7b4ae824289504c173a597e86a00ceab452095b7 ***

Author: John Darrington <john@darrington.wattle.id.au>
Branch: master
Commit: 7b4ae824289504c173a597e86a00ceab452095b7

Add support for the Freescale s12z processor.

bfd	* Makefile.am: Add s12z files.
	* Makefile.in: Regenerate.
	* archures.c: Add bfd_s12z_arch.
	* bfd-in.h: Add exports of bfd_putb24 and bfd_putl24.
	* bfd-in2.h: Regenerate.
	* config.bfd: Add s12z target.
	* configure.ac: Add s12z target.
	* configure: Regenerate.
	* cpu-s12z.c: New file.
	* elf32-s12z.c: New file.
	* libbfd.c (bfd_putb24): New function.
	(bfd_putl24): New function.
	* libbfd.h: Regenerate.
	* reloc.c: Add s12z relocations.
	(bfd_get_reloc_size): Handle size 5 relocs.
	* targets.c: Add s12z_elf32_vec.

opcodes	* Makefile.am: Add support for s12z architecture.
	* configure.ac: Likewise.
	* disassemble.c: Likewise.
	* disassemble.h: Likewise.
	* Makefile.in: Regenerate.
	* configure: Regenerate.
	* s12z-dis.c: New file.
	* s12z.h: New file.

include	* elf/s12z.h: New header.

ld	* Makefile.am: Add support for s12z architecture.
	* configure.tgt: Likewise.
	* Makefile.in: Regenerate.
	* emulparams/m9s12zelf.sh: New file.
	* scripttempl/elfm9s12z.sc: New file.
	* testsuite/ld-discard/static.d: Expect to fail for the s12z
	target.
	* testsuite/ld-elf/endsym.d: Likewise.
	* testsuite/ld-elf/merge.d: Likewise.
	* testsuite/ld-elf/pr14926.d: Skip for the s12z target.
	* testsuite/ld-elf/sec64k.exp: Likewise.
	* testsuite/ld-s12z: New directory.
	* testsuite/ld-s12z/opr-linking.d: New file.
	* testsuite/ld-s12z/opr-linking.s: New file.
	* testsuite/ld-s12z/relative-linking.d: New file.
	* testsuite/ld-s12z/relative-linking.s: New file.
	* testsuite/ld-s12z/z12s.exp: New file.

gas	* Makefile.am: Add support for s12z target.
	* Makefile.in: Regenerate.
	* NEWS: Mention the new support.
	* config/tc-s12z.c: New file.
	* config/tc-s12z.h: New file.
	* configure.tgt: Add  s12z support.
	* doc/Makefile.am: Likewise.
	* doc/Makefile.in: Regenerate.
	* doc/all.texi: Add s12z documentation.
	* doc/as.textinfo: Likewise.
	* doc/c-s12z.texi: New file.
	* testsuite/gas/s12z: New directory.
	* testsuite/gas/s12z/abs.d: New file.
	* testsuite/gas/s12z/abs.s: New file.
	* testsuite/gas/s12z/adc-imm.d: New file.
	* testsuite/gas/s12z/adc-imm.s: New file.
	* testsuite/gas/s12z/adc-opr.d: New file.
	* testsuite/gas/s12z/adc-opr.s: New file.
	* testsuite/gas/s12z/add-imm.d: New file.
	* testsuite/gas/s12z/add-imm.s: New file.
	* testsuite/gas/s12z/add-opr.d: New file.
	* testsuite/gas/s12z/add-opr.s: New file.
	* testsuite/gas/s12z/and-imm.d: New file.
	* testsuite/gas/s12z/and-imm.s: New file.
	* testsuite/gas/s12z/and-opr.d: New file.
	* testsuite/gas/s12z/and-opr.s: New file.
	* testsuite/gas/s12z/and-or-cc.d: New file.
	* testsuite/gas/s12z/and-or-cc.s: New file.
	* testsuite/gas/s12z/bfext-special.d: New file.
	* testsuite/gas/s12z/bfext-special.s: New file.
	* testsuite/gas/s12z/bfext.d: New file.
	* testsuite/gas/s12z/bfext.s: New file.
	* testsuite/gas/s12z/bit-manip.d: New file.
	* testsuite/gas/s12z/bit-manip.s: New file.
	* testsuite/gas/s12z/bit.d: New file.
	* testsuite/gas/s12z/bit.s: New file.
	* testsuite/gas/s12z/bra-expression-defined.d: New file.
	* testsuite/gas/s12z/bra-expression-defined.s: New file.
	* testsuite/gas/s12z/bra-expression-undef.d: New file.
	* testsuite/gas/s12z/bra-expression-undef.s: New file.
	* testsuite/gas/s12z/bra.d: New file.
	* testsuite/gas/s12z/bra.s: New file.
	* testsuite/gas/s12z/brclr-symbols.d: New file.
	* testsuite/gas/s12z/brclr-symbols.s: New file.
	* testsuite/gas/s12z/brset-clr-opr-imm-rel.d: New file.
	* testsuite/gas/s12z/brset-clr-opr-imm-rel.s: New file.
	* testsuite/gas/s12z/brset-clr-opr-reg-rel.d: New file.
	* testsuite/gas/s12z/brset-clr-opr-reg-rel.s: New file.
	* testsuite/gas/s12z/brset-clr-reg-imm-rel.d: New file.
	* testsuite/gas/s12z/brset-clr-reg-imm-rel.s: New file.
	* testsuite/gas/s12z/brset-clr-reg-reg-rel.d: New file.
	* testsuite/gas/s12z/brset-clr-reg-reg-rel.s: New file.
	* testsuite/gas/s12z/clb.d: New file.
	* testsuite/gas/s12z/clb.s: New file.
	* testsuite/gas/s12z/clr-opr.d: New file.
	* testsuite/gas/s12z/clr-opr.s: New file.
	* testsuite/gas/s12z/clr.d: New file.
	* testsuite/gas/s12z/clr.s: New file.
	* testsuite/gas/s12z/cmp-imm.d: New file.
	* testsuite/gas/s12z/cmp-imm.s: New file.
	* testsuite/gas/s12z/cmp-opr-inc.d: New file.
	* testsuite/gas/s12z/cmp-opr-inc.s: New file.
	* testsuite/gas/s12z/cmp-opr-rdirect.d: New file.
	* testsuite/gas/s12z/cmp-opr-rdirect.s: New file.
	* testsuite/gas/s12z/cmp-opr-reg.d: New file.
	* testsuite/gas/s12z/cmp-opr-reg.s: New file.
	* testsuite/gas/s12z/cmp-opr-rindirect.d: New file.
	* testsuite/gas/s12z/cmp-opr-rindirect.s: New file.
	* testsuite/gas/s12z/cmp-opr-sxe4.d: New file.
	* testsuite/gas/s12z/cmp-opr-sxe4.s: New file.
	* testsuite/gas/s12z/cmp-opr-xys.d: New file.
	* testsuite/gas/s12z/cmp-opr-xys.s: New file.
	* testsuite/gas/s12z/cmp-s-imm.d: New file.
	* testsuite/gas/s12z/cmp-s-imm.s: New file.
	* testsuite/gas/s12z/cmp-s-opr.d: New file.
	* testsuite/gas/s12z/cmp-s-opr.s: New file.
	* testsuite/gas/s12z/cmp-xy.d: New file.
	* testsuite/gas/s12z/cmp-xy.s: New file.
	* testsuite/gas/s12z/com-opr.d: New file.
	* testsuite/gas/s12z/com-opr.s: New file.
	* testsuite/gas/s12z/complex-shifts.d: New file.
	* testsuite/gas/s12z/complex-shifts.s: New file.
	* testsuite/gas/s12z/db-tb-cc-opr.d: New file.
	* testsuite/gas/s12z/db-tb-cc-opr.s: New file.
	* testsuite/gas/s12z/db-tb-cc-reg.d: New file.
	* testsuite/gas/s12z/db-tb-cc-reg.s: New file.
	* testsuite/gas/s12z/dbCC.d: New file.
	* testsuite/gas/s12z/dbCC.s: New file.
	* testsuite/gas/s12z/dec-opr.d: New file.
	* testsuite/gas/s12z/dec-opr.s: New file.
	* testsuite/gas/s12z/dec.d: New file.
	* testsuite/gas/s12z/dec.s: New file.
	* testsuite/gas/s12z/div.d: New file.
	* testsuite/gas/s12z/div.s: New file.
	* testsuite/gas/s12z/eor.d: New file.
	* testsuite/gas/s12z/eor.s: New file.
	* testsuite/gas/s12z/exg.d: New file.
	* testsuite/gas/s12z/exg.s: New file.
	* testsuite/gas/s12z/ext24-ld-xy.d: New file.
	* testsuite/gas/s12z/ext24-ld-xy.s: New file.
	* testsuite/gas/s12z/inc-opr.d: New file.
	* testsuite/gas/s12z/inc-opr.s: New file.
	* testsuite/gas/s12z/inc.d: New file.
	* testsuite/gas/s12z/inc.s: New file.
	* testsuite/gas/s12z/inh.d: New file.
	* testsuite/gas/s12z/inh.s: New file.
	* testsuite/gas/s12z/jmp.d: New file.
	* testsuite/gas/s12z/jmp.s: New file.
	* testsuite/gas/s12z/jsr.d: New file.
	* testsuite/gas/s12z/jsr.s: New file.
	* testsuite/gas/s12z/ld-imm-page2.d: New file.
	* testsuite/gas/s12z/ld-imm-page2.s: New file.
	* testsuite/gas/s12z/ld-imm.d: New file.
	* testsuite/gas/s12z/ld-imm.s: New file.
	* testsuite/gas/s12z/ld-immu18.d: New file.
	* testsuite/gas/s12z/ld-immu18.s: New file.
	* testsuite/gas/s12z/ld-large-direct.d: New file.
	* testsuite/gas/s12z/ld-large-direct.s: New file.
	* testsuite/gas/s12z/ld-opr.d: New file.
	* testsuite/gas/s12z/ld-opr.s: New file.
	* testsuite/gas/s12z/ld-s-opr.d: New file.
	* testsuite/gas/s12z/ld-s-opr.s: New file.
	* testsuite/gas/s12z/ld-small-direct.d: New file.
	* testsuite/gas/s12z/ld-small-direct.s: New file.
	* testsuite/gas/s12z/lea-immu18.d: New file.
	* testsuite/gas/s12z/lea-immu18.s: New file.
	* testsuite/gas/s12z/lea.d: New file.
	* testsuite/gas/s12z/lea.s: New file.
	* testsuite/gas/s12z/mac.d: New file.
	* testsuite/gas/s12z/mac.s: New file.
	* testsuite/gas/s12z/min-max.d: New file.
	* testsuite/gas/s12z/min-max.s: New file.
	* testsuite/gas/s12z/mod.d: New file.
	* testsuite/gas/s12z/mod.s: New file.
	* testsuite/gas/s12z/mov.d: New file.
	* testsuite/gas/s12z/mov.s: New file.
	* testsuite/gas/s12z/mul-imm.d: New file.
	* testsuite/gas/s12z/mul-imm.s: New file.
	* testsuite/gas/s12z/mul-opr-opr.d: New file.
	* testsuite/gas/s12z/mul-opr-opr.s: New file.
	* testsuite/gas/s12z/mul-opr.d: New file.
	* testsuite/gas/s12z/mul-opr.s: New file.
	* testsuite/gas/s12z/mul-reg.d: New file.
	* testsuite/gas/s12z/mul-reg.s: New file.
	* testsuite/gas/s12z/mul.d: New file.
	* testsuite/gas/s12z/mul.s: New file.
	* testsuite/gas/s12z/neg-opr.d: New file.
	* testsuite/gas/s12z/neg-opr.s: New file.
	* testsuite/gas/s12z/not-so-simple-shifts.d: New file.
	* testsuite/gas/s12z/not-so-simple-shifts.s: New file.
	* testsuite/gas/s12z/opr-18u.d: New file.
	* testsuite/gas/s12z/opr-18u.s: New file.
	* testsuite/gas/s12z/opr-expr.d: New file.
	* testsuite/gas/s12z/opr-expr.s: New file.
	* testsuite/gas/s12z/opr-ext-18.d: New file.
	* testsuite/gas/s12z/opr-ext-18.s: New file.
	* testsuite/gas/s12z/opr-idx-24-reg.d: New file.
	* testsuite/gas/s12z/opr-idx-24-reg.s: New file.
	* testsuite/gas/s12z/opr-idx3-reg.d: New file.
	* testsuite/gas/s12z/opr-idx3-reg.s: New file.
	* testsuite/gas/s12z/opr-idx3-xysp-24.d: New file.
	* testsuite/gas/s12z/opr-idx3-xysp-24.s: New file.
	* testsuite/gas/s12z/opr-indirect-expr.d: New file.
	* testsuite/gas/s12z/opr-indirect-expr.s: New file.
	* testsuite/gas/s12z/opr-symbol.d: New file.
	* testsuite/gas/s12z/opr-symbol.s: New file.
	* testsuite/gas/s12z/or-imm.d: New file.
	* testsuite/gas/s12z/or-imm.s: New file.
	* testsuite/gas/s12z/or-opr.d: New file.
	* testsuite/gas/s12z/or-opr.s: New file.
	* testsuite/gas/s12z/p2-mul.d: New file.
	* testsuite/gas/s12z/p2-mul.s: New file.
	* testsuite/gas/s12z/page2-inh.d: New file.
	* testsuite/gas/s12z/page2-inh.s: New file.
	* testsuite/gas/s12z/psh-pul.d: New file.
	* testsuite/gas/s12z/psh-pul.s: New file.
	* testsuite/gas/s12z/qmul.d: New file.
	* testsuite/gas/s12z/qmul.s: New file.
	* testsuite/gas/s12z/rotate.d: New file.
	* testsuite/gas/s12z/rotate.s: New file.
	* testsuite/gas/s12z/s12z.exp: New file.
	* testsuite/gas/s12z/sat.d: New file.
	* testsuite/gas/s12z/sat.s: New file.
	* testsuite/gas/s12z/sbc-imm.d: New file.
	* testsuite/gas/s12z/sbc-imm.s: New file.
	* testsuite/gas/s12z/sbc-opr.d: New file.
	* testsuite/gas/s12z/sbc-opr.s: New file.
	* testsuite/gas/s12z/shift.d: New file.
	* testsuite/gas/s12z/shift.s: New file.
	* testsuite/gas/s12z/simple-shift.d: New file.
	* testsuite/gas/s12z/simple-shift.s: New file.
	* testsuite/gas/s12z/single-ops.d: New file.
	* testsuite/gas/s12z/single-ops.s: New file.
	* testsuite/gas/s12z/specd6.d: New file.
	* testsuite/gas/s12z/specd6.s: New file.
	* testsuite/gas/s12z/st-large-direct.d: New file.
	* testsuite/gas/s12z/st-large-direct.s: New file.
	* testsuite/gas/s12z/st-opr.d: New file.
	* testsuite/gas/s12z/st-opr.s: New file.
	* testsuite/gas/s12z/st-s-opr.d: New file.
	* testsuite/gas/s12z/st-s-opr.s: New file.
	* testsuite/gas/s12z/st-small-direct.d: New file.
	* testsuite/gas/s12z/st-small-direct.s: New file.
	* testsuite/gas/s12z/st-xy.d: New file.
	* testsuite/gas/s12z/st-xy.s: New file.
	* testsuite/gas/s12z/sub-imm.d: New file.
	* testsuite/gas/s12z/sub-imm.s: New file.
	* testsuite/gas/s12z/sub-opr.d: New file.
	* testsuite/gas/s12z/sub-opr.s: New file.
	* testsuite/gas/s12z/tfr.d: New file.
	* testsuite/gas/s12z/tfr.s: New file.
	* testsuite/gas/s12z/trap.d: New file.
	* testsuite/gas/s12z/trap.s: New file.

binutils* readelf.c: Add support for s12z architecture.
	* testsuite/lib/binutils-common.exp (is_elf_format): Excluse s12z
	targets.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] x86: Don't set eh->local_ref to 1 for linker defined symbols
@ 2018-05-18 14:23 sergiodj+buildbot
  2018-05-18 14:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18 14:23 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 011b32fd4270fb7111ee1f63695ccd44562ee7df ***

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

x86: Don't set eh->local_ref to 1 for linker defined symbols

Since symbols created by HIDDEN and PROVIDE_HIDDEN assignments in
linker script may be marked as defined, but not hidden, we can't
set eh->local_ref to 1 in _bfd_x86_elf_link_symbol_references_local.

Also R_386_GOT32X should be handled as just like R_386_GOT32 when
relocating a section.  The input R_386_GOT32X relocations, which
can be relaxed, should have been converted to R_386_PC32, R_386_32
or R_386_GOTOFF.

bfd/

	PR ld/23189
	* elf32-i386.c (elf_i386_relocate_section): Handle R_386_GOT32X
	like R_386_GOT32.
	* elfxx-x86.c (_bfd_x86_elf_link_symbol_references_local): Don't
	set eh->local_ref to 1 for linker defined symbols.

ld/

	PR ld/23189
	* testsuite/ld-i386/i386.exp: Run pr23189.
	* testsuite/ld-x86-64/x86-64.exp: Likewise.
	* testsuite/ld-i386/pr23189.d: New file.
	* testsuite/ld-i386/pr23189.s: Likewise.
	* testsuite/ld-i386/pr23189.t: Likewise.
	* testsuite/ld-x86-64/pr23189.d: Likewise.
	* testsuite/ld-x86-64/pr23189.s: Likewise.
	* testsuite/ld-x86-64/pr23189.t: Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] PR23199, Invalid SHT_GROUP entry leads to group confusion
@ 2018-05-18  9:45 sergiodj+buildbot
  2018-05-18  9:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18  9:45 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 4bba0fb1c6d391a217c25e44398a7e1c7090155f ***

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

PR23199, Invalid SHT_GROUP entry leads to group confusion

This patch prevents elf_next_in_group list pointer confusion when
SHT_GROUP sections specify other SHT_GROUP sections in their list of
group sections.

	PR 23199
	* elf.c (setup_group): Formatting.  Check that SHT_GROUP entries
	don't point at other SHT_GROUP sections.  Set shdr corresponding
	to invalid entry, to NULL rather than section 0.  Identify
	SHT_GROUP section index when reporting an error.  Cope with NULL
	shdr pointer.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] libbfd.h and libcoff.h include guards
@ 2018-05-18  4:54 sergiodj+buildbot
  2018-05-18  4:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18  4:54 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 0b4395434942ecc6f3006004784d19d9a4fbbf55 ***

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

libbfd.h and libcoff.h include guards

	* libbfd-in.h: Add include guard.
	* libcoff-in.h: Likewise.
	* doc/Makefile.am (libbfd.h, libcoff.h): Append another #endif.
	* doc/Makefile.in: Regenerate.
	* libbfd.h: Regenerate.
	* libcoff.h: Regenerate.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] opcodes sources should not include libbfd.h
@ 2018-05-18  4:22 sergiodj+buildbot
  2018-05-18  4:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-18  4:22 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 29e0f0a144fcabb6fa088c58b49e5924d7c43967 ***

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

opcodes sources should not include libbfd.h

	* nfp-dis.c: Don't #include libbfd.h.
	(init_nfp3200_priv): Use bfd_get_section_contents.
	(nit_nfp6000_mecsr_sec): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Make format_pieces recognize the \e escape sequence
@ 2018-05-17 17:59 sergiodj+buildbot
  2018-05-17 18:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-17 17:59 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT b17992c1c02a2d8a832a887c2de23a7f3ab869f8 ***

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

Make format_pieces recognize the \e escape sequence

I noticed that the printf command did not recognize the \e escape
sequence, used amongst other things to use colors:

  (gdb) printf "This is \e[32mgreen\e[m!\n"
  Unrecognized escape character \e in format string.

This patch makes format_pieces recognize it, which makes that command
print the expected result in glorious color.

I wrote a really simple unit test for format_pieces.
format_pieces::operator[] is unused so I removed it.  I added
format_piece::operator==, which is needed to compare vectors of
format_piece.

gdb/ChangeLog:

	PR cli/14975
	* Makefile.in (SUBDIR_UNITTESTS_SRCS): Add
	unittests/format_pieces-selftests.c.
	* common/format.h (format_piece) <operator==>: New.
	(format_pieces) <operator[]>: Remove.
	* common/format.c (format_pieces::format_pieces): Handle \e.
	* unittests/format_pieces-selftests.c: New.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Fix for dwz-related crash
@ 2018-05-17 17:06 sergiodj+buildbot
  2018-05-17 17:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-17 17:06 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 58f0c71853f98afe623ab89c4362682885905ebb ***

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

Fix for dwz-related crash

PR symtab/23010 reports a crash that occurs when using -readnow
on a dwz-generated debuginfo file.

The crash occurs because the DWARF has a partial CU with no language
set, and then a full CU that references this partial CU using
DW_AT_abstract_origin.

In this case, the partial CU is read by dw2_expand_all_symtabs using
language_minimal; but then this conflicts with the creation of the
block's symbol table in the C++ CU.

This patch fixes the problem by arranging for partial CUs not to be
read by -readnow.  I tend to think that it doesn't make sense to read
a partial CU in isolation -- they should only be read when imported
into some other CU.

In conjunction with some other patches I am going to post, this also
fixes the Rust -readnow crash that Jan reported.

There are two problems with this patch:

1. It is difficult to reason about.  There are many cases where I've
   patched the code to call init_cutu_and_read_dies with the flag set
   to "please do read partial units" -- but I find it difficult to be
   sure that this is always correct.

2. It is still missing a standalone test case.  This seemed hard.

2018-05-17  Tom Tromey  <tom@tromey.com>

	PR symtab/23010:
	* dwarf2read.c (load_cu, dw2_do_instantiate_symtab)
	(dw2_instantiate_symtab): Add skip_partial parameter.
	(dw2_find_last_source_symtab, dw2_map_expand_apply)
	(dw2_lookup_symbol, dw2_expand_symtabs_for_function)
	(dw2_expand_all_symtabs, dw2_expand_symtabs_with_fullname)
	(dw2_expand_symtabs_matching_one)
	(dw2_find_pc_sect_compunit_symtab)
	(dw2_debug_names_lookup_symbol)
	(dw2_debug_names_expand_symtabs_for_function): Update.
	(init_cutu_and_read_dies): Add skip_partial parameter.
	(process_psymtab_comp_unit, build_type_psymtabs_1)
	(process_skeletonless_type_unit, load_partial_comp_unit)
	(psymtab_to_symtab_1): Update.
	(load_full_comp_unit): Add skip_partial parameter.
	(process_imported_unit_die, dwarf2_read_addr_index)
	(follow_die_offset, dwarf2_fetch_die_loc_sect_off)
	(dwarf2_fetch_constant_bytes, dwarf2_fetch_die_type_sect_off)
	(read_signatured_type): Update.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] Updated simplified Chinese translation for the opcodes directory.
@ 2018-05-17 15:55 sergiodj+buildbot
  2018-05-17 15:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-17 15:55 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 809276d28ad0212dd5a3f9074090e1425e5e4d8e ***

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

Updated simplified Chinese translation for the opcodes directory.

opcodes	* po/zh_CN.po: Updated simplified Chinese translation.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
* [binutils-gdb] value.c: Remove unused variables
@ 2018-05-17 15:50 sergiodj+buildbot
  2018-05-17 15:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
  0 siblings, 1 reply; 5167+ messages in thread
From: sergiodj+buildbot @ 2018-05-17 15:50 UTC (permalink / raw)
  To: gdb-testers

*** TEST RESULTS FOR COMMIT 3e6188349fbf16e9da69837e5e1211537805e422 ***

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

value.c: Remove unused variables

Obvious patch to remove unused local variables (found by adding
-Wunused).  I didn't touch this one in value_fetch_lazy, because
check_typedef could have a desired side-effect.

  3743  struct type *type = check_typedef (value_type (val));

gdb/ChangeLog:

	* value.c (release_value): Remove unused variable.
	(record_latest_value): Likewise.
	(access_value_history): Likewise.
	(preserve_values): Likewise.


^ permalink raw reply	[flat|nested] 5167+ messages in thread
end of thread, other threads:[~2018-11-30  6:54 UTC | newest]

Thread overview: 5167+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-31 15:14 [binutils-gdb] arch-utils: Make the last endianness actually chosen sticky sergiodj+buildbot
2018-05-31 14:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 21:21 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-06-01  2:39 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-06-05  3:29 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-06-05  3:35 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-06-05  4:09 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-06-07  4:20 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-06-08 23:49 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
  -- strict thread matches above, loose matches on Subject: below --
2018-11-30  7:11 [binutils-gdb] PR23937, powerpc64le local ifunc IRELATIVE relocs are wrong sergiodj+buildbot
2018-11-30 10:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-29 23:31 [binutils-gdb] Fix leak in forward-search sergiodj+buildbot
2018-11-30  1:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-29 22:18 [binutils-gdb] Implement the "gdb_signal_to/from_target" gdbarch methods for FreeBSD sergiodj+buildbot
2018-11-30  1:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-29 21:41 [binutils-gdb] RISC-V: Add missing c.unimp instruction sergiodj+buildbot
2018-11-29 22:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-29 18:55 [binutils-gdb] Avoid buffer overflow in value_x_unop sergiodj+buildbot
2018-11-29 20:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-29 18:14 [binutils-gdb] Fix use-after-free in gdbserver sergiodj+buildbot
2018-11-29 19:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-29 13:41 [binutils-gdb] elf: Don't merge .note.gnu.property section in IR sergiodj+buildbot
2018-11-29 14:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-27 20:10 [binutils-gdb] RISC-V: Add .insn CA support sergiodj+buildbot
2018-11-27 21:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-27 19:07 [binutils-gdb] [ARM] Update knowledge of bfd architectures sergiodj+buildbot
2018-11-27 20:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-27 17:58 [binutils-gdb] MIPS/LD: Accept high-part relocations in PIC code with absolute symbols sergiodj+buildbot
2018-11-27 19:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-27 17:21 [binutils-gdb] MIPS/LD: Continue processing with refused relocations in PIC code sergiodj+buildbot
2018-11-27 18:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-27 15:46 [binutils-gdb] Initialize *uncompressed_align_pow_p to 0 sergiodj+buildbot
2018-11-27 16:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-27 13:47 [binutils-gdb] AArch64: Fix regression in Cortex A53 erratum when PIE. (PR ld/23904) sergiodj+buildbot
2018-11-27 14:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-26 22:26 [binutils-gdb] Fix spurious semicolon in sparc-linux-nat.c sergiodj+buildbot
2018-11-26 23:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-26 14:27 [binutils-gdb] Fix Solaris build sergiodj+buildbot
2018-11-26 14:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-25 23:41 [binutils-gdb] Implement timestamp'ed output on "make check" sergiodj+buildbot
2018-11-26  1:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-25 23:04 [binutils-gdb] Remove obsolete comments from field_fmt sergiodj+buildbot
2018-11-26  0:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-24 12:23 [binutils-gdb] Re-fix leak in source.c (open_source_file) sergiodj+buildbot
2018-11-24 13:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-23 14:34 [binutils-gdb] gdbserver: AArch64: Remove cannot_fetch/store_register sergiodj+buildbot
2018-11-23 16:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-22 18:39 [binutils-gdb] Fix follow_exec latent problem sergiodj+buildbot
2018-11-22 18:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-22 16:58 [binutils-gdb] Per-inferior thread list, thread ranges/iterators, down with ALL_THREADS, etc sergiodj+buildbot
2018-11-22 20:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-22 16:44 [binutils-gdb] Avoid find_thread_ptid with null_ptid sergiodj+buildbot
2018-11-22 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 21:16 [binutils-gdb] S12Z opcodes: Fix bug disassembling certain shift instructions sergiodj+buildbot
2018-11-22  2:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 17:41 [binutils-gdb] Make command-repeat work after gdb.execute sergiodj+buildbot
2018-11-22  0:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 17:24 [binutils-gdb] C++ify badness_vector, fix leaks sergiodj+buildbot
2018-11-21 17:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 17:05 [binutils-gdb] Fix linking MSP430 files created by gcc's LTO optimizer sergiodj+buildbot
2018-11-21 23:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 14:40 [binutils-gdb] gdb/riscv: Add target description support sergiodj+buildbot
2018-11-21 22:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 14:05 [binutils-gdb] valops.c: Overload resolution code: Rename parameters/locals sergiodj+buildbot
2018-11-21 20:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 13:51 [binutils-gdb] valops.c: Some more gdb::array_view sergiodj+buildbot
2018-11-21 20:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 13:48 [binutils-gdb] Eliminate make_symbol_overload_list-related globals & cleanup sergiodj+buildbot
2018-11-21 16:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21 13:16 [binutils-gdb] Use gdb:array_view in call_function_by_hand & friends sergiodj+buildbot
2018-11-21 14:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21  7:58 [binutils-gdb] gdb: Use string_printf to format int fields instead of a fixed size buffer sergiodj+buildbot
2018-11-21  7:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-21  6:21 [binutils-gdb] gdb: Respect field width and alignment for 'fmt' fields in CLI output sergiodj+buildbot
2018-11-21  6:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-20 23:25 [binutils-gdb] Add a test to verify info [functions|variables|types]|rbreak respect language_mode sergiodj+buildbot
2018-11-21  4:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-20 22:22 [binutils-gdb] Fix regression 'info variables' does not show minimal symbols sergiodj+buildbot
2018-11-20 22:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-20 21:54 [binutils-gdb] Test case for 'info variables|functions' with minimal symbols sergiodj+buildbot
2018-11-21  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-20 18:31 [binutils-gdb] GDB: S12Z: new function s12z_extract_return_value sergiodj+buildbot
2018-11-20 19:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-20  8:31 [binutils-gdb] GDB: S12Z: Add assertion sergiodj+buildbot
2018-11-20 10:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-19 23:28 [binutils-gdb] Change get_filename_and_charpos to return void sergiodj+buildbot
2018-11-20  1:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-19 22:58 [binutils-gdb] Fix inaccuracies in "info skip" help sergiodj+buildbot
2018-11-20  0:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-19 17:31 [binutils-gdb] Use std::forward_list for displaced_step_inferior_states sergiodj+buildbot
2018-11-19 18:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-19 16:20 [binutils-gdb] gdb.base/warning.exp tweaks sergiodj+buildbot
2018-11-19 18:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-18 17:46 [binutils-gdb] Fix ia64-linux-nat.c sergiodj+buildbot
2018-11-19 15:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-16 15:13 [binutils-gdb] Aarch64: Fix segfault when casting dummy calls sergiodj+buildbot
2018-11-16 18:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-16 14:16 [binutils-gdb] Use enum for return method for dummy calls sergiodj+buildbot
2018-11-16 15:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-15  1:08 [binutils-gdb] RISC-V: Handle vector type alignment sergiodj+buildbot
2018-11-15  1:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-14 23:47 [binutils-gdb] RISC-V: Fix unnamed arg alignment in registers sergiodj+buildbot
2018-11-15  3:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-14 23:34 [binutils-gdb] RISC-V: Give stack slots same align as XLEN sergiodj+buildbot
2018-11-15  0:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-14  0:45 [binutils-gdb] RISC-V: Improve linker error for FP mismatch sergiodj+buildbot
2018-11-14  1:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-13 14:26 [binutils-gdb] opcodes/nfp: Fix disassembly of crc[] with swapped operands sergiodj+buildbot
2018-11-14  0:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-13 13:15 [binutils-gdb] [ARM] Improve indentation of ARM architecture declarations sergiodj+buildbot
2018-11-13 14:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-12 13:38 [binutils-gdb] [BINUTILS, AARCH64, 5/8] Add Tag getting instruction in Memory Tagging Extension sergiodj+buildbot
2018-11-12 21:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-12 13:37 [binutils-gdb] [BINUTILS, AARCH64, 4/8] Add Tag setting instructions in Memory Tagging Extension sergiodj+buildbot
2018-11-12 20:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-12 13:37 [binutils-gdb] [BINUTILS, AARCH64, 3/8] Add Pointer Arithmetic instructions in Memory Tagging Extension sergiodj+buildbot
2018-11-12 17:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-12 13:36 [binutils-gdb] [BINUTILS, AARCH64, 2/8] Add Tag generation instructions in Memory Tagging Extension sergiodj+buildbot
2018-11-12 15:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-10  1:05 [binutils-gdb] Remove a VEC from remote.c sergiodj+buildbot
2018-11-10  3:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09 23:41 [binutils-gdb] Return scoped_fd from open_source_file and find_and_open_source sergiodj+buildbot
2018-11-10  0:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09 20:51 [binutils-gdb] Fix unsigned overflow in minsyms reader sergiodj+buildbot
2018-11-09 22:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09 17:09 [binutils-gdb] Fix a typo in iconv.m4 sergiodj+buildbot
2018-11-09 19:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09 16:53 [binutils-gdb] Correct comment concerning PE timestamp insertion sergiodj+buildbot
2018-11-09 18:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09 16:51 [binutils-gdb] Fixed warning from previous patch. Added Changelog sergiodj+buildbot
2018-11-09 17:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09 11:50 [binutils-gdb] [ARC] Fix local got entry list sergiodj+buildbot
2018-11-09 13:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09  2:36 [binutils-gdb] Capitalize "<TAB>" in require_record_target error sergiodj+buildbot
2018-11-09  2:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-09  0:05 [binutils-gdb] Avoid crash when calling warning too early sergiodj+buildbot
2018-11-09  1:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-08 16:30 [binutils-gdb] (AArch64) wrong value returned by "finish" for HFA sergiodj+buildbot
2018-11-08 17:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-08 10:32 [binutils-gdb] gdb/riscv: Update test to support targets without FP hardware sergiodj+buildbot
2018-11-08 12:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-08  1:36 [binutils-gdb] (Ada/tasking) fix array or string index out of range warning sergiodj+buildbot
2018-11-08  7:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07 19:25 [binutils-gdb] Add updated French and Portuguese translations sergiodj+buildbot
2018-11-07 20:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07 17:23 [binutils-gdb] Add support for new load commands added by Apple to the MACH-O file format sergiodj+buildbot
2018-11-07 18:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07 16:23 [binutils-gdb] gdb: Guard against NULL dereference in dwarf2_init_integer_type sergiodj+buildbot
2018-11-07 16:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07 11:08 [binutils-gdb] rx: Add target rx-*-linux sergiodj+buildbot
2018-11-07 11:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07  6:42 [binutils-gdb] [gdb] Fix gdb crash when reading core file sergiodj+buildbot
2018-11-07  9:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07  5:39 [binutils-gdb] RISC-V: Force variables to .data for code_elim sergiodj+buildbot
2018-11-07  7:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07  2:34 [binutils-gdb] Note that PT_GETREGS supplies SSTATUS for FreeBSD/riscv sergiodj+buildbot
2018-11-07  4:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-07  1:22 [binutils-gdb] Add support for a couple of new Mach-O commands sergiodj+buildbot
2018-11-07  3:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 23:52 [binutils-gdb] [BINUTILS, ARM] Add Armv8.5-A to select_arm_features and update macros sergiodj+buildbot
2018-11-07  2:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 21:18 [binutils-gdb] x86: correctly handle VPBROADCASTD with EVEX.W set outside of 64-bit mode sergiodj+buildbot
2018-11-07  0:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 18:07 [binutils-gdb] x86: correctly handle KMOVD with VEX.W set outside of 64-bit mode sergiodj+buildbot
2018-11-06 20:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 17:28 [binutils-gdb] x86: adjust {,E}VEX.W handling for PEXTR* / PINSR* sergiodj+buildbot
2018-11-06 18:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 14:45 [binutils-gdb] x86: fix various non-LIG templates sergiodj+buildbot
2018-11-06 15:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 14:03 [binutils-gdb] x86: allow {store} to select alternative {, }PEXTRW encoding sergiodj+buildbot
2018-11-06 14:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 12:32 [binutils-gdb] x86: add more VexWIG sergiodj+buildbot
2018-11-06 13:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-06 11:41 [binutils-gdb] x86: XOP VPHADD* / VPHSUB* are VEX.W0 sergiodj+buildbot
2018-11-06 12:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-04 18:25 [binutils-gdb] Return gdbpy_ref from gdbpy_get_varobj_pretty_printer sergiodj+buildbot
2018-11-04 20:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-04 16:10 [binutils-gdb] Return gdbpy_ref from gdb_py_object_from_*longest sergiodj+buildbot
2018-11-04 16:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-03 21:38 [binutils-gdb] OBVIOUS Fix a typo in ada-lang.c add_prefix_cmd for "set ada" sergiodj+buildbot
2018-11-03 21:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-03 19:46 [binutils-gdb] OBVIOUS Remove a useless const char *type and its initialization sergiodj+buildbot
2018-11-03 21:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-02 14:20 [binutils-gdb] QUIET flag initialization missing in 2 places sergiodj+buildbot
2018-11-02 17:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-02  5:31 [binutils-gdb] PR23850, strip should not discard/move .rela.plt in executable sergiodj+buildbot
2018-11-02  6:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-02  0:51 [binutils-gdb] RISC-V: Don't allow unaligned breakpoints sergiodj+buildbot
2018-11-02  4:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-01 23:19 [binutils-gdb] (Ada) fix "error in expression" when using watch -location command sergiodj+buildbot
2018-11-02  2:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-01 23:04 [binutils-gdb] remove trailing spaces in print-utils.c ("int_string" function) sergiodj+buildbot
2018-11-02  1:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-01 20:59 [binutils-gdb] Import mkdtemp gnulib module, fix mingw build sergiodj+buildbot
2018-11-01 21:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-11-01 11:34 [binutils-gdb] Reading signal handler frame in AIX sergiodj+buildbot
2018-11-01 11:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-31 19:06 [binutils-gdb] gdb/riscv: Fix failures on rv64 in gdb.arch/riscv-reg-aliases.exp test sergiodj+buildbot
2018-11-01  1:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-31 18:41 [binutils-gdb] [gdb/testsuite] Factor out lib/valgrind.exp sergiodj+buildbot
2018-11-01  0:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-31 17:26 [binutils-gdb] [gdb/testsuite] get_valueof: Don't output value in test name sergiodj+buildbot
2018-10-31 19:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-31 16:07 [binutils-gdb] [PowerPC] Include nat/linux-ptrace.h in native targets sergiodj+buildbot
2018-10-31 16:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-31 13:54 [binutils-gdb] gdb: Handle ICC's unexpected void return type sergiodj+buildbot
2018-10-31 14:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-30 21:22 [binutils-gdb] [src/erc32] Use ncurses instead of termcap on Cygwin too sergiodj+buildbot
2018-10-30 22:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-30 18:01 [binutils-gdb] Check return value of bfd_init sergiodj+buildbot
2018-10-30 17:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-30  7:55 [binutils-gdb] Remove relational operators from common/offset-type.h sergiodj+buildbot
2018-10-30 15:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-29 21:40 [binutils-gdb] Revert "GDB: Remote target can now accept the form unix::/path/to/socket." sergiodj+buildbot
2018-10-29 22:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-29 19:37 [binutils-gdb] Revert "GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested." sergiodj+buildbot
2018-10-30  4:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-29 19:19 [binutils-gdb] Revert "GDB: Only build for "unix:" connections if AF_LOCAL is supported." sergiodj+buildbot
2018-10-29 20:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-29 17:37 [binutils-gdb] Provide get_shell declaration in procfs.c sergiodj+buildbot
2018-10-29 18:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-29  8:20 [binutils-gdb] GDB: Only build for "unix:" connections if AF_LOCAL is supported sergiodj+buildbot
2018-10-29 15:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-28 11:12 [binutils-gdb] gdb/riscv: Add back missing braces in riscv-linux-nat.c sergiodj+buildbot
2018-10-28 20:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 20:36 [binutils-gdb] OBVIOUS Use report_unrecognized_option_error in 'demangle' and 'info macro' commands sergiodj+buildbot
2018-10-28  7:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:48 [binutils-gdb] Remove a bunch of usages of gdb_suppress_tests in 'runto_main' sergiodj+buildbot
2018-10-27 18:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:36 [binutils-gdb] Cache a copy of the user's shell on macOS sergiodj+buildbot
2018-10-28  5:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:30 [binutils-gdb] Do not reopen temporary files sergiodj+buildbot
2018-10-28  2:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:24 [binutils-gdb] Use mkostemp, not mkstemp sergiodj+buildbot
2018-10-28  1:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:18 [binutils-gdb] Move mkdir_recursive to common/filestuff.c sergiodj+buildbot
2018-10-28  0:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:16 [binutils-gdb] Move make_temp_filename to common/pathstuff.c sergiodj+buildbot
2018-10-27 22:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 18:10 [binutils-gdb] Unify shell-finding logic sergiodj+buildbot
2018-10-27 21:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 17:44 [binutils-gdb] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables] sergiodj+buildbot
2018-10-27 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 14:04 [binutils-gdb] Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP] sergiodj+buildbot
2018-10-27 18:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 13:37 [binutils-gdb] New cli-utils.h/.c function extract_info_print_args sergiodj+buildbot
2018-10-27 15:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 11:14 [binutils-gdb] Support AT_HWCAP2 on FreeBSD sergiodj+buildbot
2018-10-27 12:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27 10:13 [binutils-gdb] RISC-V: Linux signal frame support sergiodj+buildbot
2018-10-27 10:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27  8:57 [binutils-gdb] RISC-V: Linux signal frame support sergiodj+buildbot
2018-10-27  9:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27  6:36 [binutils-gdb] [PowerPC] Add support for EBB and PMU registers sergiodj+buildbot
2018-10-27  5:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-27  0:33 [binutils-gdb] Remove DEF_VECs from symtab.h sergiodj+buildbot
2018-10-27 13:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 22:08 [binutils-gdb] [PowerPC] Add support for HTM registers sergiodj+buildbot
2018-10-27  7:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 21:00 [binutils-gdb] [PowerPC] Reject tdescs with VSX and no FPU or Altivec sergiodj+buildbot
2018-10-27  7:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 20:29 [binutils-gdb] [PowerPC] Add support for TAR sergiodj+buildbot
2018-10-27  5:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 20:20 [binutils-gdb] [PowerPC] Add support for PPR and DSCR sergiodj+buildbot
2018-10-27  1:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 19:41 [binutils-gdb] [PowerPC] Refactor have_ initializers in rs6000-tdep.c sergiodj+buildbot
2018-10-27  0:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 19:41 [binutils-gdb] [PowerPC] Fix indentation in arch/ppc-linux-common.c sergiodj+buildbot
2018-10-26 23:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 19:07 [binutils-gdb] [PowerPC] Fix two if statements in gdb/ppc-linux-nat.c sergiodj+buildbot
2018-10-26 22:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 18:45 [binutils-gdb] [PowerPC] Remove rs6000_pseudo_register_reggroup_p sergiodj+buildbot
2018-10-26 20:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 18:31 [binutils-gdb] Add decfloat registers to float reggroup sergiodj+buildbot
2018-10-26 19:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 17:52 [binutils-gdb] [PowerPC] Don't zero-initialize vector register buffers sergiodj+buildbot
2018-10-26 18:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 17:28 [binutils-gdb] Zero-initialize linux note sections sergiodj+buildbot
2018-10-26 17:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 12:40 [binutils-gdb] Fix SYMBOL_LANGUAGE assertion failure on AIX sergiodj+buildbot
2018-10-26 16:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-26 11:01 [binutils-gdb] gdb/riscv: Remove redundant code, and catch more errors when accessing MISA sergiodj+buildbot
2018-10-26 11:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-25 16:08 [binutils-gdb] gdb/python: Make convert_values_to_python return gdbpy_ref<> sergiodj+buildbot
2018-10-25 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-25 15:12 [binutils-gdb] [gdb/testsuite] Rewrite valgrind-db-attach.exp to use vgdb sergiodj+buildbot
2018-10-25 18:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-25 12:19 [binutils-gdb] gdb/python: Make cmdpy_completer_helper return gdbpy_ref<> sergiodj+buildbot
2018-10-25 15:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-25 11:43 [binutils-gdb] gdb/riscv: Use correct regnum in riscv_linux_nat_target::fetch_registers sergiodj+buildbot
2018-10-25 14:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-25  2:40 [binutils-gdb] ELF: Hide symbols defined in discarded input sections sergiodj+buildbot
2018-10-25  3:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-24 17:35 [binutils-gdb] [gdb/testsuite] Log wait status on process no longer exists error sergiodj+buildbot
2018-10-24 16:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-24 15:12 [binutils-gdb] cmse_scan segfault sergiodj+buildbot
2018-10-24 16:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-24 13:40 [binutils-gdb] [gdb/testsuite] Rewrite catch-follow-exec.exp using gdb_test sergiodj+buildbot
2018-10-24 16:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-24 13:14 [binutils-gdb] [gdb/testsuite] Handle removed valgrind option --db-attach sergiodj+buildbot
2018-10-24 13:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 22:01 [binutils-gdb] Avoid GDB SIGTTOU on catch exec + set follow-exec-mode new (PR 23368) sergiodj+buildbot
2018-10-24  2:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 21:06 [binutils-gdb] Fix use-after-free in record_btrace_start_replaying sergiodj+buildbot
2018-10-24  0:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 16:56 [binutils-gdb] S/390: Support vector alignment hints sergiodj+buildbot
2018-10-24  0:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 15:59 [binutils-gdb] GDB: New target s12z sergiodj+buildbot
2018-10-23 22:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 15:43 [binutils-gdb] GDB: Remote target can now accept the form unix::/path/to/socket sergiodj+buildbot
2018-10-23 21:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 15:10 [binutils-gdb] GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested sergiodj+buildbot
2018-10-23 20:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 11:46 [binutils-gdb] PR23806, NULL pointer dereference in merge_strings sergiodj+buildbot
2018-10-23 16:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 11:28 [binutils-gdb] PR23805, NULL pointer dereference in elf_link_input_bfd sergiodj+buildbot
2018-10-23 15:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 10:54 [binutils-gdb] gdb/riscv: expect h/w watchpoints to trigger before the memory is written sergiodj+buildbot
2018-10-23 12:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-23 10:49 [binutils-gdb] gdb/riscv: Fix register access for register aliases sergiodj+buildbot
2018-10-23 11:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-22 22:02 [binutils-gdb] RISC-V: NaN-box FP values smaller than an FP register sergiodj+buildbot
2018-10-22 23:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-22 22:01 [binutils-gdb] RISC-V: Print FP regs as union of float types sergiodj+buildbot
2018-10-22 22:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-22 19:45 [binutils-gdb] S12Z: Disassembly: Fallback to show the address if the symbol table is empty sergiodj+buildbot
2018-10-22 20:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-22  2:44 [binutils-gdb] Allocate buffer with proper size in amd64_pseudo_register_{read_value, write} sergiodj+buildbot
2018-10-22  3:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-20 21:54 [binutils-gdb] [PUSHED/OBVIOUS] ensure help set print type gives the correct help sergiodj+buildbot
2018-10-20 23:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-20  9:57 [binutils-gdb] PR23788, objcopy: failed to find link section sergiodj+buildbot
2018-10-20 11:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-20  0:14 [binutils-gdb] Minor cleanups in tui-io.c sergiodj+buildbot
2018-10-20  0:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-19 19:31 [binutils-gdb] Clear static_links in reread_symbols sergiodj+buildbot
2018-10-19 19:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-19 17:09 [binutils-gdb] S390: Fix crash when remote tdesc doesn't define vec128 sergiodj+buildbot
2018-10-19 17:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-19 13:10 [binutils-gdb] Aarch64: Better termination checks for sigcontext reading sergiodj+buildbot
2018-10-19 19:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-19 11:35 [binutils-gdb] Testsuite: vla-optimized-out.exp is too pessimistic sergiodj+buildbot
2018-10-19 13:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-19 10:47 [binutils-gdb] Testsuite: compile-cplus-print.exp: Start inferior before compiling sergiodj+buildbot
2018-10-19 11:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-19 10:22 [binutils-gdb] Arm: Fix disassembler crashing on -b binary when thumb file and thumb not forced sergiodj+buildbot
2018-10-19 10:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-18  0:19 [binutils-gdb] gdb/ChangeLog: sergiodj+buildbot
2018-10-18  1:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-17 19:13 [binutils-gdb] Share the code to format "info proc mappings" entries for FreeBSD sergiodj+buildbot
2018-10-17 23:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-17 19:00 [binutils-gdb] gdb/MAINTAINERS: Add Rainer Orth as Solaris maintainer for GDB sergiodj+buildbot
2018-10-17 20:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-17  5:34 [binutils-gdb] PR23653, ld SIGSEGVs when attempts to link sparc object with x86_64 library sergiodj+buildbot
2018-10-17  8:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-16 21:32 [binutils-gdb] [gdb/testsuite] Rewrite catch-follow-exec.exp sergiodj+buildbot
2018-10-17  4:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-16 18:23 [binutils-gdb] AArch64: Fix error checking for SIMD udot (by element) sergiodj+buildbot
2018-10-16 21:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-16  8:51 [binutils-gdb] Simplify PR23110 PE_DEBUG_DATA size checks sergiodj+buildbot
2018-10-16  9:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-16  6:35 [binutils-gdb] PR23781, _bfd_pe_bfd_copy_private_bfd_data_common memory leak sergiodj+buildbot
2018-10-16  8:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-16  5:56 [binutils-gdb] Remove unnecessary casts from TUI sergiodj+buildbot
2018-10-16  6:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-15 20:07 [binutils-gdb] Add Alan Hayward as AArch64/ARM GDB maintainer sergiodj+buildbot
2018-10-15 20:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-15 13:05 [binutils-gdb] BFD_INIT_MAGIC sergiodj+buildbot
2018-10-15 14:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-13 13:40 [binutils-gdb] _bfd_clear_contents bounds checking sergiodj+buildbot
2018-10-13 14:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-12 20:49 [binutils-gdb] Fix buglets in gdb.trace/tspeed.{exp,c} sergiodj+buildbot
2018-10-12 21:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-12  0:20 [binutils-gdb] Fix pathname regexp in gdb.base/solib-vanish.exp sergiodj+buildbot
2018-10-12  0:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-11  9:34 [binutils-gdb] Fix interp::m_name resource leak found by Coverity sergiodj+buildbot
2018-10-11 10:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-10 14:19 [binutils-gdb] Add missing va_end found by Coverity sergiodj+buildbot
2018-10-10 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-10  7:45 [binutils-gdb] x86: fold Size{16,32,64} template attributes sergiodj+buildbot
2018-10-10  7:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-10  1:54 [binutils-gdb] Disable the undefined behavior sanitizer by default sergiodj+buildbot
2018-10-10  4:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-10  0:45 [binutils-gdb] [PATCH, BINUTULS, AARCH64, 9/9] Add SSBS to MSR/MRS sergiodj+buildbot
2018-10-10  2:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 18:12 [binutils-gdb] [PATCH, BINUTILS, AARCH64, 3/9] Add instruction SB for ARMv8.5-A sergiodj+buildbot
2018-10-09 19:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 16:52 [binutils-gdb] [PATCH, BINUTILS, AARCH64, 2/9] Add Data procoessing instructions for ARMv8.5-A sergiodj+buildbot
2018-10-09 18:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 16:35 [binutils-gdb] [PATCH, BINUTILS, AARCH64, 8/9] Add SCXTNUM_ELx and ID_PFR2_EL1 system registers sergiodj+buildbot
2018-10-10  1:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 15:52 [binutils-gdb] [PATCH, BINUTILS, AARCH64, 5/9] Add DC CVADP instruction sergiodj+buildbot
2018-10-09 22:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 15:38 [binutils-gdb] [PATCH, BINUTILS, AARCH64, 4/9] Add Execution and Data Restriction instructions sergiodj+buildbot
2018-10-09 20:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 14:06 [binutils-gdb] [gdb/testsuite] Fix target_supports_scheduler_locking raciness sergiodj+buildbot
2018-10-09 16:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09 13:37 [binutils-gdb] Fix buffer overrun found by Coverity sergiodj+buildbot
2018-10-09 14:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-09  7:39 [binutils-gdb] Do not place symbols into a discarded .dynsym sergiodj+buildbot
2018-10-09  8:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 23:07 [binutils-gdb] Remove unused variables from riscv-fbsd-tdep.c sergiodj+buildbot
2018-10-08 23:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 13:45 [binutils-gdb] Use p_vaddr_offset to set p_vaddr on segments without sections sergiodj+buildbot
2018-10-08 14:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 13:17 [binutils-gdb] AArch64: Replace C initializers with memset sergiodj+buildbot
2018-10-08 17:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 12:28 [binutils-gdb] x86: Don't add GNU_PROPERTY_X86_FEATURE_2_NEEDED for -z separate-code sergiodj+buildbot
2018-10-08 16:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 11:39 [binutils-gdb] Separate header PT_LOAD for -z separate-code sergiodj+buildbot
2018-10-08 15:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 11:10 [binutils-gdb] No PT_INTERP when .interp is zero size sergiodj+buildbot
2018-10-08 13:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-08 10:26 [binutils-gdb] Tidy elf_segment_map allocation sergiodj+buildbot
2018-10-08 11:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-07 10:25 [binutils-gdb] Add Inferior.architecture method sergiodj+buildbot
2018-10-07 10:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-07  6:18 [binutils-gdb] Fix Python gdb.Breakpoint.location crash sergiodj+buildbot
2018-10-07  6:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-07  5:46 [binutils-gdb] Update symbol domain and location values for Python sergiodj+buildbot
2018-10-07  9:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-07  5:20 [binutils-gdb] Do not accidentally include in-tree readline headers sergiodj+buildbot
2018-10-07  7:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-06 22:16 [binutils-gdb] Call nonl before wgetch in TUI sergiodj+buildbot
2018-10-06 23:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-06 16:25 [binutils-gdb] Update string expected from "help info proc" on gdb.base/info-proc.exp sergiodj+buildbot
2018-10-06 16:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-06  9:05 [binutils-gdb] Set correct SHT_NOTE type for .note.spu_name sergiodj+buildbot
2018-10-06  9:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-06  5:35 [binutils-gdb] Add -Wshadow=local sergiodj+buildbot
2018-10-06  5:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 18:32 [binutils-gdb] Simple -Wshadow=local fixes sergiodj+buildbot
2018-10-05 19:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 17:22 [binutils-gdb] Fix undefined behavior, don't pass NULL to fwrite sergiodj+buildbot
2018-10-05 18:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 16:53 [binutils-gdb] Fix -Wshadow=local warning in sol_thread_target::wait sergiodj+buildbot
2018-10-06 10:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 14:51 [binutils-gdb] or1k: Add the l.adrp insn and supporting relocations sergiodj+buildbot
2018-10-05 16:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 14:05 [binutils-gdb] or1k: Fix messages for relocations in shared libraries sergiodj+buildbot
2018-10-05 15:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 11:16 [binutils-gdb] [Arm, 3/3] Add Execution and Data Prediction instructions for AArch32 sergiodj+buildbot
2018-10-06  8:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05 11:03 [binutils-gdb] [Arm, 2/3] Add instruction SB for AArch32 sergiodj+buildbot
2018-10-06  7:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  6:49 [binutils-gdb] Shadowing fix in gdbscm_frame_read_var sergiodj+buildbot
2018-10-06  3:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  6:19 [binutils-gdb] Avoid shadowing in fdwalk sergiodj+buildbot
2018-10-06  2:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  5:52 [binutils-gdb] Avoid shadowing in linux-tdep.c sergiodj+buildbot
2018-10-05 23:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  5:39 [binutils-gdb] Use std::string in mdebugread.c sergiodj+buildbot
2018-10-05 21:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  5:25 [binutils-gdb] Avoid shadowing in gdbserver sergiodj+buildbot
2018-10-05 20:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  2:29 [binutils-gdb] Make complaint output prettier sergiodj+buildbot
2018-10-05  3:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  2:01 [binutils-gdb] Use filtered printing when reading symbols sergiodj+buildbot
2018-10-05  2:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-05  0:03 [binutils-gdb] Fix off-by-one error in complaint_internal sergiodj+buildbot
2018-10-05  1:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 22:49 [binutils-gdb] [gdb/python] Fix cpychecker error in pspy_solib_name sergiodj+buildbot
2018-10-05 12:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 22:09 [binutils-gdb] Avoid pagination in attach.exp sergiodj+buildbot
2018-10-04 22:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 21:49 [binutils-gdb] RISC-V: Delete zero-size .tdata.dyn section sergiodj+buildbot
2018-10-05  7:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 21:36 [binutils-gdb] Simplify complaints even more sergiodj+buildbot
2018-10-05  6:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 21:23 [binutils-gdb] Only print "no debugging symbols" message once sergiodj+buildbot
2018-10-05  5:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 21:11 [binutils-gdb] Clean up "Reading symbols" output sergiodj+buildbot
2018-10-05  4:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04 12:26 [binutils-gdb] Add self to gdb/MAINTAINERS sergiodj+buildbot
2018-10-04 21:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04  3:16 [binutils-gdb] Avoid two uninitialized warnings from gcc sergiodj+buildbot
2018-10-04 19:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04  3:01 [binutils-gdb] Do not pass NULL to memcpy sergiodj+buildbot
2018-10-04  7:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-04  0:06 [binutils-gdb] Remove struct keyword in range-based for sergiodj+buildbot
2018-10-04 18:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 23:50 [binutils-gdb] AArch64: Constraint disassembler and assembler changes sergiodj+buildbot
2018-10-04  2:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 23:29 [binutils-gdb] Avoid undefined behavior in ada_operator_length sergiodj+buildbot
2018-10-04 14:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 23:16 [binutils-gdb] Avoid undefined behavior in read_signed_leb128 sergiodj+buildbot
2018-10-04 13:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 22:40 [binutils-gdb] Avoid undefined behavior in extract_integer sergiodj+buildbot
2018-10-04 10:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 22:39 [binutils-gdb] AArch64: Add SVE constraints verifier sergiodj+buildbot
2018-10-04  1:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 20:36 [binutils-gdb] ELF: Group PT_NOTE segments by section alignments sergiodj+buildbot
2018-10-04  4:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 19:21 [binutils-gdb] AArch64: Wire through instr_sequence sergiodj+buildbot
2018-10-03 21:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 18:22 [binutils-gdb] AArch64: Mark sve instructions that require MOVPRFX constraints sergiodj+buildbot
2018-10-03 19:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 16:44 [binutils-gdb] Skip gdb ifunc tests on targets that don't support this feature sergiodj+buildbot
2018-10-03 17:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 11:23 [binutils-gdb] Fix the handling of inlined frames in DWARF debug info sergiodj+buildbot
2018-10-03 12:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03 10:16 [binutils-gdb] Updated Portuguese translations for the bfd/ and binutils/ subdirectories sergiodj+buildbot
2018-10-03 11:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03  9:01 [binutils-gdb] Make print_insn_s12z public sergiodj+buildbot
2018-10-03 10:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-03  1:47 [binutils-gdb] Use pulongest in aarch64-linux-tdep.c sergiodj+buildbot
2018-10-03  2:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-02 15:42 [binutils-gdb] RISC-V: Add fence.tso instruction sergiodj+buildbot
2018-10-02 17:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-02 14:34 [binutils-gdb] Allow remote debugging over a Unix local domain socket sergiodj+buildbot
2018-10-02 16:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-02  0:25 [binutils-gdb] Aarch64: Move pseudo defines to header sergiodj+buildbot
2018-10-02  3:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 16:56 [binutils-gdb] Remove ancient workaround sergiodj+buildbot
2018-10-01 19:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 15:05 [binutils-gdb] Add aarch64-sighandler-regs.exp test sergiodj+buildbot
2018-10-02  6:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 13:46 [binutils-gdb] [ARC] Fixed issue with DTSOFF relocs sergiodj+buildbot
2018-10-02  2:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 13:28 [binutils-gdb] Add workaround from gdbserver's gdb_proc_service.h to GDB sergiodj+buildbot
2018-10-01 15:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 13:03 [binutils-gdb] [ARC] PLT information was still being generated when symbol was forced_local sergiodj+buildbot
2018-10-02  0:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 12:31 [binutils-gdb] [ARC] Make sure global symbol is not an indirect or warning sergiodj+buildbot
2018-10-01 23:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 12:17 [binutils-gdb] [ARC] Improved robustness. Return FALSE in case of NULL pointer sergiodj+buildbot
2018-10-01 21:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01 11:02 [binutils-gdb] Move duplicated code to common/gdb_proc_service.h sergiodj+buildbot
2018-10-01 17:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01  9:54 [binutils-gdb] Copy configure option documentation to gdb.texinfo sergiodj+buildbot
2018-10-01 10:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-10-01  9:23 [binutils-gdb] Don't check HAVE_UNISTD_H sergiodj+buildbot
2018-10-01 12:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-29 15:33 [binutils-gdb] RISC-V: For PCREL_LO12, fix addend handling in auipc lookup sergiodj+buildbot
2018-09-30 17:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-29 14:35 [binutils-gdb] RISC-V: Allow pcrel_lo addends, error on addend overflow sergiodj+buildbot
2018-09-30 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-28 22:16 [binutils-gdb] Add "const" to a few locals in gdb sergiodj+buildbot
2018-09-28 22:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-28 12:23 [binutils-gdb] Fix PR gdb/20948: --write option to GDB causes segmentation fault sergiodj+buildbot
2018-09-28 23:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-28  0:31 [binutils-gdb] Check for negative argument in Type.template_argument sergiodj+buildbot
2018-09-27 11:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-26 16:59 [binutils-gdb] Report Python errors coming from gdb.post_event sergiodj+buildbot
2018-09-27 10:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-26 14:14 [binutils-gdb] Preserve sign when converting gdb.Value to Python int sergiodj+buildbot
2018-09-26 17:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-26 12:49 [binutils-gdb] Fix incorrect extraction of signed constants in nios2 disassembler sergiodj+buildbot
2018-09-26 13:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-25 21:14 [binutils-gdb] Also recognize __sighndlr on Solaris/x86 sergiodj+buildbot
2018-09-26 11:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-25 14:11 [binutils-gdb] Remove a spurious target_terminal::ours() from windows_nat_target::wait() sergiodj+buildbot
2018-09-25 21:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 17:58 [binutils-gdb] elf32-nds32: Don't define fls if it is provided by the system sergiodj+buildbot
2018-09-24 23:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 17:05 [binutils-gdb] csky-opc.h: Initialize fields of last array elements sergiodj+buildbot
2018-09-24 23:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 16:14 [binutils-gdb] Remove redundant test in update_inserted_breakpoint_locations sergiodj+buildbot
2018-09-24 21:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 15:38 [binutils-gdb] ELF: Don't include zero size sections at start of PT_NOTE segment sergiodj+buildbot
2018-09-24 16:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 12:44 [binutils-gdb] Add '_' in the match pattern sergiodj+buildbot
2018-09-24 13:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 10:35 [binutils-gdb] RS6000/BFD: Remove dead duplicate `config.bfd' target matchers sergiodj+buildbot
2018-09-24 11:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24 10:24 [binutils-gdb] ARC: Fix build errors with large constants and C89 sergiodj+buildbot
2018-09-24 12:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24  6:58 [binutils-gdb] Andes Technology has good news for you, we plan to update the nds32 port of binutils on upstream! sergiodj+buildbot
2018-09-24 10:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-24  6:13 [binutils-gdb] PR23685, buffer overflow sergiodj+buildbot
2018-09-24  9:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-23 18:47 [binutils-gdb] Provide pid_to_exec_file on Solaris (PR tdep/17903) sergiodj+buildbot
2018-09-24  6:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-23 16:28 [binutils-gdb] Handle missing Solaris auxv entries sergiodj+buildbot
2018-09-23 20:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-23 16:12 [binutils-gdb] Fold i386-v4-nat.c into i386-sol2-nat.c sergiodj+buildbot
2018-09-23 19:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-23 15:49 [binutils-gdb] Bug 23686, two segment faults in nm sergiodj+buildbot
2018-09-23 17:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-23 14:31 [binutils-gdb] Skip GDB tab-completion tests if no readline sergiodj+buildbot
2018-09-23 15:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-21 16:28 [binutils-gdb] Darwin: Handle unrelocated dyld sergiodj+buildbot
2018-09-21 18:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-21 15:17 [binutils-gdb] Add missing spaces after inet_ntop invocations sergiodj+buildbot
2018-09-21 15:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-20 17:14 [binutils-gdb] Logical short circuiting with argument lists sergiodj+buildbot
2018-09-20 18:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-20 16:28 [binutils-gdb] Fix /proc pathname sizes on Solaris sergiodj+buildbot
2018-09-20 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-20 10:41 [binutils-gdb] Carry the gnulib getcwd backport as a patch sergiodj+buildbot
2018-09-20 15:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-20 10:22 [binutils-gdb] Add support for 'info proc files' on FreeBSD core dumps sergiodj+buildbot
2018-09-20 12:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-20  3:28 [binutils-gdb] Generate aclocal-m4-deps.mk more deterministically and portably sergiodj+buildbot
2018-09-20  9:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 22:12 [binutils-gdb] Make the "info proc" documentation more consistent sergiodj+buildbot
2018-09-20 15:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 21:37 [binutils-gdb] Document the 'info proc files' command sergiodj+buildbot
2018-09-20 14:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 20:31 [binutils-gdb] Support 'info proc files' on live FreeBSD processes sergiodj+buildbot
2018-09-20 12:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 20:08 [binutils-gdb] Expect optional "arch=" when executing "-stack-list-frames" on gdb.arch/amd64-invalid-stack-top.exp sergiodj+buildbot
2018-09-20  3:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 19:48 [binutils-gdb] Add a new 'info proc files' subcommand of 'info proc' sergiodj+buildbot
2018-09-20 11:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 18:52 [binutils-gdb] Import gnulib's inet_ntop module sergiodj+buildbot
2018-09-20 10:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 17:19 [binutils-gdb] Use KF_PATH to verify the size of a struct kinfo_file sergiodj+buildbot
2018-09-20  8:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19 13:17 [binutils-gdb] Expect for "@" when doing "complete break ada" on gdb.ada/complete.exp sergiodj+buildbot
2018-09-19 17:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19  9:40 [binutils-gdb] Remove munmap_listp_free_cleanup sergiodj+buildbot
2018-09-19 15:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19  9:06 [binutils-gdb] Add a warning to the bfd library for when it encounters an ELF file with an invalid section size sergiodj+buildbot
2018-09-19 11:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-19  8:21 [binutils-gdb] Aarch64 SVE: Fix stack smashing when calling functions sergiodj+buildbot
2018-09-19 10:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 20:10 [binutils-gdb] [gdb/Python] Eliminate find_inferior_object sergiodj+buildbot
2018-09-18 20:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 17:57 [binutils-gdb] Do not pass -DNDEBUG to Python compilations in development mode sergiodj+buildbot
2018-09-18 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 17:40 [binutils-gdb] Check for gmp when checking for mpfr sergiodj+buildbot
2018-09-18 21:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 17:08 [binutils-gdb] Fix use-after-move in compile/compile-cplus-types.c sergiodj+buildbot
2018-09-18 17:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 15:08 [binutils-gdb] x86: Set EVex=2 on EVEX.128 only vmovd and vmovq sergiodj+buildbot
2018-09-18 15:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 14:47 [binutils-gdb] x86: Update disassembler for VexWIG sergiodj+buildbot
2018-09-18 14:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18 13:14 [binutils-gdb] x86: Set Vex=1 on VEX.128 only vmovd and vmovq sergiodj+buildbot
2018-09-18 15:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18  9:20 [binutils-gdb] Update get_standard_cache_dir for macOS sergiodj+buildbot
2018-09-18  9:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18  7:31 [binutils-gdb] x86: Replace VexW=3 with VexWIG sergiodj+buildbot
2018-09-18  7:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18  4:08 [binutils-gdb] Make save_infcall_*_state return unique pointers sergiodj+buildbot
2018-09-18  4:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18  2:42 [binutils-gdb] Remove cleanup from infrun.c sergiodj+buildbot
2018-09-18  2:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-18  1:10 [binutils-gdb] Don't steal references in the gdb Python code sergiodj+buildbot
2018-09-18  2:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 20:34 [binutils-gdb] Sort objects in gdb and gdbserver Makefiles sergiodj+buildbot
2018-09-17 20:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 15:20 [binutils-gdb] S12Z: Set the source mask value of all howtos to zero sergiodj+buildbot
2018-09-17 15:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 13:47 [binutils-gdb] Remove CPYCHECKER_RETURNS_BORROWED_REF sergiodj+buildbot
2018-09-17 15:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 13:40 [binutils-gdb] Change thread_to_thread_object to return a new reference sergiodj+buildbot
2018-09-17 14:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 12:57 [binutils-gdb] Change pspace_to_pspace_object to return a new reference sergiodj+buildbot
2018-09-17 14:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 12:25 [binutils-gdb] Use GNU style for metasyntactic variables in gdbserver sergiodj+buildbot
2018-09-17 13:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 12:03 [binutils-gdb] Use GNU style for metasyntactic variables in gdb sergiodj+buildbot
2018-09-17 12:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17 11:30 [binutils-gdb] Expand "show disassembler-options" output sergiodj+buildbot
2018-09-17 12:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17  4:32 [binutils-gdb] x86: Set VexW=3 on AVX vrsqrtss sergiodj+buildbot
2018-09-17  4:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17  2:36 [binutils-gdb] Change get_inferior_args to return const char * sergiodj+buildbot
2018-09-17  2:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-17  1:22 [binutils-gdb] x86: Set Vex=1 on VEX.128 only vmovq sergiodj+buildbot
2018-09-17  1:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-16  7:12 [binutils-gdb] Fix possible exception leak in python.c sergiodj+buildbot
2018-09-16  7:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-16  6:00 [binutils-gdb] Provide type_align gdbarch function for nios2 sergiodj+buildbot
2018-09-16  6:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15 20:32 [binutils-gdb] PR ld/21375: MIPS: Fix non-zero run-time value for undefined weaks sergiodj+buildbot
2018-09-15 20:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15 19:03 [binutils-gdb] x86: Support VEX/EVEX WIG encoding sergiodj+buildbot
2018-09-15 19:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15 17:16 [binutils-gdb] x86: Handle unsupported static rounding in vcvt[u]si2sd in 32-bit mode sergiodj+buildbot
2018-09-15 17:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15 16:19 [binutils-gdb] x86: Properly decode EVEX.W in vcvt[u]si2s[sd] in 32-bit mode sergiodj+buildbot
2018-09-15 16:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15 11:06 [binutils-gdb] i386: Reformat OP_E_memory sergiodj+buildbot
2018-09-15 12:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15  9:45 [binutils-gdb] Remove an unnecessary block in call_function_by_hand_dummy sergiodj+buildbot
2018-09-15 11:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15  9:05 [binutils-gdb] csky: Support PC relative diff relocation sergiodj+buildbot
2018-09-15 10:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15  4:21 [binutils-gdb] PR23425, unresolved symbol diagnostic sergiodj+buildbot
2018-09-15  5:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15  3:58 [binutils-gdb] x86: fold CRC32 templates sergiodj+buildbot
2018-09-15  4:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15  1:00 [binutils-gdb] Remove cleanup from try_open_exec_file sergiodj+buildbot
2018-09-15  1:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-15  0:20 [binutils-gdb] Testsuite: Add gdb_simple_compile sergiodj+buildbot
2018-09-15  3:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 22:10 [binutils-gdb] python: Add Progspace.objfiles method sergiodj+buildbot
2018-09-14 22:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 21:28 [binutils-gdb] python: Add Inferior.progspace property sergiodj+buildbot
2018-09-14 21:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 18:27 [binutils-gdb] python: Provide textual representation for Inferior and Objfile sergiodj+buildbot
2018-09-14 18:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 17:56 [binutils-gdb] x86: Remove VexW=1 from WIG VEX movq and vmovq sergiodj+buildbot
2018-09-14 18:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 15:05 [binutils-gdb] x86: drop bogus IgnoreSize from AVX512_4* insns sergiodj+buildbot
2018-09-14 15:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 14:59 [binutils-gdb] Generate more tags in gdb/testsuite/Makefile sergiodj+buildbot
2018-09-15  2:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 13:59 [binutils-gdb] Return std::string from gdb_bfd_errmsg sergiodj+buildbot
2018-09-14 23:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 13:48 [binutils-gdb] Remove cleanup from procfs.c sergiodj+buildbot
2018-09-14 22:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 13:04 [binutils-gdb] x86: drop bogus IgnoreSize from AVX512VL insns sergiodj+buildbot
2018-09-14 13:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14 12:05 [binutils-gdb] x86: drop bogus IgnoreSize from AVX512F insns sergiodj+buildbot
2018-09-14 12:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  8:17 [binutils-gdb] Fix crash with empty Rust enum sergiodj+buildbot
2018-09-14 19:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  7:16 [binutils-gdb] Add "contrib" to the list of GDB support dirs (on src-release.sh) sergiodj+buildbot
2018-09-14 19:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  6:38 [binutils-gdb] x86: drop bogus IgnoreSize from SSE4.2 insns sergiodj+buildbot
2018-09-14  6:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  4:41 [binutils-gdb] x86: drop bogus IgnoreSize from a few further insns sergiodj+buildbot
2018-09-14 16:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  3:57 [binutils-gdb] x86: drop bogus IgnoreSize from AVX512DQ insns sergiodj+buildbot
2018-09-14 14:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  3:49 [binutils-gdb] x86: drop bogus IgnoreSize from AVX512BW insns sergiodj+buildbot
2018-09-14 13:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  2:48 [binutils-gdb] x86: drop bogus IgnoreSize from SHA insns sergiodj+buildbot
2018-09-14 11:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  2:28 [binutils-gdb] x86: drop bogus IgnoreSize from AVX2 insns sergiodj+buildbot
2018-09-14 10:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  2:04 [binutils-gdb] x86: drop bogus IgnoreSize from AVX insns sergiodj+buildbot
2018-09-14  9:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  1:46 [binutils-gdb] x86: drop bogus IgnoreSize from GNFI insns sergiodj+buildbot
2018-09-14  9:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  1:38 [binutils-gdb] x86: drop bogus IgnoreSize from PCLMUL/VPCLMUL insns sergiodj+buildbot
2018-09-14  7:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-14  0:04 [binutils-gdb] x86: drop bogus IgnoreSize from SSE4.1 insns sergiodj+buildbot
2018-09-14  5:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 23:42 [binutils-gdb] x86: drop bogus IgnoreSize from SSE3 insns sergiodj+buildbot
2018-09-14  4:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 23:25 [binutils-gdb] x86: drop bogus IgnoreSize from SSE2 insns sergiodj+buildbot
2018-09-14  2:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 23:12 [binutils-gdb] x86: drop unnecessary {,No}Rex64 sergiodj+buildbot
2018-09-14  1:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 22:57 [binutils-gdb] x86: also allow D on 3-operand insns sergiodj+buildbot
2018-09-14  0:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 22:29 [binutils-gdb] x86-64: bndmk, bndldx, and bndstx don't allow RIP-relative addressing sergiodj+buildbot
2018-09-13 22:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 20:29 [binutils-gdb] Remove unused "tmp" variable sergiodj+buildbot
2018-09-13 21:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 19:20 [binutils-gdb] Fix a typo in a comment sergiodj+buildbot
2018-09-13 19:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 18:38 [binutils-gdb] python: Add tests for trying to use an invalid Inferior object sergiodj+buildbot
2018-09-13 18:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 17:42 [binutils-gdb] Move 'is_regular_file' from common-utils.c to filestuff.c sergiodj+buildbot
2018-09-13 18:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 16:49 [binutils-gdb] Add debug output about skipping files and functions sergiodj+buildbot
2018-09-13 17:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 15:36 [binutils-gdb] Testsuite: Add gdb_can_simple_compile sergiodj+buildbot
2018-09-13 15:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 13:35 [binutils-gdb] Darwin: set startup-with-shell to off on Sierra and later sergiodj+buildbot
2018-09-13 13:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 12:56 [binutils-gdb] Darwin: fix SIGTRAP when debugging sergiodj+buildbot
2018-09-13 13:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13 12:17 [binutils-gdb] [testsuite] Fix dg-extract-results.sh path sergiodj+buildbot
2018-09-13 12:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13  0:34 [binutils-gdb] Fix PR gdb/23558: Use system's 'getcwd' when cross-compiling GDB sergiodj+buildbot
2018-09-13 10:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-13  0:01 [binutils-gdb] Revert "Update gnulib to current upstream master" sergiodj+buildbot
2018-09-13  9:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-12 19:01 [binutils-gdb] Remove unused variable in record-btrace.c sergiodj+buildbot
2018-09-13  9:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-12 14:53 [binutils-gdb] (Ada) Fix resolving of homonym components in tagged types sergiodj+buildbot
2018-09-13  1:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-12 12:16 [binutils-gdb] (Ada) Cleanup code by using ada_is_access_to_unconstrained_array call sergiodj+buildbot
2018-09-13  1:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-12 12:06 [binutils-gdb] (Ada) Fix printing of access to unconstrained arrays sergiodj+buildbot
2018-09-13  0:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-12 11:28 [binutils-gdb] (Ada) New function ada_is_access_to_unconstrained_array sergiodj+buildbot
2018-09-12 23:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-11 12:01 [binutils-gdb] Fix "make install-strip" failure to install gdb-add-index.sh sergiodj+buildbot
2018-09-11 14:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10 17:59 [binutils-gdb] Make py-prettyprint.exp test names unique sergiodj+buildbot
2018-09-11 11:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10 16:47 [binutils-gdb] Allow a pretty-printer without a to_string method sergiodj+buildbot
2018-09-11 11:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10 10:42 [binutils-gdb] (Ada) fix handling of expression with parameterless function call sergiodj+buildbot
2018-09-11 11:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10  9:19 [binutils-gdb] ada-lang.c::ada_value_cast: remove unnecessary parentheses sergiodj+buildbot
2018-09-11 11:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10  9:00 [binutils-gdb] (Ada) slightly incorrect bounds for type of array indexed by enum sergiodj+buildbot
2018-09-11 11:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10  7:38 [binutils-gdb] minor reformatting in ada-lang.c::ada_to_fixed_value sergiodj+buildbot
2018-09-11  7:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10  7:19 [binutils-gdb] Handle PPC64 function descriptor in Ada decoding sergiodj+buildbot
2018-09-11  4:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10  3:54 [binutils-gdb] (Ada) infinite loop when hitting unhandled exception catchpoint sergiodj+buildbot
2018-09-11  4:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-10  0:24 [binutils-gdb] (Ada) assigning packed array aggregate with variable as component sergiodj+buildbot
2018-09-11  2:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-09  7:50 [binutils-gdb] S12Z: Make disassebler work for --enable-targets=all config sergiodj+buildbot
2018-09-11  1:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-09  4:35 [binutils-gdb] gdb/testsuite: Make test names unique in gdb.base/watchpoint.exp sergiodj+buildbot
2018-09-11  1:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-08 22:13 [binutils-gdb] compile: Remove non-const reference parameters sergiodj+buildbot
2018-09-11  1:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-08 22:11 [binutils-gdb] Remove unused tui_win_element::highlight sergiodj+buildbot
2018-09-11  1:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-08 17:19 [binutils-gdb] Remove unused tui_win_info::detail::opaque sergiodj+buildbot
2018-09-11  1:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-08  8:49 [binutils-gdb] Make -Wformat-nonliteral work with gcc sergiodj+buildbot
2018-09-11  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-08  8:41 [binutils-gdb] Disable -Wformat-nonliteral in parts of printcmd.c sergiodj+buildbot
2018-09-10 23:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-07 15:23 [binutils-gdb] Remove unnecessary casts from cli-cmds.c sergiodj+buildbot
2018-09-10 23:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-07  3:16 [binutils-gdb] [gdb/exp] Handle DW_OP_GNU_variable_value refs to abstract dies sergiodj+buildbot
2018-09-10 23:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-06  3:54 [binutils-gdb] bfd, sparc: avoid duplicated error messages on invalid relocations sergiodj+buildbot
2018-09-10 23:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-06  3:53 [binutils-gdb] bfd, sparc: issue an error when reading relocations with invalid symbol references sergiodj+buildbot
2018-09-10 23:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-05 22:50 [binutils-gdb] Automatically update "aclocal_m4_deps" when updating gnulib sergiodj+buildbot
2018-09-10 20:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-05 15:32 [binutils-gdb] Simplify ada-exp.o rule sergiodj+buildbot
2018-09-10 18:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-05 12:05 [binutils-gdb] Remove obsolete comments from Makefiles sergiodj+buildbot
2018-09-10 16:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-05  9:57 [binutils-gdb] Fix batch exit status test failure on Fedora 28 sergiodj+buildbot
2018-09-10 16:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-05  9:07 [binutils-gdb] gdb/riscv: Fix an ARI warning sergiodj+buildbot
2018-09-10 16:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-04 20:01 [binutils-gdb] gdb/riscv: Provide non-DWARF stack unwinder sergiodj+buildbot
2018-09-10 15:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-04 19:39 [binutils-gdb] gdb: Extend the trad-frame API sergiodj+buildbot
2018-09-10 15:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-04 18:26 [binutils-gdb] PR23595, simple objcopy of executable failure for msp430-elf sergiodj+buildbot
2018-09-10  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-02  6:57 [binutils-gdb] Allow an IR object with unknown architecture sergiodj+buildbot
2018-09-09 23:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-01  4:41 [binutils-gdb] RISC-V: Correct the requirement of compressed floating point instructions sergiodj+buildbot
2018-09-09 22:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-09-01  1:47 [binutils-gdb] Fix a small bug in gdb.rust/simple.rs sergiodj+buildbot
2018-09-09 10:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-31 23:08 [binutils-gdb] Regenerate gdbarch.h sergiodj+buildbot
2018-09-09  8:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-31 22:25 [binutils-gdb] Add comment describing continuable/steppable/non-steppable watchpoints sergiodj+buildbot
2018-09-09  7:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-31 20:14 [binutils-gdb] Update gnulib/Makefile.in:aclocal_m4_deps sergiodj+buildbot
2018-09-09  7:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-31 19:39 [binutils-gdb] PowerPC64 higher REL16 relocations sergiodj+buildbot
2018-09-09  7:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-31 19:26 [binutils-gdb] Rearrange ppc_size_one_stub and correct _notoc stub examples sergiodj+buildbot
2018-09-09  7:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-31 16:33 [binutils-gdb] RISC-V: Allow instruction require more than one extension sergiodj+buildbot
2018-09-09  7:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30 22:32 [binutils-gdb] gdb/riscv: Extend instruction decode to cover more instructions sergiodj+buildbot
2018-09-09  7:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30 21:42 [binutils-gdb] gdb/riscv: remove extra caching of misa register sergiodj+buildbot
2018-09-09  6:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30 21:26 [binutils-gdb] gdb: Ensure compiler doesn't optimise variable out in test sergiodj+buildbot
2018-09-09  6:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30 20:30 [binutils-gdb] Fix compile-cplus-types.c build errors sergiodj+buildbot
2018-09-09  5:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30  1:51 [binutils-gdb] Add new search_symbols_multiple API sergiodj+buildbot
2018-09-09  4:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30  1:27 [binutils-gdb] Use block_symbol in linespec APIs sergiodj+buildbot
2018-09-09  3:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30  1:07 [binutils-gdb] Change decode_compound_collector to use std::vector sergiodj+buildbot
2018-09-09  3:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30  0:47 [binutils-gdb] Change `minimal_symbols' to std::vector in linespec.c structures sergiodj+buildbot
2018-09-09  3:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-30  0:11 [binutils-gdb] Change `function_symbols' to std::vector sergiodj+buildbot
2018-09-09  3:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 22:41 [binutils-gdb] Fix windows-nat.c for -Wnarrowing sergiodj+buildbot
2018-09-09  3:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 22:36 [binutils-gdb] [MIPS] Add Loongson 3A2000/3A3000 proccessor support sergiodj+buildbot
2018-09-09  3:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 21:44 [binutils-gdb] sparc/leon: add support for partial write psr instruction sergiodj+buildbot
2018-09-09  3:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 20:38 [binutils-gdb] Fix riscv-linux native gdb build failure sergiodj+buildbot
2018-09-09  3:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 19:52 [binutils-gdb] [MIPS/GAS] Split Loongson EXT Instructions from loongson3a sergiodj+buildbot
2018-09-09  3:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 18:27 [binutils-gdb] Indicate batch mode failures by exiting with nonzero status sergiodj+buildbot
2018-09-09  3:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 17:20 [binutils-gdb] Remove newline at end of warning message sergiodj+buildbot
2018-09-09  3:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 14:45 [binutils-gdb] [MIPS/GAS] Split Loongson CAM Instructions from loongson3a sergiodj+buildbot
2018-09-09  2:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 14:27 [binutils-gdb] infcall-nested-structs: Test up to five fields sergiodj+buildbot
2018-09-09  2:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 13:59 [binutils-gdb] Aarch64: Float register detection for return values sergiodj+buildbot
2018-09-09  2:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29 13:46 [binutils-gdb] Aarch64: Float register detection for _push_dummy_call sergiodj+buildbot
2018-09-09  2:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-29  3:17 [binutils-gdb] Get rid of -Wodr warning (PR build/23399) sergiodj+buildbot
2018-09-09  2:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-28 23:33 [binutils-gdb] Modify gdb.base/commands.exp to test multi breakpoints command clearing sergiodj+buildbot
2018-09-09  2:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-28 23:18 [binutils-gdb] Fix regression for multi breakpoints command line clearing sergiodj+buildbot
2018-09-09  2:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-28 22:22 [binutils-gdb] Remove some uses of VEC from parsers sergiodj+buildbot
2018-09-09  2:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-28 18:35 [binutils-gdb] Implement struct type_stack with a vector sergiodj+buildbot
2018-09-09  1:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-28  2:23 [binutils-gdb] x86: Don't mask out the GNU_PROPERTY_X86_UINT32_VALID bit sergiodj+buildbot
2018-09-08 23:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27 23:36 [binutils-gdb] Remove -Wno-narrowing from warnings.m4 sergiodj+buildbot
2018-09-08 23:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27 23:16 [binutils-gdb] Avoid -Wnarrowing warnings in aarch64-linux-tdep.c sergiodj+buildbot
2018-09-08 23:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27 22:23 [binutils-gdb] Avoid -Wnarrowing warnings in ppc64-tdep.c sergiodj+buildbot
2018-09-08 22:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27 21:29 [binutils-gdb] Avoid -Wnarrowing warnings in struct tramp_frame instances sergiodj+buildbot
2018-09-08 22:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27 20:41 [binutils-gdb] Use CORE_ADDR_MAX in various "breaks" arrays sergiodj+buildbot
2018-09-08 22:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27 20:13 [binutils-gdb] Avoid -Wnarrowing warnings from quote_char() sergiodj+buildbot
2018-09-08 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27  8:34 [binutils-gdb] Make ada_tasks_inferior_data::task_list an std::vector sergiodj+buildbot
2018-09-08 22:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-27  8:30 [binutils-gdb] Make ada-lang.c::add_angle_brackets return an std::string sergiodj+buildbot
2018-09-08 22:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-26  1:39 [binutils-gdb] Initialize variable in py_get_event_thread sergiodj+buildbot
2018-09-08  9:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-25 23:27 [binutils-gdb] elf: Check for corrupt symbol version info sergiodj+buildbot
2018-09-08  8:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-25  0:03 [binutils-gdb] gdb/python: Use copy-initialization more when possible sergiodj+buildbot
2018-09-07 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24 23:08 [binutils-gdb] Fix 8.2 regression in gdb.python/py-evthreads.exp w/ gdbserver (PR gdb/23379) sergiodj+buildbot
2018-09-07 22:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24 15:00 [binutils-gdb] x86: Update GNU_PROPERTY_X86_XXX macros sergiodj+buildbot
2018-09-07 22:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24 14:05 [binutils-gdb] x86: Add GNU_PROPERTY_X86_UINT32_VALID sergiodj+buildbot
2018-09-07 21:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24  9:28 [binutils-gdb] Test case for functions with non-contiguous ranges sergiodj+buildbot
2018-09-07 21:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24  2:24 [binutils-gdb] Add support for non-contiguous blocks to find_pc_partial_function sergiodj+buildbot
2018-09-07 13:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24  0:42 [binutils-gdb] Introduce find_function_entry_range_from_pc and use it in infrun.c sergiodj+buildbot
2018-09-07 21:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-24  0:17 [binutils-gdb] Disassemble blocks with non-contiguous ranges sergiodj+buildbot
2018-09-07 14:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23 23:54 [binutils-gdb] Record explicit block ranges from dwarf2read.c sergiodj+buildbot
2018-09-07 12:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23 23:42 [binutils-gdb] Add block range data structure for blocks with non-contiguous address ranges sergiodj+buildbot
2018-09-07 11:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23 18:50 [binutils-gdb] Avoid problems with plugins being loaded multiple times sergiodj+buildbot
2018-09-07 10:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23 15:47 [binutils-gdb] Darwin: fix bad loop incrementation sergiodj+buildbot
2018-09-07  7:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23 15:12 [binutils-gdb] PowerPC64 "call lacks nop" sergiodj+buildbot
2018-09-06 23:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23 12:59 [binutils-gdb] Replace unworkable code in HPPA relocs handelr with an assertion sergiodj+buildbot
2018-09-06 22:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23  4:40 [binutils-gdb] Fix "unresolved reloc" error for NOTOC relocs sergiodj+buildbot
2018-09-06 18:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23  4:23 [binutils-gdb] Make read_program_headers_from_bfd return a gdb::byte_vector sergiodj+buildbot
2018-09-06 15:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-23  0:28 [binutils-gdb] bfd/development.sh: Add experimental sergiodj+buildbot
2018-09-06 14:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22 19:32 [binutils-gdb] Use the correct constants when setting the section type of HPPA unwind sections sergiodj+buildbot
2018-09-06 13:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22 18:38 [binutils-gdb] Make read_program_header return a gdb::byte_vector sergiodj+buildbot
2018-09-06 14:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22 15:34 [binutils-gdb] Fix restoring of inferior terminal settings sergiodj+buildbot
2018-09-06 14:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22 15:18 [binutils-gdb] Replace xstrvprintf usages with string_vprintf sergiodj+buildbot
2018-09-06 14:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22  9:30 [binutils-gdb] Fix AArch64 stub layout algorithm to allow for the fact that section layut might change a stub's target location sergiodj+buildbot
2018-09-06 13:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22  8:54 [binutils-gdb] Aarch64 SVE VG is Vector Granule sergiodj+buildbot
2018-09-06 12:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22  8:32 [binutils-gdb] Add AArch64 SVE to NEWS and GDB manual sergiodj+buildbot
2018-09-06 12:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-22  6:38 [binutils-gdb] S12Z: Rename reloc R_S12Z_UKNWN_3 to R_S12Z_EXT18 and implement according to recently inferred information about this reloc sergiodj+buildbot
2018-09-06 11:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-21 21:16 [binutils-gdb] Don't throw Scheme exceptions with live std::vector objects sergiodj+buildbot
2018-09-06 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-21 21:01 [binutils-gdb] Fix running objcopy on Mach-O binaries sergiodj+buildbot
2018-09-06 11:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-21 11:56 [binutils-gdb] Use operand->extract to provide defaults for optional PowerPC operands sergiodj+buildbot
2018-09-06  6:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-21  7:49 [binutils-gdb] PowerPC HOWTOs sergiodj+buildbot
2018-09-06  4:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-21  7:05 [binutils-gdb] Delete NEWHOWTO and tidy some uses of reloc_howto_struct sergiodj+buildbot
2018-09-06  3:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-21  6:54 [binutils-gdb] Fix s12z test regexps sergiodj+buildbot
2018-09-05 23:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-20  1:05 [binutils-gdb] Don't init array at run time sergiodj+buildbot
2018-09-05 11:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-20  0:54 [binutils-gdb] Tidy bit twiddling sergiodj+buildbot
2018-09-05 11:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-20  0:43 [binutils-gdb] Balance parentheses in expression sergiodj+buildbot
2018-09-05 10:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-19 15:21 [binutils-gdb] Fix debugging of stripped PIE executables with padded PT_TLS sergiodj+buildbot
2018-09-05 10:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-18 23:19 [binutils-gdb] Test case for DW_OP_GNU_variable_value sergiodj+buildbot
2018-09-05  8:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-18 21:56 [binutils-gdb] Add support of DW_OP_GNU_variable_value to DWARF assembler sergiodj+buildbot
2018-09-05  8:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-18 20:51 [binutils-gdb] Add support for DW_OP_GNU_variable_value sergiodj+buildbot
2018-09-05  7:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-18  6:31 [binutils-gdb] Opcodes: (BRCLR / BRSET) Disassemble reserved codes instead of aborting sergiodj+buildbot
2018-09-05  6:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-18  6:19 [binutils-gdb] S12Z: Move opcode header to public include directory sergiodj+buildbot
2018-09-05  5:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-17 23:39 [binutils-gdb] Remove "repeat" argument from command_line_input sergiodj+buildbot
2018-09-05  1:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-17 23:38 [binutils-gdb] Fix use-after-free in number_or_range_parser sergiodj+buildbot
2018-09-05  1:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-17 11:11 [binutils-gdb] x86: Remove empty X86_FEATURE_1_AND property sergiodj+buildbot
2018-09-05  1:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-16 13:56 [binutils-gdb] Correct elf64-ppc.c linkage stub comment and formatting fixes sergiodj+buildbot
2018-09-05  0:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-15 17:01 [binutils-gdb] Use pulongest in aarch64-linux-tdep.c sergiodj+buildbot
2018-09-05  0:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-14 14:19 [binutils-gdb] MI: Add -a option to the "-data-disassemble" command sergiodj+buildbot
2018-09-05  0:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-13 16:16 [binutils-gdb] Define _FORTIFY_SOURCE in common-defs.h sergiodj+buildbot
2018-09-04 23:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-13 15:01 [binutils-gdb] bfd: Move elf-properties.lo to BFD32_LIBS sergiodj+buildbot
2018-09-04 23:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-13 10:33 [binutils-gdb] Detect SVE when reading aarch64 core files sergiodj+buildbot
2018-09-04 23:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-13  9:34 [binutils-gdb] Split size in regset section iterators sergiodj+buildbot
2018-09-04 23:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-11 21:54 [binutils-gdb] x86: Add CpuCMOV and CpuFXSR sergiodj+buildbot
2018-09-04 19:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-11  9:28 [binutils-gdb] Factor out common relocation processing sergiodj+buildbot
2018-09-04 18:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10 22:34 [binutils-gdb] Fix forgotten xstrprintf -> string_printf change sergiodj+buildbot
2018-09-04 18:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10 20:40 [binutils-gdb] Move C-related declarations to compile-c.h sergiodj+buildbot
2018-09-04 18:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10 20:17 [binutils-gdb] Always clear h->verinfo.verdef when overriding a dynamic definition sergiodj+buildbot
2018-09-04 18:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10 20:03 [binutils-gdb] Use policies for code generation sergiodj+buildbot
2018-09-04 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10 18:47 [binutils-gdb] Rename symbol_substitution_name sergiodj+buildbot
2018-09-04 18:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10 18:34 [binutils-gdb] Return unique_xmalloc_ptr for generate_c_for_variable_locations sergiodj+buildbot
2018-09-04 17:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-10  9:48 [binutils-gdb] Rename size in get_core_register_section sergiodj+buildbot
2018-09-04 17:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-09 21:16 [binutils-gdb] RISC-V: Add configure support for riscv*-linux* sergiodj+buildbot
2018-09-04 17:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-09 21:02 [binutils-gdb] RISC-V: Add native linux support sergiodj+buildbot
2018-09-04 17:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-09 17:57 [binutils-gdb] Minor formatting fixes in riscv-tdep.h sergiodj+buildbot
2018-09-04 17:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-09 16:46 [binutils-gdb] gdb: Check element of optimised out vla exists sergiodj+buildbot
2018-09-04 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-09 16:34 [binutils-gdb] gdb: Merge similar tests into a single test script sergiodj+buildbot
2018-09-04 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-09  4:31 [binutils-gdb] Convert .note.gnu.property section between ELF32 and ELF64 sergiodj+buildbot
2018-09-04 16:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08 22:27 [binutils-gdb] Fix some comments in target.c sergiodj+buildbot
2018-09-04 16:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08 18:24 [binutils-gdb] RISC-V: Add software single step support sergiodj+buildbot
2018-09-04 16:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08 18:11 [binutils-gdb] RISC-V: Make riscv_isa_xlen a global function sergiodj+buildbot
2018-09-04 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08 13:26 [binutils-gdb] x86: Properly merge GNU_PROPERTY_X86_ISA_1_USED sergiodj+buildbot
2018-09-04 15:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08 12:34 [binutils-gdb] gdb: Fix assert for extended-remote target (PR gdb/18050) sergiodj+buildbot
2018-09-04 15:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08  8:34 [binutils-gdb] Make target_options_to_string return an std::string sergiodj+buildbot
2018-09-04 14:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08  3:19 [binutils-gdb] Fix gdb.fortran/nested-funcs.exp failure sergiodj+buildbot
2018-09-04 15:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-08  2:01 [binutils-gdb] Introduce mmap_file function sergiodj+buildbot
2018-09-04 11:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07 23:53 [binutils-gdb] Allow CPPFLAGS to be set on the make command line sergiodj+buildbot
2018-09-04 14:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07 23:40 [binutils-gdb] Add doc and news for DWARF index cache sergiodj+buildbot
2018-09-04 14:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07 23:28 [binutils-gdb] Add DWARF index cache sergiodj+buildbot
2018-09-04 14:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07 23:03 [binutils-gdb] Import gnulib's mkdir module sergiodj+buildbot
2018-09-04 12:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07  9:57 [binutils-gdb] PowerPC64 EH info for _notoc linkage stubs sergiodj+buildbot
2018-09-04 11:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07  9:44 [binutils-gdb] __tls_get_addr_opt stubs and tocsave optimization sergiodj+buildbot
2018-09-04 11:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07  4:19 [binutils-gdb] Fix compilation failure in remote.c sergiodj+buildbot
2018-09-04 11:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-07  0:38 [binutils-gdb] Use remote register numbers in tracepoint mask sergiodj+buildbot
2018-09-04  7:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 21:32 [binutils-gdb] Allow larger regblock sizes when saving tracefiles sergiodj+buildbot
2018-09-04  9:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 21:20 [binutils-gdb] Variable size for regs mask in collection list sergiodj+buildbot
2018-09-04  9:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 20:55 [binutils-gdb] Use get_remote_packet_size in download_tracepoint sergiodj+buildbot
2018-09-04  6:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 20:30 [binutils-gdb] Fix indentation in remote_target::download_tracepoint sergiodj+buildbot
2018-09-04  4:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 16:01 [binutils-gdb] [ARC] Update warning reporting sergiodj+buildbot
2018-09-03 16:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 14:55 [binutils-gdb] [ARC] Update merging attributes sergiodj+buildbot
2018-09-03 16:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 14:52 [binutils-gdb] Update dg-extract-results.* from gcc sergiodj+buildbot
2018-09-03 20:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 14:06 [binutils-gdb] [ARC] Update handling AUX-registers sergiodj+buildbot
2018-09-03 15:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06 12:12 [binutils-gdb] Remove unused variables in procfs.c etc sergiodj+buildbot
2018-09-03 15:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-06  8:09 [binutils-gdb] gdb: Avoid using W_STOPCODE(0) as this is ambiguous on MIPS sergiodj+buildbot
2018-09-03 15:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-05  8:47 [binutils-gdb] R_PPC64_REL24_NOTOC support sergiodj+buildbot
2018-09-03 15:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-05  8:17 [binutils-gdb] Lose _r2off in powerpc64 stub names sergiodj+buildbot
2018-09-03 12:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-03 22:31 [binutils-gdb] Fix thinko when deciding whether to disable TCP's Nagle algorithm sergiodj+buildbot
2018-09-02 22:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-03  8:58 [binutils-gdb] x86: drop NoRex64 from {,v}pmov{s,z}x* sergiodj+buildbot
2018-09-02 14:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-03  7:47 [binutils-gdb] x86: drop "mem" operand type attribute sergiodj+buildbot
2018-09-02 11:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-03  1:21 [binutils-gdb] RISC-V: Fix TLS and --gc-sections conflict sergiodj+buildbot
2018-09-02  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-02 22:45 [binutils-gdb] Allow "info address" of a template parameter sergiodj+buildbot
2018-09-01 21:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-02 22:32 [binutils-gdb] Fix kill issue leading to zombie process on MacOS Sierra sergiodj+buildbot
2018-09-01 20:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-02 22:19 [binutils-gdb] Check results of get_darwin_inferior sergiodj+buildbot
2018-09-01 18:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-02 19:11 [binutils-gdb] Backport gettext fixes to get rid of warnings on macOS sergiodj+buildbot
2018-09-01 13:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-01 14:09 [binutils-gdb] Fix potential illegal memory access in AVR backend sergiodj+buildbot
2018-09-01  6:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-01 13:53 [binutils-gdb] Close resource leaks in the BFD library's plugin handler sergiodj+buildbot
2018-09-01  3:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-01  3:21 [binutils-gdb] PowerPC64 __tls_get_addr_opt stub .eh_frame fix sergiodj+buildbot
2018-08-31 23:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-08-01  3:08 [binutils-gdb] csky regen sergiodj+buildbot
2018-08-31 21:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-31 21:29 [binutils-gdb] Correct previous update - new translation for the opcodes subdirectory sergiodj+buildbot
2018-08-31 19:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-31  9:53 [binutils-gdb] x86: also optimize KXOR{D,Q} and KANDN{D,Q} sergiodj+buildbot
2018-08-31 19:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-31  9:28 [binutils-gdb] x86/Intel: correct permitted operand sizes for AVX512 scatter/gather sergiodj+buildbot
2018-08-31 19:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-30 21:33 [binutils-gdb] Match any kind of error after "cannot resolve name" on lib/gdbserver-support.exp:gdbserver_start sergiodj+buildbot
2018-08-31 19:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-30 19:07 [binutils-gdb] gdb: Fix sizeof for dynamic types other than arrays sergiodj+buildbot
2018-08-31 18:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-30 15:34 [binutils-gdb] Fix crash with -D_GLIBCXX_DEBUG sergiodj+buildbot
2018-08-31 18:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-30 14:44 [binutils-gdb] Remove old lint code sergiodj+buildbot
2018-08-31 18:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-30 13:14 [binutils-gdb] Prevent a seg-fault in the linker when trying to process SH object files with bogus relocs sergiodj+buildbot
2018-08-31 18:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-30 11:50 [binutils-gdb] Add support for the C_SKY series of processors sergiodj+buildbot
2018-08-31 18:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-28 19:47 [binutils-gdb] gdb: Don't call gdb_load_shlib unless GDB is running sergiodj+buildbot
2018-08-31 18:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-28  8:33 [binutils-gdb] [gdb/exp] Interpret size of vla with unknown size as <optimized out> sergiodj+buildbot
2018-08-31 17:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-27 20:23 [binutils-gdb] Improve gcore manpage and clarify "-o" option sergiodj+buildbot
2018-08-31 17:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-27  2:40 [binutils-gdb] S12Z: Remove ELF_TARGET_ID macro sergiodj+buildbot
2018-08-31 17:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-27  2:27 [binutils-gdb] Add functions and macros to read and write 24 bit values sergiodj+buildbot
2018-08-31 16:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-27  2:25 [binutils-gdb] S12Z: Remove inappropriate comment sergiodj+buildbot
2018-08-31 15:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-27  0:35 [binutils-gdb] MIPS/GAS: Correct the AFL_ASE_MASK macro sergiodj+buildbot
2018-08-31 15:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 21:37 [binutils-gdb] Fix Cygwin compilation after target_ops C++ conversion sergiodj+buildbot
2018-08-30 20:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 17:20 [binutils-gdb] Introduce partial_symbol::address sergiodj+buildbot
2018-08-30 16:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 16:52 [binutils-gdb] Make psymbols and psymtabs independent of the program space sergiodj+buildbot
2018-08-30 19:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 16:39 [binutils-gdb] Add validity bits for psymtab high and low fields sergiodj+buildbot
2018-08-30 19:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 16:02 [binutils-gdb] Change representation of psymbol to flush out accessors sergiodj+buildbot
2018-08-30 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 15:38 [binutils-gdb] Remove dead code in end_psymtab sergiodj+buildbot
2018-08-30 15:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26 10:16 [binutils-gdb] [gdb/testsuite] Add comment in gdb.base/vla-optimized-out.c sergiodj+buildbot
2018-08-30 15:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26  8:36 [binutils-gdb] PowerPC Improve support for Gekko & Broadway sergiodj+buildbot
2018-08-30 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-26  3:50 [binutils-gdb] Implement PowerPC64 .localentry for value 1 sergiodj+buildbot
2018-08-30 14:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-25 23:35 [binutils-gdb] x86: Expand Broadcast to 3 bits sergiodj+buildbot
2018-08-30 13:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-25 23:11 [binutils-gdb] [gdb/breakpoints] Fix sigsegv in info prog at exec catchpoint sergiodj+buildbot
2018-08-30 13:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-25 22:34 [binutils-gdb] [gdb/symtab] Warn about unresolved DW_AT_upper_bound/DW_AT_count sergiodj+buildbot
2018-08-30 13:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-25 18:04 [binutils-gdb] Notify about breakpoint modification when enabling/disabling single location sergiodj+buildbot
2018-08-30 12:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-25 15:42 [binutils-gdb] list Tom Tromey as GDB Global Maintainer sergiodj+buildbot
2018-08-30 11:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-25  3:02 [binutils-gdb] Suppress string diagnostics for pre-release GCC sergiodj+buildbot
2018-08-30 10:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-24 20:51 [binutils-gdb] Set CU language before processing any DIEs (symtab/23010 et al) sergiodj+buildbot
2018-08-30  9:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-24 18:49 [binutils-gdb] Fix indentation in scoped_mmap.h sergiodj+buildbot
2018-08-30  7:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-24 17:47 [binutils-gdb] Remove some unnecessary declarations and configury sergiodj+buildbot
2018-08-30  7:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-23 19:36 [binutils-gdb] xtensa: move dynamic relocations sections consistency check sergiodj+buildbot
2018-08-30  2:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-23 19:26 [binutils-gdb] [ARC] Allow vewt instruction for ARC EM family sergiodj+buildbot
2018-08-30  1:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-23 14:29 [binutils-gdb] Avoid ubsan complaint in BFD sergiodj+buildbot
2018-08-30  2:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-23  9:02 [binutils-gdb] S/390: Suppress string diagnostics for pre-release GCC sergiodj+buildbot
2018-08-30  0:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-23  4:05 [binutils-gdb] power9 mfupmc/mtupmc sergiodj+buildbot
2018-08-29 23:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-23  3:41 [binutils-gdb] Remove some unused variables sergiodj+buildbot
2018-08-29 22:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 23:44 [binutils-gdb] Use a previously unused variable in bfin-tdep.c sergiodj+buildbot
2018-08-29 16:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 22:07 [binutils-gdb] Conditionally define xmltarget_${name} variable in regdat.sh sergiodj+buildbot
2018-08-29 21:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 21:41 [binutils-gdb] Remove unused declaration from value.c sergiodj+buildbot
2018-08-29 20:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 21:17 [binutils-gdb] Fix ravenscar-thread.c to use arch_ops sergiodj+buildbot
2018-08-29 19:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 20:37 [binutils-gdb] Call some functions in guile/ for effect sergiodj+buildbot
2018-08-29 17:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 19:59 [binutils-gdb] Remove an unused variable from spu_get_overlay_table sergiodj+buildbot
2018-08-29 15:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22 19:46 [binutils-gdb] Simple unused variable removals sergiodj+buildbot
2018-07-22 19:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-22  2:41 [binutils-gdb] Fix -Wunused-variable warnings related to conditional compilation sergiodj+buildbot
2018-07-22  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-21 13:17 [binutils-gdb] Initialize GOT slot for local symbol in non-PIC link sergiodj+buildbot
2018-07-21 13:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-21  3:46 [binutils-gdb] MIPS/Linux/native: Convert to `get_ptrace_pid' for PID extraction sergiodj+buildbot
2018-07-21  3:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-21  2:36 [binutils-gdb] Rename some frame unwind function parameters sergiodj+buildbot
2018-07-21  4:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-21  2:18 [binutils-gdb] Remove record_line_ftype sergiodj+buildbot
2018-07-21  2:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-21  0:39 [binutils-gdb] Introduce buildsym-legacy.h sergiodj+buildbot
2018-07-21  0:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 23:54 [binutils-gdb] Remove reset_symtab_globals sergiodj+buildbot
2018-07-20 23:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 21:34 [binutils-gdb] x86: Add a GNU_PROPERTY_X86_ISA_1_USED note if needed sergiodj+buildbot
2018-07-21  3:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 21:21 [binutils-gdb] Rename remaining members of buildsym_compunit to start with "m_" sergiodj+buildbot
2018-07-21  2:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 20:57 [binutils-gdb] Remove some unused buildsym functions sergiodj+buildbot
2018-07-21  1:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 20:45 [binutils-gdb] Convert the DWARF reader to new-style buildysm sergiodj+buildbot
2018-07-21  1:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 20:33 [binutils-gdb] Parameterize cp_scan_for_anonymous_namespaces sergiodj+buildbot
2018-07-21  1:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 20:08 [binutils-gdb] Move struct buildsym_compunit to buildsym.h sergiodj+buildbot
2018-07-21  0:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 19:44 [binutils-gdb] Do not use buildsym.h in some files sergiodj+buildbot
2018-07-20 23:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 19:20 [binutils-gdb] Remove parameter from record_pending_block sergiodj+buildbot
2018-07-20 22:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 18:36 [binutils-gdb] Remove the "listhead" argument from finish_block sergiodj+buildbot
2018-07-20 18:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 18:23 [binutils-gdb] Remove buildsym_init sergiodj+buildbot
2018-07-20 21:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 17:58 [binutils-gdb] Set list_in_scope later in DWARF reader sergiodj+buildbot
2018-07-20 20:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 16:47 [binutils-gdb] Move pending_blocks and pending_block_obstack to buildsym_compunit sergiodj+buildbot
2018-07-20 17:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 16:34 [binutils-gdb] Move pending addrmap globals to buildsym_compunit sergiodj+buildbot
2018-07-20 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 16:23 [binutils-gdb] Move current_subfile to buildsym_compunit sergiodj+buildbot
2018-07-20 17:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 15:57 [binutils-gdb] Make the Rust parser pure sergiodj+buildbot
2018-07-20 16:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 15:34 [binutils-gdb] [gdb/testsuite] Make noclone conditional in vla-optimized-out.c sergiodj+buildbot
2018-07-20 15:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20 12:50 [binutils-gdb] MIPS/GAS: Split Loongson MMI Instructions from loongson2f/3a sergiodj+buildbot
2018-07-20 13:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-20  2:23 [binutils-gdb] Remove myself from target-specific MAINTAINERS sergiodj+buildbot
2018-07-20  2:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19 16:25 [binutils-gdb] Remove make_cleanup_value_free_to_mark sergiodj+buildbot
2018-07-19 16:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19 15:05 [binutils-gdb] [gdb/testsuite] Fix regexp in list-thread-groups-available.exp sergiodj+buildbot
2018-07-19 15:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19 14:29 [binutils-gdb] Fix GDB build using mingw.org's MinGW sergiodj+buildbot
2018-07-19 14:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19 10:09 [binutils-gdb] x86: fold narrowing VCVT* templates sergiodj+buildbot
2018-07-19 10:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19  8:16 [binutils-gdb] x86: fold various AVX512BW templates sergiodj+buildbot
2018-07-19  8:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19  8:06 [binutils-gdb] x86: fold VFPCLASSP{D,S} templates sergiodj+buildbot
2018-07-19  9:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19  7:54 [binutils-gdb] x86: fold various AVX512* templates sergiodj+buildbot
2018-07-19  9:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19  7:40 [binutils-gdb] x86: fold various AVX512DQ templates sergiodj+buildbot
2018-07-19  8:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19  7:13 [binutils-gdb] x86: fold various AVX512CD templates sergiodj+buildbot
2018-07-19  7:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-19  6:47 [binutils-gdb] x86: pre-process opcodes table before parsing sergiodj+buildbot
2018-07-19  6:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-18 22:37 [binutils-gdb] Eliminate most remaining cleanups under gdb/guile/ sergiodj+buildbot
2018-07-18 22:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-18 20:19 [binutils-gdb] [gdb/exp] Fix printing of type of optimized out vla sergiodj+buildbot
2018-07-18 20:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-18 17:09 [binutils-gdb] BFD/XCOFF: Fix storage class setting for weak defined symbols sergiodj+buildbot
2018-07-18 17:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17 21:55 [binutils-gdb] Return unique_xmalloc_ptr from gdbscm_scm_to_string sergiodj+buildbot
2018-07-17 21:55 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17 20:28 [binutils-gdb] Return unique_xmalloc_ptr from gdbscm_safe_eval_string sergiodj+buildbot
2018-07-17 21:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17 20:04 [binutils-gdb] BFD: Use `bfd_is_abs_symbol' to determine whether a symbol is absolute sergiodj+buildbot
2018-07-17 20:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17 19:20 [binutils-gdb] LD: Export relative-from-absolute symbol marking to BFD sergiodj+buildbot
2018-07-17 19:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17 17:29 [binutils-gdb] RISC-V: Don't decrement pc after break sergiodj+buildbot
2018-07-17 18:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17 16:55 [binutils-gdb] Remove --disable-gdbcli sergiodj+buildbot
2018-07-17 17:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17  3:26 [binutils-gdb] Fix compilation error in ia64-vms-tdep.c with libunwind-ia64 sergiodj+buildbot
2018-07-17  3:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-17  2:21 [binutils-gdb] Fix compilation error in ia64-tdep.c with libunwind-ia64 sergiodj+buildbot
2018-07-17  2:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 23:48 [binutils-gdb] Use gdb_assert in two places in buildsym.c sergiodj+buildbot
2018-07-16 23:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 23:14 [binutils-gdb] Remove merge_symbol_lists sergiodj+buildbot
2018-07-16 23:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 21:45 [binutils-gdb] Add grok/write functions for new ppc core note sections sergiodj+buildbot
2018-07-17  4:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 21:34 [binutils-gdb] Move processing_gcc to stabsread sergiodj+buildbot
2018-07-16 21:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 21:09 [binutils-gdb] remote-sim.c: Remove unused variables sergiodj+buildbot
2018-07-17  2:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 20:47 [binutils-gdb] Use outermost_context_p in more places sergiodj+buildbot
2018-07-17  1:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 20:35 [binutils-gdb] Move the using directives to buildsym_compunit sergiodj+buildbot
2018-07-17  1:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 18:54 [binutils-gdb] Move scan_file_globals declaration to stabsread.h sergiodj+buildbot
2018-07-16 22:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 18:47 [binutils-gdb] Move last_source_start_addr to buildsym_compunit sergiodj+buildbot
2018-07-16 18:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 18:07 [binutils-gdb] Move some code from buildsym to stabsread sergiodj+buildbot
2018-07-16 20:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 17:29 [binutils-gdb] Move last_source file to buildsym_compunit sergiodj+buildbot
2018-07-16 17:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 17:20 [binutils-gdb] Move have_line_numbers to buildsym_compunit sergiodj+buildbot
2018-07-16 18:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 17:07 [binutils-gdb] Move pending_macros to buildsym_compunit sergiodj+buildbot
2018-07-16 17:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 17:06 [binutils-gdb] Add assert in prepare_for_building sergiodj+buildbot
2018-07-16 17:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-16 13:25 [binutils-gdb] Update the src-release script to include the new top level files test-driver and ar-lib sergiodj+buildbot
2018-07-16 13:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-14  2:23 [binutils-gdb] Remove struct keyword in range-based for loop sergiodj+buildbot
2018-07-14  2:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-13 21:45 [binutils-gdb] sim: Add Stafford Horne as or1k maintainer sergiodj+buildbot
2018-07-13 21:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-13 21:14 [binutils-gdb] gdb: Add Stafford Horne as or1k maintainer sergiodj+buildbot
2018-07-13 21:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-13 17:43 [binutils-gdb] Remove a warning on macOS sergiodj+buildbot
2018-07-13 17:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-12  9:57 [binutils-gdb] Add remainder of Em16 restrictions for AArch64 gas sergiodj+buildbot
2018-07-12 10:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-12  0:20 [binutils-gdb] Implement IPv6 support for GDB/gdbserver sergiodj+buildbot
2018-07-12  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11 23:34 [binutils-gdb] GDB: Work around D; PID handling bug in older GDBservers (PR gdb/23377) sergiodj+buildbot
2018-07-11 23:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11 20:12 [binutils-gdb] gdb: Remove traces of h8300 ecoff support sergiodj+buildbot
2018-07-11 21:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11 19:19 [binutils-gdb] Fix PR c++/23373: GDB hangs when printing a struct with a static member of itself sergiodj+buildbot
2018-07-11 19:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11 17:31 [binutils-gdb] MIPS/BFD: Fix TLS relocation resolution for regular executables sergiodj+buildbot
2018-07-11 17:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11 17:28 [binutils-gdb] Adds the speculation barrier instructions to the ARM assembler and disassembler sergiodj+buildbot
2018-07-11 18:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11 17:09 [binutils-gdb] PR ld/22570: MIPS/BFD: Fix TLS relocation resolution for PIE executables sergiodj+buildbot
2018-07-11 17:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11  9:15 [binutils-gdb] x86: adjust monitor/mwait templates sergiodj+buildbot
2018-07-11 10:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11  9:04 [binutils-gdb] x86: drop {,reg16_}inoutportreg variables sergiodj+buildbot
2018-07-11  9:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11  8:52 [binutils-gdb] x86/Intel: accept memory operand size specifiers for CET insns sergiodj+buildbot
2018-07-11  9:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11  8:40 [binutils-gdb] x86: replace off-by-one OTMax sergiodj+buildbot
2018-07-11  8:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11  1:58 [binutils-gdb] Use std::vector for moribund_locations sergiodj+buildbot
2018-07-11  2:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-11  0:07 [binutils-gdb] BFD/ELF: Correct a `remove' global shadowing error for pre-4.8 GCC sergiodj+buildbot
2018-07-11  0:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-10 15:13 [binutils-gdb] xgate cleanup sergiodj+buildbot
2018-07-10 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-10 12:43 [binutils-gdb] gdb/riscv: Fix assertion in inferior call code sergiodj+buildbot
2018-07-10 12:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 20:43 [binutils-gdb] MIPS/BFD: Do not redirect to discarded lazy binding stubs sergiodj+buildbot
2018-07-09 21:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 18:43 [binutils-gdb] Don't mention XM_CDEPS or NAT_CLIBS sergiodj+buildbot
2018-07-09 18:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 17:53 [binutils-gdb] gdb: Use add_setshow_zuinteger_unlimited_cmd in remote.c sergiodj+buildbot
2018-07-09 20:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 17:30 [binutils-gdb] gdb/testsuite: Allow for failure to read some memory addresses sergiodj+buildbot
2018-07-09 19:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 17:05 [binutils-gdb] Fix exec.c handling in Makefile sergiodj+buildbot
2018-07-09 17:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 16:34 [binutils-gdb] Remove ADD_FILES and ADD_DEPS from Makefile.in sergiodj+buildbot
2018-07-09 18:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 16:22 [binutils-gdb] Minimize yacc and lex output sergiodj+buildbot
2018-07-09 17:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 15:58 [binutils-gdb] Remove lint support sergiodj+buildbot
2018-07-09 16:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 15:15 [binutils-gdb] Use a stamp file for init.c sergiodj+buildbot
2018-07-09 15:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 15:04 [binutils-gdb] Remove some unused code from init.c build rule sergiodj+buildbot
2018-07-09 15:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09 14:39 [binutils-gdb] Remove TSOBS from gdb/Makefile.in sergiodj+buildbot
2018-07-09 14:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-09  8:51 [binutils-gdb] m68hc1* fixes sergiodj+buildbot
2018-07-09  9:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-07 15:31 [binutils-gdb] ia64-tdep.c: Fix -Wwrite-strings errors sergiodj+buildbot
2018-07-07 15:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-06 23:23 [binutils-gdb] xtensa: don't emit dynamic relocation for weak undefined symbol sergiodj+buildbot
2018-07-06 23:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-06 16:04 [binutils-gdb] Add checks for the NT_ARM_SVE section in a core file sergiodj+buildbot
2018-07-06 16:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-06 15:50 [binutils-gdb] Fix SBO bit in disassembly mask for ldrah on AArch64 sergiodj+buildbot
2018-07-06 16:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-06 15:46 [binutils-gdb] Fix the read/write flag for these registers on AArch64 sergiodj+buildbot
2018-07-06 15:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-06 13:55 [binutils-gdb] gdb/testsuite: Ensure test links in malloc and free sergiodj+buildbot
2018-07-06 13:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-06  6:41 [binutils-gdb] Update config.sub sergiodj+buildbot
2018-07-06  6:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-05 12:16 [binutils-gdb] Update config.guess and config.sub sergiodj+buildbot
2018-07-05 12:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-05 11:32 [binutils-gdb] Updated Russian, Bulgarian, and Brazilian Portuguese translations for various components of the binutuls sergiodj+buildbot
2018-07-05 11:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-05  1:05 [binutils-gdb] Error for mismatched powerpc ABI tags sergiodj+buildbot
2018-07-05  1:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-04 20:19 [binutils-gdb] Use exit_inferior in darwin_attach_pid sergiodj+buildbot
2018-07-04 20:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-04 16:41 [binutils-gdb] Update NEWS post GDB 8.2 branch creation sergiodj+buildbot
2018-07-04 17:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-04 15:34 [binutils-gdb] Warn if /proc is not accessible sergiodj+buildbot
2018-07-04 15:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-04 13:41 [binutils-gdb] Also install diagnostics.h sergiodj+buildbot
2018-07-04 13:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-04 10:14 [binutils-gdb] [gdb/symtab] Fix version check in dwarf compilation unit header sergiodj+buildbot
2018-07-04 10:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-04  5:32 [binutils-gdb] Remove VEC from breakpoint sergiodj+buildbot
2018-07-04  5:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 20:37 [binutils-gdb] Remove ptid_get_tid sergiodj+buildbot
2018-07-03 20:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 20:22 [binutils-gdb] Remove ptid_tid_p sergiodj+buildbot
2018-07-03 22:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 19:56 [binutils-gdb] Remove ptid_is_pid sergiodj+buildbot
2018-07-03 21:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 19:37 [binutils-gdb] Remove ptid_get_pid sergiodj+buildbot
2018-07-03 19:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 19:30 [binutils-gdb] Remove ptid_get_lwp sergiodj+buildbot
2018-07-03 20:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 19:08 [binutils-gdb] Remove pid_to_ptid sergiodj+buildbot
2018-07-03 19:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 17:56 [binutils-gdb] Remove exit_inferior_num_silent sergiodj+buildbot
2018-07-03 18:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03 16:21 [binutils-gdb] Fix crash in "run" on macOS when gdb is not signed sergiodj+buildbot
2018-07-03 16:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03  7:50 [binutils-gdb] GNU attribute output on errors sergiodj+buildbot
2018-07-03  8:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03  1:00 [binutils-gdb] MIPS/BFD: Make section GC work with `ict_irix5' targets sergiodj+buildbot
2018-07-03  1:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-03  0:01 [binutils-gdb] microMIPS/BFD: Add missing NewABI TLS and miscellaneous relocations sergiodj+buildbot
2018-07-03  0:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-02 23:22 [binutils-gdb] GDB PR tdep/8282: MIPS: Wire in `set disassembler-options' sergiodj+buildbot
2018-07-02 23:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-02 20:29 [binutils-gdb] x86-64: Clear the R_X86_64_converted_reloc_bit bit sergiodj+buildbot
2018-07-02 20:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-02 13:44 [binutils-gdb] gdb: Prefer RISC-V register name "s0" over "fp" sergiodj+buildbot
2018-07-02 14:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-07-02 10:50 [binutils-gdb] [ARM] Update bfd's Tag_CPU_arch knowledge sergiodj+buildbot
2018-07-02 11:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-30  2:07 [binutils-gdb] Add missing parameter to 'amd64_create_target_description' (and unbreak build) sergiodj+buildbot
2018-06-30  3:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 23:09 [binutils-gdb] fix GDB build failure for various amd64 targets sergiodj+buildbot
2018-06-29 23:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 21:10 [binutils-gdb] Improve alignment of "info threads" output, align "Target Id" column sergiodj+buildbot
2018-06-29 21:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 20:19 [binutils-gdb] remote & target_extra_thread_info, use cache w/ qThreadExtraInfo and qP too sergiodj+buildbot
2018-06-29 20:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 19:23 [binutils-gdb] "break LINENO/*ADDRESS", inline functions and "info break" output sergiodj+buildbot
2018-06-29 20:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 17:02 [binutils-gdb] Remove unstable test output sergiodj+buildbot
2018-06-29 17:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 15:19 [binutils-gdb] MIPS/BFD: Remove extraneous undefined weak symbol visibility check sergiodj+buildbot
2018-06-29 15:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-29 11:46 [binutils-gdb] Fix AArch64 encodings for by element instructions sergiodj+buildbot
2018-06-29 11:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-28 16:39 [binutils-gdb] Fix follow-exec regression / crash sergiodj+buildbot
2018-06-28 16:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-28  8:32 [binutils-gdb] Fixed top frame assumption in watchpoint-hw-attach sergiodj+buildbot
2018-06-28  9:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-28  8:08 [binutils-gdb] Make sure that sorting does not change section order sergiodj+buildbot
2018-06-28  8:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-28  7:44 [binutils-gdb] Make add-symbol-file's address argument optional sergiodj+buildbot
2018-06-28  7:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-28  7:01 [binutils-gdb] Add an optional offset option to the "symbol-file" command sergiodj+buildbot
2018-06-28  7:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-28  6:51 [binutils-gdb] Add myself as a write-after-approval GDB maintainer sergiodj+buildbot
2018-06-28  6:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 21:34 [binutils-gdb] Update "func" help text to GNU standards sergiodj+buildbot
2018-06-27 22:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 21:08 [binutils-gdb] Fix crash in machoread.c sergiodj+buildbot
2018-06-27 21:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 19:47 [binutils-gdb] Add pretty-printer for CORE_ADDR sergiodj+buildbot
2018-06-27 20:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 19:18 [binutils-gdb] gdb-gdb.py.in: Fix ordering of TypeFlags objects with Python 3 sergiodj+buildbot
2018-06-27 19:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 19:03 [binutils-gdb] Copy gdb-gdb.py to build dir sergiodj+buildbot
2018-06-27 19:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 16:49 [binutils-gdb] Fix Cell debugging regression sergiodj+buildbot
2018-06-27 16:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 15:41 [binutils-gdb] Fix lost line info for symbol at addr zero sergiodj+buildbot
2018-06-27 15:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-27 15:14 [binutils-gdb] Add overrides, fix FreeBSD build sergiodj+buildbot
2018-06-27 15:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-26 22:03 [binutils-gdb] Minor reorganization of fetch_registers/store_registers in windows-nat.c sergiodj+buildbot
2018-06-26 22:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-26 21:17 [binutils-gdb] Move ptype/o printing code to typeprint.c sergiodj+buildbot
2018-06-26 21:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-26 13:21 [binutils-gdb] Updated translations sergiodj+buildbot
2018-06-26 13:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-26 12:14 [binutils-gdb] Fix spelling mistakes sergiodj+buildbot
2018-06-26 12:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-25 17:40 [binutils-gdb] gdb: For macOS, s/thread_info/struct thread_info/ sergiodj+buildbot
2018-06-25 18:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-25 17:11 [binutils-gdb] gdb: Fix build on several hosts/ports sergiodj+buildbot
2018-06-25 17:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-24 18:48 [binutils-gdb] Regenerate configure and pot files with updated binutils version number sergiodj+buildbot
2018-06-24 19:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-24 18:32 [binutils-gdb] Update version number on development (aka HEAD) branch sergiodj+buildbot
2018-06-24 18:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-22 18:03 [binutils-gdb] Fix "info registers" regexes in gdb.base/jit-reader.exp sergiodj+buildbot
2018-06-22 18:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-22 11:54 [binutils-gdb] Correct negs aliasing on AArch64 sergiodj+buildbot
2018-06-22 12:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-22 11:32 [binutils-gdb] Fix up HAS_SVE_STATE macro sergiodj+buildbot
2018-06-22 11:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21 22:06 [binutils-gdb] MIPS/opcodes: Fix a typo in `-M ginv' option description sergiodj+buildbot
2018-06-21 23:15 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21 21:05 [binutils-gdb] MIPS/BFD: Use enumeration constants for EI_ABIVERSION sergiodj+buildbot
2018-06-21 21:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21 16:38 [binutils-gdb] Use thread_info and inferior pointers more throughout sergiodj+buildbot
2018-06-21 16:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21 15:51 [binutils-gdb] Avoid memcpys in regcache read_part/write_part for full registers sergiodj+buildbot
2018-06-21 16:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21 13:57 [binutils-gdb] Regen doc/Makefile.in sergiodj+buildbot
2018-06-21 14:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21 13:34 [binutils-gdb] Enable hardware watchpoints on attach for aarch64 sergiodj+buildbot
2018-06-21 13:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21  9:06 [binutils-gdb] Use offsets instead of addresses in ELF_SECTION_IN_SEGMENT for non SHT_NOBITS sergiodj+buildbot
2018-06-21  9:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-21  3:34 [binutils-gdb] Fix a memory leak in py-param.c sergiodj+buildbot
2018-06-21  3:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20 18:31 [binutils-gdb] Rename regcache_cooked_read_ftype and make a function_view sergiodj+buildbot
2018-06-20 18:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20 17:09 [binutils-gdb] testsuite: Fix cc-with-tweaks.sh being executed in the wrong shell sergiodj+buildbot
2018-06-20 17:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20 17:01 [binutils-gdb] Remove struct keyword in range-based for-loop sergiodj+buildbot
2018-06-20 17:22 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20 15:49 [binutils-gdb] Fix potential illegal memroy access when using a build-id note with a negative size sergiodj+buildbot
2018-06-20 16:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20 14:46 [binutils-gdb] Improve gdb.base/float128.exp failure message sergiodj+buildbot
2018-06-20 14:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20 14:11 [binutils-gdb] [BFD][AARCH64]Properly truncate no overflow checking relocation value for load/store immediate sergiodj+buildbot
2018-06-20 14:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20  5:42 [binutils-gdb] RISC-V: Accept constant operands in la and lla sergiodj+buildbot
2018-06-20  6:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-20  0:36 [binutils-gdb] PR ld/22966: Fix n64 MIPS `.got.plt' range checks sergiodj+buildbot
2018-06-20  0:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-19 18:36 [binutils-gdb] include: Sync with GCC sergiodj+buildbot
2018-06-19 18:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-19 16:56 [binutils-gdb] Change inline frame breakpoint skipping logic (fix gdb.gdb/selftest.exp) sergiodj+buildbot
2018-06-19 17:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-19  9:25 [binutils-gdb] readelf: Handle more RISC-V relocations sergiodj+buildbot
2018-06-19  9:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 22:38 [binutils-gdb] This was already applied on the GCC side sergiodj+buildbot
2018-06-18 23:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 20:52 [binutils-gdb] Remove current_traceframe declaration sergiodj+buildbot
2018-06-18 22:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 20:35 [binutils-gdb] Use unique_xmalloc_ptr in solib-aix.c sergiodj+buildbot
2018-06-18 22:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 20:28 [binutils-gdb] Use unique_xmalloc_ptr in darwin_current_sos sergiodj+buildbot
2018-06-18 21:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 20:02 [binutils-gdb] Remove resume_section_map_updates_cleanup sergiodj+buildbot
2018-06-18 20:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 19:25 [binutils-gdb] Use unique_xmalloc_ptr for read_string sergiodj+buildbot
2018-06-18 20:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 19:14 [binutils-gdb] Remove la_error sergiodj+buildbot
2018-06-18 19:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 19:11 [binutils-gdb] Remove cleanups from ser-mingw.c sergiodj+buildbot
2018-06-18 19:46 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 15:08 [binutils-gdb] libiberty: Sync with GCC sergiodj+buildbot
2018-06-18 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 14:36 [binutils-gdb] libdecnumber: Sync with GCC sergiodj+buildbot
2018-06-18 16:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 14:08 [binutils-gdb] config: Sync with GCC sergiodj+buildbot
2018-06-18 14:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 10:38 [binutils-gdb] Ptrace support for AArch64 SVE gdbserver sergiodj+buildbot
2018-06-18 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 10:30 [binutils-gdb] Ptrace support for Aarch64 SVE sergiodj+buildbot
2018-06-18 11:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18 10:19 [binutils-gdb] Add Aarch64 SVE compatibility macros sergiodj+buildbot
2018-06-18 10:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-18  7:22 [binutils-gdb] [gdb/testsuite/ada] Fix number-of-bp test in bp_inlined_func.exp sergiodj+buildbot
2018-06-18  7:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-16  0:27 [binutils-gdb] gdb: Don't drop SIGSTOP during stop_all_threads sergiodj+buildbot
2018-06-16  0:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 23:27 [binutils-gdb] update-gnulib.sh: Report required versions of autoconf/aclocal sergiodj+buildbot
2018-06-15  0:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 22:50 [binutils-gdb] MIPS: Add Global INValidate ASE support sergiodj+buildbot
2018-06-14 23:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 22:07 [binutils-gdb] Fix "beneath" conversion on AIX sergiodj+buildbot
2018-06-14 23:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 21:46 [binutils-gdb] Fix/improve on-line help of 'define' command sergiodj+buildbot
2018-06-14 22:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 17:28 [binutils-gdb] Avoid gdb.base/fork-running-state.exp lingering processes sergiodj+buildbot
2018-06-14 17:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 13:54 [binutils-gdb] [gdb/cli] Honour 'print pretty' when printing result of finish command sergiodj+buildbot
2018-06-14 14:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 12:44 [binutils-gdb] Revert accidental push of "Inline breakpoints" commit sergiodj+buildbot
2018-06-14 13:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 12:29 [binutils-gdb] gdb.gdb/selftest.exp, Use multi_line to build gdb's expected startup output sergiodj+buildbot
2018-06-14 12:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14 11:02 [binutils-gdb] Remove stale inline function handling from selftest_setup sergiodj+buildbot
2018-06-14 11:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14  3:54 [binutils-gdb] ELF dynsyms sergiodj+buildbot
2018-06-14  4:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14  2:26 [binutils-gdb] PR23282, Reinstate seek optimization sergiodj+buildbot
2018-06-14  2:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-14  2:16 [binutils-gdb] Fix GDB sparc build sergiodj+buildbot
2018-06-14  2:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-13 15:04 [binutils-gdb] MIPS: Add CRC ASE support sergiodj+buildbot
2018-06-13 15:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-13 13:04 [binutils-gdb] [gdb/testsuite] Fix hang in fork-running-state.c sergiodj+buildbot
2018-06-13 13:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-13 12:58 [binutils-gdb] [gdb/testsuite] Update gdb startup text in selftest.exp sergiodj+buildbot
2018-06-13 13:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-13  9:37 [binutils-gdb] Fix procfs.c compilation sergiodj+buildbot
2018-06-13  9:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-12 22:38 [binutils-gdb] gdb: Run INF_EXEC_COMPLETE handler for additional cases sergiodj+buildbot
2018-06-12 22:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-12 21:42 [binutils-gdb] gdb: Fix an infrun debug log message sergiodj+buildbot
2018-06-12 21:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-12  2:23 [binutils-gdb] Fix gdb build on hppa-linux sergiodj+buildbot
2018-06-12  2:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-11 13:00 [binutils-gdb] Enable Aarch64 SVE for gdbserver sergiodj+buildbot
2018-06-11 12:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-11 11:25 [binutils-gdb] Increase gdbsever PBUFSIZ sergiodj+buildbot
2018-06-11 11:45 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-11 10:47 [binutils-gdb] Add Aarch64 SVE dwarf regnums sergiodj+buildbot
2018-06-11 10:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-11  5:54 [binutils-gdb] Remove cleanups from record-full.c sergiodj+buildbot
2018-06-11  5:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-11  3:01 [binutils-gdb] Remove more "struct" keywords in range-based for loops sergiodj+buildbot
2018-06-11  2:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-10 14:17 [binutils-gdb] Remove cleanups from tracefile.c sergiodj+buildbot
2018-06-10 16:28 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-10  4:07 [binutils-gdb] Use std::unique_ptr in reg_buffer sergiodj+buildbot
2018-06-10  4:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-10  0:49 [binutils-gdb] Remove use of queue.h from gdbserver/event-loop.c sergiodj+buildbot
2018-06-10  0:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-10  0:10 [binutils-gdb] Remove a VEC from serial.c sergiodj+buildbot
2018-06-10  0:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 21:24 [binutils-gdb] Add missing client_state struct references to win target sergiodj+buildbot
2018-06-08 22:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 20:50 [binutils-gdb] Make gdbreplay use more common routines sergiodj+buildbot
2018-06-08 21:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 20:50 [binutils-gdb] ld/x86: Remove hidden _edata, __bss_start, and _end sergiodj+buildbot
2018-06-08 20:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 18:19 [binutils-gdb] Fix build issue with Python 3.7 sergiodj+buildbot
2018-06-08 19:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 17:39 [binutils-gdb] linux: Add maintenance commands to test libthread_db sergiodj+buildbot
2018-06-08 17:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 16:46 [binutils-gdb] Fix gdb mingw build sergiodj+buildbot
2018-06-08 17:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 14:56 [binutils-gdb] Remove last cleanup from btrace code sergiodj+buildbot
2018-06-08 15:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-08 14:44 [binutils-gdb] Remove cleanups from btrace code sergiodj+buildbot
2018-06-08 14:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-07 20:49 [binutils-gdb] Introduce class target_stack sergiodj+buildbot
2018-06-07 21:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-07 20:16 [binutils-gdb] Eliminate find_target_beneath sergiodj+buildbot
2018-06-07 20:38 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-07 19:21 [binutils-gdb] target_ops::beneath -> target_ops::beneath() sergiodj+buildbot
2018-06-07 20:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-07 18:59 [binutils-gdb] target_stack -> current_top_target() throughout sergiodj+buildbot
2018-06-07 19:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-07 10:06 [binutils-gdb] Aarch64 SVE pseudo register support sergiodj+buildbot
2018-06-07 10:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-07  0:45 [binutils-gdb] TIC6X __c6xabi_DSBT_BASE sergiodj+buildbot
2018-06-07  0:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-06 22:15 [binutils-gdb] Guard declarations of 'sve_{vq, vl}_from_{vl, vq}' macros on Aarch64 (and unbreak build) sergiodj+buildbot
2018-06-06 22:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-06  0:46 [binutils-gdb] Fix typo in common/enum-flags.h example sergiodj+buildbot
2018-06-06  7:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-05 23:06 [binutils-gdb] Tidy bfdio to consistenly use containing archive sergiodj+buildbot
2018-06-06  7:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-05 13:50 [binutils-gdb] PR23254, ld.bfd mishandles file pointers while scanning archive sergiodj+buildbot
2018-06-06  6:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-05  6:27 [binutils-gdb] Remove last Ada cleanups sergiodj+buildbot
2018-06-06  4:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 22:09 [binutils-gdb] (windows) GDB/MI crash when using "-list-thread-groups --available" sergiodj+buildbot
2018-06-04 22:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 19:51 [binutils-gdb] xtensa: add separate property sections option sergiodj+buildbot
2018-06-04 19:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 18:56 [binutils-gdb] xtensa: use property tables for correct disassembly sergiodj+buildbot
2018-06-04 21:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 18:33 [binutils-gdb] Use DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION to silence GCC 8.1 sergiodj+buildbot
2018-06-04 18:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 17:01 [binutils-gdb] Use ELF_SECTION_IN_SEGMENT to map segments sergiodj+buildbot
2018-06-04 17:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 16:02 [binutils-gdb] Add configure.nat as a dependency of config.status sergiodj+buildbot
2018-06-04 16:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 15:13 [binutils-gdb] Add client_state struct sergiodj+buildbot
2018-06-04 15:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 14:50 [binutils-gdb] Add DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION sergiodj+buildbot
2018-06-04 14:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 14:05 [binutils-gdb] Change functions in cp-name-parser.y into methods sergiodj+buildbot
2018-06-04 14:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 13:45 [binutils-gdb] Add aarch64 pseudo help functions sergiodj+buildbot
2018-06-04 13:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 11:57 [binutils-gdb] Use uint64_t for aarch64 tdep VQ sergiodj+buildbot
2018-06-04 12:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 11:39 [binutils-gdb] Enable SVE for GDB sergiodj+buildbot
2018-06-04 11:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-04 10:40 [binutils-gdb] Use uint64_t for SVE VQ sergiodj+buildbot
2018-06-04 11:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-03 23:24 [binutils-gdb] RISC-V: Handle out-of-range calls to undefined weak sergiodj+buildbot
2018-06-03 23:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-03 22:23 [binutils-gdb] RISC-V: Fix symbol address problem with versioned symbols sergiodj+buildbot
2018-06-03 22:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-02 14:08 [binutils-gdb] Split value_fetch_lazy sergiodj+buildbot
2018-06-02 14:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 22:57 [binutils-gdb] Include parser-defs.h in cp-name-parser.y sergiodj+buildbot
2018-06-01 23:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 21:21 [binutils-gdb] Use yy-remap.h in cp-name-parser.y sergiodj+buildbot
2018-06-01 22:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 21:12 [binutils-gdb] Move gdb/common/diagnostics.h to include/diagnostics.h sergiodj+buildbot
2018-06-01 21:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 20:47 [binutils-gdb] Remove a static buffer from cp-name-parser.y sergiodj+buildbot
2018-06-01 22:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 20:36 [binutils-gdb] inadvertent language switch during breakpoint_re_set_one sergiodj+buildbot
2018-06-01 20:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 19:10 [binutils-gdb] Bump version number to 2.30.52 sergiodj+buildbot
2018-06-01 19:47 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 18:49 [binutils-gdb] Remove type_name_no_tag and rename type_name_no_tag_or_error sergiodj+buildbot
2018-06-01 18:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 18:09 [binutils-gdb] Remove TYPE_TAG_NAME sergiodj+buildbot
2018-06-01 18:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 17:38 [binutils-gdb] Thread language through c_type_print_args sergiodj+buildbot
2018-06-01 18:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 17:11 [binutils-gdb] Make c_type_print_varspec_suffix static sergiodj+buildbot
2018-06-01 17:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01 16:14 [binutils-gdb] Add SVE register defines sergiodj+buildbot
2018-06-01 17:04 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01  8:50 [binutils-gdb] x86: fold MOV to/from segment register templates sergiodj+buildbot
2018-06-01  8:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01  7:37 [binutils-gdb] x86/Intel: accept "oword ptr" for INVPCID sergiodj+buildbot
2018-06-01  7:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-06-01  4:20 [binutils-gdb] Make _bfd_error_handler available outside libbfd sergiodj+buildbot
2018-06-01  4:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 22:06 [binutils-gdb] Fix "set" handling of Python parameters sergiodj+buildbot
2018-05-31 22:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 21:41 [binutils-gdb] Add basic Python API for convenience variables sergiodj+buildbot
2018-05-31 21:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 14:18 [binutils-gdb] Function for reading the Aarch64 SVE vector length sergiodj+buildbot
2018-05-31 14:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 14:03 [binutils-gdb] Add Aarch64 SVE target description sergiodj+buildbot
2018-05-31 14:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 11:05 [binutils-gdb] include: 2018-05-28 Bernd Edlinger <bernd.edlinger@hotmail.de> sergiodj+buildbot
2018-05-31 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 11:00 [binutils-gdb] Improve boostrap-ubsan config (PR bootstrap/64914) sergiodj+buildbot
2018-05-31 10:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31 10:07 [binutils-gdb] * argv.c (expandargv): Fix memory leak for expanded arguments sergiodj+buildbot
2018-05-31 10:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  3:17 [binutils-gdb] Unset gdbarch significant_addr_bit by default sergiodj+buildbot
2018-05-31  3:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  2:45 [binutils-gdb] (ARI) remove trailing newline in call to error in stack.c::func_command sergiodj+buildbot
2018-05-31  2:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  2:01 [binutils-gdb] Remove regcache_raw_supply sergiodj+buildbot
2018-05-31  2:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  1:41 [binutils-gdb] Remove regcache_cooked_write_part sergiodj+buildbot
2018-05-31  1:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  1:08 [binutils-gdb] Remove regcache_cooked_read_part sergiodj+buildbot
2018-05-31  1:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  0:44 [binutils-gdb] Remove regcache_cooked_read_value sergiodj+buildbot
2018-05-31  0:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-31  0:08 [binutils-gdb] Remove regcache_cooked_write sergiodj+buildbot
2018-05-31  0:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 23:40 [binutils-gdb] Remove regcache_raw_write_part sergiodj+buildbot
2018-05-30 23:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 22:37 [binutils-gdb] Remove regcache_raw_read_part sergiodj+buildbot
2018-05-30 22:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 22:21 [binutils-gdb] Remove regcache_cooked_read sergiodj+buildbot
2018-05-30 22:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 21:34 [binutils-gdb] Remove regcache_raw_read sergiodj+buildbot
2018-05-30 22:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 20:58 [binutils-gdb] Remove regcache_raw_update sergiodj+buildbot
2018-05-30 21:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 20:37 [binutils-gdb] Remove regcache_register_status sergiodj+buildbot
2018-05-30 20:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 20:01 [binutils-gdb] Remove regcache_get_ptid sergiodj+buildbot
2018-05-30 20:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 16:57 [binutils-gdb] Add or1k target to --enable-targets=all sergiodj+buildbot
2018-05-30 17:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30 15:56 [binutils-gdb] Mark END_CATCH as ATTRIBUTE_NORETURN (-Wmaybe-uninitialized warnings) sergiodj+buildbot
2018-05-30 15:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30  8:52 [binutils-gdb] Add znver2 support sergiodj+buildbot
2018-05-30 13:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30  1:23 [binutils-gdb] Remove "struct" keyword in range-based for loops sergiodj+buildbot
2018-05-30  2:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-30  0:37 [binutils-gdb] Removing lookup_minimal_symbol_and_objfile sergiodj+buildbot
2018-05-30  0:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-29 23:51 [binutils-gdb] Fix fall-through comment in windows-nat.c sergiodj+buildbot
2018-05-29 23:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-29 19:05 [binutils-gdb] Change program_space::added_solibs to a std::vector sergiodj+buildbot
2018-05-29 20:19 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-29 18:44 [binutils-gdb] Remove a VEC from type.c sergiodj+buildbot
2018-05-29 18:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-29 16:25 [binutils-gdb] Remove tp_t typedef sergiodj+buildbot
2018-05-29 17:01 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-28 19:57 [binutils-gdb] x86-64: Add TLSDESC fields to elf_x86_lazy_plt_layout sergiodj+buildbot
2018-05-28 18:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-28 16:20 [binutils-gdb] ld: Unify STT_GNU_IFUNC handling sergiodj+buildbot
2018-05-28 16:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-27 22:16 [binutils-gdb] Remove last reference to REMOTE_OBS sergiodj+buildbot
2018-05-27 21:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 22:57 [binutils-gdb] Clear entire "location" in value constructor sergiodj+buildbot
2018-05-25 23:14 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 20:59 [binutils-gdb] Remove interp_name sergiodj+buildbot
2018-05-25 21:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 20:32 [binutils-gdb] Change the as_*_interp functions to use dynamic_cast sergiodj+buildbot
2018-05-25 20:37 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 19:42 [binutils-gdb] Use scoped_restore in a couple of interp-related places sergiodj+buildbot
2018-05-25 20:05 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 17:52 [binutils-gdb] Use gdb::byte_vector in remote.c sergiodj+buildbot
2018-05-25 18:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 17:20 [binutils-gdb] Remove cleanups from coff-pe-read.c sergiodj+buildbot
2018-05-25 17:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 15:49 [binutils-gdb] Use TRY/CATCH in remove_prev_frame sergiodj+buildbot
2018-05-25 17:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25 11:59 [binutils-gdb] remote_target::m_remote_state, pointer -> object sergiodj+buildbot
2018-05-25 11:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25  7:27 [binutils-gdb] s12z regen sergiodj+buildbot
2018-05-25  9:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25  7:02 [binutils-gdb] Fix hidden visibility compiler test sergiodj+buildbot
2018-05-25  6:56 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25  1:35 [binutils-gdb] PATCH (obvious): Fix a comment, and pass stream to cb_data sergiodj+buildbot
2018-05-25  1:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-25  0:21 [binutils-gdb] Update help text in record.c sergiodj+buildbot
2018-05-25  0:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 23:53 [binutils-gdb] Update help text in linux-fork.c sergiodj+buildbot
2018-05-25  0:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 23:52 [binutils-gdb] Update help text in record-btrace.c sergiodj+buildbot
2018-05-24 23:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 22:52 [binutils-gdb] Update help text in tracepoint.c sergiodj+buildbot
2018-05-24 22:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 22:04 [binutils-gdb] Update help text in disasm.c sergiodj+buildbot
2018-05-24 22:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 21:53 [binutils-gdb] Update help text for "jump" command sergiodj+buildbot
2018-05-24 22:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 21:16 [binutils-gdb] Update help text in dcache.c sergiodj+buildbot
2018-05-24 21:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 21:10 [binutils-gdb] Update help strings in TUI sergiodj+buildbot
2018-05-24 21:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 20:37 [binutils-gdb] Update memattr.c help strings sergiodj+buildbot
2018-05-24 20:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 20:12 [binutils-gdb] Update core-related help strings sergiodj+buildbot
2018-05-24 20:29 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 20:09 [binutils-gdb] Update help strings in skip.c sergiodj+buildbot
2018-05-24 20:09 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 18:01 [binutils-gdb] gdb: Restore selected frame in print_frame_local_vars sergiodj+buildbot
2018-05-24 18:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 15:23 [binutils-gdb] testsuite: Extend TLS core file testing with an OS-generated dump sergiodj+buildbot
2018-05-24 15:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-24 13:02 [binutils-gdb] Fix macOS build, missing override sergiodj+buildbot
2018-05-24 14:11 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 20:46 [binutils-gdb] Add ATTRIBUTE_NONSTRING to ppc64_elf_write_core_note sergiodj+buildbot
2018-05-23 20:48 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 20:13 [binutils-gdb] Remove struct complaints sergiodj+buildbot
2018-05-23 20:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 19:44 [binutils-gdb] Remove struct complain sergiodj+buildbot
2018-05-23 20:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 19:22 [binutils-gdb] Remove file and line from struct complain sergiodj+buildbot
2018-05-23 19:41 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 18:12 [binutils-gdb] Remove struct explanation sergiodj+buildbot
2018-05-23 18:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 17:33 [binutils-gdb] Remove symfile_complaints sergiodj+buildbot
2018-05-23 17:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 17:01 [binutils-gdb] Remove "noisy" parameter from clear_complaints sergiodj+buildbot
2018-05-23 17:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23 15:59 [binutils-gdb] Remove internal_complaint sergiodj+buildbot
2018-05-23 16:31 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23  3:06 [binutils-gdb] Fix gdb.base/remote.exp with native-extended-gdbserver board sergiodj+buildbot
2018-05-23  2:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23  2:03 [binutils-gdb] gdb/x86: Fix `-Wstrict-overflow' build error in `i387_collect_xsave' sergiodj+buildbot
2018-05-23  2:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23  1:46 [binutils-gdb] MIPS/gdbserver: Correctly handle narrow big-endian register transfers sergiodj+buildbot
2018-05-23  1:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23  1:41 [binutils-gdb] remote: one struct remote_state per struct remote_target sergiodj+buildbot
2018-05-23  1:23 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-23  0:48 [binutils-gdb] Handle "show remote memory-write-packet-size" when not connected sergiodj+buildbot
2018-05-23  1:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 23:57 [binutils-gdb] remote: Small cleanup in compare_section_command sergiodj+buildbot
2018-05-23  0:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 23:27 [binutils-gdb] remote: remote_arch_state pointers -> remote_arch_state objects sergiodj+buildbot
2018-05-22 23:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 22:55 [binutils-gdb] remote: multiple remote_arch_state instances per arch sergiodj+buildbot
2018-05-22 23:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 22:50 [binutils-gdb] remote: Make readahead_cache a C++ class sergiodj+buildbot
2018-05-22 22:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 22:22 [binutils-gdb] remote: Eliminate remote_hostio_close_cleanup sergiodj+buildbot
2018-05-22 22:21 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 21:16 [binutils-gdb] remote: struct remote_state, use op new, fix leaks sergiodj+buildbot
2018-05-22 21:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 20:16 [binutils-gdb] Support UTF-8 identifiers in C/C++ expressions (PR gdb/22973) sergiodj+buildbot
2018-05-22 20:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 19:25 [binutils-gdb] [PowerPC] Recognize isa205 in linux core files sergiodj+buildbot
2018-05-22 19:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 19:13 [binutils-gdb] [PowerPC] Fix inclusion of dfp pseudoregs in tdep sergiodj+buildbot
2018-05-22 19:13 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 18:22 [binutils-gdb] [PowerPC] Fix VSX registers in linux core files sergiodj+buildbot
2018-05-22 18:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 17:34 [binutils-gdb] [PowerPC] Fix access to VSCR in linux targets sergiodj+buildbot
2018-05-22 17:53 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 17:02 [binutils-gdb] [PowerPC] Consolidate linux vector regset sizes sergiodj+buildbot
2018-05-22 17:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 16:47 [binutils-gdb] [PowerPC] Disable regsets using zero sizes in gdbserver sergiodj+buildbot
2018-05-22 16:58 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 15:57 [binutils-gdb] [PowerPC] Consolidate linux target description selection sergiodj+buildbot
2018-05-22 16:12 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 15:04 [binutils-gdb] fix "stale cleanup" internal-warning when using "catch assert" command sergiodj+buildbot
2018-05-22 15:42 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22  6:36 [binutils-gdb] PR23207, hppa ld SIGSEGVs on invalid object files sergiodj+buildbot
2018-05-22  7:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22  1:57 [binutils-gdb] MIPS/Linux: Disable n32 USR `ptrace' accesses to 64-bit registers sergiodj+buildbot
2018-05-22  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22  0:40 [binutils-gdb] MIPS/gdbserver: Fix issues with $zero register reads sergiodj+buildbot
2018-05-22  1:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-21 20:25 [binutils-gdb] Remove output_command_const sergiodj+buildbot
2018-05-21 22:27 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-21 18:46 [binutils-gdb] Remove cleanup from ada_collect_symbol_completion_matches sergiodj+buildbot
2018-05-21 19:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-21 18:22 [binutils-gdb] Remove cleanup from ada-lang.c sergiodj+buildbot
2018-05-21 18:44 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-21 18:16 [binutils-gdb] Remove a cleanup from trace_dump_actions sergiodj+buildbot
2018-05-21 18:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-21  3:57 [binutils-gdb] Fix copy-pasto, allocate objfile_per_bfd_storage with obstack_new sergiodj+buildbot
2018-05-21  4:36 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-21  1:51 [binutils-gdb] Introduce obstack_new, poison other "typed" obstack functions sergiodj+buildbot
2018-05-21  1:52 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-20  0:37 [binutils-gdb] Remove useless variable int i in backtrace_command_1 sergiodj+buildbot
2018-05-20  1:17 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-19  7:33 [binutils-gdb] Fix reference in comment: SRC_AND_LOC instead of LOC_AND_SRC sergiodj+buildbot
2018-05-19  7:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-19  3:06 [binutils-gdb] Allocate dwz_file with new sergiodj+buildbot
2018-05-19  3:06 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-19  2:16 [binutils-gdb] RISC-V: Add RV32E support sergiodj+buildbot
2018-05-19  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-19  1:41 [binutils-gdb] Allocate dwp_file with new sergiodj+buildbot
2018-05-19  3:02 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-19  1:31 [binutils-gdb] Use new to allocate mapped_index sergiodj+buildbot
2018-05-19  2:03 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18 23:56 [binutils-gdb] Remove mapped_index::total_size sergiodj+buildbot
2018-05-19  0:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18 22:33 [binutils-gdb] format_pieces-selftests.c: Silence ARI warnings sergiodj+buildbot
2018-05-18 22:33 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18 20:15 [binutils-gdb] Show padding in ptype/o output sergiodj+buildbot
2018-05-18 20:32 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18 15:27 [binutils-gdb] Add support for the Freescale s12z processor sergiodj+buildbot
2018-05-18 15:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18 14:23 [binutils-gdb] x86: Don't set eh->local_ref to 1 for linker defined symbols sergiodj+buildbot
2018-05-18 14:51 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18  9:45 [binutils-gdb] PR23199, Invalid SHT_GROUP entry leads to group confusion sergiodj+buildbot
2018-05-18  9:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18  4:54 [binutils-gdb] libbfd.h and libcoff.h include guards sergiodj+buildbot
2018-05-18  4:54 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-18  4:22 [binutils-gdb] opcodes sources should not include libbfd.h sergiodj+buildbot
2018-05-18  4:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-17 17:59 [binutils-gdb] Make format_pieces recognize the \e escape sequence sergiodj+buildbot
2018-05-17 18:18 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-17 17:06 [binutils-gdb] Fix for dwz-related crash sergiodj+buildbot
2018-05-17 17:39 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-17 15:55 [binutils-gdb] Updated simplified Chinese translation for the opcodes directory sergiodj+buildbot
2018-05-17 15:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-17 15:50 [binutils-gdb] value.c: Remove unused variables sergiodj+buildbot
2018-05-17 15:22 ` Failures on Fedora-s390x-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).